[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange (whoops!) //c problems
- Subject: Re: Strange (whoops!) //c problems
- From: RKFAIRCLOTH@unca.edu (Rhonda K. Faircloth)
- Date: 1996/08/15
- Distribution: world
- Newsgroups: comp.sys.apple2
- Organization: University of North Carolina at Asheville
- References: <4ur93k$cce@balsam.unca.edu> <3211C68D.73FC@esis.vsnet.ch> <4uts00$i3i@balsam.unca.edu>
Whoops! I've made some mistakes. I'm going to have to run the self test in my
brain to be sure it's working. :)
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?