Re: More //c questions!

[oaaland@aol.com (O Aaland)]

-Dave Althoff writes:

>Now for the more disturbing situation.

>Last night, I built an AppleWriter //e disk off of my enhanced //e's hard
>drive.  It boots into ProDOS 8 v. 2.0.3 (I think that is right...) on the
>//e.  On the //c, I get the P8 splash screen, then the system hangs.  Is
>this the infamous "Apple Only" ProDOS version, or did I just get unlucky? 
>It *was* the first time I tried to boot the //c into ProDOS.  If I need to
>use a different ProDOS version, which should I use...and if I don't happen
>to have it, is it available at support.apple.com?

>Well, when the AppleWriter disk didn't boot, I whipped out an old game. 
>It didn't work right either!  It was a pinball game, and it kept leaving
>traces of the 'ball' all over the screen, ultmately resulting in an
>unreadable mess.  It works fine on the //e...

>Any thoughts?  This //c stuff is all new to me.  I didn't realize it was
>so different from the ][e!


It is not that different from the ][e. What you are decribing is a classic
example of a bad ram chip. Some //c power supplies had a problem that
could blow ram under certian conditions. If I remember correctly the
problem occured at shut down. 

If you have the early ROM without the self test this can be a little more
difficult to pinpoint exactly what chip(s) is bad. I have had pretty good
luck using MECC Computer Inspector. The trick is to find a memory tester
that uses very little RAM to increase your chances that the program does
not have to load into the damaged part of memory. If all else fails then it
is time to do a ROM upgrade so that the diagnostics are in ROM.

Owen Aaland