KT> I know i certainly would, But alot of commercial-
 KT> programmers don't agree.. :(

 KT> What would be preferable, and wouldn't even need a reboot, Would be for 
 KT> each program to make it's own INI, and place them in


While we're all venting...

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

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

        #include c:\ibmworks\iwconfig.sys

And iwconfig.sys might look like:

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

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

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

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

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

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

ps: [back to original thread] -- I fall into the binary *.ini camp --with
David Noon's reasoning (if someone is smart enough to be editing the *.ini,
they won't let the fact that it isn't a text file stop them).


--- Maximus/2 3.00