From: chuck AT no DOT junk DOT mail DOT com (Chuck Adams)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: GUI debuggers/profilers ?
Date: Wed, 25 Sep 96 14:52:22 GMT
Organization: Lockheed Martin EIS
Lines: 16
Message-ID: <52bgu7$fd9@butch.lmsc.lockheed.com>
References: <Pine DOT SOL DOT 3 DOT 95 DOT 960919113609 DOT 3983B-100000 AT columbia> <324153A3 DOT 674D AT Mathematik DOT tu-chemnitz DOT de> <51scfm$9d AT butch DOT lmsc DOT lockheed DOT com> <3242A663 DOT 273 AT Mathematik DOT tu-chemnitz DOT de> <526tbc$3vn AT butch DOT lmsc DOT lockheed DOT com> <3247E7F0 DOT EA AT Mathematik DOT tu-chemnitz DOT de>
NNTP-Posting-Host: 198.7.11.31
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <3247E7F0 DOT EA AT Mathematik DOT tu-chemnitz DOT de>, Robert Hoehne <Robert DOT Hoehne AT Mathematik DOT tu-chemnitz DOT de> wrote:
>
>If you have a mouse driver loaded in your autoexec.bat or config.sys
>(are they used in NT??), then remove the loading of it and try again.
>If it now works, please let me know.
>
>Robert

NT does not use autoexec.bat or config.sys.  An NT DOS box uses autoexec.nt 
and config.nt if they exist -- on my system, they don't.  For some odd reason, 
all my DOS programs that use the mouse still work.  Typical strangeness w/ NT.

Oh well.

--
	Madness takes its toll.  Please have exact change