CompuServe Messages

I agree completely. If the config file is in the program's source directory, then use it, otherwise start searching the system for it – ie. ENVARC, etc… Vic makes the point that under 1.3 a program cannot tell what directory it started from (if CLI started), so that this option may not be as viable as I'd wanted. I know I use several programs (Imagine, IP, etc) that will only find their config files if I start the program while IN the programs directory…. (ie. if I'm in RAM: and I type: RUN DH0:ANIMS/IMAGINE/IMAGINE then the program runs, but the config file (which exists in the program directory) isn't loaded. Of course one could require an ASSIGN of Imagine, which the system could use to search for the config, etc…. or one could do a quick batch file to switch to/from the directory. Not elegant, though. Anyway, I'd vote with you; allow me to put CONFIG's in the program directory if possible, and otherwise in some system-generic place. –jp–seattle–