We've just set up Windows XP user (i.e. not administrator) accounts on our test system for use by the operators. Whenever our operator interface opens a sequence, we get the following message:
Could Not Create Temporary File
Error writing to file 'C:\Program Files\National Instruments\TestStand 3.5\Cfg\TestExec.ini
NOTE: This error can occur when writing files in the TestStand configuration directory if you do not have permissions to create or write files in that directory. To fix the problem, you can either change the settings on the coniguration directory, or change the location of the configuration directors on the Preferences page of the Station Options dialog.
Unable to save the changes to the TestStand configuration.
TestStand will not display this message again for errors saving this file during this session.
Two suggested workarounds are given in the error message itself. Both of these solutions involve giving the operator write access to the Cfg directory.
My question is this - should it be necessary to give the operator write access to the cfg directory? I would instinctively prefer to give them read-only access, as at present. There shouldn't be any reason for the operators to need to change anything, indeed it is vastly preferable that the configuration never changes.
Is there some unusual reason why TestStand needs to access this directory in our case, or does it always attempt to write to this file when a sequence is opened? Execution of our sequences works fine beyond this point, so there obviously isn't any real need to write to these files.
I would like to know whether there is a way to keep the CFG directory read-only but prevent this dialog from appearing, as it is alarming for the operators. Is there something I can do to either:
- Stop TestStand from attempting to write to the CFG directory
or:
- Stop it from displaying this dialog when it finds that it has read-only access
To replicate this problem, just set up a new Windows XP user and start TestStand. The message will then appear as soon as a sequence is loaded. Although it sometimes doesn't - I haven't yet been able to work out the logic of when and why it appears.
