CompuServe Messages

John I think I'd agree with that … but more importantly, the software should give the user the option of where he puts all that stuff since different people would clearly prefer to have it in different places. For instance, let's say you have a word-processor with a configuration file called config.wp, and your word-processor is in a volume called WP:, then … if exists "config.wp" then load "config.wp" else if exists "WP:" then if exists "WP:config.wp" then load "WP:config.wp" else if exists "S:config.wp" then load "S:config.wp" else if exists "CONFIG:config.wp" then load "CONFIG:config.wp" else print "cannot find config.wp, using defaults" That allows everyone to be happy … and is very simple to do, and doesn't have to confuse anyone. Although the ENVARC: idea is not a bad one, I would still hope that the option to save such files in the current directory or master volume would be retained. Mike (Whapping from the UK)