Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!saxony!dgil
From: dgil@pa.reuter.COM (Dave Gillett)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: Exception #13
Keywords: What's that?
Message-ID: <838@saxony.pa.reuter.COM>
Date: 25 Mar 91 22:35:37 GMT
References: <3026@beguine.UUCP>
Distribution: na
Organization: Reuter:file Inc  (A Reuter Company) Palo Alto, CA
Lines: 18

In <3026@beguine.UUCP> Brian.Chan@samba.acs.unc.edu (Brian Chan) writes:

>I have a Gateway 386 w/16Megs of RAM and I will  get an error exception
>#13 once in awhile running apps. If I choose `c` to continue, 9/10 times the
>machine will require hardare reset. Can someone kindly tell me what exp
>#13 is?


     The only "Exception #13" message I've ever seen is from QEMM, and
clearly identifies itself as such.  Are we to infer that you are running
QEMM on the machine?

     Exception #13 is (very briefly) described in the QEMM manual; it means
that QEMM has detected the effect of an invalid address operation, usually due
to a corrupted or uninitialized pointer.  It's roughly equivalent to Windows'
"This app has violated system integrity" message; odds that the system can 
continue to run are extremely poor, and re-boot is the safest choice.
                                                Dave