Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ames!vsi1!teda!mikel
From: mikel@teda.UUCP (Mikel Lechner)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: Exception #13
Keywords: What's that?
Message-ID: <23083@teda.UUCP>
Date: 28 Mar 91 07:28:49 GMT
References: <3026@beguine.UUCP> <838@saxony.pa.reuter.COM>
Distribution: na
Lines: 28

dgil@pa.reuter.COM (Dave Gillett) writes:

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

>>[. . .] Can someone kindly tell me what exp #13 is?

Quoted from Intel's 80386 "System Software Writer's Guide":

The 80386 raises this fault when a task attempts an operation that is
inconsistent with a segment descriptor.  Many such conditions exist,
including writing to a read-only segment, loading a null selector, and
accessing a more privileged segment. [. . .]  In practice, however,
a general protection fault is a protected mode task indicates a serious
program bug and the task should normally be terminated. [. . .]

>     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?

qemm is not the only software that runs protected mode.  ergo's os28/386
dos extender will also print and exception #13 message when a program
running in protected mode gets an exception #13.

-- 
Mikel Lechner			UUCP:  teda!mikel
Teradyne EDA, Inc.
5155 Old Ironsides Drive	| If you explain so clearly that nobody
Santa Clara, Ca 95054		| can misunderstand, somebody will.