From:	Tom St Denis <stdenis AT compmore DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP in ms-dos prompt (under win98)
Date:	Mon, 22 Jan 2001 19:34:11 GMT
Organization:	Deja.com
Lines:	45
Message-ID:	<94i1vi$3ai$1@nnrp1.deja.com>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1010122174148 DOT 28597B-100000 AT is>
NNTP-Posting-Host:	24.156.37.224
X-Article-Creation-Date:	Mon Jan 22 19:34:11 2001 GMT
X-Http-User-Agent:	Mozilla/5.0 (Windows 98; U) Opera 5.01 [en]
X-Http-Proxy:	1.1 x71.deja.com:80 (Squid/1.1.22) for client 24.156.37.224
X-MyDeja-Info:	XMYDJUIDtomstdenis
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <Pine DOT SUN DOT 3 DOT 91 DOT 1010122174148 DOT 28597B-100000 AT is>,
  djgpp AT delorie DOT com wrote:
>
> On Mon, 22 Jan 2001, Tom St Denis wrote:
>
> > My previous machine was a AMD K6-II.  This is an Athlon.
> >
> > > If not, what is different with this machine?  If this is the same
> > > machine where previous builds succeeded, what changed since the last
> > > successful build?
> >
> > Um I have four times the memory now, a faster cpu, and a larger hard disk.
>
> If this is a new machine, I'd suspect a hardware problem as the most
> probable cause.  Inconsistent crashes usually mean that some memory chip
> is faulty or does not keep up with the CPU and the bus.  GCC catches such
> problems quite often, because it's a memory hog, moves large buffers to
> and fro, and runs the CPU at full throttle for prolonged periods of time.
>
> If the CPU is overclocked, turn that off and see if that helps.  If the
> CPU cache(s) are set to some aggressive mode, such as write-back, change
> that to less aggressive mode and see if that helps.  If the problem
> persists even with vanilla settings of these parameters, get a
> replacement for your hardware.
>
> > Well I get those bugs during every compile.  To be honest I think it's my
> > computer, cuz I get "internal compiler errors" in MSVC too.
>
> This is yet another sign that the hardware is the reason.

Geez, you actually helped.  Thanks!

I turned off my write back and my "USWC" video mode (says it may cause
problems), I turned on my L2 ECC checked, forced the board to think it was
133mhz 8ns ram and ...

It build all of allegro 3.12 without a single crash.

Thanks alot :-)

Tom


Sent via Deja.com
http://www.deja.com/

- Raw text -