Xref: utzoo comp.sys.mac.misc:3295 comp.sys.mac.programmer:17477
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!samsung!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!ellis.uchicago.edu!dwal
From: dwal@ellis.uchicago.edu (David Walton)
Newsgroups: comp.sys.mac.misc,comp.sys.mac.programmer
Subject: Re: MEMORY FAULTS - any way to check ram for intermittent faults??
Message-ID: <1990Sep14.195601.1500@midway.uchicago.edu>
Date: 14 Sep 90 19:56:01 GMT
References: <1990Sep12.185459.15694@ux1.cso.uiuc.edu> <1990Sep13.154744.2277@midway.uchicago.edu> <10242@goofy.Apple.COM>
Sender: news@midway.uchicago.edu (News Administrator)
Distribution: comp
Organization: U. Chicago Computing Organizations, Academic and Public Comp.
Lines: 22

In article <10242@goofy.Apple.COM> Greg@AppleLink.apple.com (Greg Marriott) writes:

>dwal@ellis.uchicago.edu (David Walton) writes:
>> 
>> Um...I think that's a typo.  You mean sm _0_ 0101, don't you?  You
>> don't want to put this at memory location 2, you want it at 0.
>> 
>
>In this case, sm 2 0101 is correct.   0101 is an odd TWO byte number, 
>being stored in the low word of the longword at 0.

That's right.  Wasn't thinking.  I usually use Macsbug and do a 
	sm 0 'NIL!'

>Greg Marriott



--
David Walton            Internet: dwal@midway.uchicago.edu
University of Chicago   {  Any opinions found herein are mine, not  }
Computing Organizations {  those of my employers (or anybody else). }