Path: utzoo!mnetor!uunet!husc6!hao!oddjob!mimsy!umd5!ames!aurora!labrea!agate!ucbvax!cbosgd!cblpf!mdk1
From: mdk1@cblpf.ATT.COM (Michael King)
Newsgroups: comp.sys.m6809
Subject: RS-232 Program Pak fix
Message-ID: <1032@cblpf.ATT.COM>
Date: 3 Feb 88 21:24:55 GMT
Reply-To: mdk1@cblpf.ATT.COM (41450-Michael King)
Distribution: na
Organization: AT&T Bell Laboratories - Columbus, Ohio
Lines: 33
Keywords: Coco3 RS232
Summary: Sorry about posting this


Sorry I had to post this, but I don't have a UUCP path to Eric.

Eric,
Thanks for the info about using the bitbanger instead of the Program Pak,
Pete Lyall sent me some information about how to fix the RS-232 pak to work
with the COCO3.  I hadn't thought about using the port on the back of the COCO.
I'll see if I can get that cable. Your idea may be the easiest solution, or at
least a reasonable temporary one.  If you didn't see Pete's posting on how to
make the PHYSICAL IRQ for the COCO to RS232 Pak, let me know and I will send
you a copy of his instructions.

Also, Tim Koonce posted some information about the 2 mhz. clock speed that
may be causing the problem.  He said it was caused by a problem with the
6551 chip on the pak.

[A general note to the net, if I were to replace the 6551 chip, how would I
know what version to get.  That is, how would I know that the chip I bought
had the bug fixed.  I know that sounds like a dumb question, but I'm
a *REAL* novice when it comes to hardware.]


Thanks again for the information, I'll let you know how it goes.


Mike King
..!ihnp4!cbosgd!cblpf!mdk1

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
UUCP:..!ihnp4!cbosgd!cblpf!mdk1 |"What's the point in being grown-up |- The
                                | if you can't be childish at times?"| Doctor
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~