etung and/or steve goddard,

Has there been any official word on PR 422610? Is there some way to track that via the web? I really hope to upgrade to 10.6 soon and I'm afraid that Fusion support in version 2.0.4, which I'm running to avoid this issue, is not going to be there.

Any advice?

Steve,

I have simply downgraded since there was nothing in 2.0.5 I needed. The only concern I have right now is finding out when (if?) this issue will be addressed in 2.0.5 and also getting an answer about Snow Leopard support for 2.0.4 so that I can upgrade my OS even if this issue is not yet resolved. I asked that on another thread (http://communities.vmware.com/message/1346570#1346570).

Thanks for any insight.

Sadly, our installer guys don't seem to comprehend testing all scenarios or even code inspection.

This installer bug has been fixed in the Fusion 3.0 releases though, and I personally tested it myself, 32 and 64 bit VMs both.

However, did you try the workaround for the installer nonsense? That is, uninstall the VMware Tools using the control panel Add or Remove Programs, reboot VM, do your upgrade to Fusion 2.0.5 and
then install the VMware tools, reboot the VM.

This should then get your network drive mappings working. If you did the above and the drive letter access still fails for some reason, then you are hitting a different bug.

Thanks.
Steve