You can use vmdk2vhd to convert the "broken" vmdk file to a vhd. And then you can just mount the VHD. This has added benefits in that you can use it in VPC as well

Somehow it doesn't feel right though...

I have a few VMs created in VMWare Workstation 6.0. The "host" having been Windows XP and all the "guests" involved are XP as well. These are developer VMs where the main difference for each of them is which tools and frameworks are installed.

In one VM, we created a second virtual disk, to hold documents, source code, and things that are not part of the OS - data if you will. This one common disk "shared.vmdk" is then added as a second disk to all of the VMs. So that no matter which VM you are using at the time, you have this second disk available, and if you modify it's contents then later when you are in a different VM, you still have that data.

Further, VMWare is able to mount this shared disk as a drive even on the host. So that when you are not in a VM at all, but want to quickly get at a document from that disk, it is an easy thing to do without having to boot up a VM at all. We use this a lot.

So, now that we are trying to upgrade to 6.5 the problem is, VMWare 6.5 is unable to mount this shared disk to the host. Booting into a 6.5 VM that has it attached works fine. It just cant mount it in the host.

Thanks,

Travis