<?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; Archives</title>
	<atom:link href="http://www.coco3.com/community/category/archives/delphi/delphi-archives/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-archives/feed?page=2" />

		<item>
		<title>ms 44779</title>
		<link>http://www.coco3.com/community/1988/09/ms-44779</link>
		<comments>http://www.coco3.com/community/1988/09/ms-44779#comments</comments>
		<pubDate>Fri, 09 Sep 1988 23:58:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1988/09/ms-44779/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>44911  9SEP88-2358 Archives<br />     ms 44779<br />     From: NYPHOTO      To: HARBIE</p>
<p>Some where in the coco data base I saw a Atari.arc file to see ATARI Graphics<br />on the COCO, that is the one I am refering to. It was arced with tc2 then. I<br />never could de=arced the darn thing on my , thren coco2. I have d/l 3 or 4 arc<br />file to my COCO and no<br />go. Excer</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/1988/09/ms-44779/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ut</title>
		<link>http://www.coco3.com/community/1988/08/ut-3</link>
		<comments>http://www.coco3.com/community/1988/08/ut-3#comments</comments>
		<pubDate>Tue, 09 Aug 1988 00:52:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1988/08/ut-3/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>43908  9AUG88-0052 Archives<br />     ut<br />     From: NYPHOTO      To: MARTYGOODMAN</p>
<p>Marty, I am having trouble with arc files.I d/l COLOUR KEYS 3 and tc3 and all I<br />get is probably compress with a newer version. I d/l a second time file by file<br />and is fine.I d/l to my IBM using procom and to my coco usimg ae.bin. One more<br />thing if I d/l us<br />ing MIKEYTERM OR ULTIMATERM , wh how do I have to save them, which<br />format(ascii, bin,etc.). Thanks Excer</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1988/08/ut-3/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS9 TERMINAL Re: Msg 29985</title>
		<link>http://www.coco3.com/community/1987/07/re-os9-terminal-re-msg-29985</link>
		<comments>http://www.coco3.com/community/1987/07/re-os9-terminal-re-msg-29985#comments</comments>
		<pubDate>Tue, 07 Jul 1987 03:57:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/07/re-os9-terminal-re-msg-29985/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>30011  7JUL87-0357 Archives<br />     RE: OS9 TERMINAL (Re: Msg 29985)<br />     From: 6809ER       To: BOFA</p>
<p>Try downloading Xcom9 from the Os-9 sig and then use TRScopy to move it<br />over.</p>
<p>Steve Bjork</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/07/re-os9-terminal-re-msg-29985/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: 80 column boot Re: Msg 29416</title>
		<link>http://www.coco3.com/community/1987/06/re-80-column-boot-re-msg-29416</link>
		<comments>http://www.coco3.com/community/1987/06/re-80-column-boot-re-msg-29416#comments</comments>
		<pubDate>Wed, 24 Jun 1987 22:29:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/06/re-80-column-boot-re-msg-29416/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>29450 24JUN87-2229 Archives<br />     RE: 80 column boot (Re: Msg 29416)<br />     From: BILLH        To: BLUEJEANS</p>
<p>To get 80 columns at start up do:</p>
<p>MODPATCH<br />L TERM<br />C 2C 28 50<br />C 30 01 02</p>
<p>to get black background and green foreground (in addittion to 80 columns)</p>
<p>C 33 02 03<br />C 34 03 12<br />C 35 03 12</p>
<p>after these do:</p>
<p>V</p>
<p>This will modify the Term driver.  Then you will have to do a cobbler to make it<br />permanent.</p>
<p>Hope this helps, Bill Haesslein</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/06/re-80-column-boot-re-msg-29416/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 Re: Msg 29099</title>
		<link>http://www.coco3.com/community/1987/06/re-os-9-re-msg-29099</link>
		<comments>http://www.coco3.com/community/1987/06/re-os-9-re-msg-29099#comments</comments>
		<pubDate>Sat, 13 Jun 1987 19:57:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/06/re-os-9-re-msg-29099/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>29120 13JUN87-1957 Archives<br />     RE: OS-9 (Re: Msg 29099)<br />     From: MARTYGOODMAN To: DAVESS</p>
<p>As others may have already told you, OS9 Level II for the CoCo 3<br />is available at any Radio Shack store.  IF they don&#8217;t<br />have it in stock, you should be able to make them orderit<br />for you.  If you have trouble there, complain loudly in a letter to Fort Worth,<br />and let us<br />here know about it too.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/06/re-os-9-re-msg-29099/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 level II Re: Msg 28642</title>
		<link>http://www.coco3.com/community/1987/06/re-os-9-level-ii-re-msg-28642</link>
		<comments>http://www.coco3.com/community/1987/06/re-os-9-level-ii-re-msg-28642#comments</comments>
		<pubDate>Tue, 02 Jun 1987 06:22:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/06/re-os-9-level-ii-re-msg-28642/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>28657  2JUN87-0622 Archives<br />     RE: OS-9 level II (Re: Msg 28642)<br />     From: MARTYGOODMAN To: JIMHARRISON</p>
<p>I have been given to understand that if the 12V is not supplied to<br />the write pre comp circuit, then write pre comp simply does not<br />happen.  No more, no less.  THIS is no big deal, since write pre comp<br />is unnecessary for modern 5 1/4 in 40 trck drives.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/06/re-os-9-level-ii-re-msg-28642/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 level II Re: Msg 28592</title>
		<link>http://www.coco3.com/community/1987/06/re-os-9-level-ii-re-msg-28592</link>
		<comments>http://www.coco3.com/community/1987/06/re-os-9-level-ii-re-msg-28592#comments</comments>
		<pubDate>Mon, 01 Jun 1987 04:22:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/06/re-os-9-level-ii-re-msg-28592/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>28614  1JUN87-0422 Archives<br />     RE: OS-9 level II (Re: Msg 28592)<br />     From: MARTYGOODMAN To: JIMHARRISON</p>
<p>Question:</p>
<p>  Are you using the controller directly IN the CoCo 3 system port,<br />or with a Multipak?</p>
<p>OT the only chip on the board<br />that uses +12 volts!  The write pre comp circuit chip also<br />uses +12 volts.</p>
<p> I picked up a bunch of 5 volt only 1793 pin out compatible<br />Mitsubishi chips (M5W 1793-2 chips) for $1 each at a swap meet.<br />They work fine at normal speed in a CoCo 1 controller.<br />When I get my controller back from loan, I may try to see<br />if they make the thing work any better at 2 Mhz.</p>
<p>  One electronic slavage place I knew of was sellig<br />delsoldered but working Fujitsu 1793 chips for about $10 each<br />a while back.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/06/re-os-9-level-ii-re-msg-28592/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>multipak and rs232</title>
		<link>http://www.coco3.com/community/1987/05/multipak-and-rs232</link>
		<comments>http://www.coco3.com/community/1987/05/multipak-and-rs232#comments</comments>
		<pubDate>Sat, 30 May 1987 03:11:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/05/multipak-and-rs232/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>28464 30MAY87-0311 Archives<br />     multipak and rs232<br />     From: DAVESCHAEFER To: MARTYGOODMAN</p>
<p>Thank you for the info.  I guess I will just have to break down and buy a<br />multipak and an rs232 much to my chagrin.  I don&#8217;t have a place for a multipak<br />right now.<br />I guess I will have to move my computer station over by the Telephone stand with<br />the deskphone on it and put the phone on top of the disk drive to have room to<br />put the multipak on the computer station.<br />When that is done then I will start using OS-9 L2 communications programs for<br />all my local BBS that I log on even use it for LD calls and DELPHI.<br />Thank you again for the info, even though it wasn&#8217;t what I wanted to hear.  You<br />told the truth.  That is the best thing for all.  Have a good day.   Dave</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/05/multipak-and-rs232/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OS-9 level II</title>
		<link>http://www.coco3.com/community/1987/05/os-9-level-ii</link>
		<comments>http://www.coco3.com/community/1987/05/os-9-level-ii#comments</comments>
		<pubDate>Thu, 28 May 1987 18:44:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/05/os-9-level-ii/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>28409 28MAY87-1844 Archives<br />     OS-9 level II<br />     From: MIKE88       To: GREGL</p>
<p>Greg-<br />   I just bought OS-9 Level II, and am having big problems. The disk boots<br />correctly USUALLY, but whenever I try to do something, like FORMAT or BACKUP<br />a disk, it usually crashes about halfway thru. It either just sits there and<br />the drive stops changing tracks, or it stops and the screen flickers little<br />lines across it (crash!). A few times (1/4) it works OK, but the others it<br />doesn&#8217;t. Have any idea why? I thought it might have something to do with my<br />drives (kinda old, non R/S), but I&#8217;m not sure.</p>
<p>   -Mike</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/05/os-9-level-ii/feed</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 L2 COMMUNICATIONS Re: Msg 28244</title>
		<link>http://www.coco3.com/community/1987/05/re-os-9-l2-communications-re-msg-28244</link>
		<comments>http://www.coco3.com/community/1987/05/re-os-9-l2-communications-re-msg-28244#comments</comments>
		<pubDate>Mon, 25 May 1987 01:11:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/05/re-os-9-l2-communications-re-msg-28244/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>28267 25MAY87-0111 Archives<br />     RE: OS-9 L2 COMMUNICATIONS (Re: Msg 28244)<br />     From: MARTYGOODMAN To: DAVESCHAEFER</p>
<p>Due to the nature of the hardware of the CoCo (bit banger port)<br />and the OS9 software (interrupt driven multitasking multiuser)<br />it is an EXTREMELY poor idea to use the bit banger port,<br />and makes VASTLY greater sense to use the RS232 pak, which<br />can be had for $30 right now on close out sale at RS stores.</p>
<p>Micro Technical Consultants offered Xterm that used the<br />port on the old CoCo 1, tho&#8230; and may have a version<br />that works under L2 on the CoCo 3.</p>
<p> &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/05/re-os-9-l2-communications-re-msg-28244/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: TRScopy Re: Msg 27970</title>
		<link>http://www.coco3.com/community/1987/05/re-trscopy-re-msg-27970</link>
		<comments>http://www.coco3.com/community/1987/05/re-trscopy-re-msg-27970#comments</comments>
		<pubDate>Mon, 18 May 1987 00:07:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/05/re-trscopy-re-msg-27970/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>27989 18MAY87-0007 Archives<br />     RE: TRScopy (Re: Msg 27970)<br />     From: GREGMILLER   To: DUNK</p>
<p>The syntax for TRSCOPY is:<br /> TRSCOPY FILENAME PATHNAME #bufferspace (for copying RSDOS to OS9)<br /> TRSCOPY PATHNAME FILENAME #bufferspace (for copying OS9 to RSDOS)<br /> Examples:<br /> TRSCOPY /dd/cmds/FLIGHT FLIGHT/BIN:0 #40K<br /> TRSCOPY LETTER/TXT:0 /d0/data/newletter<br /> etc..<br /> &#8211; greg</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/05/re-trscopy-re-msg-27970/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OS9</title>
		<link>http://www.coco3.com/community/1987/05/os9-2</link>
		<comments>http://www.coco3.com/community/1987/05/os9-2#comments</comments>
		<pubDate>Sat, 16 May 1987 22:13:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/05/os9-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>27925 16MAY87-2213 Archives<br />     OS9<br />     From: GDALLRED     To: ALL</p>
<p>THE MULTIPAK IS #26-3024 AND IT HAS BEEN UPGRADED FOR THE COCO3.R/S SAID THE<br />CONTROLLER AND DRIVES MAY NEED TO BE ALIGNED. PERHAPS I NEED A NEW CONTROLLER??</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/05/os9-2/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: 0S9 Re: Msg 27892</title>
		<link>http://www.coco3.com/community/1987/05/re-0s9-re-msg-27892</link>
		<comments>http://www.coco3.com/community/1987/05/re-0s9-re-msg-27892#comments</comments>
		<pubDate>Sat, 16 May 1987 18:56:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/05/re-0s9-re-msg-27892/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>27913 16MAY87-1856 Archives<br />     RE: 0S9 (Re: Msg 27892)<br />     From: HARBIE       To: GDALLRED</p>
<p>WILD GUESS , DO YOU HAVE THE OLD RADIO SHACK DISK CONTROLLER ? THE ONE THAT<br />USES 12 VOLT AND WONT WORK IN THE COCO 2 OR 3 WITHOUT THE MULTIPACK ? IF SO ,<br />THERE&#8217;S YOUR PROBLEM .</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/05/re-0s9-re-msg-27892/feed</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>RE: 0S9 Re: Msg 27892</title>
		<link>http://www.coco3.com/community/1987/05/re-0s9-re-msg-27892-2</link>
		<comments>http://www.coco3.com/community/1987/05/re-0s9-re-msg-27892-2#comments</comments>
		<pubDate>Sat, 16 May 1987 16:32:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/05/re-0s9-re-msg-27892-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>27906 16MAY87-1632 Archives<br />     RE: 0S9 (Re: Msg 27892)<br />     From: MARTYGOODMAN To: GDALLRED</p>
<p>The OLDEST of disk controllers&#8230; that sold with the OLD GRAY<br />CASE drives and with the CoCo 1&#8230; will not, I am told,<br />work properly with the CoCo 3 at double speed.  You may<br />need a new disk controller.</p>
<p> Also&#8230; have you upgraded your Multipak?</p>
<p> What model of multipak do you have (Cat # 26-3024 or cat # 26-3124?)</p>
<p> &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/05/re-0s9-re-msg-27892-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: INITIALIZING SO9 BOOTUP Re: Msg 26983</title>
		<link>http://www.coco3.com/community/1987/04/re-initializing-so9-bootup-re-msg-26983</link>
		<comments>http://www.coco3.com/community/1987/04/re-initializing-so9-bootup-re-msg-26983#comments</comments>
		<pubDate>Sun, 26 Apr 1987 13:38:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/04/re-initializing-so9-bootup-re-msg-26983/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>27049 26APR87-1338 Archives<br />     RE: INITIALIZING SO9 BOOTUP (Re: Msg 26983)<br />     From: DRIFTER      To: WA2ONM</p>
<p>                        -< '...I'll be watching you ..' >-</p>
<p>    Try setting &#8216;t&#8217; (echo cmds) at the top of your startup file, so you can see<br />how far your procedure gets before bombing out. I suspect it is exiting<br />before it reaches your xmode baud cmd.</p>
<p>    On Level I, if your startup encountered an error it would exit AND leave<br />the error msg for why it choked. While I haven&#8217;t played around with Level<br />II much yet, my startup file will NOT leave the error msg onscreen (even<br />if it ever sends it in the first place &#8211; my vision isn&#8217;t that quick!). It<br />will just fall through to the OS9: prompt, with nary a peep about things<br />that it skipped, or why.</p>
<p>    With the &#8216;t&#8217; switch on, you can watch every move your startup file makes.<br />If my guess is correct and you have an offending cmd preceding your xmode<br />baud cmd, you will see everything up to and including the one os9 finds<br />unpalatable. Fix that one and continue.</p>
<p>          Hope this helps out,</p>
<p>                                 &#8212; drifter &#8212;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/04/re-initializing-so9-bootup-re-msg-26983/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DOWNLOADING OS9 FILES</title>
		<link>http://www.coco3.com/community/1987/04/downloading-os9-files</link>
		<comments>http://www.coco3.com/community/1987/04/downloading-os9-files#comments</comments>
		<pubDate>Fri, 24 Apr 1987 23:40:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/04/downloading-os9-files/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>26984 24APR87-2340 Archives<br />     DOWNLOADING OS9 FILES<br />     From: WA2ONM       To: ANYONE (NR)</p>
<p>HELP, I HAVE OS-9 LVL II.<br />CAN I USE MIKEY TERM 4.3<br />TO DOWNLOAD OS-9 FILES<br />AND PROGRAMS ?????<br />IF SO HOW DO I CONVERT<br />THEM TO LOAD VIA OS-9<br />OR IS THERE A NEED TO<br />CONVERT THEM TO A OS-9<br />FILE ???</p>
<p>THANKS,<br />RICH DUNKLEE, WA2ONM<br />&#8211;&#8230; &#8230;&#8211; .<br />-.-. ..- ..-.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/04/downloading-os9-files/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: I GOT IT! Re: Msg 26381</title>
		<link>http://www.coco3.com/community/1987/04/re-i-got-it-re-msg-26381</link>
		<comments>http://www.coco3.com/community/1987/04/re-i-got-it-re-msg-26381#comments</comments>
		<pubDate>Mon, 13 Apr 1987 22:38:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/04/re-i-got-it-re-msg-26381/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>26420 13APR87-2238 Archives<br />     RE: I GOT IT! (Re: Msg 26381)<br />     From: DENNYSKALA   To: WLADI</p>
<p>Try config #56K (or #48k if 56 is too much).  I haven&#8217;t tried, but config<br />may just allocate the extra memory to the copy buffer, dramatically<br />decreasing the disk swapping required.</p>
<p>                            ***** Dennis *****</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/04/re-i-got-it-re-msg-26381/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>RE: OS9 Re: Msg 26224</title>
		<link>http://www.coco3.com/community/1987/04/re-os9-re-msg-26224</link>
		<comments>http://www.coco3.com/community/1987/04/re-os9-re-msg-26224#comments</comments>
		<pubDate>Mon, 06 Apr 1987 23:16:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/04/re-os9-re-msg-26224/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>26239  6APR87-2316 Archives<br />     RE: OS9 (Re: Msg 26224)<br />     From: MARTYGOODMAN To: BARNEYS</p>
<p>Try, instead, leaving specific questions on the OS9 online special<br />interest group (type OS at the main CoCo SIG prompt).<br />That is more likely, I suspect, to get you the help you need.<br />Totally open ended questions like &#8220;I need help with OS 9&#8230; meet<br />me to help me&#8221; tend not to be very likely to produce any help.<br />Folks really can&#8217;t do much with such questions.  But questions<br />about a specific problem  usually bring fast and accurate help<br />to the asker.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/04/re-os9-re-msg-26224/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 Re: Msg 18299</title>
		<link>http://www.coco3.com/community/1987/02/re-os-9-re-msg-18299</link>
		<comments>http://www.coco3.com/community/1987/02/re-os-9-re-msg-18299#comments</comments>
		<pubDate>Mon, 16 Feb 1987 20:39:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/02/re-os-9-re-msg-18299/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>24201 16FEB87-2039 Archives<br />     RE: OS-9 (Re: Msg 18299)<br />     From: BOWSIN       To: ENDOTSON</p>
<p>Looks like the rs-os9 conversion program is getting it&#8217;s moneys worth in the<br />os-9 programs. Did not relize that it only changed<br />one track at the time I sent it in. Am glad that at least there are some<br />smart(er) people<br />out there that cuaght the slight mistake.<br />  Even though I don&#8217;t use OS-9 myself thought that since others do that that<br />program<br />would be useful to others that might want to get some OS-9 programs like from<br />this<br />sig or other services or from a pal down the street. Use it in good health guy!!<br />  By the way like the previrbiale stumbling over a dead body!! This program was<br />like that. Just happened across it lie out<br />begging to be taken!!<grin>!</p>
<p></grin></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/02/re-os-9-re-msg-18299/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>speed trap ahead</title>
		<link>http://www.coco3.com/community/1987/02/speed-trap-ahead</link>
		<comments>http://www.coco3.com/community/1987/02/speed-trap-ahead#comments</comments>
		<pubDate>Thu, 12 Feb 1987 22:36:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/02/speed-trap-ahead/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>24051 12FEB87-2236 Archives<br />     speed trap ahead<br />     From: MIKEWARD     To: MARTYGOODMAN</p>
<p>Marty,</p>
<p>I picked up &#8220;Rogue&#8221; the other day so I could tinker<br />around with OS-9 L-II a bit and had a dickens of a time.</p>
<p>Seems it didn&#8217;t want to load and/or run most of the time.</p>
<p>In the process of messing around with it to get it to go<br />most of the time I observed several curious things.</p>
<p>The original 35 track single sided disk which the OS9 on it steps<br />at 33msec doesn&#8217;t like to work well at all for me.</p>
<p>I cobbled the disk drivers to work at 6ms and wow, what an<br />improvement!</p>
<p>I also picked over the loader on track 34 and notice it<br />kicks the Coco 3 into hi-speed right off the bat.</p>
<p>I have an old 1.0 (vanilla-no mods) disk controller and<br />it never ever EVER would do disk I/O in the high speed mode.<br />As a matter of fact the ROM is so slow that typing &#8220;DIR&#8221; in<br />hi speed gets me a &#8220;? syntax error&#8221;.</p>
<p>Naturally the ROM isn&#8217;t the problem since that&#8217;s all running in<br />RAM on the Coco 3.</p>
<p>I was wondering if there are any parts in my old 1.0 controller<br />that are just intrinsically slow and that differ in some way<br />from parts used in the newer 1.1 controllers which seem not to<br />have this problem.</p>
<p>I find it curious that setting the step rate to 6ms vastly<br />improved the reliability of disk I/O although it (OS-9 L-II)<br />still crashes now and then when disk I/O is initiated.</p>
<p>Got any ideas?  I bet you&#8217;ll hear variations on this theme<br />as OS-9 L-II becomes available generally.</p>
<p>Oh, I didn&#8217;t mention that &#8220;Rogue&#8221; is an OS-9 &#8220;dungeon&#8221; game<br />that has an OS-9 L-II operating system.</p>
<p>Neet game when the disks behave!</p>
<p>If I can help with more info lemme know.</p>
<p>Mike</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/02/speed-trap-ahead/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 AND HARDWARE CLOCK??? Re: Msg 23949</title>
		<link>http://www.coco3.com/community/1987/02/re-os-9-and-hardware-clock-re-msg-23949</link>
		<comments>http://www.coco3.com/community/1987/02/re-os-9-and-hardware-clock-re-msg-23949#comments</comments>
		<pubDate>Tue, 10 Feb 1987 05:11:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/02/re-os-9-and-hardware-clock-re-msg-23949/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>23969 10FEB87-0511 Archives<br />     RE: OS-9 AND HARDWARE CLOCK??? (Re: Msg 23949)<br />     From: MARTYGOODMAN To: CAPNCRUNCH</p>
<p>Special software drivers are needed for given particular<br />hardware real time clocks.  There is no way the<br />general release of OS9 in any version can be expected to<br />suport any given particular third party real time clock.<br />The same is true of IBM PC real time clocks.</p>
<p>  Given the great value of having the computer know the<br />day and date under OS9 or MS DOS (as the OS time stamps<br />all files, and this is QUITE a valuable thing), it<br />is disgusting stupidity on the part of Tandy, IBM,<br />and most clone manufacturers to NOT have included<br />a real time clock as part of the BASE system on the<br />mutha board.</p>
<p> Consider&#8230; a multifunction stop watch that runs for<br />about 7 years on a lithium batter.. of name brand<br />variety (Casio) typically sells for $20.  And the<br />cheap watches, that just give day and date, are<br />commonly available for $2 to $5.  And those have<br />a DISPLAY, not needed by a mutha board based clock.</p>
<p> I find the failure to put a clock in the CoCo,<br />IBM PC, Tandy 1000, and such to be evidence of the<br />relative lack of competence of the deisgn teams<br />associated with those projects.. or of the sliminess<br />and greed of the associated marketting division.</p>
<p> &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/02/re-os-9-and-hardware-clock-re-msg-23949/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>CoCo3/OS-9 Level II</title>
		<link>http://www.coco3.com/community/1987/02/coco3os-9-level-ii</link>
		<comments>http://www.coco3.com/community/1987/02/coco3os-9-level-ii#comments</comments>
		<pubDate>Mon, 02 Feb 1987 23:23:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/02/coco3os-9-level-ii/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>23643  2FEB87-2323 Archives<br />     CoCo3/OS-9 Level II<br />     From: DWHILL       To: MIKE88</p>
<p>    I was reading the messages you left in the database about the CoCo 3 and<br />Level II.  Some comments:</p>
<p>    OS-9 certainly wasn&#8217;t developed on the Color Computer!  As I understand it,<br />it was developed as an operating system for Basic09, and was to be offered to<br />Motorola, which didn&#8217;t take it.  Microware offered it as a product on several<br />different 6809-based systems and the rest is a minor footnote in computer<br />history&#8230;   For a while, it seemed that OS-9 on the Color Computer was more of<br />an afterthought on Tandys part, although the Level II and Multi-Vue seems to<br />demonstrate that they&#8217;re waiting to stay in the game.</p>
<p>    Generally, a 6809 compares well with a 8088 and even a 68000 in the number<br />of instructions executed per unit of time.  Clock speed alone does NOT tell the<br />whole story!  For example, I think the CoCo3 and Level II/Multi-Vue will compare<br />favorably with a 512K Macintosh and it&#8217;s windowing environment.  The 68000 in<br />itmay not be running at 8 MHz, and it&#8217;s loaded down with handling the graphics,<br />soit does run slower than one might expect.</p>
<p>    I don&#8217;t reasonably expect the CoCo3 can keep up with an existing Amiga,<br />although it shouldn&#8217;t look too shabby either.  Possibly the same could be siad<br />of the Atari ST line (but perhaps not the newer models just announced).</p>
<p>   On the other hand, if OS-9/68K becomes available for the Amiga and Atari/ST,<br />then that might be a very superior system.</p>
<p>    Exactly how well Level II and Multi-Vue will perform remains to be seen.  I<br />expect it WILL be a little slow because of the overhead, but there may be ways<br />around it.   I do highly recommend running out of the largeest RAMdisk you can<br />get going, putting most of your CMDS directory into it.  Or, a 10 meg hard disk.<br />I found the LR Tech host adaptor and a 30 meg fast hard disk (Seagate ST4038)<br />would run nearly as fast as a RAMdisk.</p>
<p>    Some notes on Level II: memory management uses an address translator, not<br />bank switching as such to allocate memory.  Each process has up to 64K or so<br />for its own exclusive use, and the system has 64K for modules, descriptors and<br />such which doesn&#8217;t have to be shared with individual programs.  This largely<br />gets around the 64K add<br />ress range of the 6809 apparently with little overhead, though<br />it would be nice to have a larger address range&#8230;</p>
<p>    Folks, including me, speak sneeringly of the Intel uP family and MS-DOS.<br />It DOES have a lot of excellent software and support, and I do use a Leading<br />edge PC for most of my computing right now.  I am hoping that the CoCo3 and<br />Level II will provide an equally powerful environment, lacking only good<br />software<br />support.  I think that the CoCo3 does put us up to about that level of<br />performance, and perhaps a little bit more.</p>
<p>    OS-9 is very similar to Unix, except that it is written in assembly language<br />and is smaller and faster in a given environment (no fair comparing with a VAX!)</p>
<p>     What&#8217;s the bottom line?  Remains to be seen.  Much depends on the software<br />support that the CoCo 3 and Level II will receive in the next couple of years.<br />I think it has a lot of potential, but I speak as a technically-minded hacker<br />and OS-9 user/enthusiast, and perhaps my judgement is abit clouded&#8230;  The<br />system I REALLY want to have is a 68020/30 with 4-16 megs of memory and<br />OS-9/68K, but I expect that won&#8217;t be down to a reasonable level of price and<br />software<br />development for a couple of years yet&#8230;I want some SERIOUS graphics, you see&#8230;<br />    As it stands now, the CoCo 3 offers the potential of about equal performance<br />and price with the PC and lower-end 68000 computers, if we don&#8217;t get too sticky<br />about the matter of software and additional hardware support.  I look forward to<br />having a lot of fun and hopefully some good use out of my system.</p>
<p>     Now, what&#8217;s holding up Level II and Multi-Vue (get cracking, Tandy!!!)</p>
<p>&#8211;Damon</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/02/coco3os-9-level-ii/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS9 patches Re: Msg 23515</title>
		<link>http://www.coco3.com/community/1987/02/re-os9-patches-re-msg-23515</link>
		<comments>http://www.coco3.com/community/1987/02/re-os9-patches-re-msg-23515#comments</comments>
		<pubDate>Mon, 02 Feb 1987 08:29:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/02/re-os9-patches-re-msg-23515/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>23624  2FEB87-0829 Archives<br />     RE: OS9 patches (Re: Msg 23515)<br />     From: MARTYGOODMAN To: ESTIMATE</p>
<p>Bad Mpaks in that way are rare.. but that is a possible<br />explanation.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/02/re-os9-patches-re-msg-23515/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: Level II Re: Msg 23413</title>
		<link>http://www.coco3.com/community/1987/01/re-level-ii-re-msg-23413</link>
		<comments>http://www.coco3.com/community/1987/01/re-level-ii-re-msg-23413#comments</comments>
		<pubDate>Thu, 29 Jan 1987 00:54:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/01/re-level-ii-re-msg-23413/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>23462 29JAN87-0054 Archives<br />     RE: Level II (Re: Msg 23413)<br />     From: PKW          To: WHIFFLE</p>
<p>I would be interested to see the reaction of Mark Siegel when he gets sales<br />reports on the sale of Level II in the month of Feburuary (February, that is.)</p>
<p>BTW, do youknow if the OS9 ram-disk driver for the 512K Disto RAMdisk emulates<br />a 40-track drive EXACTLY or does it need to be patched?</p>
<p>&#8211; pkw</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/01/re-level-ii-re-msg-23413/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: IBM Re: Msg 22954</title>
		<link>http://www.coco3.com/community/1987/01/re-ibm-re-msg-22954</link>
		<comments>http://www.coco3.com/community/1987/01/re-ibm-re-msg-22954#comments</comments>
		<pubDate>Sun, 18 Jan 1987 16:49:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/01/re-ibm-re-msg-22954/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>22989 18JAN87-1649 Archives<br />     RE: IBM (Re: Msg 22954)<br />     From: MARTYGOODMAN To: MBRANT</p>
<p>OS-9 runs only on machines that use 6809&#8242;s or 68000 processors.<br />The IBM PC, with its 8088, cannot run OS-9, other than as<br />a software emulation of the 6809, which would be hidiously<br />slow due to the lousey quality of the 8088 compared to the<br />6809.  A 10 MHz 80286 AT might be able to emulate a 6809<br />at an acceptable speed in software, tho.  Alternatively ,<br />there are one or two hardware cards that have a 6809<br />on them that fit in the PC, and use some of its resources (its<br />keyboard and screen display and I/O.  At present I know of no<br />software emulator for the 6809 on the PC or AT, and doubt<br />anyone would bother to write one.  Afterall, emulators<br />are written for successful and popular microprocessors<br />to run on less popular machines, usually.  Not the other<br />way around!</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/01/re-ibm-re-msg-22954/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: IBM Re: Msg 22954</title>
		<link>http://www.coco3.com/community/1987/01/re-ibm-re-msg-22954-2</link>
		<comments>http://www.coco3.com/community/1987/01/re-ibm-re-msg-22954-2#comments</comments>
		<pubDate>Sun, 18 Jan 1987 15:48:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/01/re-ibm-re-msg-22954-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>22984 18JAN87-1548 Archives<br />     RE: IBM (Re: Msg 22954)<br />     From: DWHILL       To: MBRANT</p>
<p>   There are two coprocessor boards for the PC bus which use a 6809 and can<br />run OS-9.  One was advertised in a recent issue of RAINBOW and another is<br />shortly<br />to be offered on a limited basis locally (Atlanta, GA).  Now that&#8217;s about the<br />only way you can reasonably expect OS-9 to run on a PC, by using a 6809 in the<br />PC to run it!  That will only run programs written for the 6809, not the 8088<br />and other Intel family processors.</p>
<p>    Aside from that, there may be versions of UNIX or unix-like operating<br />systems<br />that will run on an AT (uses a 80286) or an 80386-based machine.  I don&#8217;t follow<br />that very closely, so I&#8217;m clear on what products are being offered.</p>
<p>    Hope this is of some help.</p>
<p>&#8211;Damon</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/01/re-ibm-re-msg-22954-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OS9 patches</title>
		<link>http://www.coco3.com/community/1987/01/os9-patches</link>
		<comments>http://www.coco3.com/community/1987/01/os9-patches#comments</comments>
		<pubDate>Wed, 14 Jan 1987 18:21:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/01/os9-patches/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>22803 14JAN87-1821 Archives<br />     OS9 patches<br />     From: REPNY        To: MARTYGOODMAN</p>
<p>In your January 1987 column in the Rainbow you mentioned some<br />patches for the OS9 CCDISK to allow double sided drives to be<br />used.  What are the file names and which DL are they in?  Can<br />these patches be used with OS9 version 2?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/01/os9-patches/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: Xcom9 Re: Msg 21751</title>
		<link>http://www.coco3.com/community/1987/01/re-xcom9-re-msg-21751</link>
		<comments>http://www.coco3.com/community/1987/01/re-xcom9-re-msg-21751#comments</comments>
		<pubDate>Fri, 02 Jan 1987 23:32:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1987/01/re-xcom9-re-msg-21751/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>21869  2JAN87-2332 Archives<br />     RE: Xcom9 (Re: Msg 21751)<br />     From: JAYTRUESDALE To: WB4GCS</p>
<p>Here is a copy of the xcom9 help screen.</p>
<p>Prefix commands with &#8216;Cntl-Y&#8217; (hex $19)<br />Use &#8216;H&#8217; cmd for Help, &#8216;O&#8217; cmd to show option settings<br />XCom9 prompts for command with Beep?<br />@  Send a break &#8211; 6850 only<br />$  Shell command<br />A  toggle Ascii mode (strip parity,tabs, etc)<br />B  set Baud rate &#8211; needs driver mods<br />E  toggle local Echo mode<br />F  specify Flow ctl (xon/xoff) for modem<br />G  Go begin xmodem sending<br />H  Help &#8211; show this menu<br />M  toggle Modem path enable<br />O  show Option settings<br />Q  Quit &#8211; end XCom9<br />R  Receive a file thru modem port<br />S  Send    a file thru modem port<br />V  toggle View modem data on crt<br />X  start/stop XMODEM protocol<br />CNTL-R  enables/disables writing to Rcv file</p>
<p>This should get you started.</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1987/01/re-xcom9-re-msg-21751/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS9 Interleave vs Step Rate Re: Msg 21335</title>
		<link>http://www.coco3.com/community/1986/12/re-os9-interleave-vs-step-rate-re-msg-21335</link>
		<comments>http://www.coco3.com/community/1986/12/re-os9-interleave-vs-step-rate-re-msg-21335#comments</comments>
		<pubDate>Mon, 29 Dec 1986 00:35:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-os9-interleave-vs-step-rate-re-msg-21335/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>21363 29DEC86-0035 Archives<br />     RE: OS9 Interleave vs Step Rate (Re: Msg 21335)<br />     From: MARTYGOODMAN To: DENNYSKALA</p>
<p>After writing some optimized fast disk duplicators,<br />I am quite familiar with the matter of tuning the interleave<br />to specific dedicated applications.  But of course this involves<br />specially formatted disks.</p>
<p> You seem to have missed the basic question:</p>
<p>   WHAT interleve should be used for formatting ones general<br />purpose OS9 disks?   BASIC uses an interleve of 4 in its<br />format program (RS BASICK).</p>
<p>  In the course of experimenting with differing interleaves<br />for READING sectors, I have found that ultra slow<br />step rates SEEM to cause one to need a different<br />read interleave for a given application.</p>
<p> I can understand your suggesting one mess with the READ<br />interleve for a given application&#8230;</p>
<p>  Bu<br />  BUT, I was asking about what interleave should be<br />used for laying down the sector headers during FORMATTING<br />of the disk.  THAT should be kept the same, I would think,<br />if only to keep one from going crazy!</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-os9-interleave-vs-step-rate-re-msg-21335/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>tsword</title>
		<link>http://www.coco3.com/community/1986/12/tsword</link>
		<comments>http://www.coco3.com/community/1986/12/tsword#comments</comments>
		<pubDate>Sun, 28 Dec 1986 21:50:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/tsword/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>21333 28DEC86-2150 Archives<br />     tsword<br />     From: JAYTRUESDALE To: DALELEAR</p>
<p>Dale:  Here is some further insight in to one of the problems I<br />mentioned with T/S Word&#8217;s Tsfmt.</p>
<p>When adjusting and filling text, if there is a space at the end<br />of a paragraph, an extra blank line is printed.</p>
<p>If within a paragraph, a line ends and has an extra space<br />following a period at the end, this space is interpreted as the<br />end of the paragraph and the justification ends there.</p>
<p>These two problems may be due to the way text is sent to<br />the formatter (Via a pipe) which in turn limits the ability to<br />&#8220;look ahead&#8221; in the text to see what is coming next.</p>
<p>I am using DynaStar to compose my text.  I set the wrap margin to<br />what ever I will be setting the Tsfmt line length to, and do not<br />do any justification in DynaStar.</p>
<p>Would I be having the problems of these extra spaces if I was<br />using T/S Edit?</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/tsword/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Software Registration</title>
		<link>http://www.coco3.com/community/1986/12/software-registration</link>
		<comments>http://www.coco3.com/community/1986/12/software-registration#comments</comments>
		<pubDate>Sun, 28 Dec 1986 00:17:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/software-registration/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>21223 28DEC86-0017 Archives<br />     Software Registration<br />     From: RICKADAMS    To: GREGL</p>
<p>So here I am again, filling out another Tandy Software Registration card,<br />and once again wondering&#8230; does filling these things out do me any good?<br />I&#8217;ve never gotten anything sent back to me in response when I fill out the<br />registration cards for OS-9 software&#8230; this could, of course, mean that<br />there is never any bugs in OS-9 software for them to get back to me on&#8230;<br />(har har chortle snicker).  On the OTHER HAND&#8230;.!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/software-registration/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>OS9 Interleave vs Step Rate</title>
		<link>http://www.coco3.com/community/1986/12/os9-interleave-vs-step-rate</link>
		<comments>http://www.coco3.com/community/1986/12/os9-interleave-vs-step-rate#comments</comments>
		<pubDate>Sat, 27 Dec 1986 10:59:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/os9-interleave-vs-step-rate/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>21152 27DEC86-1059 Archives<br />     OS9 Interleave vs Step Rate<br />     From: MARTYGOODMAN To: OS9 GURUS (NR)</p>
<p>Dear friends:</p>
<p> I need some information about OS-9.</p>
<p> (1) WHAT is the optimum Interleave (&#8220;Skip&#8221;) factor<br />for formatting OS-9 disks?</p>
<p> (2) Does this number depend on the STEP RATE at which you<br />are running your drives?  (I would guess it does to<br />some extent).</p>
<p> (3) A friend of mine running his 40 track single sided<br />drives at 30 ms step rate says the 2 is the optimum<br />interleave factor for formatting OS-9 disks.  Is<br />this so?  And what would be the optimum interleave<br />factor for those of up running OS-9 at 6 ms step rate?</p>
<p> (4) Would the question of whether one is running single<br />or double sided drives also affect the choice of<br />optimum interleave to be used in formatting an OS-9 disk?</p>
<p> I ask these combined hardware/software questions for several<br />reasons:  On general principles I want to learn the answers,<br />but more specifically I am about to modify an existing<br />commercial mas dupe program for ultra fast copying<br />of 40 track (single and double sided) OS-9 disks<br />(using either a 512K CoCo 3 OR a CoCo 1 or 2 equipped<br />with a 512K Disto RAM disk card).</p>
<p>  But need to know what interleave (skip) factor to use<br />in my format program.. and will have to adjust my<br />sector read and write order table accordingly too.</p>
<p>  Thanks much for what help you can give me, in advance!</p>
<p> &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/os9-interleave-vs-step-rate/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os9 kermit uploaded Re: Msg 20664</title>
		<link>http://www.coco3.com/community/1986/12/re-os9-kermit-uploaded-re-msg-20664</link>
		<comments>http://www.coco3.com/community/1986/12/re-os9-kermit-uploaded-re-msg-20664#comments</comments>
		<pubDate>Thu, 25 Dec 1986 15:37:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-os9-kermit-uploaded-re-msg-20664/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>21024 25DEC86-1537 Archives<br />     RE: os9 kermit uploaded (Re: Msg 20664)<br />     From: MARTYGOODMAN To: ROOKY</p>
<p>You ask a lot of questions for a christmas eve!  OK&#8230; here goes:</p>
<p> (1) OS9 Level 1 version 1 will not boot up on the Coco 3.<br />You would have to upgrade to OS9 Level 1 version 2 (a $25 or so upgrade after<br />presenting<br />proof of ownership of Level 1 ver 1 at RS Stores, I am told).</p>
<p> (2) However, there will be NO upgrade policy for OS9 Level II<br />when it comes out, and that will pretty much immediately become<br />the operating system of choice for OS9 types.  This is because<br />OS9 Level II can make use of all of the memory and extra<br />graphics capabilities of the Coco 3.  But, as it is in effect<br />a massive new product and not really an &#8220;upgrade&#8221;, Tandy and<br />Microware decided (not entirely unreasonably) that it should<br />be sold as a separate product and not as an upgrade.<br /> (My own feeling is they should give it away with each disk system,<br />but I doubt Microware or Tandy felt they could afford that).</p>
<p> (3) I&#8217;m not one of the best folks here to ask about OS9, tho<br />I&#8217;ve picked up a little about it.  Our better OS9 authorities<br />include Dale Lear (DALELEAR), Greg Law (GREGL), and Rick Adams<br />RICKADAMS).   Don Hutchison (DONHUTCHISON) seems to be getting<br />rather experienced in OS9 too.  DRIFTER and DWHILL also seem<br />to be rather savvy OS9 users who hang out here often.</p>
<p> (4) As for OS9 and the RS232 pak, OS9 Level 1 Version 2 and<br />OS9 Level II directly support the RS232 pak via T2 drivers.<br />If you don&#8217;t have such a driver I strongly suspect you are<br />using the soon to be totally obsolete OS9 Level 1 ver 1.<br />In general, the RS232 pak requires support software<br />in order to be used.  The ROM priveded with is is total<br />garbage.   Numerous RS DOS programs use the pak, and<br />OS9 directly supports it now via the T2 driver. Several OS9<br />products are available that use it thru that driver.</p>
<p> &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-os9-kermit-uploaded-re-msg-20664/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 TERMINAL PROGRAMS Re: Msg 20992</title>
		<link>http://www.coco3.com/community/1986/12/re-os-9-terminal-programs-re-msg-20992</link>
		<comments>http://www.coco3.com/community/1986/12/re-os-9-terminal-programs-re-msg-20992#comments</comments>
		<pubDate>Wed, 24 Dec 1986 21:08:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-os-9-terminal-programs-re-msg-20992/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20999 24DEC86-2108 Archives<br />     RE: OS-9 TERMINAL PROGRAMS (Re: Msg 20992)<br />     From: GREGL        To: WOODSMITH</p>
<p>Steve,</p>
<p>     I consider Basic09 to be one of the few &#8220;usable&#8221; Basic&#8217;s around.<br />But then again, when you&#8217;re hooked on structured languages, you&#8217;re<br />HOOKED. My biggest gripe with most Basic&#8217;s is that you can&#8217;t express<br />yourself with it and the listing look like junk&#8230; But with Basic09<br />you can actually &#8220;flow&#8221; through a program like water flows through a<br />pipe.</p>
<p>     I&#8217;m using some &#8220;tricks&#8221; with my terminal program to save space,<br />mainly memory&#8230; Yeah, even for Level II. I&#8217;m gonna keep the kermit,<br />and xmodem file transfer stuff in a separate program so that if you<br />want to download via xmodem, it<br />&#8216;ll load and execute &#8220;xmodem&#8221; with the proper parameters and if<br />you then change your mind after performing an xmodem transfer and<br />use kermit instead, it&#8217;ll unlink xmodem and replace it with<br />&#8220;kermit&#8221;. Of course, under Level II I plan on having them both<br />loaded and linked in memory for even faster execution. The way I<br />figure it is, under Level II, each file transfer utility can be<br />allocated up to about 56k, so without the mainline terminal program<br />in the way you can download direct to disk using a much larger buffer.<br />If you look at it like the terminal itself is 13k, xmodem is 13k, and<br />kermit is 13k then that&#8217;s 39k with only roughly 21k left for the variables<br />and buffers. But, with each a separate utility you can have roughly 43k<br />for the variables and buffers for each. And then again, under Level I<br />how can you do anything with the full code being 39k? I don&#8217;t know<br />many people running Level I on the CoCo with 39k, and I only have 41k<br />myself with a STRIPPED boot file.</p>
<p>     You&#8217;ll love it once you get running at 1200 baud, especially when<br />you don&#8217;t have to pay more for it on Delphi! Boy, I just wish I had a<br />2400 baud capable Telenet down here! Yeah Marty, I know, I know, 2400<br />may not be much faster with xmodem but still, it IS faster, especially<br />with BIG uploads. I just uploaded 2000 blocks to a local system here<br />in about 20 minutes compared to about 1 1/2 hours it would take at 300.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-os-9-terminal-programs-re-msg-20992/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: t2 Re: Msg 20871</title>
		<link>http://www.coco3.com/community/1986/12/re-t2-re-msg-20871</link>
		<comments>http://www.coco3.com/community/1986/12/re-t2-re-msg-20871#comments</comments>
		<pubDate>Tue, 23 Dec 1986 05:00:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-t2-re-msg-20871/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20907 23DEC86-0500 Archives<br />     RE: t2 (Re: Msg 20871)<br />     From: MARTYGOODMAN To: DENNYSKALA</p>
<p>This issue has come up many times over the last two years or more:</p>
<p> The port address of the RS232 pak&#8217;s UART chip is fully decoded<br />and as such that chip can be addressed regardless of what slot<br />the RS232 pak is placed in.  To THAT extent the RS232 pak is<br />fully slot independent.</p>
<p>  BUT!!!</p>
<p>  The RS232 pak&#8217;s interrupt control logic is NOT slot independent<br />and the RS232 pak&#8217;s slot MUST be selected for that aspect of it<br />to work (due to incompetent design of the CoCo system bus when<br />the first CoCo was standardized:  They did NOT bring out the<br />IRQ or FIRQ lines to the bus, and instead created this<br />thoroughly obnoxiously kludgy CART line nonsense as a<br />Rube Goldberg way of handling interrupts via the system bus.)<br />Now the CART line is SWITCHED by the slot selector in the Mpak.</p>
<p>  Thus, programs that use the RS232 pak under INTERRUPT control<br />will require that pak to be in a given specific slot.<br />Programs that do NOT make use of that interrupt (like<br />MOST RS DOS CoCo term programs such as Mikeyterm and Greg E Term)<br />will not care at all what slot the pack is in.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-t2-re-msg-20871/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Neat OS-9 Idea</title>
		<link>http://www.coco3.com/community/1986/12/neat-os-9-idea</link>
		<comments>http://www.coco3.com/community/1986/12/neat-os-9-idea#comments</comments>
		<pubDate>Wed, 17 Dec 1986 21:44:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/neat-os-9-idea/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20478 17DEC86-2144 Archives<br />     Neat OS-9 Idea<br />     From: RICKADAMS    To: GREGL</p>
<p>Hey, Greg, I was just thinking.  You know all that extra memory on the<br />Coco 3, which is hanging out there unavailable to us Level I, Version<br />2.0.0?  Wouldn&#8217;t it be nice if someone would write a version of PRINTERR<br />that would somehow load the whole ERRMSG file into unused memory (outside<br />the usual memory map), and then jimmied the system to look up numeric<br />error codes in RAM, instead of churning the disk?</p>
<p>Sure, there are problems.  You&#8217;d have to make sure that the memory usage<br />didn&#8217;t conflict with Mike&#8217;s 80-column driver.  And how would you make sure<br />that some other process wouldn&#8217;t get scheduled to run while the GIME MMU<br />registers were in a wierd state?  (Turn off interrupts briefly while you<br />accessed the other segment(s)?  Voluntarily sleep for a tick?)</p>
<p>Could it be done?  Let&#8217;s kick some ideas around.  Sure, Level II will be<br />here Real Soon Now, but why wait?  And what about those people who opt NOT<br />to go for Level II?  Who wants to tackle this problem?   Note that I don&#8217;t<br />necessarily think that YOU have to do it&#8230;  but does anyone want to<br />volunteer?  (Don&#8217;t look at ME&#8230; I am too blasted BUSY, alas!)</p>
<p>Of course, maybe what I am suggesting is impossible, in which I will<br />slink back into my cave&#8230; and await some bugger doing it anyway!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/neat-os-9-idea/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: os-9 ver 2.00 Re: Msg 20466</title>
		<link>http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20466</link>
		<comments>http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20466#comments</comments>
		<pubDate>Wed, 17 Dec 1986 21:26:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20466/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20473 17DEC86-2126 Archives<br />     RE: os-9 ver 2.00 (Re: Msg 20466)<br />     From: RICKADAMS    To: GREGL</p>
<p>That would have to be a pretty BIG bug in VERIFY that would make it<br />mess up on its whole purpose in life&#8230;  Note that EVERY module that<br />Ernie modified had a bad CRC.</p>
<p>Yeah, he might have used (inadvertently) the on-disk modules with the<br />bad CRC&#8217;s, rather than the fixed versions that he used VERIFY to create.<br />It is possible, I suppose.</p>
<p>Does the percent sign at the end of your message mean that your message<br />was originally composed on a UNIX system?  My messages sometimes have<br />that &#8220;feature&#8221; for that very reason.  Makes me feel pretty foolish&#8230;<br />I really ought to go back and edit them&#8230; but sometimes I&#8217;m just too<br />rushed.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20466/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os-9 ver 2.00 Re: Msg 20450</title>
		<link>http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20450</link>
		<comments>http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20450#comments</comments>
		<pubDate>Wed, 17 Dec 1986 21:21:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20450/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20472 17DEC86-2121 Archives<br />     RE: os-9 ver 2.00 (Re: Msg 20450)<br />     From: RICKADAMS    To: PENROSE</p>
<p>The OS9BOOT that COBBLER writes is from memory.  Rest assured that I think ANY<br />question having to do with generating a new OS-9 boot is a good question.<br />It&#8217;s a very difficult topic to understand and/or master, even for the<br />initiated, and thus this exchange will no doubt help more people than<br />just yourself&#8230; of that you can be sure!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20450/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os-9 ver 2.00 Re: Msg 20208</title>
		<link>http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20208</link>
		<comments>http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20208#comments</comments>
		<pubDate>Tue, 16 Dec 1986 23:28:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20208/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20389 16DEC86-2328 Archives<br />     RE: os-9 ver 2.00 (Re: Msg 20208)<br />     From: RICKADAMS    To: PENROSE</p>
<p>Dale Lear and I were discussing your problem<br />over lunch today, and we both would really like to help you get<br />to the bottom of this.  If you do an IDENT on each module (on disk)<br />referenced in the OS9GEN list, and the CRC&#8217;s for those modules<br />are all correct, then the CRC&#8217;s in the resulting OS9BOOT file<br />really SHOULD all be correct.  So your problem truly has us<br />puzzled, and we love a good puzzle&#8230; especially if we can<br />help it come out all right in the end&#8230;!</p>
<p>One thing you might try is to verify (generate good CRC&#8217;S) the ENTIRE<br />OS9BOOT file by doing your patches in memory, saving modules in memory,<br />etc, then using OS9GEN to generate a new OS9BOOT file on your second<br />drive (onto a freshly formatted disk).  Don&#8217;t worry about the verify step<br />until this point.  When the OS9BOOT (with admittedly bad CRC&#8217;S) has been<br />written to /D1, do the following:</p>
<p>   VERIFY /D1/TEMP U<br />   DEL /D1/OS9BOOT<br />   COPY /D1/TEMP /D1/OS9BOOT</p>
<p>That DEL and then COPY thingie looks wierd, true, but it has to be done that<br />way&#8230; it is a trick to make sure the OS9BOOT file is still contiguous.</p>
<p>Dale and/or myself will stay in touch with you.  It is truly a sad thing that<br />the nastiest, most touchy part about OS9 is the generation of an OS9 boot disk,<br />and yet this is the very thing that all OS9 neophytes are asked to do as their<br />first foray into the (otherwise wonderful, in my opinion) world of OS9.  Not<br />that you are a neophyte, tho&#8230; you sound like you know what you are doing.  As<br />Dan Rather says&#8230; &#8220;Courage!&#8221;</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-os-9-ver-2-00-re-msg-20208/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>RE: XTerm Re: Msg 20114</title>
		<link>http://www.coco3.com/community/1986/12/re-xterm-re-msg-20114</link>
		<comments>http://www.coco3.com/community/1986/12/re-xterm-re-msg-20114#comments</comments>
		<pubDate>Sat, 13 Dec 1986 04:20:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-xterm-re-msg-20114/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20156 13DEC86-0420 Archives<br />     RE: XTerm (Re: Msg 20114)<br />     From: MARTYGOODMAN To: PKW</p>
<p>Actually, if I were to write them, I&#8217;d try to be polite<br />and constructive.  I reserve my most scorching style<br />for forums like this, where it has some entertainment<br />value, both to me and, I hope, to others.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-xterm-re-msg-20114/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: XTerm Re: Msg 20109</title>
		<link>http://www.coco3.com/community/1986/12/re-xterm-re-msg-20109</link>
		<comments>http://www.coco3.com/community/1986/12/re-xterm-re-msg-20109#comments</comments>
		<pubDate>Sat, 13 Dec 1986 04:16:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-xterm-re-msg-20109/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20154 13DEC86-0416 Archives<br />     RE: XTerm (Re: Msg 20109)<br />     From: MARTYGOODMAN To: PKW</p>
<p>We have been told again and again that the ability of OS9 Level II<br />to support windowing, and the further enhancements that<br />Multiview will bring, will allow some DARN fine user interfaces<br />to be easily written under OS9 Level II.  Let&#8217;s hope<br />(1) we actually do eventually SEE those products<br />and (2) what we have heard is so.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-xterm-re-msg-20109/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: Word Processor &amp; terminal Re: Msg 20091</title>
		<link>http://www.coco3.com/community/1986/12/re-word-processor-terminal-re-msg-20091</link>
		<comments>http://www.coco3.com/community/1986/12/re-word-processor-terminal-re-msg-20091#comments</comments>
		<pubDate>Sat, 13 Dec 1986 04:01:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-word-processor-terminal-re-msg-20091/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20151 13DEC86-0401 Archives<br />     RE: Word Processor &#038; terminal (Re: Msg 20091)<br />     From: MARTYGOODMAN To: DWHILL</p>
<p>As best I can tell, Damon, there is NOTHING in the design of the<br />current GIME chip that would preclude the use<br />of 44256 (4 by 256K) chips for the upgrade. Indeed, there is<br />every reason to believe those chips would work just fine.</p>
<p> The only problem is that Tandy did not support this as<br />a drop in upgrade on the mother board, much as it did<br />not support the upgrade using 41256 chips, because 44256&#8242;s<br />are 20 pin devices, and cannot fit in the 18 pin sockets<br />of the 4464 chips currently used on the 128K CoCo 3.</p>
<p>  Tho of course using bent up pins and the like, a hacker<br />could probably install same&#8230; if the 44256 pin out is<br />similar enough to that of the 4464.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-word-processor-terminal-re-msg-20091/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: co380 source Re: Msg 19853</title>
		<link>http://www.coco3.com/community/1986/12/re-co380-source-re-msg-19853</link>
		<comments>http://www.coco3.com/community/1986/12/re-co380-source-re-msg-19853#comments</comments>
		<pubDate>Sat, 13 Dec 1986 01:36:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-co380-source-re-msg-19853/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20141 13DEC86-0136 Archives<br />     RE: co380 source (Re: Msg 19853)<br />     From: DRACMAN      To: MJD</p>
<p>Hello Mike,<br />Its unbelievable that the display is so capable of &#8216;expansion&#8217;<br />and yet TANDY stopped where they did. I have been gathering POKES<br />that make this screen do wonders ! When I do an IDENT -m co80<br />everything checks okay, but if I do an IDENT os9boot, I get<br />**Module header is incorrect ! ** No big thing&#8230; the disk<br />still boots and I&#8217;m F,D,and H with this display, just wondering<br />what might cause that ? Is it because I dumped to the modules<br />directory with a name different than what the os9 loads into<br />memory ?<br />Stephen (DRACMAN)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-co380-source-re-msg-19853/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: XTerm Re: Msg 19861</title>
		<link>http://www.coco3.com/community/1986/12/re-xterm-re-msg-19861</link>
		<comments>http://www.coco3.com/community/1986/12/re-xterm-re-msg-19861#comments</comments>
		<pubDate>Fri, 12 Dec 1986 23:11:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-xterm-re-msg-19861/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>20124 12DEC86-2311 Archives<br />     RE: XTerm (Re: Msg 19861)<br />     From: DENNYSKALA   To: GREGL</p>
<p>Greg,</p>
<p>I&#8217;ve also tried xterm.  I wouldn&#8217;t be quite so harsh about its exterior<br />as Marty, but it is a little terse.  On the other hand, I don&#8217;t think it&#8217;s<br />fair to compare it to a comm program on a 640K machine.  A menu interface<br />costs memory, or annoying disk accesses.  The developers probably wanted<br />to conserve memory for the buffer area.</p>
<p>The manual changing of word length for xmodem is kinda dumb, but then<br />again, xmodem was added after-the-fact in an update.  But there is one<br />other BIG fault with the program which no one has yet mentioned.  That is<br />the fact that when a buffer is attached to a file, it does not automatically<br />get flushed out when you exit the program normally.  That is to say,<br />you have to go to the buffer menu and manually deattach any buffers that<br />are open.  Otherwise, poof when you quit.  Now that&#8217;s annoying!</p>
<p>                            &#8212;&#8211; Dennis &#8212;&#8211;</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-xterm-re-msg-19861/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: XTerm Re: Msg 19846</title>
		<link>http://www.coco3.com/community/1986/12/re-xterm-re-msg-19846</link>
		<comments>http://www.coco3.com/community/1986/12/re-xterm-re-msg-19846#comments</comments>
		<pubDate>Wed, 10 Dec 1986 21:28:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-xterm-re-msg-19846/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19850 10DEC86-2128 Archives<br />     RE: XTerm (Re: Msg 19846)<br />     From: GREGL        To: DONHUTCHISON</p>
<p>Don,</p>
<p>    You need a special cable to run Xterm with XRS232 and XT1 on the<br />serial port. This is a simple cable and the contruction can be made<br />from an existing serial cable and the pinout is as follows:</p>
<p>         COCO                    MODEM<br />         GND   &#8212;&#8212;&#8212;&#8212;&#8212;    GND<br />         Txd   &#8212;&#8212;&#8212;&#8212;&#8212;    Txd<br />         Rcd   &#8212;&#8212;&#8212;&#8212;&#8212;    Rcd<br />         Rdy   &#8212;&#8212;-/           Rdy</p>
<p>The easiest way to do this would be to pull apart the end of the cable at the<br />modem, remove pin 1 (yellow) and strap it to pin 2 (green). You&#8217;ll notice that<br />with this setup, every time a character comes in to the serial port it will<br />cause the Ready line to change states which causes a FIRQ interrupt. This is how<br />XTerm can run higher baud rates on the bit-banger port. I will tell you for a<br />fact that it is well worth the effort to make this cable but it SHOULD have been<br />include with the package. You might want to give Microtech a call and see if<br />they goofed with your order because the DID include the special cable when I<br />ordered mine. That was a long time ago and they may not be including the cable<br />with the package now but I&#8217;d check just to be sure.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-xterm-re-msg-19846/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>RE: Word &amp; processor Re: Msg 19738</title>
		<link>http://www.coco3.com/community/1986/12/re-word-processor-re-msg-19738</link>
		<comments>http://www.coco3.com/community/1986/12/re-word-processor-re-msg-19738#comments</comments>
		<pubDate>Tue, 09 Dec 1986 23:47:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-word-processor-re-msg-19738/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19785  9DEC86-2347 Archives<br />     RE: Word &#038; processor (Re: Msg 19738)<br />     From: GREGL        To: PENROSE</p>
<p>I have my shopping list all made out&#8230; (in this order)</p>
<p>     CoCo 3<br />     Multi-pak upgrade<br />     OS-9 Level II<br />     Developers package<br />     Multi-vue (if a separate item)<br />     Magnovox 8515 monitor</p>
<p>As you can see, the RGB monitor is my last purchase as well. I&#8217;ve got a BMC<br />green screen right now that is super sharp for 80 column text and monochrome<br />graphics and I&#8217;ll live with that until I finish feeding the bill collectors.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-word-processor-re-msg-19738/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: New Story Re: Msg 19698</title>
		<link>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19698</link>
		<comments>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19698#comments</comments>
		<pubDate>Tue, 09 Dec 1986 09:09:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-new-story-re-msg-19698/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19727  9DEC86-0909 Archives<br />     RE: New Story (Re: Msg 19698)<br />     From: MARTYGOODMAN To: ANA</p>
<p>I use procomm on my IBM PC clone, and like it immensely.</p>
<p>  On my CoCo I use Mikeyterm currently, but when<br />I get it fixed up I may switch later to Greggie term<br />or Ricky-term</p>
<p>   &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19698/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: New Story Re: Msg 19690</title>
		<link>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19690</link>
		<comments>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19690#comments</comments>
		<pubDate>Tue, 09 Dec 1986 09:00:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-new-story-re-msg-19690/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19723  9DEC86-0900 Archives<br />     RE: New Story (Re: Msg 19690)<br />     From: MARTYGOODMAN To: ROBERTT</p>
<p>The packaging on IBM software often involves high quality printed<br />manuals of many hundreds of pages.  The software is often<br />many times more sophisticated, and therefore more COSTLY<br />to DEVELOP, than CoCo Software.  Finally, advertising<br />costs in the IBM PC world are easily ten fold greater<br />than costs in the CoCo world.  There is also the<br />factor that IBM PC owners went out and spent $1000<br />to $3000 for their initial investment in their machine..<br />as opposed to $100 to $500 in the case of CoCo owners.<br />Therefore they are more LIKELY to be willing and able to<br />spend more on software.</p>
<p>  Thus, IBM software costs more in part because much of it<br />IS better than CoCo software, and in part because<br />it costs more to be in the market, and in part because<br />the buyers are willing to pay a bit more.</p>
<p>  Overall, tho, IBM software tends to be far more<br />professional than the stuff we have for our CoCo..<br />certainly in most of the major categoriers (Terminal<br />software, Wordprocessing software, Data Base software<br />and Spread Sheet software).</p>
<p> But IBM hardware from Taiwan is FAR cheaper than<br />CoCo hardware accessories&#8230; and usually of better<br />quality too.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19690/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: Word Processor &amp; terminal Re: Msg 19648</title>
		<link>http://www.coco3.com/community/1986/12/re-word-processor-terminal-re-msg-19648</link>
		<comments>http://www.coco3.com/community/1986/12/re-word-processor-terminal-re-msg-19648#comments</comments>
		<pubDate>Tue, 09 Dec 1986 08:43:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-word-processor-terminal-re-msg-19648/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19722  9DEC86-0843 Archives<br />     RE: Word Processor &#038; terminal (Re: Msg 19648)<br />     From: MARTYGOODMAN To: PENROSE</p>
<p>All of the assembled and tested 512K upgrades that I know of<br />that either are released (the Radio Shack one<br />and the PBJ one, sold by Spectrum Projects and a host<br />of other CoCo suppliers) cost $130 to $150.<br />The two that I know of that are to be released later<br />(J&#038;R board and Disto CRC board) will also be in this price<br />range.</p>
<p>  Note&#8230; the 16 41256 chips alone cost $40 or more<br />to the supplier.  Then they have to pay for the board,<br />the sockets, the caps, the connectors, and the labor<br />of assembling the thing and TESTING it too.  Finally,<br />the thing has to be sold at a sufficient mark up<br />to pay for the advertisements, and allow for<br />a dealer mark up.  All of this considered, I would<br />say it is unlikely the cost of the 512K upgrade<br />will come down much in the immediate future.</p>
<p>  Hackers, tho, will eventually be able to<br />buy a BARE 512K upgrade board (from J&#038;R, and<br />possibly from Disto too&#8230; Tony was 50-50<br />on this the last time I spoke to him).<br />The price will be $40 or less for this.</p>
<p>  Overall it is the obscenely nasty design of the<br />CoCo 3, its requirement for a plug in board to upgrade<br />the memory&#8230; that forces the cost of an upgrade<br />to be three times what it would be if the thing<br />had been desiged with the needed sockets on the mother<br />board.  I am disgusted with Tandy&#8217;s decision in this<br />regard.</p>
<p>  The oft-repeated &#8220;Tandy Party Line&#8221; &#8220;explanation&#8221;<br />of why they did not put sockets on the mother<br />board is &#8220;the board was too small to fit them all&#8221;.<br />This is a lie.  The board could have been extended<br />an extra inch or so toward the keyboard with<br />no design problems at all, and if this had<br />been done they could have fit all the sockets<br />they&#8217;d need.</p>
<p>  Their making the upgrade so it has to cost three to four<br />times as much as a drop in chip upgrade would is one<br />more example, I feel, of the incompetence of the<br />folks at Fort Worth.  In saying this I am being<br />charitable to them&#8230; for the alternative<br />explanation is that they deliberately and cynically<br />wanted to soak their customers.</p>
<p>    &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-word-processor-terminal-re-msg-19648/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: CO380 with Stylo Re: Msg 19581</title>
		<link>http://www.coco3.com/community/1986/12/re-co380-with-stylo-re-msg-19581</link>
		<comments>http://www.coco3.com/community/1986/12/re-co380-with-stylo-re-msg-19581#comments</comments>
		<pubDate>Mon, 08 Dec 1986 21:18:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-co380-with-stylo-re-msg-19581/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19657  8DEC86-2118 Archives<br />     RE: CO380 with Stylo (Re: Msg 19581)<br />     From: MJD          To: GREGL</p>
<p>I have fI have found the bug in co380 for the home control<br />code.  To correct change offset 201 from 80 to 08.  This is for v1.1 and<br />v1.1b.  You can do this with the following command:<br />   debug<br />   l co80<br />   . .+201<br />   =08<br />   q<br /> I&#8217;ll upload an update by the end of the week.<br />Sorry for any problems.<br />   Have fun,  Mike Dziedzic</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-co380-with-stylo-re-msg-19581/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: CO380 with Stylo Re: Msg 19382</title>
		<link>http://www.coco3.com/community/1986/12/re-co380-with-stylo-re-msg-19382</link>
		<comments>http://www.coco3.com/community/1986/12/re-co380-with-stylo-re-msg-19382#comments</comments>
		<pubDate>Sat, 06 Dec 1986 16:36:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-co380-with-stylo-re-msg-19382/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19409  6DEC86-1636 Archives<br />     RE: CO380 with Stylo (Re: Msg 19382)<br />     From: GREGL        To: MJD</p>
<p>Stylograph III (latest version that I have) is configurable for their own<br />hires 51&#215;24 screen, O-Pak, WordPak running WordPak control codes and now<br />for Co80 using Radio Shack control codes. There you have, 4 different way<br />to run Stylo, not just the one as you had heard. You may want to wait if<br />you do buy Stylo and get the Level II version instead which can be configured<br />for just about any terminal on the market, including Co80.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-co380-with-stylo-re-msg-19382/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os-9 &amp; disks Re: Msg 19389</title>
		<link>http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19389</link>
		<comments>http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19389#comments</comments>
		<pubDate>Sat, 06 Dec 1986 16:17:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19389/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19405  6DEC86-1617 Archives<br />     RE: os-9 &#038; disks (Re: Msg 19389)<br />     From: GREGL        To: PENROSE</p>
<p>Seems that the only real difference is that you got frustrated by trying to<br />run OS-9 off one drive and I went out and purchased two 80 track DSQD drives<br />and then finally a hard disk. You&#8217;ll find OS-9 much easier off of double-sided<br />drives but you must watch out for one very critical point:</p>
<p>You CANNOT boot off of a double sided drive UNLESS you run some type of program<br />such as bootfix on that drive.</p>
<p>Very typical of situations would be you finally got the 40 track DSDD patches<br />in and you now want to create a fully capable boot disk with all of your<br />CMDS and etc. directories on it. What you would do is usually as follows:</p>
<p>OS9:format /D0 R &#8220;OS-9 System Master&#8221;</p>
<p>OS9:cobbler /D0</p>
<p>OS9:bootfix /D0; * VERY IMPORTANT</p>
<p>If you fail to do that last step you will find yourself with a bootdisk that<br />will not boot. Worse yet, if you have already copied all of your files over<br />to this disk you must now start all over again from scratch. This is the only<br />pitfall you may run into. It happened to me until I figured it out by reading<br />the documentation, hehe.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19389/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 &amp; disks Re: Msg 19387</title>
		<link>http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19387</link>
		<comments>http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19387#comments</comments>
		<pubDate>Sat, 06 Dec 1986 16:11:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19387/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19404  6DEC86-1611 Archives<br />     RE: OS-9 &#038; disks (Re: Msg 19387)<br />     From: GREGL        To: PENROSE</p>
<p>I&#8217;m not sure at the moment. Let me look through the manual real quick and<br />see just how it&#8217;s &#8216;sposed to be done&#8230;<br />Ok Penrose, the first thing you will want to go is to get into the editor via<br />a slash command, &#8216;/EDIT&#8217; and then use FETCH, &#8216;/FETCH&#8217; and it will ask you<br />for the filename to get. A quick scenario would be as follows:<br />FORUM> reply</p>
<p>TO: <cr></p>
<p>Enter text now. Use ^Z to Exit&#8230;.<br />/EDIT<br />/FETCH<br />Enter filename: reply.txt</p>
<p>You should then be reported with the number of lines in the message. Notic<br />if you include a semicolon in the filename, as in &#8216;reply.txt;1&#8242; you are<br />actually specifying the revision number if there are more than one file with<br />the same filename. Generally, don&#8217;t use revision numbers if there is only one<br />such filename in you workspace or if you want the last one uploaded of the<br />same filename.</p>
<p></cr></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19387/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: Last    Word Re: Msg 19332</title>
		<link>http://www.coco3.com/community/1986/12/re-last-word-re-msg-19332</link>
		<comments>http://www.coco3.com/community/1986/12/re-last-word-re-msg-19332#comments</comments>
		<pubDate>Sat, 06 Dec 1986 01:49:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-last-word-re-msg-19332/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19350  6DEC86-0149 Archives<br />     RE: Last    Word (Re: Msg 19332)<br />     From: GREGL        To: DENNYSKALA</p>
<p>I agree that Last Word is a totally useless word processor for anything<br />besides laughing at&#8230; Here&#8217;s the biggest quirk that I dislike, and the<br />one I use QUITE OFTEN. Want to Mark a block for removal, moving somewhere<br />else or copying? Well, you are limited to approximately one 80&#215;24 screen<br />full at one time!</p>
<p>Dennis, have you scrolled backward? Do this next time you fire it up.<br />Get into a good sized file (10k or so) and move all the way to the<br />end of the file. Then do a &#8216;Top of File&#8217;&#8230; It takes quite a bit of<br />time seeing as how LWord copies the original file BACKWARDS! That&#8217;s<br />right, the first byte in the file is now the last byte in the file!<br />You don&#8217;t see this on the screen, but you will if you list out the<br />&#8216;lw.scratch&#8217; file.</p>
<p>I&#8217;m a humping on my word processor and hope to have it running before<br />too much longer. Ie, another year as it would appear&#8230;. But don&#8217;t get<br />discouraged as I&#8217;m continually at it. As soon as I get the user-interface<br />all figured out, the rest should flow along nicely.</p>
<p>I&#8217;m switching between the word process and the BBS at the moment as I&#8217;m<br />trying to get them both finished by 1988, hehe.</p>
<p>I&#8217;m currently working on the message bases of the BBS. It&#8217;ll have up to<br />25 separate message bases and each message is variable length. Meaning<br />that if you type in a message that&#8217;s 10 characters long, it&#8217;ll only<br />take up 11 bytes of disk space with the extra one being a NULL for a<br />terminator. I find this to be very pleasing especially since there are<br />a lot of people who like to type in messages like Whiffle does with<br />stuff like &#8216;Ok, see you there.&#8217; or &#8216;Have a happy.&#8217; or &#8216;No&#8217;&#8230; Hehe,<br />short, sweet, and too the point&#8230; Then there are a few that are like<br />me and Marty&#8230; Each message is like a novel. I thought you&#8217;d agree<br />with that&#8230;</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-last-word-re-msg-19332/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os-9 Re: Msg 19316</title>
		<link>http://www.coco3.com/community/1986/12/re-os-9-re-msg-19316</link>
		<comments>http://www.coco3.com/community/1986/12/re-os-9-re-msg-19316#comments</comments>
		<pubDate>Sat, 06 Dec 1986 01:35:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-os-9-re-msg-19316/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19348  6DEC86-0135 Archives<br />     RE: os-9 (Re: Msg 19316)<br />     From: GREGL        To: DWHILL</p>
<p>There are reasons for getting &#8217;003 Warnings&#8217; but they are NOT significant.<br />If you assembly the file with listings turned on &#8216;asm file.asm l&#8217; then you<br />will see a column in between the line numbers and the hex values that will<br />contain information characters like &#8216;E&#8217; for Error followed by a description<br />or &#8216;W&#8217; for Warning. There are two reasons for getting a Warning:</p>
<p>   1) You used a LBRA where a BRA will work<br />   2) You are accessing data outside of your program area.</p>
<p>These are meant to be programmer messages to kind of flag your mind that<br />you may be able to shorted the code by using BRA, BSR, BEQ, and etc.<br />instead of the Long (4 byte) versions. Also, it gives you a hand when<br />you attempt to access data outside of your programming area. For example,<br />if you were writing a device driver you would probably use something<br />like:</p>
<p>        LDA   #$00        Get value<br />        STA   $FF69       Clear the status register</p>
<p>Since $FF69 is not in your definitions of the data memory area Asm will<br />flag an error that simply means, &#8216;Are you sure you want to store data<br />at this address as you MIGHT destroy something important.&#8217; so kind of<br />take these Warnings in stride but be glad that they are there in case you<br />do really make a typo and overwrite the direct page or such and cause<br />OS-9 to crash. In these cases the warning may save hours of debugging<br />to find out why to find out that you used &#8216;Buffer,pcr&#8217; instead of<br />&#8216;Buffer,u&#8217; which are two TOTALLY different things. Oh yes, it will<br />most certainly flag an error on any attempt to store data into PCR<br />offsets instead of U offsets.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-os-9-re-msg-19316/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 &amp; disks Re: Msg 19268</title>
		<link>http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19268</link>
		<comments>http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19268#comments</comments>
		<pubDate>Fri, 05 Dec 1986 19:10:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19268/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19280  5DEC86-1910 Archives<br />     RE: OS-9 &#038; disks (Re: Msg 19268)<br />     From: GREGL        To: PENROSE</p>
<p>A very hand set of utilities you will be looking for to use all of the 40<br />tracks and two heads is SDisk available from D.P. Johnson. I&#8217;m using SDisk<br />with my two 80 track DSQD drives and it is excellent. It can read and write<br />CoCo OS-9, Standard OS-9, Japanese OS-9, etc. although you probably need<br />never worry about that. I think this kit of software is $35 and they have<br />done me a world of good and I don&#8217;t have any complaints with it.</p>
<p>Just to be fair, Computerware is also selling Disk Fix and Utilities that<br />can read/write 40 track DSDD drives and includes one VERY HANDY utility<br />called Patch. This utility allows you to do just that to any disk file<br />that you have. You can dump the file or a selected portion, modify bytes<br />in hex, ASCII, or ASCII with the high bit set, search for a two byte hex<br />value, and even update the CRC of a module without ever copying the file.</p>
<p>You will also need one other utility to allow the double sided disk to<br />be bootable since DOS expects the boot file to be on one side of the<br />disk only. DP Johnson seels BootFix to do this and if I remember correctly<br />such a utility is included with the Computerware utilities.</p>
<p>If you want my opinion I would buy both packages, I did, and found that<br />Patch on the Computerware disk was worth the price of the package even<br />though I use the SDisk drivers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-os-9-disks-re-msg-19268/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: New Story Re: Msg 19262</title>
		<link>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19262</link>
		<comments>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19262#comments</comments>
		<pubDate>Fri, 05 Dec 1986 18:31:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-new-story-re-msg-19262/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19273  5DEC86-1831 Archives<br />     RE: New Story (Re: Msg 19262)<br />     From: DOCTORASCII  To: WHIFFLE</p>
<p>Which 400 pages of essential informatio will be trashed?  The CoCo 3 manual,<br />e.g. reveals little about the internals of that machine wheras the CoCo I<br />manual at least gave some infomation &#8220;for assembly language users&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19262/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: New Story Re: Msg 19220</title>
		<link>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19220</link>
		<comments>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19220#comments</comments>
		<pubDate>Thu, 04 Dec 1986 22:40:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-new-story-re-msg-19220/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19230  4DEC86-2240 Archives<br />     RE: New Story (Re: Msg 19220)<br />     From: GREGL        To: 6809ER</p>
<p>Here, look at the manual and figure it out&#8230;</p>
<p>type=h    For external devices, type is used for ACIA initialization<br />          values (hexadecimal).  The default=00. Bits 5-7 se either<br />          MARK, SPACE, or no parity on all devices. Codes for these are:</p>
<p>                000 = no parity<br />                101 = MARK parity<br />                111 = SPACE parity<br />                011 = even parity<br />                001 = odd parity</p>
<p>          Bits 0-3 are reserved for future use.</p>
<p>          Bit 4 selects auto-answer modem support features:<br />               1 = on<br />               0 = off</p>
<p>baud=h    Sets baud rate, word length, and stop bits for software<br />          controllable interface. The numeric coes for baud rate are:<br />          0=6E, 1=12C, 2=258, 3=4B0, 4=960, 5=12C0, 6=2580, 7=4B00</p>
<p>          Bits 0-3 determine baud rate<br />          Bit 4 is reserved for future use<br />          Bits 5-6 determine word length<br />             00 = 8 bits<br />             01 = 7 bits<br />          Bit 7 determines the number of stop bits:<br />              0 = 1 stop bit<br />              1 = 2 stop bits</p>
<p>Look at this (exactly as in the 02.00.00 update manual) and tell me what<br />the value is for 2400 baud&#8230; From this idiotic table you&#8217;ll never guess<br />that it&#8217;s supposed to be 4! Fortunately I have these values memorized<br />and didn&#8217;t have any trouble with all of those typos. Next problem, once<br />you get all the values figured out, in binary, convert them to hexadecimal.<br />This is asking TOO much for a novice, and even some experienced users!<br />It is this kind of trash that is going to create OS-9 converts, like the<br />kind that used OS-9 and thought it was too hostile. Mind you, I love<br />OS-9 very dearly but there&#8217;s just got to be a better way.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19220/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: New Story Re: Msg 19188</title>
		<link>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19188</link>
		<comments>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19188#comments</comments>
		<pubDate>Thu, 04 Dec 1986 22:29:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-new-story-re-msg-19188/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19229  4DEC86-2229 Archives<br />     RE: New Story (Re: Msg 19188)<br />     From: GREGL        To: MARTYGOODMAN</p>
<p>Marty, there was some changes made inbetween 01.00.00 and 02.00.00&#8230; Somewhere<br />along<br />the way all that got modified, I think in 01.00.00 was where it was<br />changed. But in the beginning, if you attempted to access a non-existant<br />drive that you had a descriptor for or to access a valid drive that<br />did not have a floppy in it, it would time out in about 2 seconds or<br />so. No more, it will now sit there supposedly waiting for you to insert<br />a floppy into the drive. This is handy in some cases but I much prefered<br />to have it time out as I&#8217;ve had the same thing happen to me quite a few<br />times. In order to save the hassles and to free up more memory I finally<br />completely removed the floppy driver from the boot file. The only drivers<br />I now have are for H0 and TERM. I keep the other stuff in the CMDS directory<br />for those moments when I need them and then I load them. This would be a<br />very big pain if you were running off of floppies. OS-9 indeed is a hard<br />disk environment and any attempt to run it off floppies is anything but<br />easy. I tried it for more than a year with 80 track double-sided drives<br />and I still didn&#8217;t have enough room. My CMDS directory alone fills two<br />80 trackers on both sides&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19188/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>RE: New Story Re: Msg 19186</title>
		<link>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19186</link>
		<comments>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19186#comments</comments>
		<pubDate>Thu, 04 Dec 1986 22:22:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-new-story-re-msg-19186/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19227  4DEC86-2222 Archives<br />     RE: New Story (Re: Msg 19186)<br />     From: GREGL        To: MARTYGOODMAN</p>
<p>Are you asking yourself why I aw<br />always use C for my programming stuff&#8230; #include &#8220;MODULES/Disk.io&#8221;&#8230;.<br />#include &#8220;MODULES/Keyboard&#8221;&#8230; #include &#8220;MODULES/acia.io&#8221; etc. It makes<br />life a lot easier. I&#8217;m trying to keep together a set of utilities that<br />can be included for such mundane tasks, after all, who wants to keep<br />re-inventing the wheel. The OS-9 assembler makes it a little easier<br />as well seeing as how it allows you to include files via &#8220;use&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19186/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: New Story Re: Msg 19121</title>
		<link>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19121</link>
		<comments>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19121#comments</comments>
		<pubDate>Thu, 04 Dec 1986 21:44:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-new-story-re-msg-19121/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19222  4DEC86-2144 Archives<br />     RE: New Story (Re: Msg 19121)<br />     From: 6809ER       To: WHIFFLE</p>
<p>Bob, Why would Tandy want to kill off a computer that out sold the Amiga (total<br />sales) in just the first 1.5 weeks????</p>
<p>Why would Tandy Want to kill off a computer that out sold the first year run<br />of the color computer one in just it&#8217;s first three weeks????</p>
<p>True, most of the first color computer 3 where sold to Color Computer 1/2 owners<br />. But the software will be there when the system needs to stand on it!<br />It takes time to write this new software. (most of what we are trying to do<br />has never been done on a computer that cost less then $3000.00)</p>
<p>Beside, if it takes Tandy a little while to come out with the new software<br />then just what much more $$$ for the third party software houses out there.<br />Right?</p>
<p>Steve Bjork</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-new-story-re-msg-19121/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: bouncing ball demo Re: Msg 19089</title>
		<link>http://www.coco3.com/community/1986/12/re-bouncing-ball-demo-re-msg-19089</link>
		<comments>http://www.coco3.com/community/1986/12/re-bouncing-ball-demo-re-msg-19089#comments</comments>
		<pubDate>Thu, 04 Dec 1986 21:17:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-bouncing-ball-demo-re-msg-19089/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19218  4DEC86-2117 Archives<br />     RE: bouncing ball demo (Re: Msg 19089)<br />     From: 6809ER       To: DONHUTCHISON</p>
<p>If you what to add color to my boucing ball program just change the Shape<br />file. But will take some time to update this 16k file. (It took a Color<br />Computer about 3 hours to create it in the first place.)</p>
<p>I will be starting on a new Boucing Ball program for the Color Computer 3<br />(under Os-9 level two) will a ful rainbow of colors! I hope to have it<br />done in time for the Color Expo 87 in January.</p>
<p>Steve Bjork</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-bouncing-ball-demo-re-msg-19089/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>T/S Word</title>
		<link>http://www.coco3.com/community/1986/12/ts-word</link>
		<comments>http://www.coco3.com/community/1986/12/ts-word#comments</comments>
		<pubDate>Thu, 04 Dec 1986 20:54:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/ts-word/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>19214  4DEC86-2054 Archives<br />     T/S Word<br />     From: JAYTRUESDALE To: DALELEAR</p>
<p>Dale:  Just a few quick quick comments on TS Word since you&#8217;re taking<br />notes&#8230;</p>
<p>It would be nice (but not essential) if there were some provision to<br />insert the date and/or time in the header and/or footer.  I am<br />curently working on a paper and a easy time/date stamp would be quite<br />nice to tell all these versions and drafts apart!  Now I just type the<br />info in by hand.</p>
<p>The capability of two lines of headers and footers would be nice.</p>
<p>When you use .nx to get the next section of the document, the next<br />file starts at the top of a new page.  I think this is a mistake as a<br />logical break in a document may not be at the top of a new page.  I am<br />breaking up my current file for reasons other than the start of a new<br />section, and this creates a problem.  What I will probably do in this<br />case is to merge all the files together before I do the final print.<br />If someone wants a new file to start at the top of a new page they can<br />insert a .bp directive.</p>
<p>I am entering my text using Dynastar on a Wordpak II.  I have DS set<br />to the line length I will be printing at.  I am not justifying with<br />DS, just word wrapping.  I let TSFMT do the filling and justification.<br />I found one problem/bug with this approach.  If there is a period at<br />the end of a text line that is followed by two spaces, TSFMT<br />interprets this as the end of a paragraph and does not do any filling<br />or justification for that line.  If one of the two spaces after the<br />period is deleted, then the filling &#038; justification works just fine<br />and the line is properly justified and filled using text from the<br />following line if needed.</p>
<p>Please note that I am not complaining or anything, I can (and am) work<br />around all of these items, I&#8217;m just pointing them out to you for your<br />information and consideration.</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/ts-word/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: T/S WORD Re: Msg 18977</title>
		<link>http://www.coco3.com/community/1986/12/re-ts-word-re-msg-18977</link>
		<comments>http://www.coco3.com/community/1986/12/re-ts-word-re-msg-18977#comments</comments>
		<pubDate>Mon, 01 Dec 1986 23:38:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/12/re-ts-word-re-msg-18977/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18986  1DEC86-2338 Archives<br />     RE: T/S WORD (Re: Msg 18977)<br />     From: JAYTRUESDALE To: DALELEAR</p>
<p>Dale:  Got a couple of T/S Word questions.</p>
<p>1.  Is there any way to put comments in to a source file?  From<br />my experimenting it appears as though undefined formatting<br />directives (such as .co) are ignored and replaced with a blank<br />line in the printed output.</p>
<p>2.  It looks like T/S Word always puts two spaces after a<br />period, which is fine in ordinary text, and is a feature that<br />is lacking in Dynastar.  I&#8217;m typing up my bibliography and<br />there are two spaces after my abbreviation for volume (vol.),<br />and after author initials (Strecker, W. D. for example) when I<br />print it through TSFMT.  Is there any way to turn this feature<br />off?  I looked through the manual and didn&#8217;t find any way to do<br />this.</p>
<p>Thanks in advance.</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/12/re-ts-word-re-msg-18977/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 Kermit Re: Msg 18888</title>
		<link>http://www.coco3.com/community/1986/11/re-os-9-kermit-re-msg-18888</link>
		<comments>http://www.coco3.com/community/1986/11/re-os-9-kermit-re-msg-18888#comments</comments>
		<pubDate>Sun, 30 Nov 1986 17:33:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os-9-kermit-re-msg-18888/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18907 30NOV86-1733 Archives<br />     RE: OS-9 Kermit (Re: Msg 18888)<br />     From: GREGL        To: MEGABYTE</p>
<p>Ten years, I want an Xmodem free world now, hehe&#8230; By the way Mark, if you<br />do any patches to Kermit, there are two that I definitely want to see in<br />there at any cost&#8230; Make it possible to perform an <esc>R to receive and<br />an </esc><esc>S to send files withut having to go to the shell and forking anew<br />kermit&#8230; Would definitely make my fingers a lot more appreciative.</p>
<p>One more Kermit question for you, actually a Delphi question for any one<br />that knows. Is it possible to download more than one file at a time from<br />DATABASES wiht Kermit? I tried using several different means but they all<br />download one file at a time and Delphi reports &#8220;Status: 1 file downloaded&#8221;<br />so it appears to be possible. Perhaps I&#8217;ll have to drag out the Delphi<br />handbook and see if it is in there.</p>
<p></esc></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os-9-kermit-re-msg-18888/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os9 kermit uploaded Re: Msg 18542</title>
		<link>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-18542</link>
		<comments>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-18542#comments</comments>
		<pubDate>Sat, 29 Nov 1986 18:24:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-18542/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18817 29NOV86-1824 Archives<br />     RE: os9 kermit uploaded (Re: Msg 18542)<br />     From: MEGABYTE     To: GREGL</p>
<p>Greg,<br />ex: &#8220;kermit -sl /t2 file&#8221; The &#8220;S&#8221; say send and the &#8220;L&#8221; is the<br />line paramater and it means &#8220;do th send on the spcified line&#8221;, in<br />this case /t2.  Whne kermit is local, you don&#8217;t need thatas it sends<br />and recives from/to the keyboard.  Note that the order of the options<br />to kermit IS important.  &#8220;kermit -sl /t2 file&#8221; and &#8220;kermit -sl file /t2&#8243;<br />meab two very different things!!!</p>
<p>2nd, here on delphi, there are 3 kermit commands. The two most<br />important are &#8220;kup&#8221; and &#8220;kdown&#8221; which up and download using kermit.<br />The single command &#8220;kermit&#8221; puts you in &#8220;server&#8221; mode, sort of remote<br />control kermit.  In order to end kermit on delphi&#8217;s side, you have to<br />issue a &#8220;kermit -ql /t2&#8243; command to send a &#8220;quit&#8221; signal to delphi.<br />in Order to send files, you do the standard &#8220;kermit -sl /t2 file&#8221;, BUT<br />in order to get files from a kermit server, you must use the &#8220;kermit -gl</p>
<p>Ho<br />hope thishelps</p>
<p>&#8212;Mark S.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-18542/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: coco3 and co80 Re: Msg 18772</title>
		<link>http://www.coco3.com/community/1986/11/re-coco3-and-co80-re-msg-18772</link>
		<comments>http://www.coco3.com/community/1986/11/re-coco3-and-co80-re-msg-18772#comments</comments>
		<pubDate>Sat, 29 Nov 1986 03:40:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-coco3-and-co80-re-msg-18772/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18774 29NOV86-0340 Archives<br />     RE: coco3 and co80 (Re: Msg 18772)<br />     From: MARTYGOODMAN To: KDARLING</p>
<p>Kevin,</p>
<p>  certainly two of those RS mini RAM boards COULD be used by<br />a hacker to kludge up their own 512K upgrade board&#8230;<br />I know a chap (the same feller who got ME my copy of that<br />CoCo 3 schematic) who tried to kludge one up after<br />chopping out two rows of 8 DRAM sockets from some defunct<br />piece of Tandy hardware.  But this approach is HIEDOUSLY time<br />consuming.  Considering at least THREE vendors will be supplying<br />512K upgrades, and at least one of them (and probably soon at least<br />two) will be making BARE boards available for at most $40 each,<br />I suspect THAT will become the way to go.  Certainly it is not worth<br />MY time to hassele building one prototpye from scratch.</p>
<p>  On the other hand, it probably will not be hard for a technically<br />oriented chap at any club to run off a few dozen PC boards of his<br />own for the club.  One will assume the chap will lay out his own<br />board as opposed to pirate the pattern from one of the available<br />commercial boards.  Tho if price competition ever causes the<br />cost of a bare board to drop to much below $40, it hardly will<br />pay for ANYONE to make their own.</p>
<p>  By the way, in correction of what I just wrote&#8230;</p>
<p>  I did not mean thre VENDORS, I meant three totally separate<br />DESIGNERS will be introducing 512K boards&#8230; there will<br />be MANY vendors handling one or another of those three<br />different 512K boards.</p>
<p>  Consider that the cost of producting one totally bare<br />512K board is certainly under $10 if one is doing it<br />in quantity of 1000 or more.  The usual markup from<br />production cost to retail sale price is a factor of three to<br />four, placing the likely sale price of such bare boards in the<br />$30 to $40 range, assuing anyone will be selling such an item.<br />And I have reason to believe that not one but perhaps two<br />differnt third party 512K boards will be sold as such.<br />But for now I doubt the retail price will drop much below<br />$40 for the bare board.  Note that the chips to populate<br />it cost $48, and that is not counting the sockets and<br />the dozen or more needed capacitors.  So, even for a hacker,<br />I suspect the 512K upgrade will not cost much less than $90<br />for a good long while.  Unless the price of chips drops dramatically.<br />At present the price of chips seems pretty stable.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-coco3-and-co80-re-msg-18772/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OS-9 Version 2.0 Boot</title>
		<link>http://www.coco3.com/community/1986/11/os-9-version-2-0-boot</link>
		<comments>http://www.coco3.com/community/1986/11/os-9-version-2-0-boot#comments</comments>
		<pubDate>Thu, 27 Nov 1986 23:30:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/os-9-version-2-0-boot/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18691 27NOV86-2330 Archives<br />     OS-9 Version 2.0 Boot<br />     From: OS9BERT      To: 6809ER</p>
<p>Steve, I got 2.0 to boot up with my hard drive!  I patched CONFIG to<br />work with my hard drive.  I then created a MODULES directory and copied<br />all of my drivers, etc. into this directory and ran config.  Thanks<br />for giving me some advice.  I have a question for you.  Have you or<br />anyone else done some graphics work under OS-9 on either the old<br />CoCos or the new CoCo ?  I am interested in seeing some new programs<br />that use this capability on OS-9.<br />Bert</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/os-9-version-2-0-boot/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 ON COCO3 Re: Msg 18662</title>
		<link>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18662</link>
		<comments>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18662#comments</comments>
		<pubDate>Thu, 27 Nov 1986 20:04:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18662/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18675 27NOV86-2004 Archives<br />     RE: OS-9 ON COCO3 (Re: Msg 18662)<br />     From: DWHILL       To: MARTYGOODMAN</p>
<p>   I hope that&#8217;s in source code.  I don&#8217;t think I can download binary on my<br />PC.  Really do need to get a modem for the CoCo so I can at least readily<br />download programs&#8230;</p>
<p>&#8211;Damon</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18662/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 ON COCO3 Re: Msg 18637</title>
		<link>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637</link>
		<comments>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637#comments</comments>
		<pubDate>Thu, 27 Nov 1986 18:49:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18660 27NOV86-1849 Archives<br />     RE: OS-9 ON COCO3 (Re: Msg 18637)<br />     From: MARTYGOODMAN To: DONTHRASH</p>
<p>We will very soon (in a matter of a few days at most)<br />have an 80 column driver for OS-9 level 1 ver 2<br />posted for public acess in the OS-9 data base section.</p>
<p> &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 ON COCO3 Re: Msg 18637</title>
		<link>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637-2</link>
		<comments>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637-2#comments</comments>
		<pubDate>Thu, 27 Nov 1986 13:04:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18647 27NOV86-1304 Archives<br />     RE: OS-9 ON COCO3 (Re: Msg 18637)<br />     From: RICKADAMS    To: BUDDCAR</p>
<p>An 80-column driver for OS-9 Version 2.0.0 on the Coco 3 was recently<br />uploaded to the OS-9 database here on Delphi.  I am supposed to check it<br />out and enable it within the next several days, but I am so busy helping<br />my wife handle the kids and the turkeys today that it will probably be<br />a while.  But I am looking forward to using it myself&#8230;!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 ON COCO3 Re: Msg 18637</title>
		<link>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637-3</link>
		<comments>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637-3#comments</comments>
		<pubDate>Thu, 27 Nov 1986 12:54:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637-3/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18645 27NOV86-1254 Archives<br />     RE: OS-9 ON COCO3 (Re: Msg 18637)<br />     From: BUDDCAR      To: DONTHRASH</p>
<p>If you are referring to version 02.00.00 of level 1 OS9 then yes the<br />80 col is available if you are able to download the CO380 driver<br />available on that competing service (OS9 ug on Cserve). As I hear<br />but cannot substantiate theLevel 2 OS9 will support 80 cols when it<br />becomes available. I am using 80 col mode as I write this &#8211; very!<br />pleasant to use on my zenith amber monitor. And looks GREAT! on color<br />too<br />         Bob Palmer</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os-9-on-coco3-re-msg-18637-3/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os9 kermit uploaded Re: Msg 16902</title>
		<link>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16902</link>
		<comments>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16902#comments</comments>
		<pubDate>Tue, 25 Nov 1986 18:53:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16902/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18545 25NOV86-1853 Archives<br />     RE: os9 kermit uploaded (Re: Msg 16902)<br />     From: GREGL        To: MEGABYTE</p>
<p>Mark,</p>
<p>     I just tried out kermit and I never could get it to transfer a file.<br />While runing with XTerm on /XT2 I got into workspace and typed &#8216;Kermit&#8217; and<br />it asked me if I were sending only text files and I responded &#8216;yes&#8217; and then<br />it said type three control-C&#8217;s to abort. I then went to shell, and called up<br />kermit via &#8216;kermit -sl startup /t2&#8242; and it never transferred. Nary a character<br />was transmitted though I did recieve some blocks (as viewed from xterm) that<br />looked like <soh>#N every now and again. I figured that maybe xterm was blocking<br />the way so I completely exited xterm and tried again. Nothing&#8230; So I figured<br />that since I logged at 1200 baud, 7 bit, even parity I changed /T2 from 1200<br />baud 8 bit no parity to 7 bit even with the same old nothingness.</p>
<p>     Am I doing something wrong here or do I have to log in at 8 bit no parity<br />to get it to work. Although, I was under the assumption that kermit is supposed<br />to start sending immediately, unlike xmode which must wait for the initial NAK.<br />I&#8217;m a gonna try it one more time and see what happens&#8230;</p>
<p></soh></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16902/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 Re: Msg 18171</title>
		<link>http://www.coco3.com/community/1986/11/re-os-9-re-msg-18171</link>
		<comments>http://www.coco3.com/community/1986/11/re-os-9-re-msg-18171#comments</comments>
		<pubDate>Tue, 25 Nov 1986 18:35:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os-9-re-msg-18171/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18543 25NOV86-1835 Archives<br />     RE: OS-9 (Re: Msg 18171)<br />     From: DONHUTCHISON To: PENROSE</p>
<p>  Actually, when you use the OS9->RS converter, you&#8217;re just moving the files<br />from one disk format to another&#8230; they&#8217;re not being converted in any way.<br />By the way, Dale Lear (OS9 Section Leader here) suggests copying these<br />&#8220;converted&#8221; files onto a TRUE OS9 disk as soon as possible, as the disk<br />format created by the OS9->RS converter isn&#8217;t a true OS9 format.</p>
<p>  Anyway, aren&#8217;t most of the BASIC09 programs in ASCII format?  If they are,<br />you should be able to strip the trailing stuff (produced by an XMODEM<br />download) using OS9&#8242;s editor.  Just delete any lines without text in them,<br />and you should be fine.</p>
<p>  The downloading hint that I posted was for binary files, and there really is<br />no point in making a text file &#8220;executable&#8221;.  In this case, my hint really<br />doesn&#8217;t apply&#8230; I&#8217;d try the editor, myself.</p>
<p>    Good luck!<br />     Don</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os-9-re-msg-18171/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os9 kermit uploaded Re: Msg 18441</title>
		<link>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-18441</link>
		<comments>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-18441#comments</comments>
		<pubDate>Mon, 24 Nov 1986 20:21:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-18441/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18493 24NOV86-2021 Archives<br />     RE: os9 kermit uploaded (Re: Msg 18441)<br />     From: MEGABYTE     To: GREGL</p>
<p>Greg,<br />   Kermit IS a terminal program.  Though perhaps not the smartest<br />one.  Pete Lyall uses it in combo with xcom9. Whne he wants to<br />to a file xfer, he uses xcom9 shell command processor to do it.</p>
<p>   Yes, Kermit, even the os9 coco version can send and recieve<br />multiple files.  The only probelm is that kermit09 does not<br />support meta characters. Thus a command line can look like:</p>
<p>OS9: kermit -sl /t2 file1 file2 file3 file4 file5 file6 &#8230;</p>
<p>One of the things I am working on in a version with wild card<br />support.  I use kermit all the time between both my CoCo and<br />my Unix box and my CoCo and delphi. Feel free to ask any more<br />questions.</p>
<p>&#8212;Mark S.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-18441/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 TO RS Re: Msg 18289</title>
		<link>http://www.coco3.com/community/1986/11/re-os-9-to-rs-re-msg-18289</link>
		<comments>http://www.coco3.com/community/1986/11/re-os-9-to-rs-re-msg-18289#comments</comments>
		<pubDate>Sun, 23 Nov 1986 23:42:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os-9-to-rs-re-msg-18289/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18438 23NOV86-2342 Archives<br />     RE: OS-9 TO RS (Re: Msg 18289)<br />     From: BOWSIN       To: PENROSE</p>
<p>Well guess it&#8217;s on of lives little pleasuresd. I had no need for the convert<br />program since I don&#8217;t use OS-9 myself and probably never will, but I did know<br />that it works well enough to move file to an OS-9<br />formatted disk. For me it&#8217;s good old Microsoft basic and a good assembly<br />language program and I don&#8217;t have to run the dickens out of the floppy drives<br />everytime I want the computer to do something.<br />the other choice is to go with a real heavy duty unit with about 600 to 700 of<br />ram and a hard drive. that&#8217;s 600 to 700k of ram!!Taker easy, keep cool.<br />Dan.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os-9-to-rs-re-msg-18289/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 TO RS Re: Msg 18282</title>
		<link>http://www.coco3.com/community/1986/11/re-os-9-to-rs-re-msg-18282</link>
		<comments>http://www.coco3.com/community/1986/11/re-os-9-to-rs-re-msg-18282#comments</comments>
		<pubDate>Sun, 23 Nov 1986 23:35:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os-9-to-rs-re-msg-18282/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18435 23NOV86-2335 Archives<br />     RE: OS-9 TO RS (Re: Msg 18282)<br />     From: BOWSIN       To: ENDOTSON</p>
<p>THEN I assume that you have noway of getting regular type of programs if the<br />terminal program you have is only os-9.<br />     Perhaps there is more then one way to skin a cat so to speak. What other<br />terminal programs do you have? If I may ask.<br />    Also if you leave me private mail I&#8217;ll foward<br />Darn service!! And if you don&#8217;t have any other terminal program could send you<br />a copy of mikey term. If you do have a good terminal program that does and<br />ecellent ascii<br />transfer you could give me a call and I could send you mikeyterm and a<br />diskconvert program to convert it back to binary on the disk.<br />what major town are you near? perhaps it might be covered by pc pursuit? could<br />tell by the area code that you are in.<br />Take care, have a good holiday.<br />Dan.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os-9-to-rs-re-msg-18282/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os9 kermit uploaded Re: Msg 16902</title>
		<link>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16902-2</link>
		<comments>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16902-2#comments</comments>
		<pubDate>Fri, 21 Nov 1986 21:47:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16902-2/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>18234 21NOV86-2147 Archives<br />     RE: os9 kermit uploaded (Re: Msg 16902)<br />     From: GREGL        To: MEGABYTE</p>
<p>Have you tried kermit to see if it works? I tried using that frigging DTerm<br />that comes with it and I type A to the modem and get &#8216;AAAAAAAAAAAAAAAAAAAAA<br />ad infinitum&#8217; until I type another character and then I get that character<br />ad infinitum&#8230;. So, I have yet to try my binary version of Kermit&#8230; I&#8217;ll<br />download it (or at least the rest of it, hehe) and give it another shot.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16902-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: StearmanDOS &amp; OS9 Re: Msg 17735</title>
		<link>http://www.coco3.com/community/1986/11/re-stearmandos-os9-re-msg-17735</link>
		<comments>http://www.coco3.com/community/1986/11/re-stearmandos-os9-re-msg-17735#comments</comments>
		<pubDate>Sun, 16 Nov 1986 02:20:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-stearmandos-os9-re-msg-17735/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>17797 16NOV86-0220 Archives<br />     RE: StearmanDOS &#038; OS9 (Re: Msg 17735)<br />     From: PKW          To: DALEP</p>
<p>THANKS FOR THE INFORMATION DALE.<br />BRUCE WARNER WAS KIND ENOUGH TO HELP ME OUT WITH MY PROBLEM &#8211;HE EVEN<br />CUSTOMIZED THE DS PACKAGE FOR ME AT HIS HOME. MAN, CAN HE MAKE OS-9 SINGG!!!<br />SAW PIPES AND FILTERS USED WITH SOME OF THE DP JOHNSON FILTER UTILITIES. VERY<br />IMPRESSED.<br />MY ONLY PROBLEM IS THAT &#8211;INTERESTINGLY ENOUGH &#8212; WHILE MY DRIVE 0,2 STEPS AT<br />12MS AND MY DRIVE 1,3 STEPS AT 20MS UNDER TELEPATCHED TELEWRITER, THEY DO<br />>>NOT< < FUNCTION RELIABLY AT THESE RATES UNDER BRUCE'S CUSTOMIZED DISK OF DS<br />THAT HE DID FOR ME! SO I AM<br /> NOW PAINSTAKINGLY COPYING EVERYTHING BUT THE NEW DISK DRIVERS OVER TO ANOTHER<br />SYSTEM DISK. WE&#8217;LL SEE DYNASTAR UP AND RUNNING SOON.<br />&#8211; PKW</p>
<p>PS I HEAR A NICE NEW SPELLER IS COMING OUT FOR LEVEL II ON THE COCO3 REALLY<br />SOON. ALSO!! ONE OF THE S-100 MAGAZINES HAS AN ANNOUNCEMENT THIS MONTH &#8212; ANY<br />OF THE MULTITASKING OS&#8217;S FOR THE S-100 INCLUDING OS-9 WILL BE COVERED IN<br />GREATER DETAIL IN SUBESEQUENT<br /> MONTHS. THEY ARE SEEKING EXPERTS (OR AT LEAST KNOWLEDGEABLE USERS) OF OS-9 ON<br />THE S-100 BUS. KNOW ANY? TIME FOR PROSELETYZING!!!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-stearmandos-os9-re-msg-17735/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>020 addon</title>
		<link>http://www.coco3.com/community/1986/11/020-addon</link>
		<comments>http://www.coco3.com/community/1986/11/020-addon#comments</comments>
		<pubDate>Sat, 15 Nov 1986 18:39:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/020-addon/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>17759 15NOV86-1839 Archives<br />     020 addon<br />     From: DIBBLE       To: MARTYGOODMAN</p>
<p>Could that be done!?  I seem to be constantly underestimating the CoCo.</p>
<p>I get a lot of use out of my 020&#8230; without any graphics &#8212; yet.  For<br />a serious programmer the fast compiler is worth a lot.  If you want to<br />run TeX, you will need about a meg of memory and you will yearn for<br />a fast processor.  A PC takes about a minute to format a page.</p>
<p>Figure that very fast means 38KB at least.  Wouldn&#8217;t that push bits<br />to the 6809 about as fast as it could take them?  Given that kind of<br />speed a parallel port might be easier.</p>
<p>I was thinking of the 020 as a cycle-server for the CoCo.  If it could<br />actually DMA&#8217;d to the video memory it would act like a super CoCo.<br />If that&#8217;s possible it would be SOMETHING!</p>
<p>Peter</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/020-addon/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RE: 020 in every home Re: Msg 17642</title>
		<link>http://www.coco3.com/community/1986/11/re-020-in-every-home-re-msg-17642</link>
		<comments>http://www.coco3.com/community/1986/11/re-020-in-every-home-re-msg-17642#comments</comments>
		<pubDate>Sat, 15 Nov 1986 06:34:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-020-in-every-home-re-msg-17642/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>17711 15NOV86-0634 Archives<br />     RE: 020 in every home (Re: Msg 17642)<br />     From: MARTYGOODMAN To: DIBBLE</p>
<p>I find it VERY hard to imagine why the heck anyone would<br />want a 68020 home computer that talked out a &#8220;very fast serial<br />port&#8221;.  Sheesh!  What an utter waste of computing power in<br />a home (=single user in most cases) machine.  The 68020<br />makes NO sense to me for most tasks that folks currently<br />use a home computer for (home or small business oriented<br />word processing, spread sheets, and data bases).<br />The ONLY application where the power of the 68020<br />really adds anything significant in performance for<br />the single private user would seem to be in GRAPHICS<br />manipulators of various sorts.  In THAT application<br />the 68020 should really shine, and allow setting up<br />truely professional hi res graphics editors that are<br />impossible to set up practically with any of the<br />lessor members of the 68XXY family.  But for that you<br />sure don&#8217;t want a worthless slothful &#8220;very fast&#8221; serial port!<br />No sir&#8230; you want DMA of the video!!</p>
<p>  Just puttin&#8217; in my two cents, as always!</p>
<p> &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-020-in-every-home-re-msg-17642/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os9ver2000 Re: Msg 17626</title>
		<link>http://www.coco3.com/community/1986/11/re-os9ver2000-re-msg-17626</link>
		<comments>http://www.coco3.com/community/1986/11/re-os9ver2000-re-msg-17626#comments</comments>
		<pubDate>Fri, 14 Nov 1986 01:16:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os9ver2000-re-msg-17626/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>17632 14NOV86-0116 Archives<br />     RE: os9ver2000 (Re: Msg 17626)<br />     From: PKW          To: COCOJOHN</p>
<p>NUMERIC KEYBOARD WOULD HAVE DEMANDED A >>TOTAL< < REDESIGN OF THE OUTSIDE CASE.<br />THAT WOULD BE A GOOD IDEA. THE SEX APPEAL OF THE OUTSIDE OF THE COCO IS NIL.<br />CONSIDER, COCOJOHN. THE COMMODORE AND THE APPLE ARE POPULAR NOT BECAUSE OF THE<br />SOFTWARE THAT COMMODORE AND APPLE WROTE FOR THEIR OWN COMPUTERS!!!</p>
<p>THE MORAL OF THE STORY IS, APPLE IS POPULAR BECAUSE OF ONE PROGRAM (VISICALC)<br />AND BECAUSE OF ITS GOOD GRAPHICS. COMMODORE IS POPULAR BECAUSE OF ITS<br />PRICE/PERFORMANCE AT THE TIME IT WAS ISSUED &#8212; AND BECAUSE OF ITS GOOD GRAPHICS.<br />THUS, TO MAKE THE COCO3 GREAT WILL >>NOT< < TAKE DOING ON TANDY'S PART --<br />NECESSARILY. IT NEEDS TO BE FAIRLY INEXPENSIVE (IT IS) IT NEEDS TO HAVE GREAT<br />GRAPHICS (IT DOES &#8212; JUST WAIT FOR THE NEW PROGRAMS!!!), IT NEEDS TO PERFORM<br />WELL (THAT DEPENDS ON THIRD-<br />PARTY PEOPLE MOSTLY) AND ***********LAST BUT NOT LEAST******** IT NEEDS THAT<br />>>ONE< < PROGRAM THAT WILL BRING IT TO THE ATTENTION OF EVERYONE ELSE. LIKE<br />VISICALC DID FOR THE APPLE.</p>
<p>NOW.</p>
<p>I HAVE A DREAM.</p>
<p>THAT ONE PROGRAM WILL RUN UNDER OS9 WITH WINDOWING AND WILL BE >>AS POWERFUL< <<br />AS ANY PROGRAM FOR ANY OTHER LOW- TO MID-END COMPUTER. IT WILL BE PRETTY. IT<br />WILL HAVE A GREAT MANUAL. IT WILL HAVE FOUR-COLOR GRAPHICS ON THE COVER OF THE<br />MANUAL. IT WILL BE WE<br />LL-SUPPORTED. IT WILL BE FAIRLY INEXPENSIVE (LESS THAN $150). IT WILL >> NOT < <<br />MAKE UNNECESSARY COMPROMISES.</p>
<p>THATI<br /> THAT IS THE PROGRAM THAT WILL BRING THE COCO OUT FROM THE SHADOWS AND ENSURE A<br />COCO4.</p>
<p>&#8211; PAUL</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os9ver2000-re-msg-17626/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: OS9 TS WORD Re: Msg 17500</title>
		<link>http://www.coco3.com/community/1986/11/re-os9-ts-word-re-msg-17500</link>
		<comments>http://www.coco3.com/community/1986/11/re-os9-ts-word-re-msg-17500#comments</comments>
		<pubDate>Wed, 12 Nov 1986 23:22:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os9-ts-word-re-msg-17500/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>17521 12NOV86-2322 Archives<br />     RE: OS9 (TS WORD) (Re: Msg 17500)<br />     From: DALELEAR     To: XANTHA</p>
<p>Yes Jim, TSWORD prints underline-backspace-character in underline mode.  This<br />is supported by many many printers.  It is as close to a standard as things<br />get.  Unfortunatly, if your printer doesn&#8217;t support it you have to go a<br />different<br />route.  The best thing to do is define one of your fonts as underline.  To do<br />this<br />define the control sequence for font 2(underline) as 0F.  Then define the<br />control<br />sequence for font 1 (standard font) as 0E.  To change fonts on a single word or<br />group of words within a line you have to use the fill mode as well.</p>
<p>Good Luck.<br />D.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os9-ts-word-re-msg-17500/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>CoCo Stallian</title>
		<link>http://www.coco3.com/community/1986/11/coco-stallian</link>
		<comments>http://www.coco3.com/community/1986/11/coco-stallian#comments</comments>
		<pubDate>Wed, 12 Nov 1986 20:54:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/coco-stallian/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>17503 12NOV86-2054 Archives<br />     CoCo Stallian<br />     From: DIBBLE       To: DALELEAR</p>
<p>Go for it.  I think my 020 is wonderful, but I&#8217;m a 6809 fanatic from way<br />back (the day I read about them in the BYTE articles that talked about<br />their development).  I&#8217;ll be cheering for you.</p>
<p>Peter</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/coco-stallian/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os9 kermit uploaded Re: Msg 17445</title>
		<link>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-17445</link>
		<comments>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-17445#comments</comments>
		<pubDate>Wed, 12 Nov 1986 20:27:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-17445/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>17501 12NOV86-2027 Archives<br />     RE: os9 kermit uploaded (Re: Msg 17445)<br />     From: MEGABYTE     To: MARTYGOODMAN</p>
<p>Marty,<br />  OK you have convinced me. I will break the kermit protocol<br />manuakl up into about 20k chunks.  Then I will need upload time.<br />Let me calculate how long it will take to do so, and then apply<br />for the time. I will HAVE to be on a Sunday.</p>
<p>  Keep you in touch</p>
<p>&#8212;Mark S.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-17445/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fast OS-9 board</title>
		<link>http://www.coco3.com/community/1986/11/fast-os-9-board</link>
		<comments>http://www.coco3.com/community/1986/11/fast-os-9-board#comments</comments>
		<pubDate>Sun, 09 Nov 1986 23:10:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/fast-os-9-board/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>17269  9NOV86-2310 Archives<br />     Fast OS-9 board<br />     From: DIBBLE       To: PKW</p>
<p>I  use a GMX Micro-20 for most of my computing.  Mine runs at 12.5<br />(ZMhz<br />sometimes at 16Mhz.  GMX sells a version that runs at 20MHz.  I expect<br />a 25 MHz version soon, maybe they have demonstrated one<br />running that fast.  As an interesting example of FAST, I can run<br />the entire C compile sequence on on a mediumm-sized file in less than<br />ten seconds.</p>
<p>The graphics board isn&#8217;t out yet, and when it ddoit does come out it won&#8217;t<br />have the softwre support the CoCo has.  Windows isn&#8217;t working for<br />OS-9/68K yet.</p>
<p>Peter</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/fast-os-9-board/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: OS-9 Re: Msg 15315</title>
		<link>http://www.coco3.com/community/1986/11/re-os-9-re-msg-15315</link>
		<comments>http://www.coco3.com/community/1986/11/re-os-9-re-msg-15315#comments</comments>
		<pubDate>Sun, 09 Nov 1986 01:47:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os-9-re-msg-15315/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>17197  9NOV86-0147 Archives<br />     RE: OS-9 (Re: Msg 15315)<br />     From: OS9BERT      To: JAZZCAT</p>
<p>Greg Morse has developed a great terminal package for OS-9 called XCOM9.<br />I use it all of the time.  It supports xon and xoff as well as XMODEM.<br />You can get it through the OS-9 Users Group.  It is distributed under<br />the pr</p>
<p>emise that you will pay Greg what you think it is worth (another<br />words, freeware).<br />Bert</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os-9-re-msg-15315/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DYNASTAR</title>
		<link>http://www.coco3.com/community/1986/11/dynastar</link>
		<comments>http://www.coco3.com/community/1986/11/dynastar#comments</comments>
		<pubDate>Thu, 06 Nov 1986 17:33:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/dynastar/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16976  6NOV86-1733 Archives<br />     DYNASTAR<br />     From: PKW          To: DALEP</p>
<p>DALE &#8211;<br />AT THE PRINCETON RAINBOWFEST, MY LADY FRIEND WON A FREE COPY OF DYNASPELL. (SEE<br />HOW YOUR WRK &#8212; WORK &#8212; TOUCHES MANY FOLKS!) AND SINCE ELIZABETH HAS NO COCO,<br />SHE GAVE IT TO ME. HOW SWEET! I OR &#8212; ORDERED &#8212; DYNASTAR WHEN I REDDEMED THE<br />COUPON FOR DYNAMSP<br />ELL. THE DOCS SAY THAT DS ONLY WORKS WITH THE HIRES SCREEN IN THE O-PAK PACKAGE.</p>
<p>HORRORS! SAY IT AIN&#8217;T TRUE!</p>
<p>CAN I PATCH DYNASSTAR TO WRK ON MY DISTO DISPLAY-80?<br />I ALREADY HAVE A MODIFIED CO80 MODULE INSTALLED ON MY BASICC09 WORKDISK. LLOKS<br />GREAT.<br />&#8211; THANKS FOR ANY HELP!!</p>
<p>&#8211; PKW IN ARLINGTON VA.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/dynastar/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: New Pix Programs Re: Msg 16950</title>
		<link>http://www.coco3.com/community/1986/11/re-new-pix-programs-re-msg-16950</link>
		<comments>http://www.coco3.com/community/1986/11/re-new-pix-programs-re-msg-16950#comments</comments>
		<pubDate>Thu, 06 Nov 1986 12:41:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-new-pix-programs-re-msg-16950/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16975  6NOV86-1241 Archives<br />     RE: New Pix Programs (Re: Msg 16950)<br />     From: RONALDCOLE   To: DALELEAR</p>
<p>Thanks Dale!  I hope that OS-9 users check it out.  Enough of graphics demos<br />and more graphics utilities for OS-9, I say.</p>
<p>The last few days have been warm up here, but the storm raging it&#8217;s way to the<br />West Coast made it pretty cold here (Chico, CA) last night.</p>
<p>I bought an HP7908P Hard Disk with Tape Cartridge backup at a swap for $150.<br />I intend to write drivers and design and build an HP-IB/GPIB/IEEE-488-1978<br />interface for the CoCo.  Would anyone out there be interested in an HP-IB<br />interface?  I&#8217;ve seen lots of printers and plotters and stuff go for real<br />cheep at swaps just because they only have an HP-IB connector.  If I can<br />get enough response, I may decide to market it.  Waddya think?  Any demand?</p>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-new-pix-programs-re-msg-16950/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: kermit Re: Msg 16926</title>
		<link>http://www.coco3.com/community/1986/11/re-kermit-re-msg-16926</link>
		<comments>http://www.coco3.com/community/1986/11/re-kermit-re-msg-16926#comments</comments>
		<pubDate>Thu, 06 Nov 1986 08:23:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-kermit-re-msg-16926/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16968  6NOV86-0823 Archives<br />     RE: kermit (Re: Msg 16926)<br />     From: MARTYGOODMAN To: CONNOLLY</p>
<p>We have been having some trouble with the data base<br />due to new software being implimented&#8230;<br />hopefully in a few days MEGABYTE&#8217;S upload will<br />be available to you.  Sorry about the delay.</p>
<p> &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-kermit-re-msg-16926/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>kermit is here</title>
		<link>http://www.coco3.com/community/1986/11/kermit-is-here</link>
		<comments>http://www.coco3.com/community/1986/11/kermit-is-here#comments</comments>
		<pubDate>Wed, 05 Nov 1986 20:23:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/kermit-is-here/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16904  5NOV86-2023 Archives<br />     kermit is here<br />     From: MEGABYTE     To: DALELEAR</p>
<p>Dale,<br />  I was finally able to upload kermit byfirst, uploading<br />it to my LAN, and then from the LAN to delphi.  Looks like<br />straight my CoCo to delphi is not possible.</p>
<p>&#8212;Mark S.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/kermit-is-here/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: +5 &amp; +12 Re: Msg 16819</title>
		<link>http://www.coco3.com/community/1986/11/re-5-12-re-msg-16819</link>
		<comments>http://www.coco3.com/community/1986/11/re-5-12-re-msg-16819#comments</comments>
		<pubDate>Tue, 04 Nov 1986 23:31:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-5-12-re-msg-16819/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16856  4NOV86-2331 Archives<br />     RE: +5 &#038; +12 (Re: Msg 16819)<br />     From: MARTYGOODMAN To: GREGL</p>
<p>No, Greg&#8230;</p>
<p>   A better approach is to use the MAX232 chip.  This chip<br />is a five volt only chip, that has the following functions:</p>
<p>It provides plus and minus 10 volts (using a charge pump&#8230;<br />no external components needed).  It also has on board<br />two TTL to RS232 (+/- 10V) converters, and two<br />RS232 to TTL converters.  Pretty slick, eh?<br />Price was around $4 or so a chip, if I recall.</p>
<p>  &#8212;marty</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-5-12-re-msg-16819/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os9 kermit uploaded Re: Msg 16706</title>
		<link>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16706</link>
		<comments>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16706#comments</comments>
		<pubDate>Mon, 03 Nov 1986 22:33:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16706/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16758  3NOV86-2233 Archives<br />     RE: os9 kermit uploaded (Re: Msg 16706)<br />     From: MEGABYTE     To: MARTYGOODMAN</p>
<p>Marty,<br />  It may interest you to know that I used kermit09 to<br />upload kermit09.I have used the RS-DOS kermit and know<br />that it does work.  Has anyone evry<br />er, ever enlightened you to the tremendous advantages<br />kermit has over xmodem? If not, I could&#8230;. and there are MANY!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os9-kermit-uploaded-re-msg-16706/feed</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>+5 &amp; +12</title>
		<link>http://www.coco3.com/community/1986/11/5-12</link>
		<comments>http://www.coco3.com/community/1986/11/5-12#comments</comments>
		<pubDate>Mon, 03 Nov 1986 02:15:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/5-12/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16686  3NOV86-0215 Archives<br />     +5 &#038; +12<br />     From: CONNOLLY     To: MARTYGOODMAN</p>
<p>Marty,<br />     Where is a good place to get at the +5 and +12 on the CC3?<br />I had some do-dads hooked up to my 2 that used these lines, but<br />I don&#8217;t have any kind of schematic at all for the 3. Any help<br />would be greatly appreciated.<br />      Dan</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/5-12/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>RE: OS9 2.00.00 Re: Msg 16487</title>
		<link>http://www.coco3.com/community/1986/11/re-os9-2-00-00-re-msg-16487</link>
		<comments>http://www.coco3.com/community/1986/11/re-os9-2-00-00-re-msg-16487#comments</comments>
		<pubDate>Sat, 01 Nov 1986 20:09:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os9-2-00-00-re-msg-16487/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16518  1NOV86-2009 Archives<br />     RE: OS9 2.00.00 (Re: Msg 16487)<br />     From: CHOFFMAN     To: PKW</p>
<p>After booting OS9, place the CONFIG disk in /d0 and a blank, formatted disk<br />in /d1.</p>
<p>Type ce  chd x /d0/cmds.  Then type config &#038; follow prompts on screen.</p>
<p>If this does&#8217;nt help let me know.  By the way, do you have Disk Basic 1.0 or<br />1.1?</p>
<p>Good luck!</p>
<p>Chuck Hoffman</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os9-2-00-00-re-msg-16487/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>TSEDIT/TSWORD</title>
		<link>http://www.coco3.com/community/1986/11/tsedittsword</link>
		<comments>http://www.coco3.com/community/1986/11/tsedittsword#comments</comments>
		<pubDate>Sat, 01 Nov 1986 18:24:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/tsedittsword/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16507  1NOV86-1824 Archives<br />     TSEDIT/TSWORD<br />     From: CHOFFMAN     To: DALELEAR</p>
<p>Dale,<br />,</p>
<p>Is there any way to use TSEDIT with an 80column display on the COCO 3?<br />I&#8217;ve found an excellent driver on the OS9 SIOS9 SIG on Compuserve for 80<br />columns.<br />The only problem I&#8217;ve found is not being able to use my favorite editor.</p>
<p>Can TSEDIT or T &#038; TSWORD be defaulted to use the CO80 display driver?<br />Help!</p>
<p>Chuck Hoffman</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/tsedittsword/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: os-9 quiz Re: Msg 16314</title>
		<link>http://www.coco3.com/community/1986/11/re-os-9-quiz-re-msg-16314</link>
		<comments>http://www.coco3.com/community/1986/11/re-os-9-quiz-re-msg-16314#comments</comments>
		<pubDate>Sat, 01 Nov 1986 01:49:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/11/re-os-9-quiz-re-msg-16314/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16426  1NOV86-0149 Archives<br />     RE: os-9 quiz (Re: Msg 16314)<br />     From: GREGL        To: DONHUTCHISON</p>
<p>Sorry Don, but if you type &#8220;unlink module&#8221; where module is a module loaded<br />frorom OS9Boot then it will NOT be removed from the module directory. The only<br />wayy to physically remove a module from memory when it is the OS9Boot file is to<br />create a new OS9Boot file without that module.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/11/re-os-9-quiz-re-msg-16314/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: Monochrome Madness Re: Msg 16009</title>
		<link>http://www.coco3.com/community/1986/10/re-monochrome-madness-re-msg-16009</link>
		<comments>http://www.coco3.com/community/1986/10/re-monochrome-madness-re-msg-16009#comments</comments>
		<pubDate>Fri, 31 Oct 1986 21:08:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/10/re-monochrome-madness-re-msg-16009/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>16394 31OCT86-2108 Archives<br />     RE: Monochrome Madness (Re: Msg 16009)<br />     From: SALZARD      To: CHOFFMAN</p>
<p>I understood you to mean that you couldn&#8217;t get the 80 column format on your<br />new new CoCo III.  The new basic commands for going from the 32 column screen to<br />the 40 or 80 column screens is &#8220;WIDTH40&#8243; or &#8220;WIDTH80&#8243; However if you follow<br />the sllow<br />the strings regarding the CoCo III there are lots of complaints about the<br />color leaching/bleeding on composite monitors.  CLS5 is one solution or</p>
<p>messing around with the pallette commands until almost black and white is<br />a<br />acheived or better yet getting an Analog RGB monitor.   Have you tried<br />turrning on your computer while holding down the CRTL and ALT keys????</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/10/re-monochrome-madness-re-msg-16009/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>That #*!@ CRC</title>
		<link>http://www.coco3.com/community/1986/10/that-crc</link>
		<comments>http://www.coco3.com/community/1986/10/that-crc#comments</comments>
		<pubDate>Sun, 26 Oct 1986 19:54:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/10/that-crc/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>15993 26OCT86-1954 Archives<br />     That #*!@ CRC<br />     From: DWHILL       To: DONHUTCHISON</p>
<p>   Yep, sure enough, the CRC&#8217;s were bad and the fixed modules, when loaded with<br />the Config utility, create a new boot disk with decent speed and storage.  Thanx<br />for the suggestions and help!  If this keeps up, I may actually come to under-<br />stand OS-9, even though I already love it!</p>
<p>   Now, as has been suggested, if we only had the ability to use the 80 columns<br />and new graphics capabilities&#8230;</p>
<p>   I know, I know&#8230;it&#8217;s called Level II&#8230;</p>
<p>&#8211;Damon</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/10/that-crc/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RE: directory utility Re: Msg 15832</title>
		<link>http://www.coco3.com/community/1986/10/re-directory-utility-re-msg-15832</link>
		<comments>http://www.coco3.com/community/1986/10/re-directory-utility-re-msg-15832#comments</comments>
		<pubDate>Sun, 26 Oct 1986 19:27:00 +0000</pubDate>
		<dc:creator>Delphi</dc:creator>
				<category><![CDATA[Delphi - Archives]]></category>

		<guid isPermaLink="false">http://www.coco3.com/community/1986/10/re-directory-utility-re-msg-15832/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>15989 26OCT86-1927 Archives<br />     RE: directory utility (Re: Msg 15832)<br />     From: GREGL        To: DALELEAR</p>
<p>Yup, I whipped up three previous version of that directory utility before<br />I finally got it the way I wanted with all of the checks that it does. Now<br />I&#8217;ve just discovered a bug in the blame thing&#8230; It doesn&#8217;t crash or<br />anything like that but if you do a DIR to a non-existant directory it will<br />print &#8216;Directory of . time&#8217; and then sit there. So I need to get that fixed<br />and I&#8217;ll reupload it. I&#8217;m hoping to get an assembler version of it going for<br />too much longer to increase speed and decrease size.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.coco3.com/community/1986/10/re-directory-utility-re-msg-15832/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
