Hi Peter,

PF>While we're all venting...

PF>I'd like to see a "#include" command for config.sys,  which
PF>supports auto-appending environment variables.

PF>For example,  in the c:\config.sys, you'd have

PF>        #include c:\ibmworks\iwconfig.sys

PF>And iwconfig.sys might look like:

PF>        SET PATH=c:\ibmworks;
PF>        SET LIBPATH=c:\ibmworks\dll

PF>        (where these get appended to the PATH, LIBPATH, etc, settings)

What a good idea :-)
It would be _wonderful_ for Visualage C++ which seems to put everything
(including the kitchen sink!) into config.sys.
I'm all in favour of appending, rather than pre-pending (which many
install programmes do), having been bitten by the Watcom C++ V10.0b
install which prepends itself and back levels some components :-(.

PF>I don't think I need to explain to the power users in this
PF>conference of the benefits (and I won't dwell on obvious
PF>extensions, like SET PATH=%PATH%;asdf;)

I thought we already had "SET PATH=%PATH%;extra_path" on a per-session
basis? (It works on my vanilla OS/2 3.0 here).
Or do you mean allowing it to be done to the master environment, not
just a session environment?

PF>I came up with this idea during a brain storm with David
PF>Moskowitz at last yeats ColoradOS/2;  he really liked it,
PF>and I mentioned it to Paul Giangara (sp) who was soliciting
PF>new ideas,  but it probably got forgotten about.

PF>If I go again this year, I'll try to resurrect the idea.

Have a try.

PF>It's the kind of thing,  if I had the source,  I could add
PF>& completely test in less than an hour.

But it'll take IBM weeks of management time to agree to do it :-(

George

 * SLMR 2.1a * What do you mean? You actually read this tagline!!!

--- Maximus/2 3.01