CompuServe Messages

I can't recall any instructions from C= regarding putting configuration files in S: … I thought the only "standard" that C= ever establihsed was that configs went into DEVS: (by their own inclusion of system.config). Why do you think it important to keep parameter files in one place? I can actually see no good reason why they should be stored thus … one ends up with a major hotch-potch of files sat in S: … when I do my periodic stock-take of the HD it's often difficult to work out which config file is being used for what. As has already been suggested, sometimes I want two or three different set-ups of the same software … and allowing me to keep a config file in the application directory or a volume makes life very much easier. It is just _so_ easy for programs to allow configs almost anywhere the user wants, but still retain the ability for it to reside in S: … which means all those who it in S: can have it there … but other users who have different needs can have the file somewhere else. A major requirement of user-friendly software is its configurability over and above a sensible default … forcing users to have their configs in S: has the "I-know-better-than-you-what-you-really-want" syndrome which afflicts so many programmers these days. Mike (Whapping from the UK)