I'll take a look at this on VMware server 1.0.7. 

As a work around, you could try creating the VMDK file with VMware first (using add disk in computer properties) and then ghosting to that VMDK file by using the '/addDisk' switch to force ghost to not recreate the VMDK.

The ghost command line would then look something like this:

ghost32 -clone,mode=restore,src=image.gho,dst=50 -addDisk=disk.vmdk

NOTE - Ghost and the standard tools (like omnifs32) always start numbering VMDK disks that are added from 50.

By letting VMware create the virtual disk the format should be compatible with VMware server 1.0.7.

Regards, Robert.

You suggestion does work, but is slightly annoying. ....no offense. It would be much easier to creat the vmdk on-the-fly. Which VMware products currently work w/ the vmdks from ghost? What do you guys normally use for testing? (e.g. player, workstation 5 or 6)

Thanks for looking into this,

*bump*

Any progress?

Yes - sorry for the delay.  A build is ready now which adds a switch that can be specified that enables VMware Server 1.0.7 to be targeted.  The switch is '-vmdkVersion=4' where the version number is an internal VMware hardware version setting that VMware Server is checking.

Please send me an email to robert_chester at symantec dot com and I'll make the new version of ghost available to you.  I'm assuming at this stage that you only need Ghost32.exe - please let me know in the email if you need more than this.

Regards, Robert.