X-Authentication-Warning:	acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date:	Tue, 13 Apr 1999 11:57:35 +0200 (MET DST)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender:	broeker AT acp3bf
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject:	Re: LBInstDJ
In-Reply-To:	<Pine.SUN.3.91.990413095956.29746H-100000@is>
Message-ID:	<Pine.LNX.3.93.990413115010.3378B-100000@acp3bf>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 13 Apr 1999, Eli Zaretskii wrote:

> On Mon, 12 Apr 1999, Hans-Bernhard Broeker wrote:

> > It's probably wisest to just give up immediately when multiple
> > configurations are detected. 
> 
> I'm afraid you will give up on too many systems this way.

May be. But on the other hand, once multiple conf's are active,
autoexec.bat gains a whole new amount of potential complexity.  The
installer would have to detect exactly what the given autoexec.bat does do
for every possible setting of %config%. Not even to mention multi-level
menuconfigs, with separate variables to be set, as well.

Heck, even the win98 update didn't manage to cope with my
config.sys/autoexec.bat correctly, even though M$ said they needed
something like an additional 6 months just to fix bugs in that part of the
upgrade installation... 

As might have been guessable from these messages of mine, my conclusion is
that a reliable install.exe that does change autoexec.bat itself is almost
certainly impossible to do. It's like opening a can of worms, and already
now, the observed set of potential problems seems to imply that these
worms, once freed, are impossible to keep in control. 

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -