Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!ncar!boulder!snoopy.Colorado.EDU!frechett
From: frechett@snoopy.Colorado.EDU (Mac the Ripper/ / / /)
Newsgroups: comp.sys.handhelds
Subject: Crashed and Ram 2
Message-ID: <25075@boulder.Colorado.EDU>
Date: 23 Aug 90 10:04:43 GMT
Sender: news@boulder.Colorado.EDU
Reply-To: frechett@snoopy.Colorado.EDU.Colorado.EDU (Mac the Ripper/ / / /)
Organization: University of Colorado, boulder
Lines: 43


I just posted a message about a directory that was in bad shape.  Well, 
while playing with it, trying to figure out what happened, I decide to
try a few things.
The directory is called MUS
I did a 
'MUS' visit
and it paused a sec and then flashed some garbage on the screen and turned 
itself off.  Took a ON-C to get it back on.  Next I tryed, a
'MUS' rcl 
Fine, nothing wrong, then I did an edit.  It spewed stuff all over the place.
shifted the whole screen up about 10 pixels and a about 5 to the right, then
flashed little bits over various parts of the screen for 3 sec and then I 
got .
Try to recover memory?
Yes                 No
I tryed yes and all I was left with was one directory with a scrambled name
so I did a full system reset.  Now, I would like to figure out what did this.
I have had no binary files and the files in that directory where all 2 line
programs haveing to do with musical notes.  Nothing special.  This led me to 
thinking about something that I saw when playing with ON-D.  Unfortunately 
I don't know a lot about the diagnostic stuff.  But I did notice that it will
do a bunch of tests if you press the right keys.  One of them (TAN) will 
do what appears to be a fairly complete check of the system
I do a ON-D and then press TAN and it does this:
spd 19....          (.... can be a variety of numbers)
DISP                (Then does a bunch of quick display tests)
IROM <pause> OK
IRAM <pause> OK
RAM 1 00002          Moving quickly to
RAM 2 00002 <slight pause> 
FAIL 00180      Locks briefly and then repeats whole sequence.  

Now this may be perfectly normal but anytime some electronic device gives
me any type of fail message I start to wonder.  Does anyone know what 
this particular test is supposed to indicate?  Could this possible BUG in my
machine be the cause of things like my directory problem?  I am treading 
on thin air and would love some advice.  I am pulling the batteries and am 
going to let it sit over night.  I tryed it earlier for about 35 minutes and
the clock was still correct when I put the batteries in.  I want it DEAD.  ;)
Any insite would be appreciated.  thanks.

	ian                              frechett@snoopy.colorado.edu