The settings files (devcpp.ini, devcpp.cfg) are stored
in the shell Application Data folder. On networks where
that folder has been redirected to a network location
via Active Directory policy, the redirection is not
respected. The settings files are still stored in (for
example) C:\Documents and Settings\UserName\Local
Settings\Application Data rather than the expected
network redirect location.
The net result is that the user settings are lost
everytime the user logs out.
Logged In: YES
user_id=609236
shouldn't it be transparent to the program? (meaning the
path) If the program is saving in that location not
respecting the redirection, it should still be able to read
from there. I'm just not sure how it's supposed to work...
Logged In: YES
user_id=11142
Theoretically, yes. But, apparently in reality there is some
Microsoft Magic required to handle it properly. I guess
DevCpp is using SHGetFolderPath, but apparently that doesn't
do the right thing. I don't know what the special trick
might be.
Normally, Windows would save the local contents of the
Application Data folder into the user's roaming profile when
they log off. If the folder has been redirected, it doesn't
since it assumes that stuff is already stored remotely and
it would be redundant.
One thing that would certainly solve the problem would be to
store these settings in the registry under current user
instead of using an ini file. The TRegIniFile object ought
to make that change pretty transparent.