From: "Michael Callery" 
Subject: Re: Memory > 16MB not detected
Date: 1998/05/14
Message-ID: #1/1
References: 
Organization: Netcom
Newsgroups: fido.novell


Obviously the hard drive would not cause any problem, so you need to dive
into the memory area.  Also, I'm not entirely sure by your message whether
the server acknowledges the memory and then immediate aborts or whether its
delayed.

In my case, I'm running an ALR Power Pro, EISA based.  I'm running 49 megs
of memory and do not have to use the register memory command - my computer
sees it.

Aside from Novell, you need to check the owners manual to see how it
recommends seeing the memory with a non-DOS (Novell) operating system.  Some
computers will recognize it without additional commands because the
computers are specifically geared towards being a file server. My Compaq
Proliant 2500 sees all 300 megs without any additional commands.


First, an obvious question.  Are you absolutely sure that the memory is the
right spec for the machine?  parity/non-parity/EDO whatever because it
sounds like a memory error.  What  appears to be happening, from what I'm
seeing, is that the server is not using the memory until you issue the
command to see it, which is the correct command by the way, and as soon as
you do, it GPF's with a parity error.  I would immediately suspect that you
have non-parity memory installed when you should have parity or EDO.

Other than this, I don't see any error in what you are doing, but for Novell
to come back and tell you parity error, it means the memory is crapping out
as it is read.