[Wolves] Odd memory module problem

[Kevanf1]

On Thu, 17 Mar 2005 23:41:46 +0000, Andy Wootton
<andy.wootton at wyrley.demon.co.uk> wrote:
> Mo Awkati wrote:
> 
> >With some versions of Windows you need to tweak a
> >setting, I can't remember which but if you go to
> >Crucial
> >website and check the motherboard it will tell you.
> >
> >Mo
> >
> >
> Agreed. There is a way to tell the box to ignore memory above a certain
> threshold. It is probably intended to allow developers to test if code
> will run on the lower spec machines they give their customers.
> 
> I've seen it used to 'set expectations' when a partial system is
> delivered earlier. You don't want the users getting used to decent
> performance on their shiny new PC and then being disappointed when you
> give them the whole VB app. When you install the second phase of the
> project, you whip the cover from over the memory you kept hidden and
> they think the coder is a genius. Sad but true.
> 
> Woo
> 
> _______________________________________________
> Wolves LUG mailing list
> Homepage: http://www.wolveslug.org.uk/
> Mailing list: Wolves at mailman.lug.org.uk
> Mailing list home: http://mailman.lug.org.uk/mailman/listinfo/wolves
> 
Hi guys.  Sorry I should have got back yesterday but I'm limited in PC
time at the moment  for health reasons, sadly there is no funny jokey
punchline to that.

Ok, this is what I have done so far for this mate of mine.  Bear in
mind that all this has to be done by him as he is a mate on the 'net'.
 I've got him to try the old 256mb modules individually and in each
separate slot.  On there own they worked fine.  When he tried them
both together Window$ would not start at all.  It was throwing up all
sorts of odd errors.  I've seen this before when a faulty memory
module is being used in conjunction with a good one; yet they both
work alone.  He then got onto his supplier who swapped the two 256mb
modules for one 512mb.  I believe his PC started but only registered
256mb of memory.  I have to double check on this.  Now at this stage
my first course of action would be to try the memory in a different,
known good PC.  The trouble is it is PC133 memory not newer stuff. 
Being unable to do this my thoughts are that it might be a mobo
problem.  But if this were the case then surely when he had the two
separate modules one of them would have failed to start the PC when it
was in the duff slot?  I know about the memory level problem with
Window$.  It was in the 9X series.  You could have up to 512mb but
after that Window$ either did not see it or it would fall over.  But,
you were fine with up to 512mb.  NT does not have this restriction. 
The other suggestion of developers throttling the amount of memory
actually available to Window$ is the next stage I shall investigate. 
I do recall seeing a way of doing that but I need to go delving to
find it again :-)

Cheers guys.  It might be better if he were able to use Linux because
then we would know if it was a hardware or software problem.  Unless
of course there is a BIOS restriction.  Sorry, that thought has just
popped into my head....

-- 
Take care.
Kevan Farmer

34 Hill Street
Cheslyn Hay
Staffordshire
WS6 7HR