Hi there,
I am the main developer for the VMware Shared Folders feature, and it does sound like you have hit a known issue.
This issue is that our character escaping mechanism to deal with cross platform incompatibilities with file systems is broken for this case.
The Finder allows a user to enter forward slashes in files and folder names. This is is really a colon character in the OS X file system.
Just launch a terminal shell window and do an "ls" command on that folder containing the file with "forward slash" in it. You will see that it
really has a colon character.
The VMware Shared Folders will modify that colon character which is illegal in Windows to the "^%" combination so that it can be displayed in Windows applications.
(I should stipulate, that it is not modified on disk, only the name is modified internally to the VMware Shared Folders file system prior to returning to the system and user
mode applications in the Windows VM.)
The Windows applications should then all use the name with the modified character which will be converted when sent to the Shared Folders server to access the host
file containing the colon. We have to modify any characters the OS X file system has which are not legal for Windows.
The following characters are invalid as file or folder names on Windows using NTFS:
/ ? < > \ : * | ” and any character you can type with the Ctrl key
This is currently broken for this scenario. I hope to look at for the next release.
The only workaround I can suggest is really to avoid the character (Finder using "/" or using shell and ":") in the in the file names if possible until this is fixed.
Thanks for reporting.
I hope this helps.
Steve