VMware Communities
bryceds
Contributor
Contributor
Jump to solution

Unable to open file"/...../Windows XP Professional.vmdk: The system cannot find the file specified

OS X 10.8.4

Windows XP

Fusion 4.1.4 (900582)

Noob here. I started running a Sugarsync backup of the files on my computer and now my VMware for XP won't work. My other VMware for Windows 7 does work for some reason. Interestingly enough, my system does have the file it says it is missing. Here is what the file says in notepad. Any help?

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=2323c8bf

parentCID=ffffffff

isNativeSnapshot="no"

createType="twoGbMaxExtentSparse"

# Extent description

RW 4192256 SPARSE "Windows XP Professional-s001.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s002.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s003.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s004.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s005.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s006.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s007.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s008.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s009.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s010.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s011.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s012.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s013.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s014.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s015.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s016.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s017.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s018.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s019.vmdk"

RW 4192256 SPARSE "Windows XP Professional-s020.vmdk"

RW 40960 SPARSE "Windows XP Professional-s021.vmdk"

# The Disk Data Base

#DDB

ddb.virtualHWVersion = "8"

ddb.longContentID = "1029bce55d0fad15a59048fa2323c8bf"

ddb.uuid = "60 00 C2 92 d9 39 d0 8a-11 98 13 d7 e3 6f 53 c2"

ddb.geometry.cylinders = "5874"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "56"

ddb.adapterType = "buslogic"

ddb.toolsVersion = "8452"

0 Kudos
1 Solution

Accepted Solutions
WoodyZ
Immortal
Immortal
Jump to solution

That would probably be the easiest, otherwise you have to rename the three that are correct and also change all in the Disk DescriptorFile and edit the .vmx file.  So the path of least resistance is to rename the actual Extents so all 21 have this form: "Windows XP Professional-s###.vmdk"

View solution in original post

0 Kudos
7 Replies
WoodyZ
Immortal
Immortal
Jump to solution

To help figure out what is what, the best way to provide comprehensive diagnostic information is to use the "Collect Support Information" command from the VMware Fusion (menu bar) > Help > Collect Support Information and then attach the .tgz file it created on your Desktop to a reply post.

Note: Use the "Use advanced editor" link in the upper right corner of the normal reply window to bring up the Advanced Editor where you'll be able to attach files via the Choose File button or Browse button (depending on the Browser) above the Post Message button!

0 Kudos
bryceds
Contributor
Contributor
Jump to solution

See attached

0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

The problem is that while the Disk DescriptorFile shows the Extents named as "Windows XP Professional-s###.vmdk", the actual names of most of the Extents are showing as "Windows XP Professional-s### (from Mortgageones-mac-mini).vmdk" from a listing of the files within the Package.

0 Kudos
bryceds
Contributor
Contributor
Jump to solution

To resolve, would I just need to take out "from Mortgage....)"? From every file?

0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

That would probably be the easiest, otherwise you have to rename the three that are correct and also change all in the Disk DescriptorFile and edit the .vmx file.  So the path of least resistance is to rename the actual Extents so all 21 have this form: "Windows XP Professional-s###.vmdk"

0 Kudos
bryceds
Contributor
Contributor
Jump to solution

Excellent. That worked. Thanks for the help.

0 Kudos
WoodyZ
Immortal
Immortal
Jump to solution

That's good, I'm glad it was an easy one.

BTW Not sure where the "(from Mortgageones-mac-mini)" came from however you should be able to remove the remaining files that have "(from Mortgageones-mac-mini)" in the name from within the Virtual Machine Package as they shouldn't be needed.

0 Kudos