From owner-ml  Wed Nov 12 21:22:16 1997
Received: (from majordom@localhost)
	by qoole.com (8.8.5/8.8.5) id VAA11016
	for ml-outgoing; Wed, 12 Nov 1997 21:22:16 -0800 (PST)
X-Authentication-Warning: qoole.com: majordom set sender to owner-qoole@qoole.com using -f
Received: from episun1.harvard.edu (episun1.harvard.edu [128.103.73.118])
	by qoole.com (8.8.5/8.8.5) with SMTP id VAA11012
	for <ml@qoole.com>; Wed, 12 Nov 1997 21:22:11 -0800 (PST)
Received: by episun1.harvard.edu (4.1/1.34)
	id AA21065; Thu, 13 Nov 97 00:16:54 EST
Date: Thu, 13 Nov 1997 00:16:53 -0500 (EST)
From: Gordon White <gwhite@episun1.harvard.edu>
To: ml@qoole.com
Subject: Re: PAGE FAULTS
In-Reply-To: <346A7665.B10A8EDC@idt.net>
Message-Id: <Pine.SUN.3.91.971113001506.21052A-100000@episun1>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-qoole@qoole.com
Precedence: bulk
Reply-To: ml@qoole.com
Status: RO

I am referring to quake errors.  You are playing your level, everything 
is fine, then BAM, blasted out to dos prompt with a bunch of machine 
language in a dos box.
Seems to happen when a lot of things are happening at once within the level.

G

***************************
Gordon Wh

On Wed, 12 Nov 1997, Marc Anthony DeLegge wrote:

> Chris A. Epler wrote:
> > With proper coding everything will be checked to be within bounds and
> > should
> > not experience these errors.  The file itself (the BSP or MAP) only
> > has
> > coordinates etc, the program is reading these in and parsing them.
> > When
> > it's reading them in it should have proper checking to prevent these
> > problems.
> > 
> > ------------------------------------------------------------------------
> > Chris A. Epler - KC6ZOL - ESInet System Admin - (804) 974-7308
> > Do not send Unsolicited Commercial E-Mail (UCE), legal action may be
> > taken.
> > PGP KeyID: 1024/6BBCAFE5 1997/04/14 Chris A. Epler <cepler@esinet.net>
> 
> Well.. yeah.. obviously.. however I was trying help this poor pleading
> man, not stray off topic too much and provide a brief glimpse at what
> these errors are generated from.. internal references to data or code
> that is wrongly addressed or placed... in an ideal world, an program
> would include all sorts of error trapping to catch these errors.. and
> good programmers work hard to include such error trapping... however..
> people are not omniscient and thus make mistakes on a regular basis... 
> 
> 	So... to reiterate to some degree.. these Quake errors (Im still
> unclear as to whether he was referencing Quake errors or Qoole errors..
> or even Windows errors).. are caused by internal program code looking
> for something that is not there.. and Windows calls it on it.. saying
> 'NO NO NO.. bad program, time to get a spanking!!'.. and crashes....
> 
> 	If someone would like a more technical explanation, one that does not
> cover things at a high level and thus be prone to exclusion of picky
> details, and DOES NOT cover or even come close to Qoole related issues..
> then please email me directly...
> 
> Thank you and may your programs never hog resources,
> 
> 
> 
> -- 
> ------------------------------------
> . o 0 [ Marc Anthony DeLegge ] 0 o .
> . o 0 [   marc@samadhi.com   ] 0 o .
> 
> * According to my calculations, the problem doesn't exist.
> 

