On Thu, Feb 03, 2000 at 14:09, aphro wrote:
> another thing to check is the cache on the board/chip, disable one
> at a time thru the bios and see if it does the same, its gonna run
> like a 386 but it'll be a decent test to see if the cache sometimes
> gives bad hits.
>
> worth a shot anyways ..
another thing to check is the cache on the board/chip, disable one at a
time thru the bios and see if it does the same, its gonna run like a 386
but it'll be a decent test to see if the cache sometimes gives bad hits.
worth a shot anyways ...
nate
On Thu, 3 Feb 2000, Remco van 't Veer wrote:
rw
On Thu, Feb 03, 2000 at 09:30, aphro wrote:
> quite possibly a quake-svga problem. it also could be a mainboard
> problem..is the ram that you scanned that was 'bad' in any particular
> socket? i've had ram sockets go bad on me before when the ram was ok.
I cycled my "good" SDRAM's through all s
On Thu, 3 Feb 2000, Remco van 't Veer wrote:
rwvtve >Could it be a quake-svga problem or am I still experiencing memory
rwvtve >problems? Could my video memory be faulty? Some BIOS setting?
quite possibly a quake-svga problem. it also could be a mainboard
problem..is the ram that you scanned t
Hi,
I've been having memory trouble.. A month ago I go new computer (a
PIII450 with 3*128Mb). One SDRAM modules was broken, the machine
didn't pass the kernel compile test. So I swapped till I found the
broken one and traded it for a new one. This configuratie passes a
1000 kernel compile test
5 matches
Mail list logo