Re: Z-Link hangs on my //c!

[Michael Flynt <michaelflynt@delphi.com>]

Dirk John Fischer <am883@yfn.ysu.edu> writes:
 
>The problem I DO have is, even with a 'factory' ROM & CPU upgrade
>I STILL have problems capturing text in a buffer at 2400 bps!
>1200? - no problem! 2400? - dropped characters & totally unreliable
>captures. This problem also appears using KERMIT's LOG function at
>2400 bps; but, again, not at 1200. Any help?
 
 
It is likely you have the timing problem that was present on the original
/c. Apple offered a free upgrade to fix this problem. This upgrade can and
likely will upgrade your entire system. I went from an original (first release)
/c to the memory expandable unidisk version, and it fixed the problem
entirely. This problem seems to manifest itself at 2400bps. Or even more
perhaps, as I just encountered someone running 9600bps on a //c.
 
What I would like to know is if there is a way to change the character
generator chip in the //c system. I have one that has the "running man" and
would prefer the one with an inverse carrage return symbol.