Re: IIc/UniDisk Crash to Monitor

[ddkilzer@iastate.edu (David D Kilzer)]

>voss@i40s5.ira.uka.de (Stefan Voss) wrote:
>> 
>> |> 205A-       M=00  A=18  X=00  Y=07  P=33  S=F5
>>    ^^^^        ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^
>>      |          |     |      |     |     |    |
>>  address where  |     |      |     |     |    |
>>  the crash      | Accumulator|   Y-Reg   |  Stack pointer
>>  occurred (BRK) |           X-Reg        |
>>               dunno                  Processor status
>>                                      (zero flag, negative flag, ...)

mark@trillian.jsc.nasa.gov (Mark Manning) writes:

>I'm not sure either, but I think the "M=00" is what was contained at
>memory address $205A.  (Which is the BRK command.)

>What this sounds like is one of three things:

>1. The power supply is having problems with the added burden of
>   running the 3.5" disk drive.

>2. You may need to open up the //c and clean the inside.  If enough
>   dust has accumulated, then you could be having a short somewhere.

Make sure to do this when the power is off.  :^)

>3. Try disconnecting and then reconnecting the 3.5" disk drive.
>   Sometimes the cable doesn't make a good connection.

DO NOT UNPLUG OR PLUG IN THE 3.5" DRIVE WITH THE POWER ON.  You could
really mess something up in your //c if you do this with the power
on.

Dave
-- 
David D. Kilzer               \                ST:TNG _Relics_
Computer Engineer 3           /       Capt. Montgomery Scott ("Scotty")
ddkilzer@iastate.edu          \   "I may be a captain by rank, but I never
Iowa State University, Ames   /    wanted to be anything but an engineer."