by COBS Tech Support » Tue May 16, 2006 4:25 pm
Not being familar with your network enviroment it's not possible for us to be too specific. However, we may be able to point you in the right direction. A skilled IT person should be able to hunt down the reason why this is happening.
Basically local settings in CAPITAL are stored in 3 different .INI files, depending on what the setting is:
CAPWIN.INI, which sits in either the \Windows folder of your local computer, or a user profile folder, depending on how Windows and your network is set up and which operating system version you are running.
Then there is the global file CAPSYS.INI which is found in your \CAPITAL folder. (This file may or may not exist in your particular environment.)
Then there are user specific files that all begin UserNNNN.INI where NNNN starts at 0000 and goes up to 9999.
One or more or all of these files are set to "read only" so CAPITAL cannot change these files. Or, the operating system has locked these files down so that CAPITAL cannot change their contents. This could be a security setting or setup issue of some kind. In larger companies the whole Windows environment for users is 'locked down' so that users can't change their desktop settings, or any of their local configuration settings, to achieve standardisation across the organisation. That is an admirable goal, but setting up the Windows environment in this way disables a lot of useful functionality that users want, such as the ability to save their preferred settings.