Permissions issue with Studio
chill
Posts: 186
I've been trying to set up a Windows 2000 environment at home for the purpose of coding Netlinx. In an effort to make Windows semi-secure, I've set up a "normal" user which I will use for routine non-sysadmin work, e.g. Netlinx coding. This user is a "user" in Windows 2000 terminology, i.e. no access to system areas. My theory is that when the system gets 0wn3d, rogue processes won't be able to do damage because they're running as a non-privileged user.
[Why 2000 and not something newer? Because that's what I have an installer CD for, and I'm not going to buy a new PC when I don't need to.]
In the course of testing things, I've found that Studio 2.4 (build 2.4.0.126) apparently wants to write files to c:\{blahblah}\system32\config, which of course "user" isn't allowed to do, so the compiler fails with
'ERROR: (0): C10580: Internal Error: Major system error occurred during code generation'
If I set permissions on c:\{blahblah}\system32 so that "user" has read/write/modify access, the error goes away, but this defeats the purpose of the existence of "user".
Is there some workaround, or do I just have to live with not being able to get any work done unless I'm root?
Many thanks in advance for any suggestions.
[Why 2000 and not something newer? Because that's what I have an installer CD for, and I'm not going to buy a new PC when I don't need to.]
In the course of testing things, I've found that Studio 2.4 (build 2.4.0.126) apparently wants to write files to c:\{blahblah}\system32\config, which of course "user" isn't allowed to do, so the compiler fails with
'ERROR: (0): C10580: Internal Error: Major system error occurred during code generation'
If I set permissions on c:\{blahblah}\system32 so that "user" has read/write/modify access, the error goes away, but this defeats the purpose of the existence of "user".
Is there some workaround, or do I just have to live with not being able to get any work done unless I'm root?
Many thanks in advance for any suggestions.
0
Comments
Vinc
Slang update - at least that I've seen online recently - due to some haxzor slipping a keystroke, the "in" term is currently "to be pwned". (It's pronounced "powned" - just like owned with a p in front)
- Chip (keeper of all things inane and arcane)
Hey - Xbox live - it's all about being vocal. (That's both good and bad)
- Chip