When I try to install an app (*.msi) from a shared folder I get an error from Windows Installer telling that the installer could not be opened. When I copy the file to the VM and start from there it installs well. This does not happen with *.exe installers.
It does happen with some .exe installers, if they are wrappers for .msi's. I had the same thing happen with the Boot Camp drivers.
It does happen with some .exe installers, if they are
wrappers for .msi's. I had the same thing happen
with the Boot Camp drivers.
But this should not happen shared folders should always work without problems... I also find that they work very slowly, but this I reported in another thread...
Are you referring to the VMware shared folders feature, or actual Network Shared Folders, handled by your OS? The VMware Shared Folders has had numerous issues known about for years... it's basically meant to be a quick and dirty way of sharing files easily; but it is NOT a robust solution. If you want a robust solution, use standard network shares (MS Windows File Sharing / Samba / whatever OSX uses).
Are you referring to the VMware shared folders
feature, or actual Network Shared Folders, handled by
your OS? The VMware Shared Folders has had numerous
issues known about for years... it's basically meant
to be a quick and dirty way of sharing files easily;
but it is NOT a robust solution. If you want a
robust solution, use standard network shares (MS
Windows File Sharing / Samba / whatever OSX uses).
I'm speaking of Fusion shared folders. Sharing my MAcOSX files with the VM.
And if this is NOT a ROBUST solution than it definitely should be!!