My intuitive take is that only if the PM drivers don't load for some reason
do any RM drivers that have been loaded stay in action. But, then, I do
recall people occasionally having issues when trying to start Windows from
"true DOS" mode using the WIN command in Win95/98, probably from RM/PM
conflicts, so it's not likely always a clean process. In short (my brain is
befuddled this evening), my understanding is that when Windows 95/98 loads
normally, it bypasses loading most, if not all, RM drivers, unless specified
by autoexec.bat and/or config.sys. And any subsequent loading of PM drivers
trumps any RM drivers that have been previously loaded -- with luck.

--
Gary S. Terhune
MS MVP -- Shell/User
http://grystmill.com/articles/cleanboot.htm
http://grystmill.com/articles/security.htm

"Franc Zabkar" wrote in message
news
On Fri, 26 Jan 2007 17:36:46 -0800, "Gary S. Terhune"
put finger to keyboard and composed:

AFAIK, yes, that's the case. Sorry, I didn't understand before that your
purpose was to use the CTMOUSE driver in a DOS window, as opposed to in
real-mode DOS. AFAIK, it's generally true that you can't load real-mode
drivers under Windows. I'm not *certain* that it's *always* the case, but
it's generally the case.

I was hoping that loading a DOS driver in autoexec.bat would force the
mouse to run in some kind of "MSDOS compatibility mode", as is the
case with some storage devices when their protected mode drivers
aren't configured correctly. But that's just a WAG ...

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.