I have two disks as<code>.vmdk</code> </span>
<span style="border-collapse: collapse; font-family: Arial,'Liberation Sans','DejaVu Sans',sans-serif; line-height: 18px; text-align: left" to mount the virtual disk.The disk may be inuseby a virtual machine, may not have enough volumes or mounted under another drive letter.Ifnot, verify that the file is a valid virtual disk file.</span></code>
<br /><br/><br/><br/> Thinking it's a problem with the utility, I downloaded the SDK and made my own simple program in C to try to mount a disk. It just initializes the API, connects to it, then attempts to open the disk. I get this error, once again claiming it is not a virtual disk:<br/><br/><br/><br/>
<code>
LOG: DISKLIB-DSCPTR: descriptor above max size: I64u
LOG: DISKLIB-LINK :"f:\programming\VMs\windowstrash.vdi": failed to open (The file specified isnot a virtual disk).
LOG: DISKLIB-CHAIN :"f:\programming\VMs\windowstrash.vdi": failed to open (The file specified isnot a virtual disk).
LOG: DISKLIB-LIB :Failed to open 'f:\programming\VMs\windowstrash.vdi'with flags 0x1e(The file specified isnot a virtual disk).
FAILURE
:The file specified isnot a virtual disk</span></code>
The files are clearly virtual disks, though, since I can actually mount
and use them with a virtual machine. I tried detaching them from any
VMs and trying again, but I got the same results.
<span style="border-collapse: colla<p>Any ideas? Maybe the "descriptor above max size" is a hint?</p></span>