The following issue may very well be related to Windows and/or OS X, and have nothing to do with Parallels, although I thought I'd post here to see if anyone else is experiencing this behavior. I have a Mac Pro with the latest OS X update. I run Windows XP SP3 through Boot Camp and Parallels. There are three physical hard drives in my system (2 HFS+, and 1 NTFS). When I boot into WinXP via Boot Camp, I use MacDrive to access the HFS+ drives, and it appears to work very well. When I boot into WinXP via Parallels, MacDrive doesn't work, so I instead map the HFS+ volumes to the same drive letters as network shares. All appears to work well until I attempt to set the "Read Only" flag on files (on a HFS+ drive) in Windows or CHMOD 444 through Terminal. When Parallels isn't running, I can use Terminal to set a given file to read only (444) "-r--r--r--". If I then start Parallels, and browse to the file using Windows Explorer, the file *usually* reports that it's "read only" (I added the Attributes column to the Details view" so I can see the state without touching the file). At this point, I can still check in Terminal using "ls -l" to verify the permissions are still set. If I go to Windows Explorer, and right-click the file and choose Properties, it reports the file is read only. At this point, even if I Cancel out of the properties panel without changing anything, if I check Terminal again with "ls -l", the permissions are now "-rw-r--r--". What's going on here? Sometimes, I've noticed that there is a delay between when I check the file properties in Explorer, and the permissions getting reset in Terminal, although at some point after checking Explorer, if I have a Mac Finder focused on the folder where the file resides, I'll see the Finder flash as it updates the folder contents, and only after that will the permissions be reset when I check in Terminal. I don't know if this has to do with the way Windows sets permission on network shares or shared Mac HFS+ drives, whether this is caused by Finder maintaining a permission setting that gets reset automatically, or whether this has something to do with Parallels or the fact that MacDrive is still running in the background in WinXP. Do anyone have *any* suggestions on how I could fix this? If possible could someone please attempt to duplicate the behavior on their system? I'll also take suggestions on any forums that you feel may be able to provide a solution. I use Perforce for development, and all files in the local workspace should be "read only" unless I've checked them out for modification. Because the "read only" flag/permission is being reset, Perforce fails to update all the affected files. I *really* need to prevent the flag from being reset.
We are aware about this , and developers are working on this problem. You can try to disable Shared Profile and Shared Folders as workaround
