Re: Need Help Identifying Source of //e Boot Error

[Warren Ernst <wernst@gmail.com>]

On Jun 21, 6:26 am, Michael J. Mahon <mjma...@aol.com> wrote:
> Lon Seidman <j...@lonseidman.com> wrote:
> > It looks like the error screen I'm getting happens early in the boot
> > sequence, so it's not responding to the diagnostic request (either
> > through the closed apple method or disconnecting the keyboard).  
>
> > It pops right to the error screen almost immediately once the power
> > comes on.
>
> That's why you should first re-seat the socketed chips.  Then try again.
>
>
>
>
>
> > mojoehand <mojoeh...@gmail.com> wrote:
> >> On Jun 20, 9:32 pm, Lon Seidman <lonseid...@gmail.com> wrote:
> >>> Hi all,
>
> >>> Can anyone help me identify what might be triggering the following
> >>> //e
> >>> boot error screen?
>
> >>>http://www.flickr.com/photos/lonseidman/4719844792/
>
> >>> I probably shouldn't be surprised to see this given it has been in a
> >>> garage for 15 years, but it would be nice to get this machine
> >>> breathing
> >>> again :).
>
> >>> Any ideas for trouble shooting would be greatly appreciated!
>
> >> I would first reseat all the chips. Then run a RAM test. I don't
> >> recall the exact details, but I think that if you unplug the
> > > keyboard,
> >> the IIe goes into a diagnostic test. If I'm wrong, someone else will
>
> chime in.
>
> -michael  -  NadaNet 3.1:  http://home.comcast.net/~mjmahon

Removing all the cards after you reseat all the chips and before
booting up would be useful too. If it then boots up to a ] prompt,
then start re-adding cards one at a time.

-Warr