Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!uunet!convex!swarren
From: swarren@convex.com (Steve Warren)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Help with Frances
Message-ID: <105179@convex.convex.com>
Date: 21 Aug 90 14:36:35 GMT
References: <19626@well.sf.ca.us> <1990Aug21.083830.26826@agate.berkeley.edu>
Sender: usenet@convex.com
Distribution: comp.sys.amiga.tech comp.sys.amiga.hardware
Organization: Convex Computer Corporation; Richardson, TX
Lines: 14

In article <1990Aug21.083830.26826@agate.berkeley.edu> vincelee@tornado.Berkeley.EDU (Vincent H. Lee) writes:
>same. What you need is a small C program to write a different value to all the
>RAM in a range first, and then go back to check it.  That way, all the ram
>would be guaranteed to be not only good, but distinct as well.

Write the address of the data to the data.  Then when you read bad data
out you know which address it came from.  Of course any code will work,
but the address code is easiest to interpret.

--
            _.
--Steve   ._||__      DISCLAIMER: All opinions are my own.
  Warren   v\ *|     ----------------------------------------------
             V       {uunet,sun}!convex!swarren; swarren@convex.COM