<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The TRS-80/Tandy Color Computer SuperSite! &#187; Delphi &#8211; System Modules 6809</title>
	<atom:link href="http://www.coco3.com/community/category/archives/delphi/delphi-system-modules-6809/feed" rel="self" type="application/rss+xml" />
	<link>http://www.coco3.com/community</link>
	<description>A Rainbow 30 Years Wide!  Long Live The CoCo</description>
	<lastBuildDate>Wed, 28 Jul 2010 17:39:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<atom:link rel="next" href="http://www.coco3.com/community/category/archives/delphi/delphi-system-modules-6809/feed?page=2" />

		<item>
		<title>sony 1302</title>
		<link>http://www.coco3.com/community/1994/12/sony-1302</link>
		<comments>http://www.coco3.com/community/1994/12/sony-1302#comments</comments>
		<pubDate>Sun, 18 Dec 1994 10:54:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/12/sony-1302/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>91025 18-DEC 10:54 System Modules (6809)<br />     sony 1302<br />     From: DONALDS      To: MARTYGOODMAN (NR)</p>
<p>Marty;</p>
<p>I got a sony 1302 monitor the other day and seem to have a problem with it.<br /> when I turn on the system the screen will come up fine then after it warms<br />about a minute there is a snap and I get 2 yellow line across the top of the<br />screen<br />athis the monitor works fine. would you have a sujestion (sp) as to what it may<br />be?<br />                 Don</p>
<!-- Easy AdSense V2.92 -->
<!-- Post[count: 2] -->
<div class="ezAdsense adsense adsense-leadout" style="text-align:center;margin:12px;"><script type="text/javascript"><!--
google_ad_client = "pub-2798421614853654";
/* 336x280, created 10/3/09 */
google_ad_slot = "9708036280";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div>
<!-- Easy AdSense V2.92 -->

]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/12/sony-1302/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>CC3IO Patches</title>
		<link>http://www.coco3.com/community/1994/12/cc3io-patches</link>
		<comments>http://www.coco3.com/community/1994/12/cc3io-patches#comments</comments>
		<pubDate>Mon, 05 Dec 1994 16:48:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/12/cc3io-patches/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90893 5-DEC 16:48  System Modules (6809)<br />     CC3IO Patches<br />     From: GREGL        To: ALL</p>
<p>Can anyone answer this question?</p>
<p>From:   IN%&#8221;78-5750@terranet.bluethun.quake.com&#8221;  2-DEC-1994 15:29:54.85<br />To:     IN%&#8221;gregl@delphi.com&#8221;<br />Subj:   cc3io.dr patches&#8230;</p>
<p>     Hello Greg,<br />     Marty pointed me in your Direction, as He did not know the Internet<br />address of Kevin Ddarling&#8230;<br />     I&#8217;m trying to patch cc3io.dr from Version 2.00.01 of Level II OS-9 as so<br />to properly recieve OS-9 Escape sequences over the phone-line properly&#8230;<br />     My first attempts at patching it with Information in Rainbow (2/88 I<br />believe), and Confirmed by Mike Guzzi (ApBBS Pensylvania 1-717-586-2771) was<br />interactively (not using a file and the -s option of modpatch) screwed up cc3io<br />royally&#8230; Then I tried the -s option and the file method, most bytes this time<br />around gave me a &#8220;byte does not match&#8221; warning, but other than that seems to<br />function MOSTLY&#8230; I was wondering if there was a specific patch needed or not<br />for this version of CC3io.dr</p>
<p>Edition: $10<br />Mod CRC: $F737C2      <modified for RGB default and slower kbd io: $8C69BA ></p>
<p>     Any help is appreciated&#8230;</p>
<p>Also speaking of Mods&#8230;. I heard there was a 1 byte mod for os9p1 that seemed<br />to cut down on the overhead considerably enough that 9600bps was reliable&#8230;<br />     I have the Eddie Kuns Edition 9 Clock Modules < Bigger than Level II's<br />Edition 9 clock modules>, SACIA, VRN, and NIL added to increase speed, but only<br />wound up with at best a near 100% ability of ANSI at 4800bps using Supercomm<br />2.2.</p>
<p>Thanks in advance&#8230;</p>
<p>-Later!<br /> -SS-<br />     FidoNet Address: William Barnes@1:239/1100<br />     InterNet Address: 78-5750@bluethun.quake.com <methinks></p>
<p></methinks></modified></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/12/cc3io-patches/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>boots</title>
		<link>http://www.coco3.com/community/1994/11/boots</link>
		<comments>http://www.coco3.com/community/1994/11/boots#comments</comments>
		<pubDate>Sun, 27 Nov 1994 20:17:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/11/boots/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90822 27-NOV 20:17 System Modules (6809)<br />     boots<br />     From: RICKULAND    To: ALL</p>
<p>     Well,  I  haven&#8217;t had this much fun in years.  Anybody  else<br />want  to play? The givens- a 1 meg 6809 and disto drive. Needed a<br />new boot badly. trot out all the old favorites&#8230;..<br />     Results-   after  remembering the attr thing, a deblob (just<br />repositioned)  to get the floppies writing, looks ok, except std*<br />won&#8217;t  merge to /w, and I cannot install term_win. Term_vdg works<br />fine, extra windows look ok, MVue even starts (without fonts).<br />     Ezgen  term_win in &#8211;  boot failed way back in the  OS9  BOOT<br />stage. Tried 3 windints, 2 scf, and serveral term,w,etc descripts<br />     So I&#8217;m quite stuck. Anybody?</p>
<p>                              -ricku</p>
<p>                  Rick Ulland                 CoNect<br />         rickuland@delphi.com           449 South 90th St.<br />&#8220;Operating System Nine&#8221;- 268m           Milwaukee WI 53214</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/11/boots/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>TESTCLOCK</title>
		<link>http://www.coco3.com/community/1994/11/testclock</link>
		<comments>http://www.coco3.com/community/1994/11/testclock#comments</comments>
		<pubDate>Thu, 10 Nov 1994 08:25:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/11/testclock/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90627 10-NOV 08:25 System Modules (6809)<br />     TESTCLOCK<br />     From: DONALDS      To: WDTV5</p>
<p>I have tried to get your new clock for the Disto 4n1 going but I seem to have<br />a problem &#8211; I get a boot fail every time I try to boot with it. I can remove<br />it and boot just fine. I am using a 63c09 ,4n1 , scsi drive, and do most of my<br />boot from the harddrive. all I have on the boot disk is OS9BOOT. I have moved<br />modules and some other stuff but still get a boot fail. Can you help.<br />             Don</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/11/testclock/feed</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>RBF</title>
		<link>http://www.coco3.com/community/1994/11/rbf</link>
		<comments>http://www.coco3.com/community/1994/11/rbf#comments</comments>
		<pubDate>Sun, 06 Nov 1994 01:18:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/11/rbf/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90594 6-NOV 01:18  System Modules (6809)<br />     RBF<br />     From: VE3DAC       To: WDTV5</p>
<p>Well  a bit late  but Happy 60th.  Hope that there are lots more highway<br />miles in the old body.<br />Thanks for the RBF fixes, but dare I use them at Version 1? <g>.  iI&#8217;ve had<br />to go back to V.28  on the BBS with the new 130 meg drive, didn&#8217;t want to<br />think about an allocation map that big at 1 sector per.  Almost the first thing<br />I did of course was to delete a file I didn&#8217;t mean to.<br />So now we may be ok.  I&#8217;ll pass them on to Gene K.  see how rbf30B(     ? i thin<br />k)<br />works on his Powerboost system.  Talk to you again soon.<br />Mmerv<br />  Damn old keyboard&#8230;..</p>
<p></g></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/11/rbf/feed</wfw:commentRss>
		<slash:comments>28</slash:comments>
		</item>
		<item>
		<title>ram alloc?</title>
		<link>http://www.coco3.com/community/1994/10/ram-alloc</link>
		<comments>http://www.coco3.com/community/1994/10/ram-alloc#comments</comments>
		<pubDate>Fri, 28 Oct 1994 20:54:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/10/ram-alloc/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90484 28-OCT 20:54 System Modules (6809)<br />     ram alloc?<br />     From: RICKULAND    To: ALL</p>
<p>     Ofnohoc   has  been playing with infoexpress,  installing it<br />under   MultiVue.   To  hide  the  subdirs,  the  AIF  calls   an<br />intermediate  procedure file to do the cd. Ix needs a patch under<br />shell+ anyway, to allocate less memory at startup- this was done.</p>
<p>     It was next to impossible to get ix started from a procedure<br />file! Starting with the hopelessly optimistic &#8216;ix&#8217;, the line that<br />finally killed the last bug is (drum roll&#8230;.)</p>
<p>                      ex shell ix #1 <>>>/1</p>
<p>     Prevous  failures  ranged  from fatal error  straight  away,<br />through a few 207&#8242;s and ram locks, finally stdin tied to /h0, one<br />last  207  (cumon, one page?), and here we are:-) Surely this  is<br />wrong?</p>
<p>                              -ricku</p>
<p>                  Rick Ulland                 CoNect<br />         rickuland@delphi.com           449 South 90th St.<br />&#8220;Operating System Nine&#8221;- 268m           Milwaukee WI 53214</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/10/ram-alloc/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Powerboost v.2.0</title>
		<link>http://www.coco3.com/community/1994/10/powerboost-v-2-0</link>
		<comments>http://www.coco3.com/community/1994/10/powerboost-v-2-0#comments</comments>
		<pubDate>Thu, 27 Oct 1994 23:57:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/10/powerboost-v-2-0/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90481 27-OCT 23:57 System Modules (6809)<br />     Powerboost v.2.0<br />     From: NEALSTEWARD  To: ALL</p>
<p>I finally solved my hardware problems, and am now attempting to install<br />everything I can to squeeze every little bit of speed out of this coco 3.<br />I found that after installing the B&#038;B Powerboost Native patches on my<br />boot disk, that the system crashes when I try to format my RamDisk (I<br />use /r0 &#038; rammer patched to 384k).  Is there a chance that this somehow<br />conflicts with the 2 meg upgrade???  It works without the Native patches<br />and works with the Powerboost Tuneup patches.  Any guesses?  Is there<br />anyone else running a system like this:<br />2 meg Coco 3 with HC63B09E, MPI, Ken-Ton SCSI HD, Disto SCII in no-halt<br />mode, Speech pak and a Ken-Ton Dual RS232 pak?  If you are, let me know<br />what patches &#038; upgrades are working for you.</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/10/powerboost-v-2-0/feed</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>PowerBoost &amp; SCII</title>
		<link>http://www.coco3.com/community/1994/10/powerboost-scii</link>
		<comments>http://www.coco3.com/community/1994/10/powerboost-scii#comments</comments>
		<pubDate>Sun, 16 Oct 1994 18:09:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/10/powerboost-scii/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90342 16-OCT 18:09 System Modules (6809)<br />     PowerBoost &#038; SCII<br />     From: NEALSTEWARD  To: ALL</p>
<p>Can anyone suggest how I can get B&#038;B&#8217;s PowerBoost to patch my SCII<br />drivers, since I use the alternately addressed version?  PB tuneup<br />skips the SCII drivers and I cannot use the ones addressed at $FF74-<br />$FF77 because of a conflict with the Ken-Ton SCSI pak.<br /> if I make a boot with the regular drivers, run tuneup and<br />then use ded to patch the 10 or 12 bytes that are different so CC3disk<br />addresses $FF58-5F?  Has anyone else discovered thsi problem?<br />thanks&#8230;</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/10/powerboost-scii/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RBF, new versions</title>
		<link>http://www.coco3.com/community/1994/10/rbf-new-versions</link>
		<comments>http://www.coco3.com/community/1994/10/rbf-new-versions#comments</comments>
		<pubDate>Sat, 08 Oct 1994 23:23:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/10/rbf-new-versions/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90257 8-OCT 23:23  System Modules (6809)<br />     RBF, new versions<br />     From: WDTV5        To: ALL</p>
<p>Hi all, I&#8217;ve now uploaded a pair of files, both fix the same problem, one for<br />std 6809 systems, and one for Nitros9 systems. The problem was that if you<br />were using more than 1 sector pere cluster opon your your disks, a delete<br />did not clear all the allocation bits and the disk would slowly fill up<br />with allocated, but otherwise unattached sectors. These fix that. Then<br />UnDel, by Bob Santy, fails on a multisector cluster disk. I&#8217;ve got it<br />fixed for multisector clusters, but managed to break it for single cluster<br />disks. So that will be a day or two comeing yet. Sorry. Its been a long<br />day this week.<br />Cheers all, Gene</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/10/rbf-new-versions/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disto SCSI board</title>
		<link>http://www.coco3.com/community/1994/09/disto-scsi-board</link>
		<comments>http://www.coco3.com/community/1994/09/disto-scsi-board#comments</comments>
		<pubDate>Tue, 27 Sep 1994 20:05:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/09/disto-scsi-board/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90124 27-SEP 20:05 System Modules (6809)<br />     Disto SCSI board<br />     From: DAVID106     To: ALL</p>
<p>Is it still possible to get the Disto host adapters for CoCo&#8217;s?<br />I&#8217;ve had a Quantum 105LPS laying around for some time now, and figure<br />it might be nice to actually be able to use it.  I&#8217;d need a disto<br />board, because I have a fried slot in my multi-pak, so it needs to go<br />in with the disk controller.</p>
<p>Thanx in advance,<br />  Dave</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/09/disto-scsi-board/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>printers</title>
		<link>http://www.coco3.com/community/1994/09/printers-9</link>
		<comments>http://www.coco3.com/community/1994/09/printers-9#comments</comments>
		<pubDate>Mon, 26 Sep 1994 08:37:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/09/printers-9/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90104 26-SEP 08:37 System Modules (6809)<br />     printers<br />     From: DONALDS      To: MARTYGOODMAN</p>
<p>Marty;</p>
<p>  I am looking at getting a new printer. What I would like to get is a<br />LASER printer Will this work with a COCO3 and the parallel port on a<br />disto 4n1 board. I thought I remembered you listing a pinout for it or<br />at least some    instruction on how to hook one up in the &#8217;68 Micro<br /> a while back. could you help me with this ?  Can this connection be<br />made thru the use of just a parrallel cable?</p>
<p>       Don</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/09/printers-9/feed</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>error 202</title>
		<link>http://www.coco3.com/community/1994/09/error-202</link>
		<comments>http://www.coco3.com/community/1994/09/error-202#comments</comments>
		<pubDate>Wed, 21 Sep 1994 08:28:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/09/error-202/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90036 21-SEP 08:28 System Modules (6809)<br />     error 202<br />     From: DONALDS      To: DBREEDING</p>
<p>Hi; in a earlier message you and Boisey mentioned that error 202 was caused<br />by not having the drive descripters inized. You mentioned a patch for the<br />disto drivers &#8211; I looked for that patch here in the data base and was not<br />ablr to find it. Could you email me that patch? I would be most thankful.<br />       Don</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/09/error-202/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Shell22a</title>
		<link>http://www.coco3.com/community/1994/09/shell22a-2</link>
		<comments>http://www.coco3.com/community/1994/09/shell22a-2#comments</comments>
		<pubDate>Mon, 19 Sep 1994 01:24:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/09/shell22a-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>90013 19-SEP 01:24 System Modules (6809)<br />     Shell22a<br />     From: VE3DAC       To: KSCALES</p>
<p>It seems that this is the first, am I the only one having a problem?<br />I installed the SCF and made my new merged shell module and generally it<br />seems to work ok.  I installed it to use with my Nitro boot, and all I<br />get is a technicolor screen. We&#8217;ll see how it goes when the 1.20 update<br />arrives.  But one utility  fstat  no longer seems to work on two different<br />systems.  All i get is a read error, on the hard disk or floppy.<br />  I installed the scf and shell on my Ribbs BBS  system, not Nirtro, and<br />ribbs won&#8217;t load or run. Its ok with the new scf and my shell2.1.  Seems<br />to me I had another problem, but can&#8217;t find that note.<br />   Perhaps you can pass this onto Bill, or make a suggestion?<br />Merv</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/09/shell22a-2/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>cc3disk</title>
		<link>http://www.coco3.com/community/1994/08/cc3disk</link>
		<comments>http://www.coco3.com/community/1994/08/cc3disk#comments</comments>
		<pubDate>Sat, 13 Aug 1994 22:50:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/08/cc3disk/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>89270 13-AUG 22:50 System Modules (6809)<br />     cc3disk<br />     From: SMITHBA      To: DBREEDING (NR)</p>
<p>You mentioned in a letter about a patch for cc3disk, so it will clear it&#8217;s<br />interupt when it is done. I assume you are talking about the super controller<br />2 no halt drivers. that is exactly what I have been looking for. Could you tell<br />me exactly what the name of the file is, and what topic it&#8217;s under.<br />also i&#8217;m looking for a patch to the kernal patch by bruce istead. it&#8217;s<br />supposed to recognize up to two meg, but will only recognize one meg.<br />I had to use the original kernal, and I patched the old mega command.<br />any help would be appreciated.</p>
<p>Brian Smith (SMITHBA)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/08/cc3disk/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>scsi in Burke and Burke with Scsisys10</title>
		<link>http://www.coco3.com/community/1994/08/scsi-in-burke-and-burke-with-scsisys10</link>
		<comments>http://www.coco3.com/community/1994/08/scsi-in-burke-and-burke-with-scsisys10#comments</comments>
		<pubDate>Fri, 12 Aug 1994 04:17:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/08/scsi-in-burke-and-burke-with-scsisys10/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>89241 12-AUG 04:17 System Modules (6809)<br />     scsi in Burke and Burke with Scsisys10<br />     From: MDALENE      To: ALL</p>
<p>I have a weird question, I know I should ask Chris burke this but&#8230;. Since<br />he does not write scsisys and this also applies to that author here is my<br />question<br />    I found a great deal on a Maxtor 290MB 12ms SCSI HD. and a 8 bit scsi<br />card. I was going to buy it for my xt but&#8230;. I think Cecilia (My coco 3)<br />would make better use of it. I was going to install it externally so it<br />could plug into the card via the 25pin scsi external connector. First of all<br />does Scsisys allow a user to set the port address easily along with the slot<br />selection? B&#038;B needs BOTH! and also&#8230; would the thing work The card I am<br />thinking of ordering uas a scsi driver you load from Disk. I deliberatly<br />said &#8220;NO&#8221; to the HD only version as it only allowd two HD devices and did<br />not even alllow Tape or CD-rom. (When I buy cards, I use device drivers,<br />just like on my Coco, I eat TPA (cp/m speak) but then upgrading is easier.<br />    Does Scsi sys 1.0 have a certain register demand? Does it nessarly need<br />a certain brand of Scsi chip? or if I had that info would the author prepare<br />me a version for testing? If it does not&#8230; I have a hungry Xt waiting&#8230;<br />but The case looks like it matches the coco 3 Much better. I was going to<br />lay out the Scsi HD to use 30 Meg partitions on the IBM. Give the old St-225<br />(20 MEG! Geez! Cecilia only fills hers half way full! and it is the same<br />size but newer Kalok 320!)<br />    Sorry this is so long but I really think that knowing this info could<br />give us with the B&#038;B system a second chance to go SCSI. I want to use SCSI<br />as the MFM hardware is not easily found new and I do not want to have to<br />worry if the HD croaks and I got an old outdated interface that has no<br />support. I think Chris Burke did mention that if the card selected does not<br />use IRQ&#8217;s it may work. I do not know if it does or not but My HD on my XT<br />does have an IRQ address and it works fine on my Coco 3.<br />                                     Michele Marie Dalene</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/08/scsi-in-burke-and-burke-with-scsisys10/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Making a new boot disk from scratch</title>
		<link>http://www.coco3.com/community/1994/07/making-a-new-boot-disk-from-scratch</link>
		<comments>http://www.coco3.com/community/1994/07/making-a-new-boot-disk-from-scratch#comments</comments>
		<pubDate>Sun, 31 Jul 1994 17:03:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/07/making-a-new-boot-disk-from-scratch/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88967 31-JUL 17:03 System Modules (6809)<br />     Making a new boot disk from scratch<br />     From: STEWARD      To: ALL</p>
<p>  I need some help. I&#8217;ve trashed all my floppy boot disk&#8217;s awhile ago, and I am<br />trying to start from scratch w/ the orginal level 2 disks. The problem I&#8217;m<br />having is that I can use config to create a new disk w/ the double sided<br />decriptors, but when I try to create a double sided disk to boot from, I keep<br />getting<br />the treaded BOOT FAILED.  I have tried using os9gen and cobbler to no avail.<br />Can anyone give some suggestions?<br />  Thanx.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/07/making-a-new-boot-disk-from-scratch/feed</wfw:commentRss>
		<slash:comments>28</slash:comments>
		</item>
		<item>
		<title>OSK Software</title>
		<link>http://www.coco3.com/community/1994/07/osk-software</link>
		<comments>http://www.coco3.com/community/1994/07/osk-software#comments</comments>
		<pubDate>Sat, 16 Jul 1994 22:51:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/07/osk-software/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88670 16-JUL 22:51 System Modules (6809)<br />     OSK Software<br />     From: WDTV5        To: NIMITZ</p>
<p>  David;</p>
<p>  I can&#8217;t resist making a comment regarding the &#8220;50&#8243; varieties of COCO-OS9<br />  L2 right now. While there may be a valid argument that each of us has<br />  &#8220;customized&#8221; the system such that it now does &#8220;what we want it to do&#8221;, I<br />  would also argue that the &#8220;customizations&#8221; were brought about in nearly<br />  every case because we wanted it to do something that the MicroWare&#8217;s<br />  original vision discounted as &#8220;not important enough to waste a variable<br />  on&#8221;.  And please Boisy, don&#8217;t take offense as much of this thinking<br />  probably pre-dates your involvement.</p>
<p>  I refer you to such things as the hard-coding of many things that we had<br />  to dig into and find later (or sooner in many cases) because they really<br />  were important enough to &#8220;waste a variable&#8221; on.  The original release<br />  cc3disk comes to mind for starters.  All the (relatively simple) patches<br />  required to make the C compiler actually run were another. Same comment<br />  applies to the Pascal too.</p>
<p>  Then comes Multiview, DeskMate I &#038; II, DynaCalc, Profile.  All of these,<br />  WITHOUT EXCEPTION needed massageing in one form or another.  I won&#8217;t<br />  belabor the point on DM I or II, nor send it flowers in memory of its early<br />  demise.  Multiview of course has had its main module &#8220;gshell&#8221; redone<br />  several times along with grfdrv.  DynaCalc yet needs some way to really<br />  control how it treats the printer instead of all these patches to get rid<br />  of the spurious form feed.  It really wasn&#8217;t spurious if the last job left<br />  it sitting in mid page, but *nobody* thought of that. The real cure was to<br />  have the printer ignore the darn thing IF it was allready sitting at<br />  pagetop.  Not many printers are that smart tho. A one byte var could have<br />  taken care of that in DCalc.</p>
<p>  Profile as I recall needed something done too, but I don&#8217;t at the moment<br />  recall what it was, I did it so many years back. And yes, I still use it<br />  on a semi-stock L2 system at the station.</p>
<p>  The C &#038; Pascal compilers, DynaCalc and Profile were all originally L1 and<br />  they required patches NOT to make them run on level 2, but to make them run<br />  on the average system which didn&#8217;t quite match the bare minimum system<br />  used as a hardware model. Hard-codeing things like the devicename was/is<br />  pretty inexcusable. I hear somebody saying &#8220;but we didn&#8217;t have /dd then&#8221;,<br />  which is pure hog-wash! The idea was just as valid on a level one system.<br />  WE just hadn&#8217;t thought of it YET.</p>
<p>  (Pulling out soapbox)<br />  The last point I&#8217;d like to make refers to the other comments in this<br />  thread regarding gfx drivers..  If the machine can support the graphics<br />  that apparently the MM/1 can, then the graphics drivers ARE PART AND<br />  PARCEL of the op-sys AS SHIPPED! The fact that you would have to raise the<br />  price of the package by some nominal sum (I saw $50 mentioned) has<br />  absolutely nothing to do with it in terms of &#8220;a marketing decision&#8221;<br />  because *then* you are shipping a system capable of running the application<br />  regardless of what that application might be.  The application will then<br />  be written to &#8220;your&#8221; standard.  And thats worth far more in the long run<br />  than any $50 you might &#8220;save&#8221; in the short term.  Later &#8220;for fee&#8221; upgrades<br />  then will build on that standard as they will be forced to remain<br />  &#8220;compatible&#8221; unless the distribution version is so buggy it really does<br />  need thrown out . . .  Nobody enjoys re-inventing the wheel unless the<br />  first model was square or ?</p>
<p>  It also has the effect of setting a short-term &#8220;standard&#8221; way of doing<br />  things thereby enhancing right up front, the &#8220;compatiblility&#8221; issue we now<br />  have in the L2 arena because so many of us have gone on to the Hitachi CPU<br />  in the native mode.  The PB folks have the ability to &#8220;run what they<br />  brung&#8221; while the slightly faster Nitros9 group had to wait for a patched<br />  &#8220;Home Publisher&#8221;.  Not many of us chewed any fingernails waiting for it<br />  but now we have it again. (And its *still* painfully slow)</p>
<p>  The point is that if we would have had a Multiview that actually worked<br />  shipped WITH the OS-9 distribution, I think the playing field between us<br />  and the Intel crowd would have been much closer to level. The folks in<br />  Westchester might have turned up the heat a bit faster too. (Commie<br />  Amiga&#8217;s) We&#8217;ve also wasted entirely too much time on the BLOB. This has to<br />  be a hardware thing, probably in the GIME.  That it should never have seen<br />  light outside outside the back door of 1 Tandy Center is a given! I have<br />  personally written letters to the people whom I thought could answer<br />  questions like &#8220;How much for another run of 5000&#8243; and &#8220;are the databases<br />  to define it available so the bugs can be fixed?&#8221;.  Nobody took the time<br />  or the postage to reply. Had my letters been answered, you can bet yours<br />  that I would have been on here asking for donations to help offset the<br />  &#8220;OTE&#8221; costs involved. Obviously I haven&#8217;t.</p>
<p>  So I wasted a page on your printer. But thats how it seems to me.</p>
<p>  Cheers &#8211; Gene</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/07/osk-software/feed</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Smartwatch / Ken-ton Clock</title>
		<link>http://www.coco3.com/community/1994/07/smartwatch-ken-ton-clock</link>
		<comments>http://www.coco3.com/community/1994/07/smartwatch-ken-ton-clock#comments</comments>
		<pubDate>Fri, 15 Jul 1994 03:52:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/07/smartwatch-ken-ton-clock/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88621 15-JUL 03:52 System Modules (6809)<br />     Smartwatch / Ken-ton Clock<br />     From: BILL32H      To: ALL</p>
<p> Help !!!</p>
<p>   Somebody how dose one change the base address of the smartwatch to<br />say FF70 , or were can I get a ST MK48T02-20 Clock chip I&#8217;ve tryed<br />the mk48Z02b it don&#8217;t work.<br />                               BILL32H</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/07/smartwatch-ken-ton-clock/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Module fix?</title>
		<link>http://www.coco3.com/community/1994/07/module-fix</link>
		<comments>http://www.coco3.com/community/1994/07/module-fix#comments</comments>
		<pubDate>Wed, 13 Jul 1994 20:51:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/07/module-fix/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88591 13-JUL 20:51 System Modules (6809)<br />     Module fix?<br />     From: MIKE_GUZZI   To: ALL</p>
<p>I want to change my disk controller so its no longer in slot 4. Im running<br />the sardis controller (sdisk 3) i think Sdisk3 has the slot number in it<br />but are there any other system modules that change the multipak slot to 4??<br />all my other devices are fully decoded and do not use the SCS line.</p>
<p>Mike</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/07/module-fix/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>PIA</title>
		<link>http://www.coco3.com/community/1994/07/pia</link>
		<comments>http://www.coco3.com/community/1994/07/pia#comments</comments>
		<pubDate>Fri, 08 Jul 1994 09:19:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/07/pia/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88477 8-JUL 09:19  System Modules (6809)<br />     PIA<br />     From: DONALDS      To: MARTYGOODMAN (NR)</p>
<p>Marty;<br /> I have been experiencing some troble with my keyboard. It appears that so<br />sometimes when I first turn on my machine that the right arrow key will<br />not work for a while and also I am not able to do a shift-cntrl/break<br /> function until the machine has been on for awhile then everything appears<br /> to work fine.  Could this be caused by a weak PIA (IC5) chip? or is it<br />a lead to something else.<br />   Don</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/07/pia/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>scsi system</title>
		<link>http://www.coco3.com/community/1994/06/scsi-system</link>
		<comments>http://www.coco3.com/community/1994/06/scsi-system#comments</comments>
		<pubDate>Sun, 26 Jun 1994 03:36:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/06/scsi-system/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88216 26-JUN 03:36 System Modules (6809)<br />     scsi system<br />     From: JBMANNING    To: ALL</p>
<p>Hello</p>
<p>I would like to know who is handling SCSISYS by Matthew Thompson.<br />about a year ago or so I sent my $22 dollars in to register my copy.<br />and have recieved a couple of updates through delphi after being a pest.<br />but have never recieved any thing official ie documention and disks in the<br />mail saying that I had the official registered version.</p>
<p>My user name on delphi was JIMBM but I had to cancel my delphi account<br />during the first 5 month of 94. I have opened a new acount under<br />JBMANNING which may be part of the problem.</p>
<p>ident on my version shows</p>
<p>Header for:  SCSISYS<br />Module size: $05F8    #1528<br />Module CRC:  $AC2F3E (Good)<br />Hdr parity:  $26<br />Exec. off:   $0016    #22<br />Data Size:   $028F    #655<br />Edition:     $00      #0<br />Ty/La At/Rv: $E1 $81<br />Dev Dvr mod, 6809 obj, re-en, R/O</p>
<p>is this up to date?  and how can I get full documentaion?</p>
<p>one more thing accelarated handshaking works with my drive (st277n)<br />but I can&#8217;t get cacheing to work no matter which order I arrange<br />modules. after I enable caching my doing a<br />dmode /h0 dns=80 and<br />type dir /h0 I get weird characters on the screen.<br />the docs I have say the cache uses $C000 to $DFFF in the<br />system map.  when I do an dirm this is the same as block 1, right?<br />or am I mistaken? can I enable cacheing after I boot?</p>
<p>after the last boot I tried dirm shows</p>
<p> Bk  Ofst  Size  Ty  At  Link  Module Name<br /> &#8212;  &#8212;-  &#8212;-  &#8212;  &#8212;  &#8212;-  &#8212;&#8212;&#8212;&#8211;<br />-3F   D06   12A  C1  81     0  REL<br /> 3F   E30   1D0  C1  81     1  Boot<br /> 3F  1000   ED9  C0  88     0  OS9p1<br />- 1  1300   CA4  C0  82     1  OS9p2<br />  1  1FA4    34  C0  81     1  Init<br />  1  1FD8   140  C1  81     1  OS9p3<br />  2   118    20  F1  81     1  Nil<br />  2   138   1FB  E1  81     1  VRN<br />  2   333    95  E1  81     0  Parallel<br />  2   3C8    3E  F1  81     0  P<br />  2   406   219  D1  81     0  PipeMan<br />  2   61F    28  E1  81     0  Piper<br />  2   647    26  F1  81     0  Pipe<br />  2   66D   24D  C1  83     1  Clock<br />  2   8BA   5B6  E1  81     1  AciaDrv<br />  2   E70    4B  F1  81     1  T2<br />  2   EBB   9F3  C1  81     1  IOMan<br />  2  18AE  1D4B  C1  81     1  WindInt<br />  3  15F9    46  F1  81     4  TERM<br />  3  163F    43  F1  81     0  W<br />  3  1682    44  F1  81     3  W1<br />  3  16C6    44  F1  81     0  W2<br />  3  170A    44  F1  81     0  W3<br />  3  174E    44  F1  81     0  W4<br />  3  1792    43  F1  81     3  W5<br />  3  17D5    44  F1  81     0  W6<br />  3  1819    44  F1  81     0  W7<br />  3  185D    44  F1  81     0  W8<br />  3  18A1    44  F1  81     0  W9<br />  3  18E5    45  F1  81     0  W10<br />  3  192A    45  F1  81     0  W11<br />  3  196F    45  F1  81     0  W12<br />  3  19B4    45  F1  81     0  W13<br />  3  19F9    45  F1  81     0  W14<br />  3  1A3E    45  F1  81     0  W15<br />  3  1A83  12CB  D1  81     6  RBF<br />  4   D4E   4EA  E1  82     2  CC3Disk<br />  4  1238    30  F1  81     1  D0<br />  4  1268    30  F1  81     1  D1<br />  4  1298   6DA  D1  82     C  SCF<br />  4  1972   C64  E1  81     A  CC3IO<br /> 3F   5D6   5F8  E1  81    4B  SCSISYS<br /> 3F   BCE    31  F1  89     0  H0<br /> 3F   BFF    31  F1  89    4B  DD<br />- 6     0  1FBB  C1  81     1  GrfDrv<br />- A     0   1A7  11  81     1  DirM<br />- 9     0  18B3  11  82     4  Shell<br />  9  18B3    24  11  81     0  Load<br />  9  18D7    22  11  81     0  Echo<br />  9  18F9    27  11  81     0  Prompt<br />  9  1920    68  11  81     0  Merge<br />  9  1988    4F  11  81     0  List<br />  9  19D7    22  11  81     0  Makdir<br />  9  19F9    A5  11  81     0  Del<br />  9  1A9E    84  11  81     0  Display<br />  9  1B22    7A  11  81     0  Iniz<br />  9  1B9C    27  11  81     0  cls<br />  9  1BC3   15C  11  81     0  Rename<br />-10     0  2156  11  81     1  mcron<br />-13     0  591D  11  81     1  scred</p>
<p>Thanks for your time</p>
<p>Jim Manning</p>
<p>Delphi JBMANNING<br />internet jbmannin@Endor.es.sim.com</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/06/scsi-system/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RBF32</title>
		<link>http://www.coco3.com/community/1994/06/rbf32</link>
		<comments>http://www.coco3.com/community/1994/06/rbf32#comments</comments>
		<pubDate>Sun, 26 Jun 1994 00:28:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/06/rbf32/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88212 26-JUN 00:28 System Modules (6809)<br />     RBF32<br />     From: VE3DAC       To: WDTV5 (NR)</p>
<p>Gene Krenciglowa tried out RBF32 on his Powerboost 2.03  and it won&#8217;t boot<br />with your RBF. I&#8217;ll get his message onto floppy and see if I can get it to<br />you in mail.<br />   I used to do that, no problem,  but the last couple of times when the        <br />        CR<br />at the end of the line is sent, Delphi stops accepting the message. We&#8217;ll see<br />what happens tomorrow afternoon.<br />   I booted up with one of my old Nitro disks, and the Nitro RBF is a version<br />of RBF30.  Maybe you missed it in version 1.15.  But I was able to Undel a<br />file, I just forgot until I tried it. Now I don&#8217;t know which RBF to use, I&#8217;m<br />loyal to my hacker pals, <g>.<br />  Look for further, Sun night.<br />Merv</p>
<p></g></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/06/rbf32/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Gene&#8217;s Ramdisk</title>
		<link>http://www.coco3.com/community/1994/06/genes-ramdisk</link>
		<comments>http://www.coco3.com/community/1994/06/genes-ramdisk#comments</comments>
		<pubDate>Fri, 24 Jun 1994 01:09:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/06/genes-ramdisk/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88178 24-JUN 01:09 System Modules (6809)<br />         Gene&#8217;s Ramdisk<br />     From: VE3DAC       To: WDTV5</p>
<p>With all that information I am now using &#8216;myram&#8217;.  Now to update my<br />various other boot disks. Sure is going to be strange losing my old pal<br />&#8216;Rammer&#8217;. It goes back to my starting with Lev 2, one of the few unmodified<br />things over all those years.  It is nice being able to change the R0 to do<br />a large unarc and then pop back to the standard 130K.  Thanks for the<br />Ramdisk and extra help updating my knowledge.<br />Cheers<br />Merv</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/06/genes-ramdisk/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RBF32</title>
		<link>http://www.coco3.com/community/1994/06/rbf32-2</link>
		<comments>http://www.coco3.com/community/1994/06/rbf32-2#comments</comments>
		<pubDate>Wed, 22 Jun 1994 00:34:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/06/rbf32-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88139 22-JUN 00:34 System Modules (6809)<br />     RBF32<br />     From: VE3DAC       To: WDTV5</p>
<p>Got RBF32.mn created just fine. I have tested LHA and Undel, both are ok.<br />Maybe you should just bundle the docs from rbf31_2_32, with the new .ipc<br />and have that available here.  We must all have the original RBF so I think<br />anks for the extra work creating the new .ipc.<br />Cheerio<br />Merv</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/06/rbf32-2/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>rbf32 revisited</title>
		<link>http://www.coco3.com/community/1994/06/rbf32-revisited</link>
		<comments>http://www.coco3.com/community/1994/06/rbf32-revisited#comments</comments>
		<pubDate>Sun, 19 Jun 1994 18:03:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/06/rbf32-revisited/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88085 19-JUN 18:03 System Modules (6809)<br />     rbf32 revisited<br />     From: WDTV5        To: ALL</p>
<p>Hello everyone; It appears I have a problem thats bit me on a couple of<br />occassions. I&#8217;ve made up an .ipc file to patch what I thought was the<br />version of RBF.mn that everyone whose system has had the Nitros-9 touch<br />should have been using.</p>
<p>Yes, and no. I&#8217;m finding that 1.115/1.116 Nitros9 seems to be different for<br />each user. If it had been only the crc that was different, I could possibly<br />say that &#8220;Well, I changed the at/rv &#038; ty/lg in mine so its properly<br />identified as native mode, 6309 code by &#8220;vfy&#8221;. I could. But then what do I<br />do when the 1.15 someone else has is nearly $B0 bytes longer than mine?</p>
<p>Sooo, the next upload of the .ipc to make RBF.mn edition #32 will be based<br />on the original edition #28 from my distribution disk.  As will any other<br />updates of system modules that I manage to do. Maybe this will ease the<br />confusion factor involved in trying to track upgrades. Since I&#8217;m Nitro&#8217;d<br />here, that means I&#8217;ll be crossing the border that divides nitros-9 from<br />os-9. At this point, the hassle factor has me in an I don&#8217;t care mode.<br />I&#8217;m sorry if that offends either Chris or Wes &#038; Co. Each of us is in it far<br />more for the love of the system than for any prospects of making any money<br />on it anyway, plus the copyrights are MicroWares, not Burke &#038; Burke, Gales<br />Force Enterprises, or mine.</p>
<p>There should be a side benefit too, pboost users should be able to use it<br />too.</p>
<p>Cheers all, Gene</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/06/rbf32-revisited/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: RAMDISK -New version Re: Msg 87861</title>
		<link>http://www.coco3.com/community/1994/06/re-ramdisk-new-version-re-msg-87861</link>
		<comments>http://www.coco3.com/community/1994/06/re-ramdisk-new-version-re-msg-87861#comments</comments>
		<pubDate>Sat, 18 Jun 1994 15:04:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/06/re-ramdisk-new-version-re-msg-87861/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>88035 18-JUN 15:04 System Modules (6809)<br />     RE: RAMDISK -New version (Re: Msg 87861)<br />     From: NEALSTEWARD  To: WDTV5</p>
<p>I&#8217;ll d/l it and give it a try on my system.  If it&#8217;s going to crash, it<br />will because my computer is real skitzoid!  Intermittant problems that<br />occur for no apparent reason, but seem to pop up when using a RAMdisk.<br />If it passes here, you have a winner&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/06/re-ramdisk-new-version-re-msg-87861/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NitrOS9 v1.20</title>
		<link>http://www.coco3.com/community/1994/06/nitros9-v1-20</link>
		<comments>http://www.coco3.com/community/1994/06/nitros9-v1-20#comments</comments>
		<pubDate>Tue, 14 Jun 1994 02:17:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/06/nitros9-v1-20/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87934 14-JUN 02:17 System Modules (6809)<br />     NitrOS9 v1.20<br />     From: BRIANOHAGAN  To: ALL</p>
<p>Just thought I would pass along the following from Fidonet:</p>
<p>Message No. 106 was left on 06-08-94 13:57:57<br />To&#8230;&#8230;.  : Brian O&#8217;Hagan<br />From&#8230;..  : Colin Mckay<br />Subject..  : Re: NitrOS9<br />Message Conference #37 &#8220;CoCo OS9 (National Conference)&#8221;</p>
<p>> So how does one contact Bill and Curtis in order to purchase Nitros9?</p>
<p>Bill and/or Curtis should be making an announcement here some time this<br />week regarding the status of NitrOS-9.</p>
<p>Summed up briefly, v1.20 is scheduled for release around mid-July, and you<br />should wait until then before purchase, as the price has been lowered.</p>
<p>If you need further information, you can contact me at (613)736-0329.</p>
<p>Those who already own NitrOS-9 should also wait for the announcement.</p>
<p>TTYL. Colin.</p>
<p>Colin McKay             | Abandon every hope, ye who enter here.<br />Northern Xposure        | Dante (1265-1321) &#8216;Inferno&#8217;, Canto iii<br />cmckay@northx.isis.org  | ( Inscription  over the gate to Hell )</p>
<p>&#8212; Maximus-CBCS v1.02<br /> * Origin: Micro80 Computer Club of Ottawa BBS (1:163/306)</p>
<p>Message No. 100 was left on 06-07-94 20:10:35<br />To&#8230;&#8230;.  : Brian O&#8217;Hagan<br />From&#8230;..  : Curtis Boyle<br />Subject..  : Re: NitrOS9<br />Message Conference #37 &#8220;CoCo OS9 (National Conference)&#8221;</p>
<p>  You can contact either one of us here on FidoNet, or you can write to us at:</p>
<p>Curtis Boyle or Bill Nobel<br />Mercury Graphics Corporation<br />1438 Fletcher Road<br />Saskatoon, SK<br />Canada<br />S7M 5T2</p>
<p>   Maybe put a RE: NitrOS9 on the address as well so Bill or I can tell if it<br />is regular work business or NitrOS9 related (our work is letting us use their<br />address for correspondence, since one of us is bound to be their every<br />weekday. Prevents letters from getting locked up for a couple of weeks if one<br />of us is on vacation).<br />   For dire emergencies, you can call us (by name) at work too, but don&#8217;t do<br />it too often, as our work doesn&#8217;t want to pay us for doing support for a<br />product that they have nothing to do with (except for printing our manuals at<br />a good price). The number there is (306)-384-8000.<br />    In the evenings, you can call me (306)-384-4722 or Bill (306)-978-0834 at<br />home.<br />    We will have some distributors soon for the new Version 1.20 release, as<br />well as our new upgrade/purchase policy, hopefully by the end of June, work<br />schedules permitting. We were pretty busy after getting back from the Fest,<br />and finally had time to print some manuals (V1.15/16) for backorders this<br />afternoon, so we haven&#8217;t had too much time to do much with NitrOS9. We should<br />get the manuals mailed out to individuals waiting for them by the end of the<br />week, and then start doing some bug-hunting/last minute updates &#038; the new<br />manual after that. We will keep you posted as to our progress on this echo. If<br />anyone with Delphi/Internet/Compu$erve access can pass this info along, please<br />do&#8230;I don&#8217;t have access to most of it anymore.</p>
<p>&#8212; Opus-CBCS 1.73a<br /> * Origin: The North Village OPUS, 14.4, OS/2, (306)384-0836 (1:140/26.0)</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/06/nitros9-v1-20/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VDGINT/2 meg</title>
		<link>http://www.coco3.com/community/1994/06/vdgint2-meg</link>
		<comments>http://www.coco3.com/community/1994/06/vdgint2-meg#comments</comments>
		<pubDate>Thu, 09 Jun 1994 08:33:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/06/vdgint2-meg/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87835 9-JUN 08:33  System Modules (6809)<br />     VDGINT/2 meg<br />     From: DONALDS      To: ALL</p>
<p>Has there been any break-through on getting the new reduced size VDGINT module<br />to work with the 2meg upgrade? I know Alan had redone it and it was still in<br />beta testing. Just wondering if any conculusion made on it.<br />           Don</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/06/vdgint2-meg/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PC Floppy Formatter</title>
		<link>http://www.coco3.com/community/1994/06/pc-floppy-formatter</link>
		<comments>http://www.coco3.com/community/1994/06/pc-floppy-formatter#comments</comments>
		<pubDate>Wed, 08 Jun 1994 02:47:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/06/pc-floppy-formatter/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87824 8-JUN 02:47  System Modules (6809)<br />     PC Floppy Formatter<br />     From: TAFOID       To: ALL</p>
<p>Hi!</p>
<p>     I have been looking for a modules to allow a 5.25&#8243; disk to be formatted<br />for use on the IBM.  I have looked throughly through the System Modules<br />database, with no success.</p>
<p>If anyone has one, could you email me a copy?</p>
<p>Thanks much,<br />Scott</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/06/pc-floppy-formatter/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Ramdisk</title>
		<link>http://www.coco3.com/community/1994/05/ramdisk-5</link>
		<comments>http://www.coco3.com/community/1994/05/ramdisk-5#comments</comments>
		<pubDate>Mon, 30 May 1994 20:42:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/05/ramdisk-5/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87651 30-MAY 20:42 System Modules (6809)<br />     Ramdisk<br />     From: WDTV5        To: ALL</p>
<p>I&#8217;m in the middle of doing a fresh ramdisk for the os-9&#8242;ers, based VERY<br />loosely on the devpack version but capable of useing ram up to the amount<br />in the machine even if its a 2 megger!<br />I started on this because the compiler chokes if /r0 isn&#8217;t iniz&#8217;ed first,<br />thinking that was a bug. Well it is and it isn&#8217;t. OS-9 is doing that to<br />us as it does its own &#8220;iniz&#8221; on the module if it hasn&#8217;t been already,<br />then allows the write of a file to the ramdisk without reporting any<br />errors.  Unforch, if it self initialized it, it also de-inits it at the<br />end of the write! So the file is lost, and c.pass1 (ansifront) can&#8217;t<br />find the output from c.prep. I want to stop that, effectivly making the<br />ramdisk refuse to deinit if the directory isn&#8217;t empty. I&#8217;m torn between<br />using the regular error paths to report it, or just outputting the<br />phrase &#8220;the root dir isn&#8217;t empty&#8221; on stderr. If I use an error number,<br />then the compiler and other progs will probably choke on it anyway when<br />in fact they could keep on truckin! So I need some input, what do tou<br />all (you) want it to do. The choices are to ignore it without errors, and<br />let you folks learn to delete all files before deiniting, haveing an<br />error mesage pop up at odd times, or returning a process killing error.<br />What&#8217;ll it be folks?<br />Cheers all, Gene</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/05/ramdisk-5/feed</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Ramdisk problems</title>
		<link>http://www.coco3.com/community/1994/05/ramdisk-problems</link>
		<comments>http://www.coco3.com/community/1994/05/ramdisk-problems#comments</comments>
		<pubDate>Mon, 23 May 1994 21:28:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/05/ramdisk-problems/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87507 23-MAY 21:28 System Modules (6809)<br />     Ramdisk problems<br />     From: JRUPPEL      To: ALL</p>
<p>Has anyone had any problems with the R0_720K ramdisk found here in the database<br />running a 2-meg? Ever since I upgraded I get an error 241-Sector Error when I<br />use diskcopy to copy to it. I also have a 6309 and Powerboost.<br />BTW, the Fest was a GAS!</p>
<p>John Ruppel</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/05/ramdisk-problems/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>New Drivers Disk</title>
		<link>http://www.coco3.com/community/1994/05/new-drivers-disk</link>
		<comments>http://www.coco3.com/community/1994/05/new-drivers-disk#comments</comments>
		<pubDate>Thu, 12 May 1994 01:30:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/05/new-drivers-disk/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87292 12-MAY 01:30 System Modules (6809)<br />     New Drivers Disk<br />     From: DIETER       To: NIMITZ (NR)</p>
<p>Have received the New Drivers Upgrade disk today!  Thanks!</p>
<p>Got one heck of a supprise from Canada Customes, since the sender (I assume it<br />was You, decleared the contend of the package to be $ 100.00 worth)  So I had<br />to pay $ 14.95 Goods and Services Tax on to of it,  So I that package really is<br />$ 100.00 bucks wort<br />h, I ow You some more money, if Not!  Please send me a receipt stating how much<br />the disk was really worth, and an explanation as to how and way thew mistake<br />was made&#8230;</p>
<p>Or maybe Canada Customes has You on its payroll&#8230;  Grin!!!!</p>
<p>Dieter!</p>
<p>                       Dieter</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/05/new-drivers-disk/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>BootMods Upgrade</title>
		<link>http://www.coco3.com/community/1994/05/bootmods-upgrade</link>
		<comments>http://www.coco3.com/community/1994/05/bootmods-upgrade#comments</comments>
		<pubDate>Thu, 12 May 1994 01:30:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/05/bootmods-upgrade/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87293 12-MAY 01:30 System Modules (6809)<br />     BootMods Upgrade<br />     From: DIETER       To: NIMITZ (NR)</p>
<p>The BootMods disk that You send me, are they for the MM/1a (68340 CPU), or just<br />for the 68070 cpu?  please let me know as soon as possible, thanks!</p>
<p>Dieter</p>
<p>                       Dieter</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/05/bootmods-upgrade/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Merging files</title>
		<link>http://www.coco3.com/community/1994/05/merging-files</link>
		<comments>http://www.coco3.com/community/1994/05/merging-files#comments</comments>
		<pubDate>Sat, 07 May 1994 00:15:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/05/merging-files/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87203 7-MAY 00:15  System Modules (6809)<br />     Merging files<br />     From: CHARLESAM    To: RANDYKWILSON (NR)</p>
<p>Randy, since os9 stores in 8k blocks, and SC (my version) is 17861 in size,<br />that would mean SC would occupy 23040 or 3 8k blks. Since the space is there,<br />could I merge a few commands in with SC and save paying rent. For that matter<br />would it work with other applications??? My startup file is working fine now,<br />but I don&#8217;t have much memory left after Dynastar, Supercomm, and Presto-Partner<br />get theirs. I also have an empty text window besides term. Memory left is<br />20 blks or 160k. Sys memory is 56 pgs or 14k. Thanx Charlie</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/05/merging-files/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Dynacalc problem</title>
		<link>http://www.coco3.com/community/1994/04/dynacalc-problem</link>
		<comments>http://www.coco3.com/community/1994/04/dynacalc-problem#comments</comments>
		<pubDate>Wed, 27 Apr 1994 20:21:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/04/dynacalc-problem/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87031 27-APR 20:21 System Modules (6809)<br />     Dynacalc problem<br />     From: MIKE_GUZZI   To: ALL</p>
<p>I have upgraded to Nitros9 awhile back and now dynacalc crashes the computer<br />i confirmed its nitros by booting up to a normal os9 disk and it works fine</p>
<p>anyone else have this problem or better yet a solution??</p>
<p>Mike</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/04/dynacalc-problem/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>seral mouse is coool!</title>
		<link>http://www.coco3.com/community/1994/04/seral-mouse-is-coool</link>
		<comments>http://www.coco3.com/community/1994/04/seral-mouse-is-coool#comments</comments>
		<pubDate>Mon, 25 Apr 1994 01:17:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/04/seral-mouse-is-coool/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87005 25-APR 01:17 System Modules (6809)<br />     seral mouse is coool!<br />     From: MDALENE      To: ALL</p>
<p>I finaly got a serial mouse for my coco 3,. Using Bruceisteds driers it<br />flies! but I have a questio. Somethings such as games would be beter operated<br />with a joystick. How ccan I use both the mouse for gshell as well as my<br />hires interfacce simotaniously for games that need my deluxe joystick/<br />Is there a patch I can do to the new cc3io so I can have both?// Also<br />althougn my mouse is both Logitec,mousesystems and microsoft compatible<br />could a patcch be made to thew new cc3io that would let me change windows<br />with my third mouse button? if so how? I have the smouse.ar package and<br />its source whicch I think is also in esw110.ar (Thats where I got mine)<br />so asm sources of patcching is not that hard to do if I must do it by<br />sourcecode to add those funchions I ddesire.<br />        My mouse is a procorp mouse II with support of 6400 DPI! works<br />super on gshell.. not sure if I want to play Rescue on fractalis with a<br />mouse though. it would drivve me crazy! a trackball&#8230;..? that would do!<br />        also wherre can I get the information on how to write programs<br />in decb to use it? I need the specs. who has those/<br />                                        Michele Marie Dalene</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/04/seral-mouse-is-coool/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>clocks</title>
		<link>http://www.coco3.com/community/1994/04/clocks</link>
		<comments>http://www.coco3.com/community/1994/04/clocks#comments</comments>
		<pubDate>Sun, 24 Apr 1994 23:01:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/04/clocks/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>87004 24-APR 23:01 System Modules (6809)<br />     clocks<br />     From: WDTV5        To: ALL</p>
<p>I just had a pleasant surprise! My speed record up to now for an sz file<br />send when hooked at 14.4v42, has been in the 535-539 area. I just sent a<br />43k compressed file to another local Amiga user and it went at 614 cps,<br />a noticable improvement, directly attributable to the reduced time my new<br />clock spends checking things at its tick time.  This intrigues me, and<br />I may see if there is anything else I can do to speed it up even more.<br />In the meantime, if you are a 4n1 user and run in the native mode, give<br />this clock a try once Paul makes it visible. Cheers all, Gene</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/04/clocks/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UnDel</title>
		<link>http://www.coco3.com/community/1994/04/undel</link>
		<comments>http://www.coco3.com/community/1994/04/undel#comments</comments>
		<pubDate>Mon, 04 Apr 1994 00:07:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/04/undel/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>86637 4-APR 00:07  System Modules (6809)<br />     UnDel<br />     From: WDTV5        To: ALL</p>
<p>Has anybody else noticed, and who is running NITROS-9, that UnDel doesn&#8217;t<br />work anymore?  Apparently Wes &#038; Company must have used ed 28 of RBF as the<br />model for the NATIVE mode RBF ed31 now shipping. Its the last one I have<br />anyway.</p>
<p>I beleive I have an ed32 of RBF.mn that actually works again, one slight<br />problem earlier this evening but found a place where the FAT was being<br />manipulated and I had plugged in the wrong setof bit shifters from the<br />native mode repertory. s/b fixed now.</p>
<p>Now, what I want is beta testers. I will email the .ipc file only, with<br />instructs to go with, that way I don&#8217;t step on too many toes. This is how<br />I will upload it eventually also.  Anybody with a 63B09 equipt coco3<br />currently using NITROS-9 s/b able to use it, but no one else.</p>
<p>Its in memory right now here, getting its first taste of beta testing on<br />my own system.</p>
<p>Cheers, Gene Heskett, WDTV5@delphi.com</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/04/undel/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>25 line GrfDrv patch</title>
		<link>http://www.coco3.com/community/1994/03/25-line-grfdrv-patch</link>
		<comments>http://www.coco3.com/community/1994/03/25-line-grfdrv-patch#comments</comments>
		<pubDate>Mon, 28 Mar 1994 20:19:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/03/25-line-grfdrv-patch/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>86549 28-MAR 20:19 System Modules (6809)<br />     25 line GrfDrv patch<br />     From: DENNYWRIGHT  To: ALL</p>
<p>I have patched my window descriptors for the 25 line grfdrv but when I iniz<br />them and fork a shell to them they<br />appear as 24 line windows! Why? Can anyone tell me or do I have to wcreate the<br />windows each time?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/03/25-line-grfdrv-patch/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SCSI SYS 1.0</title>
		<link>http://www.coco3.com/community/1994/03/scsi-sys-1-0</link>
		<comments>http://www.coco3.com/community/1994/03/scsi-sys-1-0#comments</comments>
		<pubDate>Tue, 22 Mar 1994 21:49:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/03/scsi-sys-1-0/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>86465 22-MAR 21:49 System Modules (6809)<br />     SCSI SYS 1.0<br />     From: DIETER       To: MATHOMPSON (NR)</p>
<p>Hi Matthew, I have send of a letter to Your Company (HardSoft) to register my<br />SCSISYS driver 1.0 also have included a cheque for $25 Dollars.</p>
<p>Am very impressed with the speed increase on my DISTO 4in1 setup, it is just my<br />spare rig, but I like it to have the best drivers, thanks!</p>
<p>Can You also send me a list of all the products You sell&#8230;</p>
<p>G&#8217;Day!</p>
<p>                       Dieter</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/03/scsi-sys-1-0/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Grfdrv Patch</title>
		<link>http://www.coco3.com/community/1994/03/grfdrv-patch</link>
		<comments>http://www.coco3.com/community/1994/03/grfdrv-patch#comments</comments>
		<pubDate>Tue, 15 Mar 1994 19:55:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/03/grfdrv-patch/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>86273 15-MAR 19:55 System Modules (6809)<br />     Grfdrv Patch<br />     From: DENNYWRIGHT  To: ALL</p>
<p>I applied the 25 line grfdrv patch but I was wondering if anyone can tell me how</p>
<p>to patch the window descriptors so that they are 25 lines. Or do I have to<br />wcreate the windows with 25 lines?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/03/grfdrv-patch/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>SMALL VDGINT</title>
		<link>http://www.coco3.com/community/1994/03/small-vdgint</link>
		<comments>http://www.coco3.com/community/1994/03/small-vdgint#comments</comments>
		<pubDate>Mon, 07 Mar 1994 08:51:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/03/small-vdgint/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>86088 7-MAR 08:51  System Modules (6809)<br />     SMALL VDGINT<br />     From: DONALDS      To: ALL</p>
<p>I read somewhere that Alan Dekok had made new VDGINT files that would<br />work with the Disto 2meg upgrade; Does anyone know where he has uploaded<br />these files to? I have the ones he first made but need the new ones to<br />work with my upgrade.<br />          Don</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/03/small-vdgint/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: SCSISYS v1.0/2.2 Re: Msg 85937</title>
		<link>http://www.coco3.com/community/1994/02/re-scsisys-v1-02-2-re-msg-85937</link>
		<comments>http://www.coco3.com/community/1994/02/re-scsisys-v1-02-2-re-msg-85937#comments</comments>
		<pubDate>Sun, 27 Feb 1994 08:40:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/re-scsisys-v1-02-2-re-msg-85937/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85939 27-FEB 08:40 System Modules (6809)<br />     RE: SCSISYS v1.0/2.2 (Re: Msg 85937)<br />     From: DONALDS      To: KSCALES</p>
<p>Thanks ken. I didn&#8217;t see what happened to my message until I had logged<br />off. The  general question I had for him was I can use both of my ST277n<br />drives under scsisys1.0 but when I switch to scsisys2.2 I can only use<br />the drive that was refurb&#8217;ed the other one I can do a scsifmt with<br />scsifmt2.2 but it will not use the 2.2 driver to do a logical format.<br />where I can do both with 1.0 driver and scsifmt.<br /> Don</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/re-scsisys-v1-02-2-re-msg-85937/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SCSISYS v1.0/2.2</title>
		<link>http://www.coco3.com/community/1994/02/scsisys-v1-02-2</link>
		<comments>http://www.coco3.com/community/1994/02/scsisys-v1-02-2#comments</comments>
		<pubDate>Fri, 25 Feb 1994 23:22:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/scsisys-v1-02-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85904 25-FEB 23:22 System Modules (6809)<br />     SCSISYS v1.0/2.2<br />     From: KSCALES      To: DONALDS</p>
<p> > Leave a message to COLIN MCKAY (I&#8217;m not sure if that is his user name or<br /> > not, no space between names). He sales Matt&#8217;s drivers (commercial<br /> > version).</p>
<p>Colin isn&#8217;t active on Delphi, but does frequent the CoCo, OS-9, and<br />MM1_Tech echos on Fido, as well as the Princeton CoCo list.  (There are<br />just too many active forums to keep up <img src='http://www.coco3.com/community/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />   So Colin follows those<br />groups, and I try to monitor this forum and the CIS OS-9 area, and we<br />keep each other informed of the highlights.</p>
<p>So, you can reach Colin through me, or you can contact him directly through<br />Delphi Internet mail at IN%&#8221;cmckay@UUISIS.ISIS.ORG&#8221;.</p>
<p> &#8230; / Ken<br /> &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br /> Ken Scales   Delphi:KSCALES   Internet:kscales@delphi.com   CIS:74646,2237</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/scsisys-v1-02-2/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SCSISYS v1.0/2.2</title>
		<link>http://www.coco3.com/community/1994/02/scsisys-v1-02-2-2</link>
		<comments>http://www.coco3.com/community/1994/02/scsisys-v1-02-2-2#comments</comments>
		<pubDate>Wed, 23 Feb 1994 09:44:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/scsisys-v1-02-2-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85837 23-FEB 09:44 System Modules (6809)<br />     SCSISYS v1.0/2.2<br />     From: DONALDS      To: ALL</p>
<p>I am looking for someone that is running 2 ST-XXXn drives with Matt Thompson<br /> new drivers. I am running 2 &#8211; ST277n drives with the version 1.0 drivers.<br />I got the version 2.2 drivers. I was able to make discriptors for drive 0<br /> and update to version 2.2. I maded discriptors for the second drive. did<br />a PHYISICAL (low level) format OK then; when I went to do a LOGICAL format<br />the lite would flicker a bit then just stay lite; after a 1/2 hour I shut<br /> it off. Now with version 1.0 after several formats (PHYS and LOGIC) I am<br />able to use both drives. But; I tried version 2.2 again but when I do a<br />dir on drive 1 the lite comes on and just hangs there. Logical format is<br />the same lite will flicker then hang there. Does anyone have a idea as to<br />why this is happening.<br />      Don</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/scsisys-v1-02-2-2/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Nitro.Help</title>
		<link>http://www.coco3.com/community/1994/02/nitro-help</link>
		<comments>http://www.coco3.com/community/1994/02/nitro-help#comments</comments>
		<pubDate>Mon, 21 Feb 1994 23:52:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/nitro-help/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85803 21-FEB 23:52 System Modules (6809)<br />     Nitro.Help<br />     From: REVWCP       To: ALL</p>
<p>Dear friends:<br />I am attempting to install Nitro9 v.115 and have run into a problem.  I<br />am using the Module by Module patch method.  Everything patched okay.  I<br />then attempted to use the following command:<br />        kwikboot -G=kernel.nv115 -f=/d0</p>
<p>It first activates /d1 and finds the file, it then accesses /d0.  Next I<br />get an error message stating that the file already exists.  It does on /d1,<br />but not on /d0 where it needs to go.  This appears to be an error in the<br />documentation.  I tried call the phone number for GaleForce 1-604-589-1660,<br /> but I never get an answer. From 8am &#8211; 5 pm pst it is supposed to be a<br />voice line,  At 5 pm &#8211; 8 am a BBS.  Wes Gale was last on delphi on 2/7/94.<br />Any help in :<br />        1. Getting Nitro running<br />        2. Getting in touch with Wes Gale<br />would be greatly appreciated.<br />With all best wishes,<br />Brother Jeremy, CSJW<br />OS9 User&#8217;s Group Treasurer</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/nitro-help/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: new 4in1 Re: Msg 85594</title>
		<link>http://www.coco3.com/community/1994/02/re-new-4in1-re-msg-85594</link>
		<comments>http://www.coco3.com/community/1994/02/re-new-4in1-re-msg-85594#comments</comments>
		<pubDate>Sat, 19 Feb 1994 21:29:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/re-new-4in1-re-msg-85594/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85709 19-FEB 21:29 System Modules (6809)<br />     RE: new 4in1 (Re: Msg 85594)<br />     From: SFISCHER     To: WTHOMPSON</p>
<p> By binary mail I am sending WTHOMPSON an AR file of the DECB program that<br /> I used to try and format my ST157N for 256 byte sector use.<br /> About 785 lines which did everything but format the drive for 256<br /> byte sectors. Also may be usefull on other SCSI drives.</p>
<p> I NEVER got the drive to use 256 Byte sectors.<br /> SEAGATE had to reload the firmware before any use on OS9.</p>
<p> Check the parity jumper on the drive and the SCSI ID.</p>
<p> If you get to any response from the drive,<br /> use SCSISys 1.0 and 512 Byte sectors.</p>
<p> Make note of the number of times the LED flashes,<br /> My ST157N drive now flashes eight times.<br /> The controller is unable to read the operating system<br /> off the drive. (TOO much oil put into the drive in a<br /> failed attempt to get the drive to rotate with out a crank).</p>
<p> SHF</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/re-new-4in1-re-msg-85594/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: new 4in1 Re: Msg 85594</title>
		<link>http://www.coco3.com/community/1994/02/re-new-4in1-re-msg-85594-2</link>
		<comments>http://www.coco3.com/community/1994/02/re-new-4in1-re-msg-85594-2#comments</comments>
		<pubDate>Sun, 13 Feb 1994 02:08:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/re-new-4in1-re-msg-85594-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85608 13-FEB 02:08 System Modules (6809)<br />     RE: new 4in1 (Re: Msg 85594)<br />    .. the co. who built it in the first<br />place!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/re-new-4in1-re-msg-85594-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>4in1 problems</title>
		<link>http://www.coco3.com/community/1994/02/4in1-problems</link>
		<comments>http://www.coco3.com/community/1994/02/4in1-problems#comments</comments>
		<pubDate>Sat, 12 Feb 1994 23:18:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/4in1-problems/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85606 12-FEB 23:18 System Modules (6809)<br />     4in1 problems<br />     From: WTHOMPSON    To: ALL</p>
<p>  Someone on fido told me how to make the scsi drive cable correctly<br />but after correcting that I STILL get no response fron the hard drive.<br />One question: who out there has a 4in1/sc2 on their coco3 with the<br />6309 cpu?  I am wonderPO  To: COCOKIWI</p>
<p>I have a Seagate 157n.  I&#8217;m pretty sure that has the contoller on it.<br />As far as 256/512 byte sectors, I am using the scsisys so I want to go to<br />512 sectors but the 157n is capable of both.<br /> Thanks,<br /> Wayne</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/4in1-problems/feed</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>RE:         Disto/Ken-Ton Clash Re: Msg 85233</title>
		<link>http://www.coco3.com/community/1994/02/re-distoken-ton-clash-re-msg-85233</link>
		<comments>http://www.coco3.com/community/1994/02/re-distoken-ton-clash-re-msg-85233#comments</comments>
		<pubDate>Fri, 11 Feb 1994 22:52:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/re-distoken-ton-clash-re-msg-85233/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85577 11-FEB 22:52 System Modules (6809)<br />     RE:         Disto/Ken-Ton Clash (Re: Msg 85233)<br />     From: MODEL299     To: COCOKIWI</p>
<p>Been a while since I logged on to reply to your last message.  If I have good<br />information on the ken-ton addresses iti can be FF74 or FF70.  I believe<br />those are the selectable addresses.   Mark</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/re-distoken-ton-clash-re-msg-85233/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SCII drivers</title>
		<link>http://www.coco3.com/community/1994/02/scii-drivers</link>
		<comments>http://www.coco3.com/community/1994/02/scii-drivers#comments</comments>
		<pubDate>Tue, 08 Feb 1994 22:56:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/scii-drivers/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85534 8-FEB 22:56  System Modules (6809)<br />     SCII drivers<br />     From: NEALSTEWARD  To: DISTO (NR)</p>
<p>Are there other versions of the drivers for the Super Controller II<br />available?  The reason I ask is when I run B&#038;B&#8217;s tuneup command to<br />powerboost my system for the 6309, it reports that it can&#8217;t match the<br />SCII modules.  I use the .slp versions because I&#8217;ve had no luck with<br />boots using the .irq versions.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/scii-drivers/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>iniz /d0</title>
		<link>http://www.coco3.com/community/1994/02/iniz-d0</link>
		<comments>http://www.coco3.com/community/1994/02/iniz-d0#comments</comments>
		<pubDate>Sun, 06 Feb 1994 09:25:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/iniz-d0/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85464 6-FEB 09:25  System Modules (6809)<br />     iniz /d0<br />     From: WTHOMPSON    To: BOISY</p>
<p>I can&#8217;t remember how to do what you did but I will try the iniz /d0 you<br />suggest.<br /> Thanks,<br /> Wayne</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/iniz-d0/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nitro</title>
		<link>http://www.coco3.com/community/1994/02/nitro</link>
		<comments>http://www.coco3.com/community/1994/02/nitro#comments</comments>
		<pubDate>Sun, 06 Feb 1994 09:12:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/02/nitro/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85462 6-FEB 09:12  System Modules (6809)<br />     Nitro<br />     From: WTHOMPSON    To: WESGALE</p>
<p>Wes,<br />  I am haveing problems with getting no-drivers to work with Nitro.<br />At first, the SC2 drivers I had were not recognized by Nitro.  Then<br />a friend in my coco club let me try out his SC2 drivers.  They are<br />differnt from the ones I had AND Nitro could patch them.  They even<br />worked when I put them in a boot.  But then a problem reared its ugly<br />head.  After a while I would get an<br />202 &#8211; Interrupt Polling Table Full<br />  I did some investigating and found that after I booted up with the<br />cc3disk.slp (nv1.15) the would occour after the floppy had been<br />accessed 11 times.  Reboot and the same thing, 11 time and error 202.<br />I even tried different versions of      the nitro&#8217;d cc3disk.slp<br />(nv1.00, nv1.107, and nv1.115)  even the stock cc3disk.slp in the<br />nitro boot had the same error.  I have a coco3 512k, newer MPI(coco3<br />upgrade), disto SC2 (slot 4), B&#038;B cocoxt(slot3), Tandy delux rs-232 pak<br />(slot1).  I have an HHD63B09E in the coco with nitro v1.15/1.16.<br />Your help would be greatly appreciated!<br /> Thanks,<br /> Wayne</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/02/nitro/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>RE:         Disto/Ken-Ton Clash Re: Msg 85212</title>
		<link>http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-msg-85212</link>
		<comments>http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-msg-85212#comments</comments>
		<pubDate>Thu, 27 Jan 1994 19:20:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-msg-85212/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85257 27-JAN 19:20 System Modules (6809)<br />     RE:         Disto/Ken-Ton Clash (Re: Msg 85212)<br />     From: DENNYWRIGHT  To: BOISY</p>
<p>Where can I find these drivers and which one do I need? I have a Super<br />Controller II and a MPI, a Ken-Ton inter        face (SCSI) and a Fujitsu MFM HD</p>
<p>w/adaptec 4000 controller board.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-msg-85212/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE:         Disto/Ken-Ton Clash Re: Msg 85212</title>
		<link>http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-msg-85212-2</link>
		<comments>http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-msg-85212-2#comments</comments>
		<pubDate>Wed, 26 Jan 1994 22:19:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-msg-85212-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85234 26-JAN 22:19 System Modules (6809)<br />     RE:         Disto/Ken-Ton Clash (Re: Msg 85212)<br />     From: COCOKIWI     To: BOISY</p>
<p>Right on..I boo,booed! I just forgot the address!<br />I have a SC II&#8230;the Sector buffer was the problem,conflicts with the Ken-ton..<br />the reason for the 4 in one bit!<groan> foot in mouth!<br />Dennis</p>
<p></groan></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-msg-85212-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE:         Disto/Ken-Ton Clash Re: MW</title>
		<link>http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-mw</link>
		<comments>http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-mw#comments</comments>
		<pubDate>Tue, 25 Jan 1994 23:19:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-mw/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85194 25-JAN 23:19 System Modules (6809)<br />     RE:         Disto/Ken-Ton Clash (Re: MW</p>
<p>Kenton and an FF50 address??  I have a ken-ton system and so far as I knew<br />it addressed itself starting at FF74 with a jumper option for FF70.  This<br />is also tha base address that is in the descriptor for the hard drives I<br />have installed.  I do not have a DISTO controller (I did get the 2 Meg) so<br />the controllers may indeed clash but I don&#8217;t think it is in the FF50 range.<br />If you know of something I missed I am interested.  As for the drivers for<br />a kenton system, the SCSISYS drivers here on delphi from Matt Thompson<br />should do a fine job for Denny.   Mark</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/01/re-distoken-ton-clash-re-mw/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disto/Ken-Ton Clash</title>
		<link>http://www.coco3.com/community/1994/01/distoken-ton-clash</link>
		<comments>http://www.coco3.com/community/1994/01/distoken-ton-clash#comments</comments>
		<pubDate>Tue, 25 Jan 1994 20:33:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/01/distoken-ton-clash/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>85189 25-JAN 20:33 System Modules (6809)<br />         Disto/Ken-Ton Clash<br />     From: DENNYWRIGHT  To: ALL</p>
<p>I have a Disto SC II and a Ken-Ton SCSI interface. I guess there is a hardware<br />prot address clash between the two of them. I am forced to use an old FD-501<br />controller with my newly acquired 75 meg hard drive. From what I have been told<br />I need a new CC3disk<br /> driver that will work with the Super Controller II and Ken-Ton SCSI interface.<br />Can anyone tell me where I might be able to get a copy of the needed drivers?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/01/distoken-ton-clash/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>VDGint</title>
		<link>http://www.coco3.com/community/1994/01/vdgint-2</link>
		<comments>http://www.coco3.com/community/1994/01/vdgint-2#comments</comments>
		<pubDate>Sun, 02 Jan 1994 10:30:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/01/vdgint-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>84541 2-JAN 10:30  System Modules (6809)<br />     VDGint<br />     From: DONALDS      To: ALL</p>
<p>I have tried to get the new VDGINT modules that Alan Dekok did to<br />work with my 2meg system and everytime the VDG screen crashs. I can use a<br />VDG screen with the VDG discriptor before I apply his but not with his.<br /> Has anyone got it to work with there 2meg systems if so how. I use a hd6309c,<br />scII, power boost, Adaptec/2HD&#8217;s.</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/01/vdgint-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>2 meg VDGInt</title>
		<link>http://www.coco3.com/community/1994/01/2-meg-vdgint</link>
		<comments>http://www.coco3.com/community/1994/01/2-meg-vdgint#comments</comments>
		<pubDate>Sat, 01 Jan 1994 22:12:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1994/01/2-meg-vdgint/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>84518 1-JAN 22:12  System Modules (6809)<br />     2 meg VDGInt<br />     From: NEALSTEWARD  To: DISTO</p>
<p>Tony,<br />Is there anyway of incorporating Alan Dekok&#8217;s VDGInt patches into the<br />2 meg VDGInt patches.  It seems that more system RAM would help a 2 meg<br />system.  Also, the 6309 version would help with speed as well as size.<br />I&#8217;m afraid such a task is way beyond my capabilities.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1994/01/2-meg-vdgint/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SC-II y-cable</title>
		<link>http://www.coco3.com/community/1993/12/sc-ii-y-cable</link>
		<comments>http://www.coco3.com/community/1993/12/sc-ii-y-cable#comments</comments>
		<pubDate>Sun, 19 Dec 1993 02:34:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/12/sc-ii-y-cable/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>84173 19-DEC 02:34 System Modules (6809)<br />     SC-II y-cable<br />     From: RICHKOTTKE   To: ROYBUR</p>
<p>Roy,<br />  I had the same problem with my SC-II when I crammed it into a PC box.  The<br />solution was to shield the ribbon cable with copper foil and ground one<br />end of the foil to the CoCo and the other end to the SC-II.  You can get<br />copper foil at most hobby shops.  Brass foil would work also, but it&#8217;s a<br />little harder to solder onto.  After I shielded the cable the SC-II worked<br />fine in no-halt mode.<br />   -Rich</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/12/sc-ii-y-cable/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Tape Backup Status</title>
		<link>http://www.coco3.com/community/1993/12/tape-backup-status</link>
		<comments>http://www.coco3.com/community/1993/12/tape-backup-status#comments</comments>
		<pubDate>Thu, 09 Dec 1993 01:41:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/12/tape-backup-status/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83876 9-DEC 01:41  System Modules (6809)<br />     Tape Backup Status<br />     From: RICHKOTTKE   To: ALL</p>
<p>Here&#8217;s the status on the Tape Backup Project:</p>
<p>I called Colorado Memory Systems to see if the would tell me how the<br />parallel port interface works.  After navigating their phone &#8220;HELP&#8221; system<br />and explaining to at least 3 &#8220;Customer Support Engineers&#8221; that I DID NOT<br />HAVE AN IBM COMPATIBLE IN ANY WAY SHAPE OR FORM, I finally got a &#8220;Supervisor&#8221;<br />(could have been the janitor for all I know) who explained to me that<br />Colorado Memory Systems is keeping the details of the interface secret to<br />prevent the Korean clone makers from ripping them off.  She did admit that<br />the drive itself uses the same MFM interface as a floppy drive and that there<br />was a converter board between the parallel port and the MFM port.</p>
<p>A quick check inside my Trakker 250 confirmed this.  The converter board<br />contains a standard Intel 82077 floppy controller chip, plus a big<br />microcontroller from Motorola that I didn&#8217;t recognize.</p>
<p>CMS also gave me a phone number for the Quarter Inch Cassette standards<br />committee.  I called them and for free (!) they are sending all the specs<br />for the industry standard QIC-117 control language and QIC-80 tape format.<br />Maybe (I hope) there will be some hints on how the tape drive uses the MFM<br />interface.</p>
<p>So at this point I have several options:</p>
<p>    &#8211; Give up on the parallel port idea and make the tape drive work<br />      using the MFM interface.  This would be good for everyone who wants<br />      to use a tape drive but don&#8217;t have a parallel port, since we could<br />      use the standard floppy controller and cable.</p>
<p>    &#8211; Disassemble the software from Colorado Memory Systems.  This would be<br />      a great intro to 8086 assembly language but vey time consuming.</p>
<p>    &#8211; Hook up a monitor to the parallel port of a PC and watch it talk to<br />      the tape drive.  I would have to build a monitor.</p>
<p>    &#8211; Write a formal-looking letter from the &#8220;QIC committee of the OS9<br />      User&#8217;s Group&#8221; (assuming I can get Boisy et al to go along) to the<br />      engineering department of CMS requesting the specs and explaining<br />      how we could expand their market for free.  I could even sign non-<br />      disclosure agreements and not give the source code to anyone.</p>
<p>    &#8211; Give up and go home.</p>
<p>Well gang, any ideas?  This isn&#8217;t going to be as easy as I thought (as<br />usual!)</p>
<p>   -Rich</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/12/tape-backup-status/feed</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>RE: Tape Backup Re: Msg 83797</title>
		<link>http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83797</link>
		<comments>http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83797#comments</comments>
		<pubDate>Tue, 07 Dec 1993 20:29:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83797/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83832 7-DEC 20:29  System Modules (6809)<br />     RE: Tape Backup (Re: Msg 83797)<br />     From: WTHOMPSON    To: RICHKOTTKE</p>
<p>  I am VERY interested in something like that!  With the parallel port<br />hookup one could use the tape backup on more than one computer system too.<br />ie for those guys that have a pc and a coco3.<br /> Thanks,<br /> Wayne</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83797/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: Tape Backup Re: Msg 83804</title>
		<link>http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83804</link>
		<comments>http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83804#comments</comments>
		<pubDate>Mon, 06 Dec 1993 19:51:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83804/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83807 6-DEC 19:51  System Modules (6809)<br />     RE: Tape Backup (Re: Msg 83804)<br />     From: RICHKOTTKE   To: KENFLANAGAN</p>
<p>Sorry Ken,<br />    It won&#8217;t work unless you&#8217;ve got a real, bi-directional parallel port.<br />I made my own, and the DISTO 3N1 may also have one.  There may be some way<br />to attach a tape drive with a simple interface and if so I&#8217;ll explore it.<br />If nothing else I&#8217;ll post the plans for my bi-directional port.<br />    -Rich</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83804/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>RE: Tape Backup Re: Msg 83797</title>
		<link>http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83797-2</link>
		<comments>http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83797-2#comments</comments>
		<pubDate>Mon, 06 Dec 1993 18:00:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83797-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83805 6-DEC 18:00  System Modules (6809)<br />     RE: Tape Backup (Re: Msg 83797)<br />     From: ILLUSIONIST  To: RICHKOTTKE</p>
<p>I would definatly be interested, I take it this is for CoCo OS-9? if so,<br />I wish you the best of luck, as you will have to write a manager for it<br />as well, RBF is obviosly for random block devices (floppies, HD&#8217;s, etc)<br />SCF is for serial devices like printers, and terminals&#8230;you would need<br />the Microware SBF (seqential block file manager)&#8230;and since Mware aint<br />gonna give it to ya, you will have to write one..unless you can somehow<br />&#8220;trick&#8221; SCF or RBF to use a tape drive..</p>
<p>                                           -* Mike</p>
<p>in any case, good luck.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/12/re-tape-backup-re-msg-83797-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Gshell</title>
		<link>http://www.coco3.com/community/1993/11/gshell-3</link>
		<comments>http://www.coco3.com/community/1993/11/gshell-3#comments</comments>
		<pubDate>Tue, 30 Nov 1993 20:10:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/11/gshell-3/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83601 30-NOV 20:10 System Modules (6809)<br />     Gshell<br />     From: ILLUSIONIST  To: ALL</p>
<p>Does anyone have any idea why Gshell would hang during the &#8220;rollover&#8221; of the<br />menu bar? This never happened before, I just started setting up Gshell and<br />MV for my girlfriend when she uses my CoCo, and everything hangs, I am<br />using the STOCK tandy windint. and used the stock gshell also.????</p>
<p>I am stuck&#8230;</p>
<p>                                                                -** Mike</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/11/gshell-3/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>st-225</title>
		<link>http://www.coco3.com/community/1993/11/st-225</link>
		<comments>http://www.coco3.com/community/1993/11/st-225#comments</comments>
		<pubDate>Sat, 27 Nov 1993 23:56:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/11/st-225/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83439 27-NOV 23:56 System Modules (6809)<br />     st-225<br />     From: RICHKOTTKE   To: RANDYKWILSON</p>
<p>Randy,<br />   According to my Seagate Installer&#8217;s manual, the ST-225 is a MFM drive with<br />4 heads, 615 tracks and a step pulse of 5-200 microseconds.  You need to set<br />up the driver so it write precompensates tracks 300-614.  It DOES NOT have<br />an auto-park feature, so you should remember to park it before powerdown.<br />If you need to know anything else drop me some e-mail.<br />   -Rich</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/11/st-225/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hard drives</title>
		<link>http://www.coco3.com/community/1993/11/hard-drives-16</link>
		<comments>http://www.coco3.com/community/1993/11/hard-drives-16#comments</comments>
		<pubDate>Sat, 27 Nov 1993 23:56:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/11/hard-drives-16/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83440 27-NOV 23:56 System Modules (6809)<br />     Hard drives<br />     From: RICHKOTTKE   To: ALL</p>
<p>Does anyone know if it&#8217;s ok to run an RLL drive in MFM mode using an MFM<br />controller?</p>
<p>   -Rich</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/11/hard-drives-16/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: Interleave Factors Re: Msg 83060</title>
		<link>http://www.coco3.com/community/1993/11/re-interleave-factors-re-msg-83060</link>
		<comments>http://www.coco3.com/community/1993/11/re-interleave-factors-re-msg-83060#comments</comments>
		<pubDate>Sun, 21 Nov 1993 16:32:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/11/re-interleave-factors-re-msg-83060/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83252 21-NOV 16:32 System Modules (6809)<br />     RE: Interleave Factors (Re: Msg 83060)<br />     From: RICKMAC      To: DSRTFOX</p>
<p>Thanks very much for leaving such a long and detailed message, but I think<br />my query was as to whether you can run a disk with an interleave factor<br />of 2 with a system that has some disks and the device driver coded for<br />an interleave factor of 3 without screwing up the system or the disks.<br />Yes, I know I can use &#8220;dmode&#8221; to change the interleave factor, but to do this<br />every time you put a diiferently formatted disk in is a hassle.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/11/re-interleave-factors-re-msg-83060/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Printer</title>
		<link>http://www.coco3.com/community/1993/11/printer-8</link>
		<comments>http://www.coco3.com/community/1993/11/printer-8#comments</comments>
		<pubDate>Sun, 21 Nov 1993 15:56:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/11/printer-8/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83250 21-NOV 15:56 System Modules (6809)<br />     Printer<br />     From: CLTUCKER     To: ALL</p>
<p>My /p prints ok not connected to SIG&#8217;s. Also OK on OS9. When printing the<br />screen on Delphi it prints periods and letters. ra.t co&#8230;..mme etc.<br />Any suggestions out there? (:-)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/11/printer-8/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Genie</title>
		<link>http://www.coco3.com/community/1993/11/genie-3</link>
		<comments>http://www.coco3.com/community/1993/11/genie-3#comments</comments>
		<pubDate>Sat, 20 Nov 1993 20:03:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/11/genie-3/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83221 20-NOV 20:03 System Modules (6809)<br />     Genie<br />     From: CLTUCKER     To: ALL</p>
<p>Am using ulterm to contact Genie. When<br />Genie answers, the dialing info screen won&#8217;t go away and cut me through.<br />The tbl seems to be on my end. Any ideas.(:-)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/11/genie-3/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: SCSI512 Re: Msg 83157</title>
		<link>http://www.coco3.com/community/1993/11/re-scsi512-re-msg-83157</link>
		<comments>http://www.coco3.com/community/1993/11/re-scsi512-re-msg-83157#comments</comments>
		<pubDate>Sat, 20 Nov 1993 12:51:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/11/re-scsi512-re-msg-83157/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83213 20-NOV 12:51 System Modules (6809)<br />     RE: SCSI512 (Re: Msg 83157)<br />     From: MIKE_GUZZI   To: REVWCP</p>
<p>I am currently using the SCSISYS 1.0 until the disks arrive (I put in for<br />the 2.0 version) making the descriptors was real easy with his program<br />and setting up the hard disk was also easy. I used 512 byte sectors right<br />off because you can get more space that way. if your having a problem<br />with his drivers, I can help.</p>
<p>Mike</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/11/re-scsi512-re-msg-83157/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: SCSI512 Re: Msg 83160</title>
		<link>http://www.coco3.com/community/1993/11/re-scsi512-re-msg-83160</link>
		<comments>http://www.coco3.com/community/1993/11/re-scsi512-re-msg-83160#comments</comments>
		<pubDate>Sat, 20 Nov 1993 00:32:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/11/re-scsi512-re-msg-83160/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>83193 20-NOV 00:32 System Modules (6809)<br />     RE: SCSI512 (Re: Msg 83160)<br />     From: REVWCP       To: BOISY</p>
<p>I was able to get the new hard drive up and running using SCSISYS_1.0 by<br />Matt Thompson.  I was also able to access the old st-138n. Now the challenge<br />will be to be able to use both.  The st-138n as /h0 and the st-251 as /h1.<br />I alread have the cable made up.  I still have to play with the descriptors<br />a bit.  One question that I have received differing opinions is do I have<br />to remove the terminating resistors from one of the drives?<br />With all best wishes.<br />Brother Jeremy, CSJW</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/11/re-scsi512-re-msg-83160/feed</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>supercomm</title>
		<link>http://www.coco3.com/community/1993/11/supercomm-10</link>
		<comments>http://www.coco3.com/community/1993/11/supercomm-10#comments</comments>
		<pubDate>Fri, 05 Nov 1993 19:07:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/11/supercomm-10/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>82746 5-NOV 19:07  System Modules (6809)<br />     supercomm<br />     From: MIKE_GUZZI   To: RANDYKWILSON</p>
<p>Randy,</p>
<p>I notice one pecular thing about supercomm. It grabs a lot of system ram.<br />accounting for the XTP value of sacia (for recieve buffer) and the extra path to</p>
<p>/NIL (VRN timing) it grabs 11 pages of ram for itself (not counting XTP value or</p>
<p>VRN) I even removed VRN and reduced the XTP value to see what happens. Why does<br />it grab so much system ram? is there anyway to make it less hungry for ram?</p>
<p>Mike</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/11/supercomm-10/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>GrfInt bug found</title>
		<link>http://www.coco3.com/community/1993/11/grfint-bug-found</link>
		<comments>http://www.coco3.com/community/1993/11/grfint-bug-found#comments</comments>
		<pubDate>Fri, 05 Nov 1993 19:04:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/11/grfint-bug-found/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>82745 5-NOV 19:04  System Modules (6809)<br />     GrfInt bug found<br />     From: MIKE_GUZZI   To: ALL</p>
<p>I finally found the bug that has been plaquing me for 2 months. This bug is with</p>
<p>GrfInt in the bootfile I cannot use /w to do any window operations It totally<br />crashes the system. Well what i discovered it my /w1 descriptor is set to<br />type=01 (vdg) as soon as i placed it back as type=80 it worked! NOTE: with<br />WindInt, it would skip /w1 and use /w2. apparently windint is a little bit<br />smarter. It also made no difference if VDGInt was in memory or not. I originally</p>
<p>thought supercomm was at fault since it would crash the system when booted after</p>
<p>i removed WindInt from the boot. Well apparently GrfInt&#8217;s coding isn&#8217;t smart<br />enough to go around type 1 windows. Thought id pass this one on.</p>
<p>Mike</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/11/grfint-bug-found/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>NitroOS9 Review</title>
		<link>http://www.coco3.com/community/1993/10/nitroos9-review</link>
		<comments>http://www.coco3.com/community/1993/10/nitroos9-review#comments</comments>
		<pubDate>Tue, 26 Oct 1993 07:41:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/10/nitroos9-review/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>82471 26-OCT 07:41 System Modules (6809)<br />     NitroOS9 Review<br />     From: MARKGRIFFITH To: ALL</p>
<p>I need a volunteer to do a complete review of the latest version of NitrOS9<br />(Ver.  1.15).  The ideal person should NOT already have a copy if NitrOS9<br />installed, but should be a user with enough experience to install and use this<br />package while taking notes along the way to write the review.  Also, this person</p>
<p>should be able to write decently.  No Hemmingways are expected, just be able to<br />put your thoughts on paper to where it can be edited for clarity and<br />correctness.  You don&#8217;t need to be an English major to do this (grin).</p>
<p>Whomever gets to do this gets to keep the NitrOS9 package as their fee for doing</p>
<p>the review.  Consequently, we expect a decent amount of time to be spent on this</p>
<p>and a good, accurate and unbiased review to be made. I&#8217;d like to include the<br />review in the December or January issue of Metamorphosis, so please make sure<br />you also have the time required to do this.</p>
<p>All volunteers please e-mail me your requests and your system particulars.<br />Thanks!</p>
<p> Mark Griffith<br /> Dirt Cheap Computer Stuff Co.<br />   &#8220;Cheap, But Not Trash&#8221;</p>
<p> (Uploaded with InfoXpress Ver. 1.01)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/10/nitroos9-review/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Parallel Port</title>
		<link>http://www.coco3.com/community/1993/10/parallel-port-3</link>
		<comments>http://www.coco3.com/community/1993/10/parallel-port-3#comments</comments>
		<pubDate>Sat, 23 Oct 1993 15:48:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - System Modules 6809]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1993/10/parallel-port-3/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>82394 23-OCT 15:48 System Modules (6809)<br />     Parallel Port<br />     From: WTHOMPSON    To: ALL</p>
<p>Does anyone know if any of the parallel ports available for the coco is<br />bidirectional?  There is a new product out for PC clones (portables mainly)<br />that is a Sound Blaster type sound board but hooks to a parallel port.  I&#8217;m not<br />sure if a bidirectional port is needed but I would think so. This seems like a<br />decent way to add quality sound to our cocos.<br />  I have seen the sound board in Computer Shopper and I also just got a catalog<br />from Tiger software and the have some info about it.  It is called the<br />Audioport.  It is billed as multimedia sound for your laptop.  It plugs into the</p>
<p>parallel port and gives microphone input, audio output via builtin speaker or<br />external amp/headphones, and multi-timbral FM sysnthesis. It also is AC/DC<br />powered.  It retails for around $70.<br />  Has anyone else seen this product?  I&#8217;m just fishing for ideas so lets hear<br />them!<br /> Thanks,<br /> Wayne</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1993/10/parallel-port-3/feed</wfw:commentRss>
		<slash:comments>30</slash:comments>
		</item>
	</channel>
</rss>
