Date: Thu, 19 Aug 1999 11:51:45 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Rolf Campbell <cp1v45 AT nortelnetworks DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: New guy having installation difficulties
In-Reply-To: <37BAF0EF.18E96EDA@americasm01.nt.com>
Message-ID: <Pine.SUN.3.91.990819114922.9461H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 18 Aug 1999, Rolf Campbell wrote:

>     It depends on how you install it.  On my installation, there is only 1
> autoexec.bat file, and it is always used.  The problems occur when you use
> a 'restart in dos mode' that needs to load some weird things into memory
> (special drivers/TSR's/RAM-drives).  Windows needs to do a real-reboot to
> load these drivers correctly (I don't know why...).  So they make a new
> autoexec file with that new settings in it (along with a config.sys) and
> they replace the real ones just before the reboot, then they put the
> originals back if you type "win" from the DOS session, and then it restarts
> the machine.

Thanks for the explanation.  However, I don't think this is the real 
reason.  What you describe exists in Windows 95 as well, and has never 
before been brought up here as a reason for problems.  Windows renames 
the special AUTOEXEC.BAT file for the DOS-Mode session before it reboots, 
so when you are back into Windows, the usual AUTOEXEC.BAT is again called 
by that name.