From: ovek AT arcticnet DOT no (Ove Kaaven)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Win95 weirdness (was Re: Configuring perl5004 problem)
Date: Sun, 02 Nov 1997 09:33:31 GMT
Organization: Vplan Programvare AS
Lines: 18
Message-ID: <345c44a4.14469661@news.arcticnet.no>
References: <630fct$3bc_002 AT mrw DOT panix DOT com> <63bv63$397 AT freenet-news DOT carleton DOT ca>
NNTP-Posting-Host: alwayscold.darkness.arcticnet.no
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire) wrote:

>And, one day, all of a sudden nytime I used "more" in a DOS box it caused
>a GPF on exit, after it was done "more"ing something and was about to
>return to the prompt. I never changed anything about more, never
>bit-twiddled the EXE (or is it a .COM?) or anything. Windows just suddenly
>decided MORE was not allowed. Sheesh.

Though Windows 95 may not be the most stable of OS-es, it's still
possible that such behaviour may be undetected hardware errors. Lately
cutting-edge OSes (recent versions of the Linux kernel) has suffered
from previously undetected hardware errors, that is first noticed from
the stress of compiling the kernel (gcc reports internal error). You
may want to read the SIG11 FAQ at http://www.bitwizard.nl/sig11/ for
further information (It happened to me too... though I never suspected
hardware error, running a memory test 4 times in a row showed faulting
system RAM). Also run a disk test, just in case.