View Single Post
  #9  
Old August 10th 04, 01:17 PM
Paul Murphy
external usenet poster
 
Posts: n/a
Default

I wouldn't say its sounds like that at all - the original poster has a valid
point, namely that it's not possible to run such a program on a machine
unless you can get it to POST and then boot to the drive that program is on.
He also asked direct questions of how he was supposed to accomplish your
idea - your link doesn't answer that question. If your suggestion was
thinking along the lines of putting the memory modules in another machine
and run the program to test them from there well thats a different matter.
My hunch though is that this is a compatibility matter and nothing other
than replacement modules (or a slim chance of a BIOS upgrade for the
motherboard - *whilst fully compatible modules eg the old ones, are
installed*), will make a difference.

Paul

"Bob Day" wrote in message
news:mJ1Sc.4271$K82.495@trndny01...
It sounds like you'd rather fight than solve your problem.
Goodbye.

-- Bob Day
http://bobday.vze.com


"Andy in NJ" SHORECOGS at COMCAST DOT NET wrote in message
...
Bob Day wrote:
How can I test the apparently bad module if I can't get the computer
to start with that module in the slot?!


By putting Memtest86+ on a bootable CDROM or floppy as explained
at http://www.memtest.org


How is the CDROM or Floppy going to run if the system doesn't BOOT?

Your post didn't specify chip density, single or double sided, tRAS,
tRP, tRCD, or CL, all of which can make a difference.


It supports up to (2) DDR 1GB 2100 memory modules. How many variations

are
there?!