-=> Quoting William Geiger to Phil Crown <=- 

 WG> QUOTE- I was thinking along the same lines but rather than have multiple
 WG> config.sys files have the Rexx script modify a single config.sys file
 WG> by remming out the unwanted sections.(Having a backup copy of cource).
 WG> It is not as good as having a config.sys menu but it will work.

I like this idea too.  I'm trying to setup a "generic"
config.sys, then just
have a Rexx program modify needed settings such as PATH, LIBPATH, adding
drivers, etc... instead of trying to maintain 3 or 4 seperate config.sys's.

 WG> Another thought is to write a program that would be called from the
 WG> config.sys durring bootup that would give me a menu to chose from and
 WG> then depending on the selections switch over to a second file that
 WG> would have the the drivers I wanted to load. Not quite sure where to
 WG> start with that one though.:)

This is a better idea, but would require thorough knowledge of how
config.sys is read and loaded.

 WG> Do you know where I can get some good docs on how OS/2 processes the
 WG> config.sys file and loads drivers?

No... but I'll keep a look out.  Config.sys seems to be fairly flexible, for
example, I've sorted my with a program called CSORT*.*, before that I sorted
it alphabetically with QEdit's block sort function, keeping only two lines
at the top.  Now I'm moving all the standard stuff to the top, so I can more
easily modify it.

If you sort your config.sys, I _think_ these two lines must be first in
config.sys...

IFS=D:\OS2\HPFS.IFS /CACHE:384 /CRECL:8 /aUtOcHeCk:CDEFG
IFS=D:\OS2\BOOT\CDFS.IFS /C:8 /Q

If you want, we can move to OS2 Echo, maybe more appropriate.  However if
we're using REXX, here may be okay.

Phil
Fido:  1:124/8014.1 | Internet:  phil.crown{at}bluecafe.com


--- Blue Wave/Max v2.30