Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!im4u!milano!baxter From: baxter@milano.UUCP Newsgroups: net.micro.6809 Subject: CoCo III, 1.8 Mhz, Slow Peripherals Message-ID: <2676@milano.UUCP> Date: Thu, 23-Oct-86 15:25:12 EDT Article-I.D.: milano.2676 Posted: Thu Oct 23 15:25:12 1986 Date-Received: Fri, 24-Oct-86 01:16:11 EDT Sender: baxter@milano.UUCP Organization: MCC, Austin, TX Lines: 33 Keywords: CoCo III Those of you having CoCo IIIs and some understanding of the hardware can do a great service for those of us who don't. CoCo III promises compatibility of peripherals with CoCo II peripherals, presumably including floppy disk controllers and modem cards. It also promises 1.8 Mhz operation. Usually faster processors won't work with controllers designed for slower machines controllers (Motorola supplies different versions of it 6809 family for different clock rates); can someone explain why the CoCo III should be an exception? For BASIC, I suppose that the following strategem might work: run at 1.8Mhz until I/O is necessary, slow down to .8Mhz, do the I/O, speed back up again. If this was done consistently, I don't understand the CoCo III is delivered running at .8Mhz as the default (excuse my ignorance if that's not the case... data on the CoCo III is really hard to find right now). Under OS-9, the strategem wouldn't work as well, especially if several devices were busy at once. Reducing OS-9 to running at .8Mhz as the least common denominator would make a joke of the 1.8Mhz ability. Anybody sane would automatically WANT the 1.8Mhz as the default, so I presume that it is under OS-9... so there must be a different strategy. An aside: was the typeahead problem with OS-9 ever solved (i.e., I can't typeahead while the disks are spinning? Replies should be to the net. If I get personal replies, I will summarize. Sorry about the bungled message preceding. -- Ira Baxter arpanet: baxter@mcc.com MCC Corporation usenet: ut-sally!im4u!milano!baxter