Siarzhuk Zharski <zharik@xxxxxx> wrote:
> I tried to figure this problem out by yourself, activated TRACE-ing
> in
> vfs.cpp and vfs_boot.cpp. But this doesn't help me much. Which module
> generate this "bfs: Mount:347: Invalid Argument"? May be you have any
> idea about this mounting problem? Of course, I can provide complete
> system log if it is required.
That won't contain more info either - as the "bfs:" suggests the
component in question is bfs. And there, you can find the problem in
Volume.cpp, line 347.
If I have the same version of that file that you have, the following
check fails:
if (diskSize < (NumBlocks() << BlockShift()))
RETURN_ERROR(B_BAD_VALUE);
Which means the disk size your VPC converter advertizes is lower than
what BFS has been initialized with.
> 1) May this possibility to make VPC-ready Haiku images be useful for
> us? In other words - should I invest a bit more time to bring my
> "vhdconverter" to production quality? :-) Currently it can produce
> fixed-size virtual drives. But mentioned VHD specification allows to
> produce sparse files that can decrease resulting size of the disk
> image
> and use images with any reasonable size.
We also have support for VMware stuff, so why not. Since the
VMwarePlayer is free to use, that might be enough for most, though :-)
> 2) Is information obtained from document under "*Microsoft Open*
> Specification *Promise*
> <http://www.microsoft.com/interop/osp/default.mspx>" license safe to
> be
> used during development for Haiku? In my case that was just reading
> VHD
> file specification.
That's a pretty ridiculous license to start with, but as long as we
don't ship with it, it should only affect those who are actually using
it which is acceptable IMO.
Bye,
Axel.