Never mind, took another look at this program... was going to say the following and much more:
It's because around line #4124 of this program, in "ReadConfigFile" subprogram, this program uses ENVIRON$() like crazy to obtain configuration.
Only the beginning of it asks for like 10 variables set LOL.
One thing that it does is create a "C:\TEMP" if it doesn't exist, to hold some temporary files.
The save or open file requester should begin in the user area, not "Program Files", to make life easier for most people. It looks like the "GetConfigFileName" subprogram is hardwired to start the dialog into "Program Files". On 64-bit this would never go into the 32-bit directory, that's why it's not advised to start there or anywhere Windows wants to put a "smart screen" on the user.
It's because around line #4124 of this program, in "ReadConfigFile" subprogram, this program uses ENVIRON$() like crazy to obtain configuration.
Only the beginning of it asks for like 10 variables set LOL.
One thing that it does is create a "C:\TEMP" if it doesn't exist, to hold some temporary files.
The save or open file requester should begin in the user area, not "Program Files", to make life easier for most people. It looks like the "GetConfigFileName" subprogram is hardwired to start the dialog into "Program Files". On 64-bit this would never go into the 32-bit directory, that's why it's not advised to start there or anywhere Windows wants to put a "smart screen" on the user.