Re: Strange (whoops!) //c problems

[rubywand@aol.com (RUBYWAND)]

In article <4uu0cs$mcf@balsam.unca.edu>, RKFAIRCLOTH@unca.edu (Rhonda K.
Faircloth) writes:

>
>My //c is the oldest version, PEEK(64447) returns 255, not 0.
>So I guess I sorta re-ask the question about the forever-loopiness of
>this ROM version: Is "no bad news" the same as "System OK"?
>
>On another note, I seem to recall that the oldest //c's also had
>some timing problems on the serial ports. Was there something other
>than a one-chip-ROM-upgrade that needed to be done in order to fix
>this? I'm considering upgrading the ROM with a burned EPROM. My final
>goal is to sell it. Maybe I can modify the ROM a bit for hacking and/or
>fun?
>
>

     Swapping in a modified-code PROM sounds like a fun project. You can
fix things up so that the old ROM can be switched-in when necessary and
put some neat stuff (e.g. new monitor commands) on the PROM. Possibly, you
could even come up with a mod (maybe, on a third 'ROM')  which would let
the IIc pass the ROM check tests that prevent IIc from running many old
games.

     It is worth noting that if the objective is, mainly, to have a
working IIc, then your best bet is to shop local school sales and II User
Group swap meets. You should be able to find a good IIc+ for around $30.
 

Rubywand