Old Marine
Member
My MacBook Pro running Leopard 10.5.1 and Parallels Desktop build 5160 has been unable to successfully get Parallels Tools installed and operating correctly since upgrading from Tiger to Leopard several weeks ago.
After getting a Parallels error message yesterday telling me to "Re-install Parallels Desktop" I backed up all Windows data and reloaded Parallels. Doing so did not resolve the problem.
Symptoms of problem is when I attempt to open any Office attachment to an Outlook message I get an error message telling me
"Parallels Desktop cannot open file C:\Documents and Settings\Administrator\Local Settings\Temporary Internet Files\OLKF5\DOCSSEA.DOC from the guest OS. You can open only files located on Windows drives (volumes) which have drive letters assigned or in Parallels Shared Folders".
I did note on one of the forums that installing an update to MacFuse would help address some of the problems being experienced by Parallels users with Leopard upgrades, but after installing that update I had no change in symptoms or the problem.
I would like to know if this is a common problem, whether there is a known workaround, and if it is on the radar for Parallels to address with the "to be announced" Leopard compatible release?
Ann feedback or comments appreciated
After getting a Parallels error message yesterday telling me to "Re-install Parallels Desktop" I backed up all Windows data and reloaded Parallels. Doing so did not resolve the problem.
Symptoms of problem is when I attempt to open any Office attachment to an Outlook message I get an error message telling me
"Parallels Desktop cannot open file C:\Documents and Settings\Administrator\Local Settings\Temporary Internet Files\OLKF5\DOCSSEA.DOC from the guest OS. You can open only files located on Windows drives (volumes) which have drive letters assigned or in Parallels Shared Folders".
I did note on one of the forums that installing an update to MacFuse would help address some of the problems being experienced by Parallels users with Leopard upgrades, but after installing that update I had no change in symptoms or the problem.
I would like to know if this is a common problem, whether there is a known workaround, and if it is on the radar for Parallels to address with the "to be announced" Leopard compatible release?
Ann feedback or comments appreciated