Path: utzoo!mnetor!uunet!husc6!bbn!rochester!ur-tut!sunybcs!boulder!tramp!williamm
From: williamm@tramp.Colorado.EDU (Michael Williams)
Newsgroups: comp.sys.apple
Subject: Help- Fried Apples & Dumplings
Message-ID: <5718@sigi.Colorado.EDU>
Date: 28 Apr 88 20:30:35 GMT
Sender: news@sigi.Colorado.EDU
Reply-To: williamm@tramp.Colorado.EDU (Michael Williams)
Organization: University of Colorado, Boulder
Lines: 42
Keywords: ][+ //e Dead


   Okay, I am in a very harsh bind here:  Neither my ][+ nor my //e
will startup correctly, and I am not desiring to pay $80 for a techie
to take off my lid and replace a $1 chip from an obvious failure.
   The problem is...it isn't obvious to me (so that's what they get
paid for, I know...).  Both problems are fairly close, but not exact,
so here they are:

][+ : It was given to me dead, so I am not sure what the immediate
      cause of failure was.  When the machine is turned on, no card
      is accessed (not the disk controller at least), and the screen
      has a static display of '?'s, ' 's, and 'F's.  Nothing else.
      I am pretty sure that the power supply has nothing to do with it
      (for I replaced it temporarily with a good one).

//e : I saw this one bite it.  I was playing a game and was pulling 
      a loose joystick cable out from the machine (it was not plugged
      in, but just sitting there looking stupid) when ALAS, my screen
      became filled with columns alternating between normal and inverse
      spaces (rows of black and white).  Turning the machine off and then
      (not immediately) back on resulted in the same lovely pattern,
      and when the disk controller was in place, the SECOND drive would
      start spinning until I did a RESET.  The self-diagnostics test
      only caused a temporary additional patter to be spit to the the
      screen.  ----BTW, this is (was? :-( ) unenhanced.

With both of these machines I have removed all cards so as to at least
pinpoint it to the motherboard (pretty specific, eh?).  Also,  I have
checked the power supplies, and they are both appearing okay.  My guess
is that it has to do with the AutoStart ROMS, but it could be the 6502.
Any suggestions as to what to check?  What could have gone wrong?
Which ROM (if so) ? Or even a good troubleshooting book?

PLEASE help me get these (at least the 'e) back onto their feet.  

Thanks much in advance for any and all help,
Remo

------------------------------------------------------------------------------
..{nbires,ncar,seismo,ihnp4}!boulder!tramp!williamm \ Bela Lugosi  riding  the
BIT: WILLIAMS_MS%CUBLDR@VAXF.COLORADO.EDU           / Kundalini Express in ...
SNAIL: 2905 E Aurora Ave #129, Boulder CO 80303     \ (could it be?) Sunshine!