From owner-ml  Wed Nov 12 19:50:31 1997
Received: (from majordom@localhost)
	by qoole.com (8.8.5/8.8.5) id TAA10744
	for ml-outgoing; Wed, 12 Nov 1997 19:50:31 -0800 (PST)
X-Authentication-Warning: qoole.com: majordom set sender to owner-qoole@qoole.com using -f
Received: from u3.farm.idt.net (root@u3.farm.idt.net [169.132.8.12])
	by qoole.com (8.8.5/8.8.5) with ESMTP id TAA10740
	for <ml@qoole.com>; Wed, 12 Nov 1997 19:50:20 -0800 (PST)
Received: from anubis (user-38lcfif.dialup.mindspring.com [209.86.62.79])
	by u3.farm.idt.net (8.8.8/8.8.5) with ESMTP id WAA05736
	for <ml@qoole.com>; Wed, 12 Nov 1997 22:45:33 -0500 (EST)
Message-ID: <346A7665.B10A8EDC@idt.net>
Date: Wed, 12 Nov 1997 22:39:17 -0500
From: Marc Anthony DeLegge <marcodel@idt.net>
X-Mailer: Mozilla 4.01 [en] (Win95; I)
MIME-Version: 1.0
To: ml@qoole.com
Subject: Re: PAGE FAULTS
X-Priority: 3 (Normal)
References: <Pine.LNX.3.96.971112153131.23603A-100000@fantasia.stormhaven.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-qoole@qoole.com
Precedence: bulk
Reply-To: ml@qoole.com
Status: RO

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.

