it's a long story. the short version is:
I seem to be missing the need (or the reason for choosing) the .vhd format as opposed to a normal RAW one?
i'm working on "Register Factory".
"Register Factory" is a set of scripts to run installations inside
a VM. The VM starts a copy of your build from attached virtual HDD and installs OS components and software , registers dlls ..
Then files and changed registry settings are transferred to your build.
.vhd files (uncompressed) are raw files (+512 extra bytes for vhd footer) and can be used for ImDisk,QEMU,VmWare,VirtualBox AND VirtualPC (and for Vista x64/vhdmount). However , ApiRegUtil works
for 'normal RAW' files as well as for excel files.
In any case, if I may, I would suggest to "call things with their names", such as:
ApiRegutil makehddinfo "C:\ramdisk.vhd" "C:\newhddinfo.txt" 40
Its only a syntax example.
ramdisk.img is the input file.
Any type of file will work (.vhd is not required)
Yes , sorry for imprecise terms
.img is the extension generally used for RAW disk images.