Many of my source files that were edited under Beta 6 are now opening up with binary garbage in them. The file contain only references to Parallels. It's highly intermittent but happens through the new Guest folder or network loopback connectivity. I've been able to get it to happen by saving from within various development tools and text editors.
I find Beta6 very stable, although I encountered "challenges" with Shared Folders. However, I did end up turning on Windows Sharing on OS X and downloaded a copy of SharePoints to restrict the Windows Filing Sharing to one or two special folders. I then used the XP image to map to those drives. I can read and write to them within PW without error. I've actually set it up now so that all my source files are in these folders on the Mac, and the Windows-specific programs access these source files by mapped network connections. Been working flawlessly for me...and...when PW is shutdown, all my updated source files are in the specified directories on the Mac. So, I can easily back them up and transfer them without having PW running.
I wouldn't recommend to share all Mac OS X files to guest OS via shared folders tool. It goes opposite to concept of safe VM sandbox. Better to create special transfer folder and map it as shared folder.
I didn't map all files, I have a separate directory within a user home directory that both sides will need to talk to (development files). When using the Shared folders (//.host/...) the files are often corrupted when saved from within the guest apps. All that is left in the file is some binary text with the words 'Parallels' and various version data. All of the corrupted files, thus far, are text files that are being edited and saved. When I create a SMB network share from OS X and map to that within the guest OS, it works fine. It's the bequethed shares that are having problems.
