home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #26 / NN_1992_26.iso / spool / comp / os / msdos / apps / 5513 < prev    next >
Encoding:
Internet Message Format  |  1992-11-10  |  982 b 
  1. From: doug@hparc0.aus.hp.com (Doug Parsons)
  2. Date: Tue, 10 Nov 1992 12:11:49 GMT
  3. Subject: Re: Re: util for pointing to bad RAM ?
  4. Message-ID: <1992Nov10.121149.21176@hparc0.aus.hp.com>
  5. Organization: HP Australasian Response Centre (Melbourne)
  6. Path: sparky!uunet!ornl!utkcs2!darwin.sura.net!zaphod.mps.ohio-state.edu!sdd.hp.com!scd.hp.com!hpscdm!hplextra!hpcc05!hparc0.aus.hp.com!doug
  7. Newsgroups: comp.os.msdos.apps
  8. References: <1992Nov8.055454.1366@qdpii.comp.qdpi.oz.au>
  9. X-Newsreader: Tin 1.1 PL4
  10. Lines: 12
  11.  
  12. I uploaded testext.zip to cica last week for someone who requested a mem
  13. tester.  It too shows a graphic representation of your memory; however, I
  14. don't know how that would map to a pc with mixed memory chips in different
  15. locations.
  16.  
  17. I would think, however, that someone that was going to work at the chip
  18. level would already know enough about it!
  19.  
  20. Swapping available memory would be the obvious choice; otherwise, take in
  21. in to get repaired would be a good idea.
  22.  
  23. douginoz.
  24.