Xref: utzoo comp.os.os9:431 comp.sys.m6809:1051
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!osu-cis!mstar!westfort!flounder
From: flounder@westfort.UUCP (The Flounder)
Newsgroups: comp.os.os9,comp.sys.m6809
Subject: Re: coco III mod
Message-ID: <2127@westfort.UUCP>
Date: 11 Mar 89 02:05:26 GMT
References: <8902131928.AA11974@decwrl.dec.com>
Reply-To: westfort!flounder@tut.cis.ohio-state.edu
Organization: Outside the Asylum at the Western Fortress
Lines: 13

It looks to me like you are curing the SCS timing problem on the CoCo 3.  
There ave been wide-spread reports of devices working properly on the 1 and 2 
and behaving intermittently flakey on the 3, due to differences in the SCS 
timing.  Tandy's official response was that peripheral cards should gate SCS 
with the E-clock --- exactly what you are doing.  I ran into this problem (and 
"sparklies") when I attempted the fix given in Rainbow in Martin Goodman's 
column March '89.  My computer refused to boot OS-9, although it wouldrun Disk 
BASIC.  Alteration of one of the timing resistors allowed OS-9 to boot, but 
screwed-up the bus timing, so that the voice pak, already hacked to run at 2 
mhz, wouldn't run at all.  I ended up removing the mod entirely.  Apparently, 
the techie who came up with the fix (Roger Krupski) was working on the earlier 
(1986) version of the GIME.  I'd like to hear from anyone else who tried the 
fix.
Richard Scranton

GEnie address R.SCRANTON
uucp ...!osu-cis!westfort!Flounder