12 May
2006
12 May
'06
1:05 p.m.
On Friday 12 May 2006 03:27 am, Jochen Kunz wrote:
On Thu, 11 May 2006 04:03:00 +0200
Gerhard Lenerz <mail at g-lenerz.de> wrote:
I ran across that same problem with some of my stuff, and it turned out that
in at least one case the issue wasn't so much the size of the ram as it was
the type -- if the board is expecting EDO and you put SDRAM in there (or
maybe that was the other way around?) you'll see just that sort of a
response...
Might be worth a shot, anyhow.
--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, a critter that can
be killed but can't be tamed. --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James
M Dakin
This the GIO32 bus. Some cards that could be
installed on top of the
graphics board were additional network/SCSI controllers or video
options.
I have a FDDI board in my Indy to get nice and fast 100 MBit/s
network...
As we are talking of Indys: What is the max. SIMM size for the Indy?
I had 8 x 32 MB in mine. I got some 64 MB SIMMs so I threw them into the
Indy to get even more RAM. But the Indy saw only 4 x 16 MB instead of 4
x 64 MB. The SIMMs worked well in a Indigo2 R10k but showed the same
problem in a Indigo2 R4k.