CompuServe Messages

John, There _is_ a reason for not putting config/setup files in the program's own directory — it requires the user to assign it. This is above the heads of most point and clickers. They have no idea how to edit a startup-sequence nor do they really want to do so. I also don't want installation programs messing around with my startup-sequence. Until there is a definite guideline from on high, you'll continue to see s: being improperly used (altho it's generally accepted now) and you'll see some programs putting their config files in devs: (after all, that's where CBM puts system-configuration), you'll see some people use env: and/or envarc: — in otherwords, it's a mess.