Xref: utzoo comp.sys.mac.misc:3222 comp.sys.mac.programmer:17444 Path: utzoo!attcan!uunet!samsung!rex!wuarchive!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!pequod.cso.uiuc.edu!dorner From: dorner@pequod.cso.uiuc.edu (Steve Dorner) Newsgroups: comp.sys.mac.misc,comp.sys.mac.programmer Subject: Re: MEMORY FAULTS - any way to check ram for intermittent faults?? Keywords: memory ram fault check Message-ID: <1990Sep12.185459.15694@ux1.cso.uiuc.edu> Date: 12 Sep 90 18:54:59 GMT References: <1990Sep11.174118.12194@Neon.Stanford.EDU> <615@keele.keele.ac.uk> Sender: news@ux1.cso.uiuc.edu (News) Reply-To: dorner@pequod.cso.uiuc.edu (Steve Dorner) Distribution: comp Organization: University of Illinois at Urbana-Champaign Lines: 26 In article <615@keele.keele.ac.uk> phd11@keele.ac.uk (Zipzoid) writes: >Plain vanilla !Mbyte Mac+, no INITS etc, sys 6.0.4. >Program dies with err=02, onetime, but restarted and run through to same >position again...no error. >I'm wondering if this can be a intermittent ram fault It's probably sort of an "intermittent ram fudge". 02 is an address error; the 68000 tried to access a word or longword at an odd address, which it can't do. Chances are the program is using an invalid pointer. Chances further are that this pointer is 0, and that your mac dies because the four bytes starting at location 0 are odd. If nobody is purposefully writing to location 0 (and no one should), location 0 will have random junk in it; this is probably why you have a problem sometimes and not others. >Even something that could be entered in (in hex!) through the inbuilt >(ROM based) MAcsbug would be a help! Try saying "sm 2 0101", continuing (what's the command for that in the mini-monitor?) and running the program. If my guesses are correct, it will fail every time. -- Steve Dorner, U of Illinois Computing Services Office Internet: s-dorner@uiuc.edu UUCP: uunet!uiucuxc!uiuc.edu!s-dorner