I have the same problem with Fusion 2.05 and Win XP SP3. Running Fusion on OS 10.5.7.

Yes, this is an annoying problem, will look into this today.

Thanks for reporting this.

Steve

Since I downgraded. I can only answer these two:

Hopefully someone else can provide the other infos:

I tryed differend letter but this didn't help.

and I can't access any shared folder by drive letter mappings.

Answers to your questions:

After the upgrade to the 2.0.5 tools the Windows VM was rebooted, is that correct? --> YES

Then accessing your Z: drive gives you the error message, can you upload a screen shot of the error message? --> see it attached (I'm sorry, it's in Spanish, but fully understandable, I hope)

Also using a command prompt and issuing:
net use z: /D
net use z: file://.host/Shared Folders
cd /d z:\
This also results in an error too? --> same error

How about if you replace the z: above with a different drive letter? --> I did try it before, same problem

Can you access any drive letter mappings to VMware shared folders? --> no by mapping, I can access navigating from the desktop shortcut or from "My networks"

Furthermore, what does the registry setting key have (using regedt32.exe)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmhgfs\networkprovider\
Key: ProviderPath
Type: REG_SZ
Value: "C:\Windows\System32\vmhgfs1.dll"
Or
"C:\Windows\System32\vmhgfs.dll"
--> it says "C:\Windows\System32\vmhgfs1.dll"

If you use Explorer and right click on properties and version tab for this file, what does the "File Version:" say? --> 8.0.6001.18702

Hope it helps,

David Esteban

What you suggest is something like what I did by accident. I'm no longer having the issue.

I messed up my attempt to downgrade back to 2.04 by forgetting to remove VMWare Tools before doing so. So I couldn't install the earlier version of VMWare tools, and the mapping problem still existed. At that point I uninstalled 2.04, went back to 2.05, tried to uninstall the tools, had the uninstaller crash several times, then decided to try to repair the VWWare Tools and do the uninstall again. Instead, the repair/remove options did not come up that time, and the installer installed the VMWare tools under 2.05 from scratch. Before uninstalling them and rolling back to 2.04 properly, I decided to check on the drive mapping... and it was working! So somewhere in that mess I may have forced a remapping of the Z: drive. I don't know.

I did try uninstalling and reinstalling the VMWare Tools before trying to downgrade, and that didn't work. Something in all the messy stuff I describe above did the trick, but I don't know what.

NEW - NEW - NEW

I've uninstalled VMware Tools, completely, and installed them again from scratch. It works now. I've got unit Z: back, working perfectly well.

I'm somewhat surprised, however, seeing that I've an A: unit (????) and a D: unit VMware Tools. (????) --> see file attached

David Esteban

No floppy disk, I'm afraid (MacBook Pro machine) ... as far as the D: unit I understand it has been mounted by the installation process ... is that correct? (I can not see it on the Mac's desktop ...