On 15 Dec 96 03:30pm, TORE HANSEN wrote to SAM MCDANIEL:
 TH> Hello SAM, on 11-29-96 you wrote to ALL  about MEMORY PROBLEMS:
SM> I have setup a new Novell 4.10 2  25 user system.
SM> hot fix off
 TH> Not such a good idea.
SM> problem
SM> At 64 meg ram the system functions very nicely for weeks.
SM> When I install the other 64mb of ram, the systems comes down hard
SM> with paging out of bounds errors or similar paging errors, or may
SM> not  even
SM> finish the novell load. This is not consistant.
SM> May do it on bootup and volume mount or may run for a
SM> few hours or 20 hours before it happens.
SM> When I installed the additional 64meg of memory and reboot the
SM> system the mem check recognizes and verifys the full 128
SM> meg. Highmem.sys verify's the 128 meg.
SM> By adding the line "register memory start address/offset address"
SM> command to
SM> the autoexec.ncf and rebooting Novell
SM> still only reports 64meg.
SM> Ive changed chip sets and made sure of matched sets of
SM> simms.
SM> What am I missing here?
 TH> Debug your machine while it is running in DOS first. If DOS
 TH> can't see the full 128 Meg, it won't work in NetWare either. I
 TH> use Symatec's Norton Utilities' NDIAGS program to run extensive
 TH> memory tests after a RAM upgrade. I have never had a problem
 TH> with RAM in the server, after it had passed the Norton tests.
Not totally correct, Tore.  There is an application note out by
Microsoft (saw it last year) that mentions the fact that DOS has a
minor glitch where it won't report available memory above 64MB *UNTIL*
you run something that actually attempts to access that memory above
64MB.
I'm afraid that if the gentleman tries to test his memory in DOS first
he may receive false readings if his tests don't attempt to access that
memory above 64MB (not all testing software is designed to look for that
much memory).
George
... Do not take life too seriously; you will never get out if it alive.
--- Via Silver Xpress V4.3P BT003
---------------