Making a project "standalone"? Configuriung it as well?
Forum rules
Before asking on how to use a ZDoom feature, read the ZDoom wiki first. This forum is archived - please use this set of forums to ask new questions.
Before asking on how to use a ZDoom feature, read the ZDoom wiki first. This forum is archived - please use this set of forums to ask new questions.
Re: Making a project "standalone"? Configuriung it as well?
But why bring up write protection? Nobody is setting it to nor does portable imply write protected.
- wildweasel
- Posts: 21706
- Joined: Tue Jul 15, 2003 7:33 pm
- Preferred Pronouns: He/Him
- Operating System Version (Optional): A lot of them
- Graphics Processor: Not Listed
- Contact:
Re: Making a project "standalone"? Configuriung it as well?
Program Files has implied write-protection in recent versions of Windows, except under specific circumstances (i.e. installing new applications). It's part of Windows' attempts to be more secure, though in practice all it really does is add confusion.maseter wrote:But why bring up write protection? Nobody is setting it to nor does portable imply write protected.
- InsanityBringer
- Posts: 3392
- Joined: Thu Jul 05, 2007 4:53 pm
- Location: opening the forbidden box
Re: Making a project "standalone"? Configuriung it as well?
I believe at one point (there still might be but I haven't heard of it) there was a "virtual folder" concept where when things tried to write to Program Files without administrator privilege, the write would silently be redirected to a user folder, which under ideal circumstances the program would see as the actual folder. This did have some weird issues in practice.
- Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49252
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: Making a project "standalone"? Configuriung it as well?
wildweasel wrote:Program Files has implied write-protection in recent versions of Windows, except under specific circumstances (i.e. installing new applications). It's part of Windows' attempts to be more secure, though in practice all it really does is add confusion.maseter wrote:But why bring up write protection? Nobody is setting it to nor does portable imply write protected.
So,under Windows it adds confusion, but under Linux it's good practice to write protect critical stuff? The main reason for this is that some badly behaved software can't trash your installed programs and you can bet that, if this wasn't the case, some malware would happily trash that stuff.
(Of course, it can still get bad if some software does not run without its app data present in write enabled directories. Any good program should be able to recreate these but I've seen it more than once that they just crashed instead of just resetting it to a base state.)
- wildweasel
- Posts: 21706
- Joined: Tue Jul 15, 2003 7:33 pm
- Preferred Pronouns: He/Him
- Operating System Version (Optional): A lot of them
- Graphics Processor: Not Listed
- Contact:
Re: Making a project "standalone"? Configuriung it as well?
Well, considering the number of software glitches I've seen that all spawned from the program being run out of Program Files (saved games not being properly read and located, etc), I'm basically inclined to never, ever install things into it unless I have no choice.