WARNING for Vista users! READ!!!
Posted: Thu Jan 22, 2009 2:55 am
Hi,
since I had a hell lot of trouble with it and the problem isn't easy to notice, I'm writing this here again (the thing just has been discussed in a different thread):
If you edit any files, like an oxp's plist in the AddOn folder of Oolite, Vista behaves the following way:
The original file stays untouched! Vista creates an AddOn folder in your users VirtualStore and stores the changed file there. Oolite will use that file and your editor will pretend that the original file has been changed, which is NOT the case.
As soon as you uninstall or update the oxp or use the game with another user, you're in deep trouble!
Workaround: Move the changed file from virtual store to the real location and then delete the VirtualStore's AddOn folder. As a result, you do not only have the proper file at the proper location for all users, you can also edit it without any more "VirtualStore" problems. Still it's a good idea to verify after each editing that no VirtualStore usage is happening again!
That's a common Vista problem. Someone thought it would be a good idea, but even Vista-internal programs get screwed up with this.
Screet
since I had a hell lot of trouble with it and the problem isn't easy to notice, I'm writing this here again (the thing just has been discussed in a different thread):
If you edit any files, like an oxp's plist in the AddOn folder of Oolite, Vista behaves the following way:
The original file stays untouched! Vista creates an AddOn folder in your users VirtualStore and stores the changed file there. Oolite will use that file and your editor will pretend that the original file has been changed, which is NOT the case.
As soon as you uninstall or update the oxp or use the game with another user, you're in deep trouble!
Workaround: Move the changed file from virtual store to the real location and then delete the VirtualStore's AddOn folder. As a result, you do not only have the proper file at the proper location for all users, you can also edit it without any more "VirtualStore" problems. Still it's a good idea to verify after each editing that no VirtualStore usage is happening again!
That's a common Vista problem. Someone thought it would be a good idea, but even Vista-internal programs get screwed up with this.
Screet