The thing that scares me about your approach, is the (some software will not operate correctly with the system attribute" disclaimer. I would be very reticent to change any installations default system behavior if it might cause problems for other software down the road.
Obviously, this is a generalization, and in your case may prove to be benign. Bob On Aug 11, 2010, at 10:34 AM, Mark Talluto wrote: > Today we had an issue with XP and its intentional desire to set folders in > specialPath(26) to read only. If you ever find that your update tech or > prefs logic fail when it shouldn't, you may have fallen victim to permissions > being set to read only. Keep in mind that MS does this on purpose in XP > under certain circumstances. The link below explains the issue further. It > also has a workaround to clear this up. A restart of the OS is required for > it to take effect. > > I hope this helps you solve this issue for your clients before it becomes a > bigger problem. We are considering adding code to our products that set this > registry key up automatically to prevent this from happening again. > > http://support.microsoft.com/kb/256614 > > > Best regards, > > Mark Talluto > http://www.canelasoftware.com > > > > > > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
