From: "John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: how to get rid of autoexec.bat
Date: Wed, 19 Feb 1997 20:31:45 -0800
Organization: Two pounds of chaos and a pinch of salt
Lines: 37
Message-ID: <330BD3B1.198B@cs.com>
References: <5efatv$juq AT chaos DOT kulnet DOT kuleuven DOT ac DOT be> <330C149D DOT 4B6A AT blackmagic DOT tait DOT co DOT nz>
Reply-To: fighteer AT cs DOT com
NNTP-Posting-Host: ppp220.cs.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
CC: koen <koen DOT janssens1 AT student DOT kuleuven DOT ac DOT be>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Bill Currie wrote:
> 
> koen wrote:
> >
> > I'm using the menu command in config.sys, so I'm able to start the computer in
> > two different modes(much memory or more speed). But there's only one
> > autoexec.bat so after the config.sys, the computer uses always the same Autoexec file
> > (whatever choice I made in the menu).
> 
> in autoexec.bat:
> 
> @call %config%

There's an easier way to do it, and it lets you keep all the necessary
commands in one batch file.  Simply put the following command near the
beginning of your AUTOEXEC.BAT:

goto %CONFIG%

Then simply create a label for each possible value of the CONFIG
variable.  In practice, it can get much more complex than that - you
might be interested in seeing my config.sys and autoexec.bat, in which I
believe I have the supreme multi-config setup.  I even have a section
that loads up a different 'win.ini' file depending on which
configuration I chose.  :)

-- 
John M. Aldrich <fighteer AT cs DOT com>                      

* Anything that happens, happens.
* Anything that, in happening, causes something else to happen,
  causes something else to happen.
* Anything that, in happening, causes itself to happen again, happens
  again.
* It doesn't necessarily do it in chronological order, though.
 
                                       --- Douglas Adams