I just noticed that on Windows XP Pro and XP home, that when I look at the properties of any directory from Windows explorer, it indicates that they are "read only" even though I have never set them as such. I try to change the read only attribute and apply it, it seems to change it, but as soon as I check the properties again, it is still listed as read only. What is up with that? Has a recent security update caused this stupid bahavior?

The reason that I even fould this is that I have my application data on Windows XP box, and the application is on various OS boxes accessing a shared drive on the XP box. Files that existed for a long time are not set as read only and the application can access them and update them without a problem. A problem occurs then the application creates a new table or file on the XP box. The newly created file evidently inherits the parent directory's read only attribute and I cannot update it. I guess I could change the read only attribute after creating a file but what a PITA. This has worked for years but now suddenly it doesn't and it is causing errors any time it has to create a file or update a newly created file. When did this change? Was this the result of MS trying to fix some holes in the OS to prevent virus infection or perhaps the result of some virus that I have somehow picked up? My virus protection is Mcafee and it is being updated practically daily. I even tried disabling Mcafee and changing the read only attributes with no success.