1 members, 4 guests, 0 anonymous users"
Now what is all this nonsense about.
VHD images are not quite raw. Maybe you're thinking of a flat vmdk file, which has two components:
[/size][/font][/color][/background][background=rgb(249, 249, 249)] 251904 Virtual Disk 3-flat.vmdk[/background] 8 Virtual Disk 3.vmdk
The header information is stored in a teency little file there, and the -flat.vmdk is totally raw.
In the case of your equivalent VHD file, the header for the VHD file is stored at the beginning, and the MBR and everything else is pushed back.
[size=4]If they were really raw images, then Unix would be able to identify them:
nas:/Volumes/VHDs# file *vhd WindowsXpVhdImportDiscUtilClone.vhd: Microsoft Disk Image, Virtual Server or Virtual PC nas:/Volumes/VHDs#
But if you're trying to say "They're RAW files, but with a small offset" then I would agree.
[color=#282828][font=georgia, serif][background=rgb(249, 249, 249)]Yes I know that this is a year too late, but I'm trying to google for that thing that loads VHD files directly... whatever it is... or does it load WIM files directly... I can't remember now... all I know is I'm sick of having to repair my VHD boot and I want to take it out on someone.