Xref: utzoo comp.os.msdos.desqview:38 comp.os.msdos.misc:1939
Newsgroups: comp.os.msdos.desqview,comp.os.msdos.misc
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!everest!iplmail!sag
From: sag@iplmail.orl.mmc.com (Steve Gabrilowitz)
Subject: Re: Another QEMM problem.
Message-ID: <1991May6.211206.18960@iplmail.orl.mmc.com>
Sender: sag@iplmail (Steve Gabrilowitz)
Organization: Martin Marietta
References:  <1991May3.205700.8459@cs.dal.ca>
Date: Mon, 6 May 1991 21:12:06 GMT

In article <1991May3.205700.8459@cs.dal.ca>, lane@cs.dal.ca (John Wright/Dr. Pat Lane) writes:
|> 
|> Hmm.  I guess I'll jump in here with another slightly off-topic question.
|> 
|> I've noticed that when running with QEMM (any version) or 386MAX under
|> DOS 4.01, that I frequently get system crashes that go something like:
|> 	"Protection Violation at CP:031B"      or
|> 	"Protected Mode Operation at CP:031B"
|> etc.  Apparently this is caused by the CPU running into an instruction
|> which is only valid under protected mode.  The address always points
|> to FASTOPEN (the IP part is always the same), regarless of whether it was
|> loaded in high memory or not.
|> 
|> I'm led to suspect that FASTOPEN has a serious bug that causes it to trash
|> part of itself after so many file opens and on the next file open, you
|> execute the trash and, of course, crash.  Needless to say, Microsoft refuses
|> to admit to any such bug.
|> 

FASTOPEN is very dangerous, particularly when you are multi-tasking!

-- 




                            Steve Gabrilowitz
                            Martin Marietta, Orlando Fl.
                            sag@iplmail.orl.mmc.com
                            Fidonet 1:363/1701