Re: More //c woes...

[oaaland@aol.com (O Aaland)]

<< Simon Williams wrote:

> Seems like the //c is getting a lot of airplay these days, so here's
> my two bits (should that be 8?)
>
> I've found that when I'm fiddling about in AppleSoft on my //c (can't
> remember which version, but the one that supports UniDisk,
> anyway...)...
>
> Uh, where was I ??? Yes, fiddling.
> After a while the //c starts to ignore my input. I'll be programming
> away, LIST the program and voila! The last n lines are missing. This
> is infuriating.
>
> So I type: SAVE MY.PROGRAM
> //c sez: SYNTAX ERROR
> I say: PR#6
> //c sez: SYNTAX ERROR etc... you see the pattern.
>
> Typically this ends with me turning off the computer and turning it
> back on after a minute or so, at which point the machine is acting
> like it never happened and everything is still fine between us...
>
> The computer is well ventillated and does not heat up appreciably... I
> tried to open it up the other day, but even after pulling all the
> screws the case would not yield (which is probably for the best, since
> that was as far as my plan went).
>
> Any thoughts?
 >>


If you have a IIc that supports a 3.5 drive, any one ecept the earliest
version, you can run the built in diagnostics. It is posible that you have a
defective memory chip that causes problems when you try to use that area of
memory.

Hold down the option (closed apple) key while turning on the computer to run
the dianostics. If nothing happens except random paterns on the screen you have
the early ROM with no diagnotics. If after a minute or two you see SYSTEM GOOD
or some other message then you have a self diagnosing machine. Early machines
cane be updated by changing thr ROM chip.

Owen A