Xref: utzoo comp.os.os9:453 comp.sys.m6809:1073
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!aucis!easton
From: easton@aucis.UUCP (Jeff Easton)
Newsgroups: comp.os.os9,comp.sys.m6809
Subject: Re: Adapting coco OS9 to other systems
Summary: Uncle! I'll buy one...
Keywords: OS9, coco III, uniboard
Message-ID: <401@aucis.UUCP>
Date: 8 Apr 89 21:43:45 GMT
References: <386@aucis.UUCP> <989@mcrware.UUCP> <388@aucis.UUCP> <22256@agate.BERKELEY.EDU>
Organization: Andrews University, Berrien Springs, MI
Lines: 30


Here comes the expensive solution ... :>

All you guys basically talked me out of trying to do a blind port of OS9
to my Uniboard system.

Since Rainbowfest/Chicago is comming up in about a week, I'm thinking of
driving over there and picking up a Coco 3 and a disk controller if there
are any good deals.  I can then buy OS9 level 2 and use that setup.  If
I get real comfortable with the system I may try the port.

A couple of questions about what to types of hardware to avoid.

1> How can I tell that the coco 3 I buy wont have the infamous "sparklly"
   problem?  Or has the problem even been fixed on late production units?
   Is there a board rev # or such I can look for?

2> What are your recommendations for a floppy controller?  I'm leaning 
   Toward a Disto II controller.  It is of the no-halt variety and has
   a bonus of some type of "port" where other modules can be attached.
   I may use this feature to add a custom board with my ACIA/VIA
   setup off the Uniboard to help in the port.

Comments?  Suggestions?

	Jeff Easton
	Zenith Data Systems

Disclaimer:  I cant be *paid* enough to speak for *anybody*.
	     UUCP: mailrus!sharkey!aucis!easton