Path: utzoo!attcan!uunet!amdahl!ames!pasteur!ucbvax!tut.cis.ohio-state.edu!osu-cis!att!ihlpl!knudsen
From: knudsen@ihlpl.ATT.COM (Knudsen)
Newsgroups: comp.sys.m6809
Subject: Re: Wordpower 3.2 disk I/O blues
Summary: Maybe same problem as Coco III
Keywords: CCBUS coco
Message-ID: <9562@ihlpl.ATT.COM>
Date: 10 Mar 89 19:54:36 GMT
References: <8903061306.AA18126@decwrl.dec.com> <636@emdeng.Dayton.NCR.COM>
Distribution: na
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 30

In article <636@emdeng.Dayton.NCR.COM>, lnewman@emdeng.Dayton.NCR.COM (Lee.A.Newman) writes:
> I purchased a CCBUS several years ago.  I tried it with a 
> J&M disk controller running JDOS, and it would not work.
> After several talks with the makers of the CCBUS, they
> finally fessed up and said there was a problem and they
> did not have a soln for JDOS.  At the time, I noticed that
> the problem probably was in the decoding circuitry on the
> CCBUS.  You probably need to check the addresses the CCBUS
> permits to be sent to the expansion cards.

This may have been the same sort of trouble that the Coco III
sometimes has with its own peripheral decoding.
They neglected to AND-gate the SCS- and CTS- outputs
with the E Clock,
and the resulting glitches caused when addresses change in certain ways
have been blamed for everything fomr
sparklies to the BLOB (Boot LIst Order Bug) in OS9-L2.

There is a hardware hack to fix that, fortunately.
I haven't tried it yet.

If I remember right, the CCBUS was the long, narrow imitation
Multi-Pak made of flimsy cream-colored plastic that got hot
as Hades at one end.
Some members of the clubs I go to have these and they work
all right, which is more than you'd expect.
I don't recallw hether they run JDOS on them.
-- 
Mike Knudsen  Bell Labs(AT&T)   att!ihlpl!knudsen
"Anyone can build a conservative design, given liberal resources." -- MJK