From badfrog at gmail.com  Sun Mar  1 02:35:44 2009
From: badfrog at gmail.com (Sean)
Date: Sun, 1 Mar 2009 01:35:44 -0600
Subject: [Coco] Midwest Gaming Classic -- CoCo represented.
In-Reply-To: <8016C974-C646-448E-8821-59900A2C0F89@pobox.com>
References: <8016C974-C646-448E-8821-59900A2C0F89@pobox.com>
Message-ID: <9efa17da0902282335q232602a9qae49841fb55443a0@mail.gmail.com>

That was me that posted about it.  I'm bringing all my carts to make
sure there are plenty of CoCo games represented there.

If you're a gamer, you will have a blast there.

On Sat, Feb 28, 2009 at 9:36 PM, Allen Huffman <alsplace at pobox.com> wrote:
> Someone posted a few days about about the Midwest Gaming Classic coming up
> in Wisconsin, and I see they even have CoCo represented as something that
> will be on display:
>
> http://www.midwestgamingclassic.com/at-the-show/museum/
>
> Neat. It's 6 hours from me. I've thought it might be interesting to combine
> the CoCoFest with something along these lines -- getting more bodies in that
> might have an interest in CoCo, but not enough to justify a trip, but when
> tons of other retro 80s stuff was added, it becomes doable...
>
> ? ? ? ? ? ? ? ?-- A
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From msmcdoug at iinet.net.au  Sun Mar  1 02:59:47 2009
From: msmcdoug at iinet.net.au (Mark McDougall)
Date: Sun, 01 Mar 2009 18:59:47 +1100
Subject: [Coco] Midwest Gaming Classic -- CoCo represented.
In-Reply-To: <807093938.4578631235882158274.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
References: <807093938.4578631235882158274.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
Message-ID: <49AA4073.9060601@iinet.net.au>

wdg3rd at comcast.net wrote:

> Hmm.  No TRS-80 1/3/4.  Yet Big 5 did some of the best ever arcade-style
> stuff on those boxes.  Despite the crappy B/W block graphics.

Amen to that!!!

Regards,

-- 
|              Mark McDougall                | "Electrical Engineers do it
|  <http://members.iinet.net.au/~msmcdoug>   |   with less resistance!"


From operator at coco3.com  Sun Mar  1 03:33:03 2009
From: operator at coco3.com (Roger Taylor)
Date: Sun, 01 Mar 2009 02:33:03 -0600
Subject: [Coco] CoCo Wireless RS-232 Pak
In-Reply-To: <200902282214.31613.rcrislip@neo.rr.com>
References: <20090225004631.9B8B120A13@qs281.pair.com>
	<200902282214.31613.rcrislip@neo.rr.com>
Message-ID: <20090301083308.7D2B620A16@qs281.pair.com>

At 09:14 PM 2/28/2009, you wrote:
>Hi Roger,
>
>I am a bit fuzzy on this. Is the Wireless RS232 a wireless extension/model of
>your CoCoNet, or is it an entirely new product. TIA


CoCoNet will be the firmware in my bluetooth pak, if that helps clear 
anything up.

I'm thinking of releasing CoCoNet itself as a free product to help 
sell my hardware solutions for having CoCoNet on power-up.

-- 
Roger Taylor

http://www.wordofthedayonline.com



From tjseagrove at writeme.com  Sun Mar  1 03:39:38 2009
From: tjseagrove at writeme.com (Tom Seagrove)
Date: Sun, 1 Mar 2009 03:39:38 -0500
Subject: [Coco] proposal for CoCoFEST! talk
In-Reply-To: <20090301.001534.288.9.JohnChasteen.2@Juno.com>
References: <20090301.001534.288.9.JohnChasteen.2@Juno.com>
Message-ID: <001a01c99a49$4250c710$c6f25530$@com>

What would one give to get a hold of some video from some Rainbow Fests
along with a couple seminars?  Would that be of any interest?

Tom

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
Behalf Of John T Chasteen
Sent: Saturday, February 28, 2009 9:36 PM
To: coco at maltedmedia.com
Subject: Re: [Coco] proposal for CoCoFEST! talk

Put my name down for one set of DVD.
John  C

On Fri, 13 Feb 2009 14:28:54 -0800 (PST) KARL SEFCIK <cdiman7 at flash.net>
writes:
> Hey Allen,   Why not do both? A dvd for those of us that want that, 
> and Youtube for those that want to see it for free? Just a reminder, 
> the group STRAIGHT NO CHASE got a 5 album recording deal just by 
> their video on Youtube, lots of people have landed lucrative acting 
> roles in movies and tv shows because of their video on Youtube. 
>     So, why not the Coco? It'd make a great skit on SNL,lol.
> Karl
> --- On Fri, 2/13/09, Allen Huffman <alsplace at pobox.com> wrote:
> From: Allen Huffman <alsplace at pobox.com>
> Subject: Re: [Coco] proposal for CoCoFEST! talk
> To: "CoCoList for Color Computer Enthusiasts" 
> <coco at maltedmedia.com>
> Date: Friday, February 13, 2009, 9:55 AM
> 
> Hmmm, this could be arranged. Would anyone be willing to pay $5 or 
> so for a DVD
> of presentations, profits going to Glenside? Sure we could just post 
> for free on
> YouTube too.
> 
> Sent from my iPhone
> Follow me on Twitter - http://twitter.com/allenhuffman
> 
> On Feb 13, 2009, at 8:49 AM, N8WQ <exwn8jef at gmail.com> wrote:
> 
> > I won't be able to come to the FEST, but are there any plans to 
> video
> tape presentations?
> > 
> > Alan Jones
> > 
> > --N8WQ - Canal Winchester, Ohio
> > http://exwn8jef.googlepages.com/home
> > 
> > 
> > 
> > John W. Linville wrote:
> >> So once again FEST! time is approaching and I have no noteworthy
> >> project to display.  Rather than come empty-handed, I thought I 
> might
> >> have an alternative this year.
> >> 
> >> I thought I might put together a little presentation on how to 
> do
> >> some simple CoCo development using the conveniences of a modern 
> PC
> >> (i.e. "cross development").  This would be a survey of some
> of the
> >> available tools and basic technologies.  As I am not a CoCo 
> programmer
> >> of any note, this would specifically _not_ be a talk to 'how to
> write
> >> the greatest CoCo game ever'.  Instead it would be more of a 
> basic
> >> overview of some of the available tools and their strengths, 
> etc.
> >> I would try to cover both RSDOS and OS-9 targets.
> >> 
> >> Does this interest anyone?  I would put together a few slides 
> and
> >> some simple demos, and the rest of the FEST! could be an 
> extended
> >> demo and Q&A opportunity.  Is this worthwhile?
> >> 
> >> Feedback welcome!
> >> 
> >> John
> >> 
> >> P.S.  I'm a Linux guy, so the presentation would be weighted
> towards
> >> what is available in a Unix-like environment (including cygwin, 
> etc).
> >> 
> >> P.P.S.  I would, of course, be open to suggestions of any 
> particular
> >> tools/projects to cover, interesting tips or resources, etc.
> >> 
> > 
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> 
> 
____________________________________________________________
Improve your driving ability with a stop at traffic school. Click now!
http://thirdpartyoffers.juno.com/TGL2141/fc/BLSrjpTMLIp7R6ScITYTlwh3PQcjyssF
IteJH9hZVO321ezUeVhHV36ywFa/

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.0.237 / Virus Database: 270.11.4/1976 - Release Date: 02/27/09
13:27:00



From rcrislip at neo.rr.com  Sun Mar  1 12:42:20 2009
From: rcrislip at neo.rr.com (richec)
Date: Sun, 1 Mar 2009 12:42:20 -0500
Subject: [Coco] CoCo Wireless RS-232 Pak
In-Reply-To: <20090301083308.7D2B620A16@qs281.pair.com>
References: <20090225004631.9B8B120A13@qs281.pair.com>
	<200902282214.31613.rcrislip@neo.rr.com>
	<20090301083308.7D2B620A16@qs281.pair.com>
Message-ID: <200903011242.20597.rcrislip@neo.rr.com>

On Sunday 01 March 2009 03:33:03 Roger Taylor wrote:
> At 09:14 PM 2/28/2009, you wrote:
> >Hi Roger,
> >
> >I am a bit fuzzy on this. Is the Wireless RS232 a wireless extension/model
> > of your CoCoNet, or is it an entirely new product. TIA
>
> CoCoNet will be the firmware in my bluetooth pak, if that helps clear
> anything up.
>
> I'm thinking of releasing CoCoNet itself as a free product to help
> sell my hardware solutions for having CoCoNet on power-up.

"I see" said the blind carpenter who got his hammer and... saw.  8-) Thanks


From cwgordon at carolina.rr.com  Sun Mar  1 14:40:20 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 1 Mar 2009 14:40:20 -0500
Subject: [Coco] HD power supply
Message-ID: <01f601c99aa5$8ec00500$ac400f00$@rr.com>

Is a power supply for a FD-501 or FD-502 sufficient to power an IDE hard
drive (or two?)

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From briang0671 at sbcglobal.net  Sun Mar  1 14:40:55 2009
From: briang0671 at sbcglobal.net (Brian Goers)
Date: Sun, 01 Mar 2009 13:40:55 -0600
Subject: [Coco] proposal for CoCoFEST! talk
In-Reply-To: <001a01c99a49$4250c710$c6f25530$@com>
References: <20090301.001534.288.9.JohnChasteen.2@Juno.com>
	<001a01c99a49$4250c710$c6f25530$@com>
Message-ID: <49AAE4C7.9020005@sbcglobal.net>

Tom Seagrove wrote:
> What would one give to get a hold of some video from some Rainbow Fests
> along with a couple seminars?  Would that be of any interest?
>
> Tom
>
> ----
What is needed is someone able to record the events. Allen is not able 
to this time.
If any one is able and willing to do this let us know.
I've seen offers to pay $5.00 for a disk.
Brian

-- 
 Brian Goers                                         Glenside Color Computer Club URL
 Glenside Vice-President of Special Events           http://GlensideCCC.com     

 IDE Boards are available.
 Show cost $45.00                                   The 18th Annual ?LAST? Chicago CoCoFEST!
 Includes items in the picture                      Will be held March 28 & 29 2009
                                                    Holiday Inn & Suites Elgin.



From gene.heskett at verizon.net  Sun Mar  1 15:17:41 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sun, 01 Mar 2009 15:17:41 -0500
Subject: [Coco] HD power supply
In-Reply-To: <01f601c99aa5$8ec00500$ac400f00$@rr.com>
References: <01f601c99aa5$8ec00500$ac400f00$@rr.com>
Message-ID: <200903011517.41500.gene.heskett@verizon.net>

On Sunday 01 March 2009, Bill wrote:
>Is a power supply for a FD-501 or FD-502 sufficient to power an IDE hard
>drive (or two?)

That might be a little borderline, Bill.  I'd hook the drive up and see if it 
spins up, if not shut 'er down quick, if it does spin up, immediately check 
the transistors for rapid heat rise, and it that doesn't burn your fingers in 
the first minute, let it be for 20 minutes and recheck the transistors and the 
transformer too this time.  If that seems reasonable, drop the cover back on 
it & let it run for an hour.

Most IDE drives take less than an amp on the 5 volt line, and usually under 
half an amp on the 12 volt line after about a 2 amp startup surge, but its 
continuous load conditions for both, where the floppy's don't use any motor 
power unless spinning, so the average drain is quite a bit less over an hours 
use.

It might be worth raiding an old std computer psu for its fan & rig it to pull 
a little air through the box as the drive may need some cooling if its in side 
a warm box.  I try to keep my drives under 40C here.  The 12 volt line, if 
cooling air is used, won't notice the < 175 ma the fan will draw as the 
cooling will readily offset that extra heat so you can power the fan from the 
12 volt line.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If Bill Gates had a nickel for every time Windows crashed... Oh wait, he
does!

   -- From a Slashdot.org post



From tjseagrove at writeme.com  Sun Mar  1 15:54:48 2009
From: tjseagrove at writeme.com (Tom Seagrove)
Date: Sun, 1 Mar 2009 15:54:48 -0500
Subject: [Coco] proposal for CoCoFEST! talk
In-Reply-To: <49AAE4C7.9020005@sbcglobal.net>
References: <20090301.001534.288.9.JohnChasteen.2@Juno.com>	<001a01c99a49$4250c710$c6f25530$@com>
	<49AAE4C7.9020005@sbcglobal.net>
Message-ID: <004601c99aaf$f6e496a0$e4adc3e0$@com>

I was referring to some from the 80's...

Tom

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
Behalf Of Brian Goers
Sent: Sunday, March 01, 2009 2:41 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] proposal for CoCoFEST! talk

Tom Seagrove wrote:
> What would one give to get a hold of some video from some Rainbow Fests
> along with a couple seminars?  Would that be of any interest?
>
> Tom
>
> ----
What is needed is someone able to record the events. Allen is not able 
to this time.
If any one is able and willing to do this let us know.
I've seen offers to pay $5.00 for a disk.
Brian

-- 
 Brian Goers                                         Glenside Color Computer
Club URL
 Glenside Vice-President of Special Events           http://GlensideCCC.com


 IDE Boards are available.
 Show cost $45.00                                   The 18th Annual "LAST"
Chicago CoCoFEST!
 Includes items in the picture                      Will be held March 28 &
29 2009
                                                    Holiday Inn & Suites
Elgin.


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.0.237 / Virus Database: 270.11.4/1976 - Release Date: 03/01/09
07:04:00



From brucewcalkins at charter.net  Sun Mar  1 16:04:36 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Sun, 1 Mar 2009 16:04:36 -0500
Subject: [Coco] HD power supply
References: <01f601c99aa5$8ec00500$ac400f00$@rr.com>
	<200903011517.41500.gene.heskett@verizon.net>
Message-ID: <0314428E0DC64FE2A977D4862FA2C7A0@speedy>


>> Is a power supply for a FD-501 or FD-502
>> sufficient to power an IDE hard drive (or two?)
>
> That might be a little borderline, Bill.

The Tandy FD-501 and 502 drives were a little light on the power capability. 
If you got the Tandy second drive kit they added a chintzy fan to keep 
things cool enough to function.  And we all know that Tandy never put 
anything into cooling, unless it burned them first.

Bruce W. 



From afra at aurigae.demon.co.uk  Sun Mar  1 16:24:23 2009
From: afra at aurigae.demon.co.uk (Phill Harvey-Smith)
Date: Sun, 01 Mar 2009 21:24:23 +0000
Subject: [Coco] HD power supply
In-Reply-To: <200903011517.41500.gene.heskett@verizon.net>
References: <01f601c99aa5$8ec00500$ac400f00$@rr.com>
	<200903011517.41500.gene.heskett@verizon.net>
Message-ID: <49AAFD07.5080806@aurigae.demon.co.uk>

Gene Heskett wrote:
> On Sunday 01 March 2009, Bill wrote:
>> Is a power supply for a FD-501 or FD-502 sufficient to power an IDE hard
>> drive (or two?)
> 
> That might be a little borderline, Bill. 

Something else that might be worth trying is a laptop 2.5" ide, as these 
typically draw less than half an apm on the 5v only, most modern ones 
can be powered off the USB, which has a max draw of 500mA / device.

Will be quieter and cooler too, though not as 'fast' as a 3.5", I doubt 
that that would make much difference at the speeds the CoCo can operate at.

Cheers.

Phill.

-- 
Phill Harvey-Smith, Programmer, Hardware hacker, and general eccentric !

"You can twist perceptions, but reality won't budge" -- Rush.


From t.fadden at cox.net  Sun Mar  1 15:53:53 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Sun, 01 Mar 2009 13:53:53 -0700
Subject: [Coco] HD power supply
In-Reply-To: <200903011517.41500.gene.heskett@verizon.net>
References: <01f601c99aa5$8ec00500$ac400f00$@rr.com>
	<200903011517.41500.gene.heskett@verizon.net>
Message-ID: <49AAF5E1.40604@cox.net>

Another option would be to get an external ide to usb case.  you can get 
them for under $20, including the power supply.

Tim

Gene Heskett wrote:
> On Sunday 01 March 2009, Bill wrote:
>   
>> Is a power supply for a FD-501 or FD-502 sufficient to power an IDE hard
>> drive (or two?)
>>     
>
> That might be a little borderline, Bill.  I'd hook the drive up and see if it 
> spins up, if not shut 'er down quick, if it does spin up, immediately check 
> the transistors for rapid heat rise, and it that doesn't burn your fingers in 
> the first minute, let it be for 20 minutes and recheck the transistors and the 
> transformer too this time.  If that seems reasonable, drop the cover back on 
> it & let it run for an hour.
>
> Most IDE drives take less than an amp on the 5 volt line, and usually under 
> half an amp on the 12 volt line after about a 2 amp startup surge, but its 
> continuous load conditions for both, where the floppy's don't use any motor 
> power unless spinning, so the average drain is quite a bit less over an hours 
> use.
>
> It might be worth raiding an old std computer psu for its fan & rig it to pull 
> a little air through the box as the drive may need some cooling if its in side 
> a warm box.  I try to keep my drives under 40C here.  The 12 volt line, if 
> cooling air is used, won't notice the < 175 ma the fan will draw as the 
> cooling will readily offset that extra heat so you can power the fan from the 
> 12 volt line.
>
>   



From os9dude at gmail.com  Sun Mar  1 17:05:28 2009
From: os9dude at gmail.com (Rogelio Perea)
Date: Sun, 1 Mar 2009 17:05:28 -0500
Subject: [Coco] HD power supply
In-Reply-To: <0314428E0DC64FE2A977D4862FA2C7A0@speedy>
References: <01f601c99aa5$8ec00500$ac400f00$@rr.com>
	<200903011517.41500.gene.heskett@verizon.net>
	<0314428E0DC64FE2A977D4862FA2C7A0@speedy>
Message-ID: <5631e580903011405t218bebb0n646eb1e40664711f@mail.gmail.com>

That was my worry when I added the 2nd drive to my FD-502 setup, the user
manual had the procedure to upgrade and the cooling fan was noted as
essential for the upgrade to work.

My upgrade was not the Tandy product but a spare I had from a Intel machine
- a generic HH drive.

I installed the drive with no fan and decided to try it out for a while,
this was back in 1989 and to this date the lack of the fan has not been an
issue, not even under heavy floppy drive usage (OS9 L2 on my CoCo 3).

Could be that the power requirements from both drives are just a tad below
the power supply capabilities, maybe a bit more and the thing just wouldn't
work.


-=[ Rogelio ]=-


On Sun, Mar 1, 2009 at 4:04 PM, Bruce W. Calkins wrote:

>
> The Tandy FD-501 and 502 drives were a little light on the power
> capability. If you got the Tandy second drive kit they added a chintzy fan
> to keep things cool enough to function.  And we all know that Tandy never
> put anything into cooling, unless it burned them first.
>
> Bruce W.


From cwgordon at carolina.rr.com  Sun Mar  1 17:12:55 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 1 Mar 2009 17:12:55 -0500
Subject: [Coco] HD power supply
In-Reply-To: <0314428E0DC64FE2A977D4862FA2C7A0@speedy>
References: <01f601c99aa5$8ec00500$ac400f00$@rr.com>	<200903011517.41500.gene.heskett@verizon.net>
	<0314428E0DC64FE2A977D4862FA2C7A0@speedy>
Message-ID: <01fb01c99aba$df6a73e0$9e3f5ba0$@rr.com>

Well, what if I just gut an old computer and get the power supply from it,
mount IT in the FD-501 (or 502) case and go from there?

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Bruce W. Calkins
> Sent: Sunday, March 01, 2009 4:05 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] HD power supply
> 
> 
> >> Is a power supply for a FD-501 or FD-502
> >> sufficient to power an IDE hard drive (or two?)
> >
> > That might be a little borderline, Bill.
> 
> The Tandy FD-501 and 502 drives were a little light on the power
> capability.
> If you got the Tandy second drive kit they added a chintzy fan to keep
> things cool enough to function.  And we all know that Tandy never put
> anything into cooling, unless it burned them first.
> 
> Bruce W.
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From cwgordon at carolina.rr.com  Sun Mar  1 17:15:43 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 1 Mar 2009 17:15:43 -0500
Subject: [Coco] coco font (kinda)
Message-ID: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>

Good morning, world. This is being typed in my version of the coco font.
Seems good enough for my needs.

anyone want it, just email me off the (whadda call this? the echo?) list?
Anyway, just email me privately. (cwgordon at carolina.rr.com)

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From exwn8jef at gmail.com  Sun Mar  1 17:17:00 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Sun, 01 Mar 2009 17:17:00 -0500
Subject: [Coco] proposal for CoCoFEST! talk
In-Reply-To: <001a01c99a49$4250c710$c6f25530$@com>
References: <20090301.001534.288.9.JohnChasteen.2@Juno.com>
	<001a01c99a49$4250c710$c6f25530$@com>
Message-ID: <49AB095C.6010201@gmail.com>

I would like to see video on what new projects people are working on in 
addition to any seminars given this year. Also it would be nice to 
include some clips from the vendors to see what kind of products are 
available for our beloved computer.

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



Tom Seagrove wrote:
> What would one give to get a hold of some video from some Rainbow Fests
> along with a couple seminars?  Would that be of any interest?
>
> Tom
>
> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
> Behalf Of John T Chasteen
> Sent: Saturday, February 28, 2009 9:36 PM
> To: coco at maltedmedia.com
> Subject: Re: [Coco] proposal for CoCoFEST! talk
>
> Put my name down for one set of DVD.
> John  C
>
> On Fri, 13 Feb 2009 14:28:54 -0800 (PST) KARL SEFCIK <cdiman7 at flash.net>
> writes:
>   
>> Hey Allen,   Why not do both? A dvd for those of us that want that, 
>> and Youtube for those that want to see it for free? Just a reminder, 
>> the group STRAIGHT NO CHASE got a 5 album recording deal just by 
>> their video on Youtube, lots of people have landed lucrative acting 
>> roles in movies and tv shows because of their video on Youtube. 
>>     So, why not the Coco? It'd make a great skit on SNL,lol.
>> Karl
>> --- On Fri, 2/13/09, Allen Huffman <alsplace at pobox.com> wrote:
>> From: Allen Huffman <alsplace at pobox.com>
>> Subject: Re: [Coco] proposal for CoCoFEST! talk
>> To: "CoCoList for Color Computer Enthusiasts" 
>> <coco at maltedmedia.com>
>> Date: Friday, February 13, 2009, 9:55 AM
>>
>> Hmmm, this could be arranged. Would anyone be willing to pay $5 or 
>> so for a DVD
>> of presentations, profits going to Glenside? Sure we could just post 
>> for free on
>> YouTube too.
>>
>> Sent from my iPhone
>> Follow me on Twitter - http://twitter.com/allenhuffman
>>
>> On Feb 13, 2009, at 8:49 AM, N8WQ <exwn8jef at gmail.com> wrote:
>>
>>     
>>> I won't be able to come to the FEST, but are there any plans to 
>>>       
>> video
>> tape presentations?
>>     
>>> Alan Jones
>>>
>>> --N8WQ - Canal Winchester, Ohio
>>> http://exwn8jef.googlepages.com/home
>>>
>>>
>>>
>>> John W. Linville wrote:
>>>       
>>>> So once again FEST! time is approaching and I have no noteworthy
>>>> project to display.  Rather than come empty-handed, I thought I 
>>>>         
>> might
>>     
>>>> have an alternative this year.
>>>>
>>>> I thought I might put together a little presentation on how to 
>>>>         
>> do
>>     
>>>> some simple CoCo development using the conveniences of a modern 
>>>>         
>> PC
>>     
>>>> (i.e. "cross development").  This would be a survey of some
>>>>         
>> of the
>>     
>>>> available tools and basic technologies.  As I am not a CoCo 
>>>>         
>> programmer
>>     
>>>> of any note, this would specifically _not_ be a talk to 'how to
>>>>         
>> write
>>     
>>>> the greatest CoCo game ever'.  Instead it would be more of a 
>>>>         
>> basic
>>     
>>>> overview of some of the available tools and their strengths, 
>>>>         
>> etc.
>>     
>>>> I would try to cover both RSDOS and OS-9 targets.
>>>>
>>>> Does this interest anyone?  I would put together a few slides 
>>>>         
>> and
>>     
>>>> some simple demos, and the rest of the FEST! could be an 
>>>>         
>> extended
>>     
>>>> demo and Q&A opportunity.  Is this worthwhile?
>>>>
>>>> Feedback welcome!
>>>>
>>>> John
>>>>
>>>> P.S.  I'm a Linux guy, so the presentation would be weighted
>>>>         
>> towards
>>     
>>>> what is available in a Unix-like environment (including cygwin, 
>>>>         
>> etc).
>>     
>>>> P.P.S.  I would, of course, be open to suggestions of any 
>>>>         
>> particular
>>     
>>>> tools/projects to cover, interesting tips or resources, etc.
>>>>
>>>>         
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>       
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>>     
> ____________________________________________________________
> Improve your driving ability with a stop at traffic school. Click now!
> http://thirdpartyoffers.juno.com/TGL2141/fc/BLSrjpTMLIp7R6ScITYTlwh3PQcjyssF
> IteJH9hZVO321ezUeVhHV36ywFa/
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.0.237 / Virus Database: 270.11.4/1976 - Release Date: 02/27/09
> 13:27:00
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>   


From farna at att.net  Sun Mar  1 19:13:23 2009
From: farna at att.net (Frank Swygert)
Date: Sun, 01 Mar 2009 19:13:23 -0500
Subject: [Coco] Eprom burner
Message-ID: <49AB24A3.8000407@att.net>

If you're going to burn a new ROM (EPROM) I suggest you find a copy of 
Art Flexser's ADOS (ADOS3 for the CC3). He's released it, I believe, so 
if it's not on the archive site it would be nice if someone would upload 
it!

If you can't find it or only want a few enhancements, a BASIC program 
that shows the enhancements is in "Tandy's Little Wonder" (available on 
the archive site in the FARNA directory).

-- 
Frank Swygert
Publisher, "American Motors Cars" 
Magazine (AMC)
For all AMC enthusiasts
http://farna.home.att.net/AMC.html
(free download available!)



From gene.heskett at verizon.net  Sun Mar  1 19:38:15 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sun, 01 Mar 2009 19:38:15 -0500
Subject: [Coco] HD power supply
In-Reply-To: <01fb01c99aba$df6a73e0$9e3f5ba0$@rr.com>
References: <01f601c99aa5$8ec00500$ac400f00$@rr.com>
	<0314428E0DC64FE2A977D4862FA2C7A0@speedy>
	<01fb01c99aba$df6a73e0$9e3f5ba0$@rr.com>
Message-ID: <200903011938.15667.gene.heskett@verizon.net>

On Sunday 01 March 2009, Bill wrote:
>Well, what if I just gut an old computer and get the power supply from it,
>mount IT in the FD-501 (or 502) case and go from there?
>
That runs a smallish chance that the very light load on the 5 volt line would 
let it go wild.  You may want to add a BIG 1 ohm resistor to ground from the 5 
volt line so it draws about 5 amps, which should satisfy nearly all of them.  
Bear in mind that would be 25 watts of heat though.  Mount it against the top 
of the case and have a place to keep your coffee warm. :)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Passionate hatred can give meaning and purpose to an empty life.
		-- Eric Hoffer



From gene.heskett at verizon.net  Sun Mar  1 19:39:47 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sun, 01 Mar 2009 19:39:47 -0500
Subject: [Coco] coco font (kinda)
In-Reply-To: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>
Message-ID: <200903011939.47713.gene.heskett@verizon.net>

On Sunday 01 March 2009, Bill wrote:
>Good morning, world. This is being typed in my version of the coco font.
>Seems good enough for my needs.

But this is a text only medium, so the font used here is whatever I select in 
kmail. :)  In other words, we can't see it.

>anyone want it, just email me off the (whadda call this? the echo?) list?
>Anyway, just email me privately. (cwgordon at carolina.rr.com)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
It's illegal in Wilbur, Washington, to ride an ugly horse.



From cwgordon at carolina.rr.com  Sun Mar  1 19:53:41 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 1 Mar 2009 19:53:41 -0500
Subject: [Coco] coco font (kinda)
In-Reply-To: <200903011939.47713.gene.heskett@verizon.net>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>
	<200903011939.47713.gene.heskett@verizon.net>
Message-ID: <000c01c99ad1$54b43b70$fe1cb250$@rr.com>

Yeah, when it came back to me, I noticed that too. However, it's still kinda
nice even though it's a crude effort, and still available to anyone who
wants it. I'll post it as a download on my board
(http://www.sq1bbs.com/coco/coco.ttf) if anyone actually does want it. If
not, oh well...

(And a sample picture is at http://www.sq1bbs.com/coco/cocottf.jpg)


> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Gene Heskett
> Sent: Sunday, March 01, 2009 7:40 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] coco font (kinda)
> 
> But this is a text only medium, so the font used here is whatever I
> select in kmail. :)  In other words, we can't see it.
> 



From robert.gault at worldnet.att.net  Sun Mar  1 21:07:51 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Sun, 01 Mar 2009 21:07:51 -0500
Subject: [Coco] coco font (kinda)
In-Reply-To: <000c01c99ad1$54b43b70$fe1cb250$@rr.com>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>	<200903011939.47713.gene.heskett@verizon.net>
	<000c01c99ad1$54b43b70$fe1cb250$@rr.com>
Message-ID: <49AB3F77.1090106@worldnet.att.net>

Bill wrote:
> Yeah, when it came back to me, I noticed that too. However, it's still kinda
> nice even though it's a crude effort, and still available to anyone who
> wants it. I'll post it as a download on my board
> (http://www.sq1bbs.com/coco/coco.ttf) if anyone actually does want it. If
> not, oh well...
> 
> (And a sample picture is at http://www.sq1bbs.com/coco/cocottf.jpg)
>
Not bad! A few changes and they will be perfect.

There are problems with some of the numbers and symbols and a few 
letters. Here is a list of your characters that don't look like the Coco 
characters.

G I J M N Q V W X Y 5 6 9 0 ? * '


From t.fadden at cox.net  Sun Mar  1 21:09:23 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Sun, 01 Mar 2009 19:09:23 -0700
Subject: [Coco] Eprom burner
In-Reply-To: <49AB24A3.8000407@att.net>
References: <49AB24A3.8000407@att.net>
Message-ID: <49AB3FD3.6080705@cox.net>

You can download ados-3 from: http://www.nitemarecafe.com/coco/index.php

Tim

Frank Swygert wrote:
> If you're going to burn a new ROM (EPROM) I suggest you find a copy of 
> Art Flexser's ADOS (ADOS3 for the CC3). He's released it, I believe, 
> so if it's not on the archive site it would be nice if someone would 
> upload it!
>
> If you can't find it or only want a few enhancements, a BASIC program 
> that shows the enhancements is in "Tandy's Little Wonder" (available 
> on the archive site in the FARNA directory).
>



From cwgordon at carolina.rr.com  Sun Mar  1 21:21:59 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 1 Mar 2009 21:21:59 -0500
Subject: [Coco] coco font (kinda)
In-Reply-To: <49AB3F77.1090106@worldnet.att.net>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>	<200903011939.47713.gene.heskett@verizon.net>	<000c01c99ad1$54b43b70$fe1cb250$@rr.com>
	<49AB3F77.1090106@worldnet.att.net>
Message-ID: <001001c99add$aadb2bb0$00918310$@rr.com>

Well, I'm not a bit surprised. I was just trying to dupe them as I saw them
on my little coco2 screen next to my PC, and my eyesight is not what it used
to be. I changed the G I J M N and 0, but the rest are gonna have to stay as
they are for my uses. I only have 1 font editor, so I'm kinda limited what I
can do.

Thanks for the reply.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Sunday, March 01, 2009 9:08 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] coco font (kinda)
> 
> Not bad! A few changes and they will be perfect.
> 
> There are problems with some of the numbers and symbols and a few
> letters. Here is a list of your characters that don't look like the
> Coco characters.
> 
> G I J M N Q V W X Y 5 6 9 0 ? * '
>



From alsplace at pobox.com  Sun Mar  1 21:35:39 2009
From: alsplace at pobox.com (Allen Huffman)
Date: Sun, 1 Mar 2009 20:35:39 -0600
Subject: [Coco] coco font (kinda)
In-Reply-To: <001001c99add$aadb2bb0$00918310$@rr.com>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>
	<200903011939.47713.gene.heskett@verizon.net>
	<000c01c99ad1$54b43b70$fe1cb250$@rr.com>
	<49AB3F77.1090106@worldnet.att.net>
	<001001c99add$aadb2bb0$00918310$@rr.com>
Message-ID: <D5C92686-A86F-428B-9A10-20AEBB9F53E4@pobox.com>


On Mar 1, 2009, at 8:21 PM, Bill wrote:

> Well, I'm not a bit surprised. I was just trying to dupe them as I  
> saw them
> on my little coco2 screen next to my PC

We should be able to easily pull the 8-bit data from the ROM and get  
that in to some viewable format -- BMP file or something. Would that  
help?

		-- Allen




From jlhickle at yahoo.com  Sun Mar  1 22:17:58 2009
From: jlhickle at yahoo.com (Jim Hickle)
Date: Sun, 1 Mar 2009 19:17:58 -0800 (PST)
Subject: [Coco] HD power supply times 10
In-Reply-To: <0314428E0DC64FE2A977D4862FA2C7A0@speedy>
Message-ID: <514098.75166.qm@web37301.mail.mud.yahoo.com>

so far I've gotten TEN copies of this message



--- On Sun, 3/1/09, Bruce W. Calkins <brucewcalkins at charter.net> wrote:

> From: Bruce W. Calkins <brucewcalkins at charter.net>
> Subject: Re: [Coco] HD power supply
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Date: Sunday, March 1, 2009, 4:04 PM
> >> Is a power supply for a FD-501 or FD-502
> >> sufficient to power an IDE hard drive (or two?)
> > 
> > That might be a little borderline, Bill.
> 
> The Tandy FD-501 and 502 drives were a little light on the
> power capability. If you got the Tandy second drive kit they
> added a chintzy fan to keep things cool enough to function. 
> And we all know that Tandy never put anything into cooling,
> unless it burned them first.
> 
> Bruce W. 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


      


From georgeramsower at gmail.com  Sun Mar  1 22:37:55 2009
From: georgeramsower at gmail.com (George Ramsower)
Date: Sun, 1 Mar 2009 21:37:55 -0600
Subject: [Coco] HD power supply times 10
References: <514098.75166.qm@web37301.mail.mud.yahoo.com>
Message-ID: <00e401c99ae8$46dabbc0$6401a8c0@OLDGEORGE>

On all messages, I get one of each.
WinXP SP3 Outlook Express

----- Original Message ----- 
From: "Jim Hickle" 

George

> so far I've gotten TEN copies of this message
> 
>> From: Bruce W. Calkins 



From cwgordon at carolina.rr.com  Sun Mar  1 22:42:08 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 1 Mar 2009 22:42:08 -0500
Subject: [Coco] coco font (kinda)
In-Reply-To: <D5C92686-A86F-428B-9A10-20AEBB9F53E4@pobox.com>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>	<200903011939.47713.gene.heskett@verizon.net>	<000c01c99ad1$54b43b70$fe1cb250$@rr.com>	<49AB3F77.1090106@worldnet.att.net>	<001001c99add$aadb2bb0$00918310$@rr.com>
	<D5C92686-A86F-428B-9A10-20AEBB9F53E4@pobox.com>
Message-ID: <000301c99ae8$ddae7d20$990b7760$@rr.com>

I think so, sure.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Allen Huffman
> Sent: Sunday, March 01, 2009 9:36 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] coco font (kinda)
> 
> We should be able to easily pull the 8-bit data from the ROM and get
> that in to some viewable format -- BMP file or something. Would that
> help?
> 



From lamune at doki-doki.net  Sun Mar  1 23:07:39 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Sun, 1 Mar 2009 20:07:39 -0800
Subject: [Coco] coco font (kinda)
In-Reply-To: <D5C92686-A86F-428B-9A10-20AEBB9F53E4@pobox.com>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com><200903011939.47713.gene.heskett@verizon.net><000c01c99ad1$54b43b70$fe1cb250$@rr.com><49AB3F77.1090106@worldnet.att.net><001001c99add$aadb2bb0$00918310$@rr.com>
	<D5C92686-A86F-428B-9A10-20AEBB9F53E4@pobox.com>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D17@fenestra.lamunet.local>

You'd have to decapsulate the 6847 and examine the mask ROM under a
microscope to do that.

Seems a lot easier to just look at the display. It's a 5x7 matrix and
not particularly difficult to reverse engineer with graph paper :)

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Allen Huffman
> Sent: Sunday, March 01, 2009 6:36 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] coco font (kinda)
> 
> 
> On Mar 1, 2009, at 8:21 PM, Bill wrote:
> 
> > Well, I'm not a bit surprised. I was just trying to dupe them as I
> > saw them
> > on my little coco2 screen next to my PC
> 
> We should be able to easily pull the 8-bit data from the ROM and get
> that in to some viewable format -- BMP file or something. Would that
> help?
> 
> 		-- Allen
> 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From bear at bears.org  Sun Mar  1 23:39:55 2009
From: bear at bears.org (Gary)
Date: Sun, 1 Mar 2009 23:39:55 -0500 (EST)
Subject: [Coco] coco font (kinda)
In-Reply-To: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D17@fenestra.lamunet.local>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com><200903011939.47713.gene.heskett@verizon.net><000c01c99ad1$54b43b70$fe1cb250$@rr.com><49AB3F77.1090106@worldnet.att.net><001001c99add$aadb2bb0$00918310$@rr.com>
	<D5C92686-A86F-428B-9A10-20AEBB9F53E4@pobox.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D17@fenestra.lamunet.local>
Message-ID: <alpine.DEB.2.00.0903012337130.10069@ferocity.bears.org>

On Sun, 1 Mar 2009, Mike Pepe wrote:

> Seems a lot easier to just look at the display. It's a 5x7 matrix and
> not particularly difficult to reverse engineer with graph paper :)

I've kind of got a graph paper view... I whipped up a python script to 
decipher the binary from MAME's VDG emulation, and thus print what each 
character looks like.  Also, XROAR has a png of the entire character set. 
(Under the GPL)

You can grab the files at: http://bears.org/~bear/coco/

Peace,
Gary

   *********    *****    **                  Gary Coulbourne
  *************************.*
****** *********** ** *******o           ---------------------
******* ********* **** ****`-            Systems Administrator
******* ********* *****                   http://www.bears.org
  ****** ********** ****                      bear at bears.org
## *****  ***** ##  ****                         KB3INA
### *****      ###   ****                ---------------------
#,,, ***,,,    ##,,,  **,,,


From cwgordon at carolina.rr.com  Mon Mar  2 07:44:56 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Mon, 2 Mar 2009 07:44:56 -0500
Subject: [Coco] checksum
Message-ID: <003001c99b34$b0fa2d00$12ee8700$@rr.com>

At one time there was a checksum program for the programs in the Rainbow
magazines. Does anyone remember which issue(s) this little program was
printed in, or does anyone actually have the BASIC listing for the program
itself.

Thanks
______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From os9dude at gmail.com  Mon Mar  2 08:12:25 2009
From: os9dude at gmail.com (Rogelio Perea)
Date: Mon, 2 Mar 2009 08:12:25 -0500
Subject: [Coco] checksum
In-Reply-To: <003001c99b34$b0fa2d00$12ee8700$@rr.com>
References: <003001c99b34$b0fa2d00$12ee8700$@rr.com>
Message-ID: <5631e580903020512s76d0e755g792223ec8bffa961@mail.gmail.com>

After The Rainbow started to use the RainbowCheck utility, issues had one
page called "Rainbow Info" that included the listing. If you have any issue
from February 1984 on forward you should be able to find the program
there...


-=[ Rogelio ]=-



On Mon, Mar 2, 2009 at 7:44 AM, Bill <cwgordon at carolina.rr.com> wrote:

> At one time there was a checksum program for the programs in the Rainbow
> magazines. Does anyone remember which issue(s) this little program was
> printed in, or does anyone actually have the BASIC listing for the program
> itself.
>
> Thanks


From cwgordon at carolina.rr.com  Mon Mar  2 08:53:38 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Mon, 2 Mar 2009 08:53:38 -0500
Subject: [Coco] Coco3 emulator
Message-ID: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>

I have been trying to use the Coco3 emulator for some time now, but every
time I do, I get an error that says:
 "The NTVDM CPU has encountered an illegal instruction. C5:17b4 IP:003a
OP:dd 0c e0 0c 09 Choose 'Close' to terminate the application"

Does anyone know what that is all about and how to fix it?

Thanks

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From mdelyea at gmail.com  Mon Mar  2 09:00:28 2009
From: mdelyea at gmail.com (mike delyea)
Date: Mon, 2 Mar 2009 09:00:28 -0500
Subject: [Coco] HD power supply times 10
In-Reply-To: <00e401c99ae8$46dabbc0$6401a8c0@OLDGEORGE>
References: <514098.75166.qm@web37301.mail.mud.yahoo.com>
	<00e401c99ae8$46dabbc0$6401a8c0@OLDGEORGE>
Message-ID: <1b52e6c80903020600q4d18b967ic01a8a766af7cc5e@mail.gmail.com>

I use gmail and don't get any extra copies.

On Sun, Mar 1, 2009 at 10:37 PM, George Ramsower
<georgeramsower at gmail.com> wrote:
> On all messages, I get one of each.
> WinXP SP3 Outlook Express
>
> ----- Original Message ----- From: "Jim Hickle"
> George
>
>> so far I've gotten TEN copies of this message
>>
>>> From: Bruce W. Calkins
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From cwgordon at carolina.rr.com  Mon Mar  2 09:01:38 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Mon, 2 Mar 2009 09:01:38 -0500
Subject: [Coco] checksum
In-Reply-To: <5631e580903020512s76d0e755g792223ec8bffa961@mail.gmail.com>
References: <003001c99b34$b0fa2d00$12ee8700$@rr.com>
	<5631e580903020512s76d0e755g792223ec8bffa961@mail.gmail.com>
Message-ID: <003a01c99b3f$67fba600$37f2f200$@rr.com>

Found it, thanks. It is originally published in the February 1984 issue,
page 21, with a complete explanation of the program and how it works.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Rogelio Perea
> Sent: Monday, March 02, 2009 8:12 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] checksum
> 
> After The Rainbow started to use the RainbowCheck utility,
> issues had one page called "Rainbow Info" that included the
> listing. If you have any issue from February 1984 on forward
> you should be able to find the program there...
>



From jlhickle at yahoo.com  Mon Mar  2 09:46:55 2009
From: jlhickle at yahoo.com (Jim Hickle)
Date: Mon, 2 Mar 2009 06:46:55 -0800 (PST)
Subject: [Coco] HD power supply times 10
In-Reply-To: <1b52e6c80903020600q4d18b967ic01a8a766af7cc5e@mail.gmail.com>
Message-ID: <285251.32449.qm@web37308.mail.mud.yahoo.com>

Ah, a clue. I use Yahoo and got two copies of your messages so far.


--- On Mon, 3/2/09, mike delyea <mdelyea at gmail.com> wrote:

> From: mike delyea <mdelyea at gmail.com>
> Subject: Re: [Coco] HD power supply times 10
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Date: Monday, March 2, 2009, 9:00 AM
> I use gmail and don't get any extra copies.
> 
> On Sun, Mar 1, 2009 at 10:37 PM, George Ramsower
> <georgeramsower at gmail.com> wrote:
> > On all messages, I get one of each.
> > WinXP SP3 Outlook Express
> >
> > ----- Original Message ----- From: "Jim
> Hickle"
> > George
> >
> >> so far I've gotten TEN copies of this message
> >>
> >>> From: Bruce W. Calkins
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> >
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


      


From jlhickle at yahoo.com  Mon Mar  2 09:50:31 2009
From: jlhickle at yahoo.com (Jim Hickle)
Date: Mon, 2 Mar 2009 06:50:31 -0800 (PST)
Subject: [Coco] HD power supply
In-Reply-To: <01fb01c99aba$df6a73e0$9e3f5ba0$@rr.com>
Message-ID: <688430.91567.qm@web37302.mail.mud.yahoo.com>

I usually get a SCSI case off of ebay.  They have adequate power
supplies.  Remove the SCSI connector and run your ribbon cable
through the hole.



--- On Sun, 3/1/09, Bill <cwgordon at carolina.rr.com> wrote:

> From: Bill <cwgordon at carolina.rr.com>
> Subject: Re: [Coco] HD power supply
> To: "'CoCoList for Color Computer Enthusiasts'" <coco at maltedmedia.com>
> Date: Sunday, March 1, 2009, 5:12 PM
> Well, what if I just gut an old computer and get the power
> supply from it,
> mount IT in the FD-501 (or 502) case and go from there?
> 
> > -----Original Message-----
> > From: coco-bounces at maltedmedia.com [mailto:coco-
> > bounces at maltedmedia.com] On Behalf Of Bruce W. Calkins
> > Sent: Sunday, March 01, 2009 4:05 PM
> > To: CoCoList for Color Computer Enthusiasts
> > Subject: Re: [Coco] HD power supply
> > 
> > 
> > >> Is a power supply for a FD-501 or FD-502
> > >> sufficient to power an IDE hard drive (or
> two?)
> > >
> > > That might be a little borderline, Bill.
> > 
> > The Tandy FD-501 and 502 drives were a little light on
> the power
> > capability.
> > If you got the Tandy second drive kit they added a
> chintzy fan to keep
> > things cool enough to function.  And we all know that
> Tandy never put
> > anything into cooling, unless it burned them first.
> > 
> > Bruce W.
> > 
> > 
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


      


From jcewy at swbell.net  Mon Mar  2 10:30:02 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Mon, 02 Mar 2009 09:30:02 -0600
Subject: [Coco] proposal for CoCoFEST! talk
In-Reply-To: <004601c99aaf$f6e496a0$e4adc3e0$@com>
References: <20090301.001534.288.9.JohnChasteen.2@Juno.com>	<001a01c99a49$4250c710$c6f25530$@com>	<49AAE4C7.9020005@sbcglobal.net>
	<004601c99aaf$f6e496a0$e4adc3e0$@com>
Message-ID: <49ABFB7A.4090403@swbell.net>

Tom Seagrove wrote:
> I was referring to some from the 80's...
>
> Tom
>
>   
I believe Roger Taylor has some of that footage on his CoCo DVD.  Am I 
right Roger?

JCE

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
> Behalf Of Brian Goers
> Sent: Sunday, March 01, 2009 2:41 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] proposal for CoCoFEST! talk
>
> Tom Seagrove wrote:
>   
>> What would one give to get a hold of some video from some Rainbow Fests
>> along with a couple seminars?  Would that be of any interest?
>>
>> Tom
>>
>> ----
>>     
> What is needed is someone able to record the events. Allen is not able 
> to this time.
> If any one is able and willing to do this let us know.
> I've seen offers to pay $5.00 for a disk.
> Brian
>
>   



From coconut at pritchard.ca  Mon Mar  2 11:18:04 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Mon, 2 Mar 2009 10:18:04 -0600
Subject: [Coco] HD power supply times 10
In-Reply-To: <285251.32449.qm@web37308.mail.mud.yahoo.com>
References: <1b52e6c80903020600q4d18b967ic01a8a766af7cc5e@mail.gmail.com>
	<285251.32449.qm@web37308.mail.mud.yahoo.com>
Message-ID: <1806abd60903020818n737ab5c1j8ded3b7537149909@mail.gmail.com>

The use of g-mail is not so much a clue, with regards to only getting 1 copy
of the same message.  I myself use Google Apps for my personal domains, and
I am only getting one copy of the messages.  However that is a feature of
G-Mail, and not indicative of whether or not I am receiving more than one
copy of messages from this list.  Please see
http://slashdot.org/~t-maxx+cowboy/journal/209653 for more information on my
assessment of G-Mails handling of duplicate e-mail.  Really nice behavior if
you ask me, as I had to many backup archives of mail from different times
and anytime I restored to a new system I used to spend hours weeding out
duplicates that resulted from the restores/imports.

I myself am only subscribed to this list via
http://five.pairlist.net/mailman/listinfo/coco.  I do have a Yahoo account
tied to the Yahoo Groups group that is linked to this mailing list, however
I do not have the Yahoo group setup to give me any sort of messages to my
mailbox.

Anyway for those of us using a G-Mail based mail service we won't actually
see the duplicates even if they are occuring.

On Mon, Mar 2, 2009 at 8:46 AM, Jim Hickle <jlhickle at yahoo.com> wrote:

> Ah, a clue. I use Yahoo and got two copies of your messages so far.
>
>
> --- On Mon, 3/2/09, mike delyea <mdelyea at gmail.com> wrote:
>
> > From: mike delyea <mdelyea at gmail.com>
> > Subject: Re: [Coco] HD power supply times 10
> > To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> > Date: Monday, March 2, 2009, 9:00 AM
> > I use gmail and don't get any extra copies.
> >
> > On Sun, Mar 1, 2009 at 10:37 PM, George Ramsower
> > <georgeramsower at gmail.com> wrote:
> > > On all messages, I get one of each.
> > > WinXP SP3 Outlook Express
> > >
> > > ----- Original Message ----- From: "Jim
> > Hickle"
> > > George
> > >
> > >> so far I've gotten TEN copies of this message
> > >>
> > >>> From: Bruce W. Calkins
> > >
> > >
> > > --
> > > Coco mailing list
> > > Coco at maltedmedia.com
> > > http://five.pairlist.net/mailman/listinfo/coco
> > >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From paulh96636 at aol.com  Mon Mar  2 11:39:35 2009
From: paulh96636 at aol.com (paulh96636 at aol.com)
Date: Mon, 02 Mar 2009 11:39:35 -0500
Subject: [Coco] HD power supply times 10
In-Reply-To: <514098.75166.qm@web37301.mail.mud.yahoo.com>
Message-ID: <8CB696C9AE9123B-E48-1236@WEBMAIL-DC15.sysops.aol.com>

A short note on what might cause multiple copies: ?I *used to* do this when using my HP pocket pc - sending email
would leave multiple copies in the recipient's mailbox for no apparent reason. ?Perhaps it's a fault with mobile PCs,

or Windows CE. ?Various complaints got no response in resolving the issue. ?




Since then, I've found that when the 'mail sent' screen appears, that backing off that screen immediately, seems to

'cure' the problem since it no longer happens. ? ?hth, ? ? ?-ph


-----Original Message-----
From: Jim Hickle <jlhickle at yahoo.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Sun, 1 Mar 2009 10:17 pm
Subject: Re: [Coco] HD power supply times 10








so far I've gotten TEN copies of this message



--- On Sun, 3/1/09, Bruce W. Calkins <brucewcalkins at charter.net> wrote:

> From: Bruce W. Calkins <brucewcalkins at charter.net>
> Subject: Re: [Coco] HD power supply
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Date: Sunday, March 1, 2009, 4:04 PM
> >> Is a power supply for a FD-501 or FD-502
> >> sufficient to power an IDE hard drive (or two?)
> > 
> > That might be a little borderline, Bill.
> 
> The Tandy FD-501 and 502 drives were a little light on the
> power capability. If you got the Tandy second drive kit they
> added a chintzy fan to keep things cool enough to function. 
> And we all know that Tandy never put anything into cooling,
> unless it burned th
em first.
> 
> Bruce W. 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


      

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



 






From jcewy at swbell.net  Mon Mar  2 11:50:35 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Mon, 02 Mar 2009 10:50:35 -0600
Subject: [Coco] Coco3 emulator
In-Reply-To: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
Message-ID: <49AC0E5B.6090100@swbell.net>

Which CoCo 3 emulator are you trying to use?  Jeff Vavasour's, VCC, 
David Keil's emulator, ROC, MESS?  Or one of the Dragon/CoCo emulators.  
Is this Linux, Mac, MS-DOS, or MS-Windows?  There are a wealth of 
possibilities for emulating the CoCo in software.

JCE

Bill wrote:
> I have been trying to use the Coco3 emulator for some time now, but every
> time I do, I get an error that says:
>  "The NTVDM CPU has encountered an illegal instruction. C5:17b4 IP:003a
> OP:dd 0c e0 0c 09 Choose 'Close' to terminate the application"
>
> Does anyone know what that is all about and how to fix it?
>
> Thanks
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>   



From cwgordon at carolina.rr.com  Mon Mar  2 12:15:40 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Mon, 2 Mar 2009 12:15:40 -0500
Subject: [Coco] Coco3 emulator
In-Reply-To: <49AC0E5B.6090100@swbell.net>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
	<49AC0E5B.6090100@swbell.net>
Message-ID: <004401c99b5a$8359eb80$8a0dc280$@rr.com>

1. This is jeff vavasour's CoCo3 emulator
	(the CoCo1 and 2 do fine - even though I don't know how to use them
very well)
2. I'm using Windows XP SP2

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Joel Ewy
> Sent: Monday, March 02, 2009 11:51 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Coco3 emulator
> 
> Which CoCo 3 emulator are you trying to use?  Jeff Vavasour's, VCC,
> David Keil's emulator, ROC, MESS?  Or one of the Dragon/CoCo emulators.
> Is this Linux, Mac, MS-DOS, or MS-Windows?  There are a wealth of
> possibilities for emulating the CoCo in software.
> 



From afra at aurigae.demon.co.uk  Mon Mar  2 12:32:02 2009
From: afra at aurigae.demon.co.uk (afra at aurigae.demon.co.uk)
Date: Mon, 02 Mar 2009 17:32:02 +0000
Subject: [Coco] Coco3 emulator
In-Reply-To: <49AC0E5B.6090100@swbell.net>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
	<49AC0E5B.6090100@swbell.net>
Message-ID: <20090302173202.145615map7bodmpw@aurigae.demon.co.uk>

Quoting Joel Ewy <jcewy at swbell.net>:
> Bill wrote:
>> I have been trying to use the Coco3 emulator for some time now, but every
>> time I do, I get an error that says:
>> "The NTVDM CPU has encountered an illegal instruction. C5:17b4 IP:003a
>> OP:dd 0c e0 0c 09 Choose 'Close' to terminate the application"
>
> Which CoCo 3 emulator are you trying to use?  Jeff Vavasour's, VCC,  
> David Keil's emulator, ROC, MESS?  Or one of the Dragon/CoCo  
> emulators.  Is this Linux, Mac, MS-DOS, or MS-Windows?  There are a  
> wealth of possibilities for emulating the CoCo in software.

Some clues from Bill's original post.

The NTVDM (NT Virtual DOS Machine) sugests that this is a dos based  
emulator running on a windows NT class machine, so Windows  
NT/2000/XP/2003/Vista/2008.

The address being specified as CS:IP also sugests a dos based program,  
I would sugest that it is trying to directly access the machine's  
hardware and windows is preventing it.

However Bill, Joel does have a valid point we will be able to help you  
much better if you tell us what emulator you are using and under what  
environment.

On a side note, I wasn't aware of any of the Dragon based emulators,  
also emulating the CoCo 3 (cirtainly not PCDragon or XRoar).

Cheers.

Phill.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



From lamune at doki-doki.net  Mon Mar  2 13:30:43 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Mon, 2 Mar 2009 10:30:43 -0800
Subject: [Coco] HD power supply
In-Reply-To: <01f601c99aa5$8ec00500$ac400f00$@rr.com>
References: <01f601c99aa5$8ec00500$ac400f00$@rr.com>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B19C@fenestra.lamunet.local>

Hey Bill,

I think you've gotten enough responses to this, but I'll throw in a
couple of cents.

You can stick a small switcher power supply in a CoCo floppy case with a
little fan. I've done this and it works great- but given how you
describe your physical condition it may not be something you'd be able
to do.

If I were looking to add an IDE to a CoCo these days, I'd skip the drive
entirely for a couple of reasons.

1: Any hard drive you buy new today would be insanely oversized for the
need
2: Any old drive in the practical range for CoCo use would be so old it
would likely die at any moment

I think the way to go would be to use an IDE to compactflash adapter and
use a 1 to 4 gig CF card. With the tiny power consumption of a CF you
may even be able to install the thing inside the CoCo.



-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com]
On Behalf Of Bill
Sent: Sunday, March 01, 2009 11:40 AM
To: CoCoList for Color Computer Enthusiasts
Subject: [Coco] HD power supply

Is a power supply for a FD-501 or FD-502 sufficient to power an IDE hard
drive (or two?)

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784



--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



From operator at coco3.com  Mon Mar  2 13:43:01 2009
From: operator at coco3.com (Roger Taylor)
Date: Mon, 02 Mar 2009 12:43:01 -0600
Subject: [Coco] Coco3 emulator
In-Reply-To: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
Message-ID: <20090302184314.DE5BE20A13@qs281.pair.com>

At 07:53 AM 3/2/2009, you wrote:
>I have been trying to use the Coco3 emulator for some time now, but every
>time I do, I get an error that says:
>  "The NTVDM CPU has encountered an illegal instruction. C5:17b4 IP:003a
>OP:dd 0c e0 0c 09 Choose 'Close' to terminate the application"
>
>Does anyone know what that is all about and how to fix it?
>
>Thanks

There's a handful of CoCo 3 emulators.  I assume you're talking about 
Jeff Vavasour's version.  It bombs out on my Vista laptop and I think 
I recall the same or similar error message.  He wrote it for the 
16-bit MS-DOS environment, so this doesn't surprise me.

-- 
Roger Taylor

http://www.wordofthedayonline.com



From operator at coco3.com  Mon Mar  2 13:52:20 2009
From: operator at coco3.com (Roger Taylor)
Date: Mon, 02 Mar 2009 12:52:20 -0600
Subject: [Coco] proposal for CoCoFEST! talk
In-Reply-To: <49ABFB7A.4090403@swbell.net>
References: <20090301.001534.288.9.JohnChasteen.2@Juno.com>
	<001a01c99a49$4250c710$c6f25530$@com>
	<49AAE4C7.9020005@sbcglobal.net>
	<004601c99aaf$f6e496a0$e4adc3e0$@com> <49ABFB7A.4090403@swbell.net>
Message-ID: <20090302185241.D77A420A13@qs281.pair.com>

At 09:30 AM 3/2/2009, you wrote:
>Tom Seagrove wrote:
>>I was referring to some from the 80's...
>>
>>Tom
>>
>>
>I believe Roger Taylor has some of that footage on his CoCo DVD.  Am 
>I right Roger?

I put out a 90+min video DVD called CoCo TV that has the highlights 
of PennFest 2000 (provided by Nick Marentes).  The DVD is menu driven 
and has an awesome 20th Century Fox like sequence that can be 
mistaken for a movie intro if you're not paying close attention.  :)


-- 
Roger Taylor

http://www.wordofthedayonline.com



From operator at coco3.com  Mon Mar  2 13:56:19 2009
From: operator at coco3.com (Roger Taylor)
Date: Mon, 02 Mar 2009 12:56:19 -0600
Subject: [Coco] Coco3 emulator
In-Reply-To: <20090302173202.145615map7bodmpw@aurigae.demon.co.uk>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
	<49AC0E5B.6090100@swbell.net>
	<20090302173202.145615map7bodmpw@aurigae.demon.co.uk>
Message-ID: <20090302190305.326E920A13@qs281.pair.com>

At 11:32 AM 3/2/2009, you wrote:
>Quoting Joel Ewy <jcewy at swbell.net>:
>>Bill wrote:
>>>I have been trying to use the Coco3 emulator for some time now, but every
>>>time I do, I get an error that says:
>>>"The NTVDM CPU has encountered an illegal instruction. C5:17b4 IP:003a
>>>OP:dd 0c e0 0c 09 Choose 'Close' to terminate the application"
>>
>>Which CoCo 3 emulator are you trying to use?  Jeff Vavasour's, VCC,
>>David Keil's emulator, ROC, MESS?  Or one of the Dragon/CoCo
>>emulators.  Is this Linux, Mac, MS-DOS, or MS-Windows?  There are a
>>wealth of possibilities for emulating the CoCo in software.
>
>Some clues from Bill's original post.
>
>The NTVDM (NT Virtual DOS Machine) sugests that this is a dos based
>emulator running on a windows NT class machine, so Windows
>NT/2000/XP/2003/Vista/2008.
>
>The address being specified as CS:IP also sugests a dos based program,
>I would sugest that it is trying to directly access the machine's
>hardware and windows is preventing it.


I've run Vavasour's emulator under XP for years (off and on).  It 
didn't look pretty but you could at least launch it and do some 
things.  Now it doesn't work under XP?  This screams of Microsoft to blame.

Maybe try the compatibility settings by right clicking the .exe file 
and then Properties.




-- 
Roger Taylor

http://www.wordofthedayonline.com



From cwgordon at carolina.rr.com  Mon Mar  2 14:15:15 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Mon, 2 Mar 2009 14:15:15 -0500
Subject: [Coco] Coco3 emulator
In-Reply-To: <20090302190305.326E920A13@qs281.pair.com>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>	<49AC0E5B.6090100@swbell.net>	<20090302173202.145615map7bodmpw@aurigae.demon.co.uk>
	<20090302190305.326E920A13@qs281.pair.com>
Message-ID: <005501c99b6b$37d12870$a7737950$@rr.com>

Nope, neither of the 4 choices works.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Roger Taylor
> Sent: Monday, March 02, 2009 1:56 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Coco3 emulator
>  
> I've run Vavasour's emulator under XP for years (off and on).  It
> didn't look pretty but you could at least launch it and do some
> things.  Now it doesn't work under XP?  This screams of Microsoft to
> blame.
> 
> Maybe try the compatibility settings by right clicking the .exe file
> and then Properties.
> 



From cyberpunk at prtc.net  Mon Mar  2 14:47:16 2009
From: cyberpunk at prtc.net (RJLCyberPunk)
Date: Mon, 2 Mar 2009 15:47:16 -0400
Subject: [Coco] Coco3 emulator
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
	<49AC0E5B.6090100@swbell.net>
Message-ID: <F30FFC0C20264AB2BB537013B57B7A21@FANTASYWARE>

I got VCC and MESS myself... :D
----- Original Message ----- 
From: "Joel Ewy" <jcewy at swbell.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Monday, March 02, 2009 12:50 PM
Subject: Re: [Coco] Coco3 emulator


> Which CoCo 3 emulator are you trying to use?  Jeff Vavasour's, VCC, 
> David Keil's emulator, ROC, MESS?  Or one of the Dragon/CoCo emulators.  
> Is this Linux, Mac, MS-DOS, or MS-Windows?  There are a wealth of 
> possibilities for emulating the CoCo in software.
> 



From Nuxie at aol.com  Mon Mar  2 15:18:08 2009
From: Nuxie at aol.com (Nuxie at aol.com)
Date: Mon, 2 Mar 2009 15:18:08 EST
Subject: [Coco] [Color Computer] Look for coco stuff
Message-ID: <bc5.43a5cdab.36dd9900@aol.com>

Wich coco3 manuals do you need. Let me know I may be able to help you out. 
Mary
 
 
In a message dated 2/27/2009 3:45:30 P.M. Central Standard Time,  
mervc at eol.ca writes:

On  Sunday 08 February 2009, seanrussoct08 wrote:
> I am looking for the  following items, if anyone has any they wish to sell.
>
> RS232  Program-Pak
> Coco 3 manuals
> deluxe color  mouse
>
>
Since the Modem Pak is easy to convert to plain  RS232,  add that to your 
list.


-- 
Merv Curley
Toronto,  Ont. Can

Debian Sid Linux    
Desktop  KDE  3.5.10    KMail 1.9.9




--
Coco mailing  list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


**************A Good Credit Score is 700 or Above. See yours in just 2 easy 
steps! 
(http://pr.atwola.com/promoclk/100126575x1219957551x1201325337/aol?redir=http:%2F%2Fwww.freecreditreport.com%2Fpm%2Fdefault.aspx%3Fsc%3D668072%26hmpgID
%3D62%26bcd%3DfebemailfooterNO62)


From linville at tuxdriver.com  Mon Mar  2 15:43:59 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Mon, 02 Mar 2009 15:43:59 -0500
Subject: [Coco] =?iso-8859-1?q?Possible_solution_for_yellowing_plastic=3F_?=
 =?iso-8859-1?q?--_Retr0Bright_=BB_home?=
Message-ID: <1236026639.14075.0.camel@localhost.localdomain>

http://retr0bright.wikispaces.com/



From mechacoco at gmail.com  Mon Mar  2 15:50:21 2009
From: mechacoco at gmail.com (Darren A)
Date: Mon, 2 Mar 2009 13:50:21 -0700
Subject: [Coco] Coco3 emulator
In-Reply-To: <004401c99b5a$8359eb80$8a0dc280$@rr.com>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
	<49AC0E5B.6090100@swbell.net> <004401c99b5a$8359eb80$8a0dc280$@rr.com>
Message-ID: <5d802cd0903021250p68a8850cm3632aec6509fb12b@mail.gmail.com>

On 3/2/09, Bill wrote:
> 1. This is jeff vavasour's CoCo3 emulator
> 	(the CoCo1 and 2 do fine - even though I don't know how to use them
> very well)
> 2. I'm using Windows XP SP2
>
--

Bill,

Since you are running Windows XP, I would recommend that you try the
VCC CoCo 3 emulator instead:

<http://vcc6809.bravehost.com/>

Darren


From robert.gault at worldnet.att.net  Mon Mar  2 15:59:13 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Mon, 02 Mar 2009 15:59:13 -0500
Subject: [Coco] Coco3 emulator
In-Reply-To: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
Message-ID: <49AC48A1.1070809@worldnet.att.net>

Bill wrote:
> I have been trying to use the Coco3 emulator for some time now, but every
> time I do, I get an error that says:
>  "The NTVDM CPU has encountered an illegal instruction. C5:17b4 IP:003a
> OP:dd 0c e0 0c 09 Choose 'Close' to terminate the application"
> 
> Does anyone know what that is all about and how to fix it?
> 
> Thanks
> 

There are several versions of the Vavasour Coco3 emulator but that might 
not be the issue. To run this under WinXP, you must provide the correct 
environment. That requires you to edit the file CONFIG.NT (should be in 
Windows\System32).

dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=100


Create a shortcut file with the following memory settings.
"Auto" for all memory entries and check the box "uses HMA".

You will probably want to have an empty file named 2Megs in the same 
directory as the program.


From cwgordon at carolina.rr.com  Mon Mar  2 16:15:41 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Mon, 2 Mar 2009 16:15:41 -0500
Subject: [Coco] Coco3 emulator
In-Reply-To: <49AC48A1.1070809@worldnet.att.net>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
	<49AC48A1.1070809@worldnet.att.net>
Message-ID: <000001c99b7c$0addfc60$2099f520$@rr.com>

Well, I did all that, and still nothing. 

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Monday, March 02, 2009 3:59 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Coco3 emulator
> 
> There are several versions of the Vavasour Coco3 emulator but that
> might
> not be the issue. To run this under WinXP, you must provide the correct
> environment. That requires you to edit the file CONFIG.NT (should be in
> Windows\System32).
> 
> dos=high, umb
> device=%SystemRoot%\system32\himem.sys
> files=100
> 
> 
> Create a shortcut file with the following memory settings.
> "Auto" for all memory entries and check the box "uses HMA".
> 
> You will probably want to have an empty file named 2Megs in the same
> directory as the program.



From lamune at doki-doki.net  Mon Mar  2 16:21:13 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Mon, 2 Mar 2009 13:21:13 -0800
Subject: [Coco] Coco3 emulator
In-Reply-To: <000001c99b7c$0addfc60$2099f520$@rr.com>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com><49AC48A1.1070809@worldnet.att.net>
	<000001c99b7c$0addfc60$2099f520$@rr.com>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B19D@fenestra.lamunet.local>

Make sure you've got CPU microcode update enabled in the BIOS. I had all
sorts of NTVDM issues because that option was disabled. (AMD cpu
specifically)

If you open a 16 bit command prompt, do you get the NTVDM issues? (start
-> run -> command)

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com]
On Behalf Of Bill
Sent: Monday, March 02, 2009 1:16 PM
To: 'CoCoList for Color Computer Enthusiasts'
Subject: Re: [Coco] Coco3 emulator

Well, I did all that, and still nothing. 

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Monday, March 02, 2009 3:59 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Coco3 emulator
> 
> There are several versions of the Vavasour Coco3 emulator but that
> might
> not be the issue. To run this under WinXP, you must provide the
correct
> environment. That requires you to edit the file CONFIG.NT (should be
in
> Windows\System32).
> 
> dos=high, umb
> device=%SystemRoot%\system32\himem.sys
> files=100
> 
> 
> Create a shortcut file with the following memory settings.
> "Auto" for all memory entries and check the box "uses HMA".
> 
> You will probably want to have an empty file named 2Megs in the same
> directory as the program.


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



From cwgordon at carolina.rr.com  Mon Mar  2 16:31:37 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Mon, 2 Mar 2009 16:31:37 -0500
Subject: [Coco] Coco3 emulator
In-Reply-To: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B19D@fenestra.lamunet.local>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com><49AC48A1.1070809@worldnet.att.net>	<000001c99b7c$0addfc60$2099f520$@rr.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B19D@fenestra.lamunet.local>
Message-ID: <000101c99b7e$4530cb20$cf926160$@rr.com>

Have no idea what microcode update is. I do have an AMD, however. When I
open run-> command I get no errors

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Mike Pepe
> Sent: Monday, March 02, 2009 4:21 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Coco3 emulator
> 
> Make sure you've got CPU microcode update enabled in the BIOS. I had
> all
> sorts of NTVDM issues because that option was disabled. (AMD cpu
> specifically)
> 
> If you open a 16 bit command prompt, do you get the NTVDM issues?
> (start
> -> run -> command)
> 



From coconut at pritchard.ca  Mon Mar  2 16:31:53 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Mon, 2 Mar 2009 15:31:53 -0600
Subject: [Coco] Coco3 emulator
In-Reply-To: <000001c99b7c$0addfc60$2099f520$@rr.com>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
	<49AC48A1.1070809@worldnet.att.net>
	<000001c99b7c$0addfc60$2099f520$@rr.com>
Message-ID: <1806abd60903021331r2b7ab65x8d08fe862a7d07af@mail.gmail.com>

I hope you found a copy of the system's ROM files, otherwise no matter what
emulator you use, you likely won't get it to work.

On Mon, Mar 2, 2009 at 3:15 PM, Bill <cwgordon at carolina.rr.com> wrote:

> Well, I did all that, and still nothing.
>
> > -----Original Message-----
> > From: coco-bounces at maltedmedia.com [mailto:coco-
> > bounces at maltedmedia.com] On Behalf Of Robert Gault
> > Sent: Monday, March 02, 2009 3:59 PM
> > To: CoCoList for Color Computer Enthusiasts
> > Subject: Re: [Coco] Coco3 emulator
> >
> > There are several versions of the Vavasour Coco3 emulator but that
> > might
> > not be the issue. To run this under WinXP, you must provide the correct
> > environment. That requires you to edit the file CONFIG.NT (should be in
> > Windows\System32).
> >
> > dos=high, umb
> > device=%SystemRoot%\system32\himem.sys
> > files=100
> >
> >
> > Create a shortcut file with the following memory settings.
> > "Auto" for all memory entries and check the box "uses HMA".
> >
> > You will probably want to have an empty file named 2Megs in the same
> > directory as the program.
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From cwgordon at carolina.rr.com  Mon Mar  2 16:51:42 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Mon, 2 Mar 2009 16:51:42 -0500
Subject: [Coco] Coco3 emulator
In-Reply-To: <1806abd60903021331r2b7ab65x8d08fe862a7d07af@mail.gmail.com>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>	<49AC48A1.1070809@worldnet.att.net>	<000001c99b7c$0addfc60$2099f520$@rr.com>
	<1806abd60903021331r2b7ab65x8d08fe862a7d07af@mail.gmail.com>
Message-ID: <000201c99b81$13553ed0$39ffbc70$@rr.com>

Yeah, I was lucky enough to find all the rom files I needed. I got hold of
VCC emulator, and it seems to do well. I just don't know what to do with it
:) 

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Ryan Pritchard
> Sent: Monday, March 02, 2009 4:32 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Coco3 emulator
> 
> I hope you found a copy of the system's ROM files, otherwise no matter
> what
> emulator you use, you likely won't get it to work.
> 



From jdiffendaffer at yahoo.com  Mon Mar  2 17:04:32 2009
From: jdiffendaffer at yahoo.com (James Diffendaffer)
Date: Mon, 02 Mar 2009 22:04:32 -0000
Subject: [Coco] =?iso-8859-1?q?=5BColor_Computer=5D__Possible_solution_for?=
	=?iso-8859-1?q?_yellowing_plastic=3F_--_Retr0Bright_=BB_home?=
Message-ID: <gohl5g+4i7s@eGroups.com>

> http://retr0bright.wikispaces.com/

that's the same method I mentioned here:
http://five.pairlist.net/pipermail/coco/2009-February/040311.html

The most recent news seems to be that lower % hydrogen peroxide
solutions work if you give it multiple days.
3% might actually give more even results.

I have a multipack and my original coco monitor I'm going to try it on
one of these days.  If it fixes the monitor I'll be sold.  It's never
been near smoke but looks like it was in a bar for 20 years.




From os9dude at gmail.com  Mon Mar  2 18:31:57 2009
From: os9dude at gmail.com (Rogelio Perea)
Date: Mon, 2 Mar 2009 18:31:57 -0500
Subject: [Coco] Team OS9 (Seti@Home)
Message-ID: <5631e580903021531y59aa7d0alf4a6e4126f925927@mail.gmail.com>

Just the once every ten years reminder to the folks "out there" that want to
believe ;-)

I have been running the Seti at Home software on and off since 1989 and today
while checking my profile there I found that the founder status requested
last year for Team OS9 had been OK'd for transfer from the original founder
(DigitalAsphyxia - can't recall the real name at this moment). So I decided
to check it out, only 6 members of which two are the sole active ones -
cobwebs everywhere!

http://setiathome.berkeley.edu/team_display.php?teamid=36796

Thanks for the bandwidth  _\\//



-=-[ Rogelio ]=-


From joef6809 at gmail.com  Mon Mar  2 18:49:50 2009
From: joef6809 at gmail.com (Joe)
Date: Mon, 2 Mar 2009 18:49:50 -0500
Subject: [Coco] Coco3 emulator
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>
	<49AC48A1.1070809@worldnet.att.net>
Message-ID: <C942A9EDB4A04D19948D05316CC5CC81@LT1>

I've only seen that problem when a dos executable is corrupt, Can you try to 
redownload it? I know Jeff's EMU will work on XP under full screen.

----- Original Message ----- 
From: "Robert Gault" <robert.gault at worldnet.att.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Monday, March 02, 2009 3:59 PM
Subject: Re: [Coco] Coco3 emulator


> Bill wrote:
>> I have been trying to use the Coco3 emulator for some time now, but every
>> time I do, I get an error that says:
>>  "The NTVDM CPU has encountered an illegal instruction. C5:17b4 IP:003a
>> OP:dd 0c e0 0c 09 Choose 'Close' to terminate the application"
>>
>> Does anyone know what that is all about and how to fix it?
>>
>> Thanks
>>
>
> There are several versions of the Vavasour Coco3 emulator but that might 
> not be the issue. To run this under WinXP, you must provide the correct 
> environment. That requires you to edit the file CONFIG.NT (should be in 
> Windows\System32).
>
> dos=high, umb
> device=%SystemRoot%\system32\himem.sys
> files=100
>
>
> Create a shortcut file with the following memory settings.
> "Auto" for all memory entries and check the box "uses HMA".
>
> You will probably want to have an empty file named 2Megs in the same 
> directory as the program.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From alsplace at pobox.com  Mon Mar  2 18:56:34 2009
From: alsplace at pobox.com (Allen Huffman)
Date: Mon, 2 Mar 2009 16:56:34 -0700
Subject: [Coco] Team OS9 (Seti@Home)
In-Reply-To: <5631e580903021531y59aa7d0alf4a6e4126f925927@mail.gmail.com>
References: <5631e580903021531y59aa7d0alf4a6e4126f925927@mail.gmail.com>
Message-ID: <1E6BE6DB-0A52-4CF0-B708-873C3ABFD8A4@pobox.com>

Chet Simspon I think. Am I still listed?haven't ran it in years.

Sent from my iPhone
Follow me on Twitter - http://twitter.com/allenhuffman

On Mar 2, 2009, at 4:31 PM, Rogelio Perea <os9dude at gmail.com> wrote:

> Just the once every ten years reminder to the folks "out there" that  
> want to
> believe ;-)
>
> I have been running the Seti at Home software on and off since 1989 and  
> today
> while checking my profile there I found that the founder status  
> requested
> last year for Team OS9 had been OK'd for transfer from the original  
> founder
> (DigitalAsphyxia - can't recall the real name at this moment). So I  
> decided
> to check it out, only 6 members of which two are the sole active  
> ones -
> cobwebs everywhere!
>
> http://setiathome.berkeley.edu/team_display.php?teamid=36796
>
> Thanks for the bandwidth  _\\//
>
>
>
> -=-[ Rogelio ]=-
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


From joef6809 at gmail.com  Mon Mar  2 18:57:23 2009
From: joef6809 at gmail.com (Joe)
Date: Mon, 2 Mar 2009 18:57:23 -0500
Subject: [Coco] Coco3 emulator
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com><49AC48A1.1070809@worldnet.att.net>
	<000001c99b7c$0addfc60$2099f520$@rr.com>
Message-ID: <B6A256F4687D47D09C495AFC16C0139C@LT1>

I found your problem. I bet your rom image is exactly 32768 bytes. Jeffs EMU 
needs a 2 byte header to tell it where to load.
If this is the case (right click -> properties) Contact me off list 
joef6809 at gmail.com
----- Original Message ----- 
From: "Bill" <cwgordon at carolina.rr.com>
To: "'CoCoList for Color Computer Enthusiasts'" <coco at maltedmedia.com>
Sent: Monday, March 02, 2009 4:15 PM
Subject: Re: [Coco] Coco3 emulator


> Well, I did all that, and still nothing.
>
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Robert Gault
>> Sent: Monday, March 02, 2009 3:59 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] Coco3 emulator
>>
>> There are several versions of the Vavasour Coco3 emulator but that
>> might
>> not be the issue. To run this under WinXP, you must provide the correct
>> environment. That requires you to edit the file CONFIG.NT (should be in
>> Windows\System32).
>>
>> dos=high, umb
>> device=%SystemRoot%\system32\himem.sys
>> files=100
>>
>>
>> Create a shortcut file with the following memory settings.
>> "Auto" for all memory entries and check the box "uses HMA".
>>
>> You will probably want to have an empty file named 2Megs in the same
>> directory as the program.
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From jcewy at swbell.net  Mon Mar  2 18:57:21 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Mon, 02 Mar 2009 17:57:21 -0600
Subject: [Coco] Coco3 emulator
In-Reply-To: <20090302173202.145615map7bodmpw@aurigae.demon.co.uk>
References: <003501c99b3e$4a5fcdc0$df1f6940$@rr.com>	<49AC0E5B.6090100@swbell.net>
	<20090302173202.145615map7bodmpw@aurigae.demon.co.uk>
Message-ID: <49AC7261.3020602@swbell.net>

afra at aurigae.demon.co.uk wrote:
> ...
>
> On a side note, I wasn't aware of any of the Dragon based emulators, 
> also emulating the CoCo 3 (cirtainly not PCDragon or XRoar).
>
Right.  I zoned out on the fact that he mentioned that it was a CoCo >3< 
emulator...

JCE

> Cheers.
>
> Phill.
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



From os9dude at gmail.com  Mon Mar  2 19:04:14 2009
From: os9dude at gmail.com (Rogelio Perea)
Date: Mon, 2 Mar 2009 19:04:14 -0500
Subject: [Coco] Team OS9 (Seti@Home)
In-Reply-To: <1E6BE6DB-0A52-4CF0-B708-873C3ABFD8A4@pobox.com>
References: <5631e580903021531y59aa7d0alf4a6e4126f925927@mail.gmail.com>
	<1E6BE6DB-0A52-4CF0-B708-873C3ABFD8A4@pobox.com>
Message-ID: <5631e580903021604y697d02w5c0faf92123c2fe7@mail.gmail.com>

Chet Simpson... that's it! :-)

I don't think you're listed there Allen...



On Mon, Mar 2, 2009 at 6:56 PM, Allen Huffman <alsplace at pobox.com> wrote:

> Chet Simspon I think. Am I still listed?haven't ran it in years.
>
> Sent from my iPhone
> Follow me on Twitter - http://twitter.com/allenhuffman
>
>
> On Mar 2, 2009, at 4:31 PM, Rogelio Perea <os9dude at gmail.com> wrote:
>
>  Just the once every ten years reminder to the folks "out there" that want
>> to
>> believe ;-)
>>
>> I have been running the Seti at Home software on and off since 1989 and
>> today
>> while checking my profile there I found that the founder status requested
>> last year for Team OS9 had been OK'd for transfer from the original
>> founder
>> (DigitalAsphyxia - can't recall the real name at this moment). So I
>> decided
>> to check it out, only 6 members of which two are the sole active ones -
>> cobwebs everywhere!
>>
>> http://setiathome.berkeley.edu/team_display.php?teamid=36796
>>
>> Thanks for the bandwidth  _\\//
>>
>


From alsplace at pobox.com  Mon Mar  2 19:11:19 2009
From: alsplace at pobox.com (Allen Huffman)
Date: Mon, 2 Mar 2009 17:11:19 -0700
Subject: [Coco] Team OS9 (Seti@Home)
In-Reply-To: <5631e580903021604y697d02w5c0faf92123c2fe7@mail.gmail.com>
References: <5631e580903021531y59aa7d0alf4a6e4126f925927@mail.gmail.com>
	<1E6BE6DB-0A52-4CF0-B708-873C3ABFD8A4@pobox.com>
	<5631e580903021604y697d02w5c0faf92123c2fe7@mail.gmail.com>
Message-ID: <0575CD3B-48B3-4031-BDFC-631F89482F14@pobox.com>

We had two. One was that one, and I probably joined Team Microware or  
something.

Sent from my iPhone
Follow me on Twitter - http://twitter.com/allenhuffman

On Mar 2, 2009, at 5:04 PM, Rogelio Perea <os9dude at gmail.com> wrote:

> Chet Simpson... that's it! :-)
>
> I don't think you're listed there Allen...
>
>
>
> On Mon, Mar 2, 2009 at 6:56 PM, Allen Huffman <alsplace at pobox.com>  
> wrote:
>
>> Chet Simspon I think. Am I still listed?haven't ran it in years.
>>
>> Sent from my iPhone
>> Follow me on Twitter - http://twitter.com/allenhuffman
>>
>>
>> On Mar 2, 2009, at 4:31 PM, Rogelio Perea <os9dude at gmail.com> wrote:
>>
>> Just the once every ten years reminder to the folks "out there"  
>> that want
>>> to
>>> believe ;-)
>>>
>>> I have been running the Seti at Home software on and off since 1989 and
>>> today
>>> while checking my profile there I found that the founder status  
>>> requested
>>> last year for Team OS9 had been OK'd for transfer from the original
>>> founder
>>> (DigitalAsphyxia - can't recall the real name at this moment). So I
>>> decided
>>> to check it out, only 6 members of which two are the sole active  
>>> ones -
>>> cobwebs everywhere!
>>>
>>> http://setiathome.berkeley.edu/team_display.php?teamid=36796
>>>
>>> Thanks for the bandwidth  _\\//
>>>
>>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


From jcewy at swbell.net  Mon Mar  2 22:06:45 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Mon, 02 Mar 2009 21:06:45 -0600
Subject: [Coco] MPI Schematics in PDF?
Message-ID: <49AC9EC5.100@swbell.net>

I was fairly certain I'd seen schematics for various models of the 
Multi-Pak Interface floating around, but can't locate any at the 
moment.  I do have my original manual for my 26-3124, which includes a 
schematic, but it isn't very illuminating since it is all just one big 
ASIC.  So what I'm really looking for is the 26-3024 PAL-based model.  
(Were there other models of the MPI?)

Anybody know off hand where such a schematic is available?

JCE



From jcewy at swbell.net  Mon Mar  2 22:16:49 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Mon, 02 Mar 2009 21:16:49 -0600
Subject: [Coco] MPI Schematics in PDF?
In-Reply-To: <49AC9EC5.100@swbell.net>
References: <49AC9EC5.100@swbell.net>
Message-ID: <49ACA121.9020602@swbell.net>

Addendum:  I notice that there is one in Frank Swygert's book "Tandy's 
Little Wonder".  However the scan is really illegible to the point that 
I can't even figure out what chip is what.

JCE

Joel Ewy wrote:
> I was fairly certain I'd seen schematics for various models of the 
> Multi-Pak Interface floating around, but can't locate any at the 
> moment.  I do have my original manual for my 26-3124, which includes a 
> schematic, but it isn't very illuminating since it is all just one big 
> ASIC.  So what I'm really looking for is the 26-3024 PAL-based model.  
> (Were there other models of the MPI?)
>
> Anybody know off hand where such a schematic is available?
>
> JCE
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



From devries.bob at gmail.com  Mon Mar  2 22:29:39 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Tue, 3 Mar 2009 13:29:39 +1000
Subject: [Coco] MPI Schematics in PDF?
References: <49AC9EC5.100@swbell.net> <49ACA121.9020602@swbell.net>
Message-ID: <003b01c99bb0$4b3abda0$0701a8c0@master>

Joel,

I have here some PDF files of the 26-3124 manual, and JPEGS of the 26-3024 
MPI schematics. The former are quite small, however the files for the 3024 
(4 of tham) are quite large (1.2 MB to 3.2MB).

I can email any of them.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Joel Ewy" <jcewy at swbell.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Tuesday, March 03, 2009 1:16 PM
Subject: Re: [Coco] MPI Schematics in PDF?


> Addendum:  I notice that there is one in Frank Swygert's book "Tandy's 
> Little Wonder".  However the scan is really illegible to the point that I 
> can't even figure out what chip is what.
>
> JCE
>
> Joel Ewy wrote:
>> I was fairly certain I'd seen schematics for various models of the 
>> Multi-Pak Interface floating around, but can't locate any at the moment. 
>> I do have my original manual for my 26-3124, which includes a schematic, 
>> but it isn't very illuminating since it is all just one big ASIC.  So 
>> what I'm really looking for is the 26-3024 PAL-based model.  (Were there 
>> other models of the MPI?)
>>
>> Anybody know off hand where such a schematic is available?
>>
>> JCE
>>
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From robert.gault at worldnet.att.net  Mon Mar  2 22:44:09 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Mon, 02 Mar 2009 22:44:09 -0500
Subject: [Coco] MPI Schematics in PDF?
In-Reply-To: <49ACA121.9020602@swbell.net>
References: <49AC9EC5.100@swbell.net> <49ACA121.9020602@swbell.net>
Message-ID: <49ACA789.7050306@worldnet.att.net>

Joel Ewy wrote:
> Addendum:  I notice that there is one in Frank Swygert's book "Tandy's 
> Little Wonder".  However the scan is really illegible to the point that 
> I can't even figure out what chip is what.
> 
> JCE
> 
> Joel Ewy wrote:
>> I was fairly certain I'd seen schematics for various models of the 
>> Multi-Pak Interface floating around, but can't locate any at the 
>> moment.  I do have my original manual for my 26-3124, which includes a 
>> schematic, but it isn't very illuminating since it is all just one big 
>> ASIC.  So what I'm really looking for is the 26-3024 PAL-based model.  
>> (Were there other models of the MPI?)
>>
>> Anybody know off hand where such a schematic is available?
>>
>> JCE

Try the manual here
ftp://maltedmedia.com/coco/MANUALS1/TANDY_HW/PAK/MULTIPAK


From jcewy at swbell.net  Mon Mar  2 22:46:27 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Mon, 02 Mar 2009 21:46:27 -0600
Subject: [Coco] MPI Schematics in PDF?
In-Reply-To: <003b01c99bb0$4b3abda0$0701a8c0@master>
References: <49AC9EC5.100@swbell.net> <49ACA121.9020602@swbell.net>
	<003b01c99bb0$4b3abda0$0701a8c0@master>
Message-ID: <49ACA813.60803@swbell.net>

Thanks Bob,

I have DSL, so receiving large files won't be a problem for me.  I'd 
love it if you'd email me the 3024 schematics especially, and the 3124 
manual while you're at it, if you don't mind.

JCE

Bob Devries wrote:
> Joel,
>
> I have here some PDF files of the 26-3124 manual, and JPEGS of the 
> 26-3024 MPI schematics. The former are quite small, however the files 
> for the 3024 (4 of tham) are quite large (1.2 MB to 3.2MB).
>
> I can email any of them.
>
> -- 
> Regards, Bob Devries, Dalby, Queensland, Australia
>
> Isaiah 50:4 The sovereign Lord has given me
> the capacity to be his spokesman,
> so that I know how to help the weary.
>
> website: http://www.home.gil.com.au/~bdevasl
> my blog: http://bdevries.invigorated.org/
>
> ----- Original Message ----- From: "Joel Ewy" <jcewy at swbell.net>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Tuesday, March 03, 2009 1:16 PM
> Subject: Re: [Coco] MPI Schematics in PDF?
>
>
>> Addendum:  I notice that there is one in Frank Swygert's book 
>> "Tandy's Little Wonder".  However the scan is really illegible to the 
>> point that I can't even figure out what chip is what.
>>
>> JCE
>>
>> Joel Ewy wrote:
>>> I was fairly certain I'd seen schematics for various models of the 
>>> Multi-Pak Interface floating around, but can't locate any at the 
>>> moment. I do have my original manual for my 26-3124, which includes 
>>> a schematic, but it isn't very illuminating since it is all just one 
>>> big ASIC.  So what I'm really looking for is the 26-3024 PAL-based 
>>> model.  (Were there other models of the MPI?)
>>>
>>> Anybody know off hand where such a schematic is available?
>>>
>>> JCE
>>>
>>>
>>> -- 
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco 
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



From coconut at pritchard.ca  Mon Mar  2 23:18:44 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Mon, 2 Mar 2009 22:18:44 -0600
Subject: [Coco] MPI Schematics in PDF?
In-Reply-To: <49ACA789.7050306@worldnet.att.net>
References: <49AC9EC5.100@swbell.net> <49ACA121.9020602@swbell.net>
	<49ACA789.7050306@worldnet.att.net>
Message-ID: <AEBF03E8-9357-4F33-A417-83790F6F60D0@pritchard.ca>

That manual unfortunately does not have schematics.

Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies



On 2-Mar-09, at 9:44 PM, Robert Gault wrote:

> Joel Ewy wrote:
>> Addendum:  I notice that there is one in Frank Swygert's book  
>> "Tandy's Little Wonder".  However the scan is really illegible to  
>> the point that I can't even figure out what chip is what.
>> JCE
>> Joel Ewy wrote:
>>> I was fairly certain I'd seen schematics for various models of the  
>>> Multi-Pak Interface floating around, but can't locate any at the  
>>> moment.  I do have my original manual for my 26-3124, which  
>>> includes a schematic, but it isn't very illuminating since it is  
>>> all just one big ASIC.  So what I'm really looking for is the  
>>> 26-3024 PAL-based model.  (Were there other models of the MPI?)
>>>
>>> Anybody know off hand where such a schematic is available?
>>>
>>> JCE
>
> Try the manual here
> ftp://maltedmedia.com/coco/MANUALS1/TANDY_HW/PAK/MULTIPAK
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From carlossantiago at austin.rr.com  Tue Mar  3 00:08:10 2009
From: carlossantiago at austin.rr.com (Carlos Santiago)
Date: Mon, 2 Mar 2009 23:08:10 -0600
Subject: [Coco] patching EDTASM+ to work with disk
Message-ID: <FD45F809-9E76-4875-B2D2-12D5FDAA5D2C@austin.rr.com>

So, I attempted to patch the cartridge version of EDTASM+ to work in  
disk extended basic. I entered the assembly language program,  
assembled it and saved it to cassette. when I tried to read the file  
from cassette to move it to disk, I got I/O errors. I used a  
microcassette recorder that I have had for years. Unfortunately, I  
found that the cassette player has a problem after I wrote the files  
to tape.

1. Can I some how attach the coco cassette wires to my PC sound card  
so that I can save and load program?
2. If so, what software do I need to use?
3. I have a copy DSK image of Disk EDTASM+, but it is on the PC, how  
do I transfer it to the coco?




From brucewcalkins at charter.net  Tue Mar  3 05:44:53 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Tue, 3 Mar 2009 05:44:53 -0500
Subject: [Coco] patching EDTASM+ to work with disk
References: <FD45F809-9E76-4875-B2D2-12D5FDAA5D2C@austin.rr.com>
Message-ID: <D7D35534737945E384F518E4B657A075@speedy>

> 1. Can I some how attach the coco cassette wires to my PC sound card  so 
> that I can save and load program?
Yes.

> 2. If so, what software do I need to use?
Any sound recording program.  IIRC; Windows sound recorder has a 60 second 
length limit.  The Free Audacity program is over-kill for the task but free 
is good and it can do a lot of sound work.

> 3. I have a copy DSK image of Disk EDTASM+, but it is on the PC, how  do I 
> transfer it to the coco?
Retrieve and Dskini from Jeff V's. emulator program work for reading and 
writing .dsk files to and from a PC.   If you have a 3.5" disk drive on your 
CoCo you can use the usual 3.5" disk drive found on older PCs.  If not you 
will want a 5.25" drive on your PC and many newer PC do not support 5.25" 
drives.

There are also programs such as Cloud Nine's DriveWire and Roger Taylor's 
CoCoNet to transfer data to and from a CoCo and PC.

Bruce W. 



From deek at d2dc.net  Tue Mar  3 07:39:44 2009
From: deek at d2dc.net (Jeff Teunissen)
Date: Tue, 03 Mar 2009 07:39:44 -0500
Subject: [Coco] 3.58MHz mode for (SDL)MESS
Message-ID: <49AD2510.7010705@d2dc.net>

I've been playing around with SDLMESS 0.129 on my laptop, and got sick of
having to hold the PgDn key to speed up things like ar extractions and
compiles (and likewise sick of having the real-time clock speed up too), so I
created a "combination POKE" for the emulated SAM.

With the current code, by poking $ffd9 or $ffd7 you get "2MHz" mode (MESS
doesn't emulate the CoCo1/2's fast-mode VDG failure). I figured I could get
away with using both bits set to get a "4MHz" mode.

If you have the MESS source, the line to change is found in
src/mess/machine/coco.c, around line 1879. I changed:

    cpu_set_clockscale(device->machine->cpu[0], val ? 2 : 1);
to:
    cpu_set_clockscale(device->machine->cpu[0], ((val&3)==3)?4:(val?2:1));

For the most part, the hack works remarkably well. NitrOS-9 doesn't even look
at $ffd7, so you have to POKE &HFFD7,0 before starting it up (unless you write
a program to do the pokes later), but if you do that everything runs twice as
fast. Unlike when turning throttling off, the interrupts should continue at
the same rate, so RT clocks should stay stable. The only bad thing I've
noticed is that the joystick routine goes a bit screwy, so Multi-Vue becomes
more irritating than usual.

I also hacked Boisy's "mode" utility to switch the CPU modes on the fly, but
that's just a couple of extra clr $ffd6/7 lines.

Just thought I'd share.


From jdaggett at gate.net  Tue Mar  3 07:40:15 2009
From: jdaggett at gate.net (jdaggett at gate.net)
Date: Tue, 03 Mar 2009 07:40:15 -0500
Subject: [Coco] MPI Schematics in PDF?
In-Reply-To: <49ACA789.7050306@worldnet.att.net>
References: <49AC9EC5.100@swbell.net>, <49ACA121.9020602@swbell.net>,
	<49ACA789.7050306@worldnet.att.net>
Message-ID: <49ACDEDF.16326.642C8@jdaggett.gate.net>

On 2 Mar 2009 at 22:44, Robert Gault wrote:

> Joel Ewy wrote:
> > Addendum:  I notice that there is one in Frank Swygert's book
> > "Tandy's Little Wonder".  However the scan is really illegible to
> > the point that I can't even figure out what chip is what.
> > 
> > JCE
> > 
> > Joel Ewy wrote:
> >> I was fairly certain I'd seen schematics for various models of the
> >> Multi-Pak Interface floating around, but can't locate any at the
> >> moment.  I do have my original manual for my 26-3124, which
> >> includes a schematic, but it isn't very illuminating since it is
> >> all just one big ASIC.  So what I'm really looking for is the
> >> 26-3024 PAL-based model.  (Were there other models of the MPI?)
> >>
> >> Anybody know off hand where such a schematic is available?
> >>
> >> JCE
> 
> Try the manual here
> ftp://maltedmedia.com/coco/MANUALS1/TANDY_HW/PAK/MULTIPAK
> 
The schematics will be found in the service manual and not the user 
manual.

Besides I have redrawn the 3024 schematic in Eagle and can reproduce a 
PDF of it. 

james



From robert.gault at worldnet.att.net  Tue Mar  3 08:55:52 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Tue, 03 Mar 2009 08:55:52 -0500
Subject: [Coco] patching EDTASM+ to work with disk
In-Reply-To: <FD45F809-9E76-4875-B2D2-12D5FDAA5D2C@austin.rr.com>
References: <FD45F809-9E76-4875-B2D2-12D5FDAA5D2C@austin.rr.com>
Message-ID: <49AD36E8.9040108@worldnet.att.net>

Carlos Santiago wrote:
> So, I attempted to patch the cartridge version of EDTASM+ to work in 
> disk extended basic. I entered the assembly language program, assembled 
> it and saved it to cassette. when I tried to read the file from cassette 
> to move it to disk, I got I/O errors. I used a microcassette recorder 
> that I have had for years. Unfortunately, I found that the cassette 
> player has a problem after I wrote the files to tape.
> 
> 1. Can I some how attach the coco cassette wires to my PC sound card so 
> that I can save and load program?
> 2. If so, what software do I need to use?
> 3. I have a copy DSK image of Disk EDTASM+, but it is on the PC, how do 
> I transfer it to the coco?
> 
> 

You have a number of options. Don't reinvent the wheel. If you have 
access to "The Rainbow", Sept. 1983, there is an article by Roger 
Schrag, "Superpatch for EDTASM". It shows how to save and patch the 
EDTASM ROM pak converting it to a disk program.

There are many ways to transfer a .dsk image on a PC to a real floppy. 
What you use depends on whether your PC OS is based on DOS or is WinNT 
or later.
For DOS based systems, any emulator that reads real disks can create 
floppies. The utilities that come with the JVC emulator can also be used.
For WinNT XP or Vista systems, programs like Omniflop and Cocodisk can 
be used to create floppies.
If you have a terminal program on your Coco (Ultimaterm for Basic or an 
OS-9 package) you can transfer files to the Coco over a null-modem cable 
using Hyperterminal or a similar PC program.


From cwgordon at carolina.rr.com  Tue Mar  3 09:19:48 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Tue, 3 Mar 2009 09:19:48 -0500
Subject: [Coco] CCR-81 & CCR-82 manuals
Message-ID: <004b01c99c0b$1c627e40$55277ac0$@rr.com>

Does anyone have these manuals they can PDF for me? Specifically the CCR-82.
I need to see if I can find the specs for a PS

Thanks

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From robert.gault at worldnet.att.net  Tue Mar  3 09:33:38 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Tue, 03 Mar 2009 09:33:38 -0500
Subject: [Coco] CCR-81 & CCR-82 manuals
In-Reply-To: <004b01c99c0b$1c627e40$55277ac0$@rr.com>
References: <004b01c99c0b$1c627e40$55277ac0$@rr.com>
Message-ID: <49AD3FC2.2010902@worldnet.att.net>

Bill wrote:
> Does anyone have these manuals they can PDF for me? Specifically the CCR-82.
> I need to see if I can find the specs for a PS
> 
> Thanks
> 

Specs for the CCR-81 are:
Tape system              2-track monaural
Tape speed               4.75 cm/sec
Wow and Flutter          0.15%
  (WRMS)
Signal-to-Noise Ratio    49/40 dB
  (DC/AC)
Semiconductors           1 IC, 5 transistors, 7 diodes
Erase System              DC Erasing
AGC delaytime at REC     0.4 sec
Turn on time at REC      0.4 sec
Record System            AC Bias
Power                    DC 4 "C" cells
                          AC 120V 60Hz  depends on the country of
                                        purchased.
                             230V 50Hz
                             240V 50Hz

Size and weight are given but I doubt you care about them.


From cwgordon at carolina.rr.com  Tue Mar  3 09:45:33 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Tue, 3 Mar 2009 09:45:33 -0500
Subject: [Coco] CCR-81 & CCR-82 manuals
In-Reply-To: <49AD3FC2.2010902@worldnet.att.net>
References: <004b01c99c0b$1c627e40$55277ac0$@rr.com>
	<49AD3FC2.2010902@worldnet.att.net>
Message-ID: <005001c99c0e$b59a3ff0$20cebfd0$@rr.com>

Basically, I need to know about the input amperage and the tip polarity of
the AC power supply on the CCR-82. I need to find one.

Thanks

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Tuesday, March 03, 2009 9:34 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] CCR-81 & CCR-82 manuals
> 
> Power                    DC 4 "C" cells
>                           AC 120V 60Hz  depends on the country of
purchased.
>                              230V 50Hz
>                              240V 50Hz
> 



From vchester at setec-cr.com  Tue Mar  3 10:22:18 2009
From: vchester at setec-cr.com (Chester A Patterson)
Date: Tue, 3 Mar 2009 09:22:18 -0600
Subject: [Coco] patching EDTASM+ to work with disk
In-Reply-To: <49AD36E8.9040108@worldnet.att.net>
Message-ID: <0A9B63EA8B906947A409C6F0295CA07E013DD5FE@setec-server.SETEC.COM>

I have Disk EDTASM+ in one of the CF Card RS-DOS disks in a Cloud9 IDE
in a MPI in my CC3. CF card 256MB partitioned 127MB for OS9, remainder
for 256 RS-DOS "floppies". I don't have the cartridge EDTASM+ (yet) much
less the patches for disk op.

What advantages/disadvantages does the cartridge version of EDTASM+
offer over the disk verion?
My guess is the principal one is being able to use HDB-DOS as opposed to
the funky EDTASM+ DOS.

Please advise.

Thanks.

/Chester
Costa Rica


From coconut at pritchard.ca  Tue Mar  3 10:36:31 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Tue, 3 Mar 2009 09:36:31 -0600
Subject: [Coco] CCR-81 & CCR-82 manuals
In-Reply-To: <005001c99c0e$b59a3ff0$20cebfd0$@rr.com>
References: <004b01c99c0b$1c627e40$55277ac0$@rr.com>
	<49AD3FC2.2010902@worldnet.att.net>
	<005001c99c0e$b59a3ff0$20cebfd0$@rr.com>
Message-ID: <1806abd60903030736p2f441bf9lcd764af88731e6f7@mail.gmail.com>

Google is your friend searching ccr-82 gave me this link as the 5th link on
my results.

http://www.classiccmp.org/dunfield/r/ccr82.pdf

On Tue, Mar 3, 2009 at 8:45 AM, Bill <cwgordon at carolina.rr.com> wrote:

> Basically, I need to know about the input amperage and the tip polarity of
> the AC power supply on the CCR-82. I need to find one.
>
> Thanks
>
> > -----Original Message-----
> > From: coco-bounces at maltedmedia.com [mailto:coco-
> > bounces at maltedmedia.com] On Behalf Of Robert Gault
> > Sent: Tuesday, March 03, 2009 9:34 AM
> > To: CoCoList for Color Computer Enthusiasts
> > Subject: Re: [Coco] CCR-81 & CCR-82 manuals
> >
> > Power                    DC 4 "C" cells
> >                           AC 120V 60Hz  depends on the country of
> purchased.
> >                              230V 50Hz
> >                              240V 50Hz
> >
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From coconut at pritchard.ca  Tue Mar  3 10:44:26 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Tue, 3 Mar 2009 09:44:26 -0600
Subject: [Coco] CCR-81 & CCR-82 manuals
In-Reply-To: <005001c99c0e$b59a3ff0$20cebfd0$@rr.com>
References: <004b01c99c0b$1c627e40$55277ac0$@rr.com>
	<49AD3FC2.2010902@worldnet.att.net>
	<005001c99c0e$b59a3ff0$20cebfd0$@rr.com>
Message-ID: <1806abd60903030744s6b0c5e0bw91ce24ab93645369@mail.gmail.com>

Also found this one when searching CCR-81

http://video.aol.com/video-detail/1983-tandy-ccr-81-cassette-recorder/183160563

On Tue, Mar 3, 2009 at 8:45 AM, Bill <cwgordon at carolina.rr.com> wrote:

> Basically, I need to know about the input amperage and the tip polarity of
> the AC power supply on the CCR-82. I need to find one.
>
> Thanks
>
> > -----Original Message-----
> > From: coco-bounces at maltedmedia.com [mailto:coco-
> > bounces at maltedmedia.com] On Behalf Of Robert Gault
> > Sent: Tuesday, March 03, 2009 9:34 AM
> > To: CoCoList for Color Computer Enthusiasts
> > Subject: Re: [Coco] CCR-81 & CCR-82 manuals
> >
> > Power                    DC 4 "C" cells
> >                           AC 120V 60Hz  depends on the country of
> purchased.
> >                              230V 50Hz
> >                              240V 50Hz
> >
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From coconut at pritchard.ca  Tue Mar  3 10:54:24 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Tue, 3 Mar 2009 09:54:24 -0600
Subject: [Coco] CCR-81 & CCR-82 manuals
In-Reply-To: <1806abd60903030744s6b0c5e0bw91ce24ab93645369@mail.gmail.com>
References: <004b01c99c0b$1c627e40$55277ac0$@rr.com>
	<49AD3FC2.2010902@worldnet.att.net>
	<005001c99c0e$b59a3ff0$20cebfd0$@rr.com>
	<1806abd60903030744s6b0c5e0bw91ce24ab93645369@mail.gmail.com>
Message-ID: <1806abd60903030754x6bfae6dai98a732126949e300@mail.gmail.com>

Refined search of CCR-81 manual PDF resulted in a PDF version of the one
shown in the video.

http://www.classiccmp.org/cini/pdf/Tandy/CCR81%20Owners%20Manual.pdf

On Tue, Mar 3, 2009 at 9:44 AM, Ryan Pritchard <coconut at pritchard.ca> wrote:

> Also found this one when searching CCR-81
>
>
> http://video.aol.com/video-detail/1983-tandy-ccr-81-cassette-recorder/183160563
>
> On Tue, Mar 3, 2009 at 8:45 AM, Bill <cwgordon at carolina.rr.com> wrote:
>
>> Basically, I need to know about the input amperage and the tip polarity of
>> the AC power supply on the CCR-82. I need to find one.
>>
>> Thanks
>>
>> > -----Original Message-----
>> > From: coco-bounces at maltedmedia.com [mailto:coco-
>> > bounces at maltedmedia.com] On Behalf Of Robert Gault
>> > Sent: Tuesday, March 03, 2009 9:34 AM
>> > To: CoCoList for Color Computer Enthusiasts
>> > Subject: Re: [Coco] CCR-81 & CCR-82 manuals
>> >
>> > Power                    DC 4 "C" cells
>> >                           AC 120V 60Hz  depends on the country of
>> purchased.
>> >                              230V 50Hz
>> >                              240V 50Hz
>> >
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
>
> --
> Regards,
>
> Ryan Pritchard
> Fun Extends All Basic Life Expectancies
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From brucewcalkins at charter.net  Tue Mar  3 11:57:18 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Tue, 3 Mar 2009 11:57:18 -0500
Subject: [Coco] patching EDTASM+ to work with disk
References: <FD45F809-9E76-4875-B2D2-12D5FDAA5D2C@austin.rr.com>
	<49AD36E8.9040108@worldnet.att.net>
Message-ID: <E6C6B75FB685401592D73B58A2CA510B@speedy>

> You have a number of options. Don't reinvent the wheel.
Speaking of which, there is a disk based version of EDTASM which is built to 
work from disk.  There should be a dot-DSK copy on-line somewhere.

Bruce W. 



From cwgordon at carolina.rr.com  Tue Mar  3 12:05:16 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Tue, 3 Mar 2009 12:05:16 -0500
Subject: [Coco] CCR-81 & CCR-82 manuals
In-Reply-To: <1806abd60903030754x6bfae6dai98a732126949e300@mail.gmail.com>
References: <004b01c99c0b$1c627e40$55277ac0$@rr.com>	<49AD3FC2.2010902@worldnet.att.net>	<005001c99c0e$b59a3ff0$20cebfd0$@rr.com>	<1806abd60903030744s6b0c5e0bw91ce24ab93645369@mail.gmail.com>
	<1806abd60903030754x6bfae6dai98a732126949e300@mail.gmail.com>
Message-ID: <005401c99c22$39bd05c0$ad371140$@rr.com>

Thanks, that's a great help.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Ryan Pritchard
> Sent: Tuesday, March 03, 2009 10:54 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] CCR-81 & CCR-82 manuals
> 
> Refined search of CCR-81 manual PDF resulted in a PDF version of the
> one
> shown in the video.
> 
> http://www.classiccmp.org/cini/pdf/Tandy/CCR81%20Owners%20Manual.pdf
> 
> On Tue, Mar 3, 2009 at 9:44 AM, Ryan Pritchard <coconut at pritchard.ca>
> wrote:
> 
> > Also found this one when searching CCR-81
> >
> >
> > http://video.aol.com/video-detail/1983-tandy-ccr-81-cassette-
> recorder/183160563
> >
> > On Tue, Mar 3, 2009 at 8:45 AM, Bill <cwgordon at carolina.rr.com>
> wrote:
> >
> >> Basically, I need to know about the input amperage and the tip
> polarity of
> >> the AC power supply on the CCR-82. I need to find one.
> >>
> >> Thanks
> >>
> >> > -----Original Message-----
> >> > From: coco-bounces at maltedmedia.com [mailto:coco-
> >> > bounces at maltedmedia.com] On Behalf Of Robert Gault
> >> > Sent: Tuesday, March 03, 2009 9:34 AM
> >> > To: CoCoList for Color Computer Enthusiasts
> >> > Subject: Re: [Coco] CCR-81 & CCR-82 manuals
> >> >
> >> > Power                    DC 4 "C" cells
> >> >                           AC 120V 60Hz  depends on the country of
> >> purchased.
> >> >                              230V 50Hz
> >> >                              240V 50Hz
> >> >
> >>
> >>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> http://five.pairlist.net/mailman/listinfo/coco
> >>
> >
> >
> >
> > --
> > Regards,
> >
> > Ryan Pritchard
> > Fun Extends All Basic Life Expectancies
> >
> 
> 
> 
> --
> Regards,
> 
> Ryan Pritchard
> Fun Extends All Basic Life Expectancies
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From coconut at pritchard.ca  Tue Mar  3 12:28:54 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Tue, 3 Mar 2009 11:28:54 -0600
Subject: [Coco] CCR-81 & CCR-82 manuals
In-Reply-To: <005401c99c22$39bd05c0$ad371140$@rr.com>
References: <004b01c99c0b$1c627e40$55277ac0$@rr.com>
	<49AD3FC2.2010902@worldnet.att.net>
	<005001c99c0e$b59a3ff0$20cebfd0$@rr.com>
	<1806abd60903030744s6b0c5e0bw91ce24ab93645369@mail.gmail.com>
	<1806abd60903030754x6bfae6dai98a732126949e300@mail.gmail.com>
	<005401c99c22$39bd05c0$ad371140$@rr.com>
Message-ID: <1806abd60903030928n1cb0a672ka31a10810a6d472b@mail.gmail.com>

One last thought, now, is that after reading both manuals, it appears that
either tape system is capable of connecting directly to mains power
(120/240) systems with quite possibly the most easy to find power cables
ever.  Most VCRs in Canada and the US had the same cable through most of the
80's and 90's and even today various stereo components still use these
simple two prong cables.  The tape systems have built in transformers and
would not require an external power supply if you have the simple power
cable.

On Tue, Mar 3, 2009 at 11:05 AM, Bill <cwgordon at carolina.rr.com> wrote:

> Thanks, that's a great help.
>
> > -----Original Message-----
> > From: coco-bounces at maltedmedia.com [mailto:coco-
> > bounces at maltedmedia.com] On Behalf Of Ryan Pritchard
> > Sent: Tuesday, March 03, 2009 10:54 AM
> > To: CoCoList for Color Computer Enthusiasts
> > Subject: Re: [Coco] CCR-81 & CCR-82 manuals
> >
> > Refined search of CCR-81 manual PDF resulted in a PDF version of the
> > one
> > shown in the video.
> >
> > http://www.classiccmp.org/cini/pdf/Tandy/CCR81%20Owners%20Manual.pdf
> >
> > On Tue, Mar 3, 2009 at 9:44 AM, Ryan Pritchard <coconut at pritchard.ca>
> > wrote:
> >
> > > Also found this one when searching CCR-81
> > >
> > >
> > > http://video.aol.com/video-detail/1983-tandy-ccr-81-cassette-
> > recorder/183160563
> > >
> > > On Tue, Mar 3, 2009 at 8:45 AM, Bill <cwgordon at carolina.rr.com>
> > wrote:
> > >
> > >> Basically, I need to know about the input amperage and the tip
> > polarity of
> > >> the AC power supply on the CCR-82. I need to find one.
> > >>
> > >> Thanks
> > >>
> > >> > -----Original Message-----
> > >> > From: coco-bounces at maltedmedia.com [mailto:coco-
> > >> > bounces at maltedmedia.com] On Behalf Of Robert Gault
> > >> > Sent: Tuesday, March 03, 2009 9:34 AM
> > >> > To: CoCoList for Color Computer Enthusiasts
> > >> > Subject: Re: [Coco] CCR-81 & CCR-82 manuals
> > >> >
> > >> > Power                    DC 4 "C" cells
> > >> >                           AC 120V 60Hz  depends on the country of
> > >> purchased.
> > >> >                              230V 50Hz
> > >> >                              240V 50Hz
> > >> >
> > >>
> > >>
> > >> --
> > >> Coco mailing list
> > >> Coco at maltedmedia.com
> > >> http://five.pairlist.net/mailman/listinfo/coco
> > >>
> > >
> > >
> > >
> > > --
> > > Regards,
> > >
> > > Ryan Pritchard
> > > Fun Extends All Basic Life Expectancies
> > >
> >
> >
> >
> > --
> > Regards,
> >
> > Ryan Pritchard
> > Fun Extends All Basic Life Expectancies
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From cwgordon at carolina.rr.com  Tue Mar  3 13:24:07 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Tue, 3 Mar 2009 13:24:07 -0500
Subject: [Coco] CCR-81 & CCR-82 manuals
In-Reply-To: <1806abd60903030928n1cb0a672ka31a10810a6d472b@mail.gmail.com>
References: <004b01c99c0b$1c627e40$55277ac0$@rr.com>	<49AD3FC2.2010902@worldnet.att.net>	<005001c99c0e$b59a3ff0$20cebfd0$@rr.com>	<1806abd60903030744s6b0c5e0bw91ce24ab93645369@mail.gmail.com>	<1806abd60903030754x6bfae6dai98a732126949e300@mail.gmail.com>	<005401c99c22$39bd05c0$ad371140$@rr.com>
	<1806abd60903030928n1cb0a672ka31a10810a6d472b@mail.gmail.com>
Message-ID: <005901c99c2d$3dba2300$b92e6900$@rr.com>

Nope, the ccr-82 will only work with an ac to dc converter. The cc-81 works
with either ac to dc converter or straight ac.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Ryan Pritchard
> Sent: Tuesday, March 03, 2009 12:29 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] CCR-81 & CCR-82 manuals
> 
> One last thought, now, is that after reading both manuals, it appears
> that either tape system is capable of connecting directly to mains power
> (120/240) systems with quite possibly the most easy to find power
> cables ever.  Most VCRs in Canada and the US had the same cable through
most
> of the 80's and 90's and even today various stereo components still use
these
> simple two prong cables.  The tape systems have built in transformers
> and would not require an external power supply if you have the simple
power
> cable.



From coder32768 at gmail.com  Tue Mar  3 15:24:28 2009
From: coder32768 at gmail.com (Rick Taylor)
Date: Tue, 3 Mar 2009 12:24:28 -0800
Subject: [Coco] Hello list, and looking for B&B XT-ROM image
Message-ID: <fc509d260903031224w19ffe37x33769da8dc23b9d5@mail.gmail.com>

Hi all,
I just joined the list a few days ago. I am Rick Taylor - I used to be on
Delphi ages ago with some now-embarrassing name such as "c_demigod" or
something close (I was a kid, don't hate me :) )

Anyway I still occasionally play with the CoCo, and I recently set it back
up and decided that I was going to refurbish this thing in earnest, get a
new case for it, etc.

The setup is using the Burke & Burke CocoXT system, with a WD1002-27X
controller and an RLL drive. I also have the XT-ROM, but it has never worked
for me. I'm deciding I will assume it had been fried at some point, and am
going to get Boisy at Cloud9 (or someone else with an EPROM burner) to burn
me off an EPROM so I can try again.

I understand that the EPROM images have been released as either shareware or
as public domain, but I've had no real luck locating them. Boisy said to try
Glenside CoCo club, but I'm not sure who to contact there.

Any pointers?

Thanks!

-- Rick

-- 
All of this machinery making modern music can still be open hearted -
not so coldly charted; it's really just a question of your honesty.

- Neil Peart, Rush, _The Spirit of Radio_


From devries.bob at gmail.com  Tue Mar  3 15:40:44 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Wed, 4 Mar 2009 06:40:44 +1000
Subject: [Coco] Hello list, and looking for B&B XT-ROM image
References: <fc509d260903031224w19ffe37x33769da8dc23b9d5@mail.gmail.com>
Message-ID: <007c01c99c44$7caa1400$0701a8c0@master>

Rick, I've emailed the image file to you in private.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Rick Taylor" <coder32768 at gmail.com>
To: <coco at maltedmedia.com>
Sent: Wednesday, March 04, 2009 6:24 AM
Subject: [Coco] Hello list, and looking for B&B XT-ROM image


> Hi all,
> I just joined the list a few days ago. I am Rick Taylor - I used to be on
> Delphi ages ago with some now-embarrassing name such as "c_demigod" or
> something close (I was a kid, don't hate me :) )
>
> Anyway I still occasionally play with the CoCo, and I recently set it back
> up and decided that I was going to refurbish this thing in earnest, get a
> new case for it, etc.
>
> The setup is using the Burke & Burke CocoXT system, with a WD1002-27X
> controller and an RLL drive. I also have the XT-ROM, but it has never 
> worked
> for me. I'm deciding I will assume it had been fried at some point, and am
> going to get Boisy at Cloud9 (or someone else with an EPROM burner) to 
> burn
> me off an EPROM so I can try again.
>
> I understand that the EPROM images have been released as either shareware 
> or
> as public domain, but I've had no real luck locating them. Boisy said to 
> try
> Glenside CoCo club, but I'm not sure who to contact there.
>
> Any pointers?
>
> Thanks!
>
> -- Rick
>
> -- 
> All of this machinery making modern music can still be open hearted -
> not so coldly charted; it's really just a question of your honesty.
>
> - Neil Peart, Rush, _The Spirit of Radio_
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From goosey at virgo.sdc.org  Tue Mar  3 16:16:08 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Tue, 3 Mar 2009 14:16:08 -0700
Subject: [Coco] Hello list, and looking for B&B XT-ROM image
In-Reply-To: <fc509d260903031224w19ffe37x33769da8dc23b9d5@mail.gmail.com>
References: <fc509d260903031224w19ffe37x33769da8dc23b9d5@mail.gmail.com>
Message-ID: <20090303211607.GA31161@virgo.sdc.org>

On Tue, Mar 03, 2009 at 12:24:28PM -0800, Rick Taylor wrote:
> I understand that the EPROM images have been released as either shareware or
> as public domain, but I've had no real luck locating them. Boisy said to try
> Glenside CoCo club, but I'm not sure who to contact there.

I uploaded a bunch of the old Burke & Burke software to maltedmedia
and rtsi... but I'm not sure an image of the actual boot-ROM was
included.  <shrug> I don't have the hardware, I just uploaded the
software someone else had sent me.

Good luck,
Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From msmcdoug at iinet.net.au  Tue Mar  3 16:17:09 2009
From: msmcdoug at iinet.net.au (Mark McDougall)
Date: Wed, 04 Mar 2009 08:17:09 +1100
Subject: [Coco] RS232 paks
Message-ID: <49AD9E55.6000804@iinet.net.au>

Hi Guys,

Was wondering if you could answer a few quick 232-related questions:

1. Which ACIA/UART chips are used in the various coco RS232 paks? Which 
one(s) is/are the most common? Which (if any) is considered "superior"?

2. Are any of the handshaking lines (RTS/CTS etc) used? If so, which?

3. What sort of connector(s) is/are used on the more common 232 carts?

Also, pointers to the various manuals/schematics would be greatly appreciated!

Thanks in advance!
Regards,

-- 
|              Mark McDougall                | "Electrical Engineers do it
|  <http://members.iinet.net.au/~msmcdoug>   |   with less resistance!"


From mechacoco at gmail.com  Tue Mar  3 16:40:59 2009
From: mechacoco at gmail.com (Darren A)
Date: Tue, 3 Mar 2009 14:40:59 -0700
Subject: [Coco] RS232 paks
In-Reply-To: <49AD9E55.6000804@iinet.net.au>
References: <49AD9E55.6000804@iinet.net.au>
Message-ID: <5d802cd0903031340k45573f1bob557d639026d1d55@mail.gmail.com>

On 3/3/09, Mark McDougall wrote:
> Hi Guys,
>
> Was wondering if you could answer a few quick 232-related questions:
>
> 1. Which ACIA/UART chips are used in the various coco RS232 paks? Which
> one(s) is/are the most common? Which (if any) is considered "superior"?

The 6551 ACIA is used in every RS-232 pak that I have seen (Tandy
Deluxe, Direct Connect Modem, CoCo PRO!, Roger Taylor's wireless pak
and I think the TelePak).

> 2. Are any of the handshaking lines (RTS/CTS etc) used? If so, which?

The 6551 has RTS, CTS, DSR, DTR and DCD.  It doesn't implement them
very well IMO.  Some of these must be asserted in order for the ACIA
to be enabled for both transmit and receive.  If CTS goes HI while
transmitting, it will stop in the middle of a byte.  I'm not sure if
all of these are present on the connector.

Sock Master has some info on his site on how to improve the hardware
handshaking:
<http://www.axess.com/twilight/sock/cocofile/rs232mod.txt>

> 3. What sort of connector(s) is/are used on the more common 232 carts?

Mostly DB25.  The telepak may use a DB9.  The wireless pak has no connector.

> Also, pointers to the various manuals/schematics would be greatly
> appreciated!

This pdf has the Tandy Deluxe, DC Modem Pak and CoCoPRO! :
<ftp://maltedmedia.com/coco/MANUALS0/MISC/HARDWARE/CoCoPro_RS232.pdf>

Darren


From msmcdoug at iinet.net.au  Tue Mar  3 16:53:06 2009
From: msmcdoug at iinet.net.au (Mark McDougall)
Date: Wed, 04 Mar 2009 08:53:06 +1100
Subject: [Coco] RS232 paks
In-Reply-To: <5d802cd0903031340k45573f1bob557d639026d1d55@mail.gmail.com>
References: <49AD9E55.6000804@iinet.net.au>
	<5d802cd0903031340k45573f1bob557d639026d1d55@mail.gmail.com>
Message-ID: <49ADA6C2.6000006@iinet.net.au>

Darren A wrote:

> The 6551 ACIA is used in every RS-232 pak that I have seen (Tandy
> Deluxe, Direct Connect Modem, CoCo PRO!, Roger Taylor's wireless pak
> and I think the TelePak).
	(snip)

Awesome, that's _exactly_ what I was after, in one succinct, detailed email 
- very much appreciated - thanks!!!

I also believe that at least one person has "gone 16550" to use his words??? 
Is that the case? Are there many here that are using 16550, and what 
software supports it?

Regards,

-- 
|              Mark McDougall                | "Electrical Engineers do it
|  <http://members.iinet.net.au/~msmcdoug>   |   with less resistance!"


From cwgordon at carolina.rr.com  Tue Mar  3 17:09:07 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Tue, 3 Mar 2009 17:09:07 -0500
Subject: [Coco] RS232 Pak and MPI
Message-ID: <009101c99c4c$ae922270$0bb66750$@rr.com>

I know this is probably asking a bit much, but does anyone have an RS232 Pak
and/or a MPI they would be willing to part with? Please email me privately.

Thanks.

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From robert.gault at worldnet.att.net  Tue Mar  3 17:17:29 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Tue, 03 Mar 2009 17:17:29 -0500
Subject: [Coco] patching EDTASM+ to work with disk
In-Reply-To: <0A9B63EA8B906947A409C6F0295CA07E013DD5FE@setec-server.SETEC.COM>
References: <0A9B63EA8B906947A409C6F0295CA07E013DD5FE@setec-server.SETEC.COM>
Message-ID: <49ADAC79.3030507@worldnet.att.net>

Chester A Patterson wrote:
> I have Disk EDTASM+ in one of the CF Card RS-DOS disks in a Cloud9 IDE
> in a MPI in my CC3. CF card 256MB partitioned 127MB for OS9, remainder
> for 256 RS-DOS "floppies". I don't have the cartridge EDTASM+ (yet) much
> less the patches for disk op.
> 
> What advantages/disadvantages does the cartridge version of EDTASM+
> offer over the disk verion?
> My guess is the principal one is being able to use HDB-DOS as opposed to
> the funky EDTASM+ DOS.
> 
> Please advise.
> 
> Thanks.
> 
> /Chester

The ROM pak is a cassette based system; disadvantage. The ROM code 
exists above $C000 so binary programs can be loaded "anywhere" in RAM; 
advantage. The disk system occupies most of RAM leaving room from about 
$6000-$7FFF for code. This is a disadvantage if you are trying to debug 
large programs.

HDBOS does not replace the DOS that comes with Disk EDTASM+. That DOS is 
still required. If you want a version of Disk EDTASM+ that is compatible 
with hard drive systems, you will probably have to buy it from me.
http://home.att.net/~robert.gault/Coco/Sales/Flyer.htm



From benbleau at gmail.com  Tue Mar  3 17:24:03 2009
From: benbleau at gmail.com (Benoit Bleau)
Date: Tue, 03 Mar 2009 17:24:03 -0500
Subject: [Coco] RS232 paks
In-Reply-To: <49ADA6C2.6000006@iinet.net.au>
References: <49AD9E55.6000804@iinet.net.au>	<5d802cd0903031340k45573f1bob557d639026d1d55@mail.gmail.com>
	<49ADA6C2.6000006@iinet.net.au>
Message-ID: <49ADAE03.5090200@gmail.com>


>
> I also believe that at least one person has "gone 16550" to use his 
> words??? Is that the case? Are there many here that are using 16550, 
> and what software supports it?
>
> Regards,
>

Chuck Youse was working on a dual 16550 board, until he dropped from the 
coco scene :(

-Benoit


From coconut at pritchard.ca  Tue Mar  3 17:32:10 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Tue, 3 Mar 2009 16:32:10 -0600
Subject: [Coco] Multi-Pak Interface question.
Message-ID: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>

If one were to acquire a 26-3024 MPI that had the PAL upgrade to run with
the CoCo3, would it still work on a CoCo 1 or CoCo 2?

-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From jps.subscriptions at gmail.com  Tue Mar  3 17:37:13 2009
From: jps.subscriptions at gmail.com (J.P. Samson)
Date: Tue, 3 Mar 2009 15:37:13 -0700
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
Message-ID: <6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>

On Mar 3, 2009, at 3:32 PM, Ryan Pritchard wrote:
> If one were to acquire a 26-3024 MPI that had the PAL upgrade to run  
> with
> the CoCo3, would it still work on a CoCo 1 or CoCo 2?

Yes.

The caveat being there was one known pak that would be broken with the  
PAL upgrade, but I can't remember which.  It wasn't a common pak, to  
be sure.

-- JP



From coder32768 at gmail.com  Tue Mar  3 17:38:03 2009
From: coder32768 at gmail.com (Rick Taylor)
Date: Tue, 3 Mar 2009 14:38:03 -0800
Subject: [Coco] Hello list, and looking for B&B XT-ROM image
In-Reply-To: <007c01c99c44$7caa1400$0701a8c0@master>
References: <fc509d260903031224w19ffe37x33769da8dc23b9d5@mail.gmail.com>
	<007c01c99c44$7caa1400$0701a8c0@master>
Message-ID: <fc509d260903031438h517e92dqda32194b68cfb1b3@mail.gmail.com>

Bob --
Thanks, I appreciate it!

-- Rick

On Tue, Mar 3, 2009 at 12:40 PM, Bob Devries <devries.bob at gmail.com> wrote:

> Rick, I've emailed the image file to you in private.
>
> --
> Regards, Bob Devries, Dalby, Queensland, Australia
>
> Isaiah 50:4 The sovereign Lord has given me
> the capacity to be his spokesman,
> so that I know how to help the weary.
>
> website: http://www.home.gil.com.au/~bdevasl
> my blog: http://bdevries.invigorated.org/
>
> ----- Original Message ----- From: "Rick Taylor" <coder32768 at gmail.com>
> To: <coco at maltedmedia.com>
> Sent: Wednesday, March 04, 2009 6:24 AM
> Subject: [Coco] Hello list, and looking for B&B XT-ROM image
>
>
>  Hi all,
>> I just joined the list a few days ago. I am Rick Taylor - I used to be on
>> Delphi ages ago with some now-embarrassing name such as "c_demigod" or
>> something close (I was a kid, don't hate me :) )
>>
>> Anyway I still occasionally play with the CoCo, and I recently set it back
>> up and decided that I was going to refurbish this thing in earnest, get a
>> new case for it, etc.
>>
>> The setup is using the Burke & Burke CocoXT system, with a WD1002-27X
>> controller and an RLL drive. I also have the XT-ROM, but it has never
>> worked
>> for me. I'm deciding I will assume it had been fried at some point, and am
>> going to get Boisy at Cloud9 (or someone else with an EPROM burner) to
>> burn
>> me off an EPROM so I can try again.
>>
>> I understand that the EPROM images have been released as either shareware
>> or
>> as public domain, but I've had no real luck locating them. Boisy said to
>> try
>> Glenside CoCo club, but I'm not sure who to contact there.
>>
>> Any pointers?
>>
>> Thanks!
>>
>> -- Rick
>>
>> --
>> All of this machinery making modern music can still be open hearted -
>> not so coldly charted; it's really just a question of your honesty.
>>
>> - Neil Peart, Rush, _The Spirit of Radio_
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
All of this machinery making modern music can still be open hearted -
not so coldly charted; it's really just a question of your honesty.

- Neil Peart, Rush, _The Spirit of Radio_


From devries.bob at gmail.com  Tue Mar  3 18:19:53 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Wed, 4 Mar 2009 09:19:53 +1000
Subject: [Coco] Multi-Pak Interface question.
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>
Message-ID: <00a501c99c56$916e3850$0701a8c0@master>

The PAK which failed with the MPI upgrade was the one which came with the 
first version of CocoMax. Its address was at $FF90 IIRC, which is the same 
as the Coco3's GIME chip registers.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "J.P. Samson" <jps.subscriptions at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 04, 2009 8:37 AM
Subject: Re: [Coco] Multi-Pak Interface question.


> On Mar 3, 2009, at 3:32 PM, Ryan Pritchard wrote:
>> If one were to acquire a 26-3024 MPI that had the PAL upgrade to run 
>> with
>> the CoCo3, would it still work on a CoCo 1 or CoCo 2?
>
> Yes.
>
> The caveat being there was one known pak that would be broken with the 
> PAL upgrade, but I can't remember which.  It wasn't a common pak, to  be 
> sure.
>
> -- JP
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From coder32768 at gmail.com  Tue Mar  3 19:28:00 2009
From: coder32768 at gmail.com (Rick Taylor)
Date: Tue, 3 Mar 2009 16:28:00 -0800
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <00a501c99c56$916e3850$0701a8c0@master>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>
	<00a501c99c56$916e3850$0701a8c0@master>
Message-ID: <fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>

Has anyone ever made Multi-Pak clones? Would it be legal to do so?

On Tue, Mar 3, 2009 at 3:19 PM, Bob Devries <devries.bob at gmail.com> wrote:

> The PAK which failed with the MPI upgrade was the one which came with the
> first version of CocoMax. Its address was at $FF90 IIRC, which is the same
> as the Coco3's GIME chip registers.
>
> --
> Regards, Bob Devries, Dalby, Queensland, Australia
>
> Isaiah 50:4 The sovereign Lord has given me
> the capacity to be his spokesman,
> so that I know how to help the weary.
>
> website: http://www.home.gil.com.au/~bdevasl
> my blog: http://bdevries.invigorated.org/
>
> ----- Original Message ----- From: "J.P. Samson" <
> jps.subscriptions at gmail.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Wednesday, March 04, 2009 8:37 AM
> Subject: Re: [Coco] Multi-Pak Interface question.
>
>
>
>  On Mar 3, 2009, at 3:32 PM, Ryan Pritchard wrote:
>>
>>> If one were to acquire a 26-3024 MPI that had the PAL upgrade to run with
>>> the CoCo3, would it still work on a CoCo 1 or CoCo 2?
>>>
>>
>> Yes.
>>
>> The caveat being there was one known pak that would be broken with the PAL
>> upgrade, but I can't remember which.  It wasn't a common pak, to  be sure.
>>
>> -- JP
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
All of this machinery making modern music can still be open hearted -
not so coldly charted; it's really just a question of your honesty.

- Neil Peart, Rush, _The Spirit of Radio_


From afra at aurigae.demon.co.uk  Tue Mar  3 19:56:05 2009
From: afra at aurigae.demon.co.uk (Phill Harvey-Smith)
Date: Wed, 04 Mar 2009 00:56:05 +0000
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>
	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
Message-ID: <49ADD1A5.9040808@aurigae.demon.co.uk>

Rick Taylor wrote:
> Has anyone ever made Multi-Pak clones? 

I believe there are a couple of designs that I have seen, after all it's 
not really rocket science, really just a buffered bus expander with some 
selection & arbitration logic really.

> Would it be legal to do so?

I'm not a lawyer so all IMHO :)

Literal hardware clones, probably, but wether it would be a problem 
would depend on wether Radio Shack where interested in persuing it, 
considdering that the Dragon 32/64 where a virtual clones of the CoCo, 
I'd say probably not. Also considdering the age of the hardware in 
question it would probably not be worth it.

Logical clones using the same registers at the same IO locations and 
custom designed hardware using say LS logic or a CPLD should be fine.

As an example look at all the IBM PC clones there where, which where 
functionally identical, and IBM couldn't do anything about them, unless 
as was the case with some of them, they ripped off the IBM bios, rather 
than coding their own.

Cheers.

Phill.

-- 
Phill Harvey-Smith, Programmer, Hardware hacker, and general eccentric !

"You can twist perceptions, but reality won't budge" -- Rush.


From tjseagrove at writeme.com  Tue Mar  3 21:23:06 2009
From: tjseagrove at writeme.com (Tom Seagrove)
Date: Tue, 3 Mar 2009 21:23:06 -0500
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <49ADD1A5.9040808@aurigae.demon.co.uk>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<49ADD1A5.9040808@aurigae.demon.co.uk>
Message-ID: <010401c99c70$27721d30$76565790$@com>

Chris Hawk, who is on this list, made a product called the SlotPak III.  I
own one and used it until everything got packed away.  Soon, it will find a
home in my new computer room where I will setup my CoCo III again.  It
worked great and never had any problem at all with it.  Everything was
housed in what looked like a standard floppy controller housing and had a
base to support it.  It had a total of 3 slots and 2 were switchable.

Tom

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
Behalf Of Phill Harvey-Smith
Sent: Tuesday, March 03, 2009 7:56 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] Multi-Pak Interface question.

Rick Taylor wrote:
> Has anyone ever made Multi-Pak clones? 

I believe there are a couple of designs that I have seen, after all it's 
not really rocket science, really just a buffered bus expander with some 
selection & arbitration logic really.

> Would it be legal to do so?

I'm not a lawyer so all IMHO :)

Literal hardware clones, probably, but wether it would be a problem 
would depend on wether Radio Shack where interested in persuing it, 
considdering that the Dragon 32/64 where a virtual clones of the CoCo, 
I'd say probably not. Also considdering the age of the hardware in 
question it would probably not be worth it.

Logical clones using the same registers at the same IO locations and 
custom designed hardware using say LS logic or a CPLD should be fine.

As an example look at all the IBM PC clones there where, which where 
functionally identical, and IBM couldn't do anything about them, unless 
as was the case with some of them, they ripped off the IBM bios, rather 
than coding their own.

Cheers.

Phill.

-- 
Phill Harvey-Smith, Programmer, Hardware hacker, and general eccentric !

"You can twist perceptions, but reality won't budge" -- Rush.

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.0.237 / Virus Database: 270.11.5/1978 - Release Date: 03/03/09
07:25:00



From cdiman7 at flash.net  Tue Mar  3 22:59:42 2009
From: cdiman7 at flash.net (KARL SEFCIK)
Date: Tue, 3 Mar 2009 19:59:42 -0800 (PST)
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
Message-ID: <576677.85363.qm@web80203.mail.mud.yahoo.com>

Rick, and others,? ? I was replying and had to reboot, hope I can remember all the stuff I was going to add. Forgive me for not being in the chat, but answering on the echo, what if we were to make an MPI on an ASIC basis? Get the hardware, engineer it, and then for the Roms and software that made the MPI work, we get a huge memory chip and program it with Linux? Then the bugs can be worked arounde, Ramtron makes a 4 MB chip that retains memory (with no power) for life now, just a thought.?

--- On Tue, 3/3/09, Rick Taylor <coder32768 at gmail.com> wrote:
From: Rick Taylor <coder32768 at gmail.com>
Subject: Re: [Coco] Multi-Pak Interface question.
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Date: Tuesday, March 3, 2009, 7:28 PM

Has anyone ever made Multi-Pak clones? Would it be legal to do so?

On Tue, Mar 3, 2009 at 3:19 PM, Bob Devries <devries.bob at gmail.com>
wrote:

> The PAK which failed with the MPI upgrade was the one which came with the
> first version of CocoMax. Its address was at $FF90 IIRC, which is the same
> as the Coco3's GIME chip registers.
>
> --
> Regards, Bob Devries, Dalby, Queensland, Australia
>
> Isaiah 50:4 The sovereign Lord has given me
> the capacity to be his spokesman,
> so that I know how to help the weary.
>
> website: http://www.home.gil.com.au/~bdevasl
> my blog: http://bdevries.invigorated.org/
>
> ----- Original Message ----- From: "J.P. Samson" <
> jps.subscriptions at gmail.com>
> To: "CoCoList for Color Computer Enthusiasts"
<coco at maltedmedia.com>
> Sent: Wednesday, March 04, 2009 8:37 AM
> Subject: Re: [Coco] Multi-Pak Interface question.
>
>
>
>  On Mar 3, 2009, at 3:32 PM, Ryan Pritchard wrote:
>>
>>> If one were to acquire a 26-3024 MPI that had the PAL upgrade to
run with
>>> the CoCo3, would it still work on a CoCo 1 or CoCo 2?
>>>
>>
>> Yes.
>>
>> The caveat being there was one known pak that would be broken with the
PAL
>> upgrade, but I can't remember which.  It wasn't a common pak,
to  be sure.
>>
>> -- JP
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
All of this machinery making modern music can still be open hearted -
not so coldly charted; it's really just a question of your honesty.

- Neil Peart, Rush, _The Spirit of Radio_

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From coconut at pritchard.ca  Tue Mar  3 23:11:48 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Tue, 3 Mar 2009 22:11:48 -0600
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <49ADD1A5.9040808@aurigae.demon.co.uk>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>
	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<49ADD1A5.9040808@aurigae.demon.co.uk>
Message-ID: <EE279CB9-DDE7-4918-901C-E40D4FCE7D50@pritchard.ca>

It would be my understanding that any patent (if any existed) on the  
MPI would be expired at this point, leaving only a potential for copy- 
write issues.  Though my thought is if one can buy the PAL fix for the  
CoCo 3, then one merely has to assemble said parts from a schematic  
and voila MPI.

On the flip side there was mention of Chris Hawk who is still on this  
list that previously made a compatible/comparable device called the  
SlotPak III, as was pointed out by Tom Seagrove.  Maybe he would be  
able to release details on that device if they still exist such that  
we could see these manufactured again, or at least people could choose  
to make one themselves.

Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies



On 3-Mar-09, at 6:56 PM, Phill Harvey-Smith wrote:

> Rick Taylor wrote:
>> Has anyone ever made Multi-Pak clones?
>
> I believe there are a couple of designs that I have seen, after all  
> it's not really rocket science, really just a buffered bus expander  
> with some selection & arbitration logic really.
>
>> Would it be legal to do so?
>
> I'm not a lawyer so all IMHO :)
>
> Literal hardware clones, probably, but wether it would be a problem  
> would depend on wether Radio Shack where interested in persuing it,  
> considdering that the Dragon 32/64 where a virtual clones of the  
> CoCo, I'd say probably not. Also considdering the age of the  
> hardware in question it would probably not be worth it.
>
> Logical clones using the same registers at the same IO locations and  
> custom designed hardware using say LS logic or a CPLD should be fine.
>
> As an example look at all the IBM PC clones there where, which where  
> functionally identical, and IBM couldn't do anything about them,  
> unless as was the case with some of them, they ripped off the IBM  
> bios, rather than coding their own.
>
> Cheers.
>
> Phill.
>
> -- 
> Phill Harvey-Smith, Programmer, Hardware hacker, and general  
> eccentric !
>
> "You can twist perceptions, but reality won't budge" -- Rush.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From lamune at doki-doki.net  Tue Mar  3 23:56:57 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Tue, 3 Mar 2009 20:56:57 -0800
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <576677.85363.qm@web80203.mail.mud.yahoo.com>
References: <fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<576677.85363.qm@web80203.mail.mud.yahoo.com>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D27@fenestra.lamunet.local>

Engineer an ASIC for a new MPI? Nonsense. The MPI logic can be constructed with probably less than ten bucks worth of 7400 series logic.

The real engineering challenge I think would be in the physical packaging of such a device.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of KARL SEFCIK
> Sent: Tuesday, March 03, 2009 8:00 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Multi-Pak Interface question.
> 
> Rick, and others,? ? I was replying and had to reboot, hope I can
> remember all the stuff I was going to add. Forgive me for not being in
> the chat, but answering on the echo, what if we were to make an MPI on
> an ASIC basis? Get the hardware, engineer it, and then for the Roms and
> software that made the MPI work, we get a huge memory chip and program
> it with Linux? Then the bugs can be worked arounde, Ramtron makes a 4
> MB chip that retains memory (with no power) for life now, just a
> thought.
> 
> --- On Tue, 3/3/09, Rick Taylor <coder32768 at gmail.com> wrote:
> From: Rick Taylor <coder32768 at gmail.com>
> Subject: Re: [Coco] Multi-Pak Interface question.
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Date: Tuesday, March 3, 2009, 7:28 PM
> 
> Has anyone ever made Multi-Pak clones? Would it be legal to do so?
> 
> On Tue, Mar 3, 2009 at 3:19 PM, Bob Devries <devries.bob at gmail.com>
> wrote:
> 
> > The PAK which failed with the MPI upgrade was the one which came with
> the
> > first version of CocoMax. Its address was at $FF90 IIRC, which is the
> same
> > as the Coco3's GIME chip registers.
> >
> > --
> > Regards, Bob Devries, Dalby, Queensland, Australia
> >
> > Isaiah 50:4 The sovereign Lord has given me
> > the capacity to be his spokesman,
> > so that I know how to help the weary.
> >
> > website: http://www.home.gil.com.au/~bdevasl
> > my blog: http://bdevries.invigorated.org/
> >
> > ----- Original Message ----- From: "J.P. Samson" <
> > jps.subscriptions at gmail.com>
> > To: "CoCoList for Color Computer Enthusiasts"
> <coco at maltedmedia.com>
> > Sent: Wednesday, March 04, 2009 8:37 AM
> > Subject: Re: [Coco] Multi-Pak Interface question.
> >
> >
> >
> >  On Mar 3, 2009, at 3:32 PM, Ryan Pritchard wrote:
> >>
> >>> If one were to acquire a 26-3024 MPI that had the PAL upgrade to
> run with
> >>> the CoCo3, would it still work on a CoCo 1 or CoCo 2?
> >>>
> >>
> >> Yes.
> >>
> >> The caveat being there was one known pak that would be broken with
> the
> PAL
> >> upgrade, but I can't remember which.  It wasn't a common pak,
> to  be sure.
> >>
> >> -- JP
> >>
> >>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> http://five.pairlist.net/mailman/listinfo/coco
> >>
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> >
> 
> 
> 
> --
> All of this machinery making modern music can still be open hearted -
> not so coldly charted; it's really just a question of your honesty.
> 
> - Neil Peart, Rush, _The Spirit of Radio_
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From johnguin at hotmail.com  Tue Mar  3 23:58:15 2009
From: johnguin at hotmail.com (John Guin)
Date: Wed, 4 Mar 2009 04:58:15 +0000
Subject: [Coco] Team OS9 (Seti@Home)
In-Reply-To: <0575CD3B-48B3-4031-BDFC-631F89482F14@pobox.com>
References: <5631e580903021531y59aa7d0alf4a6e4126f925927@mail.gmail.com>
	<1E6BE6DB-0A52-4CF0-B708-873C3ABFD8A4@pobox.com>
	<5631e580903021604y697d02w5c0faf92123c2fe7@mail.gmail.com> 
	<0575CD3B-48B3-4031-BDFC-631F89482F14@pobox.com>
Message-ID: <BAY138-W34A50E380817AC7A1BDC1BD9A70@phx.gbl>


To go off topic, I've been running GIMPS for almost 12 years now.  Still no primes detected - my big claim to fame was being in the top 100 at one point.

 

Now it would be VERY interesting to find a shared project that the COCO could be used for - slow as it is...

 

John
 
> From: alsplace at pobox.com
> To: coco at maltedmedia.com
> Date: Mon, 2 Mar 2009 17:11:19 -0700
> Subject: Re: [Coco] Team OS9 (Seti at Home)
> 
> We had two. One was that one, and I probably joined Team Microware or 
> something.
> 
> Sent from my iPhone
> Follow me on Twitter - http://twitter.com/allenhuffman
> 
> On Mar 2, 2009, at 5:04 PM, Rogelio Perea <os9dude at gmail.com> wrote:
> 
> > Chet Simpson... that's it! :-)
> >
> > I don't think you're listed there Allen...
> >
> >
> >
> > On Mon, Mar 2, 2009 at 6:56 PM, Allen Huffman <alsplace at pobox.com> 
> > wrote:
> >
> >> Chet Simspon I think. Am I still listed?haven't ran it in years.
> >>
> >> Sent from my iPhone
> >> Follow me on Twitter - http://twitter.com/allenhuffman
> >>
> >>
> >> On Mar 2, 2009, at 4:31 PM, Rogelio Perea <os9dude at gmail.com> wrote:
> >>
> >> Just the once every ten years reminder to the folks "out there" 
> >> that want
> >>> to
> >>> believe ;-)
> >>>
> >>> I have been running the Seti at Home software on and off since 1989 and
> >>> today
> >>> while checking my profile there I found that the founder status 
> >>> requested
> >>> last year for Team OS9 had been OK'd for transfer from the original
> >>> founder
> >>> (DigitalAsphyxia - can't recall the real name at this moment). So I
> >>> decided
> >>> to check it out, only 6 members of which two are the sole active 
> >>> ones -
> >>> cobwebs everywhere!
> >>>
> >>> http://setiathome.berkeley.edu/team_display.php?teamid=36796
> >>>
> >>> Thanks for the bandwidth _\\//
> >>>
> >>
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco

_________________________________________________________________
Express your personality in color! Preview and select themes for Hotmail?. 
http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=TXT_MSGTX_WL_HM_express_032009#colortheme

From goosey at virgo.sdc.org  Wed Mar  4 00:56:39 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Tue, 3 Mar 2009 22:56:39 -0700
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <49ADA6C2.6000006@iinet.net.au>
References: <49AD9E55.6000804@iinet.net.au>
	<5d802cd0903031340k45573f1bob557d639026d1d55@mail.gmail.com>
	<49ADA6C2.6000006@iinet.net.au>
Message-ID: <20090304055639.GA25102@virgo.sdc.org>

On Wed, Mar 04, 2009 at 08:53:06AM +1100, Mark McDougall wrote:

> I also believe that at least one person has "gone 16550" to use his 
> words??? Is that the case? Are there many here that are using 16550, and 
> what software supports it?

There have been one or two projects to build a 16550 serial card.
>From what I understand, they have floundered not on the hardware
issues, but on software issues. :-(

Writing an OS-9 driver is one thing, but (I believe) the 16550 can't
really pretend to be a 6551, and this breaks *every* BASIC terminal
program ever written...

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From goosey at virgo.sdc.org  Wed Mar  4 01:07:44 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Tue, 3 Mar 2009 23:07:44 -0700
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>
	<00a501c99c56$916e3850$0701a8c0@master>
	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
Message-ID: <20090304060744.GC25102@virgo.sdc.org>

On Tue, Mar 03, 2009 at 04:28:00PM -0800, Rick Taylor wrote:
> Has anyone ever made Multi-Pak clones? Would it be legal to do so?

I think every CoCo person who even pretends to be a hardware type has
designed their own MPI.

The trick is getting the connectors... :-(

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From afra at aurigae.demon.co.uk  Wed Mar  4 03:00:20 2009
From: afra at aurigae.demon.co.uk (Phill Harvey-Smith)
Date: Wed, 04 Mar 2009 08:00:20 +0000
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <20090304060744.GC25102@virgo.sdc.org>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
Message-ID: <49AE3514.9080606@aurigae.demon.co.uk>

Willard Goosey wrote:
> On Tue, Mar 03, 2009 at 04:28:00PM -0800, Rick Taylor wrote:
>> Has anyone ever made Multi-Pak clones? Would it be legal to do so?
> 
> I think every CoCo person who even pretends to be a hardware type has
> designed their own MPI.
> 
> The trick is getting the connectors... :-(

For some experements I did a while back, I used PC 8 bit ISA connectors 
and cut them down. Last time I checked these where still available.

Cheers.

Phill.



From brucewcalkins at charter.net  Wed Mar  4 05:51:45 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Wed, 4 Mar 2009 05:51:45 -0500
Subject: [Coco] Multi-Pak Interface question.
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com><49ADD1A5.9040808@aurigae.demon.co.uk>
	<010401c99c70$27721d30$76565790$@com>
Message-ID: <304C8BD75E6D43EFB06D155A7321BCC0@speedy>

> Has anyone ever made Multi-Pak clones?
 IIRCC; PBJ made a six slot version.  It was available in kit form or 
assembled.  I got a half done kit in one batch of CoCo hardware.

Bruce W.



From farna at att.net  Wed Mar  4 07:52:33 2009
From: farna at att.net (Frank Swygert)
Date: Wed, 04 Mar 2009 07:52:33 -0500
Subject: [Coco] CCR-81 & CCR-82 manuals
Message-ID: <49AE7991.80705@att.net>

Outside of the tip should be negative, inside positive. If it uses a phono jack the tip should be positive, large rear section negative. 

4 "C" cells clues you in on the power requirement. Should be 6V. According to a chart on Wikipedia (http://en.wikipedia.org/wiki/List_of_battery_sizes#Table_of_modern_battery_sizes), an alkaline C cell puts out 8000 mAh, standard battery 3800 mAh. That only indicates what the battery will put out, not what the cassette player needs though. 

Amps is the amount of electricity used, volts is the "pressure" it's delivered at.  A device will only draw what it needs, so you can use a larger amperage power supply than required, but you can't use a smaller one. If you try to use a smaller one it will of course heat up. You should be safe with a 1A universal power supply. Most small "wall arts" are 1A or less. Maybe someone has the AC supply for a CCR-81 or 82 that they can look at just to make sure. 

--------------
Date: Tue, 3 Mar 2009 09:45:33 -0500
From: "Bill" <cwgordon at carolina.rr.com>
Subject: Re: [Coco] CCR-81 & CCR-82 manuals
To: "'CoCoList for Color Computer Enthusiasts'" <coco at maltedmedia.com>
Message-ID: <005001c99c0e$b59a3ff0$20cebfd0$@rr.com>
Content-Type: text/plain;	charset="us-ascii"

Basically, I need to know about the input amperage and the tip polarity of
the AC power supply on the CCR-82. I need to find one.

-- 
Frank Swygert
Publisher, "American Motors Cars" 
Magazine (AMC)
For all AMC enthusiasts
http://farna.home.att.net/AMC.html
(free download available!)



From davehazelton at comcast.net  Wed Mar  4 08:12:44 2009
From: davehazelton at comcast.net (David Hazelton)
Date: Wed, 04 Mar 2009 08:12:44 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <20090304055639.GA25102@virgo.sdc.org>
References: <49AD9E55.6000804@iinet.net.au>	<5d802cd0903031340k45573f1bob557d639026d1d55@mail.gmail.com>	<49ADA6C2.6000006@iinet.net.au>
	<20090304055639.GA25102@virgo.sdc.org>
Message-ID: <49AE7E4C.2000806@comcast.net>

Willard Goosey wrote:
> On Wed, Mar 04, 2009 at 08:53:06AM +1100, Mark McDougall wrote:
>
>   
>> I also believe that at least one person has "gone 16550" to use his 
>> words??? Is that the case? Are there many here that are using 16550, and 
>> what software supports it?
>>     
>
> There have been one or two projects to build a 16550 serial card.
> >From what I understand, they have floundered not on the hardware
> issues, but on software issues. :-(
>
> Writing an OS-9 driver is one thing, but (I believe) the 16550 can't
> really pretend to be a 6551, and this breaks *every* BASIC terminal
> program ever written...
>
> Willard
>   
I have one built by Conect (IIRC)  Since when I bought it I only used 
OS9, It worked great.  I did get better throughput then the RS-PAK.  I 
did mostly Zmodem for file transfers, but I also logged in to VAX 
machines and Unix based Machines at Work.  

~David




From rcrislip at neo.rr.com  Wed Mar  4 09:01:20 2009
From: rcrislip at neo.rr.com (richec)
Date: Wed, 4 Mar 2009 09:01:20 -0500
Subject: [Coco] coco font (kinda)
In-Reply-To: <001001c99add$aadb2bb0$00918310$@rr.com>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>
	<49AB3F77.1090106@worldnet.att.net>
	<001001c99add$aadb2bb0$00918310$@rr.com>
Message-ID: <200903040901.21089.rcrislip@neo.rr.com>

Hi Bill,

What font editor are you using. Typesmith? TIA


From mmarlette at frontiernet.net  Wed Mar  4 10:40:20 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Wed, 4 Mar 2009 15:40:20 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <379248463.77591236181220250.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

Willard,

The NitrOS-9/Driver is already written for a 16550 device. I have had a homebrew card running for almost 10yrs based upon that chipset.

Yes, it would break all the old term programs. A caveat of adding new technology to an old machine. Not a problem in NitrOS-9 as the driver/dd is not part of the actual program, when properly written.

The SuperBoard has a multi-function chip on it that has the 16550 in it. Anyone that has done high speed serial testing in a system will design it with hardware handshaking. It is no secret that the ACIA(6551) has issues with this, plus almost no buffer space. Not a good choice for new designs, IMHO. 16xxx series offers GREAT buffers, programmable interrupt thresholds etc..... I guess that is why they are so common, oh they work too! :)

Regards,

Mark
Cloud-9

----- Original Message -----
From: "Willard Goosey" <goosey at virgo.sdc.org>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Tuesday, March 3, 2009 11:56:39 PM GMT -06:00 US/Canada Central
Subject: [Coco] 16550 wasRe:  RS232 paks

On Wed, Mar 04, 2009 at 08:53:06AM +1100, Mark McDougall wrote:

> I also believe that at least one person has "gone 16550" to use his 
> words??? Is that the case? Are there many here that are using 16550, and 
> what software supports it?

There have been one or two projects to build a 16550 serial card.
>From what I understand, they have floundered not on the hardware
issues, but on software issues. :-(

Writing an OS-9 driver is one thing, but (I believe) the 16550 can't
really pretend to be a 6551, and this breaks *every* BASIC terminal
program ever written...

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From gene.heskett at verizon.net  Wed Mar  4 10:42:37 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 10:42:37 -0500
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <304C8BD75E6D43EFB06D155A7321BCC0@speedy>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<010401c99c70$27721d30$76565790$@com>
	<304C8BD75E6D43EFB06D155A7321BCC0@speedy>
Message-ID: <200903041042.37260.gene.heskett@verizon.net>

On Wednesday 04 March 2009, Bruce W. Calkins wrote:
>> Has anyone ever made Multi-Pak clones?
>
> IIRCC; PBJ made a six slot version.  It was available in kit form or
>assembled.  I got a half done kit in one batch of CoCo hardware.
>
>Bruce W.
>
Do you still have it?,  I might be interested in seeing if I can finish it.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"If you are afraid of loneliness, don't marry."
-- Chekhov



From cwgordon at carolina.rr.com  Wed Mar  4 10:47:06 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Wed, 4 Mar 2009 10:47:06 -0500
Subject: [Coco] coco font (kinda)
In-Reply-To: <200903040901.21089.rcrislip@neo.rr.com>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>	<49AB3F77.1090106@worldnet.att.net>	<001001c99add$aadb2bb0$00918310$@rr.com>
	<200903040901.21089.rcrislip@neo.rr.com>
Message-ID: <012301c99ce0$78ce1970$6a6a4c50$@rr.com>

Font Creator 5.0 Professional.

My biggest drawback at copying a font is my poor eyesight.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of richec
> Sent: Wednesday, March 04, 2009 9:01 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] coco font (kinda)
> 
> Hi Bill,
> 
> What font editor are you using. Typesmith? TIA
> 



From cwgordon at carolina.rr.com  Wed Mar  4 10:48:14 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Wed, 4 Mar 2009 10:48:14 -0500
Subject: [Coco] FD-500 drive cable
Message-ID: <012401c99ce0$a1836500$e48a2f00$@rr.com>

Does anyone have an FD-500 drive cable I could have? 

Thanks

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From gene.heskett at verizon.net  Wed Mar  4 10:53:07 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 10:53:07 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <49AE7E4C.2000806@comcast.net>
References: <49AD9E55.6000804@iinet.net.au>
	<20090304055639.GA25102@virgo.sdc.org> <49AE7E4C.2000806@comcast.net>
Message-ID: <200903041053.07509.gene.heskett@verizon.net>

On Wednesday 04 March 2009, David Hazelton wrote:
>Willard Goosey wrote:
>> On Wed, Mar 04, 2009 at 08:53:06AM +1100, Mark McDougall wrote:
>>> I also believe that at least one person has "gone 16550" to use his
>>> words??? Is that the case? Are there many here that are using 16550, and
>>> what software supports it?
>>
>> There have been one or two projects to build a 16550 serial card.
>>
>> >From what I understand, they have floundered not on the hardware
>>
>> issues, but on software issues. :-(
>>
>> Writing an OS-9 driver is one thing, but (I believe) the 16550 can't
>> really pretend to be a 6551, and this breaks *every* BASIC terminal
>> program ever written...
>>
>> Willard
>
>I have one built by Conect (IIRC)  Since when I bought it I only used
>OS9, It worked great.  I did get better throughput then the RS-PAK.  I
>did mostly Zmodem for file transfers, but I also logged in to VAX
>machines and Unix based Machines at Work.
>
Since the 16550 needs a 16 wide group of register addresses, which would 
displace 4 regular packs from the coco's address space, I wonder how that was 
handled?  I could see it being done with a 2 byte write or read sequence where 
the first write sets the register address, the next read or write then sets or 
gets that data. If the IRQ source register address wasn't subject to that, I 
could see it being done in the usual coco 4 byte wide address space, of course 
with its own driver.

Was the Conect driver ever dissed and made part of the nitros9 package?

>~
>David
>
-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"If you are afraid of loneliness, don't marry."
-- Chekhov



From gene.heskett at verizon.net  Wed Mar  4 10:55:52 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 10:55:52 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <379248463.77591236181220250.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
References: <379248463.77591236181220250.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <200903041055.52516.gene.heskett@verizon.net>

On Wednesday 04 March 2009, Mark Marlette wrote:
>Willard,
>
>The NitrOS-9/Driver is already written for a 16550 device. I have had a
> homebrew card running for almost 10yrs based upon that chipset.
>
>Yes, it would break all the old term programs. A caveat of adding new
> technology to an old machine. Not a problem in NitrOS-9 as the driver/dd is
> not part of the actual program, when properly written.
>
>The SuperBoard has a multi-function chip on it that has the 16550 in it.
> Anyone that has done high speed serial testing in a system will design it
> with hardware handshaking. It is no secret that the ACIA(6551) has issues
> with this, plus almost no buffer space. Not a good choice for new designs,
> IMHO. 16xxx series offers GREAT buffers, programmable interrupt thresholds
> etc..... I guess that is why they are so common, oh they work too! :)

Heh.  But the SuperBoard will be available before, or after Duke Nukem 
Forever?

:-)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Things are not always what they seem.
		-- Phaedrus



From brucewcalkins at charter.net  Wed Mar  4 14:27:31 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Wed, 4 Mar 2009 14:27:31 -0500
Subject: [Coco] Multi-Pak Interface question.
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com><010401c99c70$27721d30$76565790$@com><304C8BD75E6D43EFB06D155A7321BCC0@speedy>
	<200903041042.37260.gene.heskett@verizon.net>
Message-ID: <258E30D8F7E94CEFB09D8A50AE08AD0B@speedy>

>>> Has anyone ever made Multi-Pak clones?
>>
>> IIRCC; PBJ made a six slot version.  It was available in kit form or
>>assembled.  I got a half done kit in one batch of CoCo hardware.
>>
>>Bruce W.
>>
> Do you still have it?,  I might be interested in seeing if I can finish 
> it.
>
> -- 
> Cheers, Gene


LOL; it is still on my to-do list, as soon as I get enough Round-Tuits.  ;)

Now that I think about it, it is a good candidate for one of the repacks.



Bruce W.



From operator at coco3.com  Wed Mar  4 14:39:59 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 04 Mar 2009 13:39:59 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <379248463.77591236181220250.JavaMail.root@cl04-host03.roch
	.ny.frontiernet.net>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<379248463.77591236181220250.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <20090304194026.A8A8920A13@qs281.pair.com>

At 09:40 AM 3/4/2009, you wrote:
>Willard,
>
>The NitrOS-9/Driver is already written for a 16550 device. I have 
>had a homebrew card running for almost 10yrs based upon that chipset.
>
>Yes, it would break all the old term programs. A caveat of adding 
>new technology to an old machine. Not a problem in NitrOS-9 as the 
>driver/dd is not part of the actual program, when properly written.
>
>The SuperBoard has a multi-function chip on it that has the 16550 in 
>it. Anyone that has done high speed serial testing in a system will 
>design it with hardware handshaking. It is no secret that the 
>ACIA(6551) has issues with this, plus almost no buffer space. Not a 
>good choice for new designs, IMHO. 16xxx series offers GREAT 
>buffers, programmable interrupt thresholds etc..... I guess that is 
>why they are so common, oh they work too! :)
>
>Regards,
>
>Mark
>Cloud-9


Mark,

Exactly what problems have you yourself had with the 6551 so that I 
may try to offer a software solution?  I'm not claiming to have all 
the answers, but I've done a serious amount of 6551 coding in the 
past, and I can assure you that the chip itself is not always the 
problem.  The programmer is 90% of the problem.  The OS is 90% of the 
problem.  If there's some little bug or dislike about a certain chip, 
I guarantee that there's the same number or more in the 16550.  I've 
read about that chip and based on how many variants are floating 
around, how can anyone ever agree on a right way to code the 
routines?  It appears to be a mess, no less than what you claim about 
the 6551.  I'm not saying any certain chip is BETTER than the other.. 
I'm saying that TOO many programmers and nonprogrammers have clashed 
about these chips and in the end, they're all still being used 
today.  You can always tell when the programmer took shortcuts or 
just didn't know what he was doing.

When you say the 6551 is not a wise choice for any new designs, your 
intent is clear but the statement is not true.  Someone who's put out 
a new wireless RS-232 pak didn't just wake up yesterday and discover 
the 6551.  People who know how to write good software aren't afraid 
of the 6551.

My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo 
1's, 1 CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy 
looping tests (1-2 days sometimes), and I haven't seen it bomb out 
yet.  Can you please tell me what circumstances I need in order to 
break my protocol ?






-- 
Roger Taylor

http://www.wordofthedayonline.com



From lamune at doki-doki.net  Wed Mar  4 14:48:19 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Wed, 4 Mar 2009 11:48:19 -0800
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <20090304194026.A8A8920A13@qs281.pair.com>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net><379248463.77591236181220250.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<20090304194026.A8A8920A13@qs281.pair.com>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A4@fenestra.lamunet.local>

Roger,

The 6551 does have a nasty bug where a state change in the hardware flow
control causes partially transmitted (or assembled?) characters to be
dropped.

I would guess that in what you're doing, things are totally software
driven and in tight loops where such conditions would not happen.

In a multitasking environment such as OS9 what Mark says is much more
applicable. I'd agree in that situation I'd take a 16550 over a 6551 any
day. 



-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com]
On Behalf Of Roger Taylor
Sent: Wednesday, March 04, 2009 11:40 AM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] 16550 wasRe: RS232 paks

At 09:40 AM 3/4/2009, you wrote:
>Willard,
>
>The NitrOS-9/Driver is already written for a 16550 device. I have 
>had a homebrew card running for almost 10yrs based upon that chipset.
>
>Yes, it would break all the old term programs. A caveat of adding 
>new technology to an old machine. Not a problem in NitrOS-9 as the 
>driver/dd is not part of the actual program, when properly written.
>
>The SuperBoard has a multi-function chip on it that has the 16550 in 
>it. Anyone that has done high speed serial testing in a system will 
>design it with hardware handshaking. It is no secret that the 
>ACIA(6551) has issues with this, plus almost no buffer space. Not a 
>good choice for new designs, IMHO. 16xxx series offers GREAT 
>buffers, programmable interrupt thresholds etc..... I guess that is 
>why they are so common, oh they work too! :)
>
>Regards,
>
>Mark
>Cloud-9


Mark,

Exactly what problems have you yourself had with the 6551 so that I 
may try to offer a software solution?  I'm not claiming to have all 
the answers, but I've done a serious amount of 6551 coding in the 
past, and I can assure you that the chip itself is not always the 
problem.  The programmer is 90% of the problem.  The OS is 90% of the 
problem.  If there's some little bug or dislike about a certain chip, 
I guarantee that there's the same number or more in the 16550.  I've 
read about that chip and based on how many variants are floating 
around, how can anyone ever agree on a right way to code the 
routines?  It appears to be a mess, no less than what you claim about 
the 6551.  I'm not saying any certain chip is BETTER than the other.. 
I'm saying that TOO many programmers and nonprogrammers have clashed 
about these chips and in the end, they're all still being used 
today.  You can always tell when the programmer took shortcuts or 
just didn't know what he was doing.

When you say the 6551 is not a wise choice for any new designs, your 
intent is clear but the statement is not true.  Someone who's put out 
a new wireless RS-232 pak didn't just wake up yesterday and discover 
the 6551.  People who know how to write good software aren't afraid 
of the 6551.

My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo 
1's, 1 CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy 
looping tests (1-2 days sometimes), and I haven't seen it bomb out 
yet.  Can you please tell me what circumstances I need in order to 
break my protocol ?






-- 
Roger Taylor

http://www.wordofthedayonline.com


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



From coconut at pritchard.ca  Wed Mar  4 15:45:00 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Wed, 4 Mar 2009 14:45:00 -0600
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <20090304060744.GC25102@virgo.sdc.org>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>
	<00a501c99c56$916e3850$0701a8c0@master>
	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
Message-ID: <1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>

If I am correct either of these connectors should do the trick for board
mounting.

http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=EDC341402-ND

http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=EDC395402-ND

On Wed, Mar 4, 2009 at 12:07 AM, Willard Goosey <goosey at virgo.sdc.org>wrote:

> On Tue, Mar 03, 2009 at 04:28:00PM -0800, Rick Taylor wrote:
> > Has anyone ever made Multi-Pak clones? Would it be legal to do so?
>
> I think every CoCo person who even pretends to be a hardware type has
> designed their own MPI.
>
> The trick is getting the connectors... :-(
>
> Willard
> --
> Willard Goosey  goosey at sdc.org
> Socorro, New Mexico, USA
> I search my heart and find Cimmeria, land of Darkness and the Night.
>  -- R.E. Howard
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From mmarlette at frontiernet.net  Wed Mar  4 15:55:48 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Wed, 4 Mar 2009 20:55:48 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <334800648.181391236199895387.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <1269562842.183071236200148073.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

Roger,

As Mike and Darren have indicated, this is very much the case. No offense Mike as I don't recall, but for Darren his posts are so correct, enjoyable to read on my end. His CoCo testing on slew rate was enjoyable to read, true engineer or one that thinks as one.

Not matter what you do in your software you will not fix the internal flaws of the ACIA. Your application might be able to live with it but does not remove the fact. IE: retransmit a packet of lost data or corrupt data etc....

You probably are not invoking hardware handshaking in your design.

This is a requirement of my design(s). You can have any requirement you want. The fact is that when the OS tells the sending device to stop because it is full and processing the data, it better stop and without data loss. This again is not the case with the 6551.

You can try and powercode around it but once you move out of your app the under lying problem is still present.

Your test condition. Make one of your PCs so busy that they can't service the data stream from the CoCo. The PC, normally, if programmed to, would use RTS/CTS to stop the flow. I have done extensive testing using at Atmel AVR which at 230.4K baud can cause a Win XP box 3.2GHZ Dual Core, blahblah, machine to loose data. So if you aren't using hardware handshaking and you just assume that the PC is fast enough to keep up with the data stream, then you will have issues. Not all PC are created equal. Most CoCos are, on the RSDOS side. Move away from DECB which is NOT an OS but sorts of a loader, deal with REAL world interrupts, you will see. 

How is your device performing in NitrOS-9? Test case: Start a stream of data from the PC, then do a dir of a hard drive or floppy. You will see that the RTS/CTS lines will activate to slow the data transmission until full attention can be given back to the stream. No RTS/CTS, hardware shake, watch the data loss. Pretty simple.

I have done both designs, The ACIA does work, just not well in higher bandwidth situations due to the flow problems. Thus my requirement. I am curious how you device is performing in NitrOS-9. Do you have any test cases running there?

Hopefully that helps. ???

Regards,

Mark
Cloud-9 



----- Original Message -----
From: "Roger Taylor" <operator at coco3.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 4, 2009 1:39:59 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

At 09:40 AM 3/4/2009, you wrote:
>Willard,
>
>The NitrOS-9/Driver is already written for a 16550 device. I have 
>had a homebrew card running for almost 10yrs based upon that chipset.
>
>Yes, it would break all the old term programs. A caveat of adding 
>new technology to an old machine. Not a problem in NitrOS-9 as the 
>driver/dd is not part of the actual program, when properly written.
>
>The SuperBoard has a multi-function chip on it that has the 16550 in 
>it. Anyone that has done high speed serial testing in a system will 
>design it with hardware handshaking. It is no secret that the 
>ACIA(6551) has issues with this, plus almost no buffer space. Not a 
>good choice for new designs, IMHO. 16xxx series offers GREAT 
>buffers, programmable interrupt thresholds etc..... I guess that is 
>why they are so common, oh they work too! :)
>
>Regards,
>
>Mark
>Cloud-9


Mark,

Exactly what problems have you yourself had with the 6551 so that I 
may try to offer a software solution?  I'm not claiming to have all 
the answers, but I've done a serious amount of 6551 coding in the 
past, and I can assure you that the chip itself is not always the 
problem.  The programmer is 90% of the problem.  The OS is 90% of the 
problem.  If there's some little bug or dislike about a certain chip, 
I guarantee that there's the same number or more in the 16550.  I've 
read about that chip and based on how many variants are floating 
around, how can anyone ever agree on a right way to code the 
routines?  It appears to be a mess, no less than what you claim about 
the 6551.  I'm not saying any certain chip is BETTER than the other.. 
I'm saying that TOO many programmers and nonprogrammers have clashed 
about these chips and in the end, they're all still being used 
today.  You can always tell when the programmer took shortcuts or 
just didn't know what he was doing.

When you say the 6551 is not a wise choice for any new designs, your 
intent is clear but the statement is not true.  Someone who's put out 
a new wireless RS-232 pak didn't just wake up yesterday and discover 
the 6551.  People who know how to write good software aren't afraid 
of the 6551.

My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo 
1's, 1 CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy 
looping tests (1-2 days sometimes), and I haven't seen it bomb out 
yet.  Can you please tell me what circumstances I need in order to 
break my protocol ?






-- 
Roger Taylor

http://www.wordofthedayonline.com


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From gene.heskett at verizon.net  Wed Mar  4 15:56:13 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 15:56:13 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A4@fenestra.lamunet.local>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<20090304194026.A8A8920A13@qs281.pair.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A4@fenestra.lamunet.local>
Message-ID: <200903041556.13849.gene.heskett@verizon.net>

On Wednesday 04 March 2009, Mike Pepe wrote:
>Roger,
>
>The 6551 does have a nasty bug where a state change in the hardware flow
>control causes partially transmitted (or assembled?) characters to be
>dropped.
>
>I would guess that in what you're doing, things are totally software
>driven and in tight loops where such conditions would not happen.
>
>In a multitasking environment such as OS9 what Mark says is much more
>applicable. I'd agree in that situation I'd take a 16550 over a 6551 any
>day.
>
>
>
>-----Original Message-----
>From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com]
>On Behalf Of Roger Taylor
>Sent: Wednesday, March 04, 2009 11:40 AM
>To: CoCoList for Color Computer Enthusiasts
>Subject: Re: [Coco] 16550 wasRe: RS232 paks
>
>At 09:40 AM 3/4/2009, you wrote:
>>Willard,
>>
>>The NitrOS-9/Driver is already written for a 16550 device. I have
>>had a homebrew card running for almost 10yrs based upon that chipset.
>>
>>Yes, it would break all the old term programs. A caveat of adding
>>new technology to an old machine. Not a problem in NitrOS-9 as the
>>driver/dd is not part of the actual program, when properly written.
>>
>>The SuperBoard has a multi-function chip on it that has the 16550 in
>>it. Anyone that has done high speed serial testing in a system will
>>design it with hardware handshaking. It is no secret that the
>>ACIA(6551) has issues with this, plus almost no buffer space. Not a
>>good choice for new designs, IMHO. 16xxx series offers GREAT
>>buffers, programmable interrupt thresholds etc..... I guess that is
>>why they are so common, oh they work too! :)
>>
>>Regards,
>>
>>Mark
>>Cloud-9
>
>Mark,
>
>Exactly what problems have you yourself had with the 6551 so that I
>may try to offer a software solution?  I'm not claiming to have all
>the answers, but I've done a serious amount of 6551 coding in the
>past, and I can assure you that the chip itself is not always the
>problem.  The programmer is 90% of the problem.  The OS is 90% of the
>problem.  If there's some little bug or dislike about a certain chip,
>I guarantee that there's the same number or more in the 16550.  I've
>read about that chip and based on how many variants are floating
>around, how can anyone ever agree on a right way to code the
>routines?  It appears to be a mess, no less than what you claim about
>the 6551.  I'm not saying any certain chip is BETTER than the other..
>I'm saying that TOO many programmers and nonprogrammers have clashed
>about these chips and in the end, they're all still being used
>today.  You can always tell when the programmer took shortcuts or
>just didn't know what he was doing.
>
>When you say the 6551 is not a wise choice for any new designs, your
>intent is clear but the statement is not true.  Someone who's put out
>a new wireless RS-232 pak didn't just wake up yesterday and discover
>the 6551.  People who know how to write good software aren't afraid
>of the 6551.
>
With sockmasters fix it does the 7 wire hardware protocol flawlessly.  I didd 
at one time using it between the coco and an amiga, this while I was doing the 
last version of zmodem, (rzsz-3.36.lzh?), and there I never had a problem even 
when the tally lights on an rs232 sniffer were indicating flow was disabled 
1/4/th of the time while using 9600 baud and getting 730cps.  I have also used 
it to move files to/from the coco using minicom on this box although without 
visible rs232 flow tally leds.

>My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo
>1's, 1 CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy
>looping tests (1-2 days sometimes), and I haven't seen it bomb out
>yet.  Can you please tell me what circumstances I need in order to
>break my protocol ?

I haven't found a ush<->bluetooth gismo yet Roger but I'm still looking, I 
need to get rid of the direct wire as mother nature has blown some usb 
extension cabling already, and I can't think of a better way to get good 
isolation than this pack of yours.


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Beware of geeks bearing graft.



From gene.heskett at verizon.net  Wed Mar  4 16:15:42 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 16:15:42 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <200903041556.13849.gene.heskett@verizon.net>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A4@fenestra.lamunet.local>
	<200903041556.13849.gene.heskett@verizon.net>
Message-ID: <200903041615.42740.gene.heskett@verizon.net>

On Wednesday 04 March 2009, Gene Heskett wrote:
>On Wednesday 04 March 2009, Mike Pepe wrote:
>>Roger,
[...]
>I haven't found a ush<->bluetooth gismo yet Roger but I'm still looking, I
>need to get rid of the direct wire as mother nature has blown some usb
>extension cabling already, and I can't think of a better way to get good
>isolation than this pack of yours.
PS:
Just ordered 2 of these:
<http://www.usbgear.com/computer_cable_details.cfm?sku=USBG-
BLUE-20&cats=158&catid=661%2C123%2C158>

which are said to be class 1 devices.  Are they suitable? I figure I can put 
one on the laptop too.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The only perfect science is hind-sight.



From coconut at pritchard.ca  Wed Mar  4 17:13:23 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Wed, 4 Mar 2009 16:13:23 -0600
Subject: [Coco] '68' Micro Journal
In-Reply-To: <293588CE-36F5-4146-9EA5-859238ED2946@pritchard.ca>
References: <293588CE-36F5-4146-9EA5-859238ED2946@pritchard.ca>
Message-ID: <1806abd60903041413n4ccabf89va02dfffde5789dc0@mail.gmail.com>

So with all the activity lately with regards to magazine scanning on the
list.  I am expecting that if these magazines were to be scanned there would
be significant interest.

My concerns:
- Scanning takes a long time one page at a time.
- Cutting the spine devalues the magazine (these are in very good
condition), but makes the scanning go oh so much faster (plus I have access
to an auto sheet feeder multi-purpose device, with selectable DPI.

On Sun, Sep 28, 2008 at 2:47 PM, Ryan Pritchard <coconut at pritchard.ca>wrote:

> Hi all,
>
> I just went through a box in my basement.  This can be either a good or a
> bad thing.  I today's case I would guess it is a good thing as the subject
> of the posting may allude to.
>
> I have in my possession the following issues of '68' Micro Journal.
>
> Volume 1 all issues (1-9), though issues 1-3 are photo copies.
> Volume 2 all 12 issues.
> Volume 3 all 12 issues.
> Volume 4 all 12 issues.
> Volume 5 all 12 issues.
> Volume 6 all 11 issues, volume 8 was an AUG/SEP issue.
> Volume 7 all 12 issues.
> Volume 8 all 12 issues.
> Volume 9 all 12 issues.
> Volume 10 all 12 issues.
> Volume 11 issues 1-7, volume 6 was JUN/JUL, volume 7 was AUG/SEP.  Issue 1
> from volume 12 indicated '68' Micro Journal did not publish in OCT/NOV/DEC.
> Volume 12 issue 1, volume 1 was JAN/FEB.  (Is this all there was?  If so I
> have a complete set of '68' Micro Journal originals, save the three
> mentioned previously.
>
> I also currently have found the following issues in duplicate.
> Volume 2, issue 10.
> Volume 4, issues 3, 4, 7, 8.
> Volume 5, issue 1.
> Volume 11, issue 6.
>
> Regards,
>
> Ryan Pritchard
> Fun Extends All Basic Life Expectancies
>
>
>
>


-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From msmcdoug at iinet.net.au  Wed Mar  4 17:18:34 2009
From: msmcdoug at iinet.net.au (Mark McDougall)
Date: Thu, 05 Mar 2009 09:18:34 +1100
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <200903041053.07509.gene.heskett@verizon.net>
References: <49AD9E55.6000804@iinet.net.au>	<20090304055639.GA25102@virgo.sdc.org>
	<49AE7E4C.2000806@comcast.net>
	<200903041053.07509.gene.heskett@verizon.net>
Message-ID: <49AEFE3A.3080201@iinet.net.au>

Gene Heskett wrote:

> Since the 16550 needs a 16 wide group of register addresses, which would 
> displace 4 regular packs from the coco's address space, I wonder how that was 
> handled?  

The 16550 only needs 8 bytes of addressing...

Regards,

-- 
|              Mark McDougall                | "Electrical Engineers do it
|  <http://members.iinet.net.au/~msmcdoug>   |   with less resistance!"


From cwgordon at carolina.rr.com  Wed Mar  4 17:21:41 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Wed, 4 Mar 2009 17:21:41 -0500
Subject: [Coco] Disk commands
Message-ID: <000001c99d17$983923e0$c8ab6ba0$@rr.com>

It's been SO long since I tinkered with a coco, I have forgotten nearly all
I knew. First, how do I backup up a disk? I cannot remember the command. 


______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From coconut at pritchard.ca  Wed Mar  4 17:27:48 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Wed, 4 Mar 2009 16:27:48 -0600
Subject: [Coco] Disk commands
In-Reply-To: <000001c99d17$983923e0$c8ab6ba0$@rr.com>
References: <000001c99d17$983923e0$c8ab6ba0$@rr.com>
Message-ID: <1806abd60903041427o3c524222ja6083f1ea58d1fa9@mail.gmail.com>

Hi Bill,

ftp://maltedmedia.com/coco/<ftp://maltedmedia.com/coco/MANUALS1/TANDY_HW/PAK/MULTIPAK>is
your friend.  You will find all sorts of goodies there including Disk
Basic manuals.

On Wed, Mar 4, 2009 at 4:21 PM, Bill <cwgordon at carolina.rr.com> wrote:

> It's been SO long since I tinkered with a coco, I have forgotten nearly all
> I knew. First, how do I backup up a disk? I cannot remember the command.
>
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From cwgordon at carolina.rr.com  Wed Mar  4 17:33:57 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Wed, 4 Mar 2009 17:33:57 -0500
Subject: [Coco] Disk commands
In-Reply-To: <1806abd60903041427o3c524222ja6083f1ea58d1fa9@mail.gmail.com>
References: <000001c99d17$983923e0$c8ab6ba0$@rr.com>
	<1806abd60903041427o3c524222ja6083f1ea58d1fa9@mail.gmail.com>
Message-ID: <000501c99d19$4ee518f0$ecaf4ad0$@rr.com>

DUH!! I had forgotten that. Thanks...

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Ryan Pritchard
> Sent: Wednesday, March 04, 2009 5:28 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Disk commands
> 
> Hi Bill,
> 
> ftp://maltedmedia.com/coco/<ftp://maltedmedia.com/coco/MANUALS1/TANDY_H
> W/PAK/MULTIPAK> is your friend.  You will find all sorts of goodies there
including Disk
> Basic manuals.



From t.fadden at cox.net  Wed Mar  4 17:41:19 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Wed, 04 Mar 2009 15:41:19 -0700
Subject: [Coco] '68' Micro Journal
In-Reply-To: <1806abd60903041413n4ccabf89va02dfffde5789dc0@mail.gmail.com>
References: <293588CE-36F5-4146-9EA5-859238ED2946@pritchard.ca>
	<1806abd60903041413n4ccabf89va02dfffde5789dc0@mail.gmail.com>
Message-ID: <49AF038F.6020309@cox.net>

So, whats your point?  You have four choices:

1. Don't do anything, and when you die some one will burn the magazines.
2. Sell them on ebay, and get rich?
3. Scan them without taking them apart, and spend a lot of your time.
4. Cut them apart, and get better/faster results.

The choice is yours, not ours.  I do understand you concerns. The only 
difference is. I already made up my mind for the Magazines I have. So 
far I got Rainbows 93 done, and am now working on 92

Tim

Ryan Pritchard wrote:
> So with all the activity lately with regards to magazine scanning on the
> list.  I am expecting that if these magazines were to be scanned there would
> be significant interest.
>
> My concerns:
> - Scanning takes a long time one page at a time.
> - Cutting the spine devalues the magazine (these are in very good
> condition), but makes the scanning go oh so much faster (plus I have access
> to an auto sheet feeder multi-purpose device, with selectable DPI.
>
> On Sun, Sep 28, 2008 at 2:47 PM, Ryan Pritchard <coconut at pritchard.ca>wrote:
>
>   
>> Hi all,
>>
>> I just went through a box in my basement.  This can be either a good or a
>> bad thing.  I today's case I would guess it is a good thing as the subject
>> of the posting may allude to.
>>
>> I have in my possession the following issues of '68' Micro Journal.
>>
>> Volume 1 all issues (1-9), though issues 1-3 are photo copies.
>> Volume 2 all 12 issues.
>> Volume 3 all 12 issues.
>> Volume 4 all 12 issues.
>> Volume 5 all 12 issues.
>> Volume 6 all 11 issues, volume 8 was an AUG/SEP issue.
>> Volume 7 all 12 issues.
>> Volume 8 all 12 issues.
>> Volume 9 all 12 issues.
>> Volume 10 all 12 issues.
>> Volume 11 issues 1-7, volume 6 was JUN/JUL, volume 7 was AUG/SEP.  Issue 1
>> from volume 12 indicated '68' Micro Journal did not publish in OCT/NOV/DEC.
>> Volume 12 issue 1, volume 1 was JAN/FEB.  (Is this all there was?  If so I
>> have a complete set of '68' Micro Journal originals, save the three
>> mentioned previously.
>>
>> I also currently have found the following issues in duplicate.
>> Volume 2, issue 10.
>> Volume 4, issues 3, 4, 7, 8.
>> Volume 5, issue 1.
>> Volume 11, issue 6.
>>
>> Regards,
>>
>> Ryan Pritchard
>> Fun Extends All Basic Life Expectancies
>>
>>
>>
>>
>>     
>
>
>   



From operator at coco3.com  Wed Mar  4 17:48:16 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 04 Mar 2009 16:48:16 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <200903041615.42740.gene.heskett@verizon.net>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A4@fenestra.lamunet.local>
	<200903041556.13849.gene.heskett@verizon.net>
	<200903041615.42740.gene.heskett@verizon.net>
Message-ID: <20090304224859.7076820A13@qs281.pair.com>

At 03:15 PM 3/4/2009, you wrote:
>On Wednesday 04 March 2009, Gene Heskett wrote:
> >On Wednesday 04 March 2009, Mike Pepe wrote:
> >>Roger,
>[...]
> >I haven't found a ush<->bluetooth gismo yet Roger but I'm still looking, I
> >need to get rid of the direct wire as mother nature has blown some usb
> >extension cabling already, and I can't think of a better way to get good
> >isolation than this pack of yours.
>PS:
>Just ordered 2 of these:
><http://www.usbgear.com/computer_cable_details.cfm?sku=USBG-
>BLUE-20&cats=158&catid=661%2C123%2C158>
>
>which are said to be class 1 devices.  Are they suitable? I figure I can put
>one on the laptop too.\


Yes, that one looks as good as any.  The IOGear dongle that Wal-Mart 
pushes it also good (I also have that one), but then I just plugged a 
$2.98 dongle into a new XP SP3 mini laptop and it worked right off, 
no driver CD or web searching.  I took the laptop out in the yard 
while my daughter typed on the CoCo in my office and she repeated 
back what I was typing, answered some silly questions, etc.  That's 
not what I call official testing but it was good for starters.  This 
is with a 115200 bps connection.  I repeat... this was a test of the 
cheap $2.98 dongle, not my pak.

Here is that particular dongle.   It came in QUICK and the shipping 
was free.  In other words, whoever this Hong Kong seller is, he's 
doing it for the numbers, not the profits.

http://cgi.ebay.com/100M-2-4G-USB-2-0-BLUETOOTH-DONGLE-V2-EDR-PC-ADAPTER_W0QQitemZ380108270824QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item380108270824&_trksid=p3286.c0.m14&_trkparms=72%3A1234|66%3A2|65%3A12|39%3A1|240%3A1308|301%3A1|293%3A1|294%3A50


-- 
Roger Taylor

http://www.wordofthedayonline.com



From operator at coco3.com  Wed Mar  4 17:49:43 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 04 Mar 2009 16:49:43 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <49AEFE3A.3080201@iinet.net.au>
References: <49AD9E55.6000804@iinet.net.au>
	<20090304055639.GA25102@virgo.sdc.org>
	<49AE7E4C.2000806@comcast.net>
	<200903041053.07509.gene.heskett@verizon.net>
	<49AEFE3A.3080201@iinet.net.au>
Message-ID: <20090304225029.8244520A13@qs281.pair.com>

At 04:18 PM 3/4/2009, you wrote:
>Gene Heskett wrote:
>
>>Since the 16550 needs a 16 wide group of register addresses, which 
>>would displace 4 regular packs from the coco's address space, I 
>>wonder how that was handled?
>
>The 16550 only needs 8 bytes of addressing...

ONLY 8 ?  Wow.  :)


-- 
Roger Taylor

http://www.wordofthedayonline.com



From coconut at pritchard.ca  Wed Mar  4 17:54:56 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Wed, 4 Mar 2009 16:54:56 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <20090304224859.7076820A13@qs281.pair.com>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A4@fenestra.lamunet.local>
	<200903041556.13849.gene.heskett@verizon.net>
	<200903041615.42740.gene.heskett@verizon.net>
	<20090304224859.7076820A13@qs281.pair.com>
Message-ID: <1806abd60903041454n3185a4ecgbc8304e015b99ec1@mail.gmail.com>

I presume you mean a test of the way cheap dongle on the PC communicating at
115200 bps with your serial BT adapter on the CoCo.

On Wed, Mar 4, 2009 at 4:48 PM, Roger Taylor <operator at coco3.com> wrote:

> At 03:15 PM 3/4/2009, you wrote:
>
>> On Wednesday 04 March 2009, Gene Heskett wrote:
>> >On Wednesday 04 March 2009, Mike Pepe wrote:
>> >>Roger,
>> [...]
>> >I haven't found a ush<->bluetooth gismo yet Roger but I'm still looking,
>> I
>> >need to get rid of the direct wire as mother nature has blown some usb
>> >extension cabling already, and I can't think of a better way to get good
>> >isolation than this pack of yours.
>> PS:
>> Just ordered 2 of these:
>> <http://www.usbgear.com/computer_cable_details.cfm?sku=USBG-
>> BLUE-20&cats=158&catid=661%2C123%2C158>
>>
>> which are said to be class 1 devices.  Are they suitable? I figure I can
>> put
>> one on the laptop too.\
>>
>
>
> Yes, that one looks as good as any.  The IOGear dongle that Wal-Mart pushes
> it also good (I also have that one), but then I just plugged a $2.98 dongle
> into a new XP SP3 mini laptop and it worked right off, no driver CD or web
> searching.  I took the laptop out in the yard while my daughter typed on the
> CoCo in my office and she repeated back what I was typing, answered some
> silly questions, etc.  That's not what I call official testing but it was
> good for starters.  This is with a 115200 bps connection.  I repeat... this
> was a test of the cheap $2.98 dongle, not my pak.
>
> Here is that particular dongle.   It came in QUICK and the shipping was
> free.  In other words, whoever this Hong Kong seller is, he's doing it for
> the numbers, not the profits.
>
>
> http://cgi.ebay.com/100M-2-4G-USB-2-0-BLUETOOTH-DONGLE-V2-EDR-PC-ADAPTER_W0QQitemZ380108270824QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item380108270824&_trksid=p3286.c0.m14&_trkparms=72%3A1234|66%3A2|65%3A12|39%3A1|240%3A1308|301%3A1|293%3A1|294%3A50<http://cgi.ebay.com/100M-2-4G-USB-2-0-BLUETOOTH-DONGLE-V2-EDR-PC-ADAPTER_W0QQitemZ380108270824QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item380108270824&_trksid=p3286.c0.m14&_trkparms=72%3A1234%7C66%3A2%7C65%3A12%7C39%3A1%7C240%3A1308%7C301%3A1%7C293%3A1%7C294%3A50>
>
>
> --
> Roger Taylor
>
> http://www.wordofthedayonline.com
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From lamune at doki-doki.net  Wed Mar  4 18:04:36 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Wed, 4 Mar 2009 15:04:36 -0800
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com><6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com><00a501c99c56$916e3850$0701a8c0@master><fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com><20090304060744.GC25102@virgo.sdc.org>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>

The second one is the better bet- it looks less likely to hit the
grounding ears of a pak like the disk controller or RS232

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com]
On Behalf Of Ryan Pritchard
Sent: Wednesday, March 04, 2009 12:45 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] Multi-Pak Interface question.

If I am correct either of these connectors should do the trick for board
mounting.

http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=EDC3414
02-ND

http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=EDC3954
02-ND

On Wed, Mar 4, 2009 at 12:07 AM, Willard Goosey
<goosey at virgo.sdc.org>wrote:

> On Tue, Mar 03, 2009 at 04:28:00PM -0800, Rick Taylor wrote:
> > Has anyone ever made Multi-Pak clones? Would it be legal to do so?
>
> I think every CoCo person who even pretends to be a hardware type has
> designed their own MPI.
>
> The trick is getting the connectors... :-(
>
> Willard
> --
> Willard Goosey  goosey at sdc.org
> Socorro, New Mexico, USA
> I search my heart and find Cimmeria, land of Darkness and the Night.
>  -- R.E. Howard
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



From tlindner at macmess.org  Wed Mar  4 18:07:04 2009
From: tlindner at macmess.org (tim lindner)
Date: Wed, 4 Mar 2009 15:07:04 -0800
Subject: [Coco] '68' Micro Journal
In-Reply-To: <1806abd60903041413n4ccabf89va02dfffde5789dc0@mail.gmail.com>
Message-ID: <1iw27ah.19xipcmiffapfM%tlindner@macmess.org>

Ryan Pritchard <coconut at pritchard.ca> wrote:

> I am expecting that if these magazines were to be scanned there would
> be significant interest.

They've already been scanned and made avaiable by the publisher.

-- 
tim lindner
tlindner at macmess.org                                              Bright



From t.fadden at cox.net  Wed Mar  4 17:43:40 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Wed, 04 Mar 2009 15:43:40 -0700
Subject: [Coco] Disk commands
In-Reply-To: <000001c99d17$983923e0$c8ab6ba0$@rr.com>
References: <000001c99d17$983923e0$c8ab6ba0$@rr.com>
Message-ID: <49AF041C.6000001@cox.net>

Bill, 

There are several sights with pdf documents of basic, and disk basic for 
the coco.  Google will show you.
RTFM
backup 0 to 1


Bill wrote:
> It's been SO long since I tinkered with a coco, I have forgotten nearly all
> I knew. First, how do I backup up a disk? I cannot remember the command. 
>
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From msmcdoug at iinet.net.au  Wed Mar  4 18:14:50 2009
From: msmcdoug at iinet.net.au (Mark McDougall)
Date: Thu, 05 Mar 2009 10:14:50 +1100
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <20090304225029.8244520A13@qs281.pair.com>
References: <49AD9E55.6000804@iinet.net.au>	<20090304055639.GA25102@virgo.sdc.org>	<49AE7E4C.2000806@comcast.net>	<200903041053.07509.gene.heskett@verizon.net>	<49AEFE3A.3080201@iinet.net.au>
	<20090304225029.8244520A13@qs281.pair.com>
Message-ID: <49AF0B6A.2090804@iinet.net.au>

Roger Taylor wrote:

> ONLY 8 ?  Wow.  :)

Heh, as opposed to 16.. :)

Regards,

-- 
|              Mark McDougall                | "Electrical Engineers do it
|  <http://members.iinet.net.au/~msmcdoug>   |   with less resistance!"


From operator at coco3.com  Wed Mar  4 18:17:21 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 04 Mar 2009 17:17:21 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <1269562842.183071236200148073.JavaMail.root@cl04-host03.ro
	ch.ny.frontiernet.net>
References: <334800648.181391236199895387.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<1269562842.183071236200148073.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <20090304231838.E12B820A16@qs281.pair.com>

At 02:55 PM 3/4/2009, you wrote:


>I have done both designs, The ACIA does work, just not well in 
>higher bandwidth situations due to the flow problems.

Using old software and old ways of thinking, this might be true for 
certain situations only, not all.



>  Thus my requirement. I am curious how you device is performing in 
> NitrOS-9. Do you have any test cases running there?

How well is NitrOS-9 tweaked to work with your stuff?


-- 
Roger Taylor

http://www.wordofthedayonline.com



From operator at coco3.com  Wed Mar  4 18:22:13 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 04 Mar 2009 17:22:13 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <1806abd60903041454n3185a4ecgbc8304e015b99ec1@mail.gmail.co
 m>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A4@fenestra.lamunet.local>
	<200903041556.13849.gene.heskett@verizon.net>
	<200903041615.42740.gene.heskett@verizon.net>
	<20090304224859.7076820A13@qs281.pair.com>
	<1806abd60903041454n3185a4ecgbc8304e015b99ec1@mail.gmail.com>
Message-ID: <20090304232240.4ECF220A13@qs281.pair.com>

At 04:54 PM 3/4/2009, you wrote:
>I presume you mean a test of the way cheap dongle on the PC communicating at
>115200 bps with your serial BT adapter on the CoCo.

Yes, that's the point.. a $2.98 dongle with a 100 meter range did the 
trick with the CoCo, but the same dongle connects to my IOGear dongle 
on the other laptop and carries all the neat protocols that the 
Windows bluetooth stack offers.  So, $2.98 vs $25 is the point I was making.

-- 
Roger Taylor

http://www.wordofthedayonline.com



From mmarlette at frontiernet.net  Wed Mar  4 18:25:17 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Wed, 4 Mar 2009 23:25:17 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <1660341785.230581236208909500.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <828685370.231941236209117917.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>


IDE/ATA is 8 as well......aaaaahhhhhhh :)


----- Original Message -----
From: "Mark McDougall" <msmcdoug at iinet.net.au>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 4, 2009 5:14:50 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

Roger Taylor wrote:

> ONLY 8 ?  Wow.  :)

Heh, as opposed to 16.. :)

Regards,

-- 
|              Mark McDougall                | "Electrical Engineers do it
|  <http://members.iinet.net.au/~msmcdoug>   |   with less resistance!"

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From devries.bob at gmail.com  Wed Mar  4 18:43:47 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Thu, 5 Mar 2009 09:43:47 +1000
Subject: [Coco] 16550 wasRe:  RS232 paks
References: <49AD9E55.6000804@iinet.net.au>	<20090304055639.GA25102@virgo.sdc.org>	<49AE7E4C.2000806@comcast.net>	<200903041053.07509.gene.heskett@verizon.net>	<49AEFE3A.3080201@iinet.net.au><20090304225029.8244520A13@qs281.pair.com>
	<49AF0B6A.2090804@iinet.net.au>
Message-ID: <007d01c99d23$13a052a0$0701a8c0@master>

I wonder if there's some software/hardware way to extend the I/O address 
range of the Coco in a similar way to the sideways ROM/RAM in the BBC 
computer?

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Mark McDougall" <msmcdoug at iinet.net.au>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, March 05, 2009 9:14 AM
Subject: Re: [Coco] 16550 wasRe: RS232 paks


> Roger Taylor wrote:
>
>> ONLY 8 ?  Wow.  :)
>
> Heh, as opposed to 16.. :)
>
> Regards,
>
> -- 
> |              Mark McDougall                | "Electrical Engineers do it
> |  <http://members.iinet.net.au/~msmcdoug>   |   with less resistance!"
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From georgeramsower at gmail.com  Wed Mar  4 18:51:29 2009
From: georgeramsower at gmail.com (George Ramsower)
Date: Wed, 4 Mar 2009 17:51:29 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net><379248463.77591236181220250.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<20090304194026.A8A8920A13@qs281.pair.com>
Message-ID: <005e01c99d24$24486ec0$6401a8c0@OLDGEORGE>

----- Original Message ----- 
From: "Roger Taylor"
> At 09:40 AM 3/4/2009, you wrote:
>>Willard,
>>
>>The NitrOS-9/Driver is already written for a 16550 device. I have had a 
>>homebrew card running for almost 10yrs based upon that chipset.
>>
>>Yes, it would break all the old term programs. A caveat of adding new 
>>technology to an old machine. Not a problem in NitrOS-9 as the driver/dd 
>>is not part of the actual program, when properly written.
>>
>>The SuperBoard has a multi-function chip on it that has the 16550 in it. 
>>Anyone that has done high speed serial testing in a system will design it 
>>with hardware handshaking. It is no secret that the ACIA(6551) has issues 
>>with this, plus almost no buffer space. Not a good choice for new designs, 
>>IMHO. 16xxx series offers GREAT buffers, programmable interrupt thresholds 
>>etc..... I guess that is why they are so common, oh they work too! :)
>>
>>Regards,
>>
>>Mark
>>Cloud-9
>
>
> Mark,
>
> Exactly what problems have you yourself had with the 6551 so that I may 
> try to offer a software solution?  I'm not claiming to have all the 
> answers, but I've done a serious amount of 6551 coding in the past, and I 
> can assure you that the chip itself is not always the problem.  The 
> programmer is 90% of the problem.  The OS is 90% of the problem.  If 
> there's some little bug or dislike about a certain chip, I guarantee that 
> there's the same number or more in the 16550.  I've read about that chip 
> and based on how many variants are floating around, how can anyone ever 
> agree on a right way to code the routines?  It appears to be a mess, no 
> less than what you claim about the 6551.  I'm not saying any certain chip 
> is BETTER than the other.. I'm saying that TOO many programmers and 
> nonprogrammers have clashed about these chips and in the end, they're all 
> still being used today.  You can always tell when the programmer took 
> shortcuts or just didn't know what he was doing.
>
> When you say the 6551 is not a wise choice for any new designs, your 
> intent is clear but the statement is not true.  Someone who's put out a 
> new wireless RS-232 pak didn't just wake up yesterday and discover the 
> 6551.  People who know how to write good software aren't afraid of the 
> 6551.
>
> My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo 1's, 1 
> CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy looping 
> tests (1-2 days sometimes), and I haven't seen it bomb out yet.  Can you 
> please tell me what circumstances I need in order to break my protocol ?

 I'm not a guru on all this but, it seems to me that if there was a bug in 
the original 6551, over the years it's been produced and cloned that 
somewhere, someone would have fixed it.
 I think Roger may be correct inasmuch that programming may have been the 
problem... although I don't know. It just seems that way because the darned 
chip would have been fixed by now.
 I'm happy with my 6551 chips in my (OS9) coco. I'm not using Nitros9 so it 
would naturally be a little slower but, I've done megs of transfers without 
incident..... I think.



From gene.heskett at verizon.net  Wed Mar  4 19:04:30 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 19:04:30 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <49AEFE3A.3080201@iinet.net.au>
References: <49AD9E55.6000804@iinet.net.au>
	<200903041053.07509.gene.heskett@verizon.net>
	<49AEFE3A.3080201@iinet.net.au>
Message-ID: <200903041904.30740.gene.heskett@verizon.net>

On Wednesday 04 March 2009, Mark McDougall wrote:
>Gene Heskett wrote:
>> Since the 16550 needs a 16 wide group of register addresses, which would
>> displace 4 regular packs from the coco's address space, I wonder how that
>> was handled?
>
>The 16550 only needs 8 bytes of addressing...
>
Hmm, I was in this case parroting what some else said, probably a decade back.

And while that is good news, it still needs more space that a 6551.  OTOH, 
does not this 8 bytes more or less give us a dual serial port?  Most such 
chips as used in the pc's back then are duals at heart.  If so, that would 
equal out rather nicely.  Now days, the common Superio chipset has duals in it 
even if not bonded out.  Here, I can find a ttyS1, but I believe the only 
hardware actually installed is ttyS0, and it is called an 8250 by linux.

>Regards,


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My parents went to Niagara Falls and all I got was this crummy life.



From afra at aurigae.demon.co.uk  Wed Mar  4 19:08:30 2009
From: afra at aurigae.demon.co.uk (Phill Harvey-Smith)
Date: Thu, 05 Mar 2009 00:08:30 +0000
Subject: [Coco]  Paged RAM/ROM (was 16550/rs232).
In-Reply-To: <007d01c99d23$13a052a0$0701a8c0@master>
References: <49AD9E55.6000804@iinet.net.au>	<20090304055639.GA25102@virgo.sdc.org>	<49AE7E4C.2000806@comcast.net>	<200903041053.07509.gene.heskett@verizon.net>	<49AEFE3A.3080201@iinet.net.au><20090304225029.8244520A13@qs281.pair.com>	<49AF0B6A.2090804@iinet.net.au>
	<007d01c99d23$13a052a0$0701a8c0@master>
Message-ID: <49AF17FE.9070204@aurigae.demon.co.uk>

Bob Devries wrote:
> I wonder if there's some software/hardware way to extend the I/O address 
> range of the Coco in a similar way to the sideways ROM/RAM in the BBC 
> computer?

Yeah that's pretty easy to implement, there's no magic really, the BBC's 
  sideways memory's just paged RAM/ROM.

The CoCo 3 already implements this, through the task registers, it would 
be trickier on a CoCo 1/2 or a Dragon because the SAM address decoding 
would get in the way, so you'd have to asert device select disable (cart 
pin 40), and manually decode the addresses.

But it's still easily doable, with the restriction that the 6847 has to 
take it's data from the normal RAM.

If you're prepared to also decode the multiplexed addresses from the SAM 
then there's no reason why you couldn't implement fully paged banks of 
memory on the CoCo/Dragon machines as the CoCo3 has. It's actually 
something I started working on, and got as far as emulating the Dragon 
Plus addon, giving me a total of 128K of ram (from a 1M 30 pin SIMM).

The real problem is not one of hardware but software, the BBC computers 
have OS support for paged ROMS, so it's easy to implement addon firmware 
in sideways memory and as long as you obey the rules it all works even 
with other software in sideways memory. It would be hard to retr-fit 
that to Basic on the CoCo, as there's already so much out there that 
would not conform to this.

For OS-9/Nitros of course this is not a problem, as long as the kernel 
knows how to deal with the paging (as it does on the CoCo3).

Cheers.

Phill.

-- 
Phill Harvey-Smith, Programmer, Hardware hacker, and general eccentric !

"You can twist perceptions, but reality won't budge" -- Rush.


From gene.heskett at verizon.net  Wed Mar  4 19:08:16 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 19:08:16 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <20090304224859.7076820A13@qs281.pair.com>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<200903041615.42740.gene.heskett@verizon.net>
	<20090304224859.7076820A13@qs281.pair.com>
Message-ID: <200903041908.16945.gene.heskett@verizon.net>

On Wednesday 04 March 2009, Roger Taylor wrote:
>At 03:15 PM 3/4/2009, you wrote:
>>On Wednesday 04 March 2009, Gene Heskett wrote:
>> >On Wednesday 04 March 2009, Mike Pepe wrote:
>> >>Roger,
>>
>>[...]
>>
>> >I haven't found a ush<->bluetooth gismo yet Roger but I'm still looking,
>> > I need to get rid of the direct wire as mother nature has blown some usb
>> > extension cabling already, and I can't think of a better way to get good
>> > isolation than this pack of yours.
>>
>>PS:
>>Just ordered 2 of these:
>><http://www.usbgear.com/computer_cable_details.cfm?sku=USBG-
>>BLUE-20&cats=158&catid=661%2C123%2C158>
>>
>>which are said to be class 1 devices.  Are they suitable? I figure I can
>> put one on the laptop too.\
>
>Yes, that one looks as good as any.  The IOGear dongle that Wal-Mart
>pushes it also good (I also have that one), but then I just plugged a
>$2.98 dongle into a new XP SP3 mini laptop and it worked right off,
>no driver CD or web searching.  I took the laptop out in the yard
>while my daughter typed on the CoCo in my office and she repeated
>back what I was typing, answered some silly questions, etc.  That's
>not what I call official testing but it was good for starters.  This
>is with a 115200 bps connection.  I repeat... this was a test of the
>cheap $2.98 dongle, not my pak.
>
>Here is that particular dongle.   It came in QUICK and the shipping
>was free.  In other words, whoever this Hong Kong seller is, he's
>doing it for the numbers, not the profits.
>
>http://cgi.ebay.com/100M-2-4G-USB-2-0-BLUETOOTH-DONGLE-V2-EDR-PC-ADAPTER_W0Q
>QitemZ380108270824QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item38010827082
>4&_trksid=p3286.c0.m14&_trkparms=72%3A1234|66%3A2|65%3A12|39%3A1|240%3A1308|
>301%3A1|293%3A1|294%3A50

Humm, wish I had known that, but these are already ordered.  Sigh.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Jayne: "... and if wishes were horses we'd all be eating steak!"
				--Episode #14, "Objects in Space"



From mmarlette at frontiernet.net  Wed Mar  4 19:13:32 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Thu, 5 Mar 2009 00:13:32 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <1206785309.241111236211178532.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <2120297497.244951236212012329.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

George,

Google a bit and you will see, it is a wonderful tool.

Maybe you will believe our own SockMaster on the subject.......

http://www.axess.com/twilight/sock/cocofile/rs232mod.txt

This is an extraction from his article from :

   Now for what IS in the diagram:  The other problem with putting a high-speed
modem on my BBS is a little less important,  but fixing it makes everything
much easier.  With this modification the CPU gets less bogged down, the RS-232
driver becomes easier to write, and the BBS *never* misses any incoming data.
Normally, the 6551 simply has no way of telling my modem when it's data buffer
is full.  If someone called my BBS at a high baud rate and tried uploading a
text file, my driver simply didn't read the data fast enough to get it all
without missing bytes. Every time the disk drive went on, the CPU halts and the
6551 misses more data.  In order not to miss data, the RS-232 driver would have
to immediately read data from the 6551 every time a byte came in.  The
solution?  I made a little circuit that sits on top of the 6551 chip (a 74ls32
and 74ls00) that generates a new RTS control signal.  Since modern modems have
a data buffer, it would be really neat to unload a lot of work from the CoCo
and leave it for the modem to do.  This hardware circuit simply creates a new
RTS line for the 6551.  Every time the 6551 receives data, the circuit raises
the RTS line (which tells the modem to stop sending to the CoCo) until that
data is read by the software.  If the driver reads the data at the full
incoming speed, there is no slowdown in throughput.  If the driver goes on a
break, or the disk drive comes into use... whatever, the modem is told not to
send any more data to the 6551 until the 6551 is ready to recieve it!
Effectively, the circuit disallows the 6551 from missing any data.  It also
places the job of buffering incoming data on the modem, and not the CoCo.
The CoCo doesn't have to keep reading the 6551 every time a byte comes in,
since it won't lose the data if it lets it wait.  Now it can read the data
when it actually wants it.  This speeds up my BBS quite a bit,  I only read
from  the 6551 when the BBS wants input from the user.  If the user transmits
stuff while the BBS is calculating, loading, thinking, etc... the modem will
buffer it for me.


Regards,

Mark
Cloud-9
----- Original Message -----
From: "George Ramsower" <georgeramsower at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 4, 2009 5:51:29 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

----- Original Message ----- 
From: "Roger Taylor"
> At 09:40 AM 3/4/2009, you wrote:
>>Willard,
>>
>>The NitrOS-9/Driver is already written for a 16550 device. I have had a 
>>homebrew card running for almost 10yrs based upon that chipset.
>>
>>Yes, it would break all the old term programs. A caveat of adding new 
>>technology to an old machine. Not a problem in NitrOS-9 as the driver/dd 
>>is not part of the actual program, when properly written.
>>
>>The SuperBoard has a multi-function chip on it that has the 16550 in it. 
>>Anyone that has done high speed serial testing in a system will design it 
>>with hardware handshaking. It is no secret that the ACIA(6551) has issues 
>>with this, plus almost no buffer space. Not a good choice for new designs, 
>>IMHO. 16xxx series offers GREAT buffers, programmable interrupt thresholds 
>>etc..... I guess that is why they are so common, oh they work too! :)
>>
>>Regards,
>>
>>Mark
>>Cloud-9
>
>
> Mark,
>
> Exactly what problems have you yourself had with the 6551 so that I may 
> try to offer a software solution?  I'm not claiming to have all the 
> answers, but I've done a serious amount of 6551 coding in the past, and I 
> can assure you that the chip itself is not always the problem.  The 
> programmer is 90% of the problem.  The OS is 90% of the problem.  If 
> there's some little bug or dislike about a certain chip, I guarantee that 
> there's the same number or more in the 16550.  I've read about that chip 
> and based on how many variants are floating around, how can anyone ever 
> agree on a right way to code the routines?  It appears to be a mess, no 
> less than what you claim about the 6551.  I'm not saying any certain chip 
> is BETTER than the other.. I'm saying that TOO many programmers and 
> nonprogrammers have clashed about these chips and in the end, they're all 
> still being used today.  You can always tell when the programmer took 
> shortcuts or just didn't know what he was doing.
>
> When you say the 6551 is not a wise choice for any new designs, your 
> intent is clear but the statement is not true.  Someone who's put out a 
> new wireless RS-232 pak didn't just wake up yesterday and discover the 
> 6551.  People who know how to write good software aren't afraid of the 
> 6551.
>
> My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo 1's, 1 
> CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy looping 
> tests (1-2 days sometimes), and I haven't seen it bomb out yet.  Can you 
> please tell me what circumstances I need in order to break my protocol ?

 I'm not a guru on all this but, it seems to me that if there was a bug in 
the original 6551, over the years it's been produced and cloned that 
somewhere, someone would have fixed it.
 I think Roger may be correct inasmuch that programming may have been the 
problem... although I don't know. It just seems that way because the darned 
chip would have been fixed by now.
 I'm happy with my 6551 chips in my (OS9) coco. I'm not using Nitros9 so it 
would naturally be a little slower but, I've done megs of transfers without 
incident..... I think.


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From mechacoco at gmail.com  Wed Mar  4 19:29:45 2009
From: mechacoco at gmail.com (Darren A)
Date: Wed, 4 Mar 2009 17:29:45 -0700
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <005e01c99d24$24486ec0$6401a8c0@OLDGEORGE>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<379248463.77591236181220250.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<20090304194026.A8A8920A13@qs281.pair.com>
	<005e01c99d24$24486ec0$6401a8c0@OLDGEORGE>
Message-ID: <5d802cd0903041629v1707a74clb50b2e2741bbbf@mail.gmail.com>

On 3/4/09, George Ramsower wrote:
>
>  I'm not a guru on all this but, it seems to me that if there was a bug in
> the original 6551, over the years it's been produced and cloned that
> somewhere, someone would have fixed it.

--

The problem is that they apparently didn't consider it to be a bug,
since the behavior is actually documented in the datasheet.

The datasheet for the updated version of the 6551 produced by The
Western Design Center inidcates a change to this behavior.
Unfortunately, their chip has many other problems that have yet to be
worked out.

Darren


From mmarlette at frontiernet.net  Wed Mar  4 19:34:53 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Thu, 5 Mar 2009 00:34:53 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <1058935473.250331236212905573.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <2102867535.251961236213293264.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

Roger,

Tweaked, none. 

Randy Wilson wrote the driver for it. This was done MANY years ago. I helped him test it. A properly written driver will work in all conditions.

Rick U. of Conect, I did work with him on the tail end of his business and have most of what he had done.

I test my products in the worst case environment. If It works there then it will work in a normal one.

I see you missed some of my questions, after you asked for my input. If you were sincere with your request as I was, you will address my questions. I'll put them below again in smaller broke out of the paragraphs for your ease of response. I re-addressed the first question as it was more of a statement on my part that I thought you would addressed.

Again I ask you. 

Are you hardware handshaking with your device?

Do you have a test case under NitrOS-9?

Please expand in detail if you wish.

Regards,

Mark
Cloud-9


----- Original Message -----
From: "Roger Taylor" <operator at coco3.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 4, 2009 5:17:21 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

At 02:55 PM 3/4/2009, you wrote:


>I have done both designs, The ACIA does work, just not well in 
>higher bandwidth situations due to the flow problems.

Using old software and old ways of thinking, this might be true for 
certain situations only, not all.



>  Thus my requirement. I am curious how you device is performing in 
> NitrOS-9. Do you have any test cases running there?

How well is NitrOS-9 tweaked to work with your stuff?


-- 
Roger Taylor

http://www.wordofthedayonline.com


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From mmarlette at frontiernet.net  Wed Mar  4 19:43:24 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Thu, 5 Mar 2009 00:43:24 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <509601205.253311236213680362.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <1572219371.253831236213804374.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

Bob,

Probably but there is space in the map for larger devices and without stepping on the legacy ones.

SuperBoard has a dual port 16550, plus a bidirectional parallel port  on it. So that would be 16 IO bytes for the ACEs, not a problem and doesn't step on anything.

Regards,

Mark
Cloud-9

----- Original Message -----
From: "Bob Devries" <devries.bob at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 4, 2009 5:43:47 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

I wonder if there's some software/hardware way to extend the I/O address 
range of the Coco in a similar way to the sideways ROM/RAM in the BBC 
computer?

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Mark McDougall" <msmcdoug at iinet.net.au>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, March 05, 2009 9:14 AM
Subject: Re: [Coco] 16550 wasRe: RS232 paks


> Roger Taylor wrote:
>
>> ONLY 8 ?  Wow.  :)
>
> Heh, as opposed to 16.. :)
>
> Regards,
>
> -- 
> |              Mark McDougall                | "Electrical Engineers do it
> |  <http://members.iinet.net.au/~msmcdoug>   |   with less resistance!"
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From georgeramsower at gmail.com  Wed Mar  4 20:19:25 2009
From: georgeramsower at gmail.com (George Ramsower)
Date: Wed, 4 Mar 2009 19:19:25 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
References: <2120297497.244951236212012329.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <009e01c99d30$6ce5a470$6401a8c0@OLDGEORGE>

hmm.
 I think I'll have to find some time and see how I built that 3 port com 
board. It works goodly. I'm wondering if I made those changes to the 
intended design.
 All I know now is that it works. I ran two modems on two different 
telephone exchanges and it eliminated long distance charges from one to the 
other. I was lucky enough to be in the middle and didn't have to pay between 
them.
 This was the old way to do BBS systems to avoid long distance charges. I 
didn't join a network and therefore, I was not a hub.
 "Hub" was that what it was called? Dammit, I can't remember.

George

----- Original Message ----- 
From: "Mark Marlette"
> George,
>
> Google a bit and you will see, it is a wonderful tool.
>
> Maybe you will believe our own SockMaster on the subject.......
>
> http://www.axess.com/twilight/sock/cocofile/rs232mod.txt
>
> This is an extraction from his article from :
>
>   Now for what IS in the diagram:  The other problem with putting a 
> high-speed
> modem on my BBS is a little less important,  but fixing it makes 
> everything
> much easier.  With this modification the CPU gets less bogged down, the 
> RS-232
> driver becomes easier to write, and the BBS *never* misses any incoming 
> data.
> Normally, the 6551 simply has no way of telling my modem when it's data 
> buffer
> is full.  If someone called my BBS at a high baud rate and tried uploading 
> a
> text file, my driver simply didn't read the data fast enough to get it all
> without missing bytes. Every time the disk drive went on, the CPU halts 
> and the
> 6551 misses more data.  In order not to miss data, the RS-232 driver would 
> have
> to immediately read data from the 6551 every time a byte came in.  The
> solution?  I made a little circuit that sits on top of the 6551 chip (a 
> 74ls32
> and 74ls00) that generates a new RTS control signal.  Since modern modems 
> have
> a data buffer, it would be really neat to unload a lot of work from the 
> CoCo
> and leave it for the modem to do.  This hardware circuit simply creates a 
> new
> RTS line for the 6551.  Every time the 6551 receives data, the circuit 
> raises
> the RTS line (which tells the modem to stop sending to the CoCo) until 
> that
> data is read by the software.  If the driver reads the data at the full
> incoming speed, there is no slowdown in throughput.  If the driver goes on 
> a
> break, or the disk drive comes into use... whatever, the modem is told not 
> to
> send any more data to the 6551 until the 6551 is ready to recieve it!
> Effectively, the circuit disallows the 6551 from missing any data.  It 
> also
> places the job of buffering incoming data on the modem, and not the CoCo.
> The CoCo doesn't have to keep reading the 6551 every time a byte comes in,
> since it won't lose the data if it lets it wait.  Now it can read the data
> when it actually wants it.  This speeds up my BBS quite a bit,  I only 
> read
> from  the 6551 when the BBS wants input from the user.  If the user 
> transmits
> stuff while the BBS is calculating, loading, thinking, etc... the modem 
> will
> buffer it for me.
>
>
> Regards,
>
> Mark
> Cloud-9
> ----- Original Message -----
> From: "George Ramsower"
> ----- Original Message ----- 
> From: "Roger Taylor"
>> At 09:40 AM 3/4/2009, you wrote:
>>>Willard,
>>>
>>>The NitrOS-9/Driver is already written for a 16550 device. I have had a
>>>homebrew card running for almost 10yrs based upon that chipset.
>>>
>>>Yes, it would break all the old term programs. A caveat of adding new
>>>technology to an old machine. Not a problem in NitrOS-9 as the driver/dd
>>>is not part of the actual program, when properly written.
>>>
>>>The SuperBoard has a multi-function chip on it that has the 16550 in it.
>>>Anyone that has done high speed serial testing in a system will design it
>>>with hardware handshaking. It is no secret that the ACIA(6551) has issues
>>>with this, plus almost no buffer space. Not a good choice for new 
>>>designs,
>>>IMHO. 16xxx series offers GREAT buffers, programmable interrupt 
>>>thresholds
>>>etc..... I guess that is why they are so common, oh they work too! :)
>>>
>>>Regards,
>>>
>>>Mark
>>>Cloud-9
>>
>>
>> Mark,
>>
>> Exactly what problems have you yourself had with the 6551 so that I may
>> try to offer a software solution?  I'm not claiming to have all the
>> answers, but I've done a serious amount of 6551 coding in the past, and I
>> can assure you that the chip itself is not always the problem.  The
>> programmer is 90% of the problem.  The OS is 90% of the problem.  If
>> there's some little bug or dislike about a certain chip, I guarantee that
>> there's the same number or more in the 16550.  I've read about that chip
>> and based on how many variants are floating around, how can anyone ever
>> agree on a right way to code the routines?  It appears to be a mess, no
>> less than what you claim about the 6551.  I'm not saying any certain chip
>> is BETTER than the other.. I'm saying that TOO many programmers and
>> nonprogrammers have clashed about these chips and in the end, they're all
>> still being used today.  You can always tell when the programmer took
>> shortcuts or just didn't know what he was doing.
>>
>> When you say the 6551 is not a wise choice for any new designs, your
>> intent is clear but the statement is not true.  Someone who's put out a
>> new wireless RS-232 pak didn't just wake up yesterday and discover the
>> 6551.  People who know how to write good software aren't afraid of the
>> 6551.
>>
>> My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo 1's, 1
>> CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy looping
>> tests (1-2 days sometimes), and I haven't seen it bomb out yet.  Can you
>> please tell me what circumstances I need in order to break my protocol ?
>
> I'm not a guru on all this but, it seems to me that if there was a bug in
> the original 6551, over the years it's been produced and cloned that
> somewhere, someone would have fixed it.
> I think Roger may be correct inasmuch that programming may have been the
> problem... although I don't know. It just seems that way because the 
> darned
> chip would have been fixed by now.
> I'm happy with my 6551 chips in my (OS9) coco. I'm not using Nitros9 so it
> would naturally be a little slower but, I've done megs of transfers 
> without
> incident..... I think.




From mmarlette at frontiernet.net  Wed Mar  4 20:28:42 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Thu, 5 Mar 2009 01:28:42 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <009e01c99d30$6ce5a470$6401a8c0@OLDGEORGE>
Message-ID: <534074304.264771236216522902.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

George,

Do not forget that the chip does work. It just doesn't work in all conditions.

If it didn't work they wouldn't sell it.

In your application is obviously is working for you. I have stated the conditions, SockMaster did as well. It will fall flat on it's face.

'For a Few Dollars More', you can have the real deal. Problem is that the 16550 will not support the legacy term programs for the CoCo, there are all kinds of issues that we deal with when adding technology to an old computer. It is way more work to implement but that is why it is on the SB. Can't have lost data, ever.

Clint Eastwood fans will get my movie title above.... :)

Regards,

Mark


----- Original Message -----
From: "George Ramsower" <georgeramsower at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 4, 2009 7:19:25 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

hmm.
 I think I'll have to find some time and see how I built that 3 port com 
board. It works goodly. I'm wondering if I made those changes to the 
intended design.
 All I know now is that it works. I ran two modems on two different 
telephone exchanges and it eliminated long distance charges from one to the 
other. I was lucky enough to be in the middle and didn't have to pay between 
them.
 This was the old way to do BBS systems to avoid long distance charges. I 
didn't join a network and therefore, I was not a hub.
 "Hub" was that what it was called? Dammit, I can't remember.

George

----- Original Message ----- 
From: "Mark Marlette"
> George,
>
> Google a bit and you will see, it is a wonderful tool.
>
> Maybe you will believe our own SockMaster on the subject.......
>
> http://www.axess.com/twilight/sock/cocofile/rs232mod.txt
>
> This is an extraction from his article from :
>
>   Now for what IS in the diagram:  The other problem with putting a 
> high-speed
> modem on my BBS is a little less important,  but fixing it makes 
> everything
> much easier.  With this modification the CPU gets less bogged down, the 
> RS-232
> driver becomes easier to write, and the BBS *never* misses any incoming 
> data.
> Normally, the 6551 simply has no way of telling my modem when it's data 
> buffer
> is full.  If someone called my BBS at a high baud rate and tried uploading 
> a
> text file, my driver simply didn't read the data fast enough to get it all
> without missing bytes. Every time the disk drive went on, the CPU halts 
> and the
> 6551 misses more data.  In order not to miss data, the RS-232 driver would 
> have
> to immediately read data from the 6551 every time a byte came in.  The
> solution?  I made a little circuit that sits on top of the 6551 chip (a 
> 74ls32
> and 74ls00) that generates a new RTS control signal.  Since modern modems 
> have
> a data buffer, it would be really neat to unload a lot of work from the 
> CoCo
> and leave it for the modem to do.  This hardware circuit simply creates a 
> new
> RTS line for the 6551.  Every time the 6551 receives data, the circuit 
> raises
> the RTS line (which tells the modem to stop sending to the CoCo) until 
> that
> data is read by the software.  If the driver reads the data at the full
> incoming speed, there is no slowdown in throughput.  If the driver goes on 
> a
> break, or the disk drive comes into use... whatever, the modem is told not 
> to
> send any more data to the 6551 until the 6551 is ready to recieve it!
> Effectively, the circuit disallows the 6551 from missing any data.  It 
> also
> places the job of buffering incoming data on the modem, and not the CoCo.
> The CoCo doesn't have to keep reading the 6551 every time a byte comes in,
> since it won't lose the data if it lets it wait.  Now it can read the data
> when it actually wants it.  This speeds up my BBS quite a bit,  I only 
> read
> from  the 6551 when the BBS wants input from the user.  If the user 
> transmits
> stuff while the BBS is calculating, loading, thinking, etc... the modem 
> will
> buffer it for me.
>
>
> Regards,
>
> Mark
> Cloud-9
> ----- Original Message -----
> From: "George Ramsower"
> ----- Original Message ----- 
> From: "Roger Taylor"
>> At 09:40 AM 3/4/2009, you wrote:
>>>Willard,
>>>
>>>The NitrOS-9/Driver is already written for a 16550 device. I have had a
>>>homebrew card running for almost 10yrs based upon that chipset.
>>>
>>>Yes, it would break all the old term programs. A caveat of adding new
>>>technology to an old machine. Not a problem in NitrOS-9 as the driver/dd
>>>is not part of the actual program, when properly written.
>>>
>>>The SuperBoard has a multi-function chip on it that has the 16550 in it.
>>>Anyone that has done high speed serial testing in a system will design it
>>>with hardware handshaking. It is no secret that the ACIA(6551) has issues
>>>with this, plus almost no buffer space. Not a good choice for new 
>>>designs,
>>>IMHO. 16xxx series offers GREAT buffers, programmable interrupt 
>>>thresholds
>>>etc..... I guess that is why they are so common, oh they work too! :)
>>>
>>>Regards,
>>>
>>>Mark
>>>Cloud-9
>>
>>
>> Mark,
>>
>> Exactly what problems have you yourself had with the 6551 so that I may
>> try to offer a software solution?  I'm not claiming to have all the
>> answers, but I've done a serious amount of 6551 coding in the past, and I
>> can assure you that the chip itself is not always the problem.  The
>> programmer is 90% of the problem.  The OS is 90% of the problem.  If
>> there's some little bug or dislike about a certain chip, I guarantee that
>> there's the same number or more in the 16550.  I've read about that chip
>> and based on how many variants are floating around, how can anyone ever
>> agree on a right way to code the routines?  It appears to be a mess, no
>> less than what you claim about the 6551.  I'm not saying any certain chip
>> is BETTER than the other.. I'm saying that TOO many programmers and
>> nonprogrammers have clashed about these chips and in the end, they're all
>> still being used today.  You can always tell when the programmer took
>> shortcuts or just didn't know what he was doing.
>>
>> When you say the 6551 is not a wise choice for any new designs, your
>> intent is clear but the statement is not true.  Someone who's put out a
>> new wireless RS-232 pak didn't just wake up yesterday and discover the
>> 6551.  People who know how to write good software aren't afraid of the
>> 6551.
>>
>> My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo 1's, 1
>> CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy looping
>> tests (1-2 days sometimes), and I haven't seen it bomb out yet.  Can you
>> please tell me what circumstances I need in order to break my protocol ?
>
> I'm not a guru on all this but, it seems to me that if there was a bug in
> the original 6551, over the years it's been produced and cloned that
> somewhere, someone would have fixed it.
> I think Roger may be correct inasmuch that programming may have been the
> problem... although I don't know. It just seems that way because the 
> darned
> chip would have been fixed by now.
> I'm happy with my 6551 chips in my (OS9) coco. I'm not using Nitros9 so it
> would naturally be a little slower but, I've done megs of transfers 
> without
> incident..... I think.



--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From tjseagrove at writeme.com  Wed Mar  4 20:31:15 2009
From: tjseagrove at writeme.com (Tom Seagrove)
Date: Wed, 4 Mar 2009 20:31:15 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <534074304.264771236216522902.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
References: <009e01c99d30$6ce5a470$6401a8c0@OLDGEORGE>
	<534074304.264771236216522902.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <00aa01c99d32$15647300$402d5900$@com>

Fist Full of Dollars?

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
Behalf Of Mark Marlette
Sent: Wednesday, March 04, 2009 8:29 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] 16550 wasRe: RS232 paks

George,

Do not forget that the chip does work. It just doesn't work in all
conditions.

If it didn't work they wouldn't sell it.

In your application is obviously is working for you. I have stated the
conditions, SockMaster did as well. It will fall flat on it's face.

'For a Few Dollars More', you can have the real deal. Problem is that the
16550 will not support the legacy term programs for the CoCo, there are all
kinds of issues that we deal with when adding technology to an old computer.
It is way more work to implement but that is why it is on the SB. Can't have
lost data, ever.

Clint Eastwood fans will get my movie title above.... :)

Regards,

Mark


----- Original Message -----
From: "George Ramsower" <georgeramsower at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 4, 2009 7:19:25 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

hmm.
 I think I'll have to find some time and see how I built that 3 port com 
board. It works goodly. I'm wondering if I made those changes to the 
intended design.
 All I know now is that it works. I ran two modems on two different 
telephone exchanges and it eliminated long distance charges from one to the 
other. I was lucky enough to be in the middle and didn't have to pay between

them.
 This was the old way to do BBS systems to avoid long distance charges. I 
didn't join a network and therefore, I was not a hub.
 "Hub" was that what it was called? Dammit, I can't remember.

George

----- Original Message ----- 
From: "Mark Marlette"
> George,
>
> Google a bit and you will see, it is a wonderful tool.
>
> Maybe you will believe our own SockMaster on the subject.......
>
> http://www.axess.com/twilight/sock/cocofile/rs232mod.txt
>
> This is an extraction from his article from :
>
>   Now for what IS in the diagram:  The other problem with putting a 
> high-speed
> modem on my BBS is a little less important,  but fixing it makes 
> everything
> much easier.  With this modification the CPU gets less bogged down, the 
> RS-232
> driver becomes easier to write, and the BBS *never* misses any incoming 
> data.
> Normally, the 6551 simply has no way of telling my modem when it's data 
> buffer
> is full.  If someone called my BBS at a high baud rate and tried uploading

> a
> text file, my driver simply didn't read the data fast enough to get it all
> without missing bytes. Every time the disk drive went on, the CPU halts 
> and the
> 6551 misses more data.  In order not to miss data, the RS-232 driver would

> have
> to immediately read data from the 6551 every time a byte came in.  The
> solution?  I made a little circuit that sits on top of the 6551 chip (a 
> 74ls32
> and 74ls00) that generates a new RTS control signal.  Since modern modems 
> have
> a data buffer, it would be really neat to unload a lot of work from the 
> CoCo
> and leave it for the modem to do.  This hardware circuit simply creates a 
> new
> RTS line for the 6551.  Every time the 6551 receives data, the circuit 
> raises
> the RTS line (which tells the modem to stop sending to the CoCo) until 
> that
> data is read by the software.  If the driver reads the data at the full
> incoming speed, there is no slowdown in throughput.  If the driver goes on

> a
> break, or the disk drive comes into use... whatever, the modem is told not

> to
> send any more data to the 6551 until the 6551 is ready to recieve it!
> Effectively, the circuit disallows the 6551 from missing any data.  It 
> also
> places the job of buffering incoming data on the modem, and not the CoCo.
> The CoCo doesn't have to keep reading the 6551 every time a byte comes in,
> since it won't lose the data if it lets it wait.  Now it can read the data
> when it actually wants it.  This speeds up my BBS quite a bit,  I only 
> read
> from  the 6551 when the BBS wants input from the user.  If the user 
> transmits
> stuff while the BBS is calculating, loading, thinking, etc... the modem 
> will
> buffer it for me.
>
>
> Regards,
>
> Mark
> Cloud-9
> ----- Original Message -----
> From: "George Ramsower"
> ----- Original Message ----- 
> From: "Roger Taylor"
>> At 09:40 AM 3/4/2009, you wrote:
>>>Willard,
>>>
>>>The NitrOS-9/Driver is already written for a 16550 device. I have had a
>>>homebrew card running for almost 10yrs based upon that chipset.
>>>
>>>Yes, it would break all the old term programs. A caveat of adding new
>>>technology to an old machine. Not a problem in NitrOS-9 as the driver/dd
>>>is not part of the actual program, when properly written.
>>>
>>>The SuperBoard has a multi-function chip on it that has the 16550 in it.
>>>Anyone that has done high speed serial testing in a system will design it
>>>with hardware handshaking. It is no secret that the ACIA(6551) has issues
>>>with this, plus almost no buffer space. Not a good choice for new 
>>>designs,
>>>IMHO. 16xxx series offers GREAT buffers, programmable interrupt 
>>>thresholds
>>>etc..... I guess that is why they are so common, oh they work too! :)
>>>
>>>Regards,
>>>
>>>Mark
>>>Cloud-9
>>
>>
>> Mark,
>>
>> Exactly what problems have you yourself had with the 6551 so that I may
>> try to offer a software solution?  I'm not claiming to have all the
>> answers, but I've done a serious amount of 6551 coding in the past, and I
>> can assure you that the chip itself is not always the problem.  The
>> programmer is 90% of the problem.  The OS is 90% of the problem.  If
>> there's some little bug or dislike about a certain chip, I guarantee that
>> there's the same number or more in the 16550.  I've read about that chip
>> and based on how many variants are floating around, how can anyone ever
>> agree on a right way to code the routines?  It appears to be a mess, no
>> less than what you claim about the 6551.  I'm not saying any certain chip
>> is BETTER than the other.. I'm saying that TOO many programmers and
>> nonprogrammers have clashed about these chips and in the end, they're all
>> still being used today.  You can always tell when the programmer took
>> shortcuts or just didn't know what he was doing.
>>
>> When you say the 6551 is not a wise choice for any new designs, your
>> intent is clear but the statement is not true.  Someone who's put out a
>> new wireless RS-232 pak didn't just wake up yesterday and discover the
>> 6551.  People who know how to write good software aren't afraid of the
>> 6551.
>>
>> My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo 1's, 1
>> CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy looping
>> tests (1-2 days sometimes), and I haven't seen it bomb out yet.  Can you
>> please tell me what circumstances I need in order to break my protocol ?
>
> I'm not a guru on all this but, it seems to me that if there was a bug in
> the original 6551, over the years it's been produced and cloned that
> somewhere, someone would have fixed it.
> I think Roger may be correct inasmuch that programming may have been the
> problem... although I don't know. It just seems that way because the 
> darned
> chip would have been fixed by now.
> I'm happy with my 6551 chips in my (OS9) coco. I'm not using Nitros9 so it
> would naturally be a little slower but, I've done megs of transfers 
> without
> incident..... I think.



--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.0.237 / Virus Database: 270.11.6/1981 - Release Date: 03/04/09
07:41:00



From mmarlette at frontiernet.net  Wed Mar  4 20:46:12 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Thu, 5 Mar 2009 01:46:12 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <00aa01c99d32$15647300$402d5900$@com>
Message-ID: <859593698.270341236217572919.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

Tom,

(1965) .... For a Few Dollars More (UK) (USA) 

:)

Was just on this past weekend, AMC as I recall. Nothing like a good western on while doing CoCo dev work!

Mark
Cloud-9


----- Original Message -----
From: "Tom Seagrove" <tjseagrove at writeme.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 4, 2009 7:31:15 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

Fist Full of Dollars?

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
Behalf Of Mark Marlette
Sent: Wednesday, March 04, 2009 8:29 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] 16550 wasRe: RS232 paks

George,

Do not forget that the chip does work. It just doesn't work in all
conditions.

If it didn't work they wouldn't sell it.

In your application is obviously is working for you. I have stated the
conditions, SockMaster did as well. It will fall flat on it's face.

'For a Few Dollars More', you can have the real deal. Problem is that the
16550 will not support the legacy term programs for the CoCo, there are all
kinds of issues that we deal with when adding technology to an old computer.
It is way more work to implement but that is why it is on the SB. Can't have
lost data, ever.

Clint Eastwood fans will get my movie title above.... :)

Regards,

Mark


----- Original Message -----
From: "George Ramsower" <georgeramsower at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 4, 2009 7:19:25 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

hmm.
 I think I'll have to find some time and see how I built that 3 port com 
board. It works goodly. I'm wondering if I made those changes to the 
intended design.
 All I know now is that it works. I ran two modems on two different 
telephone exchanges and it eliminated long distance charges from one to the 
other. I was lucky enough to be in the middle and didn't have to pay between

them.
 This was the old way to do BBS systems to avoid long distance charges. I 
didn't join a network and therefore, I was not a hub.
 "Hub" was that what it was called? Dammit, I can't remember.

George

----- Original Message ----- 
From: "Mark Marlette"
> George,
>
> Google a bit and you will see, it is a wonderful tool.
>
> Maybe you will believe our own SockMaster on the subject.......
>
> http://www.axess.com/twilight/sock/cocofile/rs232mod.txt
>
> This is an extraction from his article from :
>
>   Now for what IS in the diagram:  The other problem with putting a 
> high-speed
> modem on my BBS is a little less important,  but fixing it makes 
> everything
> much easier.  With this modification the CPU gets less bogged down, the 
> RS-232
> driver becomes easier to write, and the BBS *never* misses any incoming 
> data.
> Normally, the 6551 simply has no way of telling my modem when it's data 
> buffer
> is full.  If someone called my BBS at a high baud rate and tried uploading

> a
> text file, my driver simply didn't read the data fast enough to get it all
> without missing bytes. Every time the disk drive went on, the CPU halts 
> and the
> 6551 misses more data.  In order not to miss data, the RS-232 driver would

> have
> to immediately read data from the 6551 every time a byte came in.  The
> solution?  I made a little circuit that sits on top of the 6551 chip (a 
> 74ls32
> and 74ls00) that generates a new RTS control signal.  Since modern modems 
> have
> a data buffer, it would be really neat to unload a lot of work from the 
> CoCo
> and leave it for the modem to do.  This hardware circuit simply creates a 
> new
> RTS line for the 6551.  Every time the 6551 receives data, the circuit 
> raises
> the RTS line (which tells the modem to stop sending to the CoCo) until 
> that
> data is read by the software.  If the driver reads the data at the full
> incoming speed, there is no slowdown in throughput.  If the driver goes on

> a
> break, or the disk drive comes into use... whatever, the modem is told not

> to
> send any more data to the 6551 until the 6551 is ready to recieve it!
> Effectively, the circuit disallows the 6551 from missing any data.  It 
> also
> places the job of buffering incoming data on the modem, and not the CoCo.
> The CoCo doesn't have to keep reading the 6551 every time a byte comes in,
> since it won't lose the data if it lets it wait.  Now it can read the data
> when it actually wants it.  This speeds up my BBS quite a bit,  I only 
> read
> from  the 6551 when the BBS wants input from the user.  If the user 
> transmits
> stuff while the BBS is calculating, loading, thinking, etc... the modem 
> will
> buffer it for me.
>
>
> Regards,
>
> Mark
> Cloud-9
> ----- Original Message -----
> From: "George Ramsower"
> ----- Original Message ----- 
> From: "Roger Taylor"
>> At 09:40 AM 3/4/2009, you wrote:
>>>Willard,
>>>
>>>The NitrOS-9/Driver is already written for a 16550 device. I have had a
>>>homebrew card running for almost 10yrs based upon that chipset.
>>>
>>>Yes, it would break all the old term programs. A caveat of adding new
>>>technology to an old machine. Not a problem in NitrOS-9 as the driver/dd
>>>is not part of the actual program, when properly written.
>>>
>>>The SuperBoard has a multi-function chip on it that has the 16550 in it.
>>>Anyone that has done high speed serial testing in a system will design it
>>>with hardware handshaking. It is no secret that the ACIA(6551) has issues
>>>with this, plus almost no buffer space. Not a good choice for new 
>>>designs,
>>>IMHO. 16xxx series offers GREAT buffers, programmable interrupt 
>>>thresholds
>>>etc..... I guess that is why they are so common, oh they work too! :)
>>>
>>>Regards,
>>>
>>>Mark
>>>Cloud-9
>>
>>
>> Mark,
>>
>> Exactly what problems have you yourself had with the 6551 so that I may
>> try to offer a software solution?  I'm not claiming to have all the
>> answers, but I've done a serious amount of 6551 coding in the past, and I
>> can assure you that the chip itself is not always the problem.  The
>> programmer is 90% of the problem.  The OS is 90% of the problem.  If
>> there's some little bug or dislike about a certain chip, I guarantee that
>> there's the same number or more in the 16550.  I've read about that chip
>> and based on how many variants are floating around, how can anyone ever
>> agree on a right way to code the routines?  It appears to be a mess, no
>> less than what you claim about the 6551.  I'm not saying any certain chip
>> is BETTER than the other.. I'm saying that TOO many programmers and
>> nonprogrammers have clashed about these chips and in the end, they're all
>> still being used today.  You can always tell when the programmer took
>> shortcuts or just didn't know what he was doing.
>>
>> When you say the 6551 is not a wise choice for any new designs, your
>> intent is clear but the statement is not true.  Someone who's put out a
>> new wireless RS-232 pak didn't just wake up yesterday and discover the
>> 6551.  People who know how to write good software aren't afraid of the
>> 6551.
>>
>> My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo 1's, 1
>> CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy looping
>> tests (1-2 days sometimes), and I haven't seen it bomb out yet.  Can you
>> please tell me what circumstances I need in order to break my protocol ?
>
> I'm not a guru on all this but, it seems to me that if there was a bug in
> the original 6551, over the years it's been produced and cloned that
> somewhere, someone would have fixed it.
> I think Roger may be correct inasmuch that programming may have been the
> problem... although I don't know. It just seems that way because the 
> darned
> chip would have been fixed by now.
> I'm happy with my 6551 chips in my (OS9) coco. I'm not using Nitros9 so it
> would naturally be a little slower but, I've done megs of transfers 
> without
> incident..... I think.



--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.0.237 / Virus Database: 270.11.6/1981 - Release Date: 03/04/09
07:41:00


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From farna at att.net  Wed Mar  4 20:52:42 2009
From: farna at att.net (Frank Swygert)
Date: Wed, 04 Mar 2009 20:52:42 -0500
Subject: [Coco] Disk commands
Message-ID: <49AF306A.4090109@att.net>

Bill, if you just need a reminder on commands and syntax got to ftp://maltedmedia.com/coco/Farna/ and look at the Quick Reference Guides. Print one out for DECB and keep it handy! There's one for OS-9 too. Never did one for Nitros... would be nice! 


---------
Date: Wed, 4 Mar 2009 17:21:41 -0500
From: "Bill" <cwgordon at carolina.rr.com>

It's been SO long since I tinkered with a coco, I have forgotten nearly all
I knew. First, how do I backup up a disk? I cannot remember the command. 

-- 
Frank Swygert
Publisher, "American Motors Cars" 
Magazine (AMC)
For all AMC enthusiasts
http://farna.home.att.net/AMC.html
(free download available!)



From chawks at dls.net  Wed Mar  4 20:59:13 2009
From: chawks at dls.net (Christopher Hawks)
Date: Wed, 04 Mar 2009 19:59:13 -0600
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <EE279CB9-DDE7-4918-901C-E40D4FCE7D50@pritchard.ca>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>	<49ADD1A5.9040808@aurigae.demon.co.uk>
	<EE279CB9-DDE7-4918-901C-E40D4FCE7D50@pritchard.ca>
Message-ID: <49AF31F1.6040806@dls.net>

Ryan Pritchard said the following on 03/03/2009 10:11 PM:
> It would be my understanding that any patent (if any existed) on the MPI 
> would be expired at this point, leaving only a potential for copy-write 
> issues.  Though my thought is if one can buy the PAL fix for the CoCo 3, 
> then one merely has to assemble said parts from a schematic and voila MPI.
> 
> On the flip side there was mention of Chris Hawk who is still on this 
> list that previously made a compatible/comparable device called the 
> SlotPak III, as was pointed out by Tom Seagrove.  Maybe he would be able 
> to release details on that device if they still exist such that we could 
> see these manufactured again, or at least people could choose to make 
> one themselves.

     I never built the Slot-Pak III. But, I did design it and make some early 
prototypes. Howard Medical and CoCoPro built and sold them. I have the 
schematic somewhere (I think) and I do have a bare pc-board. There are no 
Net-Lists or Gerber files as this was designed in 1988 and the board was laid 
out with pin-striping tape.

-- 
Christopher R. Hawks
HAWKSoft
---------------------------------------------------------
"Who is General Failure and why is he reading my hard disk?"
Microsoft spel chekar vor sail, worgs grate !!
	-- Felix von Leitner, leitner at inf.fu-berlin.de


From boisy at tee-boy.com  Wed Mar  4 21:02:00 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Wed, 4 Mar 2009 20:02:00 -0600
Subject: [Coco] CoCo Wireless RS-232 Pak
In-Reply-To: <20090301083308.7D2B620A16@qs281.pair.com>
References: <20090225004631.9B8B120A13@qs281.pair.com>
	<200902282214.31613.rcrislip@neo.rr.com>
	<20090301083308.7D2B620A16@qs281.pair.com>
Message-ID: <0412E723-2A63-4090-90B4-166762C071FE@tee-boy.com>

On Mar 1, 2009, at 2:33 AM, Roger Taylor wrote:

> At 09:14 PM 2/28/2009, you wrote:
>> Hi Roger,
>>
>> I am a bit fuzzy on this. Is the Wireless RS232 a wireless  
>> extension/model of
>> your CoCoNet, or is it an entirely new product. TIA
>
>
> CoCoNet will be the firmware in my bluetooth pak, if that helps  
> clear anything up.
>
> I'm thinking of releasing CoCoNet itself as a free product to help  
> sell my hardware solutions for having CoCoNet on power-up.


Roger,

I have to believe that you are well aware that giving away your  
CoCoNet software would directly undermine sales of DriveWire.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From jps.subscriptions at gmail.com  Wed Mar  4 21:29:33 2009
From: jps.subscriptions at gmail.com (J.P. Samson)
Date: Wed, 4 Mar 2009 19:29:33 -0700
Subject: [Coco] CoCo Wireless RS-232 Pak
In-Reply-To: <0412E723-2A63-4090-90B4-166762C071FE@tee-boy.com>
References: <20090225004631.9B8B120A13@qs281.pair.com>
	<200902282214.31613.rcrislip@neo.rr.com>
	<20090301083308.7D2B620A16@qs281.pair.com>
	<0412E723-2A63-4090-90B4-166762C071FE@tee-boy.com>
Message-ID: <D7F85E86-82A6-4D65-AE8F-A8464CC73F11@gmail.com>

On Mar 4, 2009, at 7:02 PM, Boisy Pitre wrote:
> I have to believe that you are well aware that giving away your  
> CoCoNet software would directly undermine sales of DriveWire.

Wouldn't giving away the CoCoNet software also undermine sales of  
Roger's custom RS-232?  Anyone with an existing RS-232 Pak could get  
all the functionality for free.

-- JP



From gene.heskett at verizon.net  Wed Mar  4 21:38:53 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 21:38:53 -0500
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <49AF31F1.6040806@dls.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<EE279CB9-DDE7-4918-901C-E40D4FCE7D50@pritchard.ca>
	<49AF31F1.6040806@dls.net>
Message-ID: <200903042138.53329.gene.heskett@verizon.net>

On Wednesday 04 March 2009, Christopher Hawks wrote:
>Ryan Pritchard said the following on 03/03/2009 10:11 PM:
>> It would be my understanding that any patent (if any existed) on the MPI
>> would be expired at this point, leaving only a potential for copy-write
>> issues.  Though my thought is if one can buy the PAL fix for the CoCo 3,
>> then one merely has to assemble said parts from a schematic and voila MPI.
>>
>> On the flip side there was mention of Chris Hawk who is still on this
>> list that previously made a compatible/comparable device called the
>> SlotPak III, as was pointed out by Tom Seagrove.  Maybe he would be able
>> to release details on that device if they still exist such that we could
>> see these manufactured again, or at least people could choose to make
>> one themselves.
>
>     I never built the Slot-Pak III. But, I did design it and make some
> early prototypes. Howard Medical and CoCoPro built and sold them. I have
> the schematic somewhere (I think) and I do have a bare pc-board. There are
> no Net-Lists or Gerber files as this was designed in 1988 and the board was
> laid out with pin-striping tape.

Ahh, the old school.  Lay it out about 4x with tape, and run it over to the 
newspaper where their Brown Horizontal would bring it to size and make the 
negative 6 up.  Bring it back, spray some resist on a pcb & let it dry in a 
hot dark box, sandwitch the negative against the pcb, close the exposure frame 
& turn on the vacuum pump to pull things up nice & snug & burn with an arc 
lamp from about a foot & a half for 4 or 5 minutes.  Develop in kerosene & 
drop it into the one relatively high tech gizmo we had at KOTA, a DEA Spray 
etcher.  Once warmed up, it was about 2 minutes for a double sided board that 
had 6 copies of my stuff on it.  Wash it up, cut it up, drill, mount & solder 
parts.  About 2 days and we had 6 copies up and running.  And the notes I'd 
made with a pencil inside the 10x10 grid background as I laid out the tape?  
Perfectly legible in copper .025" high.  High end of the 60's, and I was 
impressed with the 'state of the art'.  Seems like at least an eon ago now.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Only those who leisurely approach that which the masses are busy about
can be busy about that which the masses take leisurely.
		-- Lao Tsu



From operator at coco3.com  Wed Mar  4 21:47:42 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 04 Mar 2009 20:47:42 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <200903041908.16945.gene.heskett@verizon.net>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<200903041615.42740.gene.heskett@verizon.net>
	<20090304224859.7076820A13@qs281.pair.com>
	<200903041908.16945.gene.heskett@verizon.net>
Message-ID: <20090305024830.9FEB220A13@qs281.pair.com>

At 06:08 PM 3/4/2009, you wrote:
> >http://cgi.ebay.com/100M-2-4G-USB-2-0-BLUETOOTH-DONGLE-V2-EDR-PC-ADAPTER_W0Q
> >QitemZ380108270824QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item38010827082
> >4&_trksid=p3286.c0.m14&_trkparms=72%3A1234|66%3A2|65%3A12|39%3A1|240%3A1308|
> >301%3A1|293%3A1|294%3A50
>
>Humm, wish I had known that, but these are already ordered.  Sigh.

That's ok, try ordering 200 1.8432 mhz crystals only to find they are 
the size of a small padlock instead of the modern mini ones.  That 
ebay seller needed a horse kick in the nuts after doing that to 
me.  Oh well.  They'll probably work but I'll just keep'em around in 
case I need something to stick paper on the cork 
board.  heheh.  Double thumb tacks, how brilliant.


-- 
Roger Taylor

http://www.wordofthedayonline.com



From gene.heskett at verizon.net  Wed Mar  4 21:55:52 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 21:55:52 -0500
Subject: [Coco] CoCo Wireless RS-232 Pak
In-Reply-To: <D7F85E86-82A6-4D65-AE8F-A8464CC73F11@gmail.com>
References: <20090225004631.9B8B120A13@qs281.pair.com>
	<0412E723-2A63-4090-90B4-166762C071FE@tee-boy.com>
	<D7F85E86-82A6-4D65-AE8F-A8464CC73F11@gmail.com>
Message-ID: <200903042155.52211.gene.heskett@verizon.net>

On Wednesday 04 March 2009, J.P. Samson wrote:
>On Mar 4, 2009, at 7:02 PM, Boisy Pitre wrote:
>> I have to believe that you are well aware that giving away your
>> CoCoNet software would directly undermine sales of DriveWire.
>
>Wouldn't giving away the CoCoNet software also undermine sales of
>Roger's custom RS-232?  Anyone with an existing RS-232 Pak could get
>all the functionality for free.

Missing one point though.  Using Rogers bluetooth, we can do away with the 
sometimes pretty long cable from the pc to the coco.  My poor old coco3, 
sitting all set up but in the finished basement, about 25 feet away by a hole 
in the floor, has been damaged, or had stuff in the cabling damaged by the emp 
of a nearby lightning strike, twice now.  Using the bluetooth, there is no 
long cables to pick up the emp.  When usb extension cables are $40 ea, and I 
only have one left of the 3 I originally bought, failures induced by the 
outside noise, I'll get this setup and not have to worry about that ever 
again. Once again, the coco will be self contained, so the powerline on its 
desk can bounce 100k volts in a different direction from this room, the whole 
thing bounces in unison and there is no damage because there is no long 
antenna.

This whole room except for the overhead lights, is running on a single duplex 
outlet with about a 500 joule surge protector, and 80% of the rest is plugged 
into a 1500WH UPS.

Amazingly to me, I have had a 125' piece if cat5 plugged into my 8 port switch 
that runs into the basement and across to a point near where the telco line 
comes thru the footing, then under the back porch and up the wall to an anchor 
point on the back porch roof, then about 40 feet out to the shop building 
stretched overhead across the back yard for almost 5 years now, and neither 
the switch nor the nic in the milling machines box have been damaged.

Before I put everything on one power source in here, I used to lose a modem 
every time somebody called that stuff butter.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Entropy isn't what it used to be.



From gene.heskett at verizon.net  Wed Mar  4 21:57:48 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 21:57:48 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <20090305024830.9FEB220A13@qs281.pair.com>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<200903041908.16945.gene.heskett@verizon.net>
	<20090305024830.9FEB220A13@qs281.pair.com>
Message-ID: <200903042157.48688.gene.heskett@verizon.net>

On Wednesday 04 March 2009, Roger Taylor wrote:
>At 06:08 PM 3/4/2009, you wrote:
>> >http://cgi.ebay.com/100M-2-4G-USB-2-0-BLUETOOTH-DONGLE-V2-EDR-PC-ADAPTER_
>> >W0Q
>> > QitemZ380108270824QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item3801082
>> >7082
>> > 4&_trksid=p3286.c0.m14&_trkparms=72%3A1234|66%3A2|65%3A12|39%3A1|240%3A1
>> >308| 301%3A1|293%3A1|294%3A50
>>
>>Humm, wish I had known that, but these are already ordered.  Sigh.
>
>That's ok, try ordering 200 1.8432 mhz crystals only to find they are
>the size of a small padlock instead of the modern mini ones.  That
>ebay seller needed a horse kick in the nuts after doing that to
>me.  Oh well.  They'll probably work but I'll just keep'em around in
>case I need something to stick paper on the cork
>board.  heheh.  Double thumb tacks, how brilliant.

ROTFLMAO!  I have a picture of that in my mind right now. :)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
While your friend holds you affectionately by both your hands you are
safe, for you can watch both of his.
		-- Ambrose Bierce, "The Devil's Dictionary"



From operator at coco3.com  Wed Mar  4 22:08:11 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 04 Mar 2009 21:08:11 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <2120297497.244951236212012329.JavaMail.root@cl04-host03.ro
	ch.ny.frontiernet.net>
References: <1206785309.241111236211178532.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<2120297497.244951236212012329.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <20090305030839.018F920A13@qs281.pair.com>

At 06:13 PM 3/4/2009, you wrote:
>George,
>
>Google a bit and you will see, it is a wonderful tool.
>
>Maybe you will believe our own SockMaster on the subject.......
>
>http://www.axess.com/twilight/sock/cocofile/rs232mod.txt
>
>This is an extraction from his article from :
>
>    Now for what IS in the diagram:  The other problem with putting 
> a high-speed
>modem on my BBS is a little less important,  but fixing it makes everything



While Sock is an amazing think tank, I like to think that I am, too.  :)
Btw, his hack article deals with 6551 connections to a certain flavor of modem.


-- 
Roger Taylor

http://www.wordofthedayonline.com



From coconut at pritchard.ca  Wed Mar  4 22:30:47 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Wed, 4 Mar 2009 21:30:47 -0600
Subject: [Coco] '68' Micro Journal
In-Reply-To: <1iw27ah.19xipcmiffapfM%tlindner@macmess.org>
References: <1iw27ah.19xipcmiffapfM%tlindner@macmess.org>
Message-ID: <C88FA3BC-DB27-4E12-88FD-F9A15CB5A794@pritchard.ca>

That's awesome!  Where does one find them?

Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies



On 4-Mar-09, at 5:07 PM, tim lindner wrote:

> Ryan Pritchard <coconut at pritchard.ca> wrote:
>
>> I am expecting that if these magazines were to be scanned there would
>> be significant interest.
>
> They've already been scanned and made avaiable by the publisher.
>
> --  
> tim lindner
> tlindner at macmess.org                                               
> Bright
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From gene.heskett at verizon.net  Wed Mar  4 22:41:31 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 04 Mar 2009 22:41:31 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <20090305030839.018F920A13@qs281.pair.com>
References: <1206785309.241111236211178532.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<2120297497.244951236212012329.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<20090305030839.018F920A13@qs281.pair.com>
Message-ID: <200903042241.31360.gene.heskett@verizon.net>

On Wednesday 04 March 2009, Roger Taylor wrote:
>At 06:13 PM 3/4/2009, you wrote:
>>George,
>>
>>Google a bit and you will see, it is a wonderful tool.
>>
>>Maybe you will believe our own SockMaster on the subject.......
>>
>>http://www.axess.com/twilight/sock/cocofile/rs232mod.txt
>>
>>This is an extraction from his article from :
>>
>>    Now for what IS in the diagram:  The other problem with putting
>> a high-speed
>>modem on my BBS is a little less important,  but fixing it makes everything
>
>While Sock is an amazing think tank, I like to think that I am, too.  :)
>Btw, his hack article deals with 6551 connections to a certain flavor of
> modem.

The point is that it makes the modem do the work, if it cannot, then it is as 
broken as the 6551.  And back then, new modems were only as far away as wally 
world.  New, properly configured rs-232 backs weren't available at any price 
unless you yourself did the fixes that folks like Sock figured out.

As for brains, I think at this point your bona-fides in that dept are well 
established. 20 years ago I could have gotten into some pretty good 
discusssions with you, but 20 years ago I was also only 54.  Now I have to 
admit I bow to the ones with the giddy-yup to git-r-done.  My giddy-up often 
gets up ahead of me, or sleeps in, I haven't figured out which but he is 
certainly not on the same page as I.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Hell is empty and all the devils are here.
		-- Wm. Shakespeare, "The Tempest"



From operator at coco3.com  Wed Mar  4 23:04:11 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 04 Mar 2009 22:04:11 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <2102867535.251961236213293264.JavaMail.root@cl04-host03.ro
	ch.ny.frontiernet.net>
References: <1058935473.250331236212905573.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<2102867535.251961236213293264.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <20090305040440.8656220A13@qs281.pair.com>

At 06:34 PM 3/4/2009, you wrote:
>Roger,

>Again I ask you.
>Are you hardware handshaking with your device?
>Do you have a test case under NitrOS-9?
>Please expand in detail if you wish.

Mark, I explained to you many times that my pak was a working clone 
of the Tandy Deluxe RS-232 Pak.  Yes, the CTS and RTS signals are 
there, and Yes, the pak works under OS-9 and NitrOS-9.

Do any of your items work the same under Color BASIC as they do for 
the NitrOS-9 hackjob of OS-9 ?    Has anything in NitrOS-9 been 
changed from the original OS-9 just to get one of your gadgets to 1) 
function better, 2) just function, 3) have a practical use?


-- 
Roger Taylor

http://www.wordofthedayonline.com



From operator at coco3.com  Wed Mar  4 23:24:01 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 04 Mar 2009 22:24:01 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <200903042241.31360.gene.heskett@verizon.net>
References: <1206785309.241111236211178532.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<2120297497.244951236212012329.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<20090305030839.018F920A13@qs281.pair.com>
	<200903042241.31360.gene.heskett@verizon.net>
Message-ID: <20090305042429.A03D520A15@qs281.pair.com>

At 09:41 PM 3/4/2009, you wrote:

>As for brains, I think at this point your bona-fides in that dept are well
>established. 20 years ago I could have gotten into some pretty good
>discusssions with you, but 20 years ago I was also only 54.  Now I have to
>admit I bow to the ones with the giddy-yup to git-r-done.  My giddy-up often
>gets up ahead of me, or sleeps in, I haven't figured out which but he is
>certainly not on the same page as I.


My hat's off to you.

-- 
Roger Taylor

http://www.wordofthedayonline.com



From operator at coco3.com  Thu Mar  5 00:13:34 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 04 Mar 2009 23:13:34 -0600
Subject: [Coco] CoCo Wireless RS-232 Pak
Message-ID: <20090305051402.E9D0220A13@qs281.pair.com>

Hey guys, magically, the former wireless pak prototype became a 
production grade beauty, so I updated the inside-peek picture which 
has been scaled down to tease with Mark a little more.  :)  If you 
squint just right you could get a headache.  ;)

www.coco3.com
-- 
Roger Taylor

http://www.wordofthedayonline.com



From neilsmorr at gmail.com  Thu Mar  5 00:25:04 2009
From: neilsmorr at gmail.com (Neil Morrison)
Date: Wed, 4 Mar 2009 21:25:04 -0800
Subject: [Coco] Disk commands
References: <49AF306A.4090109@att.net>
Message-ID: <889B18E239034185B3ACA0E535F9A3FE@NewBaby>


See also 
http://tech.groups.yahoo.com/group/ColorComputer/files/DiskCommands.htm

Color Disk BASIC Commands (Still needs editing!)

Neil

----- Original Message ----- 
From: "Frank Swygert" <farna at att.net>

> Bill, if you just need a reminder on commands and syntax got to 
> ftp://maltedmedia.com/coco/Farna/ and look at the Quick Reference Guides. 
> Print one out for DECB and keep it handy! There's one for OS-9 too. Never 
> did one for Nitros... would be nice!



From jps.subscriptions at gmail.com  Thu Mar  5 05:24:56 2009
From: jps.subscriptions at gmail.com (J.P. Samson)
Date: Thu, 5 Mar 2009 03:24:56 -0700
Subject: [Coco] CoCo Wireless RS-232 Pak
In-Reply-To: <200903042155.52211.gene.heskett@verizon.net>
References: <20090225004631.9B8B120A13@qs281.pair.com>
	<0412E723-2A63-4090-90B4-166762C071FE@tee-boy.com>
	<D7F85E86-82A6-4D65-AE8F-A8464CC73F11@gmail.com>
	<200903042155.52211.gene.heskett@verizon.net>
Message-ID: <2558C275-41C9-4F73-B0C0-A22C8086EF9F@gmail.com>

On Mar 4, 2009, at 7:55 PM, Gene Heskett wrote:
> On Wednesday 04 March 2009, J.P. Samson wrote:
>> On Mar 4, 2009, at 7:02 PM, Boisy Pitre wrote:
>>> I have to believe that you are well aware that giving away your
>>> CoCoNet software would directly undermine sales of DriveWire.
>>
>> Wouldn't giving away the CoCoNet software also undermine sales of
>> Roger's custom RS-232?  Anyone with an existing RS-232 Pak could get
>> all the functionality for free.
>
> Missing one point though.  Using Rogers bluetooth, we can do away  
> with the
> sometimes pretty long cable from the pc to the coco.  My poor old  
> coco3,
> sitting all set up but in the finished basement, about 25 feet away  
> by a hole
> in the floor, has been damaged, or had stuff in the cabling damaged  
> by the emp
> of a nearby lightning strike, twice now.  Using the bluetooth, there  
> is no
> long cables to pick up the emp.

Yes, if you are interested in a BlueTooth RS-232 Pak, I imagine you'd  
buy one regardless of whether CoCoNet existed.  In that case, CoCoNet  
being free or bundled with the Pak really has no bearing on the  
sale.  :-)

Giving CoCoNet away for nothing could also undermine sales of Roger's  
CoCoNet ROM Pak, too, if one is content simply to load the CoCoNet DOS  
off a floppy as needed.  (Painful, yes, but this is how DriveWire is  
basically sold, too.)  This is the scenario that concerns Boisy,  
because he is charging for the DriveWire client software.

But each of these two products, CoCoNet and DriveWire, do promote  
sales of supporting hardware for their respective enterprises.  Roger  
will be selling BlueTooth RS-232 Paks, and standalone Paks with  
CoCoNet ROMS and serial cables.  Cloud-9 bundles a serial cable with  
DriveWire software purchases, and will burn DriveWire ROMS for  
insertion into existing floppy drive controllers.  Personally, I think  
these additional purchases are required if you will be regularly using  
the software.

This is a capitalist country, so we should be encouraged by such  
competitive moves.  But the CoCo community is small, and I guess Boisy  
isn't too happy about potentially having his toes stepped on in this  
case.  But what should really be of concern to Boisy is whether the  
CoCoNet software is superior to the DriveWire software.  That is what  
is really going to affect his sales, regardless of whether CoCoNet  
costs money or is free.

I'm not gonna take sides here or anything.  I don't think this is a  
scenario where anybody needs to be taking sides.  I already own  
DriveWire 2.  I have no idea if DriveWire 3 will be a compelling  
upgrade--all the details assumedly haven't yet been released.  So  
Boisy has made his money out of me and probably many others, and I  
expect at some point Roger will too for his BlueTooth CoCoNet (unless  
Cloud-9 pulls a rabbit out of its hat).

-- JP



From boisy at tee-boy.com  Thu Mar  5 08:07:23 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Thu, 5 Mar 2009 07:07:23 -0600
Subject: [Coco] CoCo Wireless RS-232 Pak
Message-ID: <393A84BA-F04D-47C5-A522-994CEBEDA49F@tee-boy.com>

> Hey guys, magically, the former wireless pak prototype became a
> production grade beauty, so I updated the inside-peek picture which
> has been scaled down to tease with Mark a little more. :) If you
> squint just right you could get a headache. ;)

Roger,

I also noticed another bit of magic on your website, specifically a  
disappearing act.   The reference to the bitbanger features of CoCoNet  
have been removed.  Does this mean that CoCoNet will only support your  
wireless pak, and that you won't be releasing support for the bitbanger?

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From boisy at tee-boy.com  Thu Mar  5 08:43:40 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Thu, 5 Mar 2009 07:43:40 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
Message-ID: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>

> Do any of your items work the same under Color BASIC as they do for
> the NitrOS-9 hackjob of OS-9 ? Has anything in NitrOS-9 been
> changed from the original OS-9 just to get one of your gadgets to 1)
> function better, 2) just function, 3) have a practical use?

Roger,

There can be no other way to take the "NitrOS-9 hackjob of OS-9"  
comment above as anything other than a slight and a jab at the project.

In the "CoCoNutz!" Christmas 2005 newsletter there is a column titled  
"A Talk With Roger Taylor of CoCo 3.com."  In reference to the  
interview question "What is your favorite operating system? Are you a  
Linux guy or Microsoft guy?" Your response on the CoCo was:

"With the CoCo, my favorite OS would probably have to be NitrOS-9  
which is a highly-customized version of OS-9  Level II.  Although I've  
written almost everything for Disk BASIC, I prefer the power of OS-9  
when I use the CoCo."

This statement is incongruent with your current view that NitrOS-9 is  
a hack job.  Can you please explain what happened between 2005 and now?

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From cwgordon at carolina.rr.com  Thu Mar  5 09:11:01 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 5 Mar 2009 09:11:01 -0500
Subject: [Coco] Pretty new screen
Message-ID: <002401c99d9c$36cbe180$a463a480$@rr.com>

I woke up this morning and turned on my Coco, and I have a pretty new
screen. Please look at http://www.sq1bbs.com/coco/coco-scr.jpg (this is a
close duplicate of the screen) and see if you can (maybe) figure out what's
wrong. I'm sure that there are some Cocoists who have seen this before.

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From rcrislip at neo.rr.com  Thu Mar  5 09:32:49 2009
From: rcrislip at neo.rr.com (richec)
Date: Thu, 5 Mar 2009 09:32:49 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <00aa01c99d32$15647300$402d5900$@com>
References: <009e01c99d30$6ce5a470$6401a8c0@OLDGEORGE>
	<534074304.264771236216522902.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<00aa01c99d32$15647300$402d5900$@com>
Message-ID: <200903050932.50103.rcrislip@neo.rr.com>

On Wednesday 04 March 2009 20:31:15 Tom Seagrove wrote:
Aw just "Hang-en High" 8-)

> Fist Full of Dollars?
>
> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
> Behalf Of Mark Marlette
> Sent: Wednesday, March 04, 2009 8:29 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] 16550 wasRe: RS232 paks
>
> George,
>
> Do not forget that the chip does work. It just doesn't work in all
> conditions.
>
> If it didn't work they wouldn't sell it.
>
> In your application is obviously is working for you. I have stated the
> conditions, SockMaster did as well. It will fall flat on it's face.
>
> 'For a Few Dollars More', you can have the real deal. Problem is that the
> 16550 will not support the legacy term programs for the CoCo, there are all
> kinds of issues that we deal with when adding technology to an old
> computer. It is way more work to implement but that is why it is on the SB.
> Can't have lost data, ever.
>
> Clint Eastwood fans will get my movie title above.... :)
>
> Regards,
>
> Mark
>
>
> ----- Original Message -----
> From: "George Ramsower" <georgeramsower at gmail.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Wednesday, March 4, 2009 7:19:25 PM GMT -06:00 US/Canada Central
> Subject: Re: [Coco] 16550 wasRe:  RS232 paks
>
> hmm.
>  I think I'll have to find some time and see how I built that 3 port com
> board. It works goodly. I'm wondering if I made those changes to the
> intended design.
>  All I know now is that it works. I ran two modems on two different
> telephone exchanges and it eliminated long distance charges from one to the
> other. I was lucky enough to be in the middle and didn't have to pay
> between
>
> them.
>  This was the old way to do BBS systems to avoid long distance charges. I
> didn't join a network and therefore, I was not a hub.
>  "Hub" was that what it was called? Dammit, I can't remember.
>
> George
>
> ----- Original Message -----
> From: "Mark Marlette"
>
> > George,
> >
> > Google a bit and you will see, it is a wonderful tool.
> >
> > Maybe you will believe our own SockMaster on the subject.......
> >
> > http://www.axess.com/twilight/sock/cocofile/rs232mod.txt
> >
> > This is an extraction from his article from :
> >
> >   Now for what IS in the diagram:  The other problem with putting a
> > high-speed
> > modem on my BBS is a little less important,  but fixing it makes
> > everything
> > much easier.  With this modification the CPU gets less bogged down, the
> > RS-232
> > driver becomes easier to write, and the BBS *never* misses any incoming
> > data.
> > Normally, the 6551 simply has no way of telling my modem when it's data
> > buffer
> > is full.  If someone called my BBS at a high baud rate and tried
> > uploading
> >
> > a
> > text file, my driver simply didn't read the data fast enough to get it
> > all without missing bytes. Every time the disk drive went on, the CPU
> > halts and the
> > 6551 misses more data.  In order not to miss data, the RS-232 driver
> > would
> >
> > have
> > to immediately read data from the 6551 every time a byte came in.  The
> > solution?  I made a little circuit that sits on top of the 6551 chip (a
> > 74ls32
> > and 74ls00) that generates a new RTS control signal.  Since modern modems
> > have
> > a data buffer, it would be really neat to unload a lot of work from the
> > CoCo
> > and leave it for the modem to do.  This hardware circuit simply creates a
> > new
> > RTS line for the 6551.  Every time the 6551 receives data, the circuit
> > raises
> > the RTS line (which tells the modem to stop sending to the CoCo) until
> > that
> > data is read by the software.  If the driver reads the data at the full
> > incoming speed, there is no slowdown in throughput.  If the driver goes
> > on
> >
> > a
> > break, or the disk drive comes into use... whatever, the modem is told
> > not
> >
> > to
> > send any more data to the 6551 until the 6551 is ready to recieve it!
> > Effectively, the circuit disallows the 6551 from missing any data.  It
> > also
> > places the job of buffering incoming data on the modem, and not the CoCo.
> > The CoCo doesn't have to keep reading the 6551 every time a byte comes
> > in, since it won't lose the data if it lets it wait.  Now it can read the
> > data when it actually wants it.  This speeds up my BBS quite a bit,  I
> > only read
> > from  the 6551 when the BBS wants input from the user.  If the user
> > transmits
> > stuff while the BBS is calculating, loading, thinking, etc... the modem
> > will
> > buffer it for me.
> >
> >
> > Regards,
> >
> > Mark
> > Cloud-9
> > ----- Original Message -----
> > From: "George Ramsower"
> > ----- Original Message -----
> > From: "Roger Taylor"
> >
> >> At 09:40 AM 3/4/2009, you wrote:
> >>>Willard,
> >>>
> >>>The NitrOS-9/Driver is already written for a 16550 device. I have had a
> >>>homebrew card running for almost 10yrs based upon that chipset.
> >>>
> >>>Yes, it would break all the old term programs. A caveat of adding new
> >>>technology to an old machine. Not a problem in NitrOS-9 as the driver/dd
> >>>is not part of the actual program, when properly written.
> >>>
> >>>The SuperBoard has a multi-function chip on it that has the 16550 in it.
> >>>Anyone that has done high speed serial testing in a system will design
> >>> it with hardware handshaking. It is no secret that the ACIA(6551) has
> >>> issues with this, plus almost no buffer space. Not a good choice for
> >>> new designs,
> >>>IMHO. 16xxx series offers GREAT buffers, programmable interrupt
> >>>thresholds
> >>>etc..... I guess that is why they are so common, oh they work too! :)
> >>>
> >>>Regards,
> >>>
> >>>Mark
> >>>Cloud-9
> >>
> >> Mark,
> >>
> >> Exactly what problems have you yourself had with the 6551 so that I may
> >> try to offer a software solution?  I'm not claiming to have all the
> >> answers, but I've done a serious amount of 6551 coding in the past, and
> >> I can assure you that the chip itself is not always the problem.  The
> >> programmer is 90% of the problem.  The OS is 90% of the problem.  If
> >> there's some little bug or dislike about a certain chip, I guarantee
> >> that there's the same number or more in the 16550.  I've read about that
> >> chip and based on how many variants are floating around, how can anyone
> >> ever agree on a right way to code the routines?  It appears to be a
> >> mess, no less than what you claim about the 6551.  I'm not saying any
> >> certain chip is BETTER than the other.. I'm saying that TOO many
> >> programmers and nonprogrammers have clashed about these chips and in the
> >> end, they're all still being used today.  You can always tell when the
> >> programmer took shortcuts or just didn't know what he was doing.
> >>
> >> When you say the 6551 is not a wise choice for any new designs, your
> >> intent is clear but the statement is not true.  Someone who's put out a
> >> new wireless RS-232 pak didn't just wake up yesterday and discover the
> >> 6551.  People who know how to write good software aren't afraid of the
> >> 6551.
> >>
> >> My wireless RS-232 pak has been connected to 7 CoCo units (2 CoCo 1's, 1
> >> CoCo 3, 4 CoCo 2's) and to 2 PCs @ 115200 bps running lengthy looping
> >> tests (1-2 days sometimes), and I haven't seen it bomb out yet.  Can you
> >> please tell me what circumstances I need in order to break my protocol ?
> >
> > I'm not a guru on all this but, it seems to me that if there was a bug in
> > the original 6551, over the years it's been produced and cloned that
> > somewhere, someone would have fixed it.
> > I think Roger may be correct inasmuch that programming may have been the
> > problem... although I don't know. It just seems that way because the
> > darned
> > chip would have been fixed by now.
> > I'm happy with my 6551 chips in my (OS9) coco. I'm not using Nitros9 so
> > it would naturally be a little slower but, I've done megs of transfers
> > without
> > incident..... I think.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.237 / Virus Database: 270.11.6/1981 - Release Date: 03/04/09
> 07:41:00
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco




From rcrislip at neo.rr.com  Thu Mar  5 09:58:19 2009
From: rcrislip at neo.rr.com (richec)
Date: Thu, 5 Mar 2009 09:58:19 -0500
Subject: [Coco] coco font (kinda)
In-Reply-To: <012301c99ce0$78ce1970$6a6a4c50$@rr.com>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>
	<200903040901.21089.rcrislip@neo.rr.com>
	<012301c99ce0$78ce1970$6a6a4c50$@rr.com>
Message-ID: <200903050958.19945.rcrislip@neo.rr.com>


Heh welcome to my world <sigh>.

> Font Creator 5.0 Professional.
>
> My biggest drawback at copying a font is my poor eyesight.
>
> > -----Original Message-----
> > From: coco-bounces at maltedmedia.com [mailto:coco-
> > bounces at maltedmedia.com] On Behalf Of richec
> > Sent: Wednesday, March 04, 2009 9:01 AM
> > To: CoCoList for Color Computer Enthusiasts
> > Subject: Re: [Coco] coco font (kinda)
> >
> > Hi Bill,
> >
> > What font editor are you using. Typesmith? TIA
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco




From cwgordon at carolina.rr.com  Thu Mar  5 10:03:31 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 5 Mar 2009 10:03:31 -0500
Subject: [Coco] coco font (kinda)
In-Reply-To: <200903050958.19945.rcrislip@neo.rr.com>
References: <01fc01c99abb$43f39ad0$cbdad070$@rr.com>	<200903040901.21089.rcrislip@neo.rr.com>	<012301c99ce0$78ce1970$6a6a4c50$@rr.com>
	<200903050958.19945.rcrislip@neo.rr.com>
Message-ID: <002c01c99da3$8cbe4680$a63ad380$@rr.com>

Yeah, remember the days that we could spot a fly on a wall on a house across
the field?

Now it's good to be able to spot the HOUSE!!

hehehehe

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of richec
> Sent: Thursday, March 05, 2009 9:58 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] coco font (kinda)
> 
> 
> Heh welcome to my world <sigh>.
> 
> > Font Creator 5.0 Professional.
> >
> > My biggest drawback at copying a font is my poor eyesight.
> >
> > > -----Original Message-----
> > > From: coco-bounces at maltedmedia.com [mailto:coco-
> > > bounces at maltedmedia.com] On Behalf Of richec
> > > Sent: Wednesday, March 04, 2009 9:01 AM
> > > To: CoCoList for Color Computer Enthusiasts
> > > Subject: Re: [Coco] coco font (kinda)
> > >
> > > Hi Bill,
> > >
> > > What font editor are you using. Typesmith? TIA
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From mmarlette at frontiernet.net  Thu Mar  5 10:04:37 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Thu, 5 Mar 2009 15:04:37 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <20090305040440.8656220A13@qs281.pair.com>
Message-ID: <1613232635.374751236265477297.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

Roger,

A few quick points for the ones that are growing tired of this thread,  
as am I.

  1. Lets agree to disagree.
  2. We have different requirements for our designs.

Worn-out thread followers might want to exit at this point, maybe not  
though??

You specifically asked me for some test cases. I gave them to you. You  
ignored all of my questions, instead answering them with questions and  
skirting the issues of the 6551. In the future, please do not ask me a  
question that you don't want to hear the answers to.

You post messages to the list commenting on every step of your design,  
announcing your progress, and openly soliciting questions and  
comments; consequently, I and others respond. In my industry, this is  
called "peer review."

Yet there is a pattern to your responses that suggest to me that you  
don't work in this industry.  If the critique isn't complimentary or  
your ego isn't being stroked, you either avoid answering the question  
or you get defensive.

In these same posts, you attempt to mask the true inner workings of  
your products with terms like "magic" and other hyperbole.  Marketers  
hype; engineers demystify things.

What you are doing is nothing new, no squinting required. I know how  
you are making the device go 115.2k; I also know how you are getting  
your device to work in your app and avoiding the 6551 errata. I also  
know that there is NitrOS-9 support for your device.  There is nothing  
new here. Your pak, outside of your app, will work as good or as  
poorly as any other RS-232 pak which is deemed by what you are doing.  
You are not smarter than the chip manufactures, trust me when I say  
this. You really think that they want to place a statement like that  
in their data sheets? Discounting the CTS/RTS problem and blaming it  
on a specific modem may seem plausible to non-techies, but is  
ridiculous to technical people.

There is a difference between innovation and integration.  Your  
bluetooth pak is an example of the later.  I realize that you have  
time and money invested in to your product and you are avoiding the  
questions that you directly asked me to save some face on it. We  
clearly have different views on our requirements and quality of our  
products, and that is ok.  But every time you try to blow smoke, I  
will be there to clear the air.

As to your comments of, I believe it was, '90% of programmers don't  
know what they are doing' or something close to that, is something  
that many here may take offense to. Are you the 10% that are "in the  
know?"  You are talking to a smart group of people here on this list;  
9 out of 10 don't know what they are doing? If I made a statement like  
that at work I would not be allowed to work on projects, be labeled as  
a crazy person and then be looking for another job.

Again, this tells me that you probably don't make your living in the  
field of hardware/software development.

Regards,

Mark
Cloud-9

----- Original Message -----
From: "Roger Taylor" <operator at coco3.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Wednesday, March 4, 2009 10:04:11 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

At 06:34 PM 3/4/2009, you wrote:
>Roger,

>Again I ask you.
>Are you hardware handshaking with your device?
>Do you have a test case under NitrOS-9?
>Please expand in detail if you wish.

Mark, I explained to you many times that my pak was a working clone 
of the Tandy Deluxe RS-232 Pak.  Yes, the CTS and RTS signals are 
there, and Yes, the pak works under OS-9 and NitrOS-9.

Do any of your items work the same under Color BASIC as they do for 
the NitrOS-9 hackjob of OS-9 ?    Has anything in NitrOS-9 been 
changed from the original OS-9 just to get one of your gadgets to 1) 
function better, 2) just function, 3) have a practical use?


-- 
Roger Taylor

http://www.wordofthedayonline.com


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From tlindner at macmess.org  Thu Mar  5 10:18:26 2009
From: tlindner at macmess.org (tim lindner)
Date: Thu, 5 Mar 2009 07:18:26 -0800
Subject: [Coco] '68' Micro Journal
In-Reply-To: <C88FA3BC-DB27-4E12-88FD-F9A15CB5A794@pritchard.ca>
Message-ID: <1iw3g91.1abu5bvef4sg6M%tlindner@macmess.org>

Ryan Pritchard <coconut at pritchard.ca> wrote:

> That's awesome!  Where does one find them?

I thought they were on the web somewhere. But apearently not.

I'll try to find my copy, and upload them somewhere.

-- 
tim lindner
tlindner at macmess.org                                              Bright



From robert.gault at worldnet.att.net  Thu Mar  5 11:22:17 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 05 Mar 2009 11:22:17 -0500
Subject: [Coco] Pretty new screen
In-Reply-To: <002401c99d9c$36cbe180$a463a480$@rr.com>
References: <002401c99d9c$36cbe180$a463a480$@rr.com>
Message-ID: <49AFFC39.7060003@worldnet.att.net>

Bill wrote:
> I woke up this morning and turned on my Coco, and I have a pretty new
> screen. Please look at http://www.sq1bbs.com/coco/coco-scr.jpg (this is a
> close duplicate of the screen) and see if you can (maybe) figure out what's
> wrong. I'm sure that there are some Cocoists who have seen this before.
> 

There is no way to tell what is wrong just by looking at this image.

You should check the seating of all socketed ICs and the MPI / Coco 
ports if used. Oxidation and misalignment preventing Basic from starting 
is a possibility.

If you have or have access to a service manual, check voltages at 
various parts of the motherboard. Part of the power supply could have blown.


From cwgordon at carolina.rr.com  Thu Mar  5 11:28:01 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 5 Mar 2009 11:28:01 -0500
Subject: [Coco] Pretty new screen
In-Reply-To: <49AFFC39.7060003@worldnet.att.net>
References: <002401c99d9c$36cbe180$a463a480$@rr.com>
	<49AFFC39.7060003@worldnet.att.net>
Message-ID: <002d01c99daf$5b54ede0$11fec9a0$@rr.com>

Well, I was HOPEING that someone else had seen this screen and knew what
caused it. Oh, well.....

Thanks

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Thursday, March 05, 2009 11:22 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Pretty new screen
> 
> There is no way to tell what is wrong just by looking at this image.



From afra at aurigae.demon.co.uk  Thu Mar  5 11:57:40 2009
From: afra at aurigae.demon.co.uk (afra at aurigae.demon.co.uk)
Date: Thu, 05 Mar 2009 16:57:40 +0000
Subject: [Coco] Pretty new screen
In-Reply-To: <002401c99d9c$36cbe180$a463a480$@rr.com>
References: <002401c99d9c$36cbe180$a463a480$@rr.com>
Message-ID: <20090305165740.88583yz4xfj3qzcw@aurigae.demon.co.uk>

Quoting Bill <cwgordon at carolina.rr.com>:

> I woke up this morning and turned on my Coco, and I have a pretty new
> screen. Please look at http://www.sq1bbs.com/coco/coco-scr.jpg (this is a
> close duplicate of the screen) and see if you can (maybe) figure out what's
> wrong. I'm sure that there are some Cocoists who have seen this before.

Which CoCo model is this ?

Whilst I agree with Robert who said that it would be impossible to  
tell for cirtain, the one time I have seen a patern like that before  
from a Dragon, which is basically the same as the CoCo 1/2, the  
problem was the 74LS244 buffer chip that sits between the processor  
data bus and the RAM/VDG data bus. Said LS chip had died and no data  
was getting writen to the RAM, and so the VDG was just pulling out  
whatever default patern was there.

Cheers.

Phill.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



From lamune at doki-doki.net  Thu Mar  5 12:25:49 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Thu, 5 Mar 2009 09:25:49 -0800
Subject: [Coco] Pretty new screen
In-Reply-To: <20090305165740.88583yz4xfj3qzcw@aurigae.demon.co.uk>
References: <002401c99d9c$36cbe180$a463a480$@rr.com>
	<20090305165740.88583yz4xfj3qzcw@aurigae.demon.co.uk>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A7@fenestra.lamunet.local>

That's entirely possible. A great diagnostic is to listen carefully when
you power up the CoCo. If you hear a double click from the cassette
relay, the CoCo has initialized the hardware properly. If you get a
single click, it hasn't. 

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com]
On Behalf Of afra at aurigae.demon.co.uk
Sent: Thursday, March 05, 2009 8:58 AM
To: coco at maltedmedia.com
Subject: Re: [Coco] Pretty new screen

Quoting Bill <cwgordon at carolina.rr.com>:

> I woke up this morning and turned on my Coco, and I have a pretty new
> screen. Please look at http://www.sq1bbs.com/coco/coco-scr.jpg (this
is a
> close duplicate of the screen) and see if you can (maybe) figure out
what's
> wrong. I'm sure that there are some Cocoists who have seen this
before.

Which CoCo model is this ?

Whilst I agree with Robert who said that it would be impossible to  
tell for cirtain, the one time I have seen a patern like that before  
from a Dragon, which is basically the same as the CoCo 1/2, the  
problem was the 74LS244 buffer chip that sits between the processor  
data bus and the RAM/VDG data bus. Said LS chip had died and no data  
was getting writen to the RAM, and so the VDG was just pulling out  
whatever default patern was there.

Cheers.

Phill.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



From jcewy at swbell.net  Thu Mar  5 14:12:36 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Thu, 05 Mar 2009 13:12:36 -0600
Subject: [Coco] '68' Micro Journal
In-Reply-To: <1iw3g91.1abu5bvef4sg6M%tlindner@macmess.org>
References: <1iw3g91.1abu5bvef4sg6M%tlindner@macmess.org>
Message-ID: <49B02424.4080801@swbell.net>

tim lindner wrote:
> Ryan Pritchard <coconut at pritchard.ca> wrote:
>
>   
>> That's awesome!  Where does one find them?
>>     
>
> I thought they were on the web somewhere. But apearently not.
>
> I'll try to find my copy, and upload them somewhere.
>
>   
Please let us know where and when.  I'm very interested in seeing them, 
and I'm sure others on this list will be as well.  I have a few issues 
of '68 Micro Journal and really enjoyed them.

JCE



From da3m0n_slay3r at yahoo.com  Thu Mar  5 14:31:13 2009
From: da3m0n_slay3r at yahoo.com (Bill Barnes)
Date: Thu, 5 Mar 2009 11:31:13 -0800 (PST)
Subject: [Coco] multiple multiple mutltiple multiple messages
Message-ID: <506847.71743.qm@web31103.mail.mud.yahoo.com>


I'll agree. it *has* to be somewhere... and if everyone isn't suffering the same thing... it can't directly be the backbone of this group.

Time to find out who, and what ISP and mail system.

-Later!  ?-WB-??? -- BABIC Computer Consulting.

--- On Sat, 2/28/09, Bob Devries <devries.bob at gmail.com> wrote:

From: Bob Devries <devries.bob at gmail.com>
Subject: Re: [Coco] multiple multiple mutltiple multiple messages
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Date: Saturday, February 28, 2009, 9:54 PM

Bill, the thing is that it only appears to be happening to *some* people 
here. I know it isn't happening to me, so the problem is in either the 
computers of the users who are having problems, or with the ISP that they 
are connected to.

If the problem lay with the malted media server, we would surely all suffer. 
Similarly if the problem is with the Yahoo server, all the Yahoo subscribers 
would have the problem.

My $0.02

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Bill Barnes" <da3m0n_slay3r at yahoo.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Sunday, March 01, 2009 1:41 PM
Subject: Re: [Coco] multiple multiple mutltiple multiple messages


Surely Bob,I doubt that you are personally sending messages multiple times, 
yet I am getting doubles most of the time from you. [exact same format, 
exact same headers.] There must be some other problem... I can only 
speculate myself, that something is echoing back what it receives... wish I 
knew exactly what it was...

-Later!? -WB- -- BABIC Computer Consulting.

--- On Sat, 2/28/09, Bob Devries <devries.bob at gmail.com> wrote:

From: Bob Devries <devries.bob at gmail.com>
Subject: Re: [Coco] multiple multiple mutltiple multiple messages
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Date: Saturday, February 28, 2009, 8:57 PM

Hmm, the only time I ever get multiple messages, is (a) if my connection to
my mail server terminates before the delete command is sent, and (b) if
someone sends the message multiple times (Yes, that does happen).

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Jim Hickle" <jlhickle at yahoo.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Sunday, March 01, 2009 10:42 AM
Subject: [Coco] multiple multiple mutltiple multiple messages


>I got this message 4 times, all marked with the same time, none of them
>from Yahoo.
>
>
> --- On Sat, 2/28/09, Bob Devries <devries.bob at gmail.com> wrote:
>
>> From: Bob Devries <devries.bob at gmail.com>
>> Subject: Re: [Coco] Another cable
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Date: Saturday, February 28, 2009, 3:51 PM
>> The Orchestra-90 has two RCA (phono) type sockets for left
>> and right stereo output. The Speech Sound Cartridge has
>> none.
>>
>> --
>> Regards, Bob Devries, Dalby, Queensland, Australia
>>
>> Isaiah 50:4 The sovereign Lord has given me
>> the capacity to be his spokesman,
>> so that I know how to help the weary.
>>
>> website: http://www.home.gil.com.au/~bdevasl
>> my blog: http://bdevries.invigorated.org/
>>
>> ----- Original Message ----- From: "Bill Barnes"
>> <da3m0n_slay3r at yahoo.com>
>> To: "CoCoList for Color Computer Enthusiasts"
>> <coco at maltedmedia.com>
>> Sent: Sunday, March 01, 2009 6:04 AM
>> Subject: Re: [Coco] Another cable
>>
>>
>> Sounds like a regular run of the mill cable that allows you
>> to say hook up a portable CD player via headphone jack into
>> the back of a component stereo or cassette deck, OR from
>> that cassette deck into the aux input of a soundcard. There
>> is obviously more uses, but these are a couple that come to
>> mind. Can't remember the orc90 or ssc external
>> connections.
>>
>> -Later! -WB- -- BABIC Computer Consulting.
>>
>> --- On Fri, 2/27/09, Willard Goosey
>> <goosey at virgo.sdc.org> wrote:
>>
>> From: Willard Goosey <goosey at virgo.sdc.org>
>> Subject: Re: [Coco] Another cable
>> To: "CoCoList for Color Computer Enthusiasts"
>> <coco at maltedmedia.com>
>> Date: Friday, February 27, 2009, 11:35 AM
>>
>>
>> -----Inline Attachment Follows-----
>>
>> On Thu, Feb 26, 2009 at 07:25:40PM -0500, Bill wrote:
>> > Speaking of cables, I just found another one, it has 2
>> RCA plugs on one end
>> > and a stereo mini-jack on the other. What do you
>> supposed that is for? I got
>> > it with a coco cassette I purchased. (Cassette is NOT
>> a stereo)
>>
>> Probably just a connector-converter cable... Mine is:
>> rca-shield - rca-shield - top jack connector
>> rca-white-center - bottom jack connector
>> rca-red-center - center jack connector
>>
>>
>> |||######
>> rca = ====|||########
>> |||######
>> ^ ^
>> center shield
>>
>>
>> jack: ^
>> | bottom
>> -
>> | middle
>> -
>> | top
>> ===
>> ===
>>
>>
>> And I'll have you know I had to dissasemble my
>> Amiga's wiring to get
>> to this. (there, it converts the Amiga's RCA audio out,
>> with a gender
>> bender, to the mini-jack so I could hook up a set of PC
>> powered
>> speakers. There is also another one converting a Linux
>> box's
>> mini-jack to RCA so it can be hooked into my stereo
>> system.)
>>
>> Used to also be able to get this in a little (~ 1"
>> long) adaptor from
>> Radio Shack. Don't know if they still have'em or
>> not.
>>
>> Willard
>> -- Willard Goosey goosey at sdc.org
>> Socorro, New Mexico, USA
>> I search my heart and find Cimmeria, land of Darkness and
>> the Night.
>> -- R.E. Howard
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco





--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco 


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



      


From da3m0n_slay3r at yahoo.com  Thu Mar  5 14:40:20 2009
From: da3m0n_slay3r at yahoo.com (Bill Barnes)
Date: Thu, 5 Mar 2009 11:40:20 -0800 (PST)
Subject: [Coco] POLL: multiple message problem
Message-ID: <203706.64927.qm@web31108.mail.mud.yahoo.com>

Ok, I think we shoulf figure out here, who all has the multiple-copies problem: In doing so, can we identify our ISP and email service? ?With this data, we can see what is affected, and to what extent. (is is just an ISP, is it a specific email system? is it some link along the way?)I'll start.multiples problem: YES? ? ? ? ? ? ? ? ? ? ISP: Cox? ? ?eMail System: Yahoonow just need someone to keep track of it all, preferably someone who isn't caught in a multiples problem, any volunteers? It would be good to know this as we all can agree, it gets annoying and fills our inboxes way faster than normal, and needs to be fixed. I wanna read about and contribute to the CoCo, NOT get bogged down in multiples.
-Later!? -WB- ?? -- BABIC Computer Consulting.




      


From cwgordon at carolina.rr.com  Thu Mar  5 14:45:11 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 5 Mar 2009 14:45:11 -0500
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <203706.64927.qm@web31108.mail.mud.yahoo.com>
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
Message-ID: <003401c99dca$e5e1b9a0$b1a52ce0$@rr.com>

Well, I'm getting multiple messages in each of 3 echoes. I have time warner
cable as my ISP, and I use outlook

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Bill Barnes
> Sent: Thursday, March 05, 2009 2:40 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] POLL: multiple message problem
> 
> Ok, I think we shoulf figure out here, who all has the multiple-copies
> problem



From exwn8jef at gmail.com  Thu Mar  5 15:35:12 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Thu, 05 Mar 2009 15:35:12 -0500
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <203706.64927.qm@web31108.mail.mud.yahoo.com>
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
Message-ID: <49B03780.4010706@gmail.com>

no echoes here
I use gmail, insight ISP, and Thunderbird email client

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



Bill Barnes wrote:
> Ok, I think we shoulf figure out here, who all has the multiple-copies problem: In doing so, can we identify our ISP and email service?  With this data, we can see what is affected, and to what extent. (is is just an ISP, is it a specific email system? is it some link along the way?)I'll start.multiples problem: YES                    ISP: Cox     eMail System: Yahoonow just need someone to keep track of it all, preferably someone who isn't caught in a multiples problem, any volunteers? It would be good to know this as we all can agree, it gets annoying and fills our inboxes way faster than normal, and needs to be fixed. I wanna read about and contribute to the CoCo, NOT get bogged down in multiples.
> -Later!  -WB-    -- BABIC Computer Consulting.
>
>
>
>
>       
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>   


From msmcdoug at iinet.net.au  Thu Mar  5 15:36:50 2009
From: msmcdoug at iinet.net.au (Mark McDougall)
Date: Fri, 06 Mar 2009 07:36:50 +1100
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <003401c99dca$e5e1b9a0$b1a52ce0$@rr.com>
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
	<003401c99dca$e5e1b9a0$b1a52ce0$@rr.com>
Message-ID: <49B037E2.3020000@iinet.net.au>

Bill wrote:

> Well, I'm getting multiple messages in each of 3 echoes. I have time warner
> cable as my ISP, and I use outlook

I'm getting multiples in here and in the trs-80 yahoo group...

Regards,

-- 
|              Mark McDougall                | "Electrical Engineers do it
|  <http://members.iinet.net.au/~msmcdoug>   |   with less resistance!"


From cwgordon at carolina.rr.com  Thu Mar  5 15:44:35 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 5 Mar 2009 15:44:35 -0500
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <49B037E2.3020000@iinet.net.au>
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>	<003401c99dca$e5e1b9a0$b1a52ce0$@rr.com>
	<49B037E2.3020000@iinet.net.au>
Message-ID: <004801c99dd3$350a7d70$9f1f7850$@rr.com>

Maybe I should have been clearer...

These are the echoes I get (and usually get multiples on)

Coco at maltedmedia.com
RainbowArchive at yahoogroups.com
ColorComputer at yahoogroups.com


> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Mark McDougall
> Sent: Thursday, March 05, 2009 3:37 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] POLL: multiple message problem
> 
> I'm getting multiples in here and in the trs-80 yahoo group...



From coconut at pritchard.ca  Thu Mar  5 16:00:20 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Thu, 5 Mar 2009 15:00:20 -0600
Subject: [Coco] Pretty new screen
In-Reply-To: <002401c99d9c$36cbe180$a463a480$@rr.com>
References: <002401c99d9c$36cbe180$a463a480$@rr.com>
Message-ID: <1806abd60903051300i4aa86361vb271aeab41345749@mail.gmail.com>

Ack, it is the Green and Orange screen of death...  Run...  roflmao...  I
have no clue.

On Thu, Mar 5, 2009 at 8:11 AM, Bill <cwgordon at carolina.rr.com> wrote:

> I woke up this morning and turned on my Coco, and I have a pretty new
> screen. Please look at http://www.sq1bbs.com/coco/coco-scr.jpg (this is a
> close duplicate of the screen) and see if you can (maybe) figure out what's
> wrong. I'm sure that there are some Cocoists who have seen this before.
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From coconut at pritchard.ca  Thu Mar  5 16:07:30 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Thu, 5 Mar 2009 15:07:30 -0600
Subject: [Coco] '68' Micro Journal
In-Reply-To: <1iw3g91.1abu5bvef4sg6M%tlindner@macmess.org>
References: <C88FA3BC-DB27-4E12-88FD-F9A15CB5A794@pritchard.ca>
	<1iw3g91.1abu5bvef4sg6M%tlindner@macmess.org>
Message-ID: <1806abd60903051307i627a60d4p5b16964081e40299@mail.gmail.com>

If you find them then great, cause it will save me the time of scanning
every last one of them, also open up the possibility of finding a new owner
for the originals.  Because having someone burn them at the end of my life
as Tim Fadden suggested sounds like a horrible thing to have happen to said
magazines, worse than cutting them down the spine if you as me.  Of course
cutting them down the spine may actually be more ummm... whats the term for
humane in reference to a book or magazine?  LOL!

Plus after skimming through the first year, it would seem that posting the
'68' Micro Journal collection for others to gain access to, would be in line
with the whole philosphy behind the magazine.

On Thu, Mar 5, 2009 at 9:18 AM, tim lindner <tlindner at macmess.org> wrote:

> Ryan Pritchard <coconut at pritchard.ca> wrote:
>
> > That's awesome!  Where does one find them?
>
> I thought they were on the web somewhere. But apearently not.
>
> I'll try to find my copy, and upload them somewhere.
>
> --
> tim lindner
> tlindner at macmess.org                                              Bright
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From t.fadden at cox.net  Thu Mar  5 16:40:07 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Thu, 05 Mar 2009 14:40:07 -0700
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <203706.64927.qm@web31108.mail.mud.yahoo.com>
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
Message-ID: <49B046B7.1030907@cox.net>

No duplicate emails for me: pop.west.cox.net

Tim

Bill Barnes wrote:
> Ok, I think we shoulf figure out here, who all has the multiple-copies problem: In doing so, can we identify our ISP and email service?  With this data, we can see what is affected, and to what extent. (is is just an ISP, is it a specific email system? is it some link along the way?)I'll start.multiples problem: YES                    ISP: Cox     eMail System: Yahoonow just need someone to keep track of it all, preferably someone who isn't caught in a multiples problem, any volunteers? It would be good to know this as we all can agree, it gets annoying and fills our inboxes way faster than normal, and needs to be fixed. I wanna read about and contribute to the CoCo, NOT get bogged down in multiples.
> -Later!  -WB-    -- BABIC Computer Consulting.
>
>
>
>
>       
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From badfrog at gmail.com  Thu Mar  5 16:49:29 2009
From: badfrog at gmail.com (Sean)
Date: Thu, 5 Mar 2009 15:49:29 -0600
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <49B046B7.1030907@cox.net>
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
	<49B046B7.1030907@cox.net>
Message-ID: <9efa17da0903051349q66861a9egd20d190039c39400@mail.gmail.com>

No problems here, Gmail from both Charter and Nuvox.

On Thu, Mar 5, 2009 at 3:40 PM, Tim Fadden <t.fadden at cox.net> wrote:
> No duplicate emails for me: pop.west.cox.net
>
> Tim
>
> Bill Barnes wrote:
>>
>> Ok, I think we shoulf figure out here, who all has the multiple-copies
>> problem: In doing so, can we identify our ISP and email service? ?With this
>> data, we can see what is affected, and to what extent. (is is just an ISP,
>> is it a specific email system? is it some link along the way?)I'll
>> start.multiples problem: YES ? ? ? ? ? ? ? ? ? ?ISP: Cox ? ? eMail System:
>> Yahoonow just need someone to keep track of it all, preferably someone who
>> isn't caught in a multiples problem, any volunteers? It would be good to
>> know this as we all can agree, it gets annoying and fills our inboxes way
>> faster than normal, and needs to be fixed. I wanna read about and contribute
>> to the CoCo, NOT get bogged down in multiples.
>> -Later! ?-WB- ? ?-- BABIC Computer Consulting.
>>
>>
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From operator at coco3.com  Thu Mar  5 17:15:02 2009
From: operator at coco3.com (Roger Taylor)
Date: Thu, 05 Mar 2009 16:15:02 -0600
Subject: [Coco] CoCo Wireless RS-232 Pak
In-Reply-To: <393A84BA-F04D-47C5-A522-994CEBEDA49F@tee-boy.com>
References: <393A84BA-F04D-47C5-A522-994CEBEDA49F@tee-boy.com>
Message-ID: <20090305221537.8155420A15@qs281.pair.com>

At 07:07 AM 3/5/2009, you wrote:
>>Hey guys, magically, the former wireless pak prototype became a
>>production grade beauty, so I updated the inside-peek picture which
>>has been scaled down to tease with Mark a little more. :) If you
>>squint just right you could get a headache. ;)
>
>Roger,
>
>I also noticed another bit of magic on your website, specifically a
>disappearing act.   The reference to the bitbanger features of CoCoNet
>have been removed.  Does this mean that CoCoNet will only support your
>wireless pak, and that you won't be releasing support for the bitbanger?
>
>Regards,
>Boisy G. Pitre


No, it doesn't mean that at all.  I was editing the site pretty late 
and decided to finish the text copy later.

-- 
Roger Taylor

http://www.wordofthedayonline.com



From mdelyea at gmail.com  Thu Mar  5 17:25:04 2009
From: mdelyea at gmail.com (mike delyea)
Date: Thu, 5 Mar 2009 17:25:04 -0500
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <9efa17da0903051349q66861a9egd20d190039c39400@mail.gmail.com>
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
	<49B046B7.1030907@cox.net>
	<9efa17da0903051349q66861a9egd20d190039c39400@mail.gmail.com>
Message-ID: <1b52e6c80903051425y38a2ec97q2bddedf6c794440a@mail.gmail.com>

Problem - nope
ISP - Sympatico
email - gmail

On Thu, Mar 5, 2009 at 4:49 PM, Sean <badfrog at gmail.com> wrote:
> No problems here, Gmail from both Charter and Nuvox.
>
> On Thu, Mar 5, 2009 at 3:40 PM, Tim Fadden <t.fadden at cox.net> wrote:
>> No duplicate emails for me: pop.west.cox.net
>>
>> Tim
>>
>> Bill Barnes wrote:
>>>
>>> Ok, I think we shoulf figure out here, who all has the multiple-copies
>>> problem: In doing so, can we identify our ISP and email service? ?With this
>>> data, we can see what is affected, and to what extent. (is is just an ISP,
>>> is it a specific email system? is it some link along the way?)I'll
>>> start.multiples problem: YES ? ? ? ? ? ? ? ? ? ?ISP: Cox ? ? eMail System:
>>> Yahoonow just need someone to keep track of it all, preferably someone who
>>> isn't caught in a multiples problem, any volunteers? It would be good to
>>> know this as we all can agree, it gets annoying and fills our inboxes way
>>> faster than normal, and needs to be fixed. I wanna read about and contribute
>>> to the CoCo, NOT get bogged down in multiples.
>>> -Later! ?-WB- ? ?-- BABIC Computer Consulting.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>
>>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From operator at coco3.com  Thu Mar  5 17:37:53 2009
From: operator at coco3.com (Roger Taylor)
Date: Thu, 05 Mar 2009 16:37:53 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
Message-ID: <20090305223830.7949020A14@qs281.pair.com>

At 07:43 AM 3/5/2009, you wrote:
>>Do any of your items work the same under Color BASIC as they do for
>>the NitrOS-9 hackjob of OS-9 ? Has anything in NitrOS-9 been
>>changed from the original OS-9 just to get one of your gadgets to 1)
>>function better, 2) just function, 3) have a practical use?
>
>Roger,
>
>There can be no other way to take the "NitrOS-9 hackjob of OS-9"
>comment above as anything other than a slight and a jab at the project.

Not true, Boisy.  If this were true, Mark's 6551 bashing or the 
comment about no new products should use the 6551 would be the same 
types of jabs.  It doesn't matter, anyway.  I use NitrOS-9 and it's 
awesome.  People will use my pak and enjoy using it no matter what we 
say here on the list.  It won't make a difference in what my product 
can do.  Yes, I plan to provide OS-9 support.




>In the "CoCoNutz!" Christmas 2005 newsletter there is a column titled
>"A Talk With Roger Taylor of CoCo 3.com."  In reference to the
>interview question "What is your favorite operating system? Are you a
>Linux guy or Microsoft guy?" Your response on the CoCo was:
>
>"With the CoCo, my favorite OS would probably have to be NitrOS-9
>which is a highly-customized version of OS-9  Level II.  Although I've
>written almost everything for Disk BASIC, I prefer the power of OS-9
>when I use the CoCo."

Exactly.  And I've written quite a bit of software for OS-9.



>This statement is incongruent with your current view that NitrOS-9 is
>a hack job.  Can you please explain what happened between 2005 and now?

NitrOS-9 *is* a hack job, Boisy.  With you being the main person 
behind NitrOS-9 these days (you are, correct?) and with all of 
Cloud-9's products, Is it possible perhaps that NitrOS-9 might be the 
better OS for Cloud-9 products than Disk BASIC, or perhaps Disk BASIC 
might be the better OS for non Cloud-9 products?

Mark wanted to know how my product performed under NitrOS-9, and if 
my answer was anything less than "it works PERFECT" I were to be 
bashed for not being "up to date" on things, when in fact I don't 
think 100% of the CoCo world uses NitrOS-9 or has even heard of it 
yet.  If I had asked how well does your stuff perform under the 
original OS-9, what kind of answer should I expect.

And I still don't see what the overall point here is.  I've got 
wireless RS-232 paks for sale.  All existing 6551 CoCo software can 
use it.  That much is true.  All the other chit chat is not going to 
make a hill of beans difference in what the pak will do or where this 
system will go over time.

Long Live The CoCo,
Roger Taylor


-- 
Roger Taylor

http://www.wordofthedayonline.com



From snhirsch at gmail.com  Thu Mar  5 17:39:04 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Thu, 5 Mar 2009 17:39:04 -0500 (EST)
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <203706.64927.qm@web31108.mail.mud.yahoo.com>
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
Message-ID: <alpine.DEB.2.00.0903051737340.32155@duo>

On Thu, 5 Mar 2009, Bill Barnes wrote:

> Ok, I think we shoulf figure out here, who all has the multiple-copies 
> problem: In doing so, can we identify our ISP and email service?

ISP: Burlington Telecom

Mail: gmail, picked up by fetchmail using secure POP

No problem with multiple messages.  Never.


-- 


From operator at coco3.com  Thu Mar  5 17:39:04 2009
From: operator at coco3.com (Roger Taylor)
Date: Thu, 05 Mar 2009 16:39:04 -0600
Subject: [Coco] Pretty new screen
In-Reply-To: <002401c99d9c$36cbe180$a463a480$@rr.com>
References: <002401c99d9c$36cbe180$a463a480$@rr.com>
Message-ID: <20090305223936.BE78220A13@qs281.pair.com>

At 08:11 AM 3/5/2009, you wrote:
>I woke up this morning and turned on my Coco, and I have a pretty new
>screen. Please look at http://www.sq1bbs.com/coco/coco-scr.jpg (this is a
>close duplicate of the screen) and see if you can (maybe) figure out what's
>wrong. I'm sure that there are some Cocoists who have seen this before.


It kinda looks like a bad DRAM chip to me.


-- 
Roger Taylor

http://www.wordofthedayonline.com



From brucewcalkins at charter.net  Thu Mar  5 17:40:52 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Thu, 5 Mar 2009 17:40:52 -0500
Subject: [Coco] POLL: multiple message problem
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
	<003401c99dca$e5e1b9a0$b1a52ce0$@rr.com>
Message-ID: <ACA116F32C8D44168AD1E210A2EDA485@speedy>

>----- Original Message ----- 
> Well, I'm getting multiple messages in each of 3 echoes. I have time 
> warner
> cable as my ISP, and I use outlook
>
>> -----Original Message-----
>> Ok, I think we shoulf figure out here, who all has the multiple-copies
>> problem



Well, I have Charter Cable as my ISP and ATM I am not having any problems 
with multiple messages.

Bruce W. 



From devries.bob at gmail.com  Thu Mar  5 18:26:04 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Fri, 6 Mar 2009 09:26:04 +1000
Subject: [Coco] POLL: multiple message problem
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
Message-ID: <007901c99de9$c3b26900$0701a8c0@master>

Well,
I have no problems with duplicate messages.

I'm on ADSL with www.itel.com.au (iTel Community Telco, Ipswich, Australia)

I'm using gmail, but use their POP3 email service

I'm using Outlook Express 6

I'm only subscribed to coco at maltedmedia since it echoes the messages from 
the Yahoo coco groups.


--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Bill Barnes" <da3m0n_slay3r at yahoo.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Friday, March 06, 2009 5:40 AM
Subject: Re: [Coco] POLL: multiple message problem


Ok, I think we shoulf figure out here, who all has the multiple-copies 
problem: In doing so, can we identify our ISP and email service? With this 
data, we can see what is affected, and to what extent. (is is just an ISP, 
is it a specific email system? is it some link along the way?)I'll 
start.multiples problem: YES ISP: Cox eMail System: Yahoonow just need 
someone to keep track of it all, preferably someone who isn't caught in a 
multiples problem, any volunteers? It would be good to know this as we all 
can agree, it gets annoying and fills our inboxes way faster than normal, 
and needs to be fixed. I wanna read about and contribute to the CoCo, NOT 
get bogged down in multiples.
-Later! -WB- -- BABIC Computer Consulting.






--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco 



From rbihler at msn.com  Thu Mar  5 18:44:44 2009
From: rbihler at msn.com (RON BIHLER)
Date: Thu, 5 Mar 2009 16:44:44 -0700
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <9efa17da0903051349q66861a9egd20d190039c39400@mail.gmail.com>
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
	<49B046B7.1030907@cox.net> 
	<9efa17da0903051349q66861a9egd20d190039c39400@mail.gmail.com>
Message-ID: <BAY118-W1515740897A721B7407132AFA40@phx.gbl>


No dups, with MSN or Thunderbird

 

Ron
 

 

 

 

 

> >> Ok, I think we shoulf figure out here, who all has the multiple-copies
> >> problem: In doing so, can we identify our ISP and email service?  With this
> >> data, we can see what is affected, and to what extent. (is is just an ISP,
> >> is it a specific email system? is it some link along the way?)I'll
> >> start.multiples problem: YES                    ISP: Cox     eMail System:
> >> Yahoonow just need someone to keep track of it all, preferably someone who
> >> isn't caught in a multiples problem, any volunteers? It would be good to
> >> know this as we all can agree, it gets annoying and fills our inboxes way
> >> faster than normal, and needs to be fixed. I wanna read about and contribute
> >> to the CoCo, NOT get bogged down in multiples.
> >> -Later!  -WB-    -- BABIC Computer Consulting.
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> http://five.pairlist.net/mailman/listinfo/coco
> >>
> >>
> >>
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> >
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From boisy at tee-boy.com  Thu Mar  5 19:03:55 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Thu, 5 Mar 2009 18:03:55 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <20090305223830.7949020A14@qs281.pair.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
	<20090305223830.7949020A14@qs281.pair.com>
Message-ID: <6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>

On Mar 5, 2009, at 4:37 PM, Roger Taylor wrote:
> NitrOS-9 *is* a hack job, Boisy.  With you being the main person  
> behind NitrOS-9 these days (you are, correct?) and with all of  
> Cloud-9's products, Is it possible perhaps that NitrOS-9 might be  
> the better OS for Cloud-9 products than Disk BASIC, or perhaps Disk  
> BASIC might be the better OS for non Cloud-9 products?

Roger,

My understanding of the meaning of the word "hack job" is embodied by  
the following definitions that I pulled from www.urbandictionary.com:

1. A procedure or operation performed by someone with inadequate skill  
or knowlege of the subject.
2. Something done shoddily or ineptly.
3. A crude and improvised or temporary solution to a problem, designed  
to be more functional and timely than precise, durable or of good  
quality.

What is your definition of the word?  I hope it's not one of the above.

> And I still don't see what the overall point here is.  I've got  
> wireless RS-232 paks for sale.  All existing 6551 CoCo software can  
> use it.  That much is true.  All the other chit chat is not going to  
> make a hill of beans difference in what the pak will do or where  
> this system will go over time.

To be clear: Mark's critique of the technical merits of your wireless  
pak doesn't concern or interest me in the least.  I don't have a dog  
in that hunt.

What does concern me (and what you've failed to address thus far in  
your replies) is that you chose this venue, an open forum, to post a  
message indicating that you were considering giving away a product  
whose functionality mimics a product that I sell. Not only does this  
position conflict with statements you've made in the past about not  
wanting to compete with DriveWire, but it also brings into question  
your motivation for requests that you made to me some months ago to  
test software under DriveWire (which I obliged to do and which ran  
fine), under the guise that you were going to buy a copy if it worked  
(which you never did).

As someone else pointed out, this is America and laissez faire  
capitalism reigns.  You have every right to change your mind and  
create a competing product in an already small market, no matter what  
your motivation (money, ego, or both).  I don't hold patents on  
DriveWire, and while it's a nice little product that has done well for  
me, it is not my day job, so loosing sales to your product is not a  
matter of taking food from my table.  But if you're going to compete,  
compete fairly. Don't mislead people and take up their time for your  
benefit at their expense.  It is anti-competitive and it's wrong.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From goosey at virgo.sdc.org  Thu Mar  5 19:41:50 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Thu, 5 Mar 2009 17:41:50 -0700
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <49AE3514.9080606@aurigae.demon.co.uk>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>
	<00a501c99c56$916e3850$0701a8c0@master>
	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
	<49AE3514.9080606@aurigae.demon.co.uk>
Message-ID: <20090306004150.GB14496@virgo.sdc.org>

On Wed, Mar 04, 2009 at 08:00:20AM +0000, Phill Harvey-Smith wrote:
> Willard Goosey wrote:
> >The trick is getting the connectors... :-(
> 
> For some experements I did a while back, I used PC 8 bit ISA connectors 
> and cut them down. Last time I checked these where still available.

True.  

Maybe when I get around to making a new case for my Glenside IDE, I'll
chop up a couple of ISA connectors and solder them on, and see how
good a y-cable it is.

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From goosey at virgo.sdc.org  Thu Mar  5 19:44:15 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Thu, 5 Mar 2009 17:44:15 -0700
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <49AE7E4C.2000806@comcast.net>
References: <49AD9E55.6000804@iinet.net.au>
	<5d802cd0903031340k45573f1bob557d639026d1d55@mail.gmail.com>
	<49ADA6C2.6000006@iinet.net.au>
	<20090304055639.GA25102@virgo.sdc.org>
	<49AE7E4C.2000806@comcast.net>
Message-ID: <20090306004415.GC14496@virgo.sdc.org>

On Wed, Mar 04, 2009 at 08:12:44AM -0500, David Hazelton wrote:

> I have one built by Conect (IIRC)  Since when I bought it I only used 
> OS9, It worked great.  I did get better throughput then the RS-PAK.  I 
> did mostly Zmodem for file transfers, but I also logged in to VAX 
> machines and Unix based Machines at Work.  

I bet it did!  Zmodem likes uarts with fat FIFOs.  Under OS-9 with a
6551, I couldn't ever get error-free zmodem downloads faster than
4800. :-(

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From fwp at deepthought.com  Thu Mar  5 20:42:02 2009
From: fwp at deepthought.com (Frank Pittel)
Date: Thu, 5 Mar 2009 19:42:02 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
	<20090305223830.7949020A14@qs281.pair.com>
	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
Message-ID: <20090306014202.GL7702@warlock.deepthought.com>

On Thu, Mar 05, 2009 at 06:03:55PM -0600, Boisy Pitre wrote:
> On Mar 5, 2009, at 4:37 PM, Roger Taylor wrote:
>> NitrOS-9 *is* a hack job, Boisy.  With you being the main person  
>> behind NitrOS-9 these days (you are, correct?) and with all of  
>> Cloud-9's products, Is it possible perhaps that NitrOS-9 might be the 
>> better OS for Cloud-9 products than Disk BASIC, or perhaps Disk BASIC 
>> might be the better OS for non Cloud-9 products?
>
> Roger,
>
> My understanding of the meaning of the word "hack job" is embodied by  
> the following definitions that I pulled from www.urbandictionary.com:
>
> 1. A procedure or operation performed by someone with inadequate skill  
> or knowlege of the subject.
> 2. Something done shoddily or ineptly.
> 3. A crude and improvised or temporary solution to a problem, designed  
> to be more functional and timely than precise, durable or of good  
> quality.
>
> What is your definition of the word?  I hope it's not one of the above.

I would normally use definition #2 but one and three would work.

>> And I still don't see what the overall point here is.  I've got  
>> wireless RS-232 paks for sale.  All existing 6551 CoCo software can  
>> use it.  That much is true.  All the other chit chat is not going to  
>> make a hill of beans difference in what the pak will do or where this 
>> system will go over time.
>
> To be clear: Mark's critique of the technical merits of your wireless  
> pak doesn't concern or interest me in the least.  I don't have a dog in 
> that hunt.
>
> What does concern me (and what you've failed to address thus far in your 
> replies) is that you chose this venue, an open forum, to post a message 
> indicating that you were considering giving away a product whose 
> functionality mimics a product that I sell. Not only does this position 
> conflict with statements you've made in the past about not wanting to 
> compete with DriveWire, but it also brings into question your motivation 
> for requests that you made to me some months ago to test software under 
> DriveWire (which I obliged to do and which ran fine), under the guise 
> that you were going to buy a copy if it worked (which you never did).
>
> As someone else pointed out, this is America and laissez faire  
> capitalism reigns.  You have every right to change your mind and create a 
> competing product in an already small market, no matter what your 
> motivation (money, ego, or both).  I don't hold patents on DriveWire, and 
> while it's a nice little product that has done well for me, it is not my 
> day job, so loosing sales to your product is not a matter of taking food 
> from my table.  But if you're going to compete, compete fairly. Don't 
> mislead people and take up their time for your benefit at their expense.  
> It is anti-competitive and it's wrong.

It also make continue support, help, etc unlikely.


From exwn8jef at gmail.com  Thu Mar  5 19:59:47 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Thu, 05 Mar 2009 19:59:47 -0500
Subject: [Coco] DriveWire
In-Reply-To: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com><6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com><00a501c99c56$916e3850$0701a8c0@master><fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com><20090304060744.GC25102@virgo.sdc.org>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
Message-ID: <49B07583.2010308@gmail.com>

Boisy,
I was looking at Cloud 9 site, but didn't see any kind of descripton for 
DriveWire yet. I don't have a clue what it is. What is DriveWire if you 
don't mind me asking? I am assuming that it is some kind of file 
transfer protocal using some kind of cable from the PC to the CoCo? I 
look forward to hearing about it. Thanks...

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



From mmarlette at frontiernet.net  Thu Mar  5 20:03:01 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Fri, 6 Mar 2009 01:03:01 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <1641967837.39921236301376341.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

Willard,

Exactly my point. Zmodem by nature will re-xmit the loss but you can see that your effective baud rate goes in the tank.

Was this Zmodem xfer saved to a hard disk or floppy?

Regards,

Mark
Cloud-9


----- Original Message -----
From: "Willard Goosey" <goosey at virgo.sdc.org>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, March 5, 2009 6:44:15 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

On Wed, Mar 04, 2009 at 08:12:44AM -0500, David Hazelton wrote:

> I have one built by Conect (IIRC)  Since when I bought it I only used 
> OS9, It worked great.  I did get better throughput then the RS-PAK.  I 
> did mostly Zmodem for file transfers, but I also logged in to VAX 
> machines and Unix based Machines at Work.  

I bet it did!  Zmodem likes uarts with fat FIFOs.  Under OS-9 with a
6551, I couldn't ever get error-free zmodem downloads faster than
4800. :-(

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From goosey at virgo.sdc.org  Thu Mar  5 20:15:45 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Thu, 5 Mar 2009 18:15:45 -0700
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <379248463.77591236181220250.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
References: <1647102443.77031236181099762.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<379248463.77591236181220250.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <20090306011544.GD14496@virgo.sdc.org>

On Wed, Mar 04, 2009 at 03:40:20PM +0000, Mark Marlette wrote:
> Willard,
> 
> The NitrOS-9/Driver is already written for a 16550 device. I have
> had a homebrew card running for almost 10yrs based upon that
> chipset.
> 
Cool.  I didn't know that.  Didn't one of the other hardware-seller
types -- don't remember who -- have a 16550 card built, and then
basically self-destruct over the software issues?

> Yes, it would break all the old term programs. A caveat of adding
> new technology to an old machine. Not a problem in NitrOS-9 as the
> driver/dd is not part of the actual program, when properly written.
> 
But V-TERM does such an AWESOME job of vt100 emulation -- it even does
double high/double wide correctly. Not to mention the fact that it can
handle anything EMACS throws at it, and nothing stress-tests a
terminal emulator like EMACS. :-)

I do understand your caveat.  Please understand that I did specify
BASIC terminal emulators.  

I would not use an OS-9 terminal program that did not go through the
proper descriptor/driver interface.

> The SuperBoard has a multi-function chip on it that has the 16550 in
> it. 

Nice...  If I had a job I'd get one.

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From t.fadden at cox.net  Thu Mar  5 20:18:51 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Thu, 05 Mar 2009 18:18:51 -0700
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <49B079FB.5010701@cox.net>

Hi Mark,

This is my throughput with zmodem also using scsisys 1.1 hard drive with 
modified os9, but not nitros. Using a Disto super II with a 4in1 card 
serial port.  I do have a bootable Nitros9 floppy with the scsisys 
drivers on them, so I could give it a shot with that, and let you know.  
>From my standpoint, the nitros9 floppy drivers lock up keyboard input, a 
feature I do not personally like.  I tend to type ahead a lot when doing 
stuff.  Even on High-end Sun servers running solaris. :-)

Tim

Mark Marlette wrote:
> Willard,
>
> Exactly my point. Zmodem by nature will re-xmit the loss but you can see that your effective baud rate goes in the tank.
>
> Was this Zmodem xfer saved to a hard disk or floppy?
>
> Regards,
>
> Mark
> Cloud-9
>
>
> ----- Original Message -----
> From: "Willard Goosey" <goosey at virgo.sdc.org>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Thursday, March 5, 2009 6:44:15 PM GMT -06:00 US/Canada Central
> Subject: Re: [Coco] 16550 wasRe:  RS232 paks
>
> On Wed, Mar 04, 2009 at 08:12:44AM -0500, David Hazelton wrote:
>
>   
>> I have one built by Conect (IIRC)  Since when I bought it I only used 
>> OS9, It worked great.  I did get better throughput then the RS-PAK.  I 
>> did mostly Zmodem for file transfers, but I also logged in to VAX 
>> machines and Unix based Machines at Work.  
>>     
>
> I bet it did!  Zmodem likes uarts with fat FIFOs.  Under OS-9 with a
> 6551, I couldn't ever get error-free zmodem downloads faster than
> 4800. :-(
>
> Willard
>   



From goosey at virgo.sdc.org  Thu Mar  5 20:20:13 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Thu, 5 Mar 2009 18:20:13 -0700
Subject: [Coco] Multi-Pak Interface question.
In-Reply-To: <1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>
	<00a501c99c56$916e3850$0701a8c0@master>
	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
Message-ID: <20090306012013.GE14496@virgo.sdc.org>

On Wed, Mar 04, 2009 at 02:45:00PM -0600, Ryan Pritchard wrote:
> If I am correct either of these connectors should do the trick for board
> mounting.
> 
> http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=EDC341402-ND
> 
> http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=EDC395402-ND

Cool. I'll have to look at these sometime when I have money. :-) :-(

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From mmarlette at frontiernet.net  Thu Mar  5 20:32:21 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Fri, 6 Mar 2009 01:32:21 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <690921055.46811236303022572.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <1326779178.47181236303141717.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

Tim,

You can if you like. I know what is going to happen already. :)

I thought there was a driver for the SCII, no halt, so that you didn't loose the data you were typing. Make sure you are using the correct one to get the benefit of the SCII's no halt.

Regards,

Mark




----- Original Message -----
From: "Tim Fadden" <t.fadden at cox.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, March 5, 2009 7:18:51 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

Hi Mark,

This is my throughput with zmodem also using scsisys 1.1 hard drive with 
modified os9, but not nitros. Using a Disto super II with a 4in1 card 
serial port.  I do have a bootable Nitros9 floppy with the scsisys 
drivers on them, so I could give it a shot with that, and let you know.  
>From my standpoint, the nitros9 floppy drivers lock up keyboard input, a 
feature I do not personally like.  I tend to type ahead a lot when doing 
stuff.  Even on High-end Sun servers running solaris. :-)

Tim

Mark Marlette wrote:
> Willard,
>
> Exactly my point. Zmodem by nature will re-xmit the loss but you can see that your effective baud rate goes in the tank.
>
> Was this Zmodem xfer saved to a hard disk or floppy?
>
> Regards,
>
> Mark
> Cloud-9
>
>
> ----- Original Message -----
> From: "Willard Goosey" <goosey at virgo.sdc.org>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Thursday, March 5, 2009 6:44:15 PM GMT -06:00 US/Canada Central
> Subject: Re: [Coco] 16550 wasRe:  RS232 paks
>
> On Wed, Mar 04, 2009 at 08:12:44AM -0500, David Hazelton wrote:
>
>   
>> I have one built by Conect (IIRC)  Since when I bought it I only used 
>> OS9, It worked great.  I did get better throughput then the RS-PAK.  I 
>> did mostly Zmodem for file transfers, but I also logged in to VAX 
>> machines and Unix based Machines at Work.  
>>     
>
> I bet it did!  Zmodem likes uarts with fat FIFOs.  Under OS-9 with a
> 6551, I couldn't ever get error-free zmodem downloads faster than
> 4800. :-(
>
> Willard
>   


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From boisy at tee-boy.com  Thu Mar  5 20:32:22 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Thu, 5 Mar 2009 19:32:22 -0600
Subject: [Coco] DriveWire
In-Reply-To: <49B07583.2010308@gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com><6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com><00a501c99c56$916e3850$0701a8c0@master><fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com><20090304060744.GC25102@virgo.sdc.org>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
Message-ID: <F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>

On Mar 5, 2009, at 6:59 PM, N8WQ wrote:

> Boisy,
> I was looking at Cloud 9 site, but didn't see any kind of descripton  
> for DriveWire yet. I don't have a clue what it is. What is DriveWire  
> if you don't mind me asking? I am assuming that it is some kind of  
> file transfer protocal using some kind of cable from the PC to the  
> CoCo? I look forward to hearing about it. Thanks...

Alan,

You described it correctly.  It's a software package that gives you  
BASIC and NitrOS-9 drivers to access your PC, Mac or Linux system as a  
storage device over the CoCo's bitbanger.

I removed the page for DriveWire 2, which will be replaced by  
DriveWire 3 and made available later this month. At that time a new  
page for DriveWire 3 will go up.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com

>
> Alan Jones
>
> -- 
> N8WQ - Canal Winchester, Ohio
> http://exwn8jef.googlepages.com/home
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From devries.bob at gmail.com  Thu Mar  5 20:32:59 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Fri, 6 Mar 2009 11:32:59 +1000
Subject: [Coco] 16550 wasRe:  RS232 paks
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<49B079FB.5010701@cox.net>
Message-ID: <002401c99dfb$a25373a0$0701a8c0@master>

I'm sure I have run ZMODEM on NitrOS9 using the 9600 baud setting. I have a 
Disto SCII with 4-in-1. There didn't appear to be too much difference saving 
to the floppy or hard disc, however, that was using the No-Halt drivers as 
supplied by Disto.

Of course, I *usually* saved to RamDisk, if the file was not too large, but 
then, a file bigger than 32K was considered large back then.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Tim Fadden" <t.fadden at cox.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Friday, March 06, 2009 11:18 AM
Subject: Re: [Coco] 16550 wasRe: RS232 paks


> Hi Mark,
>
> This is my throughput with zmodem also using scsisys 1.1 hard drive with 
> modified os9, but not nitros. Using a Disto super II with a 4in1 card 
> serial port.  I do have a bootable Nitros9 floppy with the scsisys drivers 
> on them, so I could give it a shot with that, and let you know.
>>From my standpoint, the nitros9 floppy drivers lock up keyboard input, a
> feature I do not personally like.  I tend to type ahead a lot when doing 
> stuff.  Even on High-end Sun servers running solaris. :-)
>
> Tim
>
> Mark Marlette wrote:
>> Willard,
>>
>> Exactly my point. Zmodem by nature will re-xmit the loss but you can see 
>> that your effective baud rate goes in the tank.
>>
>> Was this Zmodem xfer saved to a hard disk or floppy?
>>
>> Regards,
>>
>> Mark
>> Cloud-9
>>
>>
>> ----- Original Message -----
>> From: "Willard Goosey" <goosey at virgo.sdc.org>
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Sent: Thursday, March 5, 2009 6:44:15 PM GMT -06:00 US/Canada Central
>> Subject: Re: [Coco] 16550 wasRe:  RS232 paks
>>
>> On Wed, Mar 04, 2009 at 08:12:44AM -0500, David Hazelton wrote:
>>
>>
>>> I have one built by Conect (IIRC)  Since when I bought it I only used 
>>> OS9, It worked great.  I did get better throughput then the RS-PAK.  I 
>>> did mostly Zmodem for file transfers, but I also logged in to VAX 
>>> machines and Unix based Machines at Work.
>>
>> I bet it did!  Zmodem likes uarts with fat FIFOs.  Under OS-9 with a
>> 6551, I couldn't ever get error-free zmodem downloads faster than
>> 4800. :-(
>>
>> Willard
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From goosey at virgo.sdc.org  Thu Mar  5 20:36:16 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Thu, 5 Mar 2009 18:36:16 -0700
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
References: <1641967837.39921236301376341.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <20090306013616.GF14496@virgo.sdc.org>

On Fri, Mar 06, 2009 at 01:03:01AM +0000, Mark Marlette wrote:
> Willard,
> 
> Exactly my point. Zmodem by nature will re-xmit the loss but you can
> see that your effective baud rate goes in the tank.
> 
Yep.  I used to have 10-12 computers wired together with a web of
rs232 cables.  I'm quite familiar with the issues. 

Fortunately, I finally got the vaguely-modern machines on ethernet,
and the remaining serial lines are much saner now.

> Was this Zmodem xfer saved to a hard disk or floppy?

It was many many moons ago, but I'm pretty sure it was to a hard disk.
If not, it was to a RAM disk.  It was almost certainly over a direct
(null-modem) link to a linux box, rather than a modem.

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From devries.bob at gmail.com  Thu Mar  5 20:36:21 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Fri, 6 Mar 2009 11:36:21 +1000
Subject: [Coco] 16550 wasRe:  RS232 paks
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<49B079FB.5010701@cox.net>
Message-ID: <002d01c99dfc$08234b60$0701a8c0@master>

Of course, I have no idea exactly what the THROUGHPUT was in CPS with that 
setup.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Tim Fadden" <t.fadden at cox.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Friday, March 06, 2009 11:18 AM
Subject: Re: [Coco] 16550 wasRe: RS232 paks


> Hi Mark,
>
> This is my throughput with zmodem also using scsisys 1.1 hard drive with 
> modified os9, but not nitros. Using a Disto super II with a 4in1 card 
> serial port.  I do have a bootable Nitros9 floppy with the scsisys drivers 
> on them, so I could give it a shot with that, and let you know.
>>From my standpoint, the nitros9 floppy drivers lock up keyboard input, a
> feature I do not personally like.  I tend to type ahead a lot when doing 
> stuff.  Even on High-end Sun servers running solaris. :-)
>
> Tim
>
> Mark Marlette wrote:
>> Willard,
>>
>> Exactly my point. Zmodem by nature will re-xmit the loss but you can see 
>> that your effective baud rate goes in the tank.
>>
>> Was this Zmodem xfer saved to a hard disk or floppy?
>>
>> Regards,
>>
>> Mark
>> Cloud-9
>>
>>
>> ----- Original Message -----
>> From: "Willard Goosey" <goosey at virgo.sdc.org>
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Sent: Thursday, March 5, 2009 6:44:15 PM GMT -06:00 US/Canada Central
>> Subject: Re: [Coco] 16550 wasRe:  RS232 paks
>>
>> On Wed, Mar 04, 2009 at 08:12:44AM -0500, David Hazelton wrote:
>>
>>
>>> I have one built by Conect (IIRC)  Since when I bought it I only used 
>>> OS9, It worked great.  I did get better throughput then the RS-PAK.  I 
>>> did mostly Zmodem for file transfers, but I also logged in to VAX 
>>> machines and Unix based Machines at Work.
>>
>> I bet it did!  Zmodem likes uarts with fat FIFOs.  Under OS-9 with a
>> 6551, I couldn't ever get error-free zmodem downloads faster than
>> 4800. :-(
>>
>> Willard
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From goosey at virgo.sdc.org  Thu Mar  5 20:44:16 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Thu, 5 Mar 2009 18:44:16 -0700
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <002401c99dfb$a25373a0$0701a8c0@master>
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<49B079FB.5010701@cox.net> <002401c99dfb$a25373a0$0701a8c0@master>
Message-ID: <20090306014416.GG14496@virgo.sdc.org>

On Fri, Mar 06, 2009 at 11:32:59AM +1000, Bob Devries wrote:
> I'm sure I have run ZMODEM on NitrOS9 using the 9600 baud setting. I have a 

Well, NitrOS helps a *lot*.  I vaguely remember Boisie ranting about
how utterly horrible the original OS-9LII's interrupt-handling code
is.

Even with the 6809 versions, it's noticably more responsive.

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From boisy at tee-boy.com  Thu Mar  5 20:57:18 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Thu, 5 Mar 2009 19:57:18 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <20090306014416.GG14496@virgo.sdc.org>
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<49B079FB.5010701@cox.net> <002401c99dfb$a25373a0$0701a8c0@master>
	<20090306014416.GG14496@virgo.sdc.org>
Message-ID: <0E031C3B-7C12-4850-9015-E24B13E996C8@tee-boy.com>

Willard,

You can thank Alan DeKok for that work.  He went into the kernel and  
optimized interrupt handling as best as he could and squeezed some  
additional performance.  NitrOS-9 still carries those enhancements.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com

On Mar 5, 2009, at 7:44 PM, Willard Goosey wrote:

> On Fri, Mar 06, 2009 at 11:32:59AM +1000, Bob Devries wrote:
>> I'm sure I have run ZMODEM on NitrOS9 using the 9600 baud setting.  
>> I have a
>
> Well, NitrOS helps a *lot*.  I vaguely remember Boisie ranting about
> how utterly horrible the original OS-9LII's interrupt-handling code
> is.
>
> Even with the 6809 versions, it's noticably more responsive.
>
> Willard
> -- 
> Willard Goosey  goosey at sdc.org
> Socorro, New Mexico, USA
> I search my heart and find Cimmeria, land of Darkness and the Night.
>  -- R.E. Howard
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From mmarlette at frontiernet.net  Thu Mar  5 21:16:04 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Fri, 6 Mar 2009 02:16:04 +0000 (UTC)
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <1323462009.57261236305332581.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <393468942.58841236305764798.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

Bob,

Good information. Each system will vary a bit but 9600 to 115200 is a big jump, 57600 is to far as well. You will see the errors.

Flow is critical on the coco as the data can come in fast. NitrOS-9 has a lot going on to support the small buffer of the 6551. The 16550's buffer is large enough for the driver to grab the larger packets and keep up. Much more efficient. I would like even larger buffers but your choices are somewhat limited in the Super I/O chips from manufactures.

Regards,

Mark
Cloud-9


----- Original Message -----
From: "Bob Devries" <devries.bob at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, March 5, 2009 7:36:21 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe:  RS232 paks

Of course, I have no idea exactly what the THROUGHPUT was in CPS with that 
setup.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Tim Fadden" <t.fadden at cox.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Friday, March 06, 2009 11:18 AM
Subject: Re: [Coco] 16550 wasRe: RS232 paks


> Hi Mark,
>
> This is my throughput with zmodem also using scsisys 1.1 hard drive with 
> modified os9, but not nitros. Using a Disto super II with a 4in1 card 
> serial port.  I do have a bootable Nitros9 floppy with the scsisys drivers 
> on them, so I could give it a shot with that, and let you know.
>>From my standpoint, the nitros9 floppy drivers lock up keyboard input, a
> feature I do not personally like.  I tend to type ahead a lot when doing 
> stuff.  Even on High-end Sun servers running solaris. :-)
>
> Tim
>
> Mark Marlette wrote:
>> Willard,
>>
>> Exactly my point. Zmodem by nature will re-xmit the loss but you can see 
>> that your effective baud rate goes in the tank.
>>
>> Was this Zmodem xfer saved to a hard disk or floppy?
>>
>> Regards,
>>
>> Mark
>> Cloud-9
>>
>>
>> ----- Original Message -----
>> From: "Willard Goosey" <goosey at virgo.sdc.org>
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Sent: Thursday, March 5, 2009 6:44:15 PM GMT -06:00 US/Canada Central
>> Subject: Re: [Coco] 16550 wasRe:  RS232 paks
>>
>> On Wed, Mar 04, 2009 at 08:12:44AM -0500, David Hazelton wrote:
>>
>>
>>> I have one built by Conect (IIRC)  Since when I bought it I only used 
>>> OS9, It worked great.  I did get better throughput then the RS-PAK.  I 
>>> did mostly Zmodem for file transfers, but I also logged in to VAX 
>>> machines and Unix based Machines at Work.
>>
>> I bet it did!  Zmodem likes uarts with fat FIFOs.  Under OS-9 with a
>> 6551, I couldn't ever get error-free zmodem downloads faster than
>> 4800. :-(
>>
>> Willard
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From snhirsch at gmail.com  Thu Mar  5 21:39:33 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Thu, 5 Mar 2009 21:39:33 -0500 (EST)
Subject: [Coco] DriveWire
In-Reply-To: <F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com><6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com><00a501c99c56$916e3850$0701a8c0@master><fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com><20090304060744.GC25102@virgo.sdc.org>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
Message-ID: <alpine.DEB.2.00.0903052138530.32155@duo>

On Thu, 5 Mar 2009, Boisy Pitre wrote:

> On Mar 5, 2009, at 6:59 PM, N8WQ wrote:
>
>> Boisy,
>> I was looking at Cloud 9 site, but didn't see any kind of descripton for 
>> DriveWire yet. I don't have a clue what it is. What is DriveWire if you 
>> don't mind me asking? I am assuming that it is some kind of file transfer 
>> protocal using some kind of cable from the PC to the CoCo? I look forward 
>> to hearing about it. Thanks...
>
> Alan,
>
> You described it correctly.  It's a software package that gives you BASIC and 
> NitrOS-9 drivers to access your PC, Mac or Linux system as a storage device 
> over the CoCo's bitbanger.
>
> I removed the page for DriveWire 2, which will be replaced by DriveWire 3 and 
> made available later this month. At that time a new page for DriveWire 3 will 
> go up.

And it will be _well_ worth waiting for! :-)

Steve


-- 


From storycrafter at gmail.com  Thu Mar  5 21:43:59 2009
From: storycrafter at gmail.com (Mark Martin)
Date: Thu, 5 Mar 2009 20:43:59 -0600
Subject: [Coco] DriveWire
In-Reply-To: <alpine.DEB.2.00.0903052138530.32155@duo>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>
	<00a501c99c56$916e3850$0701a8c0@master>
	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<alpine.DEB.2.00.0903052138530.32155@duo>
Message-ID: <e40c28290903051843h10e05bdei1d4f6ef93228b489@mail.gmail.com>

On Thu, Mar 5, 2009 at 8:39 PM, Steven Hirsch <snhirsch at gmail.com> wrote:
> On Thu, 5 Mar 2009, Boisy Pitre wrote:
>
>> I removed the page for DriveWire 2, which will be replaced by DriveWire 3
>> and made available later this month. At that time a new page for DriveWire 3
>> will go up.
>
> And it will be _well_ worth waiting for! :-)

Speaking of, am I correct in assuming it will be available for
purchase at the fest, or am I wishful thinking again?

Mark


From boisy at tee-boy.com  Thu Mar  5 21:46:58 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Thu, 5 Mar 2009 20:46:58 -0600
Subject: [Coco] DriveWire
In-Reply-To: <e40c28290903051843h10e05bdei1d4f6ef93228b489@mail.gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>
	<00a501c99c56$916e3850$0701a8c0@master>
	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<alpine.DEB.2.00.0903052138530.32155@duo>
	<e40c28290903051843h10e05bdei1d4f6ef93228b489@mail.gmail.com>
Message-ID: <CDFE0816-1699-4F65-9856-3924D7B2B151@tee-boy.com>

Martin,

Yes, DriveWire 3 will be available starting at the fest.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com

On Mar 5, 2009, at 8:43 PM, Mark Martin wrote:

> On Thu, Mar 5, 2009 at 8:39 PM, Steven Hirsch <snhirsch at gmail.com>  
> wrote:
>> On Thu, 5 Mar 2009, Boisy Pitre wrote:
>>
>>> I removed the page for DriveWire 2, which will be replaced by  
>>> DriveWire 3
>>> and made available later this month. At that time a new page for  
>>> DriveWire 3
>>> will go up.
>>
>> And it will be _well_ worth waiting for! :-)
>
> Speaking of, am I correct in assuming it will be available for
> purchase at the fest, or am I wishful thinking again?
>
> Mark
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From operator at coco3.com  Thu Mar  5 21:58:04 2009
From: operator at coco3.com (Roger Taylor)
Date: Thu, 05 Mar 2009 20:58:04 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
	<20090305223830.7949020A14@qs281.pair.com>
	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
Message-ID: <20090306025839.3A62020A13@qs281.pair.com>

To Mark and Boisy,

I'm going to say a few words that are going to hit home.  No offense, 
and no hard feelings?

My friends, you can't have it all.  The CoCo "market" doesn't belong 
only to two guys.

I need something better than DriveWire.  I need a system that can 
bring all possible resources into the CoCo over a bluetooth link or 
cable from a nearby "PC" (Windows, Linux, etc).  I don't want it next 
year from somebody else.  I want it right now.

I understand that the idea could possibly kill a bunch of hardware 
gadgets out there, but just because you invent new hardware doesn't 
mean my purpose isn't to solve the problem with older original 
hardware becoming harder to find.

I'm a problem solver, not a problem starter.  And I'm tired of the 
negative comments.

I realize that you're not going to like the CoCoNet venture, and 
you're not going to like the other products I'm going to 
produce.  I'm ok with this.

So be it.

Roger Taylor
-- 
Roger Taylor

http://www.wordofthedayonline.com



From coconut at pritchard.ca  Thu Mar  5 22:33:18 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Thu, 5 Mar 2009 21:33:18 -0600
Subject: [Coco] DriveWire
In-Reply-To: <F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>
	<00a501c99c56$916e3850$0701a8c0@master>
	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
Message-ID: <1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>

Hi Boisy,
I don't know much about how often you sold DriveWire 2 to people with only a
CoCo 1.  But might I suggest you keep DriveWire 2 listed by possibly
renaming it to DriveWire for CoCo 1.  There are people out here like myself
that have been evaluating which direction we are headed, but only have a
CoCo 1.

My personal concern right now is that I really would love to get an IDE
interface, but then I lose my Floppy Controller, since I don't currently
have a Multi-Pak Interface.  The thing is no matter which direction I choose
without a MPI or a Y Cable (much more limited I hear) I will only have one
slot and the bit banger seems to be my only choice.

Perhaps you can clear something up for me.  It is my understanding that Disk
Basic did not support Hard Drives, and that Cloud9's HDB-DOS allows a person
to simulate up to 256 single sided 35 track floppy images on a physical hard
drive.  I also understood that if one bought DriveWire 2 they received a
special HDB-DOS that allowed access of up to 1024 floppy images (256 per
each of the 4 drive numbers).

Now where I get lost is that with DriveWire 2 you indicate I could boot
strap NitrOS-9 from a DriveWire virtual drive.  Isn't the NitrOS-9 Level 1
boot diskette either 2 5.25" disks or 1 3.5" disk, since you only include
one disk image for NitrOS-9 I presume you are loading the larger disk image.
 Does NitroOS-9 support for DriveWire allow for larger disk images?  whereby
the virtual drives look like larger Hard Drives?

Basically without an MPI I think I have to consider your DriveWire product
over your IDE or SCSI product so that I can have continued floppy access.

On Thu, Mar 5, 2009 at 7:32 PM, Boisy Pitre <boisy at tee-boy.com> wrote:

> On Mar 5, 2009, at 6:59 PM, N8WQ wrote:
>
>  Boisy,
>> I was looking at Cloud 9 site, but didn't see any kind of descripton for
>> DriveWire yet. I don't have a clue what it is. What is DriveWire if you
>> don't mind me asking? I am assuming that it is some kind of file transfer
>> protocal using some kind of cable from the PC to the CoCo? I look forward to
>> hearing about it. Thanks...
>>
>
> Alan,
>
> You described it correctly.  It's a software package that gives you BASIC
> and NitrOS-9 drivers to access your PC, Mac or Linux system as a storage
> device over the CoCo's bitbanger.
>
> I removed the page for DriveWire 2, which will be replaced by DriveWire 3
> and made available later this month. At that time a new page for DriveWire 3
> will go up.
>
> Regards,
> Boisy G. Pitre
> --
> Tee-Boy
> Mobile: 337.781.3570
> Email: boisy at tee-boy.com
> Web: http://www.tee-boy.com
>
>
>
>> Alan Jones
>>
>> --
>> N8WQ - Canal Winchester, Ohio
>> http://exwn8jef.googlepages.com/home
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From chawks at dls.net  Thu Mar  5 22:40:26 2009
From: chawks at dls.net (Christopher Hawks)
Date: Thu, 05 Mar 2009 21:40:26 -0600
Subject: [Coco] DriveWire
In-Reply-To: <CDFE0816-1699-4F65-9856-3924D7B2B151@tee-boy.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>	<20090304060744.GC25102@virgo.sdc.org>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<alpine.DEB.2.00.0903052138530.32155@duo>	<e40c28290903051843h10e05bdei1d4f6ef93228b489@mail.gmail.com>
	<CDFE0816-1699-4F65-9856-3924D7B2B151@tee-boy.com>
Message-ID: <49B09B2A.1020807@dls.net>

Boisy Pitre said the following on 03/05/2009 08:46 PM:
> Martin,
> 
> Yes, DriveWire 3 will be available starting at the fest.

     I'm getting in line now...

-- 
Christopher R. Hawks
HAWKSoft
---------------------------------------------------------
Windows without the X is like making love without a partner.
win-nt from the people who invented edlin.
Linux, the way to get rid of boot viruses
	-- MaDsen Wikholm, mwikholm at at8.abo.fi


From fwp at deepthought.com  Thu Mar  5 23:31:40 2009
From: fwp at deepthought.com (Frank Pittel)
Date: Thu, 5 Mar 2009 22:31:40 -0600
Subject: [Coco] DriveWire
In-Reply-To: <49B09B2A.1020807@dls.net>
References: <fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<alpine.DEB.2.00.0903052138530.32155@duo>
	<e40c28290903051843h10e05bdei1d4f6ef93228b489@mail.gmail.com>
	<CDFE0816-1699-4F65-9856-3924D7B2B151@tee-boy.com>
	<49B09B2A.1020807@dls.net>
Message-ID: <20090306043140.GM7702@warlock.deepthought.com>

On Thu, Mar 05, 2009 at 09:40:26PM -0600, Christopher Hawks wrote:
> Boisy Pitre said the following on 03/05/2009 08:46 PM:
>> Martin,
>>
>> Yes, DriveWire 3 will be available starting at the fest.
>
>     I'm getting in line now...

I'm in line right behind you.


From mmarlette at frontiernet.net  Thu Mar  5 22:52:51 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Fri, 6 Mar 2009 03:52:51 +0000 (UTC)
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <1371925828.79471236311426107.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <1716644178.79891236311571842.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>

Roger,

Your message did not hit home at all. I take no offense to your message.

You miss the point or choose to avoid the real issues and questions.

This isn't about Cloud-9 owning the market. I am not going to explain myself again to you. For someone who claims to be brilliant you sure are not getting it.

I have no fear of your products that you create. You clearly design to a different level of expectations than I do. The 6551(ACIA) compared to a 16550(ACE) is comical in comparison. You can create whatever product you would like, just don't over sell it and say that it is going to perform beyond it's capabilities. In your app all will be well and good. Use the interface outside of that and the 6551 will fall flat on it's face, just like all of the other 6551s that have come before yours. Write a special driver for NitrOS-9 and all will be well until some other devices comes in and disrupts your timing. Show us your skills in NitrOS-9. It can be done.

Again, you invented nothing. The schematics are up on A7's web site. The RS232 pak is well documented as well. You integrated, big difference.

You continue to avoid, skirt the issues and blow smoke.

Regards,

Mark
Cloud-9


----- Original Message -----
From: "Roger Taylor" <operator at coco3.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, March 5, 2009 8:58:04 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] 16550 wasRe: RS232 paks

To Mark and Boisy,

I'm going to say a few words that are going to hit home.  No offense, 
and no hard feelings?

My friends, you can't have it all.  The CoCo "market" doesn't belong 
only to two guys.

I need something better than DriveWire.  I need a system that can 
bring all possible resources into the CoCo over a bluetooth link or 
cable from a nearby "PC" (Windows, Linux, etc).  I don't want it next 
year from somebody else.  I want it right now.

I understand that the idea could possibly kill a bunch of hardware 
gadgets out there, but just because you invent new hardware doesn't 
mean my purpose isn't to solve the problem with older original 
hardware becoming harder to find.

I'm a problem solver, not a problem starter.  And I'm tired of the 
negative comments.

I realize that you're not going to like the CoCoNet venture, and 
you're not going to like the other products I'm going to 
produce.  I'm ok with this.

So be it.

Roger Taylor
-- 
Roger Taylor

http://www.wordofthedayonline.com


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From da3m0n_slay3r at yahoo.com  Thu Mar  5 23:04:14 2009
From: da3m0n_slay3r at yahoo.com (Bill Barnes)
Date: Thu, 5 Mar 2009 20:04:14 -0800 (PST)
Subject: [Coco] POLL: multiple message problem
Message-ID: <270973.22891.qm@web31102.mail.mud.yahoo.com>


What I've seen here today is no direct connection to ISP, E-Mail Client, or Web-mail/POP server.

Oddly enough, today's email coming into me for all the lists/groups I'm subscribed to, contained no multiple copies. I Hope it stays that way. There's no way I want to sift through 486 messages coco related, just to find that over 50% of them are repeats, and attempting to scan through them, passing on the repeats quickly, resulting in a temp ban by Yahoo for too much activity because I missed keeping up with it for 3-4 days.


-Later!
  ?-WB-??? -- BABIC Computer Consulting.



      


From gene.heskett at verizon.net  Thu Mar  5 23:54:05 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Thu, 05 Mar 2009 23:54:05 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <002d01c99dfc$08234b60$0701a8c0@master>
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<49B079FB.5010701@cox.net> <002d01c99dfc$08234b60$0701a8c0@master>
Message-ID: <200903052354.05764.gene.heskett@verizon.net>

On Thursday 05 March 2009, Bob Devries wrote:
>Of course, I have no idea exactly what the THROUGHPUT was in CPS with that
>setup.
>
When I was working on rzsz-3.36 last, the optimized version everybody should 
have by now, using hardware flow control, could transmit to an amiga at around 
740 cps with both sides set to 9600 baud.  In fairness to the flow control 
problems in the 6551, the amiga could of course keep up with the coco so the 
flow control never activated to trigger the bug under those conditions.  So of 
course that bug never stuck up its hand in my tests.  That would only show up 
when the target machine was slower than the coco.

Conversely, with the amiga sending to the coco, the flow controls were used to 
slow the amiga down, and again the average speed was in the 735 cps area.  And 
it was sustained over files of nominally a megabyte.  Only noticeable slowdown 
was those created by the no-halt controller if I was writing to a floppy, but 
usually I used my hard drive or the ramdisk I wrote since my coco3 has a 2 meg 
kit in it and I can instantly (a few hundred milliseconds) set it up at up to 
about 1.7 megs max but usually for 1.5 megs.

x and y modem, with their much simpler and faster error checking, can run lots 
faster than that.  The speed killer in rzsz is the crc checking, done on a per 
byte basis as the byte comes in or goes out.  Someday, someone should convert 
that to checking just one 256 byte buffer at once, it should at least triple 
rzsz's speed in cps.

Those speeds above were obtained with the crc table lookup method.  Using 
rzsz's original crc method slowed it by a bit more than half, to around 330 
cps both ways, so that table lookup was a huge improvement right there.  Now 
it needs to be converted to doing that loop once, over a full or partial 
buffer.  I believe that would get it nicely above 960 cps (9600 baud).

Anyway, those are the figures to shoot at, have fun, the code _is_ out there.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
<``Erik> 18,446,744,073,709,551,616 is a big number



From boisy at tee-boy.com  Thu Mar  5 23:54:40 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Thu, 5 Mar 2009 22:54:40 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <20090306025839.3A62020A13@qs281.pair.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
	<20090305223830.7949020A14@qs281.pair.com>
	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
	<20090306025839.3A62020A13@qs281.pair.com>
Message-ID: <C485B547-7A3E-415D-8173-779C96B3F6A2@tee-boy.com>

You don't get it Roger, and by God, I don't think you ever will.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com

On Mar 5, 2009, at 8:58 PM, Roger Taylor wrote:

> To Mark and Boisy,
>
> I'm going to say a few words that are going to hit home.  No  
> offense, and no hard feelings?
>
> My friends, you can't have it all.  The CoCo "market" doesn't belong  
> only to two guys.
>
> I need something better than DriveWire.  I need a system that can  
> bring all possible resources into the CoCo over a bluetooth link or  
> cable from a nearby "PC" (Windows, Linux, etc).  I don't want it  
> next year from somebody else.  I want it right now.
>
> I understand that the idea could possibly kill a bunch of hardware  
> gadgets out there, but just because you invent new hardware doesn't  
> mean my purpose isn't to solve the problem with older original  
> hardware becoming harder to find.
>
> I'm a problem solver, not a problem starter.  And I'm tired of the  
> negative comments.
>
> I realize that you're not going to like the CoCoNet venture, and  
> you're not going to like the other products I'm going to produce.   
> I'm ok with this.
>
> So be it.
>
> Roger Taylor
> -- 
> Roger Taylor
>
> http://www.wordofthedayonline.com
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From operator at coco3.com  Thu Mar  5 23:54:29 2009
From: operator at coco3.com (Roger Taylor)
Date: Thu, 05 Mar 2009 22:54:29 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <1716644178.79891236311571842.JavaMail.root@cl04-host03.roc
	h.ny.frontiernet.net>
References: <1371925828.79471236311426107.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<1716644178.79891236311571842.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <20090306045559.E186820A15@qs281.pair.com>

At 09:52 PM 3/5/2009, you wrote:
>Roger,
>Your message did not hit home at all. I take no offense to your message.

>This isn't about Cloud-9 owning the market. I am not going to 
>explain myself again to you.

You don't own any market.  Mark, you are the most arrogant fella I 
have ever chatted with, and I'm not going to explain myself to you 
anymore, either, even when you demand it.
http://dictionary.reference.com/browse/arrogant

Maybe if you quit bashing other people's CoCo efforts and accusing 
them of blowing smoke, you'll have time to finish that SuperBoard 
before 10 other eldest and most valued CoCo users meet their 
relatives in heaven.  You brought up "expectations", so I couldn't resist.


-- 
Roger Taylor

http://www.wordofthedayonline.com



From boisy at tee-boy.com  Thu Mar  5 23:55:58 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Thu, 5 Mar 2009 22:55:58 -0600
Subject: [Coco] DriveWire
In-Reply-To: <1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>
	<00a501c99c56$916e3850$0701a8c0@master>
	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
Message-ID: <C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>


On Mar 5, 2009, at 9:33 PM, Ryan Pritchard wrote:

> Hi Boisy,
> I don't know much about how often you sold DriveWire 2 to people  
> with only a
> CoCo 1.  But might I suggest you keep DriveWire 2 listed by possibly
> renaming it to DriveWire for CoCo 1.  There are people out here like  
> myself
> that have been evaluating which direction we are headed, but only  
> have a
> CoCo 1.
>
> My personal concern right now is that I really would love to get an  
> IDE
> interface, but then I lose my Floppy Controller, since I don't  
> currently
> have a Multi-Pak Interface.  The thing is no matter which direction  
> I choose
> without a MPI or a Y Cable (much more limited I hear) I will only  
> have one
> slot and the bit banger seems to be my only choice.
>
> Perhaps you can clear something up for me.  It is my understanding  
> that Disk
> Basic did not support Hard Drives, and that Cloud9's HDB-DOS allows  
> a person
> to simulate up to 256 single sided 35 track floppy images on a  
> physical hard
> drive.  I also understood that if one bought DriveWire 2 they  
> received a
> special HDB-DOS that allowed access of up to 1024 floppy images (256  
> per
> each of the 4 drive numbers).

That is correct.

> Now where I get lost is that with DriveWire 2 you indicate I could  
> boot
> strap NitrOS-9 from a DriveWire virtual drive.  Isn't the NitrOS-9  
> Level 1
> boot diskette either 2 5.25" disks or 1 3.5" disk, since you only  
> include
> one disk image for NitrOS-9 I presume you are loading the larger  
> disk image.
> Does NitroOS-9 support for DriveWire allow for larger disk images?   
> whereby
> the virtual drives look like larger Hard Drives?

Yes, that is correct. Under NitrOS-9, you can format a DriveWire disk  
as large as RBF will allow (4GB)

> Basically without an MPI I think I have to consider your DriveWire  
> product
> over your IDE or SCSI product so that I can have continued floppy  
> access.

Thanks for your input Ryan.  I'll mull over the CoCo 1 suggestions  
you've made.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From briang0671 at sbcglobal.net  Fri Mar  6 00:03:32 2009
From: briang0671 at sbcglobal.net (Brian Goers)
Date: Thu, 05 Mar 2009 23:03:32 -0600
Subject: [Coco] Glenside IDE board Connectors
Message-ID: <49B0AEA4.5010108@sbcglobal.net>

Since the CoCoFest is coming up soon. I thought I would order card edge 
connectors that mount on the IDE board at CONN2 and CONN 3. Then if you 
don't have a Multi-Pak Interface or Slot-pak you can plug the floppy 
controller into the IDE board.

I have not ordered them yet and things become hurried as the Fest 
approaches I will probably mail the connector after the Fest.
If I can mail them sooner I will.
These are the 2 row 20 connectors without the flange. If the flange will 
not interfere with the tabs on the floppy controller I will buy those 
instead.
Brian

-- 
 Brian Goers                                         Glenside Color Computer Club URL
 Glenside Vice-President of Special Events           http://GlensideCCC.com     

 IDE Boards are available.
 Show cost $45.00                                   The 18th Annual ?LAST? Chicago CoCoFEST!
 Includes items in the picture                      Will be held March 28 & 29 2009
                                                    Holiday Inn & Suites Elgin.



From da3m0n_slay3r at yahoo.com  Fri Mar  6 00:04:03 2009
From: da3m0n_slay3r at yahoo.com (Bill Barnes)
Date: Thu, 5 Mar 2009 21:04:03 -0800 (PST)
Subject: [Coco] POLL: multiple message problem
Message-ID: <906764.95699.qm@web31102.mail.mud.yahoo.com>


I may have spoke too soon. (referring to me seeing repeats.)

-Later!  ?-WB-??? -- BABIC Computer Consulting.

--- On Thu, 3/5/09, Bill Barnes <da3m0n_slay3r at yahoo.com> wrote:

From: Bill Barnes <da3m0n_slay3r at yahoo.com>
Subject: Re: [Coco] POLL: multiple message problem
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Date: Thursday, March 5, 2009, 10:04 PM


What I've seen here today is no direct connection to ISP, E-Mail Client, or Web-mail/POP server.

Oddly enough, today's email coming into me for all the lists/groups I'm subscribed to, contained no multiple copies. I Hope it stays that way. There's no way I want to sift through 486 messages coco related, just to find that over 50% of them are repeats, and attempting to scan through them, passing on the repeats quickly, resulting in a temp ban by Yahoo for too much activity because I missed keeping up with it for 3-4 days.


-Later!
? ?-WB-??? -- BABIC Computer Consulting.



      


From operator at coco3.com  Fri Mar  6 00:18:00 2009
From: operator at coco3.com (Roger Taylor)
Date: Thu, 05 Mar 2009 23:18:00 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <C485B547-7A3E-415D-8173-779C96B3F6A2@tee-boy.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
	<20090305223830.7949020A14@qs281.pair.com>
	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
	<20090306025839.3A62020A13@qs281.pair.com>
	<C485B547-7A3E-415D-8173-779C96B3F6A2@tee-boy.com>
Message-ID: <20090306051857.6554620A16@qs281.pair.com>

At 10:54 PM 3/5/2009, you wrote:
>You don't get it Roger, and by God, I don't think you ever will.

Trust me, Boisy.  I get it.  We have a pile of b.s. on the ground and 
somebody's been trying their best to get me to slam my foot into it, 
only when I did, the shit slung over on them.  And sometimes the 
person baiting the hook gets the hook stuck in their finger.  I've 
said all I'm going to say.

Now you guys keep up the good work, and let others peacefully keep up 
their good work, and all will be well.  I'm going to bed.


-- 
Roger Taylor

http://www.wordofthedayonline.com



From boisy at tee-boy.com  Fri Mar  6 00:29:29 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Thu, 5 Mar 2009 23:29:29 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <20090306051857.6554620A16@qs281.pair.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
	<20090305223830.7949020A14@qs281.pair.com>
	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
	<20090306025839.3A62020A13@qs281.pair.com>
	<C485B547-7A3E-415D-8173-779C96B3F6A2@tee-boy.com>
	<20090306051857.6554620A16@qs281.pair.com>
Message-ID: <3388E7A0-C802-4BB5-B101-2EF0365428F7@tee-boy.com>

On Mar 5, 2009, at 11:18 PM, Roger Taylor wrote:

> At 10:54 PM 3/5/2009, you wrote:
>> You don't get it Roger, and by God, I don't think you ever will.
>
> Trust me, Boisy.  I get it.  We have a pile of b.s. on the ground  
> and somebody's been trying their best to get me to slam my foot into  
> it, only when I did, the shit slung over on them.  And sometimes the  
> person baiting the hook gets the hook stuck in their finger.  I've  
> said all I'm going to say.
>
> Now you guys keep up the good work, and let others peacefully keep  
> up their good work, and all will be well.  I'm going to bed.

Apology accepted.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From fwp at deepthought.com  Fri Mar  6 01:13:52 2009
From: fwp at deepthought.com (Frank Pittel)
Date: Fri, 6 Mar 2009 00:13:52 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <20090306051857.6554620A16@qs281.pair.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
	<20090305223830.7949020A14@qs281.pair.com>
	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
	<20090306025839.3A62020A13@qs281.pair.com>
	<C485B547-7A3E-415D-8173-779C96B3F6A2@tee-boy.com>
	<20090306051857.6554620A16@qs281.pair.com>
Message-ID: <20090306061352.GN7702@warlock.deepthought.com>

On Thu, Mar 05, 2009 at 11:18:00PM -0600, Roger Taylor wrote:
> At 10:54 PM 3/5/2009, you wrote:
>> You don't get it Roger, and by God, I don't think you ever will.
>
> Trust me, Boisy.  I get it.  We have a pile of b.s. on the ground and  
> somebody's been trying their best to get me to slam my foot into it,  
> only when I did, the shit slung over on them.  And sometimes the person 
> baiting the hook gets the hook stuck in their finger.  I've said all I'm 
> going to say.
>
> Now you guys keep up the good work, and let others peacefully keep up  
> their good work, and all will be well.  I'm going to bed.

Now that everyone has said all they're going to say on the matter can we let
it drop? While I like the idea of a "bluetooth network" between the coco and pc.
I don't see how it would be useful to me.

A few things I would like to see for those that care and have the ability to do it.

A superide type device with a additional port for floppy drives.
A usb port usable for storage with hdb-dos and nitros support.
A version of hdb-dos that lets me use my superide adaptor, scsi adaptor and drivewire
at the same time!! 
and last but not least the ability to use drivewire that will let my coco "print" to
a file on my pc running linux.

Those four products would allow me to die a happy man! :-)

Frank


From mark at cloud9tech.com  Fri Mar  6 00:38:16 2009
From: mark at cloud9tech.com (Mark Marlette)
Date: Thu, 05 Mar 2009 23:38:16 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <20090306045559.E186820A15@qs281.pair.com>
References: <1371925828.79471236311426107.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<1716644178.79891236311571842.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<20090306045559.E186820A15@qs281.pair.com>
Message-ID: <6.2.5.6.2.20090305232410.02a71940@cloud9tech.com>

Roger,

Can you please come up with an original idea of your own. Boisy posts 
a definition then you do.

You can also draw the same comparison to your CoCoNet product.

You said 'The CoCo "market" doesn't belong only to two guys.' I said 
owned....If that makes me arrogant, then again, guilty. I call myself 
confident. ;)

You directly asked the questions, remember? I guess not.

Looks like I hit another nerve Roger, thin skinned, you would never 
survive a peer review board.

Your SuperBoard comment doesn't bother me either, shows the real you 
and how you present yourself.

I answer to my customers, which you are not and never have been. 
Something in which you can't say the same with myself.

Regards,

Mark
Cloud-9


At 3/5/2009 10:54 PM, you wrote:
>At 09:52 PM 3/5/2009, you wrote:
>>Roger,
>>Your message did not hit home at all. I take no offense to your message.
>
>>This isn't about Cloud-9 owning the market. I am not going to 
>>explain myself again to you.
>
>You don't own any market.  Mark, you are the most arrogant fella I 
>have ever chatted with, and I'm not going to explain myself to you 
>anymore, either, even when you demand it.
>http://dictionary.reference.com/browse/arrogant
>
>Maybe if you quit bashing other people's CoCo efforts and accusing 
>them of blowing smoke, you'll have time to finish that SuperBoard 
>before 10 other eldest and most valued CoCo users meet their 
>relatives in heaven.  You brought up "expectations", so I couldn't resist.
>
>
>--
>Roger Taylor
>
>http://www.wordofthedayonline.com
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco
>
>
>No virus found in this incoming message.
>Checked by AVG - www.avg.com
>Version: 8.0.237 / Virus Database: 270.11.8/1985 - Release Date: 
>03/05/09 07:54:00


From mark at cloud9tech.com  Fri Mar  6 00:40:54 2009
From: mark at cloud9tech.com (Mark Marlette)
Date: Thu, 05 Mar 2009 23:40:54 -0600
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <200903052354.05764.gene.heskett@verizon.net>
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<49B079FB.5010701@cox.net> <002d01c99dfc$08234b60$0701a8c0@master>
	<200903052354.05764.gene.heskett@verizon.net>
Message-ID: <6.2.5.6.2.20090305233827.02a7d4e0@cloud9tech.com>

Gene,

I am glad that your memory has returned on this. :)

Darn it, being arrogant...Again......

Regards,

Mark
Cloud-9


At 3/5/2009 10:54 PM, you wrote:
>On Thursday 05 March 2009, Bob Devries wrote:
> >Of course, I have no idea exactly what the THROUGHPUT was in CPS with that
> >setup.
> >
>When I was working on rzsz-3.36 last, the optimized version everybody should
>have by now, using hardware flow control, could transmit to an amiga 
>at around
>740 cps with both sides set to 9600 baud.  In fairness to the flow control
>problems in the 6551, the amiga could of course keep up with the coco so the
>flow control never activated to trigger the bug under those 
>conditions.  So of
>course that bug never stuck up its hand in my tests.  That would only show up
>when the target machine was slower than the coco.
>
>Conversely, with the amiga sending to the coco, the flow controls 
>were used to
>slow the amiga down, and again the average speed was in the 735 cps 
>area.  And
>it was sustained over files of nominally a megabyte.  Only 
>noticeable slowdown
>was those created by the no-halt controller if I was writing to a floppy, but
>usually I used my hard drive or the ramdisk I wrote since my coco3 
>has a 2 meg
>kit in it and I can instantly (a few hundred milliseconds) set it up at up to
>about 1.7 megs max but usually for 1.5 megs.
>
>x and y modem, with their much simpler and faster error checking, 
>can run lots
>faster than that.  The speed killer in rzsz is the crc checking, 
>done on a per
>byte basis as the byte comes in or goes out.  Someday, someone should convert
>that to checking just one 256 byte buffer at once, it should at least triple
>rzsz's speed in cps.
>
>Those speeds above were obtained with the crc table lookup method.  Using
>rzsz's original crc method slowed it by a bit more than half, to around 330
>cps both ways, so that table lookup was a huge improvement right there.  Now
>it needs to be converted to doing that loop once, over a full or partial
>buffer.  I believe that would get it nicely above 960 cps (9600 baud).
>
>Anyway, those are the figures to shoot at, have fun, the code _is_ out there.
>
>--
>Cheers, Gene
>"There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
>-Ed Howdershelt (Author)
><``Erik> 18,446,744,073,709,551,616 is a big number
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco
>
>No virus found in this incoming message.
>Checked by AVG - www.avg.com
>Version: 8.0.237 / Virus Database: 270.11.8/1985 - Release Date: 
>03/05/09 07:54:00


From gene.heskett at verizon.net  Fri Mar  6 01:03:46 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Fri, 06 Mar 2009 01:03:46 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <6.2.5.6.2.20090305233827.02a7d4e0@cloud9tech.com>
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<200903052354.05764.gene.heskett@verizon.net>
	<6.2.5.6.2.20090305233827.02a7d4e0@cloud9tech.com>
Message-ID: <200903060103.46738.gene.heskett@verizon.net>

On Friday 06 March 2009, Mark Marlette wrote:
>Gene,
>
>I am glad that your memory has returned on this. :)
>
>Darn it, being arrogant...Again......

A wee bit perhaps, but then the same can quite easily be said of me when my 
technical feet are on solid ground.  I've even got a degree from the 
University of Hard Knocks.  See at
<http://gene.homelinux.net:85/gene/pix/UHK-diploma2.jpg>

You can only get one of those if you have 'made it' in life without any 
education above high school, and as only an 8th grade graduate, I qualified 
with points to spare.  Oh, and they need a $100 bill, a donation to the 
student loan fund at Alderson-Broddus College in Phillipe WV.  I think the 
fact that you can spare the $100 bill is evidence that you've 'made it'. :)

I finally did get a GED too, also in the early 90's.  Took the test, they said 
I'd hear in a week or so, I let 2 go by and collared the teacher giving the 
test.  His reply to my question was "Why do you care, you WERE just doing it 
for the exercise weren't you?"  He of course was right. :-)

[...]

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Sodd's Second Law:
	Sooner or later, the worst possible set of circumstances is
	bound to occur.



From robert.gault at worldnet.att.net  Fri Mar  6 08:59:36 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Fri, 06 Mar 2009 08:59:36 -0500
Subject: [Coco] DriveWire
In-Reply-To: <C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>	<20090304060744.GC25102@virgo.sdc.org>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>
Message-ID: <49B12C48.2030601@worldnet.att.net>

Boisy Pitre wrote:
> 
> On Mar 5, 2009, at 9:33 PM, Ryan Pritchard wrote:
> 
><snip>
>> Now where I get lost is that with DriveWire 2 you indicate I could boot
>> strap NitrOS-9 from a DriveWire virtual drive.  Isn't the NitrOS-9 
>> Level 1
>> boot diskette either 2 5.25" disks or 1 3.5" disk, since you only include
>> one disk image for NitrOS-9 I presume you are loading the larger disk 
>> image.
>> Does NitroOS-9 support for DriveWire allow for larger disk images?  
>> whereby
>> the virtual drives look like larger Hard Drives?
> 
> Yes, that is correct. Under NitrOS-9, you can format a DriveWire disk as 
> large as RBF will allow (4GB)
> 
 ><snip>

Ryan, I'm not so sure that Boisy answered your question completely.

NitrOS-9 has a module in the kernel on track 34 called Boot. This module 
is by default hard coded to read floppies. If you want to boot from a 
real hard drive via a scsi or ide interface or from a virtual hard drive 
via DriveWire, the boot module must be replaced with a special one to 
access the correct hardware. This is done for you (I think) by Cloud-9 
when you purchase their products.
The size of the drive where the main NitrOS-9 system is installed, is 
not dependent on the interface that talks to the drive as much as it 
depends on the actual OS-9 / NitrOS-9 software. The size of a disk is 
stored on the disk's first sector in 3 bytes indicating total sectors, 
DD.TOT. So you are limited to $FFFFFF sectors. The sectors don't need to 
be 256 bytes (standard) but that is still 4GB.

So when booting via DriveWire or an IDE or SCSI system, you will still 
use a floppy. The floppy can be a virtual floppy in which case it is a 
35 track single sided image containing only the kernel on T17 and the 
os9Boot file.
You can get a feel for this with several emulators using RGBDOS for 
emulators. Both the emulator version of RGBDOS and HDBDOS derive from 
the same RGBDOS sold with KEN-TON SCSI hard drive systems for the Coco.


From cwgordon at carolina.rr.com  Fri Mar  6 09:19:35 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Fri, 6 Mar 2009 09:19:35 -0500
Subject: [Coco] Pretty new screen
In-Reply-To: <20090305165740.88583yz4xfj3qzcw@aurigae.demon.co.uk>
References: <002401c99d9c$36cbe180$a463a480$@rr.com>
	<20090305165740.88583yz4xfj3qzcw@aurigae.demon.co.uk>
Message-ID: <008f01c99e66$940fb540$bc2f1fc0$@rr.com>

WOW!! Here is something unusual. I tried today to check out the chips (all
soldered but two), and the only way I could see anything on the screen was
to tune to channel 2 (3 or 4 do not pick anything up). I still have the
screen pictured in the link I gave, but it will ONLY come in on channel 2.

The 2 socketed chips are the SN74LS785N hidden partially under the keyboard,
and the XC80652P (58C8444), just to the right of the RF output.

This is, of course, the 26-3127B Korean Coco2

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of afra at aurigae.demon.co.uk
> Sent: Thursday, March 05, 2009 11:58 AM
> To: coco at maltedmedia.com
> Subject: Re: [Coco] Pretty new screen
> 
> Which CoCo model is this ?
> 
> Whilst I agree with Robert who said that it would be impossible to
> tell for certain, the one time I have seen a pattern like that before
> from a Dragon, which is basically the same as the CoCo 1/2, the
> problem was the 74LS244 buffer chip that sits between the processor
> data bus and the RAM/VDG data bus. Said LS chip had died and no data
> was getting writen to the RAM, and so the VDG was just pulling out
> whatever default patern was there.
> 



From jlhickle at yahoo.com  Fri Mar  6 10:40:33 2009
From: jlhickle at yahoo.com (Jim Hickle)
Date: Fri, 6 Mar 2009 07:40:33 -0800 (PST)
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <203706.64927.qm@web31108.mail.mud.yahoo.com>
Message-ID: <624380.2834.qm@web37306.mail.mud.yahoo.com>

Number of multiples varies, up to ten copies coming in to yahoo mail.
Sent headers from 6 copies of a message to Dennis. He confirmed
that they are not being sent from the list.

Copies arrive at different times.? I've got 14 messages in this thread in my inbox but the original message still has not arrived.

--- On Thu, 3/5/09, Bill Barnes <da3m0n_slay3r at yahoo.com> wrote:
From: Bill Barnes <da3m0n_slay3r at yahoo.com>
Subject: Re: [Coco] POLL: multiple message problem
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Date: Thursday, March 5, 2009, 2:40 PM

Ok, I think we shoulf figure out here, who all has the multiple-copies problem:
In doing so, can we identify our ISP and email service? ?With this data, we can
see what is affected, and to what extent. (is is just an ISP, is it a specific
email system? is it some link along the way?)I'll start.multiples problem:
YES? ? ? ? ? ? ? ? ? ? ISP: Cox? ? ?eMail System: Yahoonow just
need someone to keep track of it all, preferably someone who isn't caught in
a multiples problem, any volunteers? It would be good to know this as we all can
agree, it gets annoying and fills our inboxes way faster than normal, and needs
to be fixed. I wanna read about and contribute to the CoCo, NOT get bogged down
in multiples.
-Later!? -WB- ?? -- BABIC Computer Consulting.




      

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



      


From boisy at tee-boy.com  Fri Mar  6 10:54:22 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 6 Mar 2009 09:54:22 -0600
Subject: [Coco] DriveWire 3
Message-ID: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>

As the saying goes, the only way to fight fire is with fire.

So starting today, DriveWire 3 is now a free downloadable product from  
Cloud-9.

You can go to our website at http://www.cloud9tech.com/ and click on  
the DriveWire announcement on the main page.  It will take you to the  
DriveWire 3 page, where you can now download DriveWire HDB-DOS ROMs  
for the CoCo 2 and CoCo 3.  Of course, you will need to burn your own  
EPROM in order to take advantage of these images.

For those of you who don't have an EPROM burner or cable, we've  
dropped the price of our HDB-DOS ROM Pak to $20, and are still making  
cables available for $10.

The server software for Windows and Mac will go up sometime today.   
The Linux server on SourceForge has been updated to handle the new  
protocol features.

Documentation and NitrOS-9 images will be go up this weekend.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From rcrislip at neo.rr.com  Fri Mar  6 11:27:37 2009
From: rcrislip at neo.rr.com (richec)
Date: Fri, 6 Mar 2009 11:27:37 -0500
Subject: [Coco] POLL: multiple message problem
In-Reply-To: <203706.64927.qm@web31108.mail.mud.yahoo.com>
References: <203706.64927.qm@web31108.mail.mud.yahoo.com>
Message-ID: <200903061127.37221.rcrislip@neo.rr.com>

On Thursday 05 March 2009 14:40:20 Bill Barnes wrote:
> Ok, I think we shoulf figure out here, who all has the multiple-copies
> problem: In doing so, can we identify our ISP and email service? ?With this
> data, we can see what is affected, and to what extent. (is is just an ISP,
> is it a specific email system? is it some link along the way?)I'll
> start.multiples problem: YES? ? ? ? ? ? ? ? ? ? ISP: Cox? ? ?eMail System:
> Yahoonow just need someone to keep track of it all, preferably someone who
> isn't caught in a multiples problem, any volunteers? It would be good to
> know this as we all can agree, it gets annoying and fills our inboxes way
> faster than normal, and needs to be fixed. I wanna read about and
> contribute to the CoCo, NOT get bogged down in multiples. -Later!? -WB- ??
> -- BABIC Computer Consulting.
>
>
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco

It is an occasional problem for me. Usually dulicates.


From exwn8jef at gmail.com  Fri Mar  6 11:38:09 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Fri, 06 Mar 2009 11:38:09 -0500
Subject: [Coco] DriveWire 3
In-Reply-To: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
Message-ID: <49B15171.60602@gmail.com>

Boisy,
Only one thing to say. Awesome!

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



Boisy Pitre wrote:
> As the saying goes, the only way to fight fire is with fire.
>
> So starting today, DriveWire 3 is now a free downloadable product from 
> Cloud-9.
>
> You can go to our website at http://www.cloud9tech.com/ and click on 
> the DriveWire announcement on the main page.  It will take you to the 
> DriveWire 3 page, where you can now download DriveWire HDB-DOS ROMs 
> for the CoCo 2 and CoCo 3.  Of course, you will need to burn your own 
> EPROM in order to take advantage of these images.
>
> For those of you who don't have an EPROM burner or cable, we've 
> dropped the price of our HDB-DOS ROM Pak to $20, and are still making 
> cables available for $10.
>
> The server software for Windows and Mac will go up sometime today.  
> The Linux server on SourceForge has been updated to handle the new 
> protocol features.
>
> Documentation and NitrOS-9 images will be go up this weekend.
>
> Regards,
> Boisy G. Pitre
> -- 
> Tee-Boy
> Mobile: 337.781.3570
> Email: boisy at tee-boy.com
> Web: http://www.tee-boy.com
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From exwn8jef at gmail.com  Fri Mar  6 11:47:59 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Fri, 06 Mar 2009 11:47:59 -0500
Subject: [Coco] DriveWire 3
In-Reply-To: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
Message-ID: <49B153BF.4000503@gmail.com>

Boisy,
Can you or someone on the list recommend a good USB to Serial adapter?
Unfortunately, I don't have a serial connector. :(
Thanks...

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



Boisy Pitre wrote:
> As the saying goes, the only way to fight fire is with fire.
>
> So starting today, DriveWire 3 is now a free downloadable product from 
> Cloud-9.
>
> You can go to our website at http://www.cloud9tech.com/ and click on 
> the DriveWire announcement on the main page.  It will take you to the 
> DriveWire 3 page, where you can now download DriveWire HDB-DOS ROMs 
> for the CoCo 2 and CoCo 3.  Of course, you will need to burn your own 
> EPROM in order to take advantage of these images.
>
> For those of you who don't have an EPROM burner or cable, we've 
> dropped the price of our HDB-DOS ROM Pak to $20, and are still making 
> cables available for $10.
>
> The server software for Windows and Mac will go up sometime today.  
> The Linux server on SourceForge has been updated to handle the new 
> protocol features.
>
> Documentation and NitrOS-9 images will be go up this weekend.
>
> Regards,
> Boisy G. Pitre
> -- 
> Tee-Boy
> Mobile: 337.781.3570
> Email: boisy at tee-boy.com
> Web: http://www.tee-boy.com
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From coconut at pritchard.ca  Fri Mar  6 11:57:39 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Fri, 6 Mar 2009 10:57:39 -0600
Subject: [Coco] DriveWire 3
In-Reply-To: <49B153BF.4000503@gmail.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
	<49B153BF.4000503@gmail.com>
Message-ID: <1806abd60903060857n3630c102k2942f5fda6caf716@mail.gmail.com>

I think this device will be wonderful.  I know the USB to UART chip is
compatible with Windows, Linux and Mac OS X.

http://cgi.ebay.ca/CP2102-USB-TTL-RS232-Serial-Port-Converter-Transceiver_W0QQitemZ250382968852QQcmdZViewItemQQptZPCA_Cables_Adapters?hash=item250382968852&_trksid=p4634.c0.m14

Ordering one this week, in preparation of using DriveWire on my CoCo 1, or
at very least to allow me to communicate with my GIMIX 6809 Ghost machines.

On Fri, Mar 6, 2009 at 10:47 AM, N8WQ <exwn8jef at gmail.com> wrote:

> Boisy,
> Can you or someone on the list recommend a good USB to Serial adapter?
> Unfortunately, I don't have a serial connector. :(
> Thanks...
>
> Alan Jones
>
> --
> N8WQ - Canal Winchester, Ohio
> http://exwn8jef.googlepages.com/home
>
>
>
> Boisy Pitre wrote:
>
>> As the saying goes, the only way to fight fire is with fire.
>>
>> So starting today, DriveWire 3 is now a free downloadable product from
>> Cloud-9.
>>
>> You can go to our website at http://www.cloud9tech.com/ and click on the
>> DriveWire announcement on the main page.  It will take you to the DriveWire
>> 3 page, where you can now download DriveWire HDB-DOS ROMs for the CoCo 2 and
>> CoCo 3.  Of course, you will need to burn your own EPROM in order to take
>> advantage of these images.
>>
>> For those of you who don't have an EPROM burner or cable, we've dropped
>> the price of our HDB-DOS ROM Pak to $20, and are still making cables
>> available for $10.
>>
>> The server software for Windows and Mac will go up sometime today.  The
>> Linux server on SourceForge has been updated to handle the new protocol
>> features.
>>
>> Documentation and NitrOS-9 images will be go up this weekend.
>>
>> Regards,
>> Boisy G. Pitre
>> --
>> Tee-Boy
>> Mobile: 337.781.3570
>> Email: boisy at tee-boy.com
>> Web: http://www.tee-boy.com
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From boisy at tee-boy.com  Fri Mar  6 12:07:30 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 6 Mar 2009 11:07:30 -0600
Subject: [Coco] DriveWire 3
In-Reply-To: <49B153BF.4000503@gmail.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
	<49B153BF.4000503@gmail.com>
Message-ID: <E1BC1851-E9CE-4E51-B9B1-8672A25DA044@tee-boy.com>

Alan,

I would recommend a USB<->Serial adapter with the FTDI chipset.

Let me know how your search goes.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com

On Mar 6, 2009, at 10:47 AM, N8WQ wrote:

> Boisy,
> Can you or someone on the list recommend a good USB to Serial adapter?
> Unfortunately, I don't have a serial connector. :(
> Thanks...
>
> Alan Jones
>
> --  
> N8WQ - Canal Winchester, Ohio
> http://exwn8jef.googlepages.com/home
>
>
>
> Boisy Pitre wrote:
>> As the saying goes, the only way to fight fire is with fire.
>>
>> So starting today, DriveWire 3 is now a free downloadable product  
>> from Cloud-9.
>>
>> You can go to our website at http://www.cloud9tech.com/ and click  
>> on the DriveWire announcement on the main page.  It will take you  
>> to the DriveWire 3 page, where you can now download DriveWire HDB- 
>> DOS ROMs for the CoCo 2 and CoCo 3.  Of course, you will need to  
>> burn your own EPROM in order to take advantage of these images.
>>
>> For those of you who don't have an EPROM burner or cable, we've  
>> dropped the price of our HDB-DOS ROM Pak to $20, and are still  
>> making cables available for $10.
>>
>> The server software for Windows and Mac will go up sometime today.   
>> The Linux server on SourceForge has been updated to handle the new  
>> protocol features.
>>
>> Documentation and NitrOS-9 images will be go up this weekend.
>>
>> Regards,
>> Boisy G. Pitre
>> -- 
>> Tee-Boy
>> Mobile: 337.781.3570
>> Email: boisy at tee-boy.com
>> Web: http://www.tee-boy.com
>>
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From rcrislip at neo.rr.com  Fri Mar  6 12:14:09 2009
From: rcrislip at neo.rr.com (richec)
Date: Fri, 6 Mar 2009 12:14:09 -0500
Subject: [Coco] '68' Micro Journal
In-Reply-To: <1iw3g91.1abu5bvef4sg6M%tlindner@macmess.org>
References: <1iw3g91.1abu5bvef4sg6M%tlindner@macmess.org>
Message-ID: <200903061214.09315.rcrislip@neo.rr.com>

On Thursday 05 March 2009 10:18:26 tim lindner wrote:
> Ryan Pritchard <coconut at pritchard.ca> wrote:
> > That's awesome!  Where does one find them?
>
> I thought they were on the web somewhere. But apearently not.
>
> I'll try to find my copy, and upload them somewhere.

Someone  has them up on a place called Excaliber. I was downloading some until 
I realized I already have them 8-/.


From exwn8jef at gmail.com  Fri Mar  6 12:24:54 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Fri, 06 Mar 2009 12:24:54 -0500
Subject: [Coco] DriveWire 3
In-Reply-To: <1806abd60903060857n3630c102k2942f5fda6caf716@mail.gmail.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>	<49B153BF.4000503@gmail.com>
	<1806abd60903060857n3630c102k2942f5fda6caf716@mail.gmail.com>
Message-ID: <49B15C66.8070205@gmail.com>

Hi Ryan,
Thanks for your help. I will consider this adapter, however, Boisy is 
recommending a FTDI chipset and I think I will concentrate on adapters 
that have it.

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



Ryan Pritchard wrote:
> I think this device will be wonderful.  I know the USB to UART chip is
> compatible with Windows, Linux and Mac OS X.
>
> http://cgi.ebay.ca/CP2102-USB-TTL-RS232-Serial-Port-Converter-Transceiver_W0QQitemZ250382968852QQcmdZViewItemQQptZPCA_Cables_Adapters?hash=item250382968852&_trksid=p4634.c0.m14
>
> Ordering one this week, in preparation of using DriveWire on my CoCo 1, or
> at very least to allow me to communicate with my GIMIX 6809 Ghost machines.
>
> On Fri, Mar 6, 2009 at 10:47 AM, N8WQ <exwn8jef at gmail.com> wrote:
>
>   
>> Boisy,
>> Can you or someone on the list recommend a good USB to Serial adapter?
>> Unfortunately, I don't have a serial connector. :(
>> Thanks...
>>
>> Alan Jones
>>
>> --
>> N8WQ - Canal Winchester, Ohio
>> http://exwn8jef.googlepages.com/home
>>
>>
>>
>> Boisy Pitre wrote:
>>
>>     
>>> As the saying goes, the only way to fight fire is with fire.
>>>
>>> So starting today, DriveWire 3 is now a free downloadable product from
>>> Cloud-9.
>>>
>>> You can go to our website at http://www.cloud9tech.com/ and click on the
>>> DriveWire announcement on the main page.  It will take you to the DriveWire
>>> 3 page, where you can now download DriveWire HDB-DOS ROMs for the CoCo 2 and
>>> CoCo 3.  Of course, you will need to burn your own EPROM in order to take
>>> advantage of these images.
>>>
>>> For those of you who don't have an EPROM burner or cable, we've dropped
>>> the price of our HDB-DOS ROM Pak to $20, and are still making cables
>>> available for $10.
>>>
>>> The server software for Windows and Mac will go up sometime today.  The
>>> Linux server on SourceForge has been updated to handle the new protocol
>>> features.
>>>
>>> Documentation and NitrOS-9 images will be go up this weekend.
>>>
>>> Regards,
>>> Boisy G. Pitre
>>> --
>>> Tee-Boy
>>> Mobile: 337.781.3570
>>> Email: boisy at tee-boy.com
>>> Web: http://www.tee-boy.com
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>
>>>       
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>     
>
>
>
>   


From coconut at pritchard.ca  Fri Mar  6 12:28:33 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Fri, 6 Mar 2009 11:28:33 -0600
Subject: [Coco] '68' Micro Journal
In-Reply-To: <200903061214.09315.rcrislip@neo.rr.com>
References: <1iw3g91.1abu5bvef4sg6M%tlindner@macmess.org>
	<200903061214.09315.rcrislip@neo.rr.com>
Message-ID: <1806abd60903060928n334335eat70c5f4d543e0bef@mail.gmail.com>

I have been at http://excalibur1.net/coco and to ftp://ftp.excalibur1.net,
the '68' Micro Journal magazine is not found by my eyes.

Why is that people say, oh I saw it here and over there but never link to
here or there?

On Fri, Mar 6, 2009 at 11:14 AM, richec <rcrislip at neo.rr.com> wrote:

> On Thursday 05 March 2009 10:18:26 tim lindner wrote:
> > Ryan Pritchard <coconut at pritchard.ca> wrote:
> > > That's awesome!  Where does one find them?
> >
> > I thought they were on the web somewhere. But apearently not.
> >
> > I'll try to find my copy, and upload them somewhere.
>
> Someone  has them up on a place called Excaliber. I was downloading some
> until
> I realized I already have them 8-/.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From exwn8jef at gmail.com  Fri Mar  6 12:29:49 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Fri, 06 Mar 2009 12:29:49 -0500
Subject: [Coco] OT: Windows Vista (puke!) infinite loop re-installing
	KB954430
Message-ID: <49B15D8D.1070509@gmail.com>

Folks,
I apologize for asking a Windows Vista question here :)
My computer keeps trying to update "Security Update for Microsoft XML 
Core Services 4.0 Service Pack 2 (KB954430)" over and over again.

Last week I went to Microsoft online chat help and they could'nt even 
get rid of it! LOL
Thanks...

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



From coconut at pritchard.ca  Fri Mar  6 12:41:09 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Fri, 6 Mar 2009 11:41:09 -0600
Subject: [Coco] OT: Windows Vista (puke!) infinite loop re-installing
	KB954430
In-Reply-To: <49B15D8D.1070509@gmail.com>
References: <49B15D8D.1070509@gmail.com>
Message-ID: <1806abd60903060941x52afe2ejd37e59eddf24226d@mail.gmail.com>

Upgrade to Linux...  ;)

Sorry but Vista support is out of my Linux and primarily Mac OS X existence.

On Fri, Mar 6, 2009 at 11:29 AM, N8WQ <exwn8jef at gmail.com> wrote:

> Folks,
> I apologize for asking a Windows Vista question here :)
> My computer keeps trying to update "Security Update for Microsoft XML Core
> Services 4.0 Service Pack 2 (KB954430)" over and over again.
>
> Last week I went to Microsoft online chat help and they could'nt even get
> rid of it! LOL
> Thanks...
>
> Alan Jones
>
> --
> N8WQ - Canal Winchester, Ohio
> http://exwn8jef.googlepages.com/home
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From boisy at tee-boy.com  Fri Mar  6 12:48:19 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 6 Mar 2009 11:48:19 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <20090306061352.GN7702@warlock.deepthought.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
	<20090305223830.7949020A14@qs281.pair.com>
	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
	<20090306025839.3A62020A13@qs281.pair.com>
	<C485B547-7A3E-415D-8173-779C96B3F6A2@tee-boy.com>
	<20090306051857.6554620A16@qs281.pair.com>
	<20090306061352.GN7702@warlock.deepthought.com>
Message-ID: <7AC92BB6-6880-4274-B8EE-D92ED53304A0@tee-boy.com>

> A few things I would like to see for those that care and have the  
> ability to do it.
>
> A superide type device with a additional port for floppy drives.
> A usb port usable for storage with hdb-dos and nitros support.
> A version of hdb-dos that lets me use my superide adaptor, scsi  
> adaptor and drivewire
> at the same time!!
> and last but not least the ability to use drivewire that will let my  
> coco "print" to
> a file on my pc running linux.

Frank,

I know you mentioned this before and I've been meaning to get a  
response to you.

I have some ideas about how this might be done.  Now that DriveWire 3  
is downloadable, it will be easy to update it for extensions to the  
protocol like printing.

Thanks for the feedback.

Boisy


From t.fadden at cox.net  Fri Mar  6 12:51:30 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Fri, 06 Mar 2009 10:51:30 -0700
Subject: [Coco] OT: Windows Vista (puke!) infinite loop re-installing
 KB954430
In-Reply-To: <49B15D8D.1070509@gmail.com>
References: <49B15D8D.1070509@gmail.com>
Message-ID: <49B162A2.4030901@cox.net>

Do a google search for it, and you will find the answer.  I have had 
this on a couple of vista machines.  Something to do about permissions 
on a file.  You need to uninstall one xml, and then reinstall a 
different on.  I don't remember the exact details.  But I did find the 
solution several places using  a google search.

Why all the Vista bashing?  I have 32 bit and 64 bit vista machines, and 
it is by far the most stable window I have had since windows existed!


Good Luck!

P.S.  I can do the research for a fee. :-)


N8WQ wrote:
> Folks,
> I apologize for asking a Windows Vista question here :)
> My computer keeps trying to update "Security Update for Microsoft XML 
> Core Services 4.0 Service Pack 2 (KB954430)" over and over again.
>
> Last week I went to Microsoft online chat help and they could'nt even 
> get rid of it! LOL
> Thanks...
>
> Alan Jones
>



From boisy at tee-boy.com  Fri Mar  6 12:52:16 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 6 Mar 2009 11:52:16 -0600
Subject: [Coco] DriveWire
In-Reply-To: <49B12C48.2030601@worldnet.att.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>	<20090304060744.GC25102@virgo.sdc.org>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>
	<49B12C48.2030601@worldnet.att.net>
Message-ID: <3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>

On Mar 6, 2009, at 7:59 AM, Robert Gault wrote:

> Boisy Pitre wrote:
>> On Mar 5, 2009, at 9:33 PM, Ryan Pritchard wrote:
>> <snip>
>>> Now where I get lost is that with DriveWire 2 you indicate I could  
>>> boot
>>> strap NitrOS-9 from a DriveWire virtual drive.  Isn't the NitrOS-9  
>>> Level 1
>>> boot diskette either 2 5.25" disks or 1 3.5" disk, since you only  
>>> include
>>> one disk image for NitrOS-9 I presume you are loading the larger  
>>> disk image.
>>> Does NitroOS-9 support for DriveWire allow for larger disk  
>>> images?  whereby
>>> the virtual drives look like larger Hard Drives?
>> Yes, that is correct. Under NitrOS-9, you can format a DriveWire  
>> disk as large as RBF will allow (4GB)
> ><snip>
>
> Ryan, I'm not so sure that Boisy answered your question completely.
>
> NitrOS-9 has a module in the kernel on track 34 called Boot. This  
> module is by default hard coded to read floppies. If you want to  
> boot from a real hard drive via a scsi or ide interface or from a  
> virtual hard drive via DriveWire, the boot module must be replaced  
> with a special one to access the correct hardware. This is done for  
> you (I think) by Cloud-9 when you purchase their products.
> The size of the drive where the main NitrOS-9 system is installed,  
> is not dependent on the interface that talks to the drive as much as  
> it depends on the actual OS-9 / NitrOS-9 software. The size of a  
> disk is stored on the disk's first sector in 3 bytes indicating  
> total sectors, DD.TOT. So you are limited to $FFFFFF sectors. The  
> sectors don't need to be 256 bytes (standard) but that is still 4GB.
>
> So when booting via DriveWire or an IDE or SCSI system, you will  
> still use a floppy. The floppy can be a virtual floppy in which case  
> it is a 35 track single sided image containing only the kernel on  
> T17 and the os9Boot file.
> You can get a feel for this with several emulators using RGBDOS for  
> emulators. Both the emulator version of RGBDOS and HDBDOS derive  
> from the same RGBDOS sold with KEN-TON SCSI hard drive systems for  
> the Coco.

Robert,

Thanks for the in-depth explanation.  Ryan, Robert is right.  A boot  
module for DriveWire exists to get the bootfile from the DriveWire  
server and bootstrap into NitrOS-9.  The NitrOS-9 disk image that will  
be supplied over the weekend will have all of this set up.  You would  
simply mount the disk image in the drive, bring up your CoCo into HDB- 
DOS and type DOS, then the booting would commence.


>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From goosey at virgo.sdc.org  Fri Mar  6 12:58:25 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Fri, 6 Mar 2009 10:58:25 -0700
Subject: [Coco] Oops, my bad was Re:  16550 wasRe:  RS232 paks
In-Reply-To: <0E031C3B-7C12-4850-9015-E24B13E996C8@tee-boy.com>
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<49B079FB.5010701@cox.net> <002401c99dfb$a25373a0$0701a8c0@master>
	<20090306014416.GG14496@virgo.sdc.org>
	<0E031C3B-7C12-4850-9015-E24B13E996C8@tee-boy.com>
Message-ID: <20090306175825.GA24020@virgo.sdc.org>

On Thu, Mar 05, 2009 at 07:57:18PM -0600, Boisy Pitre wrote:
> Willard,
> 
> You can thank Alan DeKok for that work.  He went into the kernel and  
> optimized interrupt handling as best as he could and squeezed some  
> additional performance.  NitrOS-9 still carries those enhancements.

Oops, Sorry about that Alan, and thank you.

Sorry for mis-spelling your name, too, Boisy. :-(

Someday I'll learn to stay out of flamewars.

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From coconut at pritchard.ca  Fri Mar  6 13:43:48 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Fri, 6 Mar 2009 12:43:48 -0600
Subject: [Coco] DriveWire
In-Reply-To: <3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>
	<49B12C48.2030601@worldnet.att.net>
	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
Message-ID: <1806abd60903061043j24d1d760hafdff573ee83b6dc@mail.gmail.com>

Boisy,

These responses from you and Robert are very informational.  Now I have a
couple of questions.

You have DriveWire 3 HDB-DOS ROM Pak available (and if I recall correctly
had a DriveWire 2 ROM Pak previously).
When you say ROM Pak are you saying a board with a ROM on it?
Or are you meaning a ROM that fits into say... an existing 26-3029 FDC ROM
socket?

I am contemplating the idea of getting the TC^3 SCSI Controller or the
SuperIDE Interface.  It looks like I could definitely use the TC^3 SCSI
Controller on a Y Cable with my 26-3029 FDC.  It also seems that I may be
able to use the SuperIDE Interface on a Y Cable, provided I either disable
the SuperIDE flash ROM or have the 26-3029 ROM disabled and an equivalent
ROM (DriveWire HDB-DOS) loaded in the SuperIDE flash ROM.  It would seem I
could then keep my physical floppy drives accessible.

Remaining concern for me is that I own a CoCo 1 and unless you provide
DriveWire 2 still and my above presumptions are correct, there is no easy
way for me to have access to virtual disk images, and physyical floppy
drives and possible physical hard drives (or Zip drive).

On Fri, Mar 6, 2009 at 11:52 AM, Boisy Pitre <boisy at tee-boy.com> wrote:

> On Mar 6, 2009, at 7:59 AM, Robert Gault wrote:
>
>  Boisy Pitre wrote:
>>
>>> On Mar 5, 2009, at 9:33 PM, Ryan Pritchard wrote:
>>> <snip>
>>>
>>>> Now where I get lost is that with DriveWire 2 you indicate I could boot
>>>> strap NitrOS-9 from a DriveWire virtual drive.  Isn't the NitrOS-9 Level
>>>> 1
>>>> boot diskette either 2 5.25" disks or 1 3.5" disk, since you only
>>>> include
>>>> one disk image for NitrOS-9 I presume you are loading the larger disk
>>>> image.
>>>> Does NitroOS-9 support for DriveWire allow for larger disk images?
>>>>  whereby
>>>> the virtual drives look like larger Hard Drives?
>>>>
>>> Yes, that is correct. Under NitrOS-9, you can format a DriveWire disk as
>>> large as RBF will allow (4GB)
>>>
>> ><snip>
>>
>> Ryan, I'm not so sure that Boisy answered your question completely.
>>
>> NitrOS-9 has a module in the kernel on track 34 called Boot. This module
>> is by default hard coded to read floppies. If you want to boot from a real
>> hard drive via a scsi or ide interface or from a virtual hard drive via
>> DriveWire, the boot module must be replaced with a special one to access the
>> correct hardware. This is done for you (I think) by Cloud-9 when you
>> purchase their products.
>> The size of the drive where the main NitrOS-9 system is installed, is not
>> dependent on the interface that talks to the drive as much as it depends on
>> the actual OS-9 / NitrOS-9 software. The size of a disk is stored on the
>> disk's first sector in 3 bytes indicating total sectors, DD.TOT. So you are
>> limited to $FFFFFF sectors. The sectors don't need to be 256 bytes
>> (standard) but that is still 4GB.
>>
>> So when booting via DriveWire or an IDE or SCSI system, you will still use
>> a floppy. The floppy can be a virtual floppy in which case it is a 35 track
>> single sided image containing only the kernel on T17 and the os9Boot file.
>> You can get a feel for this with several emulators using RGBDOS for
>> emulators. Both the emulator version of RGBDOS and HDBDOS derive from the
>> same RGBDOS sold with KEN-TON SCSI hard drive systems for the Coco.
>>
>
> Robert,
>
> Thanks for the in-depth explanation.  Ryan, Robert is right.  A boot module
> for DriveWire exists to get the bootfile from the DriveWire server and
> bootstrap into NitrOS-9.  The NitrOS-9 disk image that will be supplied over
> the weekend will have all of this set up.  You would simply mount the disk
> image in the drive, bring up your CoCo into HDB-DOS and type DOS, then the
> booting would commence.
>
>
>
>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From 6809er at bjork-huffman.net  Fri Mar  6 13:43:56 2009
From: 6809er at bjork-huffman.net (Steve Bjork)
Date: Fri, 06 Mar 2009 10:43:56 -0800
Subject: [Coco] DriveWire 3
In-Reply-To: <49B153BF.4000503@gmail.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
	<49B153BF.4000503@gmail.com>
Message-ID: <49B16EEC.7040200@bjork-huffman.net>

Or you can get a serial PCI card for $15.00 at newegg.com and that comes 
with 2 ports.
I found that the card solutions work better than most USB serial ports.

Steve

N8WQ wrote:
> Can you or someone on the list recommend a good USB to Serial adapter?
> Unfortunately, I don't have a serial connector. :(
> Thanks...
>
> Alan Jones
>



From johnguin at hotmail.com  Fri Mar  6 13:44:18 2009
From: johnguin at hotmail.com (John Guin)
Date: Fri, 6 Mar 2009 10:44:18 -0800
Subject: [Coco] OT: Windows Vista (puke!) infinite loop
	re-installing	KB954430
In-Reply-To: <49B15D8D.1070509@gmail.com>
References: <49B15D8D.1070509@gmail.com>
Message-ID: <BAY138-DAV139119D9B23BCF0FD1C2BAD9A50@phx.gbl>

Are you hitting this problem?
http://marc.info/?l=patchmanagement&m=122643928517278&w=2

John

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
Behalf Of N8WQ
Sent: Friday, March 06, 2009 9:30 AM
To: CoCoList for Color Computer Enthusiasts
Subject: [Coco] OT: Windows Vista (puke!) infinite loop re-installing
KB954430

Folks,
I apologize for asking a Windows Vista question here :)
My computer keeps trying to update "Security Update for Microsoft XML 
Core Services 4.0 Service Pack 2 (KB954430)" over and over again.

Last week I went to Microsoft online chat help and they could'nt even 
get rid of it! LOL
Thanks...

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



From rgtryner at yahoo.com  Fri Mar  6 03:51:45 2009
From: rgtryner at yahoo.com (Robert)
Date: Fri, 06 Mar 2009 08:51:45 -0000
Subject: [Coco] [Color Computer] Re: looking for speech sound module
In-Reply-To: <gminpu+i5pi@eGroups.com>
Message-ID: <goqo71+ig5t@eGroups.com>

--- In ColorComputer at yahoogroups.com, "coconutcowboy2002" <coconutcowboy2002 at ...> wrote:
>
> I am looking for a speech sound module, I am willing to pay the price 
> of a good clean one with manual.
> thanks
>
Are you still looking for a SSC?  If so, I'll check my storage, I think I have one.



From cwgordon at carolina.rr.com  Fri Mar  6 13:46:36 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Fri, 6 Mar 2009 13:46:36 -0500
Subject: [Coco] Plug & Power Controller
Message-ID: <00a801c99e8b$e14b21d0$a3e16570$@rr.com>

Does anyone have the manual for the 26-1182 Plug & Power Controller? I
looked on Excalibur, but I didn't see it.

Thanks

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784





From afra at aurigae.demon.co.uk  Fri Mar  6 13:50:36 2009
From: afra at aurigae.demon.co.uk (Phill Harvey-Smith)
Date: Fri, 06 Mar 2009 18:50:36 +0000
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <7AC92BB6-6880-4274-B8EE-D92ED53304A0@tee-boy.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>	<20090305223830.7949020A14@qs281.pair.com>	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>	<20090306025839.3A62020A13@qs281.pair.com>	<C485B547-7A3E-415D-8173-779C96B3F6A2@tee-boy.com>	<20090306051857.6554620A16@qs281.pair.com>	<20090306061352.GN7702@warlock.deepthought.com>
	<7AC92BB6-6880-4274-B8EE-D92ED53304A0@tee-boy.com>
Message-ID: <49B1707C.5000308@aurigae.demon.co.uk>

Boisy Pitre wrote:
> I have some ideas about how this might be done.  Now that DriveWire 3 is 
> downloadable, it will be easy to update it for extensions to the 
> protocol like printing.

Something else I always meant to implement, was the ability to stream a 
.cas file across drivewire to an intercepted cassette routine, for those 
things that don't like being loaded from disk.

Cheers.

Phill.

-- 
Phill Harvey-Smith, Programmer, Hardware hacker, and general eccentric !

"You can twist perceptions, but reality won't budge" -- Rush.


From boisy at tee-boy.com  Fri Mar  6 13:52:51 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 6 Mar 2009 12:52:51 -0600
Subject: [Coco] DriveWire
In-Reply-To: <1806abd60903061043j24d1d760hafdff573ee83b6dc@mail.gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<20090304060744.GC25102@virgo.sdc.org>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>
	<49B12C48.2030601@worldnet.att.net>
	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
	<1806abd60903061043j24d1d760hafdff573ee83b6dc@mail.gmail.com>
Message-ID: <2EC31C04-7F95-4BE1-A19E-8595B793D3B5@tee-boy.com>

On Mar 6, 2009, at 12:43 PM, Ryan Pritchard wrote:

> Boisy,
>
> These responses from you and Robert are very informational.  Now I  
> have a
> couple of questions.
>
> You have DriveWire 3 HDB-DOS ROM Pak available (and if I recall  
> correctly
> had a DriveWire 2 ROM Pak previously).
> When you say ROM Pak are you saying a board with a ROM on it?
> Or are you meaning a ROM that fits into say... an existing 26-3029  
> FDC ROM
> socket?

The ROM Pak is just that.. a ROM Pak.  It has a socket and an EPROM  
burned with HDB-DOS for DriveWire 3.  You could remove the EPROM from  
the pak and put it in a disk controller.

> I am contemplating the idea of getting the TC^3 SCSI Controller or the
> SuperIDE Interface.  It looks like I could definitely use the TC^3  
> SCSI
> Controller on a Y Cable with my 26-3029 FDC.  It also seems that I  
> may be
> able to use the SuperIDE Interface on a Y Cable, provided I either  
> disable
> the SuperIDE flash ROM or have the 26-3029 ROM disabled and an  
> equivalent
> ROM (DriveWire HDB-DOS) loaded in the SuperIDE flash ROM.  It would  
> seem I
> could then keep my physical floppy drives accessible.

Absolutely.  You can download the newly available ROMs from our  
website and flash them into one of the banks of the SuperIDE.

> Remaining concern for me is that I own a CoCo 1 and unless you provide
> DriveWire 2 still and my above presumptions are correct, there is no  
> easy
> way for me to have access to virtual disk images, and physyical floppy
> drives and possible physical hard drives (or Zip drive).

I'm working on that and should have something to report before long.

>
> On Fri, Mar 6, 2009 at 11:52 AM, Boisy Pitre <boisy at tee-boy.com>  
> wrote:
>
>> On Mar 6, 2009, at 7:59 AM, Robert Gault wrote:
>>
>> Boisy Pitre wrote:
>>>
>>>> On Mar 5, 2009, at 9:33 PM, Ryan Pritchard wrote:
>>>> <snip>
>>>>
>>>>> Now where I get lost is that with DriveWire 2 you indicate I  
>>>>> could boot
>>>>> strap NitrOS-9 from a DriveWire virtual drive.  Isn't the  
>>>>> NitrOS-9 Level
>>>>> 1
>>>>> boot diskette either 2 5.25" disks or 1 3.5" disk, since you only
>>>>> include
>>>>> one disk image for NitrOS-9 I presume you are loading the larger  
>>>>> disk
>>>>> image.
>>>>> Does NitroOS-9 support for DriveWire allow for larger disk images?
>>>>> whereby
>>>>> the virtual drives look like larger Hard Drives?
>>>>>
>>>> Yes, that is correct. Under NitrOS-9, you can format a DriveWire  
>>>> disk as
>>>> large as RBF will allow (4GB)
>>>>
>>>> <snip>
>>>
>>> Ryan, I'm not so sure that Boisy answered your question completely.
>>>
>>> NitrOS-9 has a module in the kernel on track 34 called Boot. This  
>>> module
>>> is by default hard coded to read floppies. If you want to boot  
>>> from a real
>>> hard drive via a scsi or ide interface or from a virtual hard  
>>> drive via
>>> DriveWire, the boot module must be replaced with a special one to  
>>> access the
>>> correct hardware. This is done for you (I think) by Cloud-9 when you
>>> purchase their products.
>>> The size of the drive where the main NitrOS-9 system is installed,  
>>> is not
>>> dependent on the interface that talks to the drive as much as it  
>>> depends on
>>> the actual OS-9 / NitrOS-9 software. The size of a disk is stored  
>>> on the
>>> disk's first sector in 3 bytes indicating total sectors, DD.TOT.  
>>> So you are
>>> limited to $FFFFFF sectors. The sectors don't need to be 256 bytes
>>> (standard) but that is still 4GB.
>>>
>>> So when booting via DriveWire or an IDE or SCSI system, you will  
>>> still use
>>> a floppy. The floppy can be a virtual floppy in which case it is a  
>>> 35 track
>>> single sided image containing only the kernel on T17 and the  
>>> os9Boot file.
>>> You can get a feel for this with several emulators using RGBDOS for
>>> emulators. Both the emulator version of RGBDOS and HDBDOS derive  
>>> from the
>>> same RGBDOS sold with KEN-TON SCSI hard drive systems for the Coco.
>>>
>>
>> Robert,
>>
>> Thanks for the in-depth explanation.  Ryan, Robert is right.  A  
>> boot module
>> for DriveWire exists to get the bootfile from the DriveWire server  
>> and
>> bootstrap into NitrOS-9.  The NitrOS-9 disk image that will be  
>> supplied over
>> the weekend will have all of this set up.  You would simply mount  
>> the disk
>> image in the drive, bring up your CoCo into HDB-DOS and type DOS,  
>> then the
>> booting would commence.
>>
>>
>>
>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
>
> -- 
> Regards,
>
> Ryan Pritchard
> Fun Extends All Basic Life Expectancies
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From coconut at pritchard.ca  Fri Mar  6 13:53:21 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Fri, 6 Mar 2009 12:53:21 -0600
Subject: [Coco] DriveWire
In-Reply-To: <1806abd60903061043j24d1d760hafdff573ee83b6dc@mail.gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>
	<49B12C48.2030601@worldnet.att.net>
	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
	<1806abd60903061043j24d1d760hafdff573ee83b6dc@mail.gmail.com>
Message-ID: <1806abd60903061053t218d90dcw1bd96a35bec66bd8@mail.gmail.com>

I realize I can keep looking for an MPI on ebay, but when I start looking at
all the various costs, I have to make some concessions at first, otherwise
it will be a long while before I get running any better than my two drive
setup running NitrOS-9 currently.

No easy way to get new programs to it, because my only working 5.25" drive
is actually an 80 track 720KB DD drive and my only working 3.5" drives are
1.44MB using the all too unrealiable 1.44MB diskette with the hole covered
to make the drive think I am using a 720KB DD diskette.

I have 3-4 of each 3.5" (720KB/1.44MB) and 5.25" (360KB/1.2MB) drives, I
just haven't been having a lot of luck getting the 5.25" drives to do
anything.  I technically have 5 working 5.25" 80 track 720KB DD drives, but
they don't help me if I get 35-40 track diskettes sent to me.

On Fri, Mar 6, 2009 at 12:43 PM, Ryan Pritchard <coconut at pritchard.ca>wrote:

> Boisy,
>
> These responses from you and Robert are very informational.  Now I have a
> couple of questions.
>
> You have DriveWire 3 HDB-DOS ROM Pak available (and if I recall correctly
> had a DriveWire 2 ROM Pak previously).
> When you say ROM Pak are you saying a board with a ROM on it?
> Or are you meaning a ROM that fits into say... an existing 26-3029 FDC ROM
> socket?
>
> I am contemplating the idea of getting the TC^3 SCSI Controller or the
> SuperIDE Interface.  It looks like I could definitely use the TC^3 SCSI
> Controller on a Y Cable with my 26-3029 FDC.  It also seems that I may be
> able to use the SuperIDE Interface on a Y Cable, provided I either disable
> the SuperIDE flash ROM or have the 26-3029 ROM disabled and an equivalent
> ROM (DriveWire HDB-DOS) loaded in the SuperIDE flash ROM.  It would seem I
> could then keep my physical floppy drives accessible.
>
> Remaining concern for me is that I own a CoCo 1 and unless you provide
> DriveWire 2 still and my above presumptions are correct, there is no easy
> way for me to have access to virtual disk images, and physyical floppy
> drives and possible physical hard drives (or Zip drive).
>
>
> On Fri, Mar 6, 2009 at 11:52 AM, Boisy Pitre <boisy at tee-boy.com> wrote:
>
>> On Mar 6, 2009, at 7:59 AM, Robert Gault wrote:
>>
>>  Boisy Pitre wrote:
>>>
>>>> On Mar 5, 2009, at 9:33 PM, Ryan Pritchard wrote:
>>>> <snip>
>>>>
>>>>> Now where I get lost is that with DriveWire 2 you indicate I could boot
>>>>> strap NitrOS-9 from a DriveWire virtual drive.  Isn't the NitrOS-9
>>>>> Level 1
>>>>> boot diskette either 2 5.25" disks or 1 3.5" disk, since you only
>>>>> include
>>>>> one disk image for NitrOS-9 I presume you are loading the larger disk
>>>>> image.
>>>>> Does NitroOS-9 support for DriveWire allow for larger disk images?
>>>>>  whereby
>>>>> the virtual drives look like larger Hard Drives?
>>>>>
>>>> Yes, that is correct. Under NitrOS-9, you can format a DriveWire disk as
>>>> large as RBF will allow (4GB)
>>>>
>>> ><snip>
>>>
>>> Ryan, I'm not so sure that Boisy answered your question completely.
>>>
>>> NitrOS-9 has a module in the kernel on track 34 called Boot. This module
>>> is by default hard coded to read floppies. If you want to boot from a real
>>> hard drive via a scsi or ide interface or from a virtual hard drive via
>>> DriveWire, the boot module must be replaced with a special one to access the
>>> correct hardware. This is done for you (I think) by Cloud-9 when you
>>> purchase their products.
>>> The size of the drive where the main NitrOS-9 system is installed, is not
>>> dependent on the interface that talks to the drive as much as it depends on
>>> the actual OS-9 / NitrOS-9 software. The size of a disk is stored on the
>>> disk's first sector in 3 bytes indicating total sectors, DD.TOT. So you are
>>> limited to $FFFFFF sectors. The sectors don't need to be 256 bytes
>>> (standard) but that is still 4GB.
>>>
>>> So when booting via DriveWire or an IDE or SCSI system, you will still
>>> use a floppy. The floppy can be a virtual floppy in which case it is a 35
>>> track single sided image containing only the kernel on T17 and the os9Boot
>>> file.
>>> You can get a feel for this with several emulators using RGBDOS for
>>> emulators. Both the emulator version of RGBDOS and HDBDOS derive from the
>>> same RGBDOS sold with KEN-TON SCSI hard drive systems for the Coco.
>>>
>>
>> Robert,
>>
>> Thanks for the in-depth explanation.  Ryan, Robert is right.  A boot
>> module for DriveWire exists to get the bootfile from the DriveWire server
>> and bootstrap into NitrOS-9.  The NitrOS-9 disk image that will be supplied
>> over the weekend will have all of this set up.  You would simply mount the
>> disk image in the drive, bring up your CoCo into HDB-DOS and type DOS, then
>> the booting would commence.
>>
>>
>>
>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
>
> --
> Regards,
>
> Ryan Pritchard
> Fun Extends All Basic Life Expectancies
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From boisy at tee-boy.com  Fri Mar  6 13:54:27 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 6 Mar 2009 12:54:27 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <49B1707C.5000308@aurigae.demon.co.uk>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>	<20090305223830.7949020A14@qs281.pair.com>	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>	<20090306025839.3A62020A13@qs281.pair.com>	<C485B547-7A3E-415D-8173-779C96B3F6A2@tee-boy.com>	<20090306051857.6554620A16@qs281.pair.com>	<20090306061352.GN7702@warlock.deepthought.com>
	<7AC92BB6-6880-4274-B8EE-D92ED53304A0@tee-boy.com>
	<49B1707C.5000308@aurigae.demon.co.uk>
Message-ID: <023F3830-9115-4D37-8239-7B6B65F1DBD7@tee-boy.com>

On Mar 6, 2009, at 12:50 PM, Phill Harvey-Smith wrote:

> Boisy Pitre wrote:
>> I have some ideas about how this might be done.  Now that DriveWire  
>> 3 is downloadable, it will be easy to update it for extensions to  
>> the protocol like printing.
>
> Something else I always meant to implement, was the ability to  
> stream a .cas file across drivewire to an intercepted cassette  
> routine, for those things that don't like being loaded from disk.

That's a good idea.  Feel free to look at the latest version of the  
DriveWire 3 Protocol Specification document on the support page of our  
website.  I just updated it to include Frank's printing request.

>
> Cheers.
>
> Phill.
>
> -- 
> Phill Harvey-Smith, Programmer, Hardware hacker, and general  
> eccentric !
>
> "You can twist perceptions, but reality won't budge" -- Rush.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From cwgordon at carolina.rr.com  Fri Mar  6 14:20:42 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Fri, 6 Mar 2009 14:20:42 -0500
Subject: [Coco] Technical question
Message-ID: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>

I was given a CoCo3, but it doesn't work. The MOTORON and MOTOROFF functions
do not work. The RF to the TV is EXTREMELY snowy and full of static.

Question #1-can all this be fixed?

Question #2-can all this be fixed for a reasonable price?

Question #3-is it worth it?

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784





From 6809er at bjork-huffman.net  Fri Mar  6 14:28:01 2009
From: 6809er at bjork-huffman.net (Steve Bjork)
Date: Fri, 06 Mar 2009 11:28:01 -0800
Subject: [Coco] Plug & Power Controller
In-Reply-To: <00a801c99e8b$e14b21d0$a3e16570$@rr.com>
References: <00a801c99e8b$e14b21d0$a3e16570$@rr.com>
Message-ID: <49B17941.4050500@bjork-huffman.net>

Hey bill, the Plug & Power Controller software does NOT work on a CoCo 
3.  (only a CoCo 1&2)
Beside, your CoCo 3 is dead anyway.

Bill wrote:
> Does anyone have the manual for the 26-1182 Plug & Power Controller? I
> looked on Excalibur, but I didn't see it.
>
> Thanks
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>   



From cwgordon at carolina.rr.com  Fri Mar  6 14:33:52 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Fri, 6 Mar 2009 14:33:52 -0500
Subject: [Coco] Plug & Power Controller
In-Reply-To: <49B17941.4050500@bjork-huffman.net>
References: <00a801c99e8b$e14b21d0$a3e16570$@rr.com>
	<49B17941.4050500@bjork-huffman.net>
Message-ID: <00be01c99e92$7b4a4ad0$71dee070$@rr.com>

Hehehehe, My Coco 3 AND my Coco 2 are dead. BUT, ya never know when one
might come along that I can get.....(crossing his fingers). So I'm still
looking for the manual.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Steve Bjork
> Sent: Friday, March 06, 2009 2:28 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Plug & Power Controller
> 
> Hey bill, the Plug & Power Controller software does NOT work on a CoCo
> 3.  (only a CoCo 1&2)
> Beside, your CoCo 3 is dead anyway.
> 



From flexser at fiu.edu  Fri Mar  6 14:43:22 2009
From: flexser at fiu.edu (Arthur Flexser)
Date: Fri, 6 Mar 2009 14:43:22 -0500
Subject: [Coco] Technical question
In-Reply-To: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
References: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
Message-ID: <dbdeb2610903061143q6d08b750nb01e358351360515@mail.gmail.com>

Quite likely, both problems are due to their respective cables, the
cassette cable in the MOTORON/OFF case
and the notoriously bad RF cable for connecting to the TV,
which is poorly shielded.  You might try switching the output from
Channel 3 to Channel 4 to see if that helps any, though I doubt that
would make much difference.  Another thing to try with the CoCo turned
on and outputting to the TV is changing the TV channel to and from the
CoCo's output channel, to let the TV's automatic tuning
adjust to the CoCo's signal.  Plugging the TV and the CoCo into
different electrical outlets might also reduce the interference.

Most CoCo users use a monitor of some sort rather than a TV, which
generally gives a far better picture, especially if it is an RGB one.
You might check if your TV has video and audio RCA-type inputs, and
connect them to the composite output and audio output jacks of the
CoCo instead of using the RF output.  That should help a great deal.

Most CoCo users also use disk systems rather than cassette, so
MOTORON/OFF wouldn't be needed.  The cassette can be started and
stopped manually in any case.
(The cassette's PLAY button must be down for MOTORON and MOTOROFF to
have any effect, by the way.)

Art

On Fri, Mar 6, 2009 at 2:20 PM, Bill <cwgordon at carolina.rr.com> wrote:
> I was given a CoCo3, but it doesn't work. The MOTORON and MOTOROFF functions
> do not work. The RF to the TV is EXTREMELY snowy and full of static.
>
> Question #1-can all this be fixed?
>
> Question #2-can all this be fixed for a reasonable price?
>
> Question #3-is it worth it?
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From fwp at deepthought.com  Fri Mar  6 15:34:00 2009
From: fwp at deepthought.com (Frank Pittel)
Date: Fri, 6 Mar 2009 14:34:00 -0600
Subject: [Coco] DriveWire 3
In-Reply-To: <49B16EEC.7040200@bjork-huffman.net>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
	<49B153BF.4000503@gmail.com> <49B16EEC.7040200@bjork-huffman.net>
Message-ID: <20090306203400.GO7702@warlock.deepthought.com>

Does the card use a 6551?? :-) (ducking and running)


On Fri, Mar 06, 2009 at 10:43:56AM -0800, Steve Bjork wrote:
> Or you can get a serial PCI card for $15.00 at newegg.com and that comes  
> with 2 ports.
> I found that the card solutions work better than most USB serial ports.
>
> Steve
>
> N8WQ wrote:
>> Can you or someone on the list recommend a good USB to Serial adapter?
>> Unfortunately, I don't have a serial connector. :(
>> Thanks...
>>
>> Alan Jones
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


From jimgerrie at ns.sympatico.ca  Fri Mar  6 14:41:24 2009
From: jimgerrie at ns.sympatico.ca (James Gerrie)
Date: Fri, 06 Mar 2009 19:41:24 -0000
Subject: [Color Computer] Re: [Coco] Possible solution for yellowing plastic? -- Retr0Bright » home
In-Reply-To: <gohl5g+4i7s@eGroups.com>
Message-ID: <goru94+6fs9@eGroups.com>

I hear lemon juice works.  Don't know if it is safe.  Never tried it.  I don't mind the smokey look.


From cwgordon at carolina.rr.com  Fri Mar  6 15:00:21 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Fri, 6 Mar 2009 15:00:21 -0500
Subject: [Coco] [Color Computer] Re: Possible solution for yellowing
	plastic? -- Retr0Bright ; home  ** DUPLICATE MESSAGES **
In-Reply-To: <goru94+6fs9@eGroups.com>
References: <gohl5g+4i7s@eGroups.com> <goru94+6fs9@eGroups.com>
Message-ID: <00c201c99e96$2ee48120$8cad8360$@rr.com>

This one I got three copies of, and two more copies in the Radio Shack Coco
(Tandy) Group

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of James Gerrie
> Sent: Friday, March 06, 2009 2:41 PM
> To: ColorComputer at yahoogroups.com
> Subject: [Color Computer] Re: [Coco] Possible solution for yellowing
> plastic? -- Retr0Bright ; home
> 
> I hear lemon juice works.  Don't know if it is safe.  Never tried it.
> I don't mind the smokey look.
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From cwgordon at carolina.rr.com  Fri Mar  6 15:07:47 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Fri, 6 Mar 2009 15:07:47 -0500
Subject: [Coco] Technical question
In-Reply-To: <dbdeb2610903061143q6d08b750nb01e358351360515@mail.gmail.com>
References: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
	<dbdeb2610903061143q6d08b750nb01e358351360515@mail.gmail.com>
Message-ID: <00c301c99e97$3832bf70$a8983e50$@rr.com>

Hello, Arthur, long time no chat...

#1
The cable I am using is the one that has been working perfectly on the
Coco2, before it went "toes up"

#2
Tried all that. Changed channels, tried another cable, tried another TV in
another room. Still too snowy and too much static to see.

#3
I was hoping that would work, however my TVs are too old for that feature.
They do fine watching cable TV and DVDs, but they don't have a monitor input

#4
I haven't been able to come up with a disk drive yet, so cassette is my only
option.

I do appreciate your input, however. 

Now, search your "memory banks" and see if you can remember me :)

Take care....

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Arthur Flexser
> Sent: Friday, March 06, 2009 2:43 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Technical question

#1 
> Quite likely, both problems are due to their respective cables, the
> cassette cable in the MOTORON/OFF case

#2
> and the notoriously bad RF cable for connecting to the TV,
> which is poorly shielded.  You might try switching the output from
> Channel 3 to Channel 4 to see if that helps any, though I doubt that
> would make much difference.  Another thing to try with the CoCo turned
> on and outputting to the TV is changing the TV channel to and from the
> CoCo's output channel, to let the TV's automatic tuning
> adjust to the CoCo's signal.  Plugging the TV and the CoCo into
> different electrical outlets might also reduce the interference.

#3 
> Most CoCo users use a monitor of some sort rather than a TV, which
> generally gives a far better picture, especially if it is an RGB one.
> You might check if your TV has video and audio RCA-type inputs, and
> connect them to the composite output and audio output jacks of the
> CoCo instead of using the RF output.  That should help a great deal.

#4 
> Most CoCo users also use disk systems rather than cassette, so
> MOTORON/OFF wouldn't be needed.  The cassette can be started and
> stopped manually in any case. (The cassette's PLAY button must be 
> down for MOTORON and MOTOROFF to have any effect, by the way.)



From robert.gault at worldnet.att.net  Fri Mar  6 16:15:46 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Fri, 06 Mar 2009 16:15:46 -0500
Subject: [Coco] DriveWire
In-Reply-To: <3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>	<20090304060744.GC25102@virgo.sdc.org>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>
	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
Message-ID: <49B19282.7080902@worldnet.att.net>

Boisy,

I've a question regards the new DriveWire ROM. I've been able to boot 
with it installed in both MESS and VCC as it is easy to replace the ROM 
images. I do have an EPROM programmer but thought I would first try the 
following with a real 6309 Coco3.

The original RGBDOS could be offset loaded into RAM (say $3000) and then 
moved into the correct location with a short ml program. RGBDOS booted 
and could be used as a test case this way before burning a ROM.
I tried that with the new drivewire ROM and it won't work, the Coco3 
crashes. Here is the ml code that moves the ROM. Any reason why this 
shouldn't work?

  org $7000
start orcc #$50
  ldx #$3000    where the ROM was offset loaded
  ldy #$c000
a@ ldd ,x++
  std ,y++
  cmpx #$e000
  blo a@
  jmp $c002
  end start

And yes, I did add the header and footer to turn the ROM into a LOADM 
binary.


From jps.subscriptions at gmail.com  Fri Mar  6 16:18:05 2009
From: jps.subscriptions at gmail.com (J.P. Samson)
Date: Fri, 6 Mar 2009 14:18:05 -0700
Subject: [Coco] DriveWire 3
In-Reply-To: <49B15C66.8070205@gmail.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>	<49B153BF.4000503@gmail.com>
	<1806abd60903060857n3630c102k2942f5fda6caf716@mail.gmail.com>
	<49B15C66.8070205@gmail.com>
Message-ID: <075DCCE2-63CC-43F8-A278-AFCA7D64C207@gmail.com>

On Mar 6, 2009, at 10:24 AM, N8WQ wrote:
> Thanks for your help. I will consider this adapter, however, Boisy  
> is recommending a FTDI chipset and I think I will concentrate on  
> adapters that have it.


Here's where I picked up my USB-to-serial adapters:
http://www.mouser.com/Search/Refine.aspx?N=254076&Keyword=895-US232R&FS=True

(It was a real b*tch to find a place that carried the FTDI cables and  
would ship to Canada.)

-- JP



From robert.gault at worldnet.att.net  Fri Mar  6 16:20:43 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Fri, 06 Mar 2009 16:20:43 -0500
Subject: [Coco] Technical question
In-Reply-To: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
References: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
Message-ID: <49B193AB.7000709@worldnet.att.net>

Bill wrote:
> I was given a CoCo3, but it doesn't work. The MOTORON and MOTOROFF functions
> do not work. The RF to the TV is EXTREMELY snowy and full of static.
> 
> Question #1-can all this be fixed?
> 
> Question #2-can all this be fixed for a reasonable price?
> 
> Question #3-is it worth it?
> 
> ______________________________________


Many if not most Coco3 problems can be "cured" by removing the GIME 
(large square chip) from its socket and re-seating it. It's an oxidation 
problem. Be careful, you will need something better than two small 
screwdrivers to do this without causing damage.


From boisy at tee-boy.com  Fri Mar  6 16:25:25 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 6 Mar 2009 15:25:25 -0600
Subject: [Coco] DriveWire
In-Reply-To: <49B19282.7080902@worldnet.att.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<6774C6DE-62BE-48D6-A6F2-6EAD95F62843@gmail.com>	<00a501c99c56$916e3850$0701a8c0@master>	<fc509d260903031628x24c5681dq1e443791f50837a@mail.gmail.com>	<20090304060744.GC25102@virgo.sdc.org>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>
	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
	<49B19282.7080902@worldnet.att.net>
Message-ID: <B60FE60D-FEAF-4E9D-879F-A17C93F1AC19@tee-boy.com>

On Mar 6, 2009, at 3:15 PM, Robert Gault wrote:

> Boisy,
>
> I've a question regards the new DriveWire ROM. I've been able to  
> boot with it installed in both MESS and VCC as it is easy to replace  
> the ROM images. I do have an EPROM programmer but thought I would  
> first try the following with a real 6309 Coco3.
>
> The original RGBDOS could be offset loaded into RAM (say $3000) and  
> then moved into the correct location with a short ml program. RGBDOS  
> booted and could be used as a test case this way before burning a ROM.
> I tried that with the new drivewire ROM and it won't work, the Coco3  
> crashes. Here is the ml code that moves the ROM. Any reason why this  
> shouldn't work?
>
> org $7000
> start orcc #$50
> ldx #$3000    where the ROM was offset loaded
> ldy #$c000
> a@ ldd ,x++
> std ,y++
> cmpx #$e000
> blo a@
> jmp $c002
> end start
>
> And yes, I did add the header and footer to turn the ROM into a  
> LOADM binary.

Robert,

Just to be clear: you're wrapping a LOADM header and footer around the  
image and place it on a disk, doing a LOADM (it now resides at $3000),  
LOADM your patch code, then EXEC &H7000.

Seems to me you would be writing right over the existing Disk BASIC  
(or RGBDOS) ROM at $C000, and that could certainly cause a crash??

>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From cwgordon at carolina.rr.com  Fri Mar  6 16:26:32 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Fri, 6 Mar 2009 16:26:32 -0500
Subject: [Coco] Technical question
In-Reply-To: <49B193AB.7000709@worldnet.att.net>
References: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
	<49B193AB.7000709@worldnet.att.net>
Message-ID: <00d401c99ea2$38da2200$aa8e6600$@rr.com>

Nope, that was the FIRST thing I tried. But thanks for the tip (in case I
had forgotten it.)

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Friday, March 06, 2009 4:21 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Technical question
> 
> Many if not most Coco3 problems can be "cured" by removing the GIME
> (large square chip) from its socket and re-seating it. It's an
> oxidation
> problem. Be careful, you will need something better than two small
> screwdrivers to do this without causing damage.
> 



From mechacoco at gmail.com  Fri Mar  6 16:29:13 2009
From: mechacoco at gmail.com (Darren A)
Date: Fri, 6 Mar 2009 14:29:13 -0700
Subject: [Coco] DriveWire
In-Reply-To: <49B19282.7080902@worldnet.att.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>
	<49B12C48.2030601@worldnet.att.net>
	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
	<49B19282.7080902@worldnet.att.net>
Message-ID: <5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>

On 3/6/09, Robert Gault wrote:
>
> Here is the ml code that moves the ROM. Any reason why this
> shouldn't work?
>
>   org $7000
> start orcc #$50
>   ldx #$3000    where the ROM was offset loaded
>   ldy #$c000
> a@ ldd ,x++
>   std ,y++
>   cmpx #$e000
>   blo a@
>   jmp $c002
>   end start
---

There is a problem with that routine.  The  CMPX #$e000  should be
CMPX #$5000  (or CMPY #$e000).

Darren


From da3m0n_slay3r at yahoo.com  Fri Mar  6 16:36:55 2009
From: da3m0n_slay3r at yahoo.com (Bill Barnes)
Date: Fri, 6 Mar 2009 13:36:55 -0800 (PST)
Subject: [Coco] POLL: multiple message problem
Message-ID: <170814.91133.qm@web31105.mail.mud.yahoo.com>


So we know it isn't directly from the list from header data, and also not everyone is being hit by multiples.


-Later!  ?-WB-??? -- BABIC Computer Consulting.

--- On Fri, 3/6/09, Jim Hickle <jlhickle at yahoo.com> wrote:

From: Jim Hickle <jlhickle at yahoo.com>
Subject: Re: [Coco] POLL: multiple message problem
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Date: Friday, March 6, 2009, 9:40 AM

Number of multiples varies, up to ten copies coming in to yahoo mail.
Sent headers from 6 copies of a message to Dennis. He confirmed
that they are not being sent from the list.

Copies arrive at different times.? I've got 14 messages in this thread in my inbox but the original message still has not arrived.

--- On Thu, 3/5/09, Bill Barnes <da3m0n_slay3r at yahoo.com> wrote:
From: Bill Barnes <da3m0n_slay3r at yahoo.com>
Subject: Re: [Coco] POLL: multiple message problem
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Date: Thursday, March 5, 2009, 2:40 PM

Ok, I think we shoulf figure out here, who all has the multiple-copies problem:
In doing so, can we identify our ISP and email service? ?With this data, we can
see what is affected, and to what extent. (is is just an ISP, is it a specific
email system? is it some link along the way?)I'll start.multiples problem:
YES? ? ? ? ? ? ? ? ? ? ISP: Cox? ? ?eMail System: Yahoonow just
need someone to keep track of it all, preferably someone who isn't caught in
a multiples problem, any volunteers? It would be good to know this as we all can
agree, it gets annoying and fills our inboxes way faster than normal, and needs
to be fixed. I wanna read about and contribute to the CoCo, NOT get bogged down
in multiples.
-Later!? -WB- ?? -- BABIC Computer Consulting.




? ? ? 

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



? ? ? 

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



      


From robert.gault at worldnet.att.net  Fri Mar  6 17:10:14 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Fri, 06 Mar 2009 17:10:14 -0500
Subject: [Coco] DriveWire
In-Reply-To: <5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>	<49B19282.7080902@worldnet.att.net>
	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>
Message-ID: <49B19F46.6090201@worldnet.att.net>

Darren A wrote:
> On 3/6/09, Robert Gault wrote:
>> Here is the ml code that moves the ROM. Any reason why this
>> shouldn't work?
>>
>>   org $7000
>> start orcc #$50
>>   ldx #$3000    where the ROM was offset loaded
>>   ldy #$c000
>> a@ ldd ,x++
>>   std ,y++
>>   cmpx #$e000
>>   blo a@
>>   jmp $c002
>>   end start
> ---
> 
> There is a problem with that routine.  The  CMPX #$e000  should be
> CMPX #$5000  (or CMPY #$e000).
> 
> Darren
> 

Duh, hits head, how obvious. Thanks Darren.

Now the ROM boots and runs. I can test or use it without burning an 
EPROM which means I can have both a hardware scsi system or a drivewire 
system without changing ROMs.


From tlindner at macmess.org  Fri Mar  6 17:25:44 2009
From: tlindner at macmess.org (tim lindner)
Date: Fri, 6 Mar 2009 14:25:44 -0800
Subject: [Coco] Technical question
In-Reply-To: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
References: <AcmekKI3Gh5OhqfBR9qkMIlveZKxOQ==>
	<00bd01c99e90$a4e107a0$eea316e0$@rr.com>
Message-ID: <5b0704c10903061425m7fec0febrda404da519e4ab43@mail.gmail.com>

On Fri, Mar 6, 2009 at 11:20 AM, Bill <cwgordon at carolina.rr.com> wrote:
> I was given a CoCo3, but it doesn't work. The MOTORON and MOTOROFF functions
> do not work. The RF to the TV is EXTREMELY snowy and full of static.
>
> Question #1-can all this be fixed?

Are you using a "Nintendo" style auto switching RF converter box? If
so then the snow is expected. Go find a manual (slide) switching RF
converter box and it will look better.

-- 
tim lindner
tlindner at macmess.org


From mdelyea at gmail.com  Fri Mar  6 17:40:41 2009
From: mdelyea at gmail.com (mike delyea)
Date: Fri, 6 Mar 2009 17:40:41 -0500
Subject: [Coco] Technical question
In-Reply-To: <5b0704c10903061425m7fec0febrda404da519e4ab43@mail.gmail.com>
References: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
	<5b0704c10903061425m7fec0febrda404da519e4ab43@mail.gmail.com>
Message-ID: <1b52e6c80903061440m5f4d9122i47808f5f4200e689@mail.gmail.com>

Isn't there an RCA to cable adapter that he could use?  I seem to
recall I did that with my coco 2.

On Fri, Mar 6, 2009 at 5:25 PM, tim lindner <tlindner at macmess.org> wrote:
> On Fri, Mar 6, 2009 at 11:20 AM, Bill <cwgordon at carolina.rr.com> wrote:
>> I was given a CoCo3, but it doesn't work. The MOTORON and MOTOROFF functions
>> do not work. The RF to the TV is EXTREMELY snowy and full of static.
>>
>> Question #1-can all this be fixed?
>
> Are you using a "Nintendo" style auto switching RF converter box? If
> so then the snow is expected. Go find a manual (slide) switching RF
> converter box and it will look better.
>
> --
> tim lindner
> tlindner at macmess.org
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From operator at coco3.com  Fri Mar  6 17:46:43 2009
From: operator at coco3.com (Roger Taylor)
Date: Fri, 06 Mar 2009 16:46:43 -0600
Subject: [Coco] new EPROM Paks
Message-ID: <20090306224722.AE05620A13@qs281.pair.com>


For anybody interested, the new high-quality 27-series EPROM Paks are 
now available for sale from the front page of coco3.com.  This is not 
a reused game pak or anything like that.  There's a jumper set on the 
board but I can also customize a pak for you by bringing out a toggle 
switch on the case for selecting the upper or lower 8K/16K.  The same 
goes for the new bluetooth RS-232 paks - custom situations are welcome.

Long Live the CoCo.
"the smoke blower"
-- 
Roger Taylor

http://www.wordofthedayonline.com



From cwgordon at carolina.rr.com  Fri Mar  6 17:55:59 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Fri, 6 Mar 2009 17:55:59 -0500
Subject: [Coco] Technical question
In-Reply-To: <5b0704c10903061425m7fec0febrda404da519e4ab43@mail.gmail.com>
References: <AcmekKI3Gh5OhqfBR9qkMIlveZKxOQ==>	<00bd01c99e90$a4e107a0$eea316e0$@rr.com>
	<5b0704c10903061425m7fec0febrda404da519e4ab43@mail.gmail.com>
Message-ID: <00e101c99eae$b82d89a0$28889ce0$@rr.com>

Nope, direct connect, I have an adapter that screws right into the coax
input

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of tim lindner
> Sent: Friday, March 06, 2009 5:26 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Technical question
> 
> Are you using a "Nintendo" style auto switching RF converter box? If
> so then the snow is expected. Go find a manual (slide) switching RF
> converter box and it will look better.
> 



From operator at coco3.com  Fri Mar  6 18:06:50 2009
From: operator at coco3.com (Roger Taylor)
Date: Fri, 06 Mar 2009 17:06:50 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <49B1707C.5000308@aurigae.demon.co.uk>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
	<20090305223830.7949020A14@qs281.pair.com>
	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
	<20090306025839.3A62020A13@qs281.pair.com>
	<C485B547-7A3E-415D-8173-779C96B3F6A2@tee-boy.com>
	<20090306051857.6554620A16@qs281.pair.com>
	<20090306061352.GN7702@warlock.deepthought.com>
	<7AC92BB6-6880-4274-B8EE-D92ED53304A0@tee-boy.com>
	<49B1707C.5000308@aurigae.demon.co.uk>
Message-ID: <20090306230730.2A19C20A14@qs281.pair.com>

At 12:50 PM 3/6/2009, you wrote:
>Boisy Pitre wrote:
>>I have some ideas about how this might be done.  Now that DriveWire 
>>3 is downloadable, it will be easy to update it for extensions to 
>>the protocol like printing.
>
>Something else I always meant to implement, was the ability to 
>stream a .cas file across drivewire to an intercepted cassette 
>routine, for those things that don't like being loaded from disk.



My cocotape.exe command will take any file stored on the PC and send 
it to the CoCo as a tape file stream over a regular tape cable.  I 
need to fix something that I missed and Gault noticed, and I'll try 
to come up with the C#, C++, Visual BASIC versions as well since it's 
now written in HLA.  Somebody else could port it I suppose.


-- 
Roger Taylor

http://www.wordofthedayonline.com



From devries.bob at gmail.com  Fri Mar  6 18:10:23 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Sat, 7 Mar 2009 09:10:23 +1000
Subject: [Coco] Technical question
References: <AcmekKI3Gh5OhqfBR9qkMIlveZKxOQ==>	<00bd01c99e90$a4e107a0$eea316e0$@rr.com><5b0704c10903061425m7fec0febrda404da519e4ab43@mail.gmail.com>
	<00e101c99eae$b82d89a0$28889ce0$@rr.com>
Message-ID: <009b01c99eb0$bce7a460$0701a8c0@master>

In my experience, sometimes the coax socket on the coco3 gets loose, and the 
wire from the tip to the modulator sub-board makes a bad connection, causing 
snow. This is of course the Aussie version of the coco, but I'm sure the USA 
version would be similar.

What I usually did was re-solder the centre contact wire, and then actually 
solder the body of the RCA socket to the frame of the modulator. It's a 
fiddly job, and may require removing the modulator from the motherboard.

Hehe, I could use a bit of snow right now; it's hot here. Thankfully I'm not 
in Victoria with the bushfire problem.
--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Bill" <cwgordon at carolina.rr.com>
To: "'CoCoList for Color Computer Enthusiasts'" <coco at maltedmedia.com>
Sent: Saturday, March 07, 2009 8:55 AM
Subject: Re: [Coco] Technical question


> Nope, direct connect, I have an adapter that screws right into the coax
> input
>
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of tim lindner
>> Sent: Friday, March 06, 2009 5:26 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] Technical question
>>
>> Are you using a "Nintendo" style auto switching RF converter box? If
>> so then the snow is expected. Go find a manual (slide) switching RF
>> converter box and it will look better.
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From operator at coco3.com  Fri Mar  6 18:15:56 2009
From: operator at coco3.com (Roger Taylor)
Date: Fri, 06 Mar 2009 17:15:56 -0600
Subject: [Coco] 16550 wasRe: RS232 paks
In-Reply-To: <20090306230730.2A19C20A14@qs281.pair.com>
References: <B2406CFE-06A1-47F2-84E2-7AE41E8C3F81@tee-boy.com>
	<20090305223830.7949020A14@qs281.pair.com>
	<6A67F631-3827-4E6E-9134-61297E190CCA@tee-boy.com>
	<20090306025839.3A62020A13@qs281.pair.com>
	<C485B547-7A3E-415D-8173-779C96B3F6A2@tee-boy.com>
	<20090306051857.6554620A16@qs281.pair.com>
	<20090306061352.GN7702@warlock.deepthought.com>
	<7AC92BB6-6880-4274-B8EE-D92ED53304A0@tee-boy.com>
	<49B1707C.5000308@aurigae.demon.co.uk>
	<20090306230730.2A19C20A14@qs281.pair.com>
Message-ID: <20090306231635.7F30F20A13@qs281.pair.com>

At 05:06 PM 3/6/2009, you wrote:
>At 12:50 PM 3/6/2009, you wrote:
>>Boisy Pitre wrote:
>>>I have some ideas about how this might be done.  Now that 
>>>DriveWire 3 is downloadable, it will be easy to update it for 
>>>extensions to the protocol like printing.
>>
>>Something else I always meant to implement, was the ability to 
>>stream a .cas file across drivewire to an intercepted cassette 
>>routine, for those things that don't like being loaded from disk.
>
>
>
>My cocotape.exe command will take any file stored on the PC and send 
>it to the CoCo as a tape file stream over a regular tape cable.  I 
>need to fix something that I missed and Gault noticed, and I'll try 
>to come up with the C#, C++, Visual BASIC versions as well since 
>it's now written in HLA.  Somebody else could port it I suppose.

Oops, let me correct my phrasing...  I will write the C#, C++, and 
Visual BASIC versions of cocotape.exe (or one of the 3).

-- 
Roger Taylor

http://www.wordofthedayonline.com



From ed.orbea at gmail.com  Fri Mar  6 18:59:41 2009
From: ed.orbea at gmail.com (Ed Orbea)
Date: Fri, 6 Mar 2009 15:59:41 -0800
Subject: [Coco] Drivewire 3.0
Message-ID: <9e22cc9d0903061559reda9f88ud05c6b8e3783299d@mail.gmail.com>

What is the "upgrade path" for those who already purchased and use Drivewire
2.0?

Thanks

Ed Orbea


From exwn8jef at gmail.com  Fri Mar  6 19:03:44 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Fri, 06 Mar 2009 19:03:44 -0500
Subject: [Coco] DriveWire 3
In-Reply-To: <49B16EEC.7040200@bjork-huffman.net>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>	<49B153BF.4000503@gmail.com>
	<49B16EEC.7040200@bjork-huffman.net>
Message-ID: <49B1B9E0.7000507@gmail.com>

Hi Steve,
I forgot to mention that my computer is a laptop. :(

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



Steve Bjork wrote:
> Or you can get a serial PCI card for $15.00 at newegg.com and that 
> comes with 2 ports.
> I found that the card solutions work better than most USB serial ports.
>
> Steve
>
> N8WQ wrote:
>> Can you or someone on the list recommend a good USB to Serial adapter?
>> Unfortunately, I don't have a serial connector. :(
>> Thanks...
>>
>> Alan Jones
>>
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From farna at att.net  Fri Mar  6 20:18:36 2009
From: farna at att.net (Frank Swygert)
Date: Fri, 06 Mar 2009 20:18:36 -0500
Subject: [Coco] Technical question
Message-ID: <49B1CB6C.3080006@att.net>

Sounds like the 6809 might be blown. Try the MOTORON/OFF commands without the cassette cable plugged in. The relay should click. If not, you've got problems! Hmmm... instead of 6809, look to the power supply first. D/L a copy of "Tandy's Little Wonder", there are instructions for testing the power supply with a multi-meter in there. 

I always used a 3' cable TV cable between the CoCo and TV, using the cable input. You can get an "F" to RCA connector from Radio Shack still. Use that on the CoCo end. The better shielded cable gets rid of most of the snow. Of course if the cable you have worked before, that points to a different problem. 

------------
Date: Fri, 6 Mar 2009 15:07:47 -0500
From: "Bill" <cwgordon at carolina.rr.com>

#1
The cable I am using is the one that has been working perfectly on the
Coco2, before it went "toes up"

#2
Tried all that. Changed channels, tried another cable, tried another TV in
another room. Still too snowy and too much static to see.

-- 
Frank Swygert
Publisher, "American Motors Cars" 
Magazine (AMC)
For all AMC enthusiasts
http://farna.home.att.net/AMC.html
(free download available!)



From gene.heskett at verizon.net  Fri Mar  6 20:45:00 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Fri, 06 Mar 2009 20:45:00 -0500
Subject: [Coco] DriveWire 3
In-Reply-To: <49B153BF.4000503@gmail.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
	<49B153BF.4000503@gmail.com>
Message-ID: <200903062045.00350.gene.heskett@verizon.net>

On Friday 06 March 2009, N8WQ wrote:
>Boisy,
>Can you or someone on the list recommend a good USB to Serial adapter?
>Unfortunately, I don't have a serial connector. :(
>Thanks...
>
>Alan Jones

The ones based on the Future Domain  Technology Inc chips are the most 
transparent.  pl2303 chips are buggy, randomly throwing away the first byte of 
a packet.  So look for the ones with FDTI as the chipset.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The more you sweat in peace, the less you bleed in war.



From gene.heskett at verizon.net  Fri Mar  6 20:50:55 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Fri, 06 Mar 2009 20:50:55 -0500
Subject: [Coco] Technical question
In-Reply-To: <49B193AB.7000709@worldnet.att.net>
References: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
	<49B193AB.7000709@worldnet.att.net>
Message-ID: <200903062050.55517.gene.heskett@verizon.net>

On Friday 06 March 2009, Robert Gault wrote:
>Bill wrote:
>> I was given a CoCo3, but it doesn't work. The MOTORON and MOTOROFF
>> functions do not work. The RF to the TV is EXTREMELY snowy and full of
>> static.
>>
>> Question #1-can all this be fixed?
>>
>> Question #2-can all this be fixed for a reasonable price?
>>
>> Question #3-is it worth it?
>>
>> ______________________________________
>
>Many if not most Coco3 problems can be "cured" by removing the GIME
>(large square chip) from its socket and re-seating it. It's an oxidation
>problem. Be careful, you will need something better than two small
>screwdrivers to do this without causing damage.
>
That gizmo is called a PLCC puller, and the shack used to have them for about 
a tenner.  Ingenious little mechanism too.

>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
In vino veritas.
	[In wine there is truth.]
		-- Pliny



From chawks at dls.net  Fri Mar  6 21:15:17 2009
From: chawks at dls.net (Christopher Hawks)
Date: Fri, 06 Mar 2009 20:15:17 -0600
Subject: [Coco] DriveWire 3
In-Reply-To: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
Message-ID: <49B1D8B5.7070004@dls.net>

Boisy Pitre said the following on 03/06/2009 09:54 AM:
> As the saying goes, the only way to fight fire is with fire.
> 
> So starting today, DriveWire 3 is now a free downloadable product from 
> Cloud-9.
> 
> You can go to our website at http://www.cloud9tech.com/ and click on the 
> DriveWire announcement on the main page.  It will take you to the 
> DriveWire 3 page, where you can now download DriveWire HDB-DOS ROMs for 
> the CoCo 2 and CoCo 3.  Of course, you will need to burn your own EPROM 
> in order to take advantage of these images.

     Well darn ... now I haveta get out of the line.

     And I was gonna take a poke at the guy behind me (Frank P).

8^)


-- 
Christopher R. Hawks
HAWKSoft
---------------------------------------------------------
C is quirky, flawed, and an enormous success
	-- Dennis M. Ritchie


From dml_68 at yahoo.com  Fri Mar  6 22:48:26 2009
From: dml_68 at yahoo.com (Derek)
Date: Fri, 6 Mar 2009 19:48:26 -0800 (PST)
Subject: [Coco] 1991 RBM Magazine Archive Now up
Message-ID: <112607.13607.qm@web30205.mail.mud.yahoo.com>

The complete year of 1991 rainbows are now up on my archive. Thanks to those who did all the hard work to scan these. As usual links can be found at the coco.com message forum here: 

http://www.coco3.com/modules.php?name=Forums&file=viewtopic&p=4179#4179




** Mistrust Authority. Promote Decentralization **


 


       


From tlindner at macmess.org  Fri Mar  6 23:01:50 2009
From: tlindner at macmess.org (tim lindner)
Date: Fri, 6 Mar 2009 20:01:50 -0800
Subject: [Coco] '68' Micro Journal
In-Reply-To: <49B02424.4080801@swbell.net>
Message-ID: <1iw6a1p.12sy61q1wbc5fsM%tlindner@macmess.org>

Joel Ewy <jcewy at swbell.net> wrote:

> Please let us know where and when.  I'm very interested in seeing them,
> and I'm sure others on this list will be as well.  I have a few issues
> of '68 Micro Journal and really enjoyed them.

I've seem to have lost my copy. Damn.

But, I found them on the Flex User's group ftp site.

Go here: http://www.flexusergroup.com/flexusergroup/fug1.htm and ask
nicely for access.

-- 
tim lindner
tlindner at macmess.org                                              Bright



From davehazelton at comcast.net  Fri Mar  6 23:13:46 2009
From: davehazelton at comcast.net (David Hazelton)
Date: Fri, 06 Mar 2009 23:13:46 -0500
Subject: [Coco] DriveWire
In-Reply-To: <49B19F46.6090201@worldnet.att.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>	<49B19282.7080902@worldnet.att.net>	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>
	<49B19F46.6090201@worldnet.att.net>
Message-ID: <49B1F47A.6050102@comcast.net>

Robert Gault wrote:
>
> Now the ROM boots and runs. I can test or use it without burning an 
> EPROM which means I can have both a hardware scsi system or a 
> drivewire system without changing ROMs.
>
> -- 
>
Robert,

Forgive my possible forgetfulness and my lack of understanding...But how 
do you use a physical system and a drivewire system together on a real 
Coco (and I guess on a Virtual Coco) ?  or Are you just loading the Rom 
code in two different locations and exec at the location the drivewire 
starts to go into drivewire mode. 

Sort of on the same note, if I load Nitros9 across drivewire can still 
access my physical Hard drive?


~David Hazelton




From boisy at tee-boy.com  Fri Mar  6 23:16:41 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 6 Mar 2009 22:16:41 -0600
Subject: [Coco] Drivewire 3.0
In-Reply-To: <9e22cc9d0903061559reda9f88ud05c6b8e3783299d@mail.gmail.com>
References: <9e22cc9d0903061559reda9f88ud05c6b8e3783299d@mail.gmail.com>
Message-ID: <6C1C2237-2E94-460D-A410-F14221E538E9@tee-boy.com>

Ed,

If you want to take advantage of the extra speed of DriveWire 3, you  
can download the new server and images.  I don't remember if you have  
a ROM or not.  Get with me in private email and we can discuss.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com

On Mar 6, 2009, at 5:59 PM, Ed Orbea wrote:

> What is the "upgrade path" for those who already purchased and use  
> Drivewire
> 2.0?
>
> Thanks
>
> Ed Orbea
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From robert.gault at worldnet.att.net  Fri Mar  6 23:36:05 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Fri, 06 Mar 2009 23:36:05 -0500
Subject: [Coco] DriveWire - test results using the now free code
In-Reply-To: <49B19F46.6090201@worldnet.att.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>	<49B19282.7080902@worldnet.att.net>	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>
	<49B19F46.6090201@worldnet.att.net>
Message-ID: <49B1F9B5.9070707@worldnet.att.net>

Here are some results of testing DriveWire3 on a Coco3 without burning 
an EPROM. Since I already have a SCSI system, I put the ROM image on my 
hard drive in LOADM format. The preamble loads the ROM at $3000. There 
is also a short binary to move the ROM to $C000-$DFFF, overwriting my 
SCSI DOS with HDBDOS for DriveWire3.

I was able to read any Basic .dsk image on my PC from my Coco. Initially 
I was not able to read any of the virtual Disk Basic disks on a .vhd 
image, although part of the OS-9 section was displayed.

Normal RGBDOS or HDBDOS contains an offset in ROM to indicate the start 
of the Basic partition of a hard drive. This offset is at $D938-$D93A. 
Looking at the DriveWire3 ROM at this location found that the offset is 
set to $000000. That make complete sense when trying to read a floppy or 
a hard drive which has no OS-9 partition.
OK, so after booting DriveWire3, I POKEd the value $5A000 into the ROM 
offset location. This value is the default for most .vhd drives that 
have an OS-9 partition and it is the default offset value in RGBDOS for 
Coco emulators.
Now after mounting a .vhd image in the DriveWire3 Win server, I was able 
to read the Basic drives on the PC from my Coco. The system behaved 
exactly like running RGBDOS in VCC or MESS.

As soon as Boisy posts the NitrOS-9 boot disk for DriveWire3, I expect 
it to work just as well as the above. I should be able to put the boot 
disk on my Coco hard drive system, and boot into NitrOS-9 on a .vhd 
drive on the PC.
Probably I will also be able to put the boot disk on a Basic drive of 
the .vhd image and after starting HDBDOS as above, boot NitrOS-9 on the 
PC without having any OS-9 code at the Coco end.


From robert.gault at worldnet.att.net  Fri Mar  6 23:53:05 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Fri, 06 Mar 2009 23:53:05 -0500
Subject: [Coco] DriveWire
In-Reply-To: <49B1F47A.6050102@comcast.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>	<49B19282.7080902@worldnet.att.net>	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>	<49B19F46.6090201@worldnet.att.net>
	<49B1F47A.6050102@comcast.net>
Message-ID: <49B1FDB1.60205@worldnet.att.net>

David Hazelton wrote:
> Robert Gault wrote:
>>
>> Now the ROM boots and runs. I can test or use it without burning an 
>> EPROM which means I can have both a hardware scsi system or a 
>> drivewire system without changing ROMs.
>>
>> -- 
>>
> Robert,
> 
> Forgive my possible forgetfulness and my lack of understanding...But how 
> do you use a physical system and a drivewire system together on a real 
> Coco (and I guess on a Virtual Coco) ?  or Are you just loading the Rom 
> code in two different locations and exec at the location the drivewire 
> starts to go into drivewire mode.
> Sort of on the same note, if I load Nitros9 across drivewire can still 
> access my physical Hard drive?
> 
> 
> ~David Hazelton
> 

Well you can't do both simultaneously. That is you can access either the 
PC hard drive or the Coco hard drive. However, as I am able to use 
HDBDOS for DriveWire3 without burning an EPROM, it is trivial to run 
either RGBDOS with a KEN-TON scsi interface or DriveWire3 and a .vhd 
virtual hard drive.

There is a separate posting of my test results that has more details.


From cwgordon at carolina.rr.com  Sat Mar  7 00:24:32 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sat, 7 Mar 2009 00:24:32 -0500
Subject: [Coco] Socketed chips for a 26-3127B Coco
Message-ID: <010201c99ee4$ff31b6b0$fd952410$@rr.com>

Does anyone have the SN74LS785N and the XC80652P (58C8444) chips they could
spare? I'd like to see if I could fix this little 36127B machine.

Thanks...

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784





From cwgordon at carolina.rr.com  Sat Mar  7 00:37:08 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sat, 7 Mar 2009 00:37:08 -0500
Subject: [Coco] Socketed chips for a 26-3127B Coco
In-Reply-To: <010201c99ee4$ff31b6b0$fd952410$@rr.com>
References: <010201c99ee4$ff31b6b0$fd952410$@rr.com>
Message-ID: <010401c99ee6$c202a630$4607f290$@rr.com>

OOPS!! Sorry, 26-3127B machine

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Bill
> Sent: Saturday, March 07, 2009 12:25 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: [Coco] Socketed chips for a 26-3127B Coco
> 
> Does anyone have the SN74LS785N and the XC80652P (58C8444) chips they
> could
> spare? I'd like to see if I could fix this little 36127B machine.
> 
> Thanks...
> 
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
> 
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
> 
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
> 
> 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From goosey at virgo.sdc.org  Sat Mar  7 00:52:53 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Fri, 6 Mar 2009 22:52:53 -0700
Subject: [Coco] Technical question
In-Reply-To: <00e101c99eae$b82d89a0$28889ce0$@rr.com>
References: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
	<5b0704c10903061425m7fec0febrda404da519e4ab43@mail.gmail.com>
	<00e101c99eae$b82d89a0$28889ce0$@rr.com>
Message-ID: <20090307055253.GA27341@virgo.sdc.org>

On Fri, Mar 06, 2009 at 05:55:59PM -0500, Bill wrote:
> Nope, direct connect, I have an adapter that screws right into the coax
> input

Darn!  I was going to recommend trying that, as that's how I got best
results with a TV. :-)

You mentioned dvds... Is there a composite video link there you could
use (say, from a dvd player to a cable box), or composite in on a vcr
or something similar?

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From lamune at doki-doki.net  Sat Mar  7 01:49:49 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Fri, 6 Mar 2009 22:49:49 -0800
Subject: [Coco] Technical question
In-Reply-To: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
References: <00bd01c99e90$a4e107a0$eea316e0$@rr.com>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D39@fenestra.lamunet.local>

Bill, I'm thinking power supply issue. The CoCo3 video modulator needs
8V and there's a little 78L08 (IC36) that provides it. If I had it here
I'd throw it on a scope and see what that looks like. The cassette relay
is fed off the same chip (SC77527) that runs the voltage regulator, so
again, smells like a power supply problem to me.


> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Bill
> Sent: Friday, March 06, 2009 11:21 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: [Coco] Technical question
> 
> I was given a CoCo3, but it doesn't work. The MOTORON and MOTOROFF
> functions
> do not work. The RF to the TV is EXTREMELY snowy and full of static.
> 
> Question #1-can all this be fixed?
> 
> Question #2-can all this be fixed for a reasonable price?
> 
> Question #3-is it worth it?
> 
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
> 
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
> 
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
> 
> 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From boisy at tee-boy.com  Sat Mar  7 07:45:57 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Sat, 7 Mar 2009 06:45:57 -0600
Subject: [Coco] DriveWire - test results using the now free code
In-Reply-To: <49B1F9B5.9070707@worldnet.att.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>	<49B19282.7080902@worldnet.att.net>	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>
	<49B19F46.6090201@worldnet.att.net>
	<49B1F9B5.9070707@worldnet.att.net>
Message-ID: <4E30BB47-2793-4C87-9C4D-3C425EC546FF@tee-boy.com>

Robert,

The NitrOS-9/6809 Level 2 image is up and available for download.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com

On Mar 6, 2009, at 10:36 PM, Robert Gault wrote:

> Here are some results of testing DriveWire3 on a Coco3 without  
> burning an EPROM. Since I already have a SCSI system, I put the ROM  
> image on my hard drive in LOADM format. The preamble loads the ROM  
> at $3000. There is also a short binary to move the ROM to $C000- 
> $DFFF, overwriting my SCSI DOS with HDBDOS for DriveWire3.
>
> I was able to read any Basic .dsk image on my PC from my Coco.  
> Initially I was not able to read any of the virtual Disk Basic disks  
> on a .vhd image, although part of the OS-9 section was displayed.
>
> Normal RGBDOS or HDBDOS contains an offset in ROM to indicate the  
> start of the Basic partition of a hard drive. This offset is at  
> $D938-$D93A. Looking at the DriveWire3 ROM at this location found  
> that the offset is set to $000000. That make complete sense when  
> trying to read a floppy or a hard drive which has no OS-9 partition.
> OK, so after booting DriveWire3, I POKEd the value $5A000 into the  
> ROM offset location. This value is the default for most .vhd drives  
> that have an OS-9 partition and it is the default offset value in  
> RGBDOS for Coco emulators.
> Now after mounting a .vhd image in the DriveWire3 Win server, I was  
> able to read the Basic drives on the PC from my Coco. The system  
> behaved exactly like running RGBDOS in VCC or MESS.
>
> As soon as Boisy posts the NitrOS-9 boot disk for DriveWire3, I  
> expect it to work just as well as the above. I should be able to put  
> the boot disk on my Coco hard drive system, and boot into NitrOS-9  
> on a .vhd drive on the PC.
> Probably I will also be able to put the boot disk on a Basic drive  
> of the .vhd image and after starting HDBDOS as above, boot NitrOS-9  
> on the PC without having any OS-9 code at the Coco end.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From snhirsch at gmail.com  Sat Mar  7 08:50:44 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Sat, 7 Mar 2009 08:50:44 -0500 (EST)
Subject: [Coco] DriveWire
In-Reply-To: <49B1FDB1.60205@worldnet.att.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>
	<49B12C48.2030601@worldnet.att.net>
	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
	<49B19282.7080902@worldnet.att.net>
	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>
	<49B19F46.6090201@worldnet.att.net> <49B1F47A.6050102@comcast.net>
	<49B1FDB1.60205@worldnet.att.net>
Message-ID: <alpine.DEB.2.00.0903070849360.32155@duo>

On Fri, 6 Mar 2009, Robert Gault wrote:

>> Forgive my possible forgetfulness and my lack of understanding...But how do 
>> you use a physical system and a drivewire system together on a real Coco

> Well you can't do both simultaneously. That is you can access either the PC 
> hard drive or the Coco hard drive.

?? Why not?  I use DriveWire on my CoCo 3 alongside an IDE hard disk and a 
floppy.  This is under OS-9.


-- 


From robert.gault at worldnet.att.net  Sat Mar  7 09:21:41 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Sat, 07 Mar 2009 09:21:41 -0500
Subject: [Coco] DriveWire - test results using the now free code
In-Reply-To: <4E30BB47-2793-4C87-9C4D-3C425EC546FF@tee-boy.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>	<49B19282.7080902@worldnet.att.net>	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>	<49B19F46.6090201@worldnet.att.net>	<49B1F9B5.9070707@worldnet.att.net>
	<4E30BB47-2793-4C87-9C4D-3C425EC546FF@tee-boy.com>
Message-ID: <49B282F5.6060509@worldnet.att.net>

Boisy Pitre wrote:
> Robert,
> 
> The NitrOS-9/6809 Level 2 image is up and available for download.
> 
> Regards,
> Boisy G. Pitre

I had intended to wait until the 6309 version and perhaps the LevelI 
versions were posted before reporting, however ....

Just tried the 6809 version which worked using my current arraignment of 
starting the Coco DriveWire from disk rather than an EPROM. There are 
several things to be aware of as a user running NitrOS-9 in this manner.

The default NitrOS-9 DriveWire version must be mounted in Winserver slot 
#0 to boot. If you enter DRIVE#1:DOS with the boot disk mounted in 
Winserver slot#1 you will see the kernel and os9boot files load, but the 
boot process will fail. That would be of concern only if you wanted a 
.vhd image in Winserver slot#0. It looks like the driver may be 
defaulting to the equivalent of a scsi channel 0. Perhaps that is 
adjustable in the /DD descriptor.

There are four new descriptors in the OS-9 version of DriveWire, /DD and 
/X1-/X3. Each of these descriptors is set for a 32,768 sector, $400 
track, 1 side, $20 sector per track .os9 image as reported by dmode and 
free. That is very different from the standard .vhd image of $5A000 
sectors with $5A tracks, $40 sides, and $40 sectors per track.
I was able to mount my .vhd image in Winserver as drive #1 and read the 
OS-9 section correctly without changing the /X1 descriptor. However, if 
I were going to use the .vhd image via DriveWire it would be much safer 
to change the descriptor to match the .vhd image.

I have not yet tried to create my own DriveWire NitrOS-9 boot disk 
residing on a .vhd image in the Basic partition.


From robert.gault at worldnet.att.net  Sat Mar  7 09:38:19 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Sat, 07 Mar 2009 09:38:19 -0500
Subject: [Coco] DriveWire
In-Reply-To: <alpine.DEB.2.00.0903070849360.32155@duo>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>	<49B19282.7080902@worldnet.att.net>	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>	<49B19F46.6090201@worldnet.att.net>
	<49B1F47A.6050102@comcast.net>	<49B1FDB1.60205@worldnet.att.net>
	<alpine.DEB.2.00.0903070849360.32155@duo>
Message-ID: <49B286DB.2010609@worldnet.att.net>

Steven Hirsch wrote:
> On Fri, 6 Mar 2009, Robert Gault wrote:
> 
>>> Forgive my possible forgetfulness and my lack of understanding...But 
>>> how do you use a physical system and a drivewire system together on a 
>>> real Coco
> 
>> Well you can't do both simultaneously. That is you can access either 
>> the PC hard drive or the Coco hard drive.
> 
> ?? Why not?  I use DriveWire on my CoCo 3 alongside an IDE hard disk and 
> a floppy.  This is under OS-9.
> 
> 

Your comparing apples and oranges. Boisy might explain this better but 
here goes.

Under OS-9, there should be two drivers on the boot disk one for the IDE 
and one for DriveWire. That means when you try to access your Coco IDE 
drive, the signal flows through an interface/controller in your MPI. 
When you try to access your PC, the signal flows through the bit-banger 
port via DriveWire.
Under Disk Basic HDBDOS, there is not room in ROM for more than one 
driver. It will be one of the following, scsi, ide, or DriveWire. (Boisy 
may have found a way to fit both scsi and ide.) So there is no way to 
access both a ide hard drive and a PC .vhd drive from a single ROM image 
under Disk Basic. You can access the floppies on the Coco while HDBDOS 
accesses the  PC for drives 4 and up but that is a different issue.


From boisy at tee-boy.com  Sat Mar  7 09:53:17 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Sat, 7 Mar 2009 08:53:17 -0600
Subject: [Coco] DriveWire
In-Reply-To: <49B286DB.2010609@worldnet.att.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>	<49B19282.7080902@worldnet.att.net>	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>	<49B19F46.6090201@worldnet.att.net>
	<49B1F47A.6050102@comcast.net>	<49B1FDB1.60205@worldnet.att.net>
	<alpine.DEB.2.00.0903070849360.32155@duo>
	<49B286DB.2010609@worldnet.att.net>
Message-ID: <E932FA08-3E53-49FC-8534-17E912E8501C@tee-boy.com>

On Mar 7, 2009, at 8:38 AM, Robert Gault wrote:

> Steven Hirsch wrote:
>> On Fri, 6 Mar 2009, Robert Gault wrote:
>>>> Forgive my possible forgetfulness and my lack of  
>>>> understanding...But how do you use a physical system and a  
>>>> drivewire system together on a real Coco
>>> Well you can't do both simultaneously. That is you can access  
>>> either the PC hard drive or the Coco hard drive.
>> ?? Why not?  I use DriveWire on my CoCo 3 alongside an IDE hard  
>> disk and a floppy.  This is under OS-9.
>
> Your comparing apples and oranges. Boisy might explain this better  
> but here goes.
>
> Under OS-9, there should be two drivers on the boot disk one for the  
> IDE and one for DriveWire. That means when you try to access your  
> Coco IDE drive, the signal flows through an interface/controller in  
> your MPI. When you try to access your PC, the signal flows through  
> the bit-banger port via DriveWire.
> Under Disk Basic HDBDOS, there is not room in ROM for more than one  
> driver. It will be one of the following, scsi, ide, or DriveWire.  
> (Boisy may have found a way to fit both scsi and ide.) So there is  
> no way to access both a ide hard drive and a PC .vhd drive from a  
> single ROM image under Disk Basic. You can access the floppies on  
> the Coco while HDBDOS accesses the  PC for drives 4 and up but that  
> is a different issue.


Right.  Just to clarify Steve, you can do this under NitrOS-9 because  
of the extensible nature of the OS and its access to memory  
resources.  On the Disk BASIC side, under HDB-DOS, it's:

	FLOPPY AND (IDE OR SCSI OR DriveWire)

Someone (Frank?) posted the other day a wishlist, one item being using  
all these devices under HDB-DOS at once.  It cannot be done under the  
current ROM size limitations that we have to work with, or without  
expanding the syntax of the existing HDB-DOS commands.

Burke & Burke's Hyper-IO was the closest I've ever seen to a Disk  
BASIC environment having access to different types of devices like  
OS-9 gives you.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From snhirsch at gmail.com  Sat Mar  7 11:09:30 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Sat, 7 Mar 2009 11:09:30 -0500 (EST)
Subject: [Coco] DriveWire
In-Reply-To: <E932FA08-3E53-49FC-8534-17E912E8501C@tee-boy.com>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>
	<49B12C48.2030601@worldnet.att.net>
	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
	<49B19282.7080902@worldnet.att.net>
	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>
	<49B19F46.6090201@worldnet.att.net> <49B1F47A.6050102@comcast.net>
	<49B1FDB1.60205@worldnet.att.net>
	<alpine.DEB.2.00.0903070849360.32155@duo>
	<49B286DB.2010609@worldnet.att.net>
	<E932FA08-3E53-49FC-8534-17E912E8501C@tee-boy.com>
Message-ID: <alpine.DEB.2.00.0903071108490.32155@duo>

On Sat, 7 Mar 2009, Boisy Pitre wrote:

> On Mar 7, 2009, at 8:38 AM, Robert Gault wrote:
>
>>> ?? Why not?  I use DriveWire on my CoCo 3 alongside an IDE hard disk and a 
>>> floppy.  This is under OS-9.
>> 
>> Your comparing apples and oranges. Boisy might explain this better but here 
>> goes.
>> 
>> Under OS-9, there should be two drivers on the boot disk one for the IDE 
>> and one for DriveWire. That means when you try to access your Coco IDE 
>> drive, the signal flows through an interface/controller in your MPI. When 
>> you try to access your PC, the signal flows through the bit-banger port via 
>> DriveWire.
>> Under Disk Basic HDBDOS, there is not room in ROM for more than one driver. 
>> It will be one of the following, scsi, ide, or DriveWire. (Boisy may have 
>> found a way to fit both scsi and ide.) So there is no way to access both a 
>> ide hard drive and a PC .vhd drive from a single ROM image under Disk 
>> Basic. You can access the floppies on the Coco while HDBDOS accesses the 
>> PC for drives 4 and up but that is a different issue.
>
>
> Right.  Just to clarify Steve, you can do this under NitrOS-9 because of the 
> extensible nature of the OS and its access to memory resources.  On the Disk 
> BASIC side, under HDB-DOS, it's:
>
> 	FLOPPY AND (IDE OR SCSI OR DriveWire)
>
> Someone (Frank?) posted the other day a wishlist, one item being using all 
> these devices under HDB-DOS at once.  It cannot be done under the current ROM 
> size limitations that we have to work with, or without expanding the syntax 
> of the existing HDB-DOS commands.

Ok, missed that qualifier.  I know almost nothing about HDBDOS and rarely 
use it.


-- 


From snhirsch at gmail.com  Sat Mar  7 11:10:57 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Sat, 7 Mar 2009 11:10:57 -0500 (EST)
Subject: [Coco] DriveWire - test results using the now free code
In-Reply-To: <49B282F5.6060509@worldnet.att.net>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>
	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>
	<49B07583.2010308@gmail.com>
	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>
	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>
	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>
	<49B12C48.2030601@worldnet.att.net>
	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
	<49B19282.7080902@worldnet.att.net>
	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>
	<49B19F46.6090201@worldnet.att.net>
	<49B1F9B5.9070707@worldnet.att.net>
	<4E30BB47-2793-4C87-9C4D-3C425EC546FF@tee-boy.com>
	<49B282F5.6060509@worldnet.att.net>
Message-ID: <alpine.DEB.2.00.0903071110290.32155@duo>

On Sat, 7 Mar 2009, Robert Gault wrote:

> There are four new descriptors in the OS-9 version of DriveWire, /DD and 
> /X1-/X3. Each of these descriptors is set for a 32,768 sector, $400 track, 1 
> side, $20 sector per track .os9 image as reported by dmode and free. That is 
> very different from the standard .vhd image of $5A000 sectors with $5A 
> tracks, $40 sides, and $40 sectors per track.
> I was able to mount my .vhd image in Winserver as drive #1 and read the OS-9 
> section correctly without changing the /X1 descriptor. However, if I were 
> going to use the .vhd image via DriveWire it would be much safer to change 
> the descriptor to match the .vhd image.

Any possibility of a quick tutorial on patching media descriptors?


-- 


From exwn8jef at gmail.com  Sat Mar  7 11:12:04 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Sat, 07 Mar 2009 11:12:04 -0500
Subject: [Coco] Model No. 26-3127B motherboard
In-Reply-To: <010401c99ee6$c202a630$4607f290$@rr.com>
References: <010201c99ee4$ff31b6b0$fd952410$@rr.com>
	<010401c99ee6$c202a630$4607f290$@rr.com>
Message-ID: <49B29CD4.1040002@gmail.com>

Folks,
Today I took apart a 26-3127B for the first time.
I have a couple of questions that need answered.
If you have time go to http://exwn8jef.googlepages.com/cocoprojects
and see if you can help me out.

Also does anyone have a scanned copy of 26-3127B service manual?

Thanks and have a great day.

Alan

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home




From lamune at doki-doki.net  Sat Mar  7 11:52:10 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Sat, 7 Mar 2009 08:52:10 -0800
Subject: [Coco] Model No. 26-3127B motherboard
In-Reply-To: <49B29CD4.1040002@gmail.com>
References: <010201c99ee4$ff31b6b0$fd952410$@rr.com><010401c99ee6$c202a630$4607f290$@rr.com>
	<49B29CD4.1040002@gmail.com>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3A@fenestra.lamunet.local>

Alan:

1: That's a 64K memory expansion card.

2: a pair of 16kx4 chips (41416 or similar) are what go in the now empty
sockets

3: the 64k/128k jumpers refer to the ROM size. 64 kilobit (8k x 8) for
standard color basic, 128 kilobit (16k x 8) for extended basic



> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of N8WQ
> Sent: Saturday, March 07, 2009 8:12 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: [Coco] Model No. 26-3127B motherboard
> 
> Folks,
> Today I took apart a 26-3127B for the first time.
> I have a couple of questions that need answered.
> If you have time go to http://exwn8jef.googlepages.com/cocoprojects
> and see if you can help me out.
> 
> Also does anyone have a scanned copy of 26-3127B service manual?
> 
> Thanks and have a great day.
> 
> Alan
> 
> --
> N8WQ - Canal Winchester, Ohio
> http://exwn8jef.googlepages.com/home
> 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From jcewy at swbell.net  Sat Mar  7 13:10:14 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Sat, 07 Mar 2009 12:10:14 -0600
Subject: [Coco] DriveWire 3
In-Reply-To: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
Message-ID: <49B2B886.6050804@swbell.net>

Boisy,

First of all, thank you for this generous gift to the CoCo community.  
May it drive the sale of many cables and ROM cartridges.  In any case, 
it should help many existing users to stay in the CoCo game, and aid 
potential new and returning CoCo users in getting started, which can't 
be anything but good for all CoCo users and vendors.  We all benefit 
when more people use the CoCo.

Last night I made up a cable, burned DW3 into a 2764, and popped it into 
an old Disto Super Controller.  Works like a champ.  I'm using the 
Windows server for now, but will try out the Linux server and probably 
also the MacOS one eventually.

A couple questions:

1.  It appears to me that the only way to transfer files between server 
disk images in HDB-DOS is through real floppy disks on the CoCo.  E.g.  
I want to make a disk image for games and one for image files, etc.  I 
have individual disk image files on the server.  I can select said files 
with "drive#[0-3]".  I can automagically expand these disk image files 
by writing to a virtual drive number >0.  But once I've issued the 
"drive#" command, the virtual disks in the other image files on the 
server are inaccessible.  I could do a "drive#0", then "drive off 1" and 
copy data to a real floppy disk, assuming I have a floppy drive hooked 
up as drive 1.   Then I could do a "drive#1" command and "drive off 1" 
again, and then copy the data from the real floppy to a virtual disk on 
a different image file on the server.

Am I right in thinking that's the only way to do what I'm trying to do 
in HDB-DOS, or am I missing something?  It would be really cool to be 
able to do something like:  "backup 254#0 to 5#3" or "copy 
"hicolor.bin:254#0" to 5#3".

Just for fun I tried loading a ramdisk program that installed itself as 
drives 2 and 3.  I wanted to try using that as an intermediate location 
for moving files between disk images.  As I expected it stomped on 
DriveWire.  I haven't tried all of the ramdisk programs I have, but I 
suspect the result will be the same.

2.  Some concern has been expressed that since the CoCo 3 version of DW3 
runs the CoCo in high-speed mode, some auto-running games might be 
unplayably fast.  Would a potential solution to this simply be to use 
the CoCo 2 version and set the server accordingly?  (With the obvious 
caveat that it would only run at 56k...)

Thanks again for making this available.

JCE



Boisy Pitre wrote:
> As the saying goes, the only way to fight fire is with fire.
>
> So starting today, DriveWire 3 is now a free downloadable product from 
> Cloud-9.
>
> You can go to our website at http://www.cloud9tech.com/ and click on 
> the DriveWire announcement on the main page.  It will take you to the 
> DriveWire 3 page, where you can now download DriveWire HDB-DOS ROMs 
> for the CoCo 2 and CoCo 3.  Of course, you will need to burn your own 
> EPROM in order to take advantage of these images.
>
> For those of you who don't have an EPROM burner or cable, we've 
> dropped the price of our HDB-DOS ROM Pak to $20, and are still making 
> cables available for $10.
>
> The server software for Windows and Mac will go up sometime today.  
> The Linux server on SourceForge has been updated to handle the new 
> protocol features.
>
> Documentation and NitrOS-9 images will be go up this weekend.
>
> Regards,
> Boisy G. Pitre
> -- 
> Tee-Boy
> Mobile: 337.781.3570
> Email: boisy at tee-boy.com
> Web: http://www.tee-boy.com
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



From afra at aurigae.demon.co.uk  Sat Mar  7 13:27:57 2009
From: afra at aurigae.demon.co.uk (Phill Harvey-Smith)
Date: Sat, 07 Mar 2009 18:27:57 +0000
Subject: [Coco] Model No. 26-3127B motherboard
In-Reply-To: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3A@fenestra.lamunet.local>
References: <010201c99ee4$ff31b6b0$fd952410$@rr.com><010401c99ee6$c202a630$4607f290$@rr.com>	<49B29CD4.1040002@gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3A@fenestra.lamunet.local>
Message-ID: <49B2BCAD.5080201@aurigae.demon.co.uk>

Mike Pepe wrote:
> Alan:
> 2: a pair of 16kx4 chips (41416 or similar) are what go in the now empty
> sockets

I believe that you can also use a pair of 41464 64kx4 chips also, for 
64K, as I have done in one of my CoCo2s.

Cheers.

Phill.

-- 
Phill Harvey-Smith, Programmer, Hardware hacker, and general eccentric !

"You can twist perceptions, but reality won't budge" -- Rush.


From fwp at deepthought.com  Sat Mar  7 14:13:44 2009
From: fwp at deepthought.com (Frank Pittel)
Date: Sat, 7 Mar 2009 13:13:44 -0600
Subject: [Coco] DriveWire 3
In-Reply-To: <49B2B886.6050804@swbell.net>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
	<49B2B886.6050804@swbell.net>
Message-ID: <20090307191344.GP7702@warlock.deepthought.com>

Joel,

I've run into that interesting limitation of drivewire and get around
it by not using virtual disks 0-3. That way I don't collide with the
floppy drives. This does waste a bit of space on the drivewire server
but hard disks for a pc are so cheap and large that it doesn't matter.

Frank


On Sat, Mar 07, 2009 at 12:10:14PM -0600, Joel Ewy wrote:
> Boisy,
>
> First of all, thank you for this generous gift to the CoCo community.   
> May it drive the sale of many cables and ROM cartridges.  In any case,  
> it should help many existing users to stay in the CoCo game, and aid  
> potential new and returning CoCo users in getting started, which can't  
> be anything but good for all CoCo users and vendors.  We all benefit  
> when more people use the CoCo.
>
> Last night I made up a cable, burned DW3 into a 2764, and popped it into  
> an old Disto Super Controller.  Works like a champ.  I'm using the  
> Windows server for now, but will try out the Linux server and probably  
> also the MacOS one eventually.
>
> A couple questions:
>
> 1.  It appears to me that the only way to transfer files between server  
> disk images in HDB-DOS is through real floppy disks on the CoCo.  E.g.   
> I want to make a disk image for games and one for image files, etc.  I  
> have individual disk image files on the server.  I can select said files  
> with "drive#[0-3]".  I can automagically expand these disk image files  
> by writing to a virtual drive number >0.  But once I've issued the  
> "drive#" command, the virtual disks in the other image files on the  
> server are inaccessible.  I could do a "drive#0", then "drive off 1" and  
> copy data to a real floppy disk, assuming I have a floppy drive hooked  
> up as drive 1.   Then I could do a "drive#1" command and "drive off 1"  
> again, and then copy the data from the real floppy to a virtual disk on  
> a different image file on the server.
>
> Am I right in thinking that's the only way to do what I'm trying to do  
> in HDB-DOS, or am I missing something?  It would be really cool to be  
> able to do something like:  "backup 254#0 to 5#3" or "copy  
> "hicolor.bin:254#0" to 5#3".
>
> Just for fun I tried loading a ramdisk program that installed itself as  
> drives 2 and 3.  I wanted to try using that as an intermediate location  
> for moving files between disk images.  As I expected it stomped on  
> DriveWire.  I haven't tried all of the ramdisk programs I have, but I  
> suspect the result will be the same.
>
> 2.  Some concern has been expressed that since the CoCo 3 version of DW3  
> runs the CoCo in high-speed mode, some auto-running games might be  
> unplayably fast.  Would a potential solution to this simply be to use  
> the CoCo 2 version and set the server accordingly?  (With the obvious  
> caveat that it would only run at 56k...)
>
> Thanks again for making this available.
>
> JCE
>
>
>
> Boisy Pitre wrote:
>> As the saying goes, the only way to fight fire is with fire.
>>
>> So starting today, DriveWire 3 is now a free downloadable product from  
>> Cloud-9.
>>
>> You can go to our website at http://www.cloud9tech.com/ and click on  
>> the DriveWire announcement on the main page.  It will take you to the  
>> DriveWire 3 page, where you can now download DriveWire HDB-DOS ROMs  
>> for the CoCo 2 and CoCo 3.  Of course, you will need to burn your own  
>> EPROM in order to take advantage of these images.
>>
>> For those of you who don't have an EPROM burner or cable, we've  
>> dropped the price of our HDB-DOS ROM Pak to $20, and are still making  
>> cables available for $10.
>>
>> The server software for Windows and Mac will go up sometime today.   
>> The Linux server on SourceForge has been updated to handle the new  
>> protocol features.
>>
>> Documentation and NitrOS-9 images will be go up this weekend.
>>
>> Regards,
>> Boisy G. Pitre
>> -- 
>> Tee-Boy
>> Mobile: 337.781.3570
>> Email: boisy at tee-boy.com
>> Web: http://www.tee-boy.com
>>
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


From exwn8jef at gmail.com  Sat Mar  7 13:36:39 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Sat, 07 Mar 2009 13:36:39 -0500
Subject: [Coco] Model No. 26-3127B motherboard
In-Reply-To: <49B2BCAD.5080201@aurigae.demon.co.uk>
References: <010201c99ee4$ff31b6b0$fd952410$@rr.com><010401c99ee6$c202a630$4607f290$@rr.com>	<49B29CD4.1040002@gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3A@fenestra.lamunet.local>
	<49B2BCAD.5080201@aurigae.demon.co.uk>
Message-ID: <49B2BEB7.2080209@gmail.com>

Phil,
Thanks for the info!

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



Phill Harvey-Smith wrote:
> Mike Pepe wrote:
>> Alan:
>> 2: a pair of 16kx4 chips (41416 or similar) are what go in the now empty
>> sockets
>
> I believe that you can also use a pair of 41464 64kx4 chips also, for 
> 64K, as I have done in one of my CoCo2s.
>
> Cheers.
>
> Phill.
>


From fwp at deepthought.com  Sat Mar  7 14:26:11 2009
From: fwp at deepthought.com (Frank Pittel)
Date: Sat, 7 Mar 2009 13:26:11 -0600
Subject: [Coco] DriveWire
In-Reply-To: <E932FA08-3E53-49FC-8534-17E912E8501C@tee-boy.com>
References: <49B12C48.2030601@worldnet.att.net>
	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>
	<49B19282.7080902@worldnet.att.net>
	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>
	<49B19F46.6090201@worldnet.att.net> <49B1F47A.6050102@comcast.net>
	<49B1FDB1.60205@worldnet.att.net>
	<alpine.DEB.2.00.0903070849360.32155@duo>
	<49B286DB.2010609@worldnet.att.net>
	<E932FA08-3E53-49FC-8534-17E912E8501C@tee-boy.com>
Message-ID: <20090307192611.GQ7702@warlock.deepthought.com>

On Sat, Mar 07, 2009 at 08:53:17AM -0600, Boisy Pitre wrote:
> On Mar 7, 2009, at 8:38 AM, Robert Gault wrote:
>
>> Steven Hirsch wrote:
>>> On Fri, 6 Mar 2009, Robert Gault wrote:
>>>>> Forgive my possible forgetfulness and my lack of  
>>>>> understanding...But how do you use a physical system and a  
>>>>> drivewire system together on a real Coco
>>>> Well you can't do both simultaneously. That is you can access  
>>>> either the PC hard drive or the Coco hard drive.
>>> ?? Why not?  I use DriveWire on my CoCo 3 alongside an IDE hard disk 
>>> and a floppy.  This is under OS-9.
>>
>> Your comparing apples and oranges. Boisy might explain this better but 
>> here goes.
>>
>> Under OS-9, there should be two drivers on the boot disk one for the  
>> IDE and one for DriveWire. That means when you try to access your Coco 
>> IDE drive, the signal flows through an interface/controller in your 
>> MPI. When you try to access your PC, the signal flows through the 
>> bit-banger port via DriveWire.
>> Under Disk Basic HDBDOS, there is not room in ROM for more than one  
>> driver. It will be one of the following, scsi, ide, or DriveWire.  
>> (Boisy may have found a way to fit both scsi and ide.) So there is no 
>> way to access both a ide hard drive and a PC .vhd drive from a single 
>> ROM image under Disk Basic. You can access the floppies on the Coco 
>> while HDBDOS accesses the  PC for drives 4 and up but that is a 
>> different issue.
>
>
> Right.  Just to clarify Steve, you can do this under NitrOS-9 because of 
> the extensible nature of the OS and its access to memory resources.  On 
> the Disk BASIC side, under HDB-DOS, it's:
>
> 	FLOPPY AND (IDE OR SCSI OR DriveWire)
>
> Someone (Frank?) posted the other day a wishlist, one item being using  
> all these devices under HDB-DOS at once.  It cannot be done under the  
> current ROM size limitations that we have to work with, or without  
> expanding the syntax of the existing HDB-DOS commands.
>
> Burke & Burke's Hyper-IO was the closest I've ever seen to a Disk BASIC 
> environment having access to different types of devices like OS-9 gives 
> you.

I'm the one that posted the wish list and it included being able to access
different types of devices under hdb-dos at once. Most of this comes from
my increased use of drivewire. As you know I also have the superide adaptor
and it always frustrates me to know that I can't use it when using drivewire.

As you know I'm trying to get away from using floppies and I hate having to use
them to copy data from a drivewire image to the cf card on the ide interface.
You mention eprom space but there are four virtual eproms on the superide and
more on the superboard (when that's available). I would happily give them up
to accomodate some type of paging to allow access to drivewire and the cf in
my superide at the same time. That would of course limit it's use to those of
us that have the superide though.

That's my fantasy but it's your product and the decision is yours.

Frank


From t.fadden at cox.net  Sat Mar  7 13:48:10 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Sat, 07 Mar 2009 11:48:10 -0700
Subject: [Coco] DriveWire 3
In-Reply-To: <20090307191344.GP7702@warlock.deepthought.com>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>	<49B2B886.6050804@swbell.net>
	<20090307191344.GP7702@warlock.deepthought.com>
Message-ID: <49B2C16A.8090803@cox.net>

Thanks,

WinServer not happy with Vista 64 bit.  :-(

Error pop-up when selecting serial port if your interested is: 
(EADPException error raised, with message: Apro exception)

Tim




From boisy at tee-boy.com  Sat Mar  7 13:49:13 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Sat, 7 Mar 2009 12:49:13 -0600
Subject: [Coco] DriveWire 3
In-Reply-To: <49B2B886.6050804@swbell.net>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>
	<49B2B886.6050804@swbell.net>
Message-ID: <188C4A60-C08D-45DF-AB51-3BAAF094A023@tee-boy.com>

On Mar 7, 2009, at 12:10 PM, Joel Ewy wrote:

> Boisy,
>
> First of all, thank you for this generous gift to the CoCo  
> community.  May it drive the sale of many cables and ROM  
> cartridges.  In any case, it should help many existing users to stay  
> in the CoCo game, and aid potential new and returning CoCo users in  
> getting started, which can't be anything but good for all CoCo users  
> and vendors.  We all benefit when more people use the CoCo.
>
> Last night I made up a cable, burned DW3 into a 2764, and popped it  
> into an old Disto Super Controller.  Works like a champ.  I'm using  
> the Windows server for now, but will try out the Linux server and  
> probably also the MacOS one eventually.
>
> A couple questions:
>
> 1.  It appears to me that the only way to transfer files between  
> server disk images in HDB-DOS is through real floppy disks on the  
> CoCo.  E.g.  I want to make a disk image for games and one for image  
> files, etc.  I have individual disk image files on the server.  I  
> can select said files with "drive#[0-3]".  I can automagically  
> expand these disk image files by writing to a virtual drive number  
> >0.  But once I've issued the "drive#" command, the virtual disks in  
> the other image files on the server are inaccessible.  I could do a  
> "drive#0", then "drive off 1" and copy data to a real floppy disk,  
> assuming I have a floppy drive hooked up as drive 1.   Then I could  
> do a "drive#1" command and "drive off 1" again, and then copy the  
> data from the real floppy to a virtual disk on a different image  
> file on the server.
>
> Am I right in thinking that's the only way to do what I'm trying to  
> do in HDB-DOS, or am I missing something?  It would be really cool  
> to be able to do something like:  "backup 254#0 to 5#3" or "copy  
> "hicolor.bin:254#0" to 5#3".

Your approach is correct.  In HDB-DOS, DRIVE X (where 0 <= X <= 255)  
switches to virtual disk X (on the same virtual drive), and DRIVE #Y  
(where 0 <= Y <= 3) switches to virtual drive Y.  There is no command  
like you noted for copying between virtual drives.  This is a  
limitation of HDB-DOS, and I'm not sure if there is room in the  
current ROM to add the # enhancement.  It's something I could look at  
though.

Contrast that to NitrOS-9, which accesses virtual drives 0-3 as /X0-/X3.
>

> Just for fun I tried loading a ramdisk program that installed itself  
> as drives 2 and 3.  I wanted to try using that as an intermediate  
> location for moving files between disk images.  As I expected it  
> stomped on DriveWire.  I haven't tried all of the ramdisk programs I  
> have, but I suspect the result will be the same.
>
> 2.  Some concern has been expressed that since the CoCo 3 version of  
> DW3 runs the CoCo in high-speed mode, some auto-running games might  
> be unplayably fast.  Would a potential solution to this simply be to  
> use the CoCo 2 version and set the server accordingly?  (With the  
> obvious caveat that it would only run at 56k...)

Yes, you could actually use the HDB-DOS CoCo 2 DriveWire ROM and run a  
CoCo 3 at 56K.

One idea is to have a single ROM that could detect a CoCo 3 vs. a CoCo  
2 with one or two PEEKs, but it would have to be a reliable method.

>
> Thanks again for making this available.

You're welcome.

>
> JCE
>
>
>
> Boisy Pitre wrote:
>> As the saying goes, the only way to fight fire is with fire.
>>
>> So starting today, DriveWire 3 is now a free downloadable product  
>> from Cloud-9.
>>
>> You can go to our website at http://www.cloud9tech.com/ and click  
>> on the DriveWire announcement on the main page.  It will take you  
>> to the DriveWire 3 page, where you can now download DriveWire HDB- 
>> DOS ROMs for the CoCo 2 and CoCo 3.  Of course, you will need to  
>> burn your own EPROM in order to take advantage of these images.
>>
>> For those of you who don't have an EPROM burner or cable, we've  
>> dropped the price of our HDB-DOS ROM Pak to $20, and are still  
>> making cables available for $10.
>>
>> The server software for Windows and Mac will go up sometime today.   
>> The Linux server on SourceForge has been updated to handle the new  
>> protocol features.
>>
>> Documentation and NitrOS-9 images will be go up this weekend.
>>
>> Regards,
>> Boisy G. Pitre
>> -- 
>> Tee-Boy
>> Mobile: 337.781.3570
>> Email: boisy at tee-boy.com
>> Web: http://www.tee-boy.com
>>
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From boisy at tee-boy.com  Sat Mar  7 13:52:54 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Sat, 7 Mar 2009 12:52:54 -0600
Subject: [Coco] DriveWire 3
In-Reply-To: <49B2C16A.8090803@cox.net>
References: <8CC1F193-B3E0-46C9-960E-9FE24C471A34@tee-boy.com>	<49B2B886.6050804@swbell.net>
	<20090307191344.GP7702@warlock.deepthought.com>
	<49B2C16A.8090803@cox.net>
Message-ID: <2894F29C-EC94-4C21-8ACA-8E19E1FB2752@tee-boy.com>

On Mar 7, 2009, at 12:48 PM, Tim Fadden wrote:

> Thanks,
>
> WinServer not happy with Vista 64 bit.  :-(
>
> Error pop-up when selecting serial port if your interested is:  
> (EADPException error raised, with message: Apro exception)
>
> Tim

Tim,

DriveWire WinServer is written in Delphi and uses Async Pro serial  
port classes.  Since I'm oriented more heavily to the Mac in my  
development, I haven't tested it under Vista 64 bit, but  your  
feedback is appreciated.

If someone would like to develop a DriveWire WinServer clone in Visual  
Studio, that would be fine by me.

>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From robert.gault at worldnet.att.net  Sat Mar  7 13:59:03 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Sat, 07 Mar 2009 13:59:03 -0500
Subject: [Coco] DriveWire - test results using the now free code
In-Reply-To: <alpine.DEB.2.00.0903071110290.32155@duo>
References: <1806abd60903031432r17e68884r3fde52de071ba12f@mail.gmail.com>	<1806abd60903041245u7c295697iab9d75e4459d6364@mail.gmail.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1A6@fenestra.lamunet.local>	<49B07583.2010308@gmail.com>	<F8ADA86D-A483-4A1F-8805-627F67ED9446@tee-boy.com>	<1806abd60903051933n32a13a89ifb2cad19f3eb1b58@mail.gmail.com>	<C52627CB-515F-4BA0-8E2C-9FE37EB8E878@tee-boy.com>	<49B12C48.2030601@worldnet.att.net>	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>	<49B19282.7080902@worldnet.att.net>	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>	<49B19F46.6090201@worldnet.att.net>	<49B1F9B5.9070707@worldnet.att.net>	<4E30BB47-2793-4C87-9C4D-3C425EC546FF@tee-boy.com>	<49B282F5.6060509@worldnet.att.net>
	<alpine.DEB.2.00.0903071110290.32155@duo>
Message-ID: <49B2C3F7.4040009@worldnet.att.net>

Steven Hirsch wrote:
> On Sat, 7 Mar 2009, Robert Gault wrote:
> 
>> There are four new descriptors in the OS-9 version of DriveWire, /DD 
>> and /X1-/X3. Each of these descriptors is set for a 32,768 sector, 
>> $400 track, 1 side, $20 sector per track .os9 image as reported by 
>> dmode and free. That is very different from the standard .vhd image of 
>> $5A000 sectors with $5A tracks, $40 sides, and $40 sectors per track.
>> I was able to mount my .vhd image in Winserver as drive #1 and read 
>> the OS-9 section correctly without changing the /X1 descriptor. 
>> However, if I were going to use the .vhd image via DriveWire it would 
>> be much safer to change the descriptor to match the .vhd image.
> 
> Any possibility of a quick tutorial on patching media descriptors?
> 
> 

Hmmm, there could be specific .pdf files on the Cloud-9 site regards 
DriveWire use. Basically all you need to do is used the OS-9 command 
dmode, ex.

dmode /x1

That will show you how the descriptor x1 is currently set and the same 
command can be used to change the descriptor. Once changed, the change 
can be made permanent with the OS-9 command cobbler.

The main problem is deciding what changes you want to make and knowing 
enough about disk structures to select reasonable values. Until I get 
more familiar with DriveWire and or get to see the source code for the 
OS-9 drivers, I don't want to offer more detailed examples at this time.


From robert.gault at worldnet.att.net  Sat Mar  7 14:25:22 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Sat, 07 Mar 2009 14:25:22 -0500
Subject: [Coco] DriveWire
In-Reply-To: <20090307192611.GQ7702@warlock.deepthought.com>
References: <49B12C48.2030601@worldnet.att.net>	<3841631D-C8C4-4654-8FFC-416E96938707@tee-boy.com>	<49B19282.7080902@worldnet.att.net>	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>	<49B19F46.6090201@worldnet.att.net>
	<49B1F47A.6050102@comcast.net>	<49B1FDB1.60205@worldnet.att.net>	<alpine.DEB.2.00.0903070849360.32155@duo>	<49B286DB.2010609@worldnet.att.net>	<E932FA08-3E53-49FC-8534-17E912E8501C@tee-boy.com>
	<20090307192611.GQ7702@warlock.deepthought.com>
Message-ID: <49B2CA22.6040104@worldnet.att.net>

Frank Pittel wrote:

> I'm the one that posted the wish list and it included being able to access
> different types of devices under hdb-dos at once. Most of this comes from
> my increased use of drivewire. As you know I also have the superide adaptor
> and it always frustrates me to know that I can't use it when using drivewire.
> 
> As you know I'm trying to get away from using floppies and I hate having to use
> them to copy data from a drivewire image to the cf card on the ide interface.
> You mention eprom space but there are four virtual eproms on the superide and
> more on the superboard (when that's available). I would happily give them up
> to accomodate some type of paging to allow access to drivewire and the cf in
> my superide at the same time. That would of course limit it's use to those of
> us that have the superide though.
> 
> That's my fantasy but it's your product and the decision is yours.
> 
> Frank
> 

That could be done as I've done that with a custom DOS of my own and 
ADOS3 does that. The idea is to bury code in the ROM at $E000-$FDFF. 
When that code needs to be used, you switch from RAM to ROM, use the 
code, and switch back to RAM.
It takes very careful coding not to self-destruct and it requires a 16K 
EPROM.


From brucewcalkins at charter.net  Sat Mar  7 15:03:55 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Sat, 7 Mar 2009 15:03:55 -0500
Subject: [Coco] Model No. 26-3127B motherboard
References: <010201c99ee4$ff31b6b0$fd952410$@rr.com><010401c99ee6$c202a630$4607f290$@rr.com><49B29CD4.1040002@gmail.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3A@fenestra.lamunet.local>
Message-ID: <9D6350E28F76415E88CD5E094D8F2449@speedy>

Mike has it concisely correct.  It does appear that the 64K expansion cards 
are not all that common.  I have seen two in the dozens of CoCos that I have 
opened up.  But there are people who have opened up as many or more than I 
and not seen one.  The sockets for the 16kx4 chips will also take the 64kx4 
chips that we pull from our CoCo 3s for the 512k expansion.  These might use 
a little less power to run that the expansion card.



Bruce W.









----- Original Message ----- 
From: "Mike Pepe"

> Alan:
>
> 1: That's a 64K memory expansion card.
>
> 2: a pair of 16kx4 chips (41416 or similar) are what go in the now empty
> sockets
>
> 3: the 64k/128k jumpers refer to the ROM size. 64 kilobit (8k x 8) for
> standard color basic, 128 kilobit (16k x 8) for extended basic
>
>
>
>> -----Original Message-----
>> From: On Behalf Of N8WQ
>>
>> Folks,
>> Today I took apart a 26-3127B for the first time.
>> I have a couple of questions that need answered.
>> If you have time go to http://exwn8jef.googlepages.com/cocoprojects
>> and see if you can help me out.
>>
>> Also does anyone have a scanned copy of 26-3127B service manual?
>>
>> Thanks and have a great day.
>>
>> Alan
>>
>> --
>> N8WQ - Canal Winchester, Ohio
>> http://exwn8jef.googlepages.com/home
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From fwp at deepthought.com  Sat Mar  7 16:51:19 2009
From: fwp at deepthought.com (Frank Pittel)
Date: Sat, 7 Mar 2009 15:51:19 -0600
Subject: [Coco] DriveWire
In-Reply-To: <49B2CA22.6040104@worldnet.att.net>
References: <49B19282.7080902@worldnet.att.net>
	<5d802cd0903061329h299f68b4w267749a03b8eff55@mail.gmail.com>
	<49B19F46.6090201@worldnet.att.net> <49B1F47A.6050102@comcast.net>
	<49B1FDB1.60205@worldnet.att.net>
	<alpine.DEB.2.00.0903070849360.32155@duo>
	<49B286DB.2010609@worldnet.att.net>
	<E932FA08-3E53-49FC-8534-17E912E8501C@tee-boy.com>
	<20090307192611.GQ7702@warlock.deepthought.com>
	<49B2CA22.6040104@worldnet.att.net>
Message-ID: <20090307215119.GS7702@warlock.deepthought.com>

On Sat, Mar 07, 2009 at 02:25:22PM -0500, Robert Gault wrote:
> Frank Pittel wrote:
>
>> I'm the one that posted the wish list and it included being able to access
>> different types of devices under hdb-dos at once. Most of this comes from
>> my increased use of drivewire. As you know I also have the superide adaptor
>> and it always frustrates me to know that I can't use it when using drivewire.
>>
>> As you know I'm trying to get away from using floppies and I hate having to use
>> them to copy data from a drivewire image to the cf card on the ide interface.
>> You mention eprom space but there are four virtual eproms on the superide and
>> more on the superboard (when that's available). I would happily give them up
>> to accomodate some type of paging to allow access to drivewire and the cf in
>> my superide at the same time. That would of course limit it's use to those of
>> us that have the superide though.
>>
>> That's my fantasy but it's your product and the decision is yours.
>>
>> Frank
>>
>
> That could be done as I've done that with a custom DOS of my own and  
> ADOS3 does that. The idea is to bury code in the ROM at $E000-$FDFF.  
> When that code needs to be used, you switch from RAM to ROM, use the  
> code, and switch back to RAM.
> It takes very careful coding not to self-destruct and it requires a 16K  
> EPROM.

While I don't think I'm up to the coding challenge anymore my SuperIDE card
has four 16K "eproms" and they can be paged electronically.


From devries.bob at gmail.com  Sat Mar  7 16:39:57 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Sun, 8 Mar 2009 07:39:57 +1000
Subject: [Coco] Model No. 26-3127B motherboard
References: <010201c99ee4$ff31b6b0$fd952410$@rr.com><010401c99ee6$c202a630$4607f290$@rr.com><49B29CD4.1040002@gmail.com><4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3A@fenestra.lamunet.local>
	<9D6350E28F76415E88CD5E094D8F2449@speedy>
Message-ID: <003d01c99f6d$454a7910$0701a8c0@master>

Hmm,

Interesting comment regarding 64K daughter boards.

Here in Australia, all the 26-3127 cocos had the daughter board as supplied 
by Tandy. Any 16K coco2 was most often upgraded with the daughter board if 
done by Tandy in-house, or with 2 64k x 4 bit chips (41464 or similar) if 
done by third party hardware people or users.

I know I upgraded a dozen of them in that manner at one stage for a Tandy 
store in exchange for a 128k Coco3 (my first Coco3).

Also, the 41464 chips from the upgraded Coco3 could be used to upgrade the 
16k coco.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Bruce W. Calkins" <brucewcalkins at charter.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Sunday, March 08, 2009 6:03 AM
Subject: Re: [Coco] Model No. 26-3127B motherboard


> Mike has it concisely correct.  It does appear that the 64K expansion 
> cards are not all that common.  I have seen two in the dozens of CoCos 
> that I have opened up.  But there are people who have opened up as many or 
> more than I and not seen one.  The sockets for the 16kx4 chips will also 
> take the 64kx4 chips that we pull from our CoCo 3s for the 512k expansion. 
> These might use a little less power to run that the expansion card.
>
>
>
> Bruce W.
>
>
>
>
>
>
>
>
>
> ----- Original Message ----- 
> From: "Mike Pepe"
>
>> Alan:
>>
>> 1: That's a 64K memory expansion card.
>>
>> 2: a pair of 16kx4 chips (41416 or similar) are what go in the now empty
>> sockets
>>
>> 3: the 64k/128k jumpers refer to the ROM size. 64 kilobit (8k x 8) for
>> standard color basic, 128 kilobit (16k x 8) for extended basic
>>
>>
>>
>>> -----Original Message-----
>>> From: On Behalf Of N8WQ
>>>
>>> Folks,
>>> Today I took apart a 26-3127B for the first time.
>>> I have a couple of questions that need answered.
>>> If you have time go to http://exwn8jef.googlepages.com/cocoprojects
>>> and see if you can help me out.
>>>
>>> Also does anyone have a scanned copy of 26-3127B service manual?
>>>
>>> Thanks and have a great day.
>>>
>>> Alan
>>>
>>> --
>>> N8WQ - Canal Winchester, Ohio
>>> http://exwn8jef.googlepages.com/home
>>>
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From rcrislip at neo.rr.com  Fri Mar  6 12:25:13 2009
From: rcrislip at neo.rr.com (richec)
Date: Fri, 6 Mar 2009 12:25:13 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <200903060103.46738.gene.heskett@verizon.net>
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<6.2.5.6.2.20090305233827.02a7d4e0@cloud9tech.com>
	<200903060103.46738.gene.heskett@verizon.net>
Message-ID: <200903061225.13849.rcrislip@neo.rr.com>

On Friday 06 March 2009 01:03:46 Gene Heskett wrote:
> On Friday 06 March 2009, Mark Marlette wrote:
> >Gene,
> >
> >I am glad that your memory has returned on this. :)
> >
> >Darn it, being arrogant...Again......
>
> A wee bit perhaps, but then the same can quite easily be said of me when my
> technical feet are on solid ground.  I've even got a degree from the
> University of Hard Knocks.  See at
> <http://gene.homelinux.net:85/gene/pix/UHK-diploma2.jpg>
>
> You can only get one of those if you have 'made it' in life without any
> education above high school, and as only an 8th grade graduate, I qualified
> with points to spare.  Oh, and they need a $100 bill, a donation to the
> student loan fund at Alderson-Broddus College in Phillipe WV.  I think the
> fact that you can spare the $100 bill is evidence that you've 'made it'. :)
>
> I finally did get a GED too, also in the early 90's.  Took the test, they
> said I'd hear in a week or so, I let 2 go by and collared the teacher
> giving the test.  His reply to my question was "Why do you care, you WERE
> just doing it for the exercise weren't you?"  He of course was right. :-)
>
> [...]

That's great! I love it 8-)


From gene.heskett at verizon.net  Sat Mar  7 17:25:46 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sat, 07 Mar 2009 17:25:46 -0500
Subject: [Coco] 16550 wasRe:  RS232 paks
In-Reply-To: <200903061225.13849.rcrislip@neo.rr.com>
References: <1272082271.39971236301381258.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<200903060103.46738.gene.heskett@verizon.net>
	<200903061225.13849.rcrislip@neo.rr.com>
Message-ID: <200903071725.46289.gene.heskett@verizon.net>

On Friday 06 March 2009, richec wrote:
>On Friday 06 March 2009 01:03:46 Gene Heskett wrote:
>> On Friday 06 March 2009, Mark Marlette wrote:
>> >Gene,
>> >
>> >I am glad that your memory has returned on this. :)
>> >
>> >Darn it, being arrogant...Again......
>>
>> A wee bit perhaps, but then the same can quite easily be said of me when
>> my technical feet are on solid ground.  I've even got a degree from the
>> University of Hard Knocks.  See at
>> <http://gene.homelinux.net:85/gene/pix/UHK-diploma2.jpg>
>>
>> You can only get one of those if you have 'made it' in life without any
>> education above high school, and as only an 8th grade graduate, I
>> qualified with points to spare.  Oh, and they need a $100 bill, a donation
>> to the student loan fund at Alderson-Broddus College in Phillipe WV.  I
>> think the fact that you can spare the $100 bill is evidence that you've
>> 'made it'. :)
>>
>> I finally did get a GED too, also in the early 90's.  Took the test, they
>> said I'd hear in a week or so, I let 2 go by and collared the teacher
>> giving the test.  His reply to my question was "Why do you care, you WERE
>> just doing it for the exercise weren't you?"  He of course was right. :-)
>>
>> [...]
>
>That's great! I love it 8-)
>
I thought some of you might get a chuckle out of that.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"The most important thing in a man is not what he knows, but what he is."
-- Narciso Yepes



From cwgordon at carolina.rr.com  Sat Mar  7 19:27:49 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sat, 7 Mar 2009 19:27:49 -0500
Subject: [Coco] FD-50X Drive manuals
Message-ID: <000b01c99f84$b60b40a0$2221c1e0$@rr.com>

Does anyone have the FD-50X drive manuals? Owner's manuals or repair
manuals? I have googled, and found nothing.

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From t.fadden at cox.net  Sat Mar  7 19:52:28 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Sat, 07 Mar 2009 17:52:28 -0700
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <000b01c99f84$b60b40a0$2221c1e0$@rr.com>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com>
Message-ID: <49B316CC.4010704@cox.net>

What information are you looking for?  How to fix the floppy drive? Make 
drive cables? disk basic commands?

I have two different versions of the Disk system manual, controller 
schematics etc. Just what are you trying to do?

Bill wrote:
> Does anyone have the FD-50X drive manuals? Owner's manuals or repair
> manuals? I have googled, and found nothing.
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From cwgordon at carolina.rr.com  Sat Mar  7 20:03:18 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sat, 7 Mar 2009 20:03:18 -0500
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <49B316CC.4010704@cox.net>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com> <49B316CC.4010704@cox.net>
Message-ID: <001a01c99f89$ab9abab0$02d03010$@rr.com>

Well, I unwittingly purchased 3 different disk drives, and none of them
work. They all act pretty much the same, and I was hoping to get some kind
of an idea what to do to possibly fix the problem.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Tim Fadden
> Sent: Saturday, March 07, 2009 7:52 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] FD-50X Drive manuals
> 
> What information are you looking for?  How to fix the floppy drive?
> Make
> drive cables? disk basic commands?
> 
> I have two different versions of the Disk system manual, controller
> schematics etc. Just what are you trying to do?
> 



From jcewy at swbell.net  Sat Mar  7 22:12:01 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Sat, 07 Mar 2009 21:12:01 -0600
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <001a01c99f89$ab9abab0$02d03010$@rr.com>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com> <49B316CC.4010704@cox.net>
	<001a01c99f89$ab9abab0$02d03010$@rr.com>
Message-ID: <49B33781.3020505@swbell.net>

If 3 different drives fail in exactly the same way, I might start to 
suspect a different part of the system, like the cabling (the 
connectors, the cables themselves, or the orientation in which they're 
plugged in), the power supply, or the controller.  Do you have a good 
way to test out those other pieces?

JCE


Bill wrote:
> Well, I unwittingly purchased 3 different disk drives, and none of them
> work. They all act pretty much the same, and I was hoping to get some kind
> of an idea what to do to possibly fix the problem.
>
>   
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Tim Fadden
>> Sent: Saturday, March 07, 2009 7:52 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] FD-50X Drive manuals
>>
>> What information are you looking for?  How to fix the floppy drive?
>> Make
>> drive cables? disk basic commands?
>>
>> I have two different versions of the Disk system manual, controller
>> schematics etc. Just what are you trying to do?
>>
>>     
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>   



From t.fadden at cox.net  Sat Mar  7 22:17:43 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Sat, 07 Mar 2009 20:17:43 -0700
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <001a01c99f89$ab9abab0$02d03010$@rr.com>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com> <49B316CC.4010704@cox.net>
	<001a01c99f89$ab9abab0$02d03010$@rr.com>
Message-ID: <49B338D7.2020702@cox.net>

Ok,

Get the make/model number from each drive. We should be able to get the 
tech information from each one.  it is most likely a jumper/cable 
problem, that can be fixed. The drives themselves most likely are ok. I 
doubt the tandy manuals would help. They are specifically for the drives 
that tandy supplied, and won't have any information on any other drive.

What are you using for a controller, case, and cable?   What are the 
symptoms? If you have your yahoo chat, start it up and I will get on 
line with ya and see if  we can work it out.

If you are using the stock tandy cable, Both drives must be set as 
target 1 (some drives may say 0)  the drive at the end of the cable 
should have the resistor pack installed, and the one in the middle of 
the cable should have the resistor removed.

If you are using a straight through cable, the only difference is that 
one floppy should be jumpered as disk one, and the other as disk 2. The 
rest still applies.

Really need details in order to properly diagnose the issue!

Tim

Bill wrote:
> Well, I unwittingly purchased 3 different disk drives, and none of them
> work. They all act pretty much the same, and I was hoping to get some kind
> of an idea what to do to possibly fix the problem.
>
>   
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Tim Fadden
>> Sent: Saturday, March 07, 2009 7:52 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] FD-50X Drive manuals
>>
>> What information are you looking for?  How to fix the floppy drive?
>> Make
>> drive cables? disk basic commands?
>>
>> I have two different versions of the Disk system manual, controller
>> schematics etc. Just what are you trying to do?
>>
>>     
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From cwgordon at carolina.rr.com  Sat Mar  7 22:25:45 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sat, 7 Mar 2009 22:25:45 -0500
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <49B33781.3020505@swbell.net>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com>
	<49B316CC.4010704@cox.net>	<001a01c99f89$ab9abab0$02d03010$@rr.com>
	<49B33781.3020505@swbell.net>
Message-ID: <002001c99f9d$91ee1170$b5ca3450$@rr.com>

I have 3 separate drives (a FD-500 and (2) FD-502s). 

I have 2 controllers (a FD-500 and a FD-502)

I have 2 cables (a flat ribbon cable and a rolled shielded cable)

I only have 1 computer (a 26-3127 Coco2).

Regardless which controller I use, or which cable I use, the result is the
same.

Two of the three are FD-502. Between them, there is (1) FD-502 controller,
one flat ribbon cable, and a round shielded cable. The drives act like this
(regardless of which controller is used, 500 or 502, or which cable is
used): When the DSKINI0 command is given, the drives "click" through each of
the 35 tracks slowly, but instead of returning to the beginning and doing it
again quickly to verify, they just spin a few seconds and display an ?IO
ERROR

The third is a FD-500 w/controller, but no cable. I've been using the cable
from the first 502 (a ribbon cable). The drive acts like this (again,
regardless of which controller is used, 500 or 502): When the DSKINI0
command is given, the drive "clicks" through 18 of the 35 tracks slowly, but
then it stays in the same place for 4 more "clicks", and displays an ?IO
ERROR.

Unfortunately, I don't have any to test anything else.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Joel Ewy
> Sent: Saturday, March 07, 2009 10:12 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] FD-50X Drive manuals
> 
> If 3 different drives fail in exactly the same way, I might start to
> suspect a different part of the system, like the cabling (the
> connectors, the cables themselves, or the orientation in which they're
> plugged in), the power supply, or the controller.  Do you have a good
> way to test out those other pieces?
> 



From t.fadden at cox.net  Sat Mar  7 22:30:54 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Sat, 07 Mar 2009 20:30:54 -0700
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <001a01c99f89$ab9abab0$02d03010$@rr.com>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com> <49B316CC.4010704@cox.net>
	<001a01c99f89$ab9abab0$02d03010$@rr.com>
Message-ID: <49B33BEE.704@cox.net>

Another thought.

The card edge connector on the drives, and the controller will have a 
slot towards one side of the connector.  Also one side of the cable will 
have a colored band.  Make sure the colored band has the same 
orientation on all of the connections.  IE: colord band signifies pin 1, 
slot on card edge designates side of connector where pin 1 is located. 
Make sure all the 1's are together !.

Another common problem on old drives is that the carriage that holds the 
heads, gets gummed up, and prevents the heads from moving in and out 
freely.
This can be seen by watching the head as a dskini is performed.  listen 
to the clicks. the head should increment each time you hear a click. If 
not, its gummed up. If so, turn of the power from the drive, remove the 
floppy disk. spray some WD40 on a q-tip or some such, and wipe down the 
rail the head moves on and then physically slide the head back and forth 
a few times. DONT spray directly on the drive! You don't want it going 
all over the place, this is not good.


Tim


Bill wrote:
> Well, I unwittingly purchased 3 different disk drives, and none of them
> work. They all act pretty much the same, and I was hoping to get some kind
> of an idea what to do to possibly fix the problem.
>
>   
>> -----Original Message----- 
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Tim Fadden
>> Sent: Saturday, March 07, 2009 7:52 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] FD-50X Drive manuals
>>
>> What information are you looking for?  How to fix the floppy drive?
>> Make
>> drive cables? disk basic commands?
>>
>> I have two different versions of the Disk system manual, controller
>> schematics etc. Just what are you trying to do?
>>
>>     
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From t.fadden at cox.net  Sat Mar  7 22:41:11 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Sat, 07 Mar 2009 20:41:11 -0700
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <002001c99f9d$91ee1170$b5ca3450$@rr.com>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com>	<49B316CC.4010704@cox.net>	<001a01c99f89$ab9abab0$02d03010$@rr.com>	<49B33781.3020505@swbell.net>
	<002001c99f9d$91ee1170$b5ca3450$@rr.com>
Message-ID: <49B33E57.3020408@cox.net>

  Bill wrote:
> I have 3 separate drives (a FD-500 and (2) FD-502s). 
>
> I have 2 controllers (a FD-500 and a FD-502)
>
> I have 2 cables (a flat ribbon cable and a rolled shielded cable)
>
> I only have 1 computer (a 26-3127 Coco2).
>
> Regardless which controller I use, or which cable I use, the result is the
> same.
>
> Two of the three are FD-502. Between them, there is (1) FD-502 controller,
> one flat ribbon cable, and a round shielded cable. The drives act like this
> (regardless of which controller is used, 500 or 502, or which cable is
> used): When the DSKINI0 command is given, the drives "click" through each of
> the 35 tracks slowly, but instead of returning to the beginning and doing it
> again quickly to verify, they just spin a few seconds and display an ?IO
> ERROR
>   
Did you try more than one floppy disk?  this could be the floppy.  Could 
also be the sticky head rails problem.

> The third is a FD-500 w/controller, but no cable. I've been using the cable
> from the first 502 (a ribbon cable). The drive acts like this (again,
> regardless of which controller is used, 500 or 502): When the DSKINI0
> command is given, the drive "clicks" through 18 of the 35 tracks slowly, but
> then it stays in the same place for 4 more "clicks", and displays an ?IO
> ERROR.
>   
This looks more like sticky head rails.

Just for general  purposes, on all of the card edge connectors, dirves 
and controllers. Us a pencil erasor on the contacts and buff them up 
pretty!
Then do the clean/lube proceedure on the drives.  I be you will get them 
working.

The round cable is most likely the stock tandy cable.  The flat ribbon 
cable is most likely home made.  If you only have 1 drive on the system 
It should make no difference which cable you use as long as you put the 
drive on the end of the cable.  Tandy drives all come set as drive 1.  
The fiddle with the cable to make the drive select different.



> Unfortunately, I don't have any to test anything else.
>
>   
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Joel Ewy
>> Sent: Saturday, March 07, 2009 10:12 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] FD-50X Drive manuals
>>
>> If 3 different drives fail in exactly the same way, I might start to
>> suspect a different part of the system, like the cabling (the
>> connectors, the cables themselves, or the orientation in which they're
>> plugged in), the power supply, or the controller.  Do you have a good
>> way to test out those other pieces?
>>
>>     
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From cwgordon at carolina.rr.com  Sat Mar  7 22:43:24 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sat, 7 Mar 2009 22:43:24 -0500
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <49B338D7.2020702@cox.net>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com>
	<49B316CC.4010704@cox.net>	<001a01c99f89$ab9abab0$02d03010$@rr.com>
	<49B338D7.2020702@cox.net>
Message-ID: <002101c99fa0$0b2ea5c0$218bf140$@rr.com>

Drive #1:
Stock Tandy FD-500 (26-3129)
The drive itself is a Texas Peripherals Model 01-0065-001

Drive #2:
Stock Tandy FD-502 (26-3133)
The drive itself is labeled Tandy FD-502 w/serial number-no other markings
(without taking it apart)

Drive #3:
Stock Tandy FD-502 (26-3133)
The drive itself is labeled Tandy FD-502 w/serial number-no other markings


> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Tim Fadden
> Sent: Saturday, March 07, 2009 10:18 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] FD-50X Drive manuals
> 
> Ok,
> 
> Get the make/model number from each drive. We should be able to get the
> tech information from each one.  it is most likely a jumper/cable
> problem, that can be fixed. The drives themselves most likely are ok. I
> doubt the tandy manuals would help. They are specifically for the
> drives
> that tandy supplied, and won't have any information on any other drive.
> 
> What are you using for a controller, case, and cable?   What are the
> symptoms? If you have your yahoo chat, start it up and I will get on
> line with ya and see if  we can work it out.
> 
> If you are using the stock tandy cable, Both drives must be set as
> target 1 (some drives may say 0)  the drive at the end of the cable
> should have the resistor pack installed, and the one in the middle of
> the cable should have the resistor removed.
> 
> If you are using a straight through cable, the only difference is that
> one floppy should be jumpered as disk one, and the other as disk 2. The
> rest still applies.
> 
> Really need details in order to properly diagnose the issue!
> 



From cwgordon at carolina.rr.com  Sat Mar  7 22:47:44 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sat, 7 Mar 2009 22:47:44 -0500
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <49B33BEE.704@cox.net>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com>
	<49B316CC.4010704@cox.net>	<001a01c99f89$ab9abab0$02d03010$@rr.com>
	<49B33BEE.704@cox.net>
Message-ID: <002201c99fa0$a43091c0$ec91b540$@rr.com>

Well, aligning the cable is not hard. If it's not properly placed, the drive
light comes on and stays on till it's corrected.

I've already cleaned the rail, and that solved nothing.

I don't mean to be rude, but it's after 11 pm here, and I must get to bed.
That's one of the disadvantages of growing old; your body will only take so
much activity for one day.

With church tomorrow, I'll be back from 1 pm Eastern Daylight Savings time
until 4 pm.

Thanks for your help, see ya tomorrow

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Tim Fadden
> Sent: Saturday, March 07, 2009 10:31 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] FD-50X Drive manuals
> 
> Another thought.
> 
> The card edge connector on the drives, and the controller will have a
> slot towards one side of the connector.  Also one side of the cable
> will
> have a colored band.  Make sure the colored band has the same
> orientation on all of the connections.  IE: colord band signifies pin
> 1,
> slot on card edge designates side of connector where pin 1 is located.
> Make sure all the 1's are together !.
> 
> Another common problem on old drives is that the carriage that holds
> the
> heads, gets gummed up, and prevents the heads from moving in and out
> freely.
> This can be seen by watching the head as a dskini is performed.  listen
> to the clicks. the head should increment each time you hear a click. If
> not, its gummed up. If so, turn of the power from the drive, remove the
> floppy disk. spray some WD40 on a q-tip or some such, and wipe down the
> rail the head moves on and then physically slide the head back and
> forth
> a few times. DONT spray directly on the drive! You don't want it going
> all over the place, this is not good.
> 
> 
> Tim
> 
> 
> Bill wrote:
> > Well, I unwittingly purchased 3 different disk drives, and none of
> them
> > work. They all act pretty much the same, and I was hoping to get some
> kind
> > of an idea what to do to possibly fix the problem.
> >
> >
> >> -----Original Message-----
> >> From: coco-bounces at maltedmedia.com [mailto:coco-
> >> bounces at maltedmedia.com] On Behalf Of Tim Fadden
> >> Sent: Saturday, March 07, 2009 7:52 PM
> >> To: CoCoList for Color Computer Enthusiasts
> >> Subject: Re: [Coco] FD-50X Drive manuals
> >>
> >> What information are you looking for?  How to fix the floppy drive?
> >> Make
> >> drive cables? disk basic commands?
> >>
> >> I have two different versions of the Disk system manual, controller
> >> schematics etc. Just what are you trying to do?
> >>
> >>
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> >
> >
> >
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From gene.heskett at verizon.net  Sat Mar  7 23:36:13 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sat, 07 Mar 2009 23:36:13 -0500
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <002001c99f9d$91ee1170$b5ca3450$@rr.com>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com>
	<49B33781.3020505@swbell.net> <002001c99f9d$91ee1170$b5ca3450$@rr.com>
Message-ID: <200903072336.13981.gene.heskett@verizon.net>

On Saturday 07 March 2009, Bill wrote:
>I have 3 separate drives (a FD-500 and (2) FD-502s).
>
>I have 2 controllers (a FD-500 and a FD-502)
>
>I have 2 cables (a flat ribbon cable and a rolled shielded cable)
>
>I only have 1 computer (a 26-3127 Coco2).
>
>Regardless which controller I use, or which cable I use, the result is the
>same.
>
>Two of the three are FD-502. Between them, there is (1) FD-502 controller,
>one flat ribbon cable, and a round shielded cable. The drives act like this
>(regardless of which controller is used, 500 or 502, or which cable is
>used): When the DSKINI0 command is given, the drives "click" through each of
>the 35 tracks slowly, but instead of returning to the beginning and doing it
>again quickly to verify, they just spin a few seconds and display an ?IO
>ERROR
>
>The third is a FD-500 w/controller, but no cable. I've been using the cable
>from the first 502 (a ribbon cable). The drive acts like this (again,
>regardless of which controller is used, 500 or 502): When the DSKINI0
>command is given, the drive "clicks" through 18 of the 35 tracks slowly, but
>then it stays in the same place for 4 more "clicks", and displays an ?IO
>ERROR.
>
>Unfortunately, I don't have any to test anything else.

1. Do the activity leds on the drives come on? (1 at a time)

2. Is this cable a 'twisted' cable (so that both drives can be set to respond 
to disk selector signal ds1, and check the drives for their jumper settings 
for that)  and does it have any missing contacts in the card edge connectors 
that plug onto the backs of the drives?

I am told that the twisted cables used for the coco's are not twisted in the 
same exact manner as those used in now very elderly pc's, you may have a 'pc' 
cable somebody threw in the kit just so it had a cable.

3. It would be unlikely that all 3 drives have worn or dirty heads, but the 
dirty part can be checked if the drive is removed from the box by wetting a q-
tip in the alcohol sold at paint supply stores such as Ace Hdwe.  Rubbing 
alcohol is cut with water and the denaturing additive, but the paint store or 
ace hdwe stuff is the real thing.  The heads can be identified once the drive 
is out of the box, they slide in and out in a position directly behind the 
disks hub driving spindle, and are usually what looks like a white ceramic 
thing about 3/16" square, mounted very flimsily in the end of the arm of the 
carriage.  Slide it to an accessible point, and wipe the face with a q-tip 
wetted with the alcohol, gently of course.  Single sided drives will have a 
felt pad on the other arm that faces the other side of the disk.  Give it time 
to dry is you get it damp.

While you are in there, the drives will probably thank you for a drop of 
sewing machine oil applied to the rods the head carriage slides on.

4. Another ugly thought, are the disk spindles belt driven?  Maybe the belts 
are slipping and the disk itself is not turning at its normal 300 rpm.  Along 
the same lines, the plastic rosette that presses the disk hub to the drive 
spindle may also have relaxed over the years, that reduces the grip pressure, 
so the disk itself, with its liner lubes all evaporated over the years which 
makes the disk hard to turn in its sleeve, and then the hub is slipping.  This 
can usually be identified by putting a magic marker mark on both sides of the 
hub hole, and doing a dskini.  Then look at the mark, if worn away on one 
side, its slipping there.

FWIW, this is a huge problem with 8" floppy drives, been there, done that.

>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Joel Ewy
>> Sent: Saturday, March 07, 2009 10:12 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] FD-50X Drive manuals
>>
>> If 3 different drives fail in exactly the same way, I might start to
>> suspect a different part of the system, like the cabling (the
>> connectors, the cables themselves, or the orientation in which they're
>> plugged in), the power supply, or the controller.  Do you have a good
>> way to test out those other pieces?
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If you find a solution and become attached to it, the solution may become
your next problem.



From lamune at doki-doki.net  Sun Mar  8 00:36:32 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Sat, 7 Mar 2009 21:36:32 -0800
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <002201c99fa0$a43091c0$ec91b540$@rr.com>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com><49B316CC.4010704@cox.net>	<001a01c99f89$ab9abab0$02d03010$@rr.com><49B33BEE.704@cox.net>
	<002201c99fa0$a43091c0$ec91b540$@rr.com>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3C@fenestra.lamunet.local>

Bill, hope you said some extra prayers, I think your CoCo collection is
possessed!

A couple of things to note:

1- you can't exclude a problem with the CoCo itself at this point
2- The old full height TP drive is probably a lost cause due its many
mechanical and analog adjustments. I wouldn't bother with it just yet
3- The FD502 service manual is useless without a ton of specialized
equipment.
4- The stepper motors are bi-phase, so when you say you hear 18 clicks
you may be hearing 35 tracks, but only every alternate step is audible.
5- The round FD502 cables are subject to failure. I've seen a couple of
broken ones so far. The flat ribbon cable may be bad also, but I doubt
all 3 cables are bad in exactly the same way.
6- bad media? Are you formatting HD floppies? Does the problem persist
on different media?

I would open the covers up on the 502's and watch the show. Most
importantly if the head restores itself to track 0 once the format
process is completed.

The format process is pretty much blind. As long as the controller is
seeing index pulses from the drive there's really nothing I can think of
that would cause it to bomb out in the middle of the process (other than
loss of index pulses)

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Bill
> Sent: Saturday, March 07, 2009 7:48 PM
> To: 'CoCoList for Color Computer Enthusiasts'
> Subject: Re: [Coco] FD-50X Drive manuals
> 
> Well, aligning the cable is not hard. If it's not properly placed, the
> drive
> light comes on and stays on till it's corrected.
> 
> I've already cleaned the rail, and that solved nothing.
> 
> I don't mean to be rude, but it's after 11 pm here, and I must get to
> bed.
> That's one of the disadvantages of growing old; your body will only
> take so
> much activity for one day.
> 
> With church tomorrow, I'll be back from 1 pm Eastern Daylight Savings
> time
> until 4 pm.
> 
> Thanks for your help, see ya tomorrow
> 
> > -----Original Message-----
> > From: coco-bounces at maltedmedia.com [mailto:coco-
> > bounces at maltedmedia.com] On Behalf Of Tim Fadden
> > Sent: Saturday, March 07, 2009 10:31 PM
> > To: CoCoList for Color Computer Enthusiasts
> > Subject: Re: [Coco] FD-50X Drive manuals
> >
> > Another thought.
> >
> > The card edge connector on the drives, and the controller will have
a
> > slot towards one side of the connector.  Also one side of the cable
> > will
> > have a colored band.  Make sure the colored band has the same
> > orientation on all of the connections.  IE: colord band signifies
pin
> > 1,
> > slot on card edge designates side of connector where pin 1 is
> located.
> > Make sure all the 1's are together !.
> >
> > Another common problem on old drives is that the carriage that holds
> > the
> > heads, gets gummed up, and prevents the heads from moving in and out
> > freely.
> > This can be seen by watching the head as a dskini is performed.
> listen
> > to the clicks. the head should increment each time you hear a click.
> If
> > not, its gummed up. If so, turn of the power from the drive, remove
> the
> > floppy disk. spray some WD40 on a q-tip or some such, and wipe down
> the
> > rail the head moves on and then physically slide the head back and
> > forth
> > a few times. DONT spray directly on the drive! You don't want it
> going
> > all over the place, this is not good.
> >
> >
> > Tim
> >
> >
> > Bill wrote:
> > > Well, I unwittingly purchased 3 different disk drives, and none of
> > them
> > > work. They all act pretty much the same, and I was hoping to get
> some
> > kind
> > > of an idea what to do to possibly fix the problem.
> > >
> > >
> > >> -----Original Message-----
> > >> From: coco-bounces at maltedmedia.com [mailto:coco-
> > >> bounces at maltedmedia.com] On Behalf Of Tim Fadden
> > >> Sent: Saturday, March 07, 2009 7:52 PM
> > >> To: CoCoList for Color Computer Enthusiasts
> > >> Subject: Re: [Coco] FD-50X Drive manuals
> > >>
> > >> What information are you looking for?  How to fix the floppy
> drive?
> > >> Make
> > >> drive cables? disk basic commands?
> > >>
> > >> I have two different versions of the Disk system manual,
> controller
> > >> schematics etc. Just what are you trying to do?
> > >>
> > >>
> > >
> > >
> > > --
> > > Coco mailing list
> > > Coco at maltedmedia.com
> > > http://five.pairlist.net/mailman/listinfo/coco
> > >
> > >
> > >
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From RJRTTY at aol.com  Sun Mar  8 01:05:29 2009
From: RJRTTY at aol.com (RJRTTY at aol.com)
Date: Sun, 8 Mar 2009 01:05:29 EST
Subject: [Coco] Technical question
Message-ID: <d53.43a30c56.36e4ba29@aol.com>

In a message dated 3/6/2009 8:51:33 P.M. Eastern  Standard Time, 
gene.heskett at verizon.net writes:
>>Many if not most  Coco3 problems can be "cured" by removing the GIME
>>(large square  chip) from its socket and re-seating it. It's an oxidation
>>problem.  Be careful, you will need something better than two  small
>>screwdrivers to do this without causing  damage.
>>
>That gizmo is called a PLCC puller, and the shack  used to have them for 
about 
>a tenner.  Ingenious little mechanism  too  


You can still get them from Jameco.....
 
Roy
 
**************Need a job? Find employment help in your area. 
(http://yellowpages.aol.com/search?query=employment_agencies&ncid=emlcntusyelp00000005)


From goosey at virgo.sdc.org  Sun Mar  8 03:27:15 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Sun, 8 Mar 2009 00:27:15 -0700
Subject: [Coco] now I remember...
Message-ID: <20090308072715.GA9480@virgo.sdc.org>

Why I never program in Pascal any more....

Since the OS-9 Pascal compiler doesn't have a RND() in its standard
functions, last summer I tracked down one in Pascal.  I got it typed
in, but then I was out of town, and away from my CoCo3, for 7 months.

So yesterday, I finally got around to hacking on the code to turn it
into a standalone Pascal subroutine module.

And now it's done, and I remember why I don't use Pascal any more. :-(

Actually, though, I had more problems with the simple fact that OS-9
subroutine modules can't (easily) have any static data space.  And an
RND generator (Knuth's Random3, if you're interested) needs a fair bit
of static space.

Once I get the bad taste out of my mouth, I want to convert the RND
code over to DEFT Pascal, since it also lacks an RND function.

And I can't write a game without random numbers. ;-)  I don't know if
I'll ever write another game in Pascal, but I do want to port my old,
bad Turbo Pascal games over.

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From goosey at virgo.sdc.org  Sun Mar  8 03:29:17 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Sun, 8 Mar 2009 00:29:17 -0700
Subject: [Coco] Amusing set of error messages (can you see whats wrong?)
Message-ID: <20090308072917.GB9480@virgo.sdc.org>

skywarp:~$ mount /home/goosey/brawl
Password: 
smbmnt must be installed suid root for direct user mounts (501,501)
smbmnt failed: 1
skywarp:~$ which smbmount
/usr/bin/smbmount
skywarp:~$ su   
Password: 
skywarp:/home/goosey# cd /usr/bin
skywarp:/usr/bin# chmod +s smbmount
skywarp:/usr/bin# ll smbmount
 484 -rwsr-sr-x    1 root     bin        489492 Apr  7  2003 smbmount
skywarp:/usr/bin# exit
skywarp:~$ mount /home/goosey/brawl
libsmb based programs must *NOT* be setuid root.
5817: Connection to brawl failed
SMB connection failed

-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From georgeramsower at gmail.com  Sun Mar  8 05:24:10 2009
From: georgeramsower at gmail.com (George Ramsower)
Date: Sun, 8 Mar 2009 03:24:10 -0600
Subject: [Coco] Amusing set of error messages (can you see whats wrong?)
References: <20090308072917.GB9480@virgo.sdc.org>
Message-ID: <008701c99fcf$a3c4cc40$6401a8c0@OLDGEORGE>


----- Original Message ----- 
From: "Willard Goosey"
Subject: [Coco] Amusing set of error messages (can you see whats wrong?)


> skywarp:~$ mount /home/goosey/brawl
> Password:
> smbmnt must be installed suid root for direct user mounts (501,501)
> smbmnt failed: 1
> skywarp:~$ which smbmount
> /usr/bin/smbmount
> skywarp:~$ su
> Password:
> skywarp:/home/goosey# cd /usr/bin
> skywarp:/usr/bin# chmod +s smbmount
> skywarp:/usr/bin# ll smbmount
> 484 -rwsr-sr-x    1 root     bin        489492 Apr  7  2003 smbmount
> skywarp:/usr/bin# exit
> skywarp:~$ mount /home/goosey/brawl
> libsmb based programs must *NOT* be setuid root.
> 5817: Connection to brawl failed
> SMB connection failed

 (Tongue in cheek) .... It appears to me that this just flat out won't work 
on a coco.  Must try pressing the reset button and wait a few milliseconds 
and it will begin to work.

George 



From cwgordon at carolina.rr.com  Sun Mar  8 07:53:29 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 8 Mar 2009 06:53:29 -0500
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3C@fenestra.lamunet.local>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com><49B316CC.4010704@cox.net>	<001a01c99f89$ab9abab0$02d03010$@rr.com><49B33BEE.704@cox.net>	<002201c99fa0$a43091c0$ec91b540$@rr.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3C@fenestra.lamunet.local>
Message-ID: <002301c99fe4$80c39130$824ab390$@rr.com>

	6- bad media? Are you formatting HD floppies? Does the problem
persist on different media?
As a matter of fact, they ARE _HD_ floppies. Certron MD-2HD, to be precise.
It's been so long since I even thought about them, I didn't put two and two
together. If anyone had a spare floppy drive (or several), I'd appreciate
the loan of one.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Mike Pepe
> Sent: Sunday, March 08, 2009 12:37 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] FD-50X Drive manuals
> 
> Bill, hope you said some extra prayers, I think your CoCo collection is
> possessed!
> 
> A couple of things to note:
> 
> 1- you can't exclude a problem with the CoCo itself at this point
> 2- The old full height TP drive is probably a lost cause due its many
> mechanical and analog adjustments. I wouldn't bother with it just yet
> 3- The FD502 service manual is useless without a ton of specialized
> equipment.
> 4- The stepper motors are bi-phase, so when you say you hear 18 clicks
> you may be hearing 35 tracks, but only every alternate step is audible.
> 5- The round FD502 cables are subject to failure. I've seen a couple of
> broken ones so far. The flat ribbon cable may be bad also, but I doubt
> all 3 cables are bad in exactly the same way.
> 6- bad media? Are you formatting HD floppies? Does the problem persist
> on different media?
> 
> I would open the covers up on the 502's and watch the show. Most
> importantly if the head restores itself to track 0 once the format
> process is completed.
> 
> The format process is pretty much blind. As long as the controller is
> seeing index pulses from the drive there's really nothing I can think
> of
> that would cause it to bomb out in the middle of the process (other
> than
> loss of index pulses) 
co



From cwgordon at carolina.rr.com  Sun Mar  8 08:33:49 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 8 Mar 2009 07:33:49 -0500
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <002301c99fe4$80c39130$824ab390$@rr.com>
References: <000b01c99f84$b60b40a0$2221c1e0$@rr.com><49B316CC.4010704@cox.net>	<001a01c99f89$ab9abab0$02d03010$@rr.com><49B33BEE.704@cox.net>	<002201c99fa0$a43091c0$ec91b540$@rr.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3C@fenestra.lamunet.local>
	<002301c99fe4$80c39130$824ab390$@rr.com>
Message-ID: <002401c99fea$226ecc20$674c6460$@rr.com>

What I meant to say was if anyone had a spare floppy disk (or several) I'd
appreciate the loan

> If anyone had a spare floppy drive (or several), I'd appreciate
> the loan of one.



From farna at att.net  Sun Mar  8 09:41:43 2009
From: farna at att.net (Frank Swygert)
Date: Sun, 08 Mar 2009 08:41:43 -0500
Subject: [Coco] FD-50X Drive manuals
Message-ID: <49B3CB17.7080006@att.net>

Bill, download "Tandy's Little Wonder". It has basic repair and troubleshooting info in it for the CoCos and most peripherals. It also has the pin-outs for all the connectors and guides on making the most used cables. 

Schematics are there also, but didn't come out real good in the transition to a PDF file. Some were marginal in print due to being copies of copies, another conversion didn't do those any good! Most can be read with a magnifying glass though. 

----------
Date: Sat, 7 Mar 2009 20:03:18 -0500
From: "Bill" <cwgordon at carolina.rr.com>

Well, I unwittingly purchased 3 different disk drives, and none of them
work. They all act pretty much the same, and I was hoping to get some kind
of an idea what to do to possibly fix the problem.

-- 
Frank Swygert
Publisher, "American Motors Cars" 
Magazine (AMC)
For all AMC enthusiasts
http://farna.home.att.net/AMC.html
(free download available!)



From cwgordon at carolina.rr.com  Sun Mar  8 09:08:14 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 8 Mar 2009 08:08:14 -0500
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <49B3CB17.7080006@att.net>
References: <49B3CB17.7080006@att.net>
Message-ID: <002501c99fee$f12f46d0$d38dd470$@rr.com>

Unfortunately there is no information about either the FD-500 or FD-502
drives.

Thanks..

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Frank Swygert
> Sent: Sunday, March 08, 2009 8:42 AM
> To: coco at maltedmedia.com
> Subject: Re: [Coco] FD-50X Drive manuals
> 
> Bill, download "Tandy's Little Wonder". It has basic repair and
> troubleshooting info in it for the CoCos and most peripherals. It also
> has the pin-outs for all the connectors and guides on making the most
> used cables.
> 
> Schematics are there also, but didn't come out real good in the
> transition to a PDF file. Some were marginal in print due to being
> copies of copies, another conversion didn't do those any good! Most can
> be read with a magnifying glass though.
> 



From cwgordon at carolina.rr.com  Sun Mar  8 09:20:45 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 8 Mar 2009 08:20:45 -0500
Subject: [Coco] Floppy disks
Message-ID: <000001c99ff0$b0e8bd20$12ba3760$@rr.com>

Please refresh my memory. Will plain old double-sided, double density disks
work? I might be able to get some from my local Office Depot (hopefully).

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From coconut at pritchard.ca  Sun Mar  8 09:32:05 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Sun, 8 Mar 2009 07:32:05 -0600
Subject: [Coco] Floppy disks
In-Reply-To: <000001c99ff0$b0e8bd20$12ba3760$@rr.com>
References: <000001c99ff0$b0e8bd20$12ba3760$@rr.com>
Message-ID: <1806abd60903080632p2c59718fj5b1c06ea82f8f92d@mail.gmail.com>

Hi Bill,
Yes you want DSDD 5.25" 360K diskettes.  I had the same problem as you
describe back in Aug / Sep last year as I tried getting my CoCo 1 going.  I
luckily had a box of DSDD diskettes.  My biggest fight was drive jumpers and
getting the drive select and other settings correct since none of my drives
where CoCo drives.

I also have both 3.5" and 5.25" floppy drives.  The only problem is I
haven't sourced any DSDD 3.5" 720K diskettes, and have been fudging my way
along covering the HD hole on the 3.5" 1.44M diskettes I have, which results
in very un-reliable disk writes.  As for my DSDD 5.25" 360K diskettes they
are flawless even with my odd Teac FD-55F-03-U 80 track DSDD 720K drives.

Unfortunately the basic I have only allows the 35 track single side
formatting.  Though it is my understanding that NitrOS-9 Level 1 can be
configured to use the entire 80 tracks and both sides.

On Sun, Mar 8, 2009 at 7:20 AM, Bill <cwgordon at carolina.rr.com> wrote:

> Please refresh my memory. Will plain old double-sided, double density disks
> work? I might be able to get some from my local Office Depot (hopefully).
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From wdg3rd at comcast.net  Sun Mar  8 09:56:42 2009
From: wdg3rd at comcast.net (wdg3rd at comcast.net)
Date: Sun, 8 Mar 2009 13:56:42 +0000 (UTC)
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <1097934851.21301236519949873.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
Message-ID: <127395783.23341236520602550.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>

----- "Tim Fadden" <t.fadden at cox.net> wrote:


> This looks more like sticky head rails.
> 
> Just for general  purposes, on all of the card edge connectors, dirves
> 
> and controllers. Us a pencil erasor on the contacts and buff them up 
> pretty!
> Then do the clean/lube proceedure on the drives.  I be you will get
> them 
> working.
> 
> The round cable is most likely the stock tandy cable.  The flat ribbon
> cable is most likely home made.  If you only have 1 drive on the
> system 
> It should make no difference which cable you use as long as you put
> the 
> drive on the end of the cable.  Tandy drives all come set as drive 1. 
> 
> The fiddle with the cable to make the drive select different.

To the best of my knowledge (which used to be pretty exhaustive, but in a couple of decades a lot of brain cells die, and I have habits that help that process), Tandy never made a round floppy cable -- it was just ribbon.  Mod 1/3/4 FD and HD, Mod 2/12/16/6k FD and HD, Coco FD and HD, Tandy 2000 and early PC compatibles external HD.  All ribbons.  (My knowledge may be incomplete, as I left the company in 1986 and they didn't completely stop manufacturing computer products until five or six more years later, so some round cables may have snuck in while I wasn't watching, but I doubt it, they cost more and the Shack was always went for the cheap).  (Connecting the ends of round cables to _anything_ is labor intensive, which makes them expensive and is one of the reasons land lines cost so much).
-- 
Ward Griffiths        wdg3rd at comcast.net

<home.comcast.net/~wdg3rd>
(page has stale links and resume is not up to date as I'm employed at a dead end job with a health plan and if I quit for a short-lived high-pay consulting gig, La Esposa will make me homeless before the first check arrives)


From gene.heskett at verizon.net  Sun Mar  8 10:06:13 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sun, 08 Mar 2009 09:06:13 -0500
Subject: [Coco] Amusing set of error messages (can you see whats wrong?)
In-Reply-To: <20090308072917.GB9480@virgo.sdc.org>
References: <20090308072917.GB9480@virgo.sdc.org>
Message-ID: <200903081006.13767.gene.heskett@verizon.net>

On Sunday 08 March 2009, Willard Goosey wrote:
>skywarp:~$ mount /home/goosey/brawl
>Password:
>smbmnt must be installed suid root for direct user mounts (501,501)
Who is 501?
>smbmnt failed: 1
>skywarp:~$ which smbmount
>/usr/bin/smbmount
>skywarp:~$ su
Where is the - sign?  You don't get root's environment without it. 
>Password:
>skywarp:/home/goosey# cd /usr/bin
>skywarp:/usr/bin# chmod +s smbmount
>skywarp:/usr/bin# ll smbmount
> 484 -rwsr-sr-x    1 root     bin        489492 Apr  7  2003 smbmount
>skywarp:/usr/bin# exit
>skywarp:~$ mount /home/goosey/brawl
>libsmb based programs must *NOT* be setuid root.
>5817: Connection to brawl failed
>SMB connection failed

This disk is on a different machine where you _were_ user 501?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My, how you've changed since I've changed.



From brucewcalkins at charter.net  Sun Mar  8 10:06:58 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Sun, 8 Mar 2009 10:06:58 -0400
Subject: [Coco] Floppy disks
References: <000001c99ff0$b0e8bd20$12ba3760$@rr.com>
Message-ID: <3FD957110AB14242875AD31FB6BD4F6E@speedy>

Yes; they might be marked as, 2S2D, 2SDD, Formated for 360k or almost any 
other combination of that information.  Better than 90% of the 2S2D disks 
will have a reinforcement ring in the center, while better than 90% ot the 
2SHD will not.

As to finding 2S2D disks?  Of late I've had better luck in thrift stores 
than office supply stores.

Bruce W.




> Please refresh my memory. Will plain old double-sided, double density 
> disks
> work? I might be able to get some from my local Office Depot (hopefully).
>



From gene.heskett at verizon.net  Sun Mar  8 10:08:24 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sun, 08 Mar 2009 09:08:24 -0500
Subject: [Coco] Floppy disks
In-Reply-To: <000001c99ff0$b0e8bd20$12ba3760$@rr.com>
References: <000001c99ff0$b0e8bd20$12ba3760$@rr.com>
Message-ID: <200903081008.24275.gene.heskett@verizon.net>

On Sunday 08 March 2009, Bill wrote:
>Please refresh my memory. Will plain old double-sided, double density disks
>work? I might be able to get some from my local Office Depot (hopefully).
>
Yes of course, the drives, if they are single sided drives, won't care whats 
on the backside.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Succumb to natural tendencies.  Be hateful and boring.



From brucewcalkins at charter.net  Sun Mar  8 10:25:45 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Sun, 8 Mar 2009 10:25:45 -0400
Subject: [Coco] Floppy disks
References: <000001c99ff0$b0e8bd20$12ba3760$@rr.com>
	<1806abd60903080632p2c59718fj5b1c06ea82f8f92d@mail.gmail.com>
Message-ID: <400F15E4F59841CBBA818F5816A4F902@speedy>

> Unfortunately the basic I have only allows the 35 track single side
> formatting.  Though it is my understanding that NitrOS-9 Level 1

> can be configured to use the entire 80 tracks and both sides.



RS Basic can be patched to use both sides of a double sided disk.  On a CoCo 
1 or 2 this requires 64k on a temporary basis or a new ROM to be permanent. 
For the CoCo 3, in which the ROM is transferred to RAM on start up, a couple 
of POKEs could set the drive look-up table for accessing the back side of 
double sided drives.  In both cases, the maximum number of drive "sides" 
visible to the CoCo was 4.  OS-9 was limited to 3 physical drives by 
hardware issues.  There is also a way to hard code the double sided drives 
to act as two drives for RS Basic.



ALL Forms of OS-9 can be patched for the FULL use of double sided drives. 
Level One Release One was a little difficult, but doable.  There were such 
"minor" issues as having to boot from a single sided disk to get to the 
double sided environment.  Any version of OS-9 after that was just a matter 
of setting the number of sides in the device descriptor.



However; the hardware solution for RS Basic made it impossible to use the 
drives as double sided under OS-9.  Also OS-9 (Not that it mattered much.) 
could not read the "other" side of the alternate side of RS Basic disks.



Bruce W.



From brucewcalkins at charter.net  Sun Mar  8 10:27:57 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Sun, 8 Mar 2009 10:27:57 -0400
Subject: [Coco] FD-50X Drive manuals
References: <127395783.23341236520602550.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
Message-ID: <F0EF66D23A0B489E8CFB9B49BADB1835@speedy>

> To the best of my knowledge (which used to 
> be pretty exhaustive, but in a couple of decades 
> a lot of brain cells die, and I have habits that 
> help that process), Tandy never made a round 
> floppy cable -- it was just ribbon. 



The FD-502 used a ribbon cable bound with a round sheath.
This may be the confusion.

Bruce W.


From wdg3rd at comcast.net  Sun Mar  8 10:29:12 2009
From: wdg3rd at comcast.net (wdg3rd at comcast.net)
Date: Sun, 8 Mar 2009 14:29:12 +0000 (UTC)
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <878047195.29411236522389812.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
Message-ID: <860604649.29991236522552692.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>

----- "Gene Heskett" <gene.heskett at verizon.net> wrote:

> FWIW, this is a huge problem with 8" floppy drives, been there, done
> that.-- 

Gene, this is slightly off-topic, but do you know of any sources (or fabrication hints) for head-load pads for old CDC and Shugart 8" SSDD floppy drives? ?I don't want to lose any more of my TRS-80 Model 2 media (nobody has yet written [or probably ever will, as there are few games] an emulator for that line and I am incompetent to do so). ?Model 2 Scripsit (no relation to Color Scripsit except in name, there were half a dozen unrelated programs with that name produced in Fort Worth) is still one of my preferred word processing programs, the same program Isaac Asimov used to type his last hundred or so books.
?
Ward Griffiths ? ? ? ?wdg3rd at comcast.net

<home.comcast.net/~wdg3rd>
(page has stale links and resume is not up to date as I'm employed at a dead end job with a health plan and if I quit for a short-lived high-pay consulting gig, La Esposa will make me homeless before the first check arrives)


From gene.heskett at verizon.net  Sun Mar  8 10:58:38 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sun, 08 Mar 2009 09:58:38 -0500
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <860604649.29991236522552692.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
References: <860604649.29991236522552692.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
Message-ID: <200903081058.38697.gene.heskett@verizon.net>

On Sunday 08 March 2009, wdg3rd at comcast.net wrote:
>----- "Gene Heskett" <gene.heskett at verizon.net> wrote:
>> FWIW, this is a huge problem with 8" floppy drives, been there, done
>> that.--
>
>Gene, this is slightly off-topic, but do you know of any sources (or
> fabrication hints) for head-load pads for old CDC and Shugart 8" SSDD
> floppy drives? ?I don't want to lose any more of my TRS-80 Model 2 media
> (nobody has yet written [or probably ever will, as there are few games] an
> emulator for that line and I am incompetent to do so). ?Model 2 Scripsit
> (no relation to Color Scripsit except in name, there were half a dozen
> unrelated programs with that name produced in Fort Worth) is still one of
> my preferred word processing programs, the same program Isaac Asimov used
> to type his last hundred or so books. 

I battled that with an old Beston Marque character generator many years ago.  
I wasn't able to find felt of the same thickness locally, and I tried to stack 
3 layers of the green stuff, using various glues including rubber cement, but 
found that if it was used sparingly enough not to bleed through, that it 
wasn't a very dependable solution since I was also giving them a short shot of 
wd-40 for lube, letting it dry thoroughly.  Then I stumbled across some brand 
new, surplus Shugart double sided 8" drives for $50 ea, and replaced both of 
the old 800's with them.  Then I got a patch from them to use double sided 
drives, and all my CG operators bowed down and kissed my shoes.

But those were the ones with insufficient pressure on the rosettes & had to 
find a shim to put under the closing clamps leaf spring in order to get enough 
pressure to drive the disks, and that led to rosette deformation and damaged 
hub holes.  It didn't help a bit that the disks we were getting had been 
laying horizontally in a Mexican warehouse for 15 years, crushing the sleeve 
edges from cold flow, and of course driving all the lubricants out.  Later, I 
solved that problem for a little while by installing some Bournelli drives, 
but they weren't all that dependable either.  Eventually we gave up and bought 
another CG, much more capable then the old Aston or Beston we'ed had since the 
biblical flood waters had receded, or at least it sure seemed it was that old.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Of course, this being Perl, we could always take both approaches.  :-)
             -- Larry Wall in <199709021744.KAA12428 at wall.org>



From farna at att.net  Sun Mar  8 12:14:29 2009
From: farna at att.net (Frank Swygert)
Date: Sun, 08 Mar 2009 11:14:29 -0500
Subject: [Coco] FD-50X Drive manuals
Message-ID: <49B3EEE5.7090807@att.net>

You are correct -- there is no specific FD-50x info, other than a 
schematic for a couple of the controller. All the drive info is generic 
to all drives. In fact the only thing unique to the CoCo is the 
controller itself. Tandy used several different drive suppliers. Other 
computers also used single sided drives, even the IBM PCjr IIRC. The 
drives themselves are generic and will work in any computer capable of 
recognizing a 5.25" single sided drive (a lot of the newer PCs won't 
recognize any 5.25" drive automatically). That's one thing that swayed 
me to go with the CoCo long ago. Tandy usually used Tandon drives, at 
least in the older ones, but I have seen other manufacturers in cases 
known to come from Tandy. The last half-high units were from someone 
else, don't recall who now (not that it matters). I had a pair of Ricoh 
360K drives in my second disk system, the first was a dinosaur full 
height Tandon. I removed the Tandon and stuck the two surplus Ricohs in 
the same case. The old full height drives took a lot more power than 
newer half-height models. Had to drill mounting holes for the second 
drive. Used the same ribbon cable, just configured the drives to work 
with the "snaggle toothed" cable. ----------- Date: Sun, 8 Mar 2009 
08:08:14 -0500 From: "Bill" <cwgordon at carolina.rr.com> Subject: Re: 
[Coco] FD-50X Drive manuals To: "'CoCoList for Color Computer 
Enthusiasts'" <coco at maltedmedia.com> Message-ID: 
<002501c99fee$f12f46d0$d38dd470$@rr.com> Content-Type: text/plain; 
charset="us-ascii" Unfortunately there is no information about either 
the FD-500 or FD-502 drives. Thanks..

> > -----Original Message-----
> > From: coco-bounces at maltedmedia.com [mailto:coco-
> > bounces at maltedmedia.com] On Behalf Of Frank Swygert
> > Sent: Sunday, March 08, 2009 8:42 AM
> > To: coco at maltedmedia.com
> > Subject: Re: [Coco] FD-50X Drive manuals
> > 
> > Bill, download "Tandy's Little Wonder". It has basic repair and
> > troubleshooting info in it for the CoCos and most peripherals. It also
> > has the pin-outs for all the connectors and guides on making the most
> > used cables.
> > 
-- 
Frank Swygert
Publisher, "American Motors Cars" 
Magazine (AMC)
For all AMC enthusiasts
http://farna.home.att.net/AMC.html
(free download available!)



From t.fadden at cox.net  Sun Mar  8 11:39:26 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Sun, 08 Mar 2009 08:39:26 -0700
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <127395783.23341236520602550.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
References: <127395783.23341236520602550.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
Message-ID: <49B3E6AE.8060004@cox.net>

Don't know about ALL of the models, but the latest 502's come with ROUND 
cables.  Unless you are pulling my leg.   They are actually  flat cables 
put into a grey ROUND sleave. If you want a picture I can send it.

Tim

wdg3rd at comcast.net wrote:
> ----- "Tim Fadden" <t.fadden at cox.net> wrote:
>
>
>   
>> This looks more like sticky head rails.
>>
>> Just for general  purposes, on all of the card edge connectors, dirves
>>
>> and controllers. Us a pencil erasor on the contacts and buff them up 
>> pretty!
>> Then do the clean/lube proceedure on the drives.  I be you will get
>> them 
>> working.
>>
>> The round cable is most likely the stock tandy cable.  The flat ribbon
>> cable is most likely home made.  If you only have 1 drive on the
>> system 
>> It should make no difference which cable you use as long as you put
>> the 
>> drive on the end of the cable.  Tandy drives all come set as drive 1. 
>>
>> The fiddle with the cable to make the drive select different.
>>     
>
> To the best of my knowledge (which used to be pretty exhaustive, but in a couple of decades a lot of brain cells die, and I have habits that help that process), Tandy never made a round floppy cable -- it was just ribbon.  Mod 1/3/4 FD and HD, Mod 2/12/16/6k FD and HD, Coco FD and HD, Tandy 2000 and early PC compatibles external HD.  All ribbons.  (My knowledge may be incomplete, as I left the company in 1986 and they didn't completely stop manufacturing computer products until five or six more years later, so some round cables may have snuck in while I wasn't watching, but I doubt it, they cost more and the Shack was always went for the cheap).  (Connecting the ends of round cables to _anything_ is labor intensive, which makes them expensive and is one of the reasons land lines cost so much).
>   



From wdg3rd at comcast.net  Sun Mar  8 12:58:30 2009
From: wdg3rd at comcast.net (wdg3rd at comcast.net)
Date: Sun, 8 Mar 2009 16:58:30 +0000 (UTC)
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <1256571638.68611236531477590.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
Message-ID: <290131814.68811236531510064.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>

I'll take your word for it.  It must have been after my time at the Shack.  I just can't think of any rational reason to roll up a flat cable that way.
-- 
Ward Griffiths        wdg3rd at comcast.net

----- "Tim Fadden" <t.fadden at cox.net> wrote:

> From: "Tim Fadden" <t.fadden at cox.net>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Sunday, March 8, 2009 11:39:26 AM GMT -05:00 US/Canada Eastern
> Subject: Re: [Coco] FD-50X Drive manuals
>
> Don't know about ALL of the models, but the latest 502's come with
> ROUND 
> cables.  Unless you are pulling my leg.   They are actually  flat
> cables 
> put into a grey ROUND sleave. If you want a picture I can send it.
> 
> Tim
> 
> wdg3rd at comcast.net wrote:
> > ----- "Tim Fadden" <t.fadden at cox.net> wrote:
> >
> >
> >   
> >> This looks more like sticky head rails.
> >>
> >> Just for general  purposes, on all of the card edge connectors,
> dirves
> >>
> >> and controllers. Us a pencil erasor on the contacts and buff them
> up 
> >> pretty!
> >> Then do the clean/lube proceedure on the drives.  I be you will
> get
> >> them 
> >> working.
> >>
> >> The round cable is most likely the stock tandy cable.  The flat
> ribbon
> >> cable is most likely home made.  If you only have 1 drive on the
> >> system 
> >> It should make no difference which cable you use as long as you
> put
> >> the 
> >> drive on the end of the cable.  Tandy drives all come set as drive
> 1. 
> >>
> >> The fiddle with the cable to make the drive select different.
> >>     
> >
> > To the best of my knowledge (which used to be pretty exhaustive, but
> in a couple of decades a lot of brain cells die, and I have habits
> that help that process), Tandy never made a round floppy cable -- it
> was just ribbon.  Mod 1/3/4 FD and HD, Mod 2/12/16/6k FD and HD, Coco
> FD and HD, Tandy 2000 and early PC compatibles external HD.  All
> ribbons.  (My knowledge may be incomplete, as I left the company in
> 1986 and they didn't completely stop manufacturing computer products
> until five or six more years later, so some round cables may have
> snuck in while I wasn't watching, but I doubt it, they cost more and
> the Shack was always went for the cheap).  (Connecting the ends of
> round cables to _anything_ is labor intensive, which makes them
> expensive and is one of the reasons land lines cost so much).



From Torsten at Dittel.info  Sun Mar  8 13:08:58 2009
From: Torsten at Dittel.info (Torsten Dittel)
Date: Sun, 08 Mar 2009 18:08:58 +0100
Subject: [Coco] Model No. 26-3127B motherboard
In-Reply-To: <003d01c99f6d$454a7910$0701a8c0@master>
References: <010201c99ee4$ff31b6b0$fd952410$@rr.com><010401c99ee6$c202a630$4607f290$@rr.com><49B29CD4.1040002@gmail.com><4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3A@fenestra.lamunet.local>	<9D6350E28F76415E88CD5E094D8F2449@speedy>
	<003d01c99f6d$454a7910$0701a8c0@master>
Message-ID: <gp0u32$77u$1@ger.gmane.org>

Picture of the Tandy "64K Satelite Board" as found here in Europe in the 
64K lowercase CoCo2B (with "TANDY 64K Color Computer" plate):

http://dittel.org/CoCo/RAM.jpg

Cheers,
Torsten



From Torsten at Dittel.info  Sun Mar  8 13:21:37 2009
From: Torsten at Dittel.info (Torsten Dittel)
Date: Sun, 08 Mar 2009 18:21:37 +0100
Subject: [Coco] Model No. 26-3127B motherboard
In-Reply-To: <gp0u32$77u$1@ger.gmane.org>
References: <010201c99ee4$ff31b6b0$fd952410$@rr.com><010401c99ee6$c202a630$4607f290$@rr.com><49B29CD4.1040002@gmail.com><4C8EB9FD6963BD4C8BA6B0B60FE8E4DD058D3A@fenestra.lamunet.local>	<9D6350E28F76415E88CD5E094D8F2449@speedy>	<003d01c99f6d$454a7910$0701a8c0@master>
	<gp0u32$77u$1@ger.gmane.org>
Message-ID: <gp0ur0$b7f$1@ger.gmane.org>

> Picture of the Tandy "64K Satelite Board" as found here in Europe in the 
> 64K lowercase CoCo2B (with "TANDY 64K Color Computer" plate):
> 
> http://dittel.org/CoCo/RAM.jpg

Now I remember the ICs originally weren't socketed as shown in the 
picture. There was a bad RAM chip on the board when we got that non 
working CoCo from our local (Cologne) Tandy computer store for free, so 
my father did replace the original chips by sockets and maybe even a new 
set of RAMs. Already the garbage on the screen revealed the T1 lowercase 
VDG, because of the slightly different "0". I guess the PAL 2B was never 
really sold in Germany (that single one was demo system), because a few 
weeks later Tandy decided to close all shops in Germany and removed the 
CoCo from the shops in Belgium & the Netherlands. No idea about UK, but 
that system was slightly different anyway (different PAL modulator, 
different AC powerline connector). That's why the PAL CoCo3 (as sold in 
Australia) never made it to Europe (even not to the UK).

Torsten



From cwgordon at carolina.rr.com  Sun Mar  8 15:15:05 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 8 Mar 2009 14:15:05 -0500
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <F0EF66D23A0B489E8CFB9B49BADB1835@speedy>
References: <127395783.23341236520602550.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
	<F0EF66D23A0B489E8CFB9B49BADB1835@speedy>
Message-ID: <000401c9a022$30c10c60$92432520$@rr.com>

Correct, thank you. I should have put the round cable reference in quotes to
set it off.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Bruce W. Calkins
> Sent: Sunday, March 08, 2009 9:28 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] FD-50X Drive manuals
> 
> > To the best of my knowledge (which used to
> > be pretty exhaustive, but in a couple of decades
> > a lot of brain cells die, and I have habits that
> > help that process), Tandy never made a round
> > floppy cable -- it was just ribbon.
> 
> 
> 
> The FD-502 used a ribbon cable bound with a round sheath.
> This may be the confusion.
> 



From goosey at virgo.sdc.org  Sun Mar  8 16:05:10 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Sun, 8 Mar 2009 14:05:10 -0600
Subject: [Coco] Amusing set of error messages (can you see whats wrong?)
In-Reply-To: <008701c99fcf$a3c4cc40$6401a8c0@OLDGEORGE>
References: <20090308072917.GB9480@virgo.sdc.org>
	<008701c99fcf$a3c4cc40$6401a8c0@OLDGEORGE>
Message-ID: <20090308200510.GA16035@virgo.sdc.org>

On Sun, Mar 08, 2009 at 03:24:10AM -0600, George Ramsower wrote:
> (Tongue in cheek) .... It appears to me that this just flat out won't work 
> on a coco. 

Not yet, anyway.  Once we have a tcp/ip stack, some sort of shared
disk is the next item on the wish list. ;-)

> Must try pressing the reset button and wait a few milliseconds 
> and it will begin to work.

Take another look... it was time to reset my brain, obviously. :-)

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From goosey at virgo.sdc.org  Sun Mar  8 16:08:58 2009
From: goosey at virgo.sdc.org (Willard Goosey)
Date: Sun, 8 Mar 2009 14:08:58 -0600
Subject: [Coco] Amusing set of error messages (can you see whats wrong?)
In-Reply-To: <200903081006.13767.gene.heskett@verizon.net>
References: <20090308072917.GB9480@virgo.sdc.org>
	<200903081006.13767.gene.heskett@verizon.net>
Message-ID: <20090308200858.GB16035@virgo.sdc.org>

On Sun, Mar 08, 2009 at 09:06:13AM -0500, Gene Heskett wrote:
> On Sunday 08 March 2009, Willard Goosey wrote:
> >skywarp:~$ mount /home/goosey/brawl
> >Password:
> >smbmnt must be installed suid root for direct user mounts (501,501)
> Who is 501?

Me. :-)

> >smbmnt failed: 1
> >skywarp:~$ which smbmount
> >/usr/bin/smbmount
> >skywarp:~$ su
> >Password:
> >skywarp:/home/goosey# cd /usr/bin
> >skywarp:/usr/bin# chmod +s smbmount
> >skywarp:/usr/bin# ll smbmount
> > 484 -rwsr-sr-x    1 root     bin        489492 Apr  7  2003 smbmount
> >skywarp:/usr/bin# exit
> >skywarp:~$ mount /home/goosey/brawl
> >libsmb based programs must *NOT* be setuid root.
> >5817: Connection to brawl failed
> >SMB connection failed
> 
> This disk is on a different machine where you _were_ user 501?

Sorry, you missed the same thing I missed the first time I went
through this.  It was definetely bedtime. :-)  Look again.  What did I
do wrong?  

Willard
-- 
Willard Goosey  goosey at sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard


From boisy at tee-boy.com  Sun Mar  8 18:28:14 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Sun, 8 Mar 2009 17:28:14 -0500
Subject: [Coco] DriveWire 3 Updates
Message-ID: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>

This afternoon I posted new updates to Cloud-9's DriveWire product page:

- All HDB-DOS ROMs are available: CoCo 1 at 38400, CoCo 2 at 57600 and  
CoCo 3 at 115200bps.  They are now all in one zip file on the page
- All NitrOS-9 disk images are available in one zip file:
     - NitrOS-9/6809 Level 1 for CoCo1 at 38400
     - NitrOS-9/6809 Level 2 for CoCo 2 at 57600
     - NitrOS-9/6809 Level 2 for CoCo 3 at 115200
     - NitrOS-9/6309 Level 2 for CoCo 3 at 115200
- Updated servers for Windows and Mac are also posted, so grab them.

Printing is now supported under NitrOS-9 by sending data to the /p  
device (tied to the scdwp driver).  Both servers handle printing.

Also, DriveWire 3 is now officially part of the NitrOS-9 Project.  The  
source is available for your perusal.

I am open to discussing how we can do nightly builds of the project to  
insure updates come in on a timely fashion.

Have fun with it this stuff.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From boisy at tee-boy.com  Sun Mar  8 20:32:48 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Sun, 8 Mar 2009 19:32:48 -0500
Subject: [Coco] Giving Credit..
Message-ID: <DD7B2305-8140-4E3C-9357-31FBEC6CE7DC@tee-boy.com>

In my posts, I forgot to mention that DriveWire 3 uses Darren  
Atkinson's 38.4/57.6/115.2K bitbanger routines.  I want to thank  
Darren publicly for his willingness to let his work go into DriveWire 3.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From robert.gault at worldnet.att.net  Sun Mar  8 20:56:48 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Sun, 08 Mar 2009 20:56:48 -0400
Subject: [Coco] Giving Credit..
In-Reply-To: <DD7B2305-8140-4E3C-9357-31FBEC6CE7DC@tee-boy.com>
References: <DD7B2305-8140-4E3C-9357-31FBEC6CE7DC@tee-boy.com>
Message-ID: <49B46950.9030901@worldnet.att.net>

Boisy Pitre wrote:
> In my posts, I forgot to mention that DriveWire 3 uses Darren Atkinson's 
> 38.4/57.6/115.2K bitbanger routines.  I want to thank Darren publicly 
> for his willingness to let his work go into DriveWire 3.
> 
> Regards,
> Boisy G. Pitre
> -- 

Three cheers for Darren. Hip hip hooray! etc. :)


From gene.heskett at verizon.net  Sun Mar  8 21:09:53 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sun, 08 Mar 2009 21:09:53 -0400
Subject: [Coco] Amusing set of error messages (can you see whats wrong?)
In-Reply-To: <20090308200858.GB16035@virgo.sdc.org>
References: <20090308072917.GB9480@virgo.sdc.org>
	<200903081006.13767.gene.heskett@verizon.net>
	<20090308200858.GB16035@virgo.sdc.org>
Message-ID: <200903082109.53376.gene.heskett@verizon.net>

On Sunday 08 March 2009, Willard Goosey wrote:
>On Sun, Mar 08, 2009 at 09:06:13AM -0500, Gene Heskett wrote:
>> On Sunday 08 March 2009, Willard Goosey wrote:
>> >skywarp:~$ mount /home/goosey/brawl
>> >Password:
>> >smbmnt must be installed suid root for direct user mounts (501,501)
>>
>> Who is 501?
>
>Me. :-)
>
Not in the passwd file you aren't, or it would have identified you.  That is 
what prompted me to ask.  Once you have gained root access, I would change the 
ownership to you as a user.

>> >smbmnt failed: 1
>> >skywarp:~$ which smbmount
>> >/usr/bin/smbmount
>> >skywarp:~$ su
>> >Password:
>> >skywarp:/home/goosey# cd /usr/bin
>> >skywarp:/usr/bin# chmod +s smbmount
>> >skywarp:/usr/bin# ll smbmount
>> > 484 -rwsr-sr-x    1 root     bin        489492 Apr  7  2003 smbmount
>> >skywarp:/usr/bin# exit
>> >skywarp:~$ mount /home/goosey/brawl
>> >libsmb based programs must *NOT* be setuid root.
>> >5817: Connection to brawl failed
>> >SMB connection failed
>>
>> This disk is on a different machine where you _were_ user 501?
>
>Sorry, you missed the same thing I missed the first time I went
>through this.  It was definetely bedtime. :-)  Look again.  What did I
>do wrong?

The only thing I'm seeing other than you didn't do an 'su -', is that that 
copy of smbmount is struggling around on crutches and about to expire from old 
age.  Don't you ever update that linux box?

For starters, smbmount has been deprecated for quite a while, mount having 
gained the ability to detect and mount a modern cifs file system completely 
automatically.

Quite a few security holes have been plugged with the newer samba installs, so 
since that copy is 6 years old, please upgrade if for no other reason than to 
bring it truly into compliance with the M$ cifs file system.

>Willard


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Fortune's Real-Life Courtroom Quote #52:

Q:  What is your name?
A:  Ernestine McDowell.
Q:  And what is your marital status?
A:  Fair.



From chawks at dls.net  Sun Mar  8 21:17:20 2009
From: chawks at dls.net (Christopher Hawks)
Date: Sun, 08 Mar 2009 20:17:20 -0500
Subject: [Coco] DriveWire 3 Updates
In-Reply-To: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
References: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
Message-ID: <49B46E20.70802@dls.net>

Boisy Pitre said the following on 03/08/2009 05:28 PM:
> This afternoon I posted new updates to Cloud-9's DriveWire product page:
> 
> - All HDB-DOS ROMs are available: CoCo 1 at 38400, CoCo 2 at 57600 and 
> CoCo 3 at 115200bps.  They are now all in one zip file on the page
> - All NitrOS-9 disk images are available in one zip file:
>     - NitrOS-9/6809 Level 1 for CoCo1 at 38400
>     - NitrOS-9/6809 Level 2 for CoCo 2 at 57600
>     - NitrOS-9/6809 Level 2 for CoCo 3 at 115200
>     - NitrOS-9/6309 Level 2 for CoCo 3 at 115200
> - Updated servers for Windows and Mac are also posted, so grab them.
> 
> Printing is now supported under NitrOS-9 by sending data to the /p 
> device (tied to the scdwp driver).  Both servers handle printing.
> 
> Also, DriveWire 3 is now officially part of the NitrOS-9 Project.  The 
> source is available for your perusal.
> 
> I am open to discussing how we can do nightly builds of the project to 
> insure updates come in on a timely fashion.
> 
> Have fun with it this stuff.

    Great Stuff!!! Thanks Boisy!!! I'm still gonna get in line...

-- 
Christopher R. Hawks
HAWKSoft
---------------------------------------------------------
'using Outlook is like hanging a sign on your back that reads "PLEASE MESS
WITH MY COMPUTER."'
	-- Scott Rosenberg


From cwgordon at carolina.rr.com  Sun Mar  8 22:17:43 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 8 Mar 2009 21:17:43 -0500
Subject: [Coco] Floppy disks
In-Reply-To: <000001c99ff0$b0e8bd20$12ba3760$@rr.com>
References: <000001c99ff0$b0e8bd20$12ba3760$@rr.com>
Message-ID: <001a01c9a05d$3b0ed400$b12c7c00$@rr.com>

Nope, the kids working there had never even seen any.

Does anyone have 1 or two they could spare? The more the merrier.

Thanks...

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Bill
> Sent: Sunday, March 08, 2009 8:21 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: [Coco] Floppy disks
> 
> Please refresh my memory. Will plain old double-sided, double density
> disks
> work? I might be able to get some from my local Office Depot
> (hopefully).
> 



From t.fadden at cox.net  Sun Mar  8 21:23:19 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Sun, 08 Mar 2009 18:23:19 -0700
Subject: [Coco] Floppy disks
In-Reply-To: <001a01c9a05d$3b0ed400$b12c7c00$@rr.com>
References: <000001c99ff0$b0e8bd20$12ba3760$@rr.com>
	<001a01c9a05d$3b0ed400$b12c7c00$@rr.com>
Message-ID: <49B46F87.4080707@cox.net>

Here ya go.

http://www.pricebat.ca/VERBATIM-FLOPPY-DISK-2S2D-IBM-FMT.p_102350/
http://www.ioffer.com/i/Scotch-Floppy-Disk-EG-2S2D-RH-10-Pack-5-1-4-Disk-New-30705596
http://ca.pricespider.com/online-store-deal/1319254/Verbatim-FLOPPY-DISK-2S2D-IBM-FMT-SUPLDATALIFEPLUS-10PK-online-store-deal-87644.html
http://www.ecrater.com/product.php?pid=1516960









Bill wrote:
> Nope, the kids working there had never even seen any.
>
> Does anyone have 1 or two they could spare? The more the merrier.
>
> Thanks...
>
>   
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Bill
>> Sent: Sunday, March 08, 2009 8:21 AM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: [Coco] Floppy disks
>>
>> Please refresh my memory. Will plain old double-sided, double density
>> disks
>> work? I might be able to get some from my local Office Depot
>> (hopefully).
>>
>>     
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From exwn8jef at gmail.com  Sun Mar  8 21:27:50 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Sun, 08 Mar 2009 21:27:50 -0400
Subject: [Coco] Motherboard Identification
In-Reply-To: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
References: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
Message-ID: <49B47096.7090905@gmail.com>

Howdy Folks,
Bill and I have been discussing CoCo motherboards. I am making a 
spreadsheet of all the different CoCo motherboards produced over the 
years. Does anyone have any motherboard identification information to 
share with the group?

For example:

Model No.       Silkscreen ID on Motherboard
-----------        -------------------------------
26-3334           20261087
26-3127B         20261043
26-3127B         20261044
26-3134B         20261058
26-3127            250087 or 8709416 REV B or DWG NO 1700235

I am finding this a little confusing. :)

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home




From cwgordon at carolina.rr.com  Sun Mar  8 22:37:11 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Sun, 8 Mar 2009 21:37:11 -0500
Subject: [Coco] Motherboard Identification
In-Reply-To: <49B47096.7090905@gmail.com>
References: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
	<49B47096.7090905@gmail.com>
Message-ID: <001c01c9a05f$f3508ed0$d9f1ac70$@rr.com>

You forgot to punch in my 20261058 for the 27B

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of N8WQ
> Sent: Sunday, March 08, 2009 8:28 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: [Coco] Motherboard Identification
>
> Does anyone have any motherboard identification information to
> share with the group?
> 



From exwn8jef at gmail.com  Sun Mar  8 21:44:41 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Sun, 08 Mar 2009 21:44:41 -0400
Subject: [Coco] Motherboard Identification
In-Reply-To: <001c01c9a05f$f3508ed0$d9f1ac70$@rr.com>
References: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>	<49B47096.7090905@gmail.com>
	<001c01c9a05f$f3508ed0$d9f1ac70$@rr.com>
Message-ID: <49B47489.2040204@gmail.com>

thanks Bill

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



Bill wrote:
> You forgot to punch in my 20261058 for the 27B
>
>   
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of N8WQ
>> Sent: Sunday, March 08, 2009 8:28 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: [Coco] Motherboard Identification
>>
>> Does anyone have any motherboard identification information to
>> share with the group?
>>
>>     
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>   


From devries.bob at gmail.com  Sun Mar  8 21:54:51 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Mon, 9 Mar 2009 11:54:51 +1000
Subject: [Coco] Motherboard Identification
References: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
	<49B47096.7090905@gmail.com>
Message-ID: <007301c9a05a$0c6e0f10$0701a8c0@master>

My Aussie Coco3 (26-3334) is #20261091

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "N8WQ" <exwn8jef at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Monday, March 09, 2009 11:27 AM
Subject: [Coco] Motherboard Identification


> Howdy Folks,
> Bill and I have been discussing CoCo motherboards. I am making a 
> spreadsheet of all the different CoCo motherboards produced over the 
> years. Does anyone have any motherboard identification information to 
> share with the group?
> 
> For example:
> 
> Model No.       Silkscreen ID on Motherboard
> -----------        -------------------------------
> 26-3334           20261087
> 26-3127B         20261043
> 26-3127B         20261044
> 26-3134B         20261058
> 26-3127            250087 or 8709416 REV B or DWG NO 1700235
> 
> I am finding this a little confusing. :)
> 
> Alan Jones
> 
> -- 
> N8WQ - Canal Winchester, Ohio
> http://exwn8jef.googlepages.com/home
> 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


From cocomongrel at googlemail.com  Sun Mar  8 21:55:32 2009
From: cocomongrel at googlemail.com (CoCo Mongrel)
Date: Sun, 8 Mar 2009 19:55:32 -0600
Subject: [Coco] Underscore in Filename in DECB
Message-ID: <bf35da7d0903081855n425c01d7x719cce07d744d899@mail.gmail.com>

OK doggonnit,

I've got some files in DECB that have what I think are stand-ins for the
underscore character.  They appear as a right-pointing arrow [ <- (but a
single character)].  I can't remember how to produce this character on the
CoCo 3 keyboard in DECB.  You can get it with <alt><-> in TW128.  But I want
to type this at the DECB command prompt.  A <shift><[down-arrow]> produces
the character on the screen, but also apparently a carriage return.  And
though it appears the same on the screen, I'm not sure it's the same
character...

cocomongrel


From cocomongrel at googlemail.com  Sun Mar  8 22:05:36 2009
From: cocomongrel at googlemail.com (CoCo Mongrel)
Date: Sun, 8 Mar 2009 20:05:36 -0600
Subject: [Coco] Underscore in Filename in DECB
Message-ID: <bf35da7d0903081905n1886ab4btd8e8b8fabddffbab@mail.gmail.com>

I think I figured it out.  HDB-DOS' FlexiKey feature was hiding it.  Hit
<shift><clear> first, then the <shift><[arrow key]> combination...

cocomongrel


From coconutcowboy2002 at yahoo.com  Sun Mar  8 21:22:17 2009
From: coconutcowboy2002 at yahoo.com (sean ross)
Date: Sun, 8 Mar 2009 18:22:17 -0700 (PDT)
Subject: [Coco] [Color Computer] Re: looking for speech sound module
In-Reply-To: <goqo71+ig5t@eGroups.com>
Message-ID: <196601.64901.qm@web55903.mail.re3.yahoo.com>

Sorry it took so long,
yes i am how much?

--- On Fri, 3/6/09, Robert <rgtryner at yahoo.com> wrote:

From: Robert <rgtryner at yahoo.com>
Subject: [Color Computer] Re: looking for speech sound module
To: ColorComputer at yahoogroups.com
Date: Friday, March 6, 2009, 3:51 AM






--- In ColorComputer@ yahoogroups. com, "coconutcowboy2002" <coconutcowboy2002@ ...> wrote:
>
> I am looking for a speech sound module, I am willing to pay the price 
> of a good clean one with manual.
> thanks
>
Are you still looking for a SSC? If so, I'll check my storage, I think I have one.

















      


From robert.gault at worldnet.att.net  Sun Mar  8 22:19:54 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Sun, 08 Mar 2009 22:19:54 -0400
Subject: [Coco] Underscore in Filename in DECB
In-Reply-To: <bf35da7d0903081855n425c01d7x719cce07d744d899@mail.gmail.com>
References: <bf35da7d0903081855n425c01d7x719cce07d744d899@mail.gmail.com>
Message-ID: <49B47CCA.5060805@worldnet.att.net>

CoCo Mongrel wrote:
> OK doggonnit,
> 
> I've got some files in DECB that have what I think are stand-ins for the
> underscore character.  They appear as a right-pointing arrow [ <- (but a
> single character)].  I can't remember how to produce this character on the
> CoCo 3 keyboard in DECB.  You can get it with <alt><-> in TW128.  But I want
> to type this at the DECB command prompt.  A <shift><[down-arrow]> produces
> the character on the screen, but also apparently a carriage return.  And
> though it appears the same on the screen, I'm not sure it's the same
> character...
> 
> cocomongrel
> 

There is no right pointing arrow produced by the ROMs. There is a left 
pointing arrow <- which is what you drew in your question.
SHIFT up-arrow will produce  <-  on the screen from Basic.
The only other arrow is the up-arrow produced by the up-arrow key.


From operator at coco3.com  Sun Mar  8 22:22:50 2009
From: operator at coco3.com (Roger Taylor)
Date: Sun, 08 Mar 2009 21:22:50 -0500
Subject: [Coco] Other features of the bluetooth RS-232 Pak
Message-ID: <20090309022336.0D1C420A13@qs281.pair.com>


Here's a little early tutorial for those who might possibly want a 
second bluetooth pak now or later.

Two CoCo's can connect to each other automatically over the air just 
like there's a null-modem cable connected.

It's called EasyConnect.  No surprise, but any 6551-based software or 
operating system is already compatible.  NitrOS-9, OS-9, Disk 
BASIC.  No software drivers are needed.  And best of all, no smoke and mirrors.

To program 2 CoCo's to link with each other automatically now and in 
the future, just do this EASY procedure once:

1) Power up each CoCo while holding down the CoCo Reset button. As 
soon as you see the LED come on (1/2 second), let off the Reset button.
2) On ONE of the CoCo's, tap the Reset button.

Done.  No need to do it again.  The paks will retain their bluetooth 
settings when the power is off.  The two 6551 chips are wirelessly 
connected to each other.

How do you know it worked?  Every 2 seconds, both CoCo's will flash 
their LEDs at the same time.

To remove EasyConnect mode or set the bluetooth module back to a 9600 
bps connection, perform the simple Reset procedure:

Resetting the bluetooth settings to factory defaults:

1) Hold down the CoCo reset button while powering up
2) after about 1.5 seconds the LED will go off
3) release the Reset button.
The pak is reset.
-- 
Roger Taylor

http://www.wordofthedayonline.com



From mmarlette at frontiernet.net  Sun Mar  8 22:25:22 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Mon, 9 Mar 2009 02:25:22 +0000 (UTC)
Subject: [Coco] Giving Credit..
In-Reply-To: <DD7B2305-8140-4E3C-9357-31FBEC6CE7DC@tee-boy.com>
Message-ID: <134514712.155231236565522678.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>


As always, GREAT work Darren!!!!

Thanks!

Mark
Cloud-9


----- Original Message -----
From: "Boisy Pitre" <boisy at tee-boy.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Sunday, March 8, 2009 7:32:48 PM GMT -06:00 US/Canada Central
Subject: [Coco] Giving Credit..

In my posts, I forgot to mention that DriveWire 3 uses Darren  
Atkinson's 38.4/57.6/115.2K bitbanger routines.  I want to thank  
Darren publicly for his willingness to let his work go into DriveWire 3.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From mdelyea at gmail.com  Mon Mar  9 07:27:03 2009
From: mdelyea at gmail.com (mike delyea)
Date: Mon, 9 Mar 2009 07:27:03 -0400
Subject: [Coco] Underscore in Filename in DECB
In-Reply-To: <49B47CCA.5060805@worldnet.att.net>
References: <bf35da7d0903081855n425c01d7x719cce07d744d899@mail.gmail.com>
	<49B47CCA.5060805@worldnet.att.net>
Message-ID: <1b52e6c80903090427j9c6fd70n4efc5af5a9495bcc@mail.gmail.com>

Also, isn't it possible that the filename could have been produced by
a string of ASCII characters?  Something like
NA$=CHR$(BLAH)+CHR$(BLAH)+CHR$(LEFT ARROW)+CHR$(BLAH), then OPENed for
output.

On Sun, Mar 8, 2009 at 10:19 PM, Robert Gault
<robert.gault at worldnet.att.net> wrote:
> CoCo Mongrel wrote:
>>
>> OK doggonnit,
>>
>> I've got some files in DECB that have what I think are stand-ins for the
>> underscore character. ?They appear as a right-pointing arrow [ <- (but a
>> single character)]. ?I can't remember how to produce this character on the
>> CoCo 3 keyboard in DECB. ?You can get it with <alt><-> in TW128. ?But I
>> want
>> to type this at the DECB command prompt. ?A <shift><[down-arrow]> produces
>> the character on the screen, but also apparently a carriage return. ?And
>> though it appears the same on the screen, I'm not sure it's the same
>> character...
>>
>> cocomongrel
>>
>
> There is no right pointing arrow produced by the ROMs. There is a left
> pointing arrow <- which is what you drew in your question.
> SHIFT up-arrow will produce ?<- ?on the screen from Basic.
> The only other arrow is the up-arrow produced by the up-arrow key.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From cocomongrel at googlemail.com  Mon Mar  9 10:45:26 2009
From: cocomongrel at googlemail.com (CoCo Mongrel)
Date: Mon, 9 Mar 2009 08:45:26 -0600
Subject: [Coco] Underscore in Filename in DECB
In-Reply-To: <49B47CCA.5060805@worldnet.att.net>
References: <bf35da7d0903081855n425c01d7x719cce07d744d899@mail.gmail.com>
	<49B47CCA.5060805@worldnet.att.net>
Message-ID: <bf35da7d0903090745h511484bhfa203245f62483@mail.gmail.com>

lfet, rghit, waht's the difference?  :)

On Sun, Mar 8, 2009 at 8:19 PM, Robert Gault
<robert.gault at worldnet.att.net>wrote:

> CoCo Mongrel wrote:
>
>> OK doggonnit,
>>
>> I've got some files in DECB that have what I think are stand-ins for the
>> underscore character.  They appear as a right-pointing arrow [ <- (but a
>> single character)].  I can't remember how to produce this character on the
>> CoCo 3 keyboard in DECB.  You can get it with <alt><-> in TW128.  But I
>> want
>> to type this at the DECB command prompt.  A <shift><[down-arrow]> produces
>> the character on the screen, but also apparently a carriage return.  And
>> though it appears the same on the screen, I'm not sure it's the same
>> character...
>>
>> cocomongrel
>>
>>
> There is no right pointing arrow produced by the ROMs. There is a left
> pointing arrow <- which is what you drew in your question.
> SHIFT up-arrow will produce  <-  on the screen from Basic.
> The only other arrow is the up-arrow produced by the up-arrow key.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From robert.gault at worldnet.att.net  Mon Mar  9 11:15:33 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Mon, 09 Mar 2009 11:15:33 -0400
Subject: [Coco] Underscore in Filename in DECB
In-Reply-To: <1b52e6c80903090427j9c6fd70n4efc5af5a9495bcc@mail.gmail.com>
References: <bf35da7d0903081855n425c01d7x719cce07d744d899@mail.gmail.com>	<49B47CCA.5060805@worldnet.att.net>
	<1b52e6c80903090427j9c6fd70n4efc5af5a9495bcc@mail.gmail.com>
Message-ID: <49B53295.806@worldnet.att.net>

mike delyea wrote:
> Also, isn't it possible that the filename could have been produced by
> a string of ASCII characters?  Something like
> NA$=CHR$(BLAH)+CHR$(BLAH)+CHR$(LEFT ARROW)+CHR$(BLAH), then OPENed for
> output.
> 
> On Sun, Mar 8, 2009 at 10:19 PM, Robert Gault
> <robert.gault at worldnet.att.net> wrote:
>> CoCo Mongrel wrote:
>>> OK doggonnit,
>>>
>>> I've got some files in DECB that have what I think are stand-ins for the
>>> underscore character.  They appear as a right-pointing arrow [ <- (but a
>>> single character)].  I can't remember how to produce this character on the
>>> CoCo 3 keyboard in DECB.  You can get it with <alt><-> in TW128.  But I
>>> want
>>> to type this at the DECB command prompt.  A <shift><[down-arrow]> produces
>>> the character on the screen, but also apparently a carriage return.  And
>>> though it appears the same on the screen, I'm not sure it's the same
>>> character...
>>>
>>> cocomongrel
>>>
>> There is no right pointing arrow produced by the ROMs. There is a left
>> pointing arrow <- which is what you drew in your question.
>> SHIFT up-arrow will produce  <-  on the screen from Basic.
>> The only other arrow is the up-arrow produced by the up-arrow key.
>>

A string like that can only produce characters stored in the Coco ROM or 
video chip. It would be different if you were running a graphics program 
that displayed characters internal to the program. Then you could 
display almost anything.

If you can find some CHR$ string that prints -> as a single character 
instead of a minus sign - and then the > sign, please post it. That was 
the request of the OP.


From mdelyea at gmail.com  Mon Mar  9 11:40:02 2009
From: mdelyea at gmail.com (mike delyea)
Date: Mon, 9 Mar 2009 11:40:02 -0400
Subject: [Coco] Underscore in Filename in DECB
In-Reply-To: <49B53295.806@worldnet.att.net>
References: <bf35da7d0903081855n425c01d7x719cce07d744d899@mail.gmail.com>
	<49B47CCA.5060805@worldnet.att.net>
	<1b52e6c80903090427j9c6fd70n4efc5af5a9495bcc@mail.gmail.com>
	<49B53295.806@worldnet.att.net>
Message-ID: <1b52e6c80903090840r25ac344ai66d307d851cb78c1@mail.gmail.com>

CHR$(95) is a left pointing arrow complete with tail.  The original
message said right pointing but had a "<-" as the example.



On Mon, Mar 9, 2009 at 11:15 AM, Robert Gault
<robert.gault at worldnet.att.net> wrote:
> mike delyea wrote:
>>
>> Also, isn't it possible that the filename could have been produced by
>> a string of ASCII characters? ?Something like
>> NA$=CHR$(BLAH)+CHR$(BLAH)+CHR$(LEFT ARROW)+CHR$(BLAH), then OPENed for
>> output.
>>
>> On Sun, Mar 8, 2009 at 10:19 PM, Robert Gault
>> <robert.gault at worldnet.att.net> wrote:
>>>
>>> CoCo Mongrel wrote:
>>>>
>>>> OK doggonnit,
>>>>
>>>> I've got some files in DECB that have what I think are stand-ins for the
>>>> underscore character. ?They appear as a right-pointing arrow [ <- (but a
>>>> single character)]. ?I can't remember how to produce this character on
>>>> the
>>>> CoCo 3 keyboard in DECB. ?You can get it with <alt><-> in TW128. ?But I
>>>> want
>>>> to type this at the DECB command prompt. ?A <shift><[down-arrow]>
>>>> produces
>>>> the character on the screen, but also apparently a carriage return. ?And
>>>> though it appears the same on the screen, I'm not sure it's the same
>>>> character...
>>>>
>>>> cocomongrel
>>>>
>>> There is no right pointing arrow produced by the ROMs. There is a left
>>> pointing arrow <- which is what you drew in your question.
>>> SHIFT up-arrow will produce ?<- ?on the screen from Basic.
>>> The only other arrow is the up-arrow produced by the up-arrow key.
>>>
>
> A string like that can only produce characters stored in the Coco ROM or
> video chip. It would be different if you were running a graphics program
> that displayed characters internal to the program. Then you could display
> almost anything.
>
> If you can find some CHR$ string that prints -> as a single character
> instead of a minus sign - and then the > sign, please post it. That was the
> request of the OP.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From dennis-ix at maltedmedia.com  Mon Mar  9 11:37:32 2009
From: dennis-ix at maltedmedia.com (Dennis Bathory-Kitsz)
Date: Mon, 09 Mar 2009 11:37:32 -0400
Subject: [Coco] Organizing FTP area
Message-ID: <200903091540.n29FekLX007428@tv-failover-01.trans-video.net>

Hi all,

Recently I've seen quite a few new items uploaded to 
ftp://maltedmedia.com/coco/

The pre-2009 stuff has been moved to the Unfiled_As_of_Yet directory, 
which is filling up. There's also a "VARIOUS" directory and numerous 
unhelpful subcategories. It's not terrible, but it's getting awkward 
and less than simple to find stuff.

It would be fantastic to have this better organized, as it's grown 
fairly large. After 2005, it got too much for me to keep up with, and 
I've received numerous suggestions on how I should re-organize it.

This isn't something that I really want to do myself.

So this is a request for ONE volunteer to help reorganize this FTP 
directory system. I'll give you unlimited FTP access (only FTP 
access) if you can work effectively with a Unix file system and are 
absolutely certain you won't screw it up.

Let me know OFF-LIST if you're interested and maybe how you would do 
it and the time frame. I'll then put those who contact me in touch 
with each other, and you can decide who would best lead the 'team' in 
doing it. Since I will be gone for a month as of March 22, I'd like 
to have it started before then.

This resource gets a lot of traffic, so it seems reasonable to fix it 
up in a useful way.

And PS to the list volunteers: During the time I'm gone, please check 
for new subscriptions and make sure they're real people.

Many thanks,
Dennis









Country Stores book!
<http://www.amazon.com/Country-Stores-Vermont-Dennis-Bathory-kitsz/dp/1596294752/>
Bathory Opera libretto!
<http://www.lulu.com/content/5649281>
"We Are All Mozart"
<http://maltedmedia.com/waam/>



From rcrislip at neo.rr.com  Mon Mar  9 12:15:19 2009
From: rcrislip at neo.rr.com (richec)
Date: Mon, 9 Mar 2009 12:15:19 -0400
Subject: [Coco] FD-50X Drive manuals
In-Reply-To: <49B3E6AE.8060004@cox.net>
References: <127395783.23341236520602550.JavaMail.root@sz0113a.westchester.pa.mail.comcast.net>
	<49B3E6AE.8060004@cox.net>
Message-ID: <200903091215.19770.rcrislip@neo.rr.com>

On Sunday 08 March 2009 11:39:26 Tim Fadden wrote:
> Don't know about ALL of the models, but the latest 502's come with ROUND
> cables.  Unless you are pulling my leg.   They are actually  flat cables
> put into a grey ROUND sleave. If you want a picture I can send it.
>
> Tim
>
> wdg3rd at comcast.net wrote:
> > ----- "Tim Fadden" <t.fadden at cox.net> wrote:
> >> This looks more like sticky head rails.
> >>
> >> Just for general  purposes, on all of the card edge connectors, dirves
> >>
> >> and controllers. Us a pencil erasor on the contacts and buff them up
> >> pretty!
> >> Then do the clean/lube proceedure on the drives.  I be you will get
> >> them
> >> working.
> >>
> >> The round cable is most likely the stock tandy cable.  The flat ribbon
> >> cable is most likely home made.  If you only have 1 drive on the
> >> system
> >> It should make no difference which cable you use as long as you put
> >> the
> >> drive on the end of the cable.  Tandy drives all come set as drive 1.
> >>
> >> The fiddle with the cable to make the drive select different.
> >
> > To the best of my knowledge (which used to be pretty exhaustive, but in a
> > couple of decades a lot of brain cells die, and I have habits that help
> > that process), Tandy never made a round floppy cable -- it was just
> > ribbon.  Mod 1/3/4 FD and HD, Mod 2/12/16/6k FD and HD, Coco FD and HD,
> > Tandy 2000 and early PC compatibles external HD.  All ribbons.  (My
> > knowledge may be incomplete, as I left the company in 1986 and they
> > didn't completely stop manufacturing computer products until five or six
> > more years later, so some round cables may have snuck in while I wasn't
> > watching, but I doubt it, they cost more and the Shack was always went
> > for the cheap).  (Connecting the ends of round cables to _anything_ is
> > labor intensive, which makes them expensive and is one of the reasons
> > land lines cost so much).
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco

Hello, for what it is worth, I have one of those beasts too. I thing I would 
have preferred the flat ribbon, the round one is not very flexible.


From boisy at tee-boy.com  Mon Mar  9 22:43:34 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Mon, 9 Mar 2009 21:43:34 -0500
Subject: [Coco] DriveWire WinServer source online
Message-ID: <240D5AA3-3521-4D7C-A8B8-39AAE8D46E34@tee-boy.com>

For those interested, I have added the source to the Windows version  
of the DriveWire server to the drivewireserver project at  
sourceforge.net.  The path to the site is http://sourceforge.net/projects/drivewireserver/ 
.

Borland Delphi 7 is needed to compile DriveWire WinServer.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From coconut at pritchard.ca  Tue Mar 10 00:10:01 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Mon, 9 Mar 2009 22:10:01 -0600
Subject: [Coco] DriveWire 3 Updates
In-Reply-To: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
References: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
Message-ID: <1806abd60903092110h42098c8bl35f6a549e1b20b16@mail.gmail.com>

<bow> Thank you kind sir (Boisy)!  </bow>
I could be wrong thinking I was the only CoCo 1 user pleading with you to
repost DriveWire 2 so that the CoCo 1 users out there could still have
access to your great product.  Yet here you go and add CoCo 1 support to
DriveWire 3, not to mention some printing support that someone else had
suggested.  And to top it off you are offering it free of charge to anyone
with their own ROM burning facilities.

I don't have ROM burning facilities myself but that is fine I have no
problem paying for the burnt ROM (and I presume a DOS Adapter because of my
FDC cartridge uses the 24pin ROM) or ROM cartridge, or choosing the SuperIDE
Interface and requesting you write the ROM to the first bank of Flash ROM on
the adapter since I don't have an MPI (heck if I choose the SuperIDE
Interface I should probably request you to burn the CoCo 1 DriveWire ROM to
bank 1, and the CoCo 2 ROM and CoCo 3 ROM to bank 2 and 3 respectively so
that if in the future I acquire different CoCo model I will already have the
ROMs ready to go - then again maybe I can write the other ROMs to those
banks myself since I would technically have that ability)

Anyway, just wanted to say cheers because of the latest development for
DriveWire.

On Sun, Mar 8, 2009 at 4:28 PM, Boisy Pitre <boisy at tee-boy.com> wrote:

> This afternoon I posted new updates to Cloud-9's DriveWire product page:
>
> - All HDB-DOS ROMs are available: CoCo 1 at 38400, CoCo 2 at 57600 and CoCo
> 3 at 115200bps.  They are now all in one zip file on the page
> - All NitrOS-9 disk images are available in one zip file:
>    - NitrOS-9/6809 Level 1 for CoCo1 at 38400
>    - NitrOS-9/6809 Level 2 for CoCo 2 at 57600
>    - NitrOS-9/6809 Level 2 for CoCo 3 at 115200
>    - NitrOS-9/6309 Level 2 for CoCo 3 at 115200
> - Updated servers for Windows and Mac are also posted, so grab them.
>
> Printing is now supported under NitrOS-9 by sending data to the /p device
> (tied to the scdwp driver).  Both servers handle printing.
>
> Also, DriveWire 3 is now officially part of the NitrOS-9 Project.  The
> source is available for your perusal.
>
> I am open to discussing how we can do nightly builds of the project to
> insure updates come in on a timely fashion.
>
> Have fun with it this stuff.
>
> Regards,
> Boisy G. Pitre
> --
> Tee-Boy
> Mobile: 337.781.3570
> Email: boisy at tee-boy.com
> Web: http://www.tee-boy.com
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From coconut at pritchard.ca  Tue Mar 10 01:00:16 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Mon, 9 Mar 2009 23:00:16 -0600
Subject: [Coco] Question regarding the Cloud9tech SuperIDE Interface.
Message-ID: <1806abd60903092200y2f3f9626k1c341fce0646cc0d@mail.gmail.com>

I know this is likely more directed to Boisy and Mark, but I figured I would
ask the CoCoList.
I have an Iomega 250MB ATAPI Zip drive, Model Z250ATAPI.  I am curious if
anyone has used the ATAPI Zip drives on the SuperIDE Interface.  I
know the TC^3
SCSI Controller pages says it supports the SCSI version of the Zip drives.

So anyone know if the ATAPI Zip works with the Super IDE Interface?

On another topic I just found eight 720K 3.5" diskettes amongst the numerous
1.44M diskettes I have.  Maybe I will have less reliability issues with my
3.5" drives going forward. =:vP

-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From boisy at tee-boy.com  Tue Mar 10 06:26:12 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Tue, 10 Mar 2009 05:26:12 -0500
Subject: [Coco] Question regarding the Cloud9tech SuperIDE Interface.
In-Reply-To: <1806abd60903092200y2f3f9626k1c341fce0646cc0d@mail.gmail.com>
References: <1806abd60903092200y2f3f9626k1c341fce0646cc0d@mail.gmail.com>
Message-ID: <86BEB40D-1470-4008-87DC-59FB7D5ADDF1@tee-boy.com>

On Mar 10, 2009, at 12:00 AM, Ryan Pritchard wrote:

> I know this is likely more directed to Boisy and Mark, but I figured  
> I would
> ask the CoCoList.
> I have an Iomega 250MB ATAPI Zip drive, Model Z250ATAPI.  I am  
> curious if
> anyone has used the ATAPI Zip drives on the SuperIDE Interface.  I
> know the TC^3
> SCSI Controller pages says it supports the SCSI version of the Zip  
> drives.
>
> So anyone know if the ATAPI Zip works with the Super IDE Interface?

Ryan,

NitrOS-9 does support ATAPI drives through the SuperDriver product.   
HDB-DOS does not have support for ATAPI drives, just ATA drives.


> On another topic I just found eight 720K 3.5" diskettes amongst the  
> numerous
> 1.44M diskettes I have.  Maybe I will have less reliability issues  
> with my
> 3.5" drives going forward. =:vP
>
> -- 
> Regards,
>
> Ryan Pritchard
> Fun Extends All Basic Life Expectancies
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From cwgordon at carolina.rr.com  Tue Mar 10 10:11:42 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Tue, 10 Mar 2009 09:11:42 -0500
Subject: [Coco] .dsk format
Message-ID: <001f01c9a18a$238d2060$6aa76120$@rr.com>

Pardon what may be a silly question, but can files saved in the .dsk format
be downloaded and put back on their original condition using a coco?

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From cwgordon at carolina.rr.com  Tue Mar 10 11:03:05 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Tue, 10 Mar 2009 10:03:05 -0500
Subject: [Coco] Coco to PC cable
Message-ID: <002001c9a191$51357ec0$f3a07c40$@rr.com>

What kind of cable would I need to copy files from my PC to my Coco?

Anybody got one??

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784





From dml_68 at yahoo.com  Tue Mar 10 10:10:53 2009
From: dml_68 at yahoo.com (Derek)
Date: Tue, 10 Mar 2009 07:10:53 -0700 (PDT)
Subject: [Coco] .dsk format
In-Reply-To: <001f01c9a18a$238d2060$6aa76120$@rr.com>
Message-ID: <112289.24291.qm@web30207.mail.mud.yahoo.com>

I do not know of a utility that runs on the coco end which will allow you to mount a .dsk image as a "real" disk.



Bill <cwgordon at carolina.rr.com> wrote: Pardon what may be a silly question, but can files saved in the .dsk format
be downloaded and put back on their original condition using a coco?

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784



--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



** Mistrust Authority. Promote Decentralization **


 


       


From robert.gault at worldnet.att.net  Tue Mar 10 10:42:53 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Tue, 10 Mar 2009 10:42:53 -0400
Subject: [Coco] .dsk format
In-Reply-To: <001f01c9a18a$238d2060$6aa76120$@rr.com>
References: <001f01c9a18a$238d2060$6aa76120$@rr.com>
Message-ID: <49B67C6D.9080309@worldnet.att.net>

Bill wrote:
> Pardon what may be a silly question, but can files saved in the .dsk format
> be downloaded and put back on their original condition using a coco?
> 

Theoretically that could be done. The problem is that the .dsk image is 
so large it won't fit on a floppy. If you have a hard drive system you 
might be able to do this running OS-9. If the .dsk image was a Disk 
Basic disk, you would need to create an OS-9 program to write sectors on 
a disk formatted for Basic.
If you can get around the above restrictions, you would write each 
sector of data from the .dsk image to the equivalent sector on a real 
floppy.

In short, it is just not worth the effort as it is so simple to create a 
real floppy from the .dsk file on a PC.


From gene.heskett at verizon.net  Tue Mar 10 10:48:58 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Tue, 10 Mar 2009 10:48:58 -0400
Subject: [Coco] .dsk format
In-Reply-To: <001f01c9a18a$238d2060$6aa76120$@rr.com>
References: <001f01c9a18a$238d2060$6aa76120$@rr.com>
Message-ID: <200903101048.58554.gene.heskett@verizon.net>

On Tuesday 10 March 2009, Bill wrote:
>Pardon what may be a silly question, but can files saved in the .dsk format
>be downloaded and put back on their original condition using a coco?

In nitros9/os9, one can rather quickly write a basic09 program to do that, the 
secret is to open  the write path to the disk in the whole disk mode, aka /d0@ 
or /d1@ etc, then copy the .dsk file to the disk, one 256 byte sector at a 
time until done.  Very simplified:

10 PROCEDURE WRTDISK
20 DIM BUFFER, 256 BYTE buffer storage 
30 DIM IPATH byte, OPATH byte
40 OPEN #IPATH,srcfilename
50 OPEN OPATH, /d0@
60 WHILE NOT(EOF, #IPATH) DO
70 READ #IPATH, BUFFER
80 WRITE #OPATH, BUFFER
90 ENDWHILE
100 CLOSE #IPATH, #OPATH
110 END

That is probably full of syntax errors because I haven't done that in years, 
but that is pretty close to the general outline of what it would take.

The coco's basic can do that too, but its default buffer size of 128 bytes 
means you need to allocate 2, and load both, then write both, using the dski 
and dsko syntax IIRC, where you have to handle in a 2 layer loop, the 
presetting and incrementing of the values you give the dski and dsko commands 
for the track and sector they need.  And I may not even have the right names 
for the dski and dsko stuff, mainly because I switched to os9 & never looked 
back about 2 months after getting my first old grey ghost coco all those years 
ago, just as soon as I could find 64k of ram to put in it.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"It's when they say 2 + 2 = 5 that I begin to argue."
-- Eric Pepke




From jcewy at swbell.net  Tue Mar 10 10:57:51 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Tue, 10 Mar 2009 09:57:51 -0500
Subject: [Coco] Coco to PC cable
In-Reply-To: <002001c9a191$51357ec0$f3a07c40$@rr.com>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
Message-ID: <49B67FEF.8050406@swbell.net>

Depends on how you want to do it. 

If you can burn an EPROM or buy a ROM pak from Cloud 9, you can use 
DriveWire.  The documentation for how to build a DriveWire cable is in 
the DriveWire 3  Specification document in the "Support" section of the 
Cloud 9 web site.  Or you could buy a cable from them.  I've just 
downloaded DriveWire 3, burned it onto an EPROM, soldered up a cable, 
and got it running.  It's very cool.  There are servers for MS-Windows, 
Linux, and MacOS X.

Roger Taylor has a program that will convert a file to an audio file 
which can be CLOADed into the CoCo's cassette port.  I think you can 
also produce such a file using a CoCo emulator running on a modern PC.  
Then you just need a CoCo cassette cable.  Roger also sells a ROM pak 
that contains a program similar to DriveWire, as well as a bluetooth 
wireless serial interface.

Or if you have an RS-232 interface of some kind, and can load a terminal 
program from tape or disk, you can use a null-modem serial cable.  The 
World Wide Web can help you here.  E.G.  
http://en.wikipedia.org/wiki/Null_modem

There are lots of ways to do what you're asking.

JCE

Bill wrote:
> What kind of cable would I need to copy files from my PC to my Coco?
>
> Anybody got one??
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>   



From operator at coco3.com  Tue Mar 10 12:18:16 2009
From: operator at coco3.com (Roger Taylor)
Date: Tue, 10 Mar 2009 11:18:16 -0500
Subject: [Coco] .dsk format
In-Reply-To: <112289.24291.qm@web30207.mail.mud.yahoo.com>
References: <001f01c9a18a$238d2060$6aa76120$@rr.com>
	<112289.24291.qm@web30207.mail.mud.yahoo.com>
Message-ID: <20090310161917.4786220A14@qs281.pair.com>

At 09:10 AM 3/10/2009, you wrote:
>I do not know of a utility that runs on the coco end which will 
>allow you to mount a .dsk image as a "real" disk.

Are you sure he's not wanting to know about DriveWire or CoCoNet?










>Bill <cwgordon at carolina.rr.com> wrote: Pardon what may be a silly 
>question, but can files saved in the .dsk format
>be downloaded and put back on their original condition using a coco?
>
>______________________________________
>*Square One Christian BBS
>Web access: http://www.sq1bbs.com/index.php
>Telnet access: telnet://sq1bbs.com
>
>A Taste of CoCo Forum
>http://www.sq1bbs.com/coco/index.php
>
>Live chat room - Ventrilo 3.x required
>Host name or IP: www.sq1bbs.com
>Port: 3784
>
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco
>
>
>
>** Mistrust Authority. Promote Decentralization **
>
>
>
>
>
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco

-- 
Roger Taylor

http://www.wordofthedayonline.com



From operator at coco3.com  Tue Mar 10 12:25:05 2009
From: operator at coco3.com (Roger Taylor)
Date: Tue, 10 Mar 2009 11:25:05 -0500
Subject: [Coco] Coco to PC cable
In-Reply-To: <49B67FEF.8050406@swbell.net>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
	<49B67FEF.8050406@swbell.net>
Message-ID: <20090310162545.30AF120A13@qs281.pair.com>

At 09:57 AM 3/10/2009, you wrote:
>Depends on how you want to do it.
>If you can burn an EPROM or buy a ROM pak from Cloud 9, you can use 
>DriveWire.  The documentation for how to build a DriveWire cable is 
>in the DriveWire 3  Specification document in the "Support" section 
>of the Cloud 9 web site.  Or you could buy a cable from them.  I've 
>just downloaded DriveWire 3, burned it onto an EPROM, soldered up a 
>cable, and got it running.  It's very cool.  There are servers for 
>MS-Windows, Linux, and MacOS X.
>
>Roger Taylor has a program that will convert a file to an audio file 
>which can be CLOADed into the CoCo's cassette port.  I think you can 
>also produce such a file using a CoCo emulator running on a modern PC.
>Then you just need a CoCo cassette cable.  Roger also sells a ROM 
>pak that contains a program similar to DriveWire, as well as a 
>bluetooth wireless serial interface.

CoCoNet hasn't been released yet, but it will be free as a download 
and I'll sell EPROM copies of the client for a small fee.  The ROM 
can drop in the bluetooth pak and give the CoCo a wireless virtual 
floppy drive system on powerup, not to mention HTTP requests and 
remote printing support.

I envy Bill in that he's showed more interest in his CoCo in two 
weeks than a lot of people here show over months or a year.  Bill, 
I'm not sure if you're a previous CoCoNut rediscovering the community 
or just a newcomer, but either way there's no turning back now.. 
you're one of us now.  :)


-- 
Roger Taylor

http://www.wordofthedayonline.com



From coconut at pritchard.ca  Tue Mar 10 12:28:31 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Tue, 10 Mar 2009 11:28:31 -0500
Subject: [Coco] Coco to PC cable
In-Reply-To: <002001c9a191$51357ec0$f3a07c40$@rr.com>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
Message-ID: <1806abd60903100928j3f2326dem63a7ab2cfae52371@mail.gmail.com>

Hi Bill,

Both http://www.cloud9tech.com/ and http://www.coco3.com/ sell the
CoCo to PC serial cables.

On Tue, Mar 10, 2009 at 10:03 AM, Bill <cwgordon at carolina.rr.com> wrote:
> What kind of cable would I need to copy files from my PC to my Coco?
>
> Anybody got one??
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From boisy at tee-boy.com  Tue Mar 10 12:47:05 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Tue, 10 Mar 2009 11:47:05 -0500
Subject: [Coco] Coco to PC cable
In-Reply-To: <20090310162545.30AF120A13@qs281.pair.com>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
	<49B67FEF.8050406@swbell.net>
	<20090310162545.30AF120A13@qs281.pair.com>
Message-ID: <4333B191-2A29-45E1-A337-0D1DE0EEAF3F@tee-boy.com>

On Mar 10, 2009, at 11:25 AM, Roger Taylor wrote:

> At 09:57 AM 3/10/2009, you wrote:
>> Depends on how you want to do it.
>> If you can burn an EPROM or buy a ROM pak from Cloud 9, you can use  
>> DriveWire.  The documentation for how to build a DriveWire cable is  
>> in the DriveWire 3  Specification document in the "Support" section  
>> of the Cloud 9 web site.  Or you could buy a cable from them.  I've  
>> just downloaded DriveWire 3, burned it onto an EPROM, soldered up a  
>> cable, and got it running.  It's very cool.  There are servers for  
>> MS-Windows, Linux, and MacOS X.
>>
>> Roger Taylor has a program that will convert a file to an audio  
>> file which can be CLOADed into the CoCo's cassette port.  I think  
>> you can also produce such a file using a CoCo emulator running on a  
>> modern PC.
>> Then you just need a CoCo cassette cable.  Roger also sells a ROM  
>> pak that contains a program similar to DriveWire, as well as a  
>> bluetooth wireless serial interface.
>
> CoCoNet hasn't been released yet, but it will be free as a download  
> and I'll sell EPROM copies of the client for a small fee.  The ROM  
> can drop in the bluetooth pak and give the CoCo a wireless virtual  
> floppy drive system on powerup, not to mention HTTP requests and  
> remote printing support.


Roger,

This message is not intended to start a flame war or be anything  
negative.  It is a call to openness.

I highly suggest that you make your product compatible with the open  
and published DriveWire 3 protocol.

There are several good reasons for this:

1. Interoperability: Existing DriveWire customers would be able to  
take advantage of your server software.
2. Compatibility: You wouldn't have to write NitrOS-9 drivers to talk  
to your server -- they're already written and are now freely  
available.  HDB-DOS for DriveWire would also just "work."

The obvious downside to not adopting the DriveWire 3 protocol would be  
that there would be two different standards for information  
interchange between the CoCo and a server.  CoCo users would be forced  
to choose one or the other in many cases.

Since there is a great deal of commonality between DriveWire 3 and  
your product, I think the CoCo community would really embrace this  
opportunity for interoperability and compatibility.  It certainly  
would make their world easier.

If you're concerned about some features that you implemented in your  
protocol that aren't in DriveWire 3, I'll be happy to review them with  
you and extend the DriveWire 3 protocol specification to accommodate  
them.

Boisy




From tjseagrove at writeme.com  Tue Mar 10 13:04:45 2009
From: tjseagrove at writeme.com (Tom Seagrove)
Date: Tue, 10 Mar 2009 13:04:45 -0400
Subject: [Coco] .dsk format
In-Reply-To: <20090310161917.4786220A14@qs281.pair.com>
References: <001f01c9a18a$238d2060$6aa76120$@rr.com>	<112289.24291.qm@web30207.mail.mud.yahoo.com>
	<20090310161917.4786220A14@qs281.pair.com>
Message-ID: <003a01c9a1a2$50e5c860$f2b15920$@com>

Am I right in assuming that with either coconet or drivewire I can access a
vitual .dsk and do a disk copy to a real disk on my coco system?

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
Behalf Of Roger Taylor
Sent: Tuesday, March 10, 2009 12:18 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] .dsk format

At 09:10 AM 3/10/2009, you wrote:
>I do not know of a utility that runs on the coco end which will 
>allow you to mount a .dsk image as a "real" disk.

Are you sure he's not wanting to know about DriveWire or CoCoNet?










>Bill <cwgordon at carolina.rr.com> wrote: Pardon what may be a silly 
>question, but can files saved in the .dsk format
>be downloaded and put back on their original condition using a coco?
>
>______________________________________
>*Square One Christian BBS
>Web access: http://www.sq1bbs.com/index.php
>Telnet access: telnet://sq1bbs.com
>
>A Taste of CoCo Forum
>http://www.sq1bbs.com/coco/index.php
>
>Live chat room - Ventrilo 3.x required
>Host name or IP: www.sq1bbs.com
>Port: 3784
>
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco
>
>
>
>** Mistrust Authority. Promote Decentralization **
>
>
>
>
>
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco

-- 
Roger Taylor

http://www.wordofthedayonline.com


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco
No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.0.237 / Virus Database: 270.11.9/1991 - Release Date: 03/10/09
07:19:00




From mdelyea at gmail.com  Tue Mar 10 13:36:48 2009
From: mdelyea at gmail.com (mike delyea)
Date: Tue, 10 Mar 2009 13:36:48 -0400
Subject: [Coco] .dsk format
In-Reply-To: <003a01c9a1a2$50e5c860$f2b15920$@com>
References: <001f01c9a18a$238d2060$6aa76120$@rr.com>
	<112289.24291.qm@web30207.mail.mud.yahoo.com>
	<20090310161917.4786220A14@qs281.pair.com>
	<003a01c9a1a2$50e5c860$f2b15920$@com>
Message-ID: <1b52e6c80903101036k3d84a79eo51fd9c1956013606@mail.gmail.com>

You can do it if you have a 360k floppy drive on a windows 98 machine
OR a 3.5" drive on the W98 machine and on the coco.  I use David
Keil's emulator because it has virtual to real drive drivers.  From
the documentation:

Depending on compatibility of your PC you should be able to read/write
single density & double density 5.25" and 3.5" disks in 360k and 720k
PC floppy drives (commonly known as low/double density drives, DD).
You should be able to read/write double density 5.25" and 3.5" disks
in 1.2meg and 1.44meg PC floppy drives (commonly known as high density
drives, HD).

Eight fixed sector length REAL floppy specification virtual disks are
supplied to read/write 256 byte/sector floppies in a PC's A: and B:
drives.

FDD0_360.DSK  	Reads 35/40 track disks on a PC A: 360k (DD) drive.
FDD1_360.DSK 	Reads 35/40 track disks on a PC B: 360k (DD) drive
FHD0_360.DSK 	Reads 35/40 track disks on a PC A: 1.2meg (HD) drive.
(double steps head)
FHD1_360.DSK 	Reads 35/40 track disks on a PC B: 1.2meg (HD) drive.
(double steps head)
FHD0_720.DSK 	Reads 80 track disks on a PC A: 1.2meg (HD) drive.
FHD1_720.DSK 	Reads 80 track disks on a PC B: 1.2meg (HD) drive.
F350_720.DSK 	Reads 80 track 3.5" disks on a PC A: 1.44meg (HD) drive.
F351_720.DSK 	Reads 80 track 3.5" disks on a PC B: 1.44meg (HD) drive.

Eight variable sector length REAL floppy specification virtual disks
are supplied to read/write 128-1024 byte/sector floppies in a PC's A:
and B: drives. These specification disks are slower than the fixed
length ones and should only be used on disks un-readable with the
fixed length specification disks.

VDD0_360.DSK 	Reads 35/40 track disks on a PC A: 360k (DD) drive.
VDD1_360.DSK 	Reads 35/40 track disks on a PC B: 360k (DD) drive
VHD0_360.DSK 	Reads 35/40 track disks on a PC A: 1.2meg (HD) drive.
(double steps head)
VHD1_360.DSK 	Reads 35/40 track disks on a PC B: 1.2meg (HD) drive.
(double steps head)
VHD0_720.DSK 	Reads 80 track disks on a PC A: 1.2meg (HD) drive.
VHD1_720.DSK 	Reads 80 track disks on a PC B: 1.2meg (HD) drive.
V350_720.DSK 	Reads 80 track 3.5" disks on a PC A: 1.44meg (HD) drive.
V351_720.DSK 	Reads 80 track 3.5" disks on a PC B: 1.44meg (HD) drive.

I can confirm that it is possible to write a 360k floppy disk (or 180k
for DECB) on a 5.25" 1.2mb disk drive.  I have successfully written
both OS-9 and Nitros-9 .dsk images to floppy using this method, also
Donkey Kong and several other games.  I seem to recall that I had to
fiddle around in the BIOS with the 1.2mb drive's settings to make it
720k (not really sure - its been a while) and I had to try a couple of
the above listed .dsk images to get it to work.  It took a bit of
experimentation.  Also, I might have formatted the disk on the coco
first.

You put the .dsk image that you want to copy in drive 0 and the
virtual driver .dsk image in drive 1 and just backup 0 to 1.

If you can't get it to work let me know and I'll fire up old 98 and
run through the procedure again to get the correct steps.

On Tue, Mar 10, 2009 at 1:04 PM, Tom Seagrove <tjseagrove at writeme.com> wrote:
> Am I right in assuming that with either coconet or drivewire I can access a
> vitual .dsk and do a disk copy to a real disk on my coco system?
>
> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
> Behalf Of Roger Taylor
> Sent: Tuesday, March 10, 2009 12:18 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] .dsk format
>
> At 09:10 AM 3/10/2009, you wrote:
>>I do not know of a utility that runs on the coco end which will
>>allow you to mount a .dsk image as a "real" disk.
>
> Are you sure he's not wanting to know about DriveWire or CoCoNet?
>
>
>
>
>
>
>
>
>
>
>>Bill <cwgordon at carolina.rr.com> wrote: Pardon what may be a silly
>>question, but can files saved in the .dsk format
>>be downloaded and put back on their original condition using a coco?
>>
>>______________________________________
>>*Square One Christian BBS
>>Web access: http://www.sq1bbs.com/index.php
>>Telnet access: telnet://sq1bbs.com
>>
>>A Taste of CoCo Forum
>>http://www.sq1bbs.com/coco/index.php
>>
>>Live chat room - Ventrilo 3.x required
>>Host name or IP: www.sq1bbs.com
>>Port: 3784
>>
>>
>>
>>--
>>Coco mailing list
>>Coco at maltedmedia.com
>>http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>>
>>** Mistrust Authority. Promote Decentralization **
>>
>>
>>
>>
>>
>>
>>
>>--
>>Coco mailing list
>>Coco at maltedmedia.com
>>http://five.pairlist.net/mailman/listinfo/coco
>
> --
> Roger Taylor
>
> http://www.wordofthedayonline.com
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.237 / Virus Database: 270.11.9/1991 - Release Date: 03/10/09
> 07:19:00
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From operator at coco3.com  Tue Mar 10 14:49:17 2009
From: operator at coco3.com (Roger Taylor)
Date: Tue, 10 Mar 2009 13:49:17 -0500
Subject: [Coco] Coco to PC cable
In-Reply-To: <4333B191-2A29-45E1-A337-0D1DE0EEAF3F@tee-boy.com>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
	<49B67FEF.8050406@swbell.net>
	<20090310162545.30AF120A13@qs281.pair.com>
	<4333B191-2A29-45E1-A337-0D1DE0EEAF3F@tee-boy.com>
Message-ID: <20090310185016.698C920A13@qs281.pair.com>

At 11:47 AM 3/10/2009, you wrote:

>Roger,
>
>This message is not intended to start a flame war or be anything
>negative.  It is a call to openness.
>
>I highly suggest that you make your product compatible with the open
>and published DriveWire 3 protocol.
>
>There are several good reasons for this:
>
>1. Interoperability: Existing DriveWire customers would be able to
>take advantage of your server software.
>2. Compatibility: You wouldn't have to write NitrOS-9 drivers to talk
>to your server -- they're already written and are now freely
>available.  HDB-DOS for DriveWire would also just "work."
>
>The obvious downside to not adopting the DriveWire 3 protocol would be
>that there would be two different standards for information
>interchange between the CoCo and a server.  CoCo users would be forced
>to choose one or the other in many cases.


No flames here.  I'm always open for a peaceful group talk.

I'm not sure I understand how any kind of "integration" of DriveWire 
and CoCoNet (or their underlying protocols) could yield two systems 
that don't eventually become identical.  Right now, they're not the 
same by any means.  It seems that eventually the now-open DriveWire 
would become CoCoNet, and CoCoNet would become DriveWire.  If this 
happens, any competition at all would be in the EPROMs and/or the 
paks they ride in, and software that uses the internet abilities of 
either progressing network system.  I don't think the name DriveWire 
will always describe what it does.  I think the name CoCoNet fully 
describes where I'm taking the system.  These are some of the key 
points that come to mind when I compare the two systems and where 
they would otherwise be going.

Here's a summary of what CoCoNet currently does:  As well as the 
server, the *CoCo* can mount virtual disks from the web or remote 
PC.  CoCoNet can request web pages and files and have them returned 
on a mounted virtual disk.  These requests can append URL parameters, 
making some serious things possible from the CoCo, like live chat, 
multi-player games, etc. without adding any additional protocol 
support.  Oh, and mounting virtual ROM Paks,... done in the bitbanger 
version, not added to the 6551 version yet.


-- 
Roger Taylor

http://www.wordofthedayonline.com



From johnchasteen.2 at juno.com  Tue Mar 10 15:10:12 2009
From: johnchasteen.2 at juno.com (John T Chasteen)
Date: Tue, 10 Mar 2009 15:10:12 -0400
Subject: [Coco] .dsk format
Message-ID: <20090310.151012.3684.0.Johnchasteen.2@juno.com>

What does it take to get David Keil's Emulator?
I have Win98 and a 3.5 in. drive on the Win98 system.
I have coco3 and Drive wire2 w/cable (Cloudp9 products)
with a Cloud9 hard drive controller w/2 CF units.
I still don't know how to transfer files downloaded on the Internet
and get the files on my coco3. I will be traveling from Bradenton,
Florida(about 50 miles South Tampa) to attend the Fest.

So at 81 years old, I meed a lot of help and it will be greatly
appreciated

John C.
 
 
On Tue, 10 Mar 2009 13:36:48 -0400 mike delyea <mdelyea at gmail.com>
writes:
> You can do it if you have a 360k floppy drive on a windows 98 
> machine
> OR a 3.5" drive on the W98 machine and on the coco.  I use David
> Keil's emulator because it has virtual to real drive drivers.  From
> the documentation:
> 
> Depending on compatibility of your PC you should be able to 
> read/write
> single density & double density 5.25" and 3.5" disks in 360k and 
> 720k
> PC floppy drives (commonly known as low/double density drives, DD).
> You should be able to read/write double density 5.25" and 3.5" 
> disks
> in 1.2meg and 1.44meg PC floppy drives (commonly known as high 
> density
> drives, HD).
> 
> Eight fixed sector length REAL floppy specification virtual disks 
> are
> supplied to read/write 256 byte/sector floppies in a PC's A: and B:
> drives.
> 
> FDD0_360.DSK          Reads 35/40 track disks on a PC A: 360k (DD) 
> drive.
> FDD1_360.DSK         Reads 35/40 track disks on a PC B: 360k (DD) 
> drive
> FHD0_360.DSK         Reads 35/40 track disks on a PC A: 1.2meg (HD) 
> drive.
> (double steps head)
> FHD1_360.DSK         Reads 35/40 track disks on a PC B: 1.2meg (HD) 
> drive.
> (double steps head)
> FHD0_720.DSK         Reads 80 track disks on a PC A: 1.2meg (HD) 
> drive.
> FHD1_720.DSK         Reads 80 track disks on a PC B: 1.2meg (HD) 
> drive.
> F350_720.DSK         Reads 80 track 3.5" disks on a PC A: 1.44meg 
> (HD) drive.
> F351_720.DSK         Reads 80 track 3.5" disks on a PC B: 1.44meg 
> (HD) drive.
> 
> Eight variable sector length REAL floppy specification virtual 
> disks
> are supplied to read/write 128-1024 byte/sector floppies in a PC's 
> A:
> and B: drives. These specification disks are slower than the fixed
> length ones and should only be used on disks un-readable with the
> fixed length specification disks.
> 
> VDD0_360.DSK         Reads 35/40 track disks on a PC A: 360k (DD) 
> drive.
> VDD1_360.DSK         Reads 35/40 track disks on a PC B: 360k (DD) 
> drive
> VHD0_360.DSK         Reads 35/40 track disks on a PC A: 1.2meg (HD) 
> drive.
> (double steps head)
> VHD1_360.DSK         Reads 35/40 track disks on a PC B: 1.2meg (HD) 
> drive.
> (double steps head)
> VHD0_720.DSK         Reads 80 track disks on a PC A: 1.2meg (HD) 
> drive.
> VHD1_720.DSK         Reads 80 track disks on a PC B: 1.2meg (HD) 
> drive.
> V350_720.DSK         Reads 80 track 3.5" disks on a PC A: 1.44meg 
> (HD) drive.
> V351_720.DSK         Reads 80 track 3.5" disks on a PC B: 1.44meg 
> (HD) drive.
> 
> I can confirm that it is possible to write a 360k floppy disk (or 
> 180k
> for DECB) on a 5.25" 1.2mb disk drive.  I have successfully written
> both OS-9 and Nitros-9 .dsk images to floppy using this method, 
> also
> Donkey Kong and several other games.  I seem to recall that I had 
> to
> fiddle around in the BIOS with the 1.2mb drive's settings to make 
> it
> 720k (not really sure - its been a while) and I had to try a couple 
> of
> the above listed .dsk images to get it to work.  It took a bit of
> experimentation.  Also, I might have formatted the disk on the coco
> first.
> 
> You put the .dsk image that you want to copy in drive 0 and the
> virtual driver .dsk image in drive 1 and just backup 0 to 1.
> 
> If you can't get it to work let me know and I'll fire up old 98 and
> run through the procedure again to get the correct steps.
> 
> On Tue, Mar 10, 2009 at 1:04 PM, Tom Seagrove 
> <tjseagrove at writeme.com> wrote:
> > Am I right in assuming that with either coconet or drivewire I can 
> access a
> > vitual .dsk and do a disk copy to a real disk on my coco system?
> >
> > -----Original Message-----
> > From: coco-bounces at maltedmedia.com 
> [mailto:coco-bounces at maltedmedia.com] On
> > Behalf Of Roger Taylor
> > Sent: Tuesday, March 10, 2009 12:18 PM
> > To: CoCoList for Color Computer Enthusiasts
> > Subject: Re: [Coco] .dsk format
> >
> > At 09:10 AM 3/10/2009, you wrote:
> >>I do not know of a utility that runs on the coco end which will
> >>allow you to mount a .dsk image as a "real" disk.
> >
> > Are you sure he's not wanting to know about DriveWire or CoCoNet?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >>Bill <cwgordon at carolina.rr.com> wrote: Pardon what may be a silly
> >>question, but can files saved in the .dsk format
> >>be downloaded and put back on their original condition using a 
> coco?
> >>
> >>______________________________________
> >>*Square One Christian BBS
> >>Web access: http://www.sq1bbs.com/index.php
> >>Telnet access: telnet://sq1bbs.com
> >>
> >>A Taste of CoCo Forum
> >>http://www.sq1bbs.com/coco/index.php
> >>
> >>Live chat room - Ventrilo 3.x required
> >>Host name or IP: www.sq1bbs.com
> >>Port: 3784
> >>
> >>
> >>
> >>--
> >>Coco mailing list
> >>Coco at maltedmedia.com
> >>http://five.pairlist.net/mailman/listinfo/coco
> >>
> >>
> >>
> >>** Mistrust Authority. Promote Decentralization **
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>--
> >>Coco mailing list
> >>Coco at maltedmedia.com
> >>http://five.pairlist.net/mailman/listinfo/coco
> >
> > --
> > Roger Taylor
> >
> > http://www.wordofthedayonline.com
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> > No virus found in this incoming message.
> > Checked by AVG - www.avg.com
> > Version: 8.0.237 / Virus Database: 270.11.9/1991 - Release Date: 
> 03/10/09
> > 07:19:00
> >
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> >
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> 
> 
 
____________________________________________________________
Digital Photography - Click Now.
http://thirdpartyoffers.juno.com/TGL2141/fc/BLSrjpTDvmRgZcbybvHXu4W8EidD1oj0onYN1QNddHIXAHA68rwPTpkJwyM/


From cwgordon at carolina.rr.com  Tue Mar 10 16:21:06 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Tue, 10 Mar 2009 15:21:06 -0500
Subject: [Coco] .dsk format
In-Reply-To: <20090310.151012.3684.0.Johnchasteen.2@juno.com>
References: <20090310.151012.3684.0.Johnchasteen.2@juno.com>
Message-ID: <005a01c9a1bd$be1c33e0$3a549ba0$@rr.com>

Totally off topic, I know, but anyway:

God bless you Brother Chasteen. I thought I was one of the older Cocoists
(at age 60).

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of John T Chasteen
> Sent: Tuesday, March 10, 2009 2:10 PM
> To: coco at maltedmedia.com
> Cc: coco at maltedmedia.com
> Subject: Re: [Coco] .dsk format
> 
> So at 81 years old, I meed a lot of help and it will be greatly
appreciated
> 



From boisy at tee-boy.com  Tue Mar 10 15:31:10 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Tue, 10 Mar 2009 14:31:10 -0500
Subject: [Coco] Coco to PC cable
In-Reply-To: <20090310185016.698C920A13@qs281.pair.com>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
	<49B67FEF.8050406@swbell.net>
	<20090310162545.30AF120A13@qs281.pair.com>
	<4333B191-2A29-45E1-A337-0D1DE0EEAF3F@tee-boy.com>
	<20090310185016.698C920A13@qs281.pair.com>
Message-ID: <68E6554E-948C-44B6-AED5-1D56427B4C3B@tee-boy.com>

> No flames here.  I'm always open for a peaceful group talk.
>
> I'm not sure I understand how any kind of "integration" of DriveWire  
> and CoCoNet (or their underlying protocols) could yield two systems  
> that don't eventually become identical.  Right now, they're not the  
> same by any means.  It seems that eventually the now-open DriveWire  
> would become CoCoNet, and CoCoNet would become DriveWire.  If this  
> happens, any competition at all would be in the EPROMs and/or the  
> paks they ride in, and software that uses the internet abilities of  
> either progressing network system.  I don't think the name DriveWire  
> will always describe what it does.  I think the name CoCoNet fully  
> describes where I'm taking the system.  These are some of the key  
> points that come to mind when I compare the two systems and where  
> they would otherwise be going.
>
> Here's a summary of what CoCoNet currently does:  As well as the  
> server, the *CoCo* can mount virtual disks from the web or remote  
> PC.  CoCoNet can request web pages and files and have them returned  
> on a mounted virtual disk.  These requests can append URL  
> parameters, making some serious things possible from the CoCo, like  
> live chat, multi-player games, etc. without adding any additional  
> protocol support.  Oh, and mounting virtual ROM Paks,... done in the  
> bitbanger version, not added to the 6551 version yet.

I don't have the benefit of seeing your CoCoNet protocol since you  
have not published it, so I cannot fully compare products here, but  
from your description, it is fair to assume that your product is a  
superset of DriveWire.

Even so, you could still adopt the DriveWire 3 protocol for disk  
storage and printing to remain compatible with the existing user base,  
and have your advanced features (web page saving, etc) outside of the  
DriveWire protocol altogether.

Adopting the protocol in CoCoNet would be a win-win for you and for  
the CoCo community.

For you, it would expand the use of your product immediately to Linux  
and Mac OS X for the disk functionality.   Do you plan on having  
NitrOS-9 support for CoCoNet?  Instead of writing your own drivers,  
you could adopt the DriveWire 3 protocol and not have to spend any  
time writing drivers.  It would just "work" under NitrOS-9.  And if  
you chose to publish your protocol, then NitrOS-9 could be made to  
adapt to any extra features that you would bring in your protocol.

For the CoCo community it would provide the following benefits:

1. HDB-DOS for DriveWire 3 users could talk to a CoCoNet server (you  
didn't indicate if the server software would be free or not, so this  
may not be an issue)
2. CoCoNet ROM users could talk to any DriveWire 3 server under Linux,  
Windows or Mac OS X for disk image support (DriveWire 3 servers are  
freely available for download)
3. NitrOS-9 users could boot from a NitrOS-9 disk mounted on your  
CoCoNet server

To enumerate the downsides of having two separate systems and  
protocols for disk storage:

1. CoCoNet customers could not use DriveWire 3 WinServer, MacServer or  
LinServer servers.
2. HDB-DOS for DriveWire customers could not use the CoCoNet server
3. Customers would be forced to choose between two products that have  
similar functionality; those who don't require web pages to be loaded  
onto their CoCo, or need NitrOS-9 support, would use HDB-DOS for  
DriveWire.  Those who would desire the web page and ROM pak features  
you offer would have to choose you product.
4. You would have to write NitrOS-9 drivers (assuming you wanted to  
support NitrOS-9, that is)

This is all, of course, your decision.  For me, there is no benefit or  
detriment to you choosing to adopt the DriveWire 3 protocol. Besides  
the benefits that I laid out above (additional server platform  
support, instant NitrOS-9 compatibility), the CoCo community would be  
the real winner here, and that's really what it's all about, right?

Is there anyone else here who would see the benefit of Roger adopting  
the DriveWire 3 protocol for disk storage in his CoCoNet product if it  
meant greater interoperability, greater choice and greater flexibility?

Boisy








From cyberpunk at prtc.net  Tue Mar 10 16:11:38 2009
From: cyberpunk at prtc.net (RJLCyberPunk)
Date: Tue, 10 Mar 2009 16:11:38 -0400
Subject: [Coco] How about a CoCo Web Browser?
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
	<1806abd60903100928j3f2326dem63a7ab2cfae52371@mail.gmail.com>
Message-ID: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>

OK now that they have a wireless blue tooh "RS232" pak for the CoCo that 
would and should allow it to use the PC it links too as a server to connect 
to the internet wouldn't the next logical step be to develop a CoCo web 
browser?

One that is at least text based with limited graphics capability like this 
one developed for the Apple II here: 
http://www.youtube.com/watch?v=OMzgp7xTp1k&fmt=18




From fwp at deepthought.com  Tue Mar 10 16:56:09 2009
From: fwp at deepthought.com (Frank Pittel)
Date: Tue, 10 Mar 2009 15:56:09 -0500
Subject: [Coco] Coco to PC cable
In-Reply-To: <68E6554E-948C-44B6-AED5-1D56427B4C3B@tee-boy.com>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
	<49B67FEF.8050406@swbell.net>
	<20090310162545.30AF120A13@qs281.pair.com>
	<4333B191-2A29-45E1-A337-0D1DE0EEAF3F@tee-boy.com>
	<20090310185016.698C920A13@qs281.pair.com>
	<68E6554E-948C-44B6-AED5-1D56427B4C3B@tee-boy.com>
Message-ID: <20090310205609.GT7702@warlock.deepthought.com>

On Tue, Mar 10, 2009 at 02:31:10PM -0500, Boisy Pitre wrote:
>> No flames here.  I'm always open for a peaceful group talk.
>>
>> I'm not sure I understand how any kind of "integration" of DriveWire  
>> and CoCoNet (or their underlying protocols) could yield two systems  
>> that don't eventually become identical.  Right now, they're not the  
>> same by any means.  It seems that eventually the now-open DriveWire  
>> would become CoCoNet, and CoCoNet would become DriveWire.  If this  
>> happens, any competition at all would be in the EPROMs and/or the paks 
>> they ride in, and software that uses the internet abilities of either 
>> progressing network system.  I don't think the name DriveWire will 
>> always describe what it does.  I think the name CoCoNet fully  
>> describes where I'm taking the system.  These are some of the key  
>> points that come to mind when I compare the two systems and where they 
>> would otherwise be going.
>>
>> Here's a summary of what CoCoNet currently does:  As well as the  
>> server, the *CoCo* can mount virtual disks from the web or remote PC.  
>> CoCoNet can request web pages and files and have them returned on a 
>> mounted virtual disk.  These requests can append URL parameters, making 
>> some serious things possible from the CoCo, like live chat, 
>> multi-player games, etc. without adding any additional protocol 
>> support.  Oh, and mounting virtual ROM Paks,... done in the bitbanger 
>> version, not added to the 6551 version yet.
>
> I don't have the benefit of seeing your CoCoNet protocol since you have 
> not published it, so I cannot fully compare products here, but from your 
> description, it is fair to assume that your product is a superset of 
> DriveWire.
>
> Even so, you could still adopt the DriveWire 3 protocol for disk storage 
> and printing to remain compatible with the existing user base, and have 
> your advanced features (web page saving, etc) outside of the DriveWire 
> protocol altogether.
>
> Adopting the protocol in CoCoNet would be a win-win for you and for the 
> CoCo community.
>
> For you, it would expand the use of your product immediately to Linux  
> and Mac OS X for the disk functionality.   Do you plan on having  
> NitrOS-9 support for CoCoNet?  Instead of writing your own drivers, you 
> could adopt the DriveWire 3 protocol and not have to spend any time 
> writing drivers.  It would just "work" under NitrOS-9.  And if you chose 
> to publish your protocol, then NitrOS-9 could be made to adapt to any 
> extra features that you would bring in your protocol.
>
> For the CoCo community it would provide the following benefits:
>
> 1. HDB-DOS for DriveWire 3 users could talk to a CoCoNet server (you  
> didn't indicate if the server software would be free or not, so this may 
> not be an issue)
> 2. CoCoNet ROM users could talk to any DriveWire 3 server under Linux,  
> Windows or Mac OS X for disk image support (DriveWire 3 servers are  
> freely available for download)
> 3. NitrOS-9 users could boot from a NitrOS-9 disk mounted on your  
> CoCoNet server
>
> To enumerate the downsides of having two separate systems and protocols 
> for disk storage:
>
> 1. CoCoNet customers could not use DriveWire 3 WinServer, MacServer or  
> LinServer servers.
> 2. HDB-DOS for DriveWire customers could not use the CoCoNet server
> 3. Customers would be forced to choose between two products that have  
> similar functionality; those who don't require web pages to be loaded  
> onto their CoCo, or need NitrOS-9 support, would use HDB-DOS for  
> DriveWire.  Those who would desire the web page and ROM pak features you 
> offer would have to choose you product.
> 4. You would have to write NitrOS-9 drivers (assuming you wanted to  
> support NitrOS-9, that is)
>
> This is all, of course, your decision.  For me, there is no benefit or  
> detriment to you choosing to adopt the DriveWire 3 protocol. Besides the 
> benefits that I laid out above (additional server platform support, 
> instant NitrOS-9 compatibility), the CoCo community would be the real 
> winner here, and that's really what it's all about, right?
>
> Is there anyone else here who would see the benefit of Roger adopting  
> the DriveWire 3 protocol for disk storage in his CoCoNet product if it  
> meant greater interoperability, greater choice and greater flexibility?

In the interest of full disclosure I should point out that I am happily using
drivewire and have little interest in switching to something else. I'm hoping
that Roger sees the wisdom having his product and drivewire use the same protocol
or at least he sees the wisdom in opening his protocol. The current coco
community is to small to have a "war" between the two protocols. While I believe
in competition I'm afraid that in this case it will divide the community and in
the long run this will be a bad thing.

Frank


From linville at tuxdriver.com  Tue Mar 10 16:01:41 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Tue, 10 Mar 2009 16:01:41 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <68E6554E-948C-44B6-AED5-1D56427B4C3B@tee-boy.com>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
	<49B67FEF.8050406@swbell.net>
	<20090310162545.30AF120A13@qs281.pair.com>
	<4333B191-2A29-45E1-A337-0D1DE0EEAF3F@tee-boy.com>
	<20090310185016.698C920A13@qs281.pair.com>
	<68E6554E-948C-44B6-AED5-1D56427B4C3B@tee-boy.com>
Message-ID: <20090310200141.GD10800@tuxdriver.com>

On Tue, Mar 10, 2009 at 02:31:10PM -0500, Boisy Pitre wrote:

> This is all, of course, your decision.  For me, there is no benefit or  
> detriment to you choosing to adopt the DriveWire 3 protocol. Besides the 
> benefits that I laid out above (additional server platform support, 
> instant NitrOS-9 compatibility), the CoCo community would be the real 
> winner here, and that's really what it's all about, right?
>
> Is there anyone else here who would see the benefit of Roger adopting  
> the DriveWire 3 protocol for disk storage in his CoCoNet product if it  
> meant greater interoperability, greater choice and greater flexibility?

As a resident member of the open source crowd, I feel compelled
to raise my hand. :-)  I think you have covered the major points
benefiting the users (or "customers") of the two projects.  There is
also the added benefit of developer cooperation -- for example,
CoCoNet could grow printing functionality without having to spend
development resources on the server.

I'd like to commend Boisy for opening-up DriveWire sources, and I
would also note that the DriveWire protocol has been well documented
for some time.  IMHO everyone developing CoCo-related software could
take that lesson to heart.  Afterall, no one is going to get rich
off this community anyway. :-)

Cooperative development is the way to go.  It exands the potential
user base and the potential developer base, while not fragmenting
the community any worse than it already is between RSDOS and NitrOS-9.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


From badfrog at gmail.com  Tue Mar 10 16:34:18 2009
From: badfrog at gmail.com (Sean)
Date: Tue, 10 Mar 2009 15:34:18 -0500
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
	<1806abd60903100928j3f2326dem63a7ab2cfae52371@mail.gmail.com>
	<052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
Message-ID: <9efa17da0903101334p716053b5yfd4e2d1a673a6884@mail.gmail.com>

Probably a more practical solution I used back in college was to dial
in to the campus terminal server, telnet to a Unix box, and use Lynx.
Also could read newsgroups from the CoCo that way!  :)

I would say graphical browsing would be unlikely, or just ungodly
slow...  Since I remember a 20k GIF file could take a minute or two to
load on the screen from disk.  JPEGs would be even worse.


On Tue, Mar 10, 2009 at 3:11 PM, RJLCyberPunk <cyberpunk at prtc.net> wrote:
> OK now that they have a wireless blue tooh "RS232" pak for the CoCo that
> would and should allow it to use the PC it links too as a server to connect
> to the internet wouldn't the next logical step be to develop a CoCo web
> browser?
>
> One that is at least text based with limited graphics capability like this
> one developed for the Apple II here:
> http://www.youtube.com/watch?v=OMzgp7xTp1k&fmt=18
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From jlhickle at yahoo.com  Tue Mar 10 16:44:33 2009
From: jlhickle at yahoo.com (Jim Hickle)
Date: Tue, 10 Mar 2009 13:44:33 -0700 (PDT)
Subject: [Coco] Coco to PC cable
In-Reply-To: <20090310205609.GT7702@warlock.deepthought.com>
Message-ID: <149213.60557.qm@web37303.mail.mud.yahoo.com>




--- On Tue, 3/10/09, Frank Pittel <fwp at deepthought.com> wrote:

>While I believe
>in competition I'm afraid that in this case it will divide the community
>and in
>the long run this will be a bad thing.



Right.  It's bad enough that we right-thinking people, i.e., those with SCSI controllers, have to endure the disunity brought about by the unwashed, IDE-using rabble.



      


From badfrog at gmail.com  Tue Mar 10 16:55:25 2009
From: badfrog at gmail.com (Sean)
Date: Tue, 10 Mar 2009 15:55:25 -0500
Subject: [Coco] Coco to PC cable
In-Reply-To: <149213.60557.qm@web37303.mail.mud.yahoo.com>
References: <20090310205609.GT7702@warlock.deepthought.com>
	<149213.60557.qm@web37303.mail.mud.yahoo.com>
Message-ID: <9efa17da0903101355t28f270bei891bb9fae678116@mail.gmail.com>

While I might have agreed with that 10 years ago, I cringe when I see
a SCSI device now (on a modern box).   Now I gotta deal with adapters
and drivers if a drive fails, I can't just go plug it into my
diagnostic PCs USB dongle and scan it.
Plus, paying for a SCSI hard drive also makes me cringe.

On Tue, Mar 10, 2009 at 3:44 PM, Jim Hickle <jlhickle at yahoo.com> wrote:
>
>
>
> --- On Tue, 3/10/09, Frank Pittel <fwp at deepthought.com> wrote:
>
>>While I believe
>>in competition I'm afraid that in this case it will divide the community
>>and in
>>the long run this will be a bad thing.
>
>
>
> Right. ?It's bad enough that we right-thinking people, i.e., those with SCSI controllers, have to endure the disunity brought about by the unwashed, IDE-using rabble.
>
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From jlhickle at yahoo.com  Tue Mar 10 17:04:41 2009
From: jlhickle at yahoo.com (Jim Hickle)
Date: Tue, 10 Mar 2009 14:04:41 -0700 (PDT)
Subject: [Coco] Coco to PC cable
In-Reply-To: <9efa17da0903101355t28f270bei891bb9fae678116@mail.gmail.com>
Message-ID: <78619.46938.qm@web37306.mail.mud.yahoo.com>





--- On Tue, 3/10/09, Sean <badfrog at gmail.com> wrote:


> and drivers if a drive fails, I can't just go plug it
> into my
> diagnostic PCs USB dongle and scan it.
> Plus, paying for a SCSI hard drive also makes me cringe.
> 


I cringe when I see a new device has a USB plug.
Bartender, gimme a good ol' parallel port.

Never priced a new SCSI drive; my Coco and Linux systems
have used drives that I got real cheap.  These are good
times indeed for us (computing) bottom feeders.  Plenty
of old hardware out there. ;)




      


From operator at coco3.com  Tue Mar 10 17:06:40 2009
From: operator at coco3.com (Roger Taylor)
Date: Tue, 10 Mar 2009 16:06:40 -0500
Subject: [Coco] Coco to PC cable
In-Reply-To: <149213.60557.qm@web37303.mail.mud.yahoo.com>
References: <20090310205609.GT7702@warlock.deepthought.com>
	<149213.60557.qm@web37303.mail.mud.yahoo.com>
Message-ID: <20090310210721.EE46220A15@qs281.pair.com>

At 03:44 PM 3/10/2009, you wrote:



>--- On Tue, 3/10/09, Frank Pittel <fwp at deepthought.com> wrote:
>
> >While I believe
> >in competition I'm afraid that in this case it will divide the community
> >and in
> >the long run this will be a bad thing.
>
>
>
>Right.  It's bad enough that we right-thinking people, i.e., those 
>with SCSI controllers, have to endure the disunity brought about by 
>the unwashed, IDE-using rabble.



Hahaha!  Humor, just at the right time.  I Love it.




-- 
Roger Taylor

http://www.wordofthedayonline.com



From t.fadden at cox.net  Tue Mar 10 17:40:17 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Tue, 10 Mar 2009 14:40:17 -0700
Subject: [Coco] Coco to PC cable
In-Reply-To: <9efa17da0903101355t28f270bei891bb9fae678116@mail.gmail.com>
References: <20090310205609.GT7702@warlock.deepthought.com>	<149213.60557.qm@web37303.mail.mud.yahoo.com>
	<9efa17da0903101355t28f270bei891bb9fae678116@mail.gmail.com>
Message-ID: <49B6DE41.6020906@cox.net>

Well, my dad always said "You get what you pay 
for!"                             :-)

Tim


Sean wrote:
> While I might have agreed with that 10 years ago, I cringe when I see
> a SCSI device now (on a modern box).   Now I gotta deal with adapters
> and drivers if a drive fails, I can't just go plug it into my
> diagnostic PCs USB dongle and scan it.
> Plus, paying for a SCSI hard drive also makes me cringe.
>
> On Tue, Mar 10, 2009 at 3:44 PM, Jim Hickle <jlhickle at yahoo.com> wrote:
>   
>>
>> --- On Tue, 3/10/09, Frank Pittel <fwp at deepthought.com> wrote:
>>
>>     
>>> While I believe
>>> in competition I'm afraid that in this case it will divide the community
>>> and in
>>> the long run this will be a bad thing.
>>>       
>>
>> Right.  It's bad enough that we right-thinking people, i.e., those with SCSI controllers, have to endure the disunity brought about by the unwashed, IDE-using rabble.
>>
>>
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>     
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From mdelyea at gmail.com  Tue Mar 10 17:51:42 2009
From: mdelyea at gmail.com (mike delyea)
Date: Tue, 10 Mar 2009 17:51:42 -0400
Subject: [Coco] .dsk format
In-Reply-To: <005a01c9a1bd$be1c33e0$3a549ba0$@rr.com>
References: <20090310.151012.3684.0.Johnchasteen.2@juno.com>
	<005a01c9a1bd$be1c33e0$3a549ba0$@rr.com>
Message-ID: <1b52e6c80903101451o74aa160eg47e944c57766bc19@mail.gmail.com>

The emulator can be downloaded here.

http://www.discover-net.net/~dmkeil/coco/coco3.htm

The download link is about halfway to the bottom of the page on the
left.  Its a big pink box with a picture of a coco in it.

I don't have drivewire but I'm guessing you would mount a .dsk image
on the windows drivewire server side and just copy it over.


From snhirsch at gmail.com  Tue Mar 10 19:16:25 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Tue, 10 Mar 2009 19:16:25 -0400 (EDT)
Subject: [Coco] Cable
In-Reply-To: <49A771F5.9020804@sbcglobal.net>
References: <005401c997d1$8fd156f0$af7404d0$@rr.com>
	<522395.12578.qm@web81505.mail.mud.yahoo.com>
	<00c801c9985c$761d3a90$6257afb0$@rr.com>
	<1b52e6c80902261558v386db21fnd7ba3b4a07a96bf5@mail.gmail.com>
	<00ce01c9986e$f5c961d0$e15c2570$@rr.com> <49A741CD.2090001@dls.net>
	<49A771F5.9020804@sbcglobal.net>
Message-ID: <alpine.DEB.2.00.0903101914050.32155@duo>

On Thu, 26 Feb 2009, Brian Goers wrote:

> You send me your address, privately not to the list.

> I'll check the UPS or Post office shipping cost for your zip code. UPS don't 
> deliver to P.O. Boxes

> I'll e-mail you back with the shipping cost.

> You pay me with PayPal $45.00 + Shipping.

Brian,

I've made a couple of attempts to contact you about an order.  Am I ending 
up in your spam-trap, or are you just busy?  If the latter, I'll 
understand.  Just wanted to make sure I'm getting through!

Steve


-- 


From diegoba at adinet.com.uy  Tue Mar 10 19:45:07 2009
From: diegoba at adinet.com.uy (Diego Barizo)
Date: Tue, 10 Mar 2009 20:45:07 -0300
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>	<1806abd60903100928j3f2326dem63a7ab2cfae52371@mail.gmail.com>
	<052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
Message-ID: <49B6FB83.3010906@adinet.com.uy>

I've been working in one for quite a while, but I'm restarting from scratch.
I tried in BASIC (I know nothing at all about assembler), drawing the 
text in the hi-res screen. It's just too slow 
(http://yaccs.info/PROGRAMAS/NETSCOCO/netscoco.html)
Now I'm just going to do a text based browser, maybe with a few 
different HPRINT fonts for bold and italics...
But don't hold your breath ;-)

Diego

RJLCyberPunk wrote:
> OK now that they have a wireless blue tooh "RS232" pak for the CoCo 
> that would and should allow it to use the PC it links too as a server 
> to connect to the internet wouldn't the next logical step be to 
> develop a CoCo web browser?
>
> One that is at least text based with limited graphics capability like 
> this one developed for the Apple II here: 
> http://www.youtube.com/watch?v=OMzgp7xTp1k&fmt=18
>
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



From cyberpunk at prtc.net  Tue Mar 10 20:14:00 2009
From: cyberpunk at prtc.net (RJLCyberPunk)
Date: Tue, 10 Mar 2009 20:14:00 -0400
Subject: [Coco] How about a CoCo Web Browser?
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>	<1806abd60903100928j3f2326dem63a7ab2cfae52371@mail.gmail.com><052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
	<49B6FB83.3010906@adinet.com.uy>
Message-ID: <30C002DBAB714400A1AAD13E1E58F3B2@FANTASYWARE>

Cool! Hope to hear more from this at some point. :D
----- Original Message ----- 
From: "Diego Barizo" <diegoba at adinet.com.uy>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Tuesday, March 10, 2009 7:45 PM
Subject: Re: [Coco] How about a CoCo Web Browser?


> I've been working in one for quite a while, but I'm restarting from 
> scratch.
> I tried in BASIC (I know nothing at all about assembler), drawing the text 
> in the hi-res screen. It's just too slow 
> (http://yaccs.info/PROGRAMAS/NETSCOCO/netscoco.html)
> Now I'm just going to do a text based browser, maybe with a few different 
> HPRINT fonts for bold and italics...
> But don't hold your breath ;-)
>
> Diego
>



From jdaggett at gate.net  Tue Mar 10 22:37:03 2009
From: jdaggett at gate.net (jdaggett at gate.net)
Date: Tue, 10 Mar 2009 22:37:03 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>,
	<052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
Message-ID: <49B6EB8F.1400.140A841@jdaggett.gate.net>

First off you need some means of connecting to the internet either through 
a modem or through a PC/MAC. Then you can think about a web browser. 
Can't put the cart before the horse or the cart wont go anywhere. 

james

On 10 Mar 2009 at 16:11, RJLCyberPunk wrote:

> OK now that they have a wireless blue tooh "RS232" pak for the CoCo
> that would and should allow it to use the PC it links too as a server
> to connect to the internet wouldn't the next logical step be to
> develop a CoCo web browser?
> 
> One that is at least text based with limited graphics capability like
> this one developed for the Apple II here:
> http://www.youtube.com/watch?v=OMzgp7xTp1k&fmt=18
> 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco




From gene.heskett at verizon.net  Tue Mar 10 23:14:20 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Tue, 10 Mar 2009 23:14:20 -0400
Subject: [Coco] .dsk format
In-Reply-To: <005a01c9a1bd$be1c33e0$3a549ba0$@rr.com>
References: <20090310.151012.3684.0.Johnchasteen.2@juno.com>
	<005a01c9a1bd$be1c33e0$3a549ba0$@rr.com>
Message-ID: <200903102314.20979.gene.heskett@verizon.net>

On Tuesday 10 March 2009, Bill wrote:
>Totally off topic, I know, but anyway:
>
>God bless you Brother Chasteen. I thought I was one of the older Cocoists
>(at age 60).

Chuckle.  You are a spring chicken Bill, compared to some of us.  John has me 
beat some, but I'm 74.

>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of John T Chasteen
>> Sent: Tuesday, March 10, 2009 2:10 PM
>> To: coco at maltedmedia.com
>> Cc: coco at maltedmedia.com
>> Subject: Re: [Coco] .dsk format
>>
>> So at 81 years old, I meed a lot of help and it will be greatly
>
>appreciated
>
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
There is a secret person undamaged within every individual.
		-- Paul Shepard



From briang0671 at sbcglobal.net  Tue Mar 10 23:28:04 2009
From: briang0671 at sbcglobal.net (Brian Goers)
Date: Tue, 10 Mar 2009 22:28:04 -0500
Subject: [Coco] Cable
In-Reply-To: <alpine.DEB.2.00.0903101914050.32155@duo>
References: <005401c997d1$8fd156f0$af7404d0$@rr.com>	<522395.12578.qm@web81505.mail.mud.yahoo.com>	<00c801c9985c$761d3a90$6257afb0$@rr.com>	<1b52e6c80902261558v386db21fnd7ba3b4a07a96bf5@mail.gmail.com>	<00ce01c9986e$f5c961d0$e15c2570$@rr.com>
	<49A741CD.2090001@dls.net>	<49A771F5.9020804@sbcglobal.net>
	<alpine.DEB.2.00.0903101914050.32155@duo>
Message-ID: <49B72FC4.1090305@sbcglobal.net>

Steven Hirsch wrote:
> On Thu, 26 Feb 2009, Brian Goers wrote:
>
>> You send me your address, privately not to the list.
>
>> I'll check the UPS or Post office shipping cost for your zip code. 
>> UPS don't deliver to P.O. Boxes
>
>> I'll e-mail you back with the shipping cost.
>
>> You pay me with PayPal $45.00 + Shipping.
>
> Brian,
>
> I've made a couple of attempts to contact you about an order. Am I 
> ending up in your spam-trap, or are you just busy? If the latter, I'll 
> understand. Just wanted to make sure I'm getting through!
>
> Steve
>
Hi! Steve
Sorry. I saw your message this morning but could not take the time to 
reply to you today.
I saw the first message you sent and this mornings message with your 
address. I'll e-mail you Wednesday morning with total cost of the 
interface and hard drive.
Brian

-- 
 Brian Goers                                         Glenside Color Computer Club URL
 Glenside Vice-President of Special Events           http://GlensideCCC.com     

 IDE Boards are available.
 Show cost $45.00                                   The 18th Annual ?LAST? Chicago CoCoFEST!
 Includes items in the picture                      Will be held March 28 & 29 2009
                                                    Holiday Inn & Suites Elgin.



From gene.heskett at verizon.net  Tue Mar 10 23:31:25 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Tue, 10 Mar 2009 23:31:25 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <20090310205609.GT7702@warlock.deepthought.com>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>
	<68E6554E-948C-44B6-AED5-1D56427B4C3B@tee-boy.com>
	<20090310205609.GT7702@warlock.deepthought.com>
Message-ID: <200903102331.25558.gene.heskett@verizon.net>

On Tuesday 10 March 2009, Frank Pittel wrote:
>On Tue, Mar 10, 2009 at 02:31:10PM -0500, Boisy Pitre wrote:
>>> No flames here.  I'm always open for a peaceful group talk.
>>>
>>> I'm not sure I understand how any kind of "integration" of DriveWire
>>> and CoCoNet (or their underlying protocols) could yield two systems
>>> that don't eventually become identical.  Right now, they're not the
>>> same by any means.  It seems that eventually the now-open DriveWire
>>> would become CoCoNet, and CoCoNet would become DriveWire.  If this
>>> happens, any competition at all would be in the EPROMs and/or the paks
>>> they ride in, and software that uses the internet abilities of either
>>> progressing network system.  I don't think the name DriveWire will
>>> always describe what it does.  I think the name CoCoNet fully
>>> describes where I'm taking the system.  These are some of the key
>>> points that come to mind when I compare the two systems and where they
>>> would otherwise be going.
>>>
>>> Here's a summary of what CoCoNet currently does:  As well as the
>>> server, the *CoCo* can mount virtual disks from the web or remote PC.
>>> CoCoNet can request web pages and files and have them returned on a
>>> mounted virtual disk.  These requests can append URL parameters, making
>>> some serious things possible from the CoCo, like live chat,
>>> multi-player games, etc. without adding any additional protocol
>>> support.  Oh, and mounting virtual ROM Paks,... done in the bitbanger
>>> version, not added to the 6551 version yet.
>>
>> I don't have the benefit of seeing your CoCoNet protocol since you have
>> not published it, so I cannot fully compare products here, but from your
>> description, it is fair to assume that your product is a superset of
>> DriveWire.
>>
>> Even so, you could still adopt the DriveWire 3 protocol for disk storage
>> and printing to remain compatible with the existing user base, and have
>> your advanced features (web page saving, etc) outside of the DriveWire
>> protocol altogether.
>>
>> Adopting the protocol in CoCoNet would be a win-win for you and for the
>> CoCo community.
>>
>> For you, it would expand the use of your product immediately to Linux
>> and Mac OS X for the disk functionality.   Do you plan on having
>> NitrOS-9 support for CoCoNet?  Instead of writing your own drivers, you
>> could adopt the DriveWire 3 protocol and not have to spend any time
>> writing drivers.  It would just "work" under NitrOS-9.  And if you chose
>> to publish your protocol, then NitrOS-9 could be made to adapt to any
>> extra features that you would bring in your protocol.
>>
>> For the CoCo community it would provide the following benefits:
>>
>> 1. HDB-DOS for DriveWire 3 users could talk to a CoCoNet server (you
>> didn't indicate if the server software would be free or not, so this may
>> not be an issue)
>> 2. CoCoNet ROM users could talk to any DriveWire 3 server under Linux,
>> Windows or Mac OS X for disk image support (DriveWire 3 servers are
>> freely available for download)
>> 3. NitrOS-9 users could boot from a NitrOS-9 disk mounted on your
>> CoCoNet server
>>
>> To enumerate the downsides of having two separate systems and protocols
>> for disk storage:
>>
>> 1. CoCoNet customers could not use DriveWire 3 WinServer, MacServer or
>> LinServer servers.
>> 2. HDB-DOS for DriveWire customers could not use the CoCoNet server
>> 3. Customers would be forced to choose between two products that have
>> similar functionality; those who don't require web pages to be loaded
>> onto their CoCo, or need NitrOS-9 support, would use HDB-DOS for
>> DriveWire.  Those who would desire the web page and ROM pak features you
>> offer would have to choose you product.
>> 4. You would have to write NitrOS-9 drivers (assuming you wanted to
>> support NitrOS-9, that is)
>>
>> This is all, of course, your decision.  For me, there is no benefit or
>> detriment to you choosing to adopt the DriveWire 3 protocol. Besides the
>> benefits that I laid out above (additional server platform support,
>> instant NitrOS-9 compatibility), the CoCo community would be the real
>> winner here, and that's really what it's all about, right?
>>
>> Is there anyone else here who would see the benefit of Roger adopting
>> the DriveWire 3 protocol for disk storage in his CoCoNet product if it
>> meant greater interoperability, greater choice and greater flexibility?
>
>In the interest of full disclosure I should point out that I am happily
> using drivewire and have little interest in switching to something else.
> I'm hoping that Roger sees the wisdom having his product and drivewire use
> the same protocol or at least he sees the wisdom in opening his protocol.
> The current coco community is to small to have a "war" between the two
> protocols. While I believe in competition I'm afraid that in this case it
> will divide the community and in the long run this will be a bad thing.
>
>Frank
>
+2 at least, Frank.  However, that could work both ways.  If Rogers code is 
clean and stable, how much work would it be to just merge them, keeping the 
best features of each?

I'm not truly interested in DriveWire, having lost some usb gear on the coco 
end of the cables I run here from Mother Nature hearing somebody call that 
stuff butter.  So I feel as if I'll have a plus, and the coco will just be 
that much better isolated from lightning damages if I replace the cable with 
bluetooth stuff.  That means I'll only have one path, where ATM, thanks to USB 
hubs, I have 2, over one cable.  That sends /p1 to here, massages it to drive 
a Brother Laser printer, and sends it back to the printer which is also 
plugged into the same usb hub on the coco's desk.  That is 2 paths via usb, 
and then I have a serial cable from the rs-232 pack to the usb adaptor, and 
that comes up here on /dev/ttyUSB2 when its powered up.  I run minicom here, 
to a shell -i /t2& on the coco3.

The only other choice I might have is to power the coco from the downstream 
side of the 1500WA UPS that runs everything else here.  That might help.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Those who have some means think that the most important thing in the
world is love.  The poor know that it is money.
		-- Gerald Brenan



From briang0671 at sbcglobal.net  Tue Mar 10 23:48:09 2009
From: briang0671 at sbcglobal.net (Brian Goers)
Date: Tue, 10 Mar 2009 22:48:09 -0500
Subject: [Coco] Do you recognize PI Day
Message-ID: <49B73479.10906@sbcglobal.net>

Since this Saturday is One of the PI days, does anyone on the list here 
have a party/celebrate around 2:00 pm in the afternoon to acknowledge 
this important number.
Why this date and time? Because PI=3.14159. That's 3-14 at 1:59 pm.
I am going to have a cake with the numbers on the circumference. ;-)
Later
Brian

-- 
 Brian Goers                                         Glenside Color Computer Club URL
 Glenside Vice-President of Special Events           http://GlensideCCC.com     

 IDE Boards are available.
 Show cost $45.00                                   The 18th Annual ?LAST? Chicago CoCoFEST!
 Includes items in the picture                      Will be held March 28 & 29 2009
                                                    Holiday Inn & Suites Elgin.



From davehazelton at comcast.net  Tue Mar 10 23:49:02 2009
From: davehazelton at comcast.net (David Hazelton)
Date: Tue, 10 Mar 2009 23:49:02 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <20090310200141.GD10800@tuxdriver.com>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>	<49B67FEF.8050406@swbell.net>	<20090310162545.30AF120A13@qs281.pair.com>	<4333B191-2A29-45E1-A337-0D1DE0EEAF3F@tee-boy.com>	<20090310185016.698C920A13@qs281.pair.com>	<68E6554E-948C-44B6-AED5-1D56427B4C3B@tee-boy.com>
	<20090310200141.GD10800@tuxdriver.com>
Message-ID: <49B734AE.8060804@comcast.net>

John W. Linville wrote:
> On Tue, Mar 10, 2009 at 02:31:10PM -0500, Boisy Pitre wrote:
>
>   
>> This is all, of course, your decision.  For me, there is no benefit or  
>> detriment to you choosing to adopt the DriveWire 3 protocol. Besides the 
>> benefits that I laid out above (additional server platform support, 
>> instant NitrOS-9 compatibility), the CoCo community would be the real 
>> winner here, and that's really what it's all about, right?
>>
>> Is there anyone else here who would see the benefit of Roger adopting  
>> the DriveWire 3 protocol for disk storage in his CoCoNet product if it  
>> meant greater interoperability, greater choice and greater flexibility?
>>     
>
> As a resident member of the open source crowd, I feel compelled
> to raise my hand. :-)  I think you have covered the major points
> benefiting the users (or "customers") of the two projects.  There is
> also the added benefit of developer cooperation -- for example,
> CoCoNet could grow printing functionality without having to spend
> development resources on the server.
>
> I'd like to commend Boisy for opening-up DriveWire sources, and I
> would also note that the DriveWire protocol has been well documented
> for some time.  IMHO everyone developing CoCo-related software could
> take that lesson to heart.  Afterall, no one is going to get rich
> off this community anyway. :-)
>
> Cooperative development is the way to go.  It exands the potential
> user base and the potential developer base, while not fragmenting
> the community any worse than it already is between RSDOS and NitrOS-9.
>
> John
>   
As my full discloser, I haven't "bought" into either.  I am looking at 
both though.  I see that since Roger has a different endgame, other than 
a Fileserver for the Coco his point.  How many times have we sat down 
and developed our own program because the canned software didn't cut 
it,  just didn't do exactly what we wanted the way we wanted.  how many 
bought VED instead of even trying TSedit.
I'm not comparing  Boisy's Drivewire to TSedit by any means,  Boisy's 
products are quality products, just that they are not what Roger 
envisions.  This reminds me of the my Vax days..Eve or Emacs.  Both very 
capable text editors,  but  (in my opinion) Emacs was more powerful or 
at least more in tune to the environment  that I was working in.  

Competition makes for better products.  If I remember right Roger's was 
working  on getting Print#-2 printing to go thru the server,  it wasn't 
in Drivewire's scope.  Shain Klammer already had a solution how he did 
it with a linux box and Frank Pittel wanted a solution.  Boisy  has a 
nitros-9 solution. ( Boisy quick question...since the DWP printers were 
daisy wheel and I'm assuming SCDWP is a daisy wheel driver, does your 
solution do graphics too or just Characters.? )  Not that I ever did  
anything outside of OS9, but  for some reason  the coco community is 
still split, between Disk Basic and OS9 (nitrOS-9). 

Now not seeing the products really close, but seeing what people have 
written. So if I'm wrong correct me. I  find Coconet more of an 
extension of Disk Basic, where HDB-DOS is a Disk Basic.  I can see why 
one would just want to add commands ...isn't that what Microware did to 
Extended Basic, instead of loading a new environment.  Now I do believe 
it would be handy for both to use an common protocol for common items; 
such as remote Disk I/O doing so could make Roger's job a lot harder; a 
Portion of his remote "networking" will not work unless you run his 
server  (Which only works on Windows).  This would make Roger's product 
look and act "sub standard" if you were to use it with a Linux server or 
a Mac server.  How many of us "hated" that Dload never worked.  kind of 
cheaped Extended Basic or the Coco 3's bit banger problems.  Things that 
worked on a Coco2 had problems on the 3.  Left me with a sour taste when 
I brought my Coco 3 home.  If Roger opened up his code and merged it 
into Drivewire.  It would become like MESS.  a good Emulator, but tied 
to too many other common machines, which makes VCC sometimes a better 
choice.

I hope Roger continues getting Coconet to what he wants Coconet to 
become.  I believe that  if he opens up his source when he releases it, 
That could benefit both the community and Roger as he has stated wants 
to bring the server to other platforms,  but this is his baby as 
Drivewire is Boisy's.  I find both products Coconet and Drivewire 3 
having a place, a different place in the coco community.  And after we 
have both products, I bet Boisy and Roger will add more features, some 
that are similiar and some that will define the differnces between the 
two products.

Now if only we could make it so we can have Coconet and HDB-DOS work 
together, so we can have both.  (What's another service on a PC anyways)

My two cents worth. 

David Hazelton





From cyberpunk at prtc.net  Wed Mar 11 00:13:13 2009
From: cyberpunk at prtc.net (RJLCyberPunk)
Date: Wed, 11 Mar 2009 00:13:13 -0400
Subject: [Coco] How about a CoCo Web Browser?
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>,
	<052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
	<49B6EB8F.1400.140A841@jdaggett.gate.net>
Message-ID: <9ADB071F55C748EDAA50841BFBAA4F5A@FANTASYWARE>

I'm sorry I thought I had made it clear that it would use or take advantage 
of thew new wireless RS232 Bluetooth cartridge that is now being sold once 
you have a blue tooth connection to a PC this PC can in turn be used as a 
server to connect to the internet. The horse has already been built in other 
words...


----- Original Message ----- 
From: <jdaggett at gate.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Tuesday, March 10, 2009 10:37 PM
Subject: Re: [Coco] How about a CoCo Web Browser?


> First off you need some means of connecting to the internet either through
> a modem or through a PC/MAC. Then you can think about a web browser.
> Can't put the cart before the horse or the cart wont go anywhere.
>
> james
>
> 



From gene.heskett at verizon.net  Wed Mar 11 00:18:31 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 11 Mar 2009 00:18:31 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <149213.60557.qm@web37303.mail.mud.yahoo.com>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
Message-ID: <200903110018.31398.gene.heskett@verizon.net>

On Tuesday 10 March 2009, Jim Hickle wrote:
>--- On Tue, 3/10/09, Frank Pittel <fwp at deepthought.com> wrote:
>>While I believe
>>in competition I'm afraid that in this case it will divide the community
>>and in
>>the long run this will be a bad thing.
>
>Right.  It's bad enough that we right-thinking people, i.e., those with SCSI
> controllers, have to endure the disunity brought about by the unwashed,
> IDE-using rabble.
>
Shhh, Jim.  We aren't supposed to let on about that. :)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Nonsense and beauty have close connections.
		-- E.M. Forster



From keeper63 at cox.net  Wed Mar 11 00:47:28 2009
From: keeper63 at cox.net (Andrew)
Date: Tue, 10 Mar 2009 21:47:28 -0700
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <mailman.24.1236742291.52173.coco@maltedmedia.com>
References: <mailman.24.1236742291.52173.coco@maltedmedia.com>
Message-ID: <49B74260.5090604@cox.net>

> Message: 1
> Date: Tue, 10 Mar 2009 16:11:38 -0400
> From: "RJLCyberPunk" <cyberpunk at prtc.net>
> Subject: [Coco] How about a CoCo Web Browser?
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Message-ID: <052725A568B14D9882FEA6B8836135BA at FANTASYWARE>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> 	reply-type=original
> 
> OK now that they have a wireless blue tooh "RS232" pak for the CoCo that 
> would and should allow it to use the PC it links too as a server to connect 
> to the internet wouldn't the next logical step be to develop a CoCo web 
> browser?
> 
> One that is at least text based with limited graphics capability like this 
> one developed for the Apple II here: 
> http://www.youtube.com/watch?v=OMzgp7xTp1k&fmt=18

I think a minimal graphical web browser (ala WAP) is possible, maybe 
written in C under OS-9 (or pure assembler, or maybe a mix of assembler 
and CBASIC-3), provided that a major part of the system is a "host 
server" program that translates the WAP-like requests into standard 
browser requests, translating the returned data into "WAP" format (or 
downloading the "WAP" format directly if the page is referenced as such) 
and delivering it back to the custom browser running on the CoCo.

Graphics could thus be made faster by translating/scaling the 
information on the host server into something fast for the CoCo. It 
wouldn't look anywhere near as good as the original, of course, given 
the graphic limits of the CoCo - but it should be somewhat 
recognizeable. It might even be possible to use "tricks" (ala Sockmaster 
and others) to allow for higher-color special displays, ie: "click here 
to see the hires version" links or buttons.

The translator software would probably be best written using Python, 
Perl or even possibly PHP (or a combo of the three), running under *nix 
(Windows users could run it under Cygwin). I don't think C would be 
necessary, as most of the conversions of graphics and other things could 
be handled by libraries already written (usually using C) for such 
tasks. I wouldn't be surprised if there isn't already an HTML 4.0 to WAP 
converter library available; the graphics could be handled by any number 
of libraries, such as ImageMagic. Speed wouldn't be an issue for such a 
server process written in higher level languages because the grunt work 
(needing such speed) could be handled by existing libraries available as 
native compiled code.

Heck - I wish I had the time, it sounds like it would be a fun project 
(I have all the tools and enough skill, just no time, unfortunately - I 
am in the middle of a long-term robotics project).

-- Andrew L. Ayers, Glendale, Arizona


From t.fadden at cox.net  Wed Mar 11 01:15:44 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Tue, 10 Mar 2009 22:15:44 -0700
Subject: [Coco] MediaFire
In-Reply-To: <49B74260.5090604@cox.net>
References: <mailman.24.1236742291.52173.coco@maltedmedia.com>
	<49B74260.5090604@cox.net>
Message-ID: <49B74900.2070404@cox.net>

Any body check out this site for sharing files?  Unlike the other 
popular site, the bandwidth is not limited on people without paid 
accounts, and you can start multiple files as fast as you can click 
them! It does still have a 100mb file limit for free use, and if a file 
is not touched in 30 days, it is deleted.  Pretty slick though. I tested 
it out, it it is very fast.

http://www.mediafire.com/

Tim Fadden






From mdelyea at gmail.com  Wed Mar 11 03:03:24 2009
From: mdelyea at gmail.com (mike delyea)
Date: Wed, 11 Mar 2009 03:03:24 -0400
Subject: [Coco] MediaFire
In-Reply-To: <49B74900.2070404@cox.net>
References: <mailman.24.1236742291.52173.coco@maltedmedia.com>
	<49B74260.5090604@cox.net> <49B74900.2070404@cox.net>
Message-ID: <1b52e6c80903110003u1f6eb51fp8b627829af95f369@mail.gmail.com>

Yah, I posted the "Inside OS-9 Level II.pdf" there.

On Wed, Mar 11, 2009 at 1:15 AM, Tim Fadden <t.fadden at cox.net> wrote:
> Any body check out this site for sharing files? ?Unlike the other popular
> site, the bandwidth is not limited on people without paid accounts, and you
> can start multiple files as fast as you can click them! It does still have a
> 100mb file limit for free use, and if a file is not touched in 30 days, it
> is deleted. ?Pretty slick though. I tested it out, it it is very fast.
>
> http://www.mediafire.com/
>
> Tim Fadden
>
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From devries.bob at gmail.com  Wed Mar 11 04:42:32 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Wed, 11 Mar 2009 18:42:32 +1000
Subject: [Coco] Driverwire server
Message-ID: <000901c9a225$5445ccc0$0701a8c0@master>

Boisy,

Have you ever considered writing an OS9 driverwire server, so that a hard 
disk based coco can be a file server for a diskless coco?

I'm sure a few of us have multiple coco's of various types, and would maybe 
be able to set them up this way.

Hmm, maybe I need to study the protocol, and see if I understand it enough 
to write a server in OS9 C.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/



From devries.bob at gmail.com  Wed Mar 11 04:46:30 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Wed, 11 Mar 2009 18:46:30 +1000
Subject: [Coco] Driverwire server
Message-ID: <001201c9a225$e1f92120$0701a8c0@master>

As a further thought to that...

Would it be feasable to allow the whole hard disk on the server coco be used 
as the file system for the client coco? I'm thinking /H0@ here.

Needless to say, there's a chance that only one hard (or virtual) drive 
could be used in this manner.
--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Bob Devries" <devries.bob at gmail.com>
To: <coco at maltedmedia.com>
Sent: Wednesday, March 11, 2009 6:42 PM
Subject: Driverwire server


> Boisy,
>
> Have you ever considered writing an OS9 driverwire server, so that a hard 
> disk based coco can be a file server for a diskless coco?
>
> I'm sure a few of us have multiple coco's of various types, and would 
> maybe be able to set them up this way.
>
> Hmm, maybe I need to study the protocol, and see if I understand it enough 
> to write a server in OS9 C.
>
> --
> Regards, Bob Devries, Dalby, Queensland, Australia
>
> Isaiah 50:4 The sovereign Lord has given me
> the capacity to be his spokesman,
> so that I know how to help the weary.
>
> website: http://www.home.gil.com.au/~bdevasl
> my blog: http://bdevries.invigorated.org/
> 



From boisy at tee-boy.com  Wed Mar 11 06:14:25 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Wed, 11 Mar 2009 05:14:25 -0500
Subject: [Coco] Driverwire server
In-Reply-To: <001201c9a225$e1f92120$0701a8c0@master>
References: <001201c9a225$e1f92120$0701a8c0@master>
Message-ID: <DA575FEB-25A2-4404-8620-E142637A9772@tee-boy.com>

On Mar 11, 2009, at 3:46 AM, Bob Devries wrote:

> As a further thought to that...
>
> Would it be feasable to allow the whole hard disk on the server coco  
> be used as the file system for the client coco? I'm thinking /H0@  
> here.
>
> Needless to say, there's a chance that only one hard (or virtual)  
> drive could be used in this manner.

Bob,

The only technical hurdle that I can see in your idea is that the  
server CoCo would have to respond to requests from a client CoCo at  
115,200bps under NitrOS-9 at a moment's notice.  The DriveWire  
protocol is designed to expect a server which will not loose any  
incoming data from the CoCo when *it* wants to get a sector, write a  
sector etc.  Another CoCo running OS-9 would have to spend a lot of  
time watching the bit banger to see when data would arrive, and that  
would slow NitrOS-9 on the server CoCo down considerably.  Writing a  
server in assembly for BASIC would probably work better since there  
would be no expectation for multi-tasking in that environment, and the  
server CoCo could spend all its time waiting for the client CoCo to  
send requests.

I'm not trying to discourage you from writing something, just be aware  
that this would be an issue that you would have to find some way to  
work around.

On a related note, an OSK machine would probably have enough hardware  
and software horsepower to act as a server, assuming its serial ports  
can attain 115,200 bps.  I don't recall the MM/1 being able to drive  
its ports that high, but the AT306 certainly can.

Good luck, and let us know what you come up with.

> --
> Regards, Bob Devries, Dalby, Queensland, Australia
>
> Isaiah 50:4 The sovereign Lord has given me
> the capacity to be his spokesman,
> so that I know how to help the weary.
>
> website: http://www.home.gil.com.au/~bdevasl
> my blog: http://bdevries.invigorated.org/
>
> ----- Original Message ----- From: "Bob Devries" <devries.bob at gmail.com 
> >
> To: <coco at maltedmedia.com>
> Sent: Wednesday, March 11, 2009 6:42 PM
> Subject: Driverwire server
>
>
>> Boisy,
>>
>> Have you ever considered writing an OS9 driverwire server, so that  
>> a hard disk based coco can be a file server for a diskless coco?
>>
>> I'm sure a few of us have multiple coco's of various types, and  
>> would maybe be able to set them up this way.
>>
>> Hmm, maybe I need to study the protocol, and see if I understand it  
>> enough to write a server in OS9 C.
>>
>> --
>> Regards, Bob Devries, Dalby, Queensland, Australia
>>
>> Isaiah 50:4 The sovereign Lord has given me
>> the capacity to be his spokesman,
>> so that I know how to help the weary.
>>
>> website: http://www.home.gil.com.au/~bdevasl
>> my blog: http://bdevries.invigorated.org/
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From n6il at ocs.net  Wed Mar 11 11:50:01 2009
From: n6il at ocs.net (Michael Furman)
Date: Wed, 11 Mar 2009 08:50:01 -0700
Subject: [Coco] Do you recognize PI Day
In-Reply-To: <49B73479.10906@sbcglobal.net>
References: <49B73479.10906@sbcglobal.net>
Message-ID: <91EF1B1C-2F20-481F-8345-2F6D004032B1@ocs.net>

I am going to two different SFBay events on PI Day:

- Electronics Flea Market @De Anza College http://www.electronicsfleamarket.com/

- Super Happy Dev House #31 http://superhappydevhouse.org/ - I should  
start bringing a Coco to this event :)

On Mar 10, 2009, at 8:48 PM, Brian Goers wrote:

> Since this Saturday is One of the PI days, does anyone on the list  
> here have a party/celebrate around 2:00 pm in the afternoon to  
> acknowledge this important number.
> Why this date and time? Because PI=3.14159. That's 3-14 at 1:59 pm.
> I am going to have a cake with the numbers on the circumference. ;-)
> Later
> Brian
>
> -- 
> Brian Goers                                         Glenside Color  
> Computer Club URL
> Glenside Vice-President of Special Events           http://GlensideCCC.com
> IDE Boards are available.
> Show cost $45.00                                   The 18th Annual  
> ?LAST? Chicago CoCoFEST!
> Includes items in the picture                      Will be held  
> March 28 & 29 2009
>                                                   Holiday Inn &  
> Suites Elgin.
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From jlhickle at yahoo.com  Wed Mar 11 11:59:13 2009
From: jlhickle at yahoo.com (Jim Hickle)
Date: Wed, 11 Mar 2009 08:59:13 -0700 (PDT)
Subject: [Coco] Do you recognize PI Day
In-Reply-To: <49B73479.10906@sbcglobal.net>
Message-ID: <556629.75624.qm@web37303.mail.mud.yahoo.com>


I'm waiting for July 22nd.






      


From cwgordon at carolina.rr.com  Wed Mar 11 12:59:11 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Wed, 11 Mar 2009 11:59:11 -0500
Subject: [Coco] MediaFire
In-Reply-To: <1b52e6c80903110003u1f6eb51fp8b627829af95f369@mail.gmail.com>
References: <mailman.24.1236742291.52173.coco@maltedmedia.com>	<49B74260.5090604@cox.net>
	<49B74900.2070404@cox.net>
	<1b52e6c80903110003u1f6eb51fp8b627829af95f369@mail.gmail.com>
Message-ID: <004401c9a26a$b3bf1f90$1b3d5eb0$@rr.com>

How do we find this file?

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of mike delyea
> Sent: Wednesday, March 11, 2009 2:03 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] MediaFire
> 
> Yah, I posted the "Inside OS-9 Level II.pdf" there.
> 



From Rich.Ries at Honeywell.com  Wed Mar 11 12:14:51 2009
From: Rich.Ries at Honeywell.com (Ries, Rich (NY80))
Date: Wed, 11 Mar 2009 12:14:51 -0400
Subject: [Coco] Coco Digest, Vol 70, Issue 32
In-Reply-To: <mailman.31.1236780016.288.coco@maltedmedia.com>
References: <mailman.31.1236780016.288.coco@maltedmedia.com>
Message-ID: <5AE7680A1972BC48AF472EE23543615F0104CD12@DE08EV808.global.ds.honeywell.com>

Sorry, I am going to have a pizza pie at 15.9 hours on Saturday. (3:54
PM EDT)

Or maybe party from 1:59 PM 'til 3:54 PM!

--Rich

-----Original Message-----
----------------------------------------------------------------------

Message: 1
Date: Tue, 10 Mar 2009 22:48:09 -0500
From: Brian Goers <briang0671 at sbcglobal.net>
Subject: [Coco] Do you recognize PI Day
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Message-ID: <49B73479.10906 at sbcglobal.net>
Content-Type: text/plain; charset=windows-1252; format=flowed

Since this Saturday is One of the PI days, does anyone on the list here 
have a party/celebrate around 2:00 pm in the afternoon to acknowledge 
this important number.
Why this date and time? Because PI=3.14159. That's 3-14 at 1:59 pm.
I am going to have a cake with the numbers on the circumference. ;-)
Later
Brian



From linville at tuxdriver.com  Wed Mar 11 14:28:03 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Wed, 11 Mar 2009 14:28:03 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <49B6EB8F.1400.140A841@jdaggett.gate.net>
References: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
	<49B6EB8F.1400.140A841@jdaggett.gate.net>
Message-ID: <20090311182803.GE8761@tuxdriver.com>

On Tue, Mar 10, 2009 at 10:37:03PM -0400, jdaggett at gate.net wrote:
> First off you need some means of connecting to the internet either through 
> a modem or through a PC/MAC. Then you can think about a web browser. 
> Can't put the cart before the horse or the cart wont go anywhere. 

I think he was presuming to use the "get any file via http" feature
of CoCoNet to account for the communications piece...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


From linville at tuxdriver.com  Wed Mar 11 14:39:46 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Wed, 11 Mar 2009 14:39:46 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <200903110018.31398.gene.heskett@verizon.net>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903110018.31398.gene.heskett@verizon.net>
Message-ID: <20090311183946.GF8761@tuxdriver.com>

On Wed, Mar 11, 2009 at 12:18:31AM -0400, Gene Heskett wrote:
> On Tuesday 10 March 2009, Jim Hickle wrote:
> >--- On Tue, 3/10/09, Frank Pittel <fwp at deepthought.com> wrote:
> >>While I believe
> >>in competition I'm afraid that in this case it will divide the community
> >>and in
> >>the long run this will be a bad thing.
> >
> >Right.  It's bad enough that we right-thinking people, i.e., those with SCSI
> > controllers, have to endure the disunity brought about by the unwashed,
> > IDE-using rabble.
> >
> Shhh, Jim.  We aren't supposed to let on about that. :)

That is worth a chuckle, but in case it was intended as a serious
point...

It is one thing to require two drivers to enable using either kind of
available hardware.  After all, most people aren't building their own
hard drives, and there are reasons (including general availability)
to prefer one type over the other on an individual basis.  (FWIW,
I'd be happy to see a SATA adapter for the CoCo!)  But in that case
you are adapting to an outside reality to bring the community together
onto common platforms.

OTOH, requiring different software (both on the CoCo and on your
server) for two such similar services when they are both under
active development within the community is IMHO a waste of talent
and resources.  In this case you are forcing users to choose between
platforms or to maintain near-duplicate environments.  It just seems
unnecessary.

Make no mistake, Roger and Boisy are entitled to the fruits of their
own labor.  And everyone is entitled to support one or the other
(or both) as they so choose.  I'm just saying that we would all be
better off if these two projects could find a way to work together.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


From mdelyea at gmail.com  Wed Mar 11 15:14:14 2009
From: mdelyea at gmail.com (mike delyea)
Date: Wed, 11 Mar 2009 15:14:14 -0400
Subject: [Coco] MediaFire
In-Reply-To: <004401c9a26a$b3bf1f90$1b3d5eb0$@rr.com>
References: <mailman.24.1236742291.52173.coco@maltedmedia.com>
	<49B74260.5090604@cox.net> <49B74900.2070404@cox.net>
	<1b52e6c80903110003u1f6eb51fp8b627829af95f369@mail.gmail.com>
	<004401c9a26a$b3bf1f90$1b3d5eb0$@rr.com>
Message-ID: <1b52e6c80903111214g74b04f8yb37912b641f79e9e@mail.gmail.com>

http://www3.sympatico.ca/michaeldelyea/index.html

On Wed, Mar 11, 2009 at 12:59 PM, Bill <cwgordon at carolina.rr.com> wrote:
> How do we find this file?
>
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of mike delyea
>> Sent: Wednesday, March 11, 2009 2:03 AM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] MediaFire
>>
>> Yah, I posted the "Inside OS-9 Level II.pdf" there.
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From operator at coco3.com  Wed Mar 11 15:39:54 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 11 Mar 2009 14:39:54 -0500
Subject: [Coco] Driverwire server
In-Reply-To: <DA575FEB-25A2-4404-8620-E142637A9772@tee-boy.com>
References: <001201c9a225$e1f92120$0701a8c0@master>
	<DA575FEB-25A2-4404-8620-E142637A9772@tee-boy.com>
Message-ID: <20090311194043.A9D5620A13@qs281.pair.com>

At 05:14 AM 3/11/2009, you wrote:
would be no expectation for multi-tasking in that environment, and the
>server CoCo could spend all its time waiting for the client CoCo to
>send requests.


>I'm not trying to discourage you from writing something, just be aware
>that this would be an issue that you would have to find some way to
>work around.


Boisy, the problem is solved for one CoCo that wants to run stuff 
while monitoring the bitbanger port.

The "listening" CoCo sends a constant beat of packets to the server 
as fast as it needs to, 60 times a second, 30 times, 10, 5, 1, 
etc.  Doesn't matter that much.  It can be timed by interrupt, or 
sent periodically at certain points in in the running code.

The packet?  The smallest possible:


Tell the server to send 512 bytes from it's Transmit Buffer:
$F200

$F meaning, Send Me Some Data, and $200 meaning the block size

Or better yet.... if the packets are to be 256 bytes or less:

$F8    where $8 really means $80 for the block size

Only one packet size scheme should be adopted, ofcourse.

The client CoCo should immediately be in bit sync to expect the 
return packet.  The server always send a block back.

The server sends whatever is in it's Transmit Buffer (not to exceed 
the Expected # of bytes), followed by filler data for any remaining 
bytes if under the expected # in the stream.

Think about the scheme before commenting.  I've already done this 
under Disk BASIC using IRQ and the timer interrupts.  The flashing 
cursor just keeps on flashing like nothing's going on in the background.

The client just appends the data to a circular buffer as usual and 
the mainline code reads from the buffer at it's own speed.

You can balance the protocol by tweaking the rate at which the CoCo 
contacts the server, the # of bytes to transfer in a block

-- 
Roger Taylor

http://www.wordofthedayonline.com



From gene.heskett at verizon.net  Wed Mar 11 15:42:43 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 11 Mar 2009 15:42:43 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <20090311183946.GF8761@tuxdriver.com>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903110018.31398.gene.heskett@verizon.net>
	<20090311183946.GF8761@tuxdriver.com>
Message-ID: <200903111542.43245.gene.heskett@verizon.net>

On Wednesday 11 March 2009, John W. Linville wrote:
>On Wed, Mar 11, 2009 at 12:18:31AM -0400, Gene Heskett wrote:
>> On Tuesday 10 March 2009, Jim Hickle wrote:
>> >--- On Tue, 3/10/09, Frank Pittel <fwp at deepthought.com> wrote:
>> >>While I believe
>> >>in competition I'm afraid that in this case it will divide the community
>> >>and in
>> >>the long run this will be a bad thing.
>> >
>> >Right.  It's bad enough that we right-thinking people, i.e., those with
>> > SCSI controllers, have to endure the disunity brought about by the
>> > unwashed, IDE-using rabble.
>>
>> Shhh, Jim.  We aren't supposed to let on about that. :)
>
>That is worth a chuckle, but in case it was intended as a serious
>point...
>
>It is one thing to require two drivers to enable using either kind of
>available hardware.  After all, most people aren't building their own
>hard drives, and there are reasons (including general availability)
>to prefer one type over the other on an individual basis.  (FWIW,
>I'd be happy to see a SATA adapter for the CoCo!)  But in that case
>you are adapting to an outside reality to bring the community together
>onto common platforms.

I agree, we really should be using one or the other.

But school is in session for a moment folks.  I get down and dirty here.

The legendarily fickle scsi interface doesn't have to be, if so darned many 
compromises weren't inherent in the average setup.
1) SCSI is a wired OR interface, built on the TTL signal level specs, eg 
anything below .60 volts is guaranteed to be a logic zero, and anything above 
2.4 volts is guaranteed to be a logic one.  In between, its a gray area.

And to remove as much cable ringing as can be done by terminating the ends 
(only) of the cable with something loosely representing the characteristic 
impedance of the cable itself was the general idea, it is in fact a 
transmission line and can have what the hams would call a high VSWR.

2)  That impedance runs, in the common flat ribbon cable with every other 
conductor in the ribbon being a ground, is about, give or take 10%, of 120 
ohms when viewed as a transmission line.  And since the specs allow for a 
nearly 40 meter cable, using logic devices that can respond to a 5ns noise 
pulse, that termination is critical.

3) Unforch the common passive terminator is a 220 ohm r connected to the 5 
volt line, in series with a 330 ohm r connected to ground. The logic line is 
connected to the junction of the 2 r's, and was INTENDED to sit at about 3.0 
volts even, which gives a 600 mv noise margin in the logic 1 state.

4) How ever, as an afterthought, they then added a diode to the top of the 
resistor network to prevent the sharing of the 5 volt logic supplies when the 
power to one or the other was turned off.  But nobody warned them the diode 
should be a very low voltage forward drop type, such as a schotkey.  So all 
the scsi cards built use a common, fairly high currant silicon diode, which 
brings the effective supply voltage down to the 4.3 to 4.4 volt range due to 
its forward drop.

5) Ok, so whats the resting logic 1 voltage now?  Given precise resistors, 
which will never happen as they are usually +-10% or more, the voltage is now 
2.61 volts.  That has reduced the noise margin from 600mv to 210mv, and the 
circuit begins to get flaky.  Add in that most power supplies age low, and are 
only making 4.88 volts when they are a year old, and there goes most of the 
remaining noise margin.

And guess what, then we are sacrificing virgins and hiring rain dancers to 
make it work.

OR, designing with active terms, which are effectively a very high powered op-
amp whose output is a regulated 3.0 volts, it can src or sink large currents 
as long as the average is low so it doesn't get too hot.  And all the term 
resistors are 120 ohms and tied to that regulated 3.0 volts.  This alleviates 
99% of the SCSI problems right there.

6) But IDE and ATAPI have essentially the same problems too, which is why the 
IDE interface specs say the Maximum cable length is 18".  And they have slowed 
the logic enough it mostly ignores the very closely spaced echos even such a 
short cable suffers from.

I think SATA is going to be around for a while, so any new drive interfaces 
should be SATA.  But that is another horse entirely I haven't even petted.  
But in the case of the coco's, that short IDE/ATAPI cable means you either 
repack the coco, or figure out how to park a hard drive very close to the mpi 
the interface is plugged into.

7) I see it as SCSI at least, was intended to be used with cables long enough 
to reach a drive in a coco usage situation. OTOH, with those teeny lappy 
drives at 100GB now, one of those could be attached to the interface card 
itself with a 3" cable and should work like a dream on that length of cable.

I could easily take the 40GB out of a 1 touch case and mount it directly on an 
ide interface, and I'd probably have the coco with the biggest hard drive in 
this group!  As is, its a now very elderly Seagate Hawk of 1GB.  It will do 
for me.

Test time is tomorrow afternoon. :-)

>OTOH, requiring different software (both on the CoCo and on your
>server) for two such similar services when they are both under
>active development within the community is IMHO a waste of talent
>and resources.  In this case you are forcing users to choose between
>platforms or to maintain near-duplicate environments.  It just seems
>unnecessary.
>
>Make no mistake, Roger and Boisy are entitled to the fruits of their
>own labor.  And everyone is entitled to support one or the other
>(or both) as they so choose.  I'm just saying that we would all be
>better off if these two projects could find a way to work together.

That would be the ideal situation.  But that is not our choice, its between 
the fellows with a dog in this 'fight'. :)

On a secondary note, the usb bluetooth keys have arrived, and I'm a bit 
confused as the kernel doesn't seem to recognize the makers code & doesn't 
load the right drivers for it.


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yow!  We're going to a new disco!



From linville at tuxdriver.com  Wed Mar 11 16:12:15 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Wed, 11 Mar 2009 16:12:15 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <200903111542.43245.gene.heskett@verizon.net>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903110018.31398.gene.heskett@verizon.net>
	<20090311183946.GF8761@tuxdriver.com>
	<200903111542.43245.gene.heskett@verizon.net>
Message-ID: <20090311201215.GH8761@tuxdriver.com>

On Wed, Mar 11, 2009 at 03:42:43PM -0400, Gene Heskett wrote:

> On a secondary note, the usb bluetooth keys have arrived, and I'm a bit 
> confused as the kernel doesn't seem to recognize the makers code & doesn't 
> load the right drivers for it.

Doh!  That sucks...  What is the USB ID?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


From linville at tuxdriver.com  Wed Mar 11 16:25:35 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Wed, 11 Mar 2009 16:25:35 -0400
Subject: [Coco] DriveWire 3 Updates
In-Reply-To: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
References: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
Message-ID: <20090311202535.GI8761@tuxdriver.com>

On Sun, Mar 08, 2009 at 05:28:14PM -0500, Boisy Pitre wrote:

> Also, DriveWire 3 is now officially part of the NitrOS-9 Project.  The  
> source is available for your perusal.

Did you move nitros9?  I checked-out the CVS repository from
SourceForge and I can't find any DriveWire stuff.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


From boisy at tee-boy.com  Wed Mar 11 16:33:21 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Wed, 11 Mar 2009 15:33:21 -0500
Subject: [Coco] Driverwire server
In-Reply-To: <20090311194043.A9D5620A13@qs281.pair.com>
References: <001201c9a225$e1f92120$0701a8c0@master>
	<DA575FEB-25A2-4404-8620-E142637A9772@tee-boy.com>
	<20090311194043.A9D5620A13@qs281.pair.com>
Message-ID: <79CCFAE9-7332-44EF-A69F-445551621E8D@tee-boy.com>

On Mar 11, 2009, at 2:39 PM, Roger Taylor wrote:

> Boisy, the problem is solved for one CoCo that wants to run stuff  
> while monitoring the bitbanger port.
>
> The "listening" CoCo sends a constant beat of packets to the server  
> as fast as it needs to, 60 times a second, 30 times, 10, 5, 1, etc.   
> Doesn't matter that much.  It can be timed by interrupt, or sent  
> periodically at certain points in in the running code.
>
> The packet?  The smallest possible:
>
>
> Tell the server to send 512 bytes from it's Transmit Buffer:
> $F200
>
> $F meaning, Send Me Some Data, and $200 meaning the block size
>
> Or better yet.... if the packets are to be 256 bytes or less:
>
> $F8    where $8 really means $80 for the block size
>
> Only one packet size scheme should be adopted, ofcourse.
>
> The client CoCo should immediately be in bit sync to expect the  
> return packet.  The server always send a block back.
>
> The server sends whatever is in it's Transmit Buffer (not to exceed  
> the Expected # of bytes), followed by filler data for any remaining  
> bytes if under the expected # in the stream.
>
> Think about the scheme before commenting.  I've already done this  
> under Disk BASIC using IRQ and the timer interrupts.  The flashing  
> cursor just keeps on flashing like nothing's going on in the  
> background.
>
> The client just appends the data to a circular buffer as usual and  
> the mainline code reads from the buffer at it's own speed.
>
> You can balance the protocol by tweaking the rate at which the CoCo  
> contacts the server, the # of bytes to transfer in a block

Roger,

This is a good approach.  Some time back, I tested a similar scheme  
(not under NitrOS-9) and had acceptable results.

In NitrOS-9, though,  it gets a little touchy, depending on how fast  
the server can respond to the client CoCo's query.  Under NitrOS-9, an  
SCF driver could be written which would hook into the F$VIRQ (virtual  
interrupt) vector.  This is called by Clock at a rate of 60 times per  
second; for the bitbanger, the response back from the server would  
have to be quick, because the driver could not afford to wait very  
long in its IRQ routine for a timeout condition.

It's an interesting problem, but with the right protocol and a little  
testing, it could probably be pulled off under NitrOS-9 without being  
detrimental to the responsiveness of the operating system.

Boisy




From boisy at tee-boy.com  Wed Mar 11 16:33:49 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Wed, 11 Mar 2009 15:33:49 -0500
Subject: [Coco] DriveWire 3 Updates
In-Reply-To: <20090311202535.GI8761@tuxdriver.com>
References: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
	<20090311202535.GI8761@tuxdriver.com>
Message-ID: <FAFA20F6-D5D7-49B5-B7C2-7E62BB9950C2@tee-boy.com>

John,

It's in there.  See nitros9/level1/modules/rbdw3.asm, nitros9/level1/ 
modules/dw3.asm, etc.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com

On Mar 11, 2009, at 3:25 PM, John W. Linville wrote:

> On Sun, Mar 08, 2009 at 05:28:14PM -0500, Boisy Pitre wrote:
>
>> Also, DriveWire 3 is now officially part of the NitrOS-9 Project.   
>> The
>> source is available for your perusal.
>
> Did you move nitros9?  I checked-out the CVS repository from
> SourceForge and I can't find any DriveWire stuff.
>
> John
> -- 
> John W. Linville		Someday the world will need a hero, and you
> linville at tuxdriver.com			might be all we have.  Be ready.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From johnstrong at hotmail.com  Wed Mar 11 16:43:02 2009
From: johnstrong at hotmail.com (John Strong)
Date: Wed, 11 Mar 2009 16:43:02 -0400
Subject: [Coco] Cocofest
In-Reply-To: <mailman.31.1236780016.288.coco@maltedmedia.com>
References: <mailman.31.1236780016.288.coco@maltedmedia.com>
Message-ID: <BLU110-W10800987FCDB2AFA670B97DF9E0@phx.gbl>


FYI

We just made our Cocofest reservations. See you there :)

John & Shirley Strong 

aka StrongWare





From jdaggett at gate.net  Wed Mar 11 17:23:51 2009
From: jdaggett at gate.net (jdaggett at gate.net)
Date: Wed, 11 Mar 2009 17:23:51 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <9ADB071F55C748EDAA50841BFBAA4F5A@FANTASYWARE>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>,
	<9ADB071F55C748EDAA50841BFBAA4F5A@FANTASYWARE>
Message-ID: <49B7F3A7.31295.667E4@jdaggett.gate.net>

On 11 Mar 2009 at 0:13, RJLCyberPunk wrote:

> I'm sorry I thought I had made it clear that it would use or take
> advantage of thew new wireless RS232 Bluetooth cartridge that is now
> being sold once you have a blue tooth connection to a PC this PC can
> in turn be used as a server to connect to the internet. The horse has
> already been built in other words...
> 
> 

BT to serial albeit slow it will work. About as a fast as 56K dial up. 

BT to USB would be better. 

After being on DSL for over five years there is no way I want to go back to 
dial up speeds. Not even fro the novalty of a Coco3 having a browser. 

just my thouhts

james
> ----- Original Message ----- 
> From: <jdaggett at gate.net>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Tuesday, March 10, 2009 10:37 PM Subject: Re: [Coco] How about a
> CoCo Web Browser?
> 
> 
> > First off you need some means of connecting to the internet either
> > through a modem or through a PC/MAC. Then you can think about a web
> > browser. Can't put the cart before the horse or the cart wont go
> > anywhere.
> >
> > james
> >
> > 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco




From jdaggett at gate.net  Wed Mar 11 17:30:27 2009
From: jdaggett at gate.net (jdaggett at gate.net)
Date: Wed, 11 Mar 2009 17:30:27 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <20090311182803.GE8761@tuxdriver.com>
References: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>,
	<49B6EB8F.1400.140A841@jdaggett.gate.net>,
	<20090311182803.GE8761@tuxdriver.com>
Message-ID: <49B7F533.2027.C7583@jdaggett.gate.net>

On 11 Mar 2009 at 14:28, John W. Linville wrote:

> On Tue, Mar 10, 2009 at 10:37:03PM -0400, jdaggett at gate.net wrote: >
> First off you need some means of connecting to the internet either
> through > a modem or through a PC/MAC. Then you can think about a web
> browser. > Can't put the cart before the horse or the cart wont go
> anywhere. 
> 
> I think he was presuming to use the "get any file via http" feature of
> CoCoNet to account for the communications piece...
> 
> John

Yes that would work if you don't mind 56K dial up speeds. 

Better off would be to have a dedicated hardware that floated on the buss 
that did all the TCP/IP stuff and hooked up to a router to do the PPPOE 
stuff. It would be faster. 

Sorry I am not thrilled with dial up speeds for internet connections. Even on  
Coco3. Roger's BT and Boisey's Drivewire are fine products for what they 
do and do best. Trying to put web browser traffic over it to a PC or a MAC 
to gain internet is not efficient or cost effective in my opinion. 


just my thoughts.  


james




> John W. Linville		Someday the world will need a hero, and you
> linville at tuxdriver.com			might be all we have.  Be ready.
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco




From t.fadden at cox.net  Wed Mar 11 17:31:02 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Wed, 11 Mar 2009 14:31:02 -0700
Subject: [Coco] MediaFire
In-Reply-To: <1b52e6c80903111214g74b04f8yb37912b641f79e9e@mail.gmail.com>
References: <mailman.24.1236742291.52173.coco@maltedmedia.com>	<49B74260.5090604@cox.net>
	<49B74900.2070404@cox.net>	<1b52e6c80903110003u1f6eb51fp8b627829af95f369@mail.gmail.com>	<004401c9a26a$b3bf1f90$1b3d5eb0$@rr.com>
	<1b52e6c80903111214g74b04f8yb37912b641f79e9e@mail.gmail.com>
Message-ID: <49B82D96.9010505@cox.net>

Sweet!   I didn't check it out last time you sent the link, as I already 
had a copy.  But I went and took a look.  I like your link page! great!

Tim

mike delyea wrote:
> http://www3.sympatico.ca/michaeldelyea/index.html
>
> On Wed, Mar 11, 2009 at 12:59 PM, Bill <cwgordon at carolina.rr.com> wrote:
>   
>> How do we find this file?
>>
>>     
>>> -----Original Message-----
>>> From: coco-bounces at maltedmedia.com [mailto:coco-
>>> bounces at maltedmedia.com] On Behalf Of mike delyea
>>> Sent: Wednesday, March 11, 2009 2:03 AM
>>> To: CoCoList for Color Computer Enthusiasts
>>> Subject: Re: [Coco] MediaFire
>>>
>>> Yah, I posted the "Inside OS-9 Level II.pdf" there.
>>>
>>>       
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>     
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From linville at tuxdriver.com  Wed Mar 11 17:56:22 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Wed, 11 Mar 2009 17:56:22 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <49B7F533.2027.C7583@jdaggett.gate.net>
References: <20090311182803.GE8761@tuxdriver.com>
	<49B7F533.2027.C7583@jdaggett.gate.net>
Message-ID: <20090311215622.GB20056@tuxdriver.com>

On Wed, Mar 11, 2009 at 05:30:27PM -0400, jdaggett at gate.net wrote:
> On 11 Mar 2009 at 14:28, John W. Linville wrote:
> 
> > On Tue, Mar 10, 2009 at 10:37:03PM -0400, jdaggett at gate.net wrote: >
> > First off you need some means of connecting to the internet either
> > through > a modem or through a PC/MAC. Then you can think about a web
> > browser. > Can't put the cart before the horse or the cart wont go
> > anywhere. 
> > 
> > I think he was presuming to use the "get any file via http" feature of
> > CoCoNet to account for the communications piece...
> > 
> > John
> 
> Yes that would work if you don't mind 56K dial up speeds. 

Probably 115k or so FWIW, but I doubt the coco could eat the data
much faster than that anyway.

> Better off would be to have a dedicated hardware that floated on the buss 
> that did all the TCP/IP stuff and hooked up to a router to do the PPPOE 
> stuff. It would be faster. 

Sure, but so would just using a PC... :-)

> Sorry I am not thrilled with dial up speeds for internet connections. Even on  
> Coco3. Roger's BT and Boisey's Drivewire are fine products for what they 
> do and do best. Trying to put web browser traffic over it to a PC or a MAC 
> to gain internet is not efficient or cost effective in my opinion. 

No probably not.  But it would be a damned cool project for someone
that would enjoy that as a hobby. :-)

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


From linville at tuxdriver.com  Wed Mar 11 17:52:27 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Wed, 11 Mar 2009 17:52:27 -0400
Subject: [Coco] DriveWire 3 Updates
In-Reply-To: <FAFA20F6-D5D7-49B5-B7C2-7E62BB9950C2@tee-boy.com>
References: <E23A55E2-9210-4906-9328-3004F76FFEA3@tee-boy.com>
	<20090311202535.GI8761@tuxdriver.com>
	<FAFA20F6-D5D7-49B5-B7C2-7E62BB9950C2@tee-boy.com>
Message-ID: <20090311215226.GA20056@tuxdriver.com>

On Wed, Mar 11, 2009 at 03:33:49PM -0500, Boisy Pitre wrote:

> It's in there.  See nitros9/level1/modules/rbdw3.asm, nitros9/level1/ 
> modules/dw3.asm, etc.

Ah, thanks...I was looking for a DriveWire directory or somesuch... :-)

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


From t.fadden at cox.net  Wed Mar 11 18:19:57 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Wed, 11 Mar 2009 15:19:57 -0700
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <20090311215622.GB20056@tuxdriver.com>
References: <20090311182803.GE8761@tuxdriver.com>	<49B7F533.2027.C7583@jdaggett.gate.net>
	<20090311215622.GB20056@tuxdriver.com>
Message-ID: <49B8390D.4060603@cox.net>

What I think would be the best thing about it is being able to download 
files text/bin, C source etc from the various coco sites directly to the 
coco, and save them on a hd or floppy to run, compile etc, eliminating 
the .dsk images etc.   Or even cooler yet create a coco browser with a 
memory based download area to save .dsk images, and then the ability to 
write them out to a real coco floppy!  use the PC for a network 
apliance, and do everything on the COCO! Now were talking.  I don't know 
about all you speed readers out there, but I can't read much faster than 
300 baud any way! ha ha ha :-)

Tim



John W. Linville wrote:
> On Wed, Mar 11, 2009 at 05:30:27PM -0400, jdaggett at gate.net wrote:
>   
>> On 11 Mar 2009 at 14:28, John W. Linville wrote:
>>
>>     
>>> On Tue, Mar 10, 2009 at 10:37:03PM -0400, jdaggett at gate.net wrote: >
>>> First off you need some means of connecting to the internet either
>>> through > a modem or through a PC/MAC. Then you can think about a web
>>> browser. > Can't put the cart before the horse or the cart wont go
>>> anywhere. 
>>>
>>> I think he was presuming to use the "get any file via http" feature of
>>> CoCoNet to account for the communications piece...
>>>
>>> John
>>>       
>> Yes that would work if you don't mind 56K dial up speeds. 
>>     
>
> Probably 115k or so FWIW, but I doubt the coco could eat the data
> much faster than that anyway.
>
>   
>> Better off would be to have a dedicated hardware that floated on the buss 
>> that did all the TCP/IP stuff and hooked up to a router to do the PPPOE 
>> stuff. It would be faster. 
>>     
>
> Sure, but so would just using a PC... :-)
>
>   
>> Sorry I am not thrilled with dial up speeds for internet connections. Even on  
>> Coco3. Roger's BT and Boisey's Drivewire are fine products for what they 
>> do and do best. Trying to put web browser traffic over it to a PC or a MAC 
>> to gain internet is not efficient or cost effective in my opinion. 
>>     
>
> No probably not.  But it would be a damned cool project for someone
> that would enjoy that as a hobby. :-)
>
> John
>   



From operator at coco3.com  Wed Mar 11 18:43:34 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 11 Mar 2009 17:43:34 -0500
Subject: [Coco] Driverwire server
In-Reply-To: <79CCFAE9-7332-44EF-A69F-445551621E8D@tee-boy.com>
References: <001201c9a225$e1f92120$0701a8c0@master>
	<DA575FEB-25A2-4404-8620-E142637A9772@tee-boy.com>
	<20090311194043.A9D5620A13@qs281.pair.com>
	<79CCFAE9-7332-44EF-A69F-445551621E8D@tee-boy.com>
Message-ID: <20090311224422.3F42620A13@qs281.pair.com>

At 03:33 PM 3/11/2009, you wrote:

>Roger,
>
>This is a good approach.  Some time back, I tested a similar scheme
>(not under NitrOS-9) and had acceptable results.
>
>In NitrOS-9, though,  it gets a little touchy, depending on how fast
>the server can respond to the client CoCo's query.  Under NitrOS-9, an
>SCF driver could be written which would hook into the F$VIRQ (virtual
>interrupt) vector.  This is called by Clock at a rate of 60 times per
>second; for the bitbanger, the response back from the server would
>have to be quick, because the driver could not afford to wait very
>long in its IRQ routine for a timeout condition.
>
>It's an interesting problem, but with the right protocol and a little
>testing, it could probably be pulled off under NitrOS-9 without being
>detrimental to the responsiveness of the operating system.
>
>Boisy

Yes, the server has to respond quickly and if interrupts are used to 
knock on the server's door 60 times a second, I'd go with a short 
block size.  Ofcourse we all realize that the throughput drops a lot 
using a scheme like this.  It's a trade-off situation:  sit and loop 
for a start bit or run other programs while not missing anything 
"coming in on the bitbanger port".  I haven't done any throughput 
math on any of this.


-- 
Roger Taylor

http://www.wordofthedayonline.com



From gene.heskett at verizon.net  Wed Mar 11 18:50:41 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Wed, 11 Mar 2009 18:50:41 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <20090311201215.GH8761@tuxdriver.com>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903111542.43245.gene.heskett@verizon.net>
	<20090311201215.GH8761@tuxdriver.com>
Message-ID: <200903111850.41878.gene.heskett@verizon.net>

On Wednesday 11 March 2009, John W. Linville wrote:
>On Wed, Mar 11, 2009 at 03:42:43PM -0400, Gene Heskett wrote:
>> On a secondary note, the usb bluetooth keys have arrived, and I'm a bit
>> confused as the kernel doesn't seem to recognize the makers code & doesn't
>> load the right drivers for it.
>
>Doh!  That sucks...  What is the USB ID?

Bus 002 Device 005: ID 0e5e:6622

>John

Thanks John, specially if you can figure an alias. :)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
A fool-proof method for sculpting an elephant: first, get a huge block of
marble; then you chip away everything that doesn't look like an elephant.



From operator at coco3.com  Wed Mar 11 18:52:17 2009
From: operator at coco3.com (Roger Taylor)
Date: Wed, 11 Mar 2009 17:52:17 -0500
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <49B7F533.2027.C7583@jdaggett.gate.net>
References: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
	<49B6EB8F.1400.140A841@jdaggett.gate.net>
	<20090311182803.GE8761@tuxdriver.com>
	<49B7F533.2027.C7583@jdaggett.gate.net>
Message-ID: <20090311225306.2D04020A13@qs281.pair.com>

At 04:30 PM 3/11/2009, you wrote:
> > John
>
>Yes that would work if you don't mind 56K dial up speeds.

Correction in order.  With today's "56K dialup" connections, you 
almost always only get 26.4k.

The 6551 has a 115200 bps mode.   The CoCo tells the PC to fetch a 
web page, and the speed of the PC's internet connection is the speed 
used.  The data appears to the CoCo on one of the remote virtual 
disks where it can be read any way you like @ 115200 bps.  Even 
considering overhead, it's extremely faster than a dial-up experience.

-- 
Roger Taylor

http://www.wordofthedayonline.com



From cyberpunk at prtc.net  Wed Mar 11 19:49:20 2009
From: cyberpunk at prtc.net (RJLCyberPunk)
Date: Wed, 11 Mar 2009 19:49:20 -0400
Subject: [Coco] How about a CoCo Web Browser?
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>,
	<9ADB071F55C748EDAA50841BFBAA4F5A@FANTASYWARE>
	<49B7F3A7.31295.667E4@jdaggett.gate.net>
Message-ID: <D5D4DBC62543475C88E8F4F3B52BF46C@FANTASYWARE>

Frankly I have no idea how fast the new wireless buetooth "RS232" pak is, 
I'll have to check

> BT to serial albeit slow it will work. About as a fast as 56K dial up.
>
> BT to USB would be better.
>
> After being on DSL for over five years there is no way I want to go back 
> to
> dial up speeds. Not even fro the novalty of a Coco3 having a browser.
>
> just my thouhts
>
> james
>> ----- Original Message ----- 
>> From: <jdaggett at gate.net>
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Sent: Tuesday, March 10, 2009 10:37 PM Subject: Re: [Coco] How about a
>> CoCo Web Browser?
>>
>>
>> > First off you need some means of connecting to the internet either
>> > through a modem or through a PC/MAC. Then you can think about a web
>> > browser. Can't put the cart before the horse or the cart wont go
>> > anywhere.
>> >
>> > james
>> >
>> >
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> 



From diegoba at adinet.com.uy  Wed Mar 11 20:25:41 2009
From: diegoba at adinet.com.uy (Diego Barizo)
Date: Wed, 11 Mar 2009 21:25:41 -0300
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <D5D4DBC62543475C88E8F4F3B52BF46C@FANTASYWARE>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>,
	<9ADB071F55C748EDAA50841BFBAA4F5A@FANTASYWARE>	<49B7F3A7.31295.667E4@jdaggett.gate.net>
	<D5D4DBC62543475C88E8F4F3B52BF46C@FANTASYWARE>
Message-ID: <49B85685.3010308@adinet.com.uy>

Besides web access, another good reason to have a browser like program 
for the CoCo, is to be able to open HTML files, which are the real 
Portable Document File, - not that other format :-)
That was the idea behind my attempt to create what is an HTML renderer, 
not a web browser. To allow me to create a formatted text file in the 
PC, and open it in the CoCo keeping most of the formatting.

Diego

RJLCyberPunk wrote:
> Frankly I have no idea how fast the new wireless buetooth "RS232" pak 
> is, I'll have to check
>
>> BT to serial albeit slow it will work. About as a fast as 56K dial up.
>>
>> BT to USB would be better.
>>
>> After being on DSL for over five years there is no way I want to go 
>> back to
>> dial up speeds. Not even fro the novalty of a Coco3 having a browser.
>>
>> just my thouhts
>>
>> james
>>> ----- Original Message ----- From: <jdaggett at gate.net>
>>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>>> Sent: Tuesday, March 10, 2009 10:37 PM Subject: Re: [Coco] How about a
>>> CoCo Web Browser?
>>>
>>>
>>> > First off you need some means of connecting to the internet either
>>> > through a modem or through a PC/MAC. Then you can think about a web
>>> > browser. Can't put the cart before the horse or the cart wont go
>>> > anywhere.
>>> >
>>> > james
>>> >
>>> >
>>>
>>>
>>> -- 
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



From linville at tuxdriver.com  Wed Mar 11 22:16:57 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Wed, 11 Mar 2009 22:16:57 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <200903111850.41878.gene.heskett@verizon.net>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903111542.43245.gene.heskett@verizon.net>
	<20090311201215.GH8761@tuxdriver.com>
	<200903111850.41878.gene.heskett@verizon.net>
Message-ID: <20090312021657.GA20874@tuxdriver.com>

On Wed, Mar 11, 2009 at 06:50:41PM -0400, Gene Heskett wrote:
> On Wednesday 11 March 2009, John W. Linville wrote:
> >On Wed, Mar 11, 2009 at 03:42:43PM -0400, Gene Heskett wrote:
> >> On a secondary note, the usb bluetooth keys have arrived, and I'm a bit
> >> confused as the kernel doesn't seem to recognize the makers code & doesn't
> >> load the right drivers for it.
> >
> >Doh!  That sucks...  What is the USB ID?
> 
> Bus 002 Device 005: ID 0e5e:6622
> 
> >John
> 
> Thanks John, specially if you can figure an alias. :)

It looks like the btusb driver claims support for that.  It is
selected by CONFIG_BT_HCIBTUSB, which is turned-on by default in
Fedora kernels.  This is the newer HCI USB Bluetooth driver, which
supercedes the older hci_usb driver (selected by CONFIG_BT_HCIUSB).

Are you using a stock Fedora kernel?  If not, make sure you are using
CONFIG_BT_HCIBTUSB (and not CONFIG_BT_HCIUSB) in your .config file.

Hth!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


From gene.heskett at verizon.net  Thu Mar 12 00:03:41 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Thu, 12 Mar 2009 00:03:41 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <20090312021657.GA20874@tuxdriver.com>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903111850.41878.gene.heskett@verizon.net>
	<20090312021657.GA20874@tuxdriver.com>
Message-ID: <200903120003.41151.gene.heskett@verizon.net>

On Wednesday 11 March 2009, John W. Linville wrote:
>On Wed, Mar 11, 2009 at 06:50:41PM -0400, Gene Heskett wrote:
>> On Wednesday 11 March 2009, John W. Linville wrote:
>> >On Wed, Mar 11, 2009 at 03:42:43PM -0400, Gene Heskett wrote:
>> >> On a secondary note, the usb bluetooth keys have arrived, and I'm a bit
>> >> confused as the kernel doesn't seem to recognize the makers code &
>> >> doesn't load the right drivers for it.
>> >
>> >Doh!  That sucks...  What is the USB ID?
>>
>> Bus 002 Device 005: ID 0e5e:6622
>>
>> >John
>>
>> Thanks John, specially if you can figure an alias. :)
>
>It looks like the btusb driver claims support for that.

I enabled that for the last build too.

>It is
>selected by CONFIG_BT_HCIBTUSB, which is turned-on by default in
>Fedora kernels.  This is the newer HCI USB Bluetooth driver, which
>supercedes the older hci_usb driver (selected by CONFIG_BT_HCIUSB).
>
>Are you using a stock Fedora kernel?  If not, make sure you are using
>CONFIG_BT_HCIBTUSB (and not CONFIG_BT_HCIUSB) in your .config file.
>
>Hth!
>
A step in the right direction I believe.

>John

From the 2.6.29-rc7/.config
[root at coyote linux-2.6.29-rc7]# grep CONFIG_BT_HCIBTUSB .config
CONFIG_BT_HCIBTUSB=m

In fact:
[root at coyote linux-2.6.29-rc7]# grep CONFIG_BT .config
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m
CONFIG_BT_HCIBTUSB=m
CONFIG_BT_HCIBTSDIO=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIVHCI=m
# CONFIG_BTRFS_FS is not set

Humm, looks like I missed one.  Or did I, is it even related
to bluetooth stuffs?  Sounds like one of those specialty filesystems.

And on the reboot, it did create 2 more /dev/hidraw (1 & 2) devices, but no
/dev/hci* are to be found.  Am I looking for the wrong device?

Doing
[root at coyote misc]# cat /dev/hidraw2
-.4d5x<=>-.4d5x<=>-.4d5x<=>-.4d5x<=>-.4d5x<=>-.4d5x<^C <- is about 10 seconds
[root at coyote misc]# echo -n '-.4d5x<=>' >/dev/hidraw1
bash: echo: write error: Broken pipe

In fact, anything along those lines is a broken pipe.

I saw, in another message, a cli example I tried:
[root at coyote linux-2.6.29-rc7]# hciconfig hci0 version
hci0:   Type: USB
        BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1
        HCI Ver: 2.0 (0x3) HCI Rev: 0x1f4 LMP Ver: 2.0 (0x3) LMP Subver: 0x1f4
        Manufacturer: CONWISE Technology Corporation Ltd (66)

It turns out that this hciconfig has quite an extensive menu:
[root at coyote linux-2.6.29-rc7]# hciconfig --help
hciconfig - HCI device configuration utility    
Usage:                                          
        hciconfig                               
        hciconfig [-a] hciX [command]           
Commands:
        up                      Open and initialize HCI device
        down                    Close HCI device
        reset                   Reset HCI device
        rstat                   Reset statistic counters
        auth                    Enable Authentication
        noauth                  Disable Authentication
        encrypt                 Enable Encryption
        noencrypt               Disable Encryption
        piscan                  Enable Page and Inquiry scan
        noscan                  Disable scan
        iscan                   Enable Inquiry scan
        pscan                   Enable Page scan
        ptype      [type]       Get/Set default packet type
        lm         [mode]       Get/Set default link mode
        lp         [policy]     Get/Set default link policy
        name       [name]       Get/Set local name
        class      [class]      Get/Set class of device
        voice      [voice]      Get/Set voice setting
        iac        [iac]        Get/Set inquiry access code
        inqtpl     [level]      Get/Set inquiry transmit power level
        inqmode    [mode]       Get/Set inquiry mode
        inqdata    [data]       Get/Set inquiry data
        inqtype    [type]       Get/Set inquiry scan type
        inqparms   [win:int]    Get/Set inquiry scan window and interval
        pageparms  [win:int]    Get/Set page scan window and interval
        pageto     [to]         Get/Set page timeout
        afhmode    [mode]       Get/Set AFH mode
        sspmode    [mode]       Get/Set Simple Pairing Mode
        aclmtu     <mtu:pkt>    Set ACL MTU and number of packets
        scomtu     <mtu:pkt>    Set SCO MTU and number of packets
        putkey     <bdaddr>     Store link key on the device
        delkey     <bdaddr>     Delete link key from the device
        oobdata                 Display local OOB data
        commands                Display supported commands
        features                Display device features
        version                 Display version information
        revision                Display revision information

will this be helpful?  However an 'up' didn't return an error and did not 
create any new /dev/ices either.

Poking around in /sys/bus/usb/drivers/usb/2-5* with ls, I get:
[root at coyote linux-2.6.29-rc7]# ls /sys/bus/usb/drivers/usb/2-5*
/sys/bus/usb/drivers/usb/2-5:
2-5.1       bcdDevice            bDeviceSubClass  bNumConfigurations  
descriptors  ep_00      power      uevent        version
2-5:1.0     bConfigurationValue  bmAttributes     bNumInterfaces      dev          
idProduct  quirks     urbnum
2-5.3       bDeviceClass         bMaxPacketSize0  busnum              devnum       
idVendor   speed      usb_device
authorized  bDeviceProtocol      bMaxPower        configuration       driver       
maxchild   subsystem  usb_endpoint

/sys/bus/usb/drivers/usb/2-5.1:
2-5.1:1.0   bConfigurationValue  bmAttributes        bNumInterfaces  dev     
idProduct  quirks     urbnum
2-5.1:1.1   bDeviceClass         bMaxPacketSize0     busnum          devnum  
idVendor   speed      usb_device
authorized  bDeviceProtocol      bMaxPower           configuration   driver  
maxchild   subsystem  usb_endpoint
bcdDevice   bDeviceSubClass      bNumConfigurations  descriptors     ep_00   
power      uevent     version

/sys/bus/usb/drivers/usb/2-5.3:
2-5.3:1.0            bDeviceClass     bMaxPacketSize0     busnum         
devnum     idVendor  quirks     uevent        version
authorized           bDeviceProtocol  bMaxPower           configuration  
driver     maxchild  serial     urbnum
bcdDevice            bDeviceSubClass  bNumConfigurations  descriptors    ep_00      
power     speed      usb_device
bConfigurationValue  bmAttributes     bNumInterfaces      dev            
idProduct  product   subsystem  usb_endpoint

So while there doesn't seem to be a correct /dev/icename, it does seem to know 
about it.

Your turn. :)

Thanks John.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Your fault -- core dumped



From snhirsch at gmail.com  Thu Mar 12 07:19:23 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Thu, 12 Mar 2009 07:19:23 -0400 (EDT)
Subject: [Coco] Coco to PC cable
In-Reply-To: <200903111542.43245.gene.heskett@verizon.net>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903110018.31398.gene.heskett@verizon.net>
	<20090311183946.GF8761@tuxdriver.com>
	<200903111542.43245.gene.heskett@verizon.net>
Message-ID: <alpine.DEB.2.00.0903120711560.32155@duo>

On Wed, 11 Mar 2009, Gene Heskett wrote:

> But school is in session for a moment folks.  I get down and dirty here.
>
> The legendarily fickle scsi interface doesn't have to be, if so darned many
> compromises weren't inherent in the average setup.
> 1) SCSI is a wired OR interface, built on the TTL signal level specs, eg
> anything below .60 volts is guaranteed to be a logic zero, and anything above
> 2.4 volts is guaranteed to be a logic one.  In between, its a gray area.

Excellent analysis, Gene!  Thanks for taking the time to write that up. 
It's important to note that more modern LVD SCSI interfaces _always_ use 
active termination.  Between that and the additional rejection of 
common-mode noise, they tend to be hugely more reliable.

All that said, I actually have had very problems with single-ended SCSI-1 
drives over the years.  In my entire collection of vintage machines (more 
than most folks would believe can fit in one ranch house), the biggest 
PITA was an SGI Iris Indigo.  Despite conventional wisdom about always 
terminating the physical ends of the bus, it simply refused to recognize 
an external drive unless I _removed_ the terminator resistor pack from 
that unit.  Go figure.

A lot of my luck probably stems from a penchant for short cabling.  The 
only SCSI drives I own that run > 3' from the controller are an LVD 
Ultra-80 RAID enclosure hooked to an IBM ServeRAID controller.  And, for 
reasons mentioned above, this is dead reliable.

Steve


-- 


From linville at tuxdriver.com  Thu Mar 12 08:40:58 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Thu, 12 Mar 2009 08:40:58 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <200903120003.41151.gene.heskett@verizon.net>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903111850.41878.gene.heskett@verizon.net>
	<20090312021657.GA20874@tuxdriver.com>
	<200903120003.41151.gene.heskett@verizon.net>
Message-ID: <20090312124057.GA3410@tuxdriver.com>

On Thu, Mar 12, 2009 at 12:03:41AM -0400, Gene Heskett wrote:
> On Wednesday 11 March 2009, John W. Linville wrote:
> >On Wed, Mar 11, 2009 at 06:50:41PM -0400, Gene Heskett wrote:
> >> On Wednesday 11 March 2009, John W. Linville wrote:
> >> >On Wed, Mar 11, 2009 at 03:42:43PM -0400, Gene Heskett wrote:
> >> >> On a secondary note, the usb bluetooth keys have arrived, and I'm a bit
> >> >> confused as the kernel doesn't seem to recognize the makers code &
> >> >> doesn't load the right drivers for it.
> >> >
> >> >Doh!  That sucks...  What is the USB ID?
> >>
> >> Bus 002 Device 005: ID 0e5e:6622
> >>
> >> >John
> >>
> >> Thanks John, specially if you can figure an alias. :)
> >
> >It looks like the btusb driver claims support for that.
> 
> I enabled that for the last build too.
> 
> >It is
> >selected by CONFIG_BT_HCIBTUSB, which is turned-on by default in
> >Fedora kernels.  This is the newer HCI USB Bluetooth driver, which
> >supercedes the older hci_usb driver (selected by CONFIG_BT_HCIUSB).
> >
> >Are you using a stock Fedora kernel?  If not, make sure you are using
> >CONFIG_BT_HCIBTUSB (and not CONFIG_BT_HCIUSB) in your .config file.
> >
> >Hth!
> >
> A step in the right direction I believe.
> 
> >John
> 
> >From the 2.6.29-rc7/.config
> [root at coyote linux-2.6.29-rc7]# grep CONFIG_BT_HCIBTUSB .config
> CONFIG_BT_HCIBTUSB=m
> 
> In fact:
> [root at coyote linux-2.6.29-rc7]# grep CONFIG_BT .config
> CONFIG_BT=m
> CONFIG_BT_L2CAP=m
> CONFIG_BT_SCO=m
> CONFIG_BT_RFCOMM=m
> CONFIG_BT_RFCOMM_TTY=y
> CONFIG_BT_BNEP=m
> CONFIG_BT_BNEP_MC_FILTER=y
> CONFIG_BT_BNEP_PROTO_FILTER=y
> CONFIG_BT_HIDP=m
> CONFIG_BT_HCIBTUSB=m
> CONFIG_BT_HCIBTSDIO=m
> CONFIG_BT_HCIUART=m
> CONFIG_BT_HCIUART_H4=y
> CONFIG_BT_HCIUART_BCSP=y
> CONFIG_BT_HCIUART_LL=y
> CONFIG_BT_HCIBCM203X=m
> CONFIG_BT_HCIBPA10X=m
> CONFIG_BT_HCIBFUSB=m
> CONFIG_BT_HCIVHCI=m
> # CONFIG_BTRFS_FS is not set
> 
> Humm, looks like I missed one.  Or did I, is it even related
> to bluetooth stuffs?  Sounds like one of those specialty filesystems.

BTRFS is a new filesystem, hoping to eventually replace EXT4.

> And on the reboot, it did create 2 more /dev/hidraw (1 & 2) devices, but no
> /dev/hci* are to be found.  Am I looking for the wrong device?

You should be running hciconfig, looking for output similar to this:

hci0:	Type: USB
	BD Address: 00:1F:3A:32:45:71 ACL MTU: 1021:8 SCO MTU: 64:1
	UP RUNNING PSCAN 
	RX bytes:966 acl:0 sco:0 events:62 errors:0
	TX bytes:3390 acl:0 sco:0 commands:62 errors:0

FWIW, my device seems to disappear with 2.6.29-rc7-wl, but I can see
it when running the stock F10 kernel, 2.6.27.19-170.2.35.fc10.x86_64.
Perhaps it has been broken upstream, or perhaps my 2.6.29-rc7-wl config
is lacking some magic, dunno.  In any case, I'd advise you to try to
get things working with a stock Fedora kernel and then proceed from
there. :-)

Hth!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


From cwgordon at carolina.rr.com  Thu Mar 12 10:21:15 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 09:21:15 -0500
Subject: [Coco] Using PC printer
Message-ID: <008601c9a31d$cdf7adb0$69e70910$@rr.com>

Is there a way to access the PC printer with Coco? I'm using DriveWire and a
Coco2. I'd like to print some documents from within a .dsk image.

Thanks

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From cwgordon at carolina.rr.com  Thu Mar 12 10:24:14 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 09:24:14 -0500
Subject: [Coco] Run program by typing DOS
Message-ID: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>

(I wish I'd remembered to put this in the last msg)

I seem to remember that there was a way to put the name of the program you
wanted to run on a special track on the floppy and type 'DOS' to make it
run.

Does anyone remember that little piece of code?

Thanks

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784





From robert.gault at worldnet.att.net  Thu Mar 12 09:42:34 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 09:42:34 -0400
Subject: [Coco] Using PC printer
In-Reply-To: <008601c9a31d$cdf7adb0$69e70910$@rr.com>
References: <008601c9a31d$cdf7adb0$69e70910$@rr.com>
Message-ID: <49B9114A.8060609@worldnet.att.net>

Bill wrote:
> Is there a way to access the PC printer with Coco? I'm using DriveWire and a
> Coco2. I'd like to print some documents from within a .dsk image.
> 
> Thanks
> 

Theoretically yes. I doubt there is any code in DW3 HDBDOS to permit 
sending print through a PC under Basic. There is a DW3 print driver for 
NitrOS-9 which means you should be able to print when running NitrOS-9 
with the DW3 printer driver.
I tried this with a USB printer and printing did not work. I've not 
tried it with a standard parallel connection to the printer.

On the other hand if you have the .dsk image on a PC, why bother going 
through the Coco? Just extract the document on the PC and print it using 
a PC program.


From cwgordon at carolina.rr.com  Thu Mar 12 10:45:55 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 09:45:55 -0500
Subject: [Coco] Using PC printer
In-Reply-To: <49B9114A.8060609@worldnet.att.net>
References: <008601c9a31d$cdf7adb0$69e70910$@rr.com>
	<49B9114A.8060609@worldnet.att.net>
Message-ID: <008801c9a321$3ffc7e10$bff57a30$@rr.com>

Dumb question: How?

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Thursday, March 12, 2009 8:43 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Using PC printer
>
> On the other hand if you have the .dsk image on a PC, why bother going
> through the Coco? Just extract the document on the PC and print it
> using a PC program.
> 



From boisy at tee-boy.com  Thu Mar 12 09:47:26 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Thu, 12 Mar 2009 08:47:26 -0500
Subject: [Coco] Using PC printer
In-Reply-To: <49B9114A.8060609@worldnet.att.net>
References: <008601c9a31d$cdf7adb0$69e70910$@rr.com>
	<49B9114A.8060609@worldnet.att.net>
Message-ID: <57001EF8-66A7-4FFA-87D4-01E840D4469A@tee-boy.com>

On Mar 12, 2009, at 8:42 AM, Robert Gault wrote:

> Bill wrote:
>> Is there a way to access the PC printer with Coco? I'm using  
>> DriveWire and a
>> Coco2. I'd like to print some documents from within a .dsk image.
>> Thanks
>
> Theoretically yes. I doubt there is any code in DW3 HDBDOS to permit  
> sending print through a PC under Basic. There is a DW3 print driver  
> for NitrOS-9 which means you should be able to print when running  
> NitrOS-9 with the DW3 printer driver.
> I tried this with a USB printer and printing did not work. I've not  
> tried it with a standard parallel connection to the printer.

Robert,

When you say you've tried it with a USB printer and it didn't work,  
what exactly happened?

> On the other hand if you have the .dsk image on a PC, why bother  
> going through the Coco? Just extract the document on the PC and  
> print it using a PC program.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From robert.gault at worldnet.att.net  Thu Mar 12 09:47:36 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 09:47:36 -0400
Subject: [Coco] Run program by typing DOS
In-Reply-To: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>
Message-ID: <49B91278.1000104@worldnet.att.net>

Bill wrote:
> (I wish I'd remembered to put this in the last msg)
> 
> I seem to remember that there was a way to put the name of the program you
> wanted to run on a special track on the floppy and type 'DOS' to make it
> run.
> 
> Does anyone remember that little piece of code?
> 
> Thanks
> 

Take a look at Vol1Issue3 of the CoCoNutz magazine at Coco3.com. You 
will find an article on how this can be done.

Based on your other question, you should be using HDBDOS on the Coco. 
That being the case, any Basic program having the name AUTOEXEC.BAS can 
be run with the DOS command.


From cwgordon at carolina.rr.com  Thu Mar 12 11:16:03 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 10:16:03 -0500
Subject: [Coco] Run program by typing DOS
In-Reply-To: <49B91278.1000104@worldnet.att.net>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>
	<49B91278.1000104@worldnet.att.net>
Message-ID: <008901c9a325$756c7790$604566b0$@rr.com>

Hehehe, now all I need to do is get Edtasm.

Thanks

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Thursday, March 12, 2009 8:48 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Run program by typing DOS
> 
> Take a look at Vol1Issue3 of the CoCoNutz magazine at Coco3.com. You
> will find an article on how this can be done.
> 
> Based on your other question, you should be using HDBDOS on the Coco.
> That being the case, any Basic program having the name AUTOEXEC.BAS can
> be run with the DOS command.
> 



From robert.gault at worldnet.att.net  Thu Mar 12 10:31:52 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 10:31:52 -0400
Subject: [Coco] Using PC printer
In-Reply-To: <57001EF8-66A7-4FFA-87D4-01E840D4469A@tee-boy.com>
References: <008601c9a31d$cdf7adb0$69e70910$@rr.com>	<49B9114A.8060609@worldnet.att.net>
	<57001EF8-66A7-4FFA-87D4-01E840D4469A@tee-boy.com>
Message-ID: <49B91CD8.4090408@worldnet.att.net>

Boisy Pitre wrote:
> On Mar 12, 2009, at 8:42 AM, Robert Gault wrote:
> 
>> Bill wrote:
>>> Is there a way to access the PC printer with Coco? I'm using 
>>> DriveWire and a
>>> Coco2. I'd like to print some documents from within a .dsk image.
>>> Thanks
>>
>> Theoretically yes. I doubt there is any code in DW3 HDBDOS to permit 
>> sending print through a PC under Basic. There is a DW3 print driver 
>> for NitrOS-9 which means you should be able to print when running 
>> NitrOS-9 with the DW3 printer driver.
>> I tried this with a USB printer and printing did not work. I've not 
>> tried it with a standard parallel connection to the printer.
> 
> Robert,
> 
> When you say you've tried it with a USB printer and it didn't work, what 
> exactly happened?
> 
>> On the other hand if you have the .dsk image on a PC, why bother going 
>> through the Coco? Just extract the document on the PC and print it 
>> using a PC program.
>>
>> -- 

The printer is the HP Deskjet 970Cse. It is using the USB connection to 
the PC with usbprint.sys for WinXP and HP support .dlls.

LLIST does nothing under HDBDOS Basic except lock up the Coco. That was 
expected.

List filename >/p with the dw3 printer modules installed just returns to 
the prompt. Tuneport /p also runs but there is no test print on the printer.
None of the diagnostic light on the printer flash.


From robert.gault at worldnet.att.net  Thu Mar 12 10:39:24 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 10:39:24 -0400
Subject: [Coco] Using PC printer
In-Reply-To: <008801c9a321$3ffc7e10$bff57a30$@rr.com>
References: <008601c9a31d$cdf7adb0$69e70910$@rr.com>	<49B9114A.8060609@worldnet.att.net>
	<008801c9a321$3ffc7e10$bff57a30$@rr.com>
Message-ID: <49B91E9C.8060008@worldnet.att.net>

Bill wrote:
> Dumb question: How?
> 

There are several programs that can extract files from a .dsk image. 
Port.exe will work with Basic .dsk images and the program comes with the 
JVC emulator. Imgtool.exe or Wimgtool.exe come with MESS and will work 
with both Basic (.dsk) and OS-9 (.os9) images. You can get the Coco 
Tools from SourceForge Toolshed and they work with both Basic and OS-9 
disk images. http://sourceforge.net/projects/toolshed/

CoCoDSK can get files from Basic images. Look for the url in the 
Coco3.com programming forum.


From robert.gault at worldnet.att.net  Thu Mar 12 10:42:30 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 10:42:30 -0400
Subject: [Coco] Run program by typing DOS
In-Reply-To: <008901c9a325$756c7790$604566b0$@rr.com>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>	<49B91278.1000104@worldnet.att.net>
	<008901c9a325$756c7790$604566b0$@rr.com>
Message-ID: <49B91F56.2080600@worldnet.att.net>

You can get a copy of Disk EDTASM+ that will run on an emulator or on a 
real Coco if you convert the .dsk image to a real disk.
http://www.discover-net.net/~dmkeil/coco/software/cocodisk.htm

Bill wrote:
> Hehehe, now all I need to do is get Edtasm.
> 
> Thanks
> 
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Robert Gault
>> Sent: Thursday, March 12, 2009 8:48 AM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] Run program by typing DOS
>>
>> Take a look at Vol1Issue3 of the CoCoNutz magazine at Coco3.com. You
>> will find an article on how this can be done.
>>
>> Based on your other question, you should be using HDBDOS on the Coco.
>> That being the case, any Basic program having the name AUTOEXEC.BAS can
>> be run with the DOS command.
>>
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> 



From dml_68 at yahoo.com  Thu Mar 12 10:43:31 2009
From: dml_68 at yahoo.com (Derek)
Date: Thu, 12 Mar 2009 07:43:31 -0700 (PDT)
Subject: [Coco] Complete 30GB CoCo Archives Links List
Message-ID: <569671.71019.qm@web30206.mail.mud.yahoo.com>

I have had a couple of folks ask me for a complete list of the archives links that I have been working on the past few months. The Archive is now just a bit over 33GB in size. Below is the link containing the most current and complete list of our coco community's archives.

http://www.coco3.com/modules.php?name=Forums&file=viewtopic&p=4270#4270

Again thanks go out to all the folks who have sent me this material over the past year or so, many of whom are still actively scanning newsletters, creating disk images and compiling materials and then sending them to me for inclusion. If you have something you would like added send me an e-mail. I give full credit when I post or as some folks prefer I can keep your contributions anonymous. 


** Mistrust Authority. Promote Decentralization **


 


       


From gene.heskett at verizon.net  Thu Mar 12 10:53:21 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Thu, 12 Mar 2009 10:53:21 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <20090312124057.GA3410@tuxdriver.com>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903120003.41151.gene.heskett@verizon.net>
	<20090312124057.GA3410@tuxdriver.com>
Message-ID: <200903121053.21846.gene.heskett@verizon.net>

On Thursday 12 March 2009, John W. Linville wrote:
>On Thu, Mar 12, 2009 at 12:03:41AM -0400, Gene Heskett wrote:
>> On Wednesday 11 March 2009, John W. Linville wrote:
>> >On Wed, Mar 11, 2009 at 06:50:41PM -0400, Gene Heskett wrote:
>> >> On Wednesday 11 March 2009, John W. Linville wrote:
>> >> >On Wed, Mar 11, 2009 at 03:42:43PM -0400, Gene Heskett wrote:
>> >> >> On a secondary note, the usb bluetooth keys have arrived, and I'm a
>> >> >> bit confused as the kernel doesn't seem to recognize the makers code
>> >> >> & doesn't load the right drivers for it.
>> >> >
>> >> >Doh!  That sucks...  What is the USB ID?
>> >>
>> >> Bus 002 Device 005: ID 0e5e:6622
>> >>
>> >> >John
>> >>
>> >> Thanks John, specially if you can figure an alias. :)
>> >
>> >It looks like the btusb driver claims support for that.
>>
>> I enabled that for the last build too.
>>
>> >It is
>> >selected by CONFIG_BT_HCIBTUSB, which is turned-on by default in
>> >Fedora kernels.  This is the newer HCI USB Bluetooth driver, which
>> >supercedes the older hci_usb driver (selected by CONFIG_BT_HCIUSB).
>> >
>> >Are you using a stock Fedora kernel?  If not, make sure you are using
>> >CONFIG_BT_HCIBTUSB (and not CONFIG_BT_HCIUSB) in your .config file.
>> >
>> >Hth!
>>
>> A step in the right direction I believe.
>>
>> >John
>> >
>> >From the 2.6.29-rc7/.config
>>
>> [root at coyote linux-2.6.29-rc7]# grep CONFIG_BT_HCIBTUSB .config
>> CONFIG_BT_HCIBTUSB=m
>>
>> In fact:
>> [root at coyote linux-2.6.29-rc7]# grep CONFIG_BT .config
>> CONFIG_BT=m
>> CONFIG_BT_L2CAP=m
>> CONFIG_BT_SCO=m
>> CONFIG_BT_RFCOMM=m
>> CONFIG_BT_RFCOMM_TTY=y
>> CONFIG_BT_BNEP=m
>> CONFIG_BT_BNEP_MC_FILTER=y
>> CONFIG_BT_BNEP_PROTO_FILTER=y
>> CONFIG_BT_HIDP=m
>> CONFIG_BT_HCIBTUSB=m
>> CONFIG_BT_HCIBTSDIO=m
>> CONFIG_BT_HCIUART=m
>> CONFIG_BT_HCIUART_H4=y
>> CONFIG_BT_HCIUART_BCSP=y
>> CONFIG_BT_HCIUART_LL=y
>> CONFIG_BT_HCIBCM203X=m
>> CONFIG_BT_HCIBPA10X=m
>> CONFIG_BT_HCIBFUSB=m
>> CONFIG_BT_HCIVHCI=m
>> # CONFIG_BTRFS_FS is not set
>>
>> Humm, looks like I missed one.  Or did I, is it even related
>> to bluetooth stuffs?  Sounds like one of those specialty filesystems.
>
>BTRFS is a new filesystem, hoping to eventually replace EXT4.
>
>> And on the reboot, it did create 2 more /dev/hidraw (1 & 2) devices, but
>> no /dev/hci* are to be found.  Am I looking for the wrong device?
>
>You should be running hciconfig, looking for output similar to this:
>
>hci0:	Type: USB
>	BD Address: 00:1F:3A:32:45:71 ACL MTU: 1021:8 SCO MTU: 64:1
>	UP RUNNING PSCAN
>	RX bytes:966 acl:0 sco:0 events:62 errors:0
>	TX bytes:3390 acl:0 sco:0 commands:62 errors:0
>
And I get:
[root at coyote init.d]# hciconfig
hci0:   Type: USB
        BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1
        UP RUNNING PSCAN ISCAN
        RX bytes:1188 acl:0 sco:0 events:47 errors:0
        TX bytes:451 acl:0 sco:0 commands:47 errors:0

>FWIW, my device seems to disappear with 2.6.29-rc7-wl, but I can see
>it when running the stock F10 kernel, 2.6.27.19-170.2.35.fc10.x86_64.
>Perhaps it has been broken upstream, or perhaps my 2.6.29-rc7-wl config
>is lacking some magic, dunno.  In any case, I'd advise you to try to
>get things working with a stock Fedora kernel and then proceed from
>there. :-)

Looks like I need to somehow set a 'mac address' aka BD?  Or is that hard 
coded in these things?  From hciconfig's --help screen:
        putkey     <bdaddr>     Store link key on the device
        delkey     <bdaddr>     Delete link key from the device
I assume these are the commands to change it.  The question then is what to?

Should it not be something from this line in an lsusb -v:
0e5e:6622=00:0e:5e:66:22:00, and assign the 2nd one I bought to 
00:0e:5e:66:22:01 etc?  This would be roughly following the usually assigned 
MAC addressing of an ethernet card I think.

>Hth!

Yes John, except for the patently bogus 'BD' address, we at least look alike.  
So I guess I wait till Roger T's bit of gear arrives.  Its en-route someplace, 
on a donkey cart maybe. :)

>John

Thanks John.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I've found my niche.  If you're wondering why I'm not there, there was
this little hole in the bottom ...
		-- John Croll



From cwgordon at carolina.rr.com  Thu Mar 12 12:03:20 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 11:03:20 -0500
Subject: [Coco] Run program by typing DOS
In-Reply-To: <49B91F56.2080600@worldnet.att.net>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>	<49B91278.1000104@worldnet.att.net>	<008901c9a325$756c7790$604566b0$@rr.com>
	<49B91F56.2080600@worldnet.att.net>
Message-ID: <008d01c9a32c$10685010$3138f030$@rr.com>

Well, I apologize for being such a pain in the ***, but I don't see a way to
download from that page

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Thursday, March 12, 2009 9:43 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Run program by typing DOS
> 
> You can get a copy of Disk EDTASM+ that will run on an emulator or on a
> real Coco if you convert the .dsk image to a real disk.
> http://www.discover-net.net/~dmkeil/coco/software/cocodisk.htm
> 



From gene.heskett at verizon.net  Thu Mar 12 11:07:07 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Thu, 12 Mar 2009 11:07:07 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <alpine.DEB.2.00.0903120711560.32155@duo>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903111542.43245.gene.heskett@verizon.net>
	<alpine.DEB.2.00.0903120711560.32155@duo>
Message-ID: <200903121107.08118.gene.heskett@verizon.net>

On Thursday 12 March 2009, Steven Hirsch wrote:
>On Wed, 11 Mar 2009, Gene Heskett wrote:
>> But school is in session for a moment folks.  I get down and dirty here.
>>
>> The legendarily fickle scsi interface doesn't have to be, if so darned
>> many compromises weren't inherent in the average setup.
>> 1) SCSI is a wired OR interface, built on the TTL signal level specs, eg
>> anything below .60 volts is guaranteed to be a logic zero, and anything
>> above 2.4 volts is guaranteed to be a logic one.  In between, its a gray
>> area.
>
>Excellent analysis, Gene!  Thanks for taking the time to write that up.
>It's important to note that more modern LVD SCSI interfaces _always_ use
>active termination.  Between that and the additional rejection of
>common-mode noise, they tend to be hugely more reliable.
>
>All that said, I actually have had very problems with single-ended SCSI-1
>drives over the years.  In my entire collection of vintage machines (more
>than most folks would believe can fit in one ranch house), the biggest
>PITA was an SGI Iris Indigo.  Despite conventional wisdom about always
>terminating the physical ends of the bus, it simply refused to recognize
>an external drive unless I _removed_ the terminator resistor pack from
>that unit.  Go figure.

Maybe it was internal?  Or it was designed by the same folks that made the 
Amiga TrumpCard?

>A lot of my luck probably stems from a penchant for short cabling.

I had a heck of a time with only a 10" cable in an amiga once, TrumpCard 
interface.  When I got down and dirty troubleshooting that, I cut the traces 
to the termpacks and reversed the supply hook ups, the pcb was laid out wrong 
so the 220 ohmers were connected to ground.  That was easier than removing and 
reversing all the soldered in termpacks by far. TrumpCard people were first 
class jerks anyway, and I didn't miss an opportunity to call them up one last 
time and call them something.  It actually worked pretty well after that.

BTW, I am a C.E.T. since 1972. :)

>The
>only SCSI drives I own that run > 3' from the controller are an LVD
>Ultra-80 RAID enclosure hooked to an IBM ServeRAID controller.  And, for
>reasons mentioned above, this is dead reliable.

I probably have about 3 feet between Marks TC^3 controller, and that Seagate 
Hawk 1GB on mine.  The TC^3 I believe has active terms, and I know the Seagate 
is termed, but don't recall if its resistor packs or active, probably r-packs 
at it's age since it is almost old enough to buy a beer these days. :)

>Steve

Thanks Steve.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Do you like "TENDER VITTLES"?



From cwgordon at carolina.rr.com  Thu Mar 12 12:09:19 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 11:09:19 -0500
Subject: [Coco] Swap & trade
Message-ID: <008e01c9a32c$e6dcfa60$b496ef20$@rr.com>

Are there any rules in this list about posting stuff for swap & trade?

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784





From linville at tuxdriver.com  Thu Mar 12 11:04:04 2009
From: linville at tuxdriver.com (John W. Linville)
Date: Thu, 12 Mar 2009 11:04:04 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <200903121053.21846.gene.heskett@verizon.net>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903120003.41151.gene.heskett@verizon.net>
	<20090312124057.GA3410@tuxdriver.com>
	<200903121053.21846.gene.heskett@verizon.net>
Message-ID: <20090312150404.GB3410@tuxdriver.com>

On Thu, Mar 12, 2009 at 10:53:21AM -0400, Gene Heskett wrote:
> On Thursday 12 March 2009, John W. Linville wrote:

> >You should be running hciconfig, looking for output similar to this:
> >
> >hci0:	Type: USB
> >	BD Address: 00:1F:3A:32:45:71 ACL MTU: 1021:8 SCO MTU: 64:1
> >	UP RUNNING PSCAN
> >	RX bytes:966 acl:0 sco:0 events:62 errors:0
> >	TX bytes:3390 acl:0 sco:0 commands:62 errors:0
> >
> And I get:
> [root at coyote init.d]# hciconfig
> hci0:   Type: USB
>         BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1
>         UP RUNNING PSCAN ISCAN
>         RX bytes:1188 acl:0 sco:0 events:47 errors:0
>         TX bytes:451 acl:0 sco:0 commands:47 errors:0
> 
> >FWIW, my device seems to disappear with 2.6.29-rc7-wl, but I can see
> >it when running the stock F10 kernel, 2.6.27.19-170.2.35.fc10.x86_64.
> >Perhaps it has been broken upstream, or perhaps my 2.6.29-rc7-wl config
> >is lacking some magic, dunno.  In any case, I'd advise you to try to
> >get things working with a stock Fedora kernel and then proceed from
> >there. :-)
> 
> Looks like I need to somehow set a 'mac address' aka BD?  Or is that hard 
> coded in these things?  From hciconfig's --help screen:
>         putkey     <bdaddr>     Store link key on the device
>         delkey     <bdaddr>     Delete link key from the device
> I assume these are the commands to change it.  The question then is what to?
> 
> Should it not be something from this line in an lsusb -v:
> 0e5e:6622=00:0e:5e:66:22:00, and assign the 2nd one I bought to 
> 00:0e:5e:66:22:01 etc?  This would be roughly following the usually assigned 
> MAC addressing of an ethernet card I think.

Very odd -- I would definitely think that it would be hard-coded on
the device.

Anyway, I'm not sure putkey and delkey are the right commands for
changing that.  But since you probably don't have tons of Bluetooth
devices around the house, a bogus MAC address is no big deal (so long
as the device actually works).

> >Hth!
> 
> Yes John, except for the patently bogus 'BD' address, we at least look alike.  
> So I guess I wait till Roger T's bit of gear arrives.  Its en-route someplace, 
> on a donkey cart maybe. :)

I'm waiting on mine too.  Hopefully Roger will use a reputable shipper... :-)

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.


From gene.heskett at verizon.net  Thu Mar 12 11:16:48 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Thu, 12 Mar 2009 11:16:48 -0400
Subject: [Coco] Using PC printer
In-Reply-To: <49B91CD8.4090408@worldnet.att.net>
References: <008601c9a31d$cdf7adb0$69e70910$@rr.com>
	<57001EF8-66A7-4FFA-87D4-01E840D4469A@tee-boy.com>
	<49B91CD8.4090408@worldnet.att.net>
Message-ID: <200903121116.48878.gene.heskett@verizon.net>

On Thursday 12 March 2009, Robert Gault wrote:
>Boisy Pitre wrote:
>> On Mar 12, 2009, at 8:42 AM, Robert Gault wrote:
>>> Bill wrote:
>>>> Is there a way to access the PC printer with Coco? I'm using
>>>> DriveWire and a
>>>> Coco2. I'd like to print some documents from within a .dsk image.
>>>> Thanks
>>>
>>> Theoretically yes. I doubt there is any code in DW3 HDBDOS to permit
>>> sending print through a PC under Basic. There is a DW3 print driver
>>> for NitrOS-9 which means you should be able to print when running
>>> NitrOS-9 with the DW3 printer driver.
>>> I tried this with a USB printer and printing did not work. I've not
>>> tried it with a standard parallel connection to the printer.
>>
>> Robert,
>>
>> When you say you've tried it with a USB printer and it didn't work, what
>> exactly happened?
>>
>>> On the other hand if you have the .dsk image on a PC, why bother going
>>> through the Coco? Just extract the document on the PC and print it
>>> using a PC program.
>>>
>>> --
>
>The printer is the HP Deskjet 970Cse. It is using the USB connection to
>the PC with usbprint.sys for WinXP and HP support .dlls.
>
>LLIST does nothing under HDBDOS Basic except lock up the Coco. That was
>expected.
>
>List filename >/p with the dw3 printer modules installed just returns to
>the prompt. Tuneport /p also runs but there is no test print on the printer.
>None of the diagnostic light on the printer flash.

Do you see traffic on the usb-serial adaptor's leds when you do a 'list 
filename >/p'?

Also, for 9600 baud out the bitbanger, I had to use a hugely different value 
for the timer in tuneport to actually get truly 9600 baud according to my 
oscilloscope.  By a factor of about 3/1 or 1/3, I've forgotten which way now 
as it's coded into my startup file.

Also, the pl2303 based usb-serial adaptors sold by the shack are broken, use 
one with an FDTI chipset, they are very transparent and haven't dropped a byte 
on me yet.

>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
take forceful action:
	Do something that should have been done a long time ago.



From dml_68 at yahoo.com  Thu Mar 12 11:18:23 2009
From: dml_68 at yahoo.com (Derek)
Date: Thu, 12 Mar 2009 08:18:23 -0700 (PDT)
Subject: [Coco] Swap & trade
In-Reply-To: <008e01c9a32c$e6dcfa60$b496ef20$@rr.com>
Message-ID: <693599.29303.qm@web30205.mail.mud.yahoo.com>

As long as it's coco equipment or items it should be just fine.



Bill <cwgordon at carolina.rr.com> wrote: Are there any rules in this list about posting stuff for swap & trade?

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



** Mistrust Authority. Promote Decentralization **


 


       


From dml_68 at yahoo.com  Thu Mar 12 11:19:40 2009
From: dml_68 at yahoo.com (Derek)
Date: Thu, 12 Mar 2009 08:19:40 -0700 (PDT)
Subject: [Coco] Run program by typing DOS
In-Reply-To: <008d01c9a32c$10685010$3138f030$@rr.com>
Message-ID: <34536.9122.qm@web30202.mail.mud.yahoo.com>

The download links are in a java script so make sure you allow java scripts to run from that page.



Bill <cwgordon at carolina.rr.com> wrote: Well, I apologize for being such a pain in the ***, but I don't see a way to
download from that page

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Thursday, March 12, 2009 9:43 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Run program by typing DOS
> 
> You can get a copy of Disk EDTASM+ that will run on an emulator or on a
> real Coco if you convert the .dsk image to a real disk.
> http://www.discover-net.net/~dmkeil/coco/software/cocodisk.htm
> 


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



** Mistrust Authority. Promote Decentralization **


 


       


From gene.heskett at verizon.net  Thu Mar 12 11:20:03 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Thu, 12 Mar 2009 11:20:03 -0400
Subject: [Coco] Coco to PC cable
In-Reply-To: <20090312150404.GB3410@tuxdriver.com>
References: <149213.60557.qm@web37303.mail.mud.yahoo.com>
	<200903121053.21846.gene.heskett@verizon.net>
	<20090312150404.GB3410@tuxdriver.com>
Message-ID: <200903121120.03739.gene.heskett@verizon.net>

On Thursday 12 March 2009, John W. Linville wrote:
>On Thu, Mar 12, 2009 at 10:53:21AM -0400, Gene Heskett wrote:
>> On Thursday 12 March 2009, John W. Linville wrote:
>> >You should be running hciconfig, looking for output similar to this:
>> >
>> >hci0:	Type: USB
>> >	BD Address: 00:1F:3A:32:45:71 ACL MTU: 1021:8 SCO MTU: 64:1
>> >	UP RUNNING PSCAN
>> >	RX bytes:966 acl:0 sco:0 events:62 errors:0
>> >	TX bytes:3390 acl:0 sco:0 commands:62 errors:0
>>
>> And I get:
>> [root at coyote init.d]# hciconfig
>> hci0:   Type: USB
>>         BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1
>>         UP RUNNING PSCAN ISCAN
>>         RX bytes:1188 acl:0 sco:0 events:47 errors:0
>>         TX bytes:451 acl:0 sco:0 commands:47 errors:0
>>
>> >FWIW, my device seems to disappear with 2.6.29-rc7-wl, but I can see
>> >it when running the stock F10 kernel, 2.6.27.19-170.2.35.fc10.x86_64.
>> >Perhaps it has been broken upstream, or perhaps my 2.6.29-rc7-wl config
>> >is lacking some magic, dunno.  In any case, I'd advise you to try to
>> >get things working with a stock Fedora kernel and then proceed from
>> >there. :-)
>>
>> Looks like I need to somehow set a 'mac address' aka BD?  Or is that hard
>> coded in these things?  From hciconfig's --help screen:
>>         putkey     <bdaddr>     Store link key on the device
>>         delkey     <bdaddr>     Delete link key from the device
>> I assume these are the commands to change it.  The question then is what
>> to?
>>
>> Should it not be something from this line in an lsusb -v:
>> 0e5e:6622=00:0e:5e:66:22:00, and assign the 2nd one I bought to
>> 00:0e:5e:66:22:01 etc?  This would be roughly following the usually
>> assigned MAC addressing of an ethernet card I think.
>
>Very odd -- I would definitely think that it would be hard-coded on
>the device.
>
>Anyway, I'm not sure putkey and delkey are the right commands for
>changing that.  But since you probably don't have tons of Bluetooth
>devices around the house, a bogus MAC address is no big deal (so long
>as the device actually works).
>
>> >Hth!
>>
>> Yes John, except for the patently bogus 'BD' address, we at least look
>> alike. So I guess I wait till Roger T's bit of gear arrives.  Its en-route
>> someplace, on a donkey cart maybe. :)
>
>I'm waiting on mine too.  Hopefully Roger will use a reputable shipper...
> :-)
>
>John

Oooooh, that's a dig. :)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Cinemuck, n.:
	The combination of popcorn, soda, and melted chocolate which
	covers the floors of movie theaters.
		-- Rich Hall, "Sniglets"



From cwgordon at carolina.rr.com  Thu Mar 12 12:23:15 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 11:23:15 -0500
Subject: [Coco] FD-502
Message-ID: <008f01c9a32e$d949df10$8bdd9d30$@rr.com>

I was foolish enough to buy two FD-502 drives off eBay, and neither one
works. One has a cable, and the other does not. Neither has controller.

I'd like to swap both units for two bare working drives. I know this sound
stupid, but maybe someone can use the box and power supply. I want one drive
to put into my existing FD-500 and the other to put into my PC.

Thanks.

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784





From jcewy at swbell.net  Thu Mar 12 11:26:13 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Thu, 12 Mar 2009 10:26:13 -0500
Subject: [Coco] Run program by typing DOS
In-Reply-To: <008d01c9a32c$10685010$3138f030$@rr.com>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>	<49B91278.1000104@worldnet.att.net>	<008901c9a325$756c7790$604566b0$@rr.com>	<49B91F56.2080600@worldnet.att.net>
	<008d01c9a32c$10685010$3138f030$@rr.com>
Message-ID: <49B92995.5050900@swbell.net>

Bill wrote:
> Well, I apologize for being such a pain in the ***, but I don't see a way to
> download from that page
>
>   
I think the link buttons are done in Javascript, so you need to have 
that enabled in your browser...

JCE
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Robert Gault
>> Sent: Thursday, March 12, 2009 9:43 AM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] Run program by typing DOS
>>
>> You can get a copy of Disk EDTASM+ that will run on an emulator or on a
>> real Coco if you convert the .dsk image to a real disk.
>> http://www.discover-net.net/~dmkeil/coco/software/cocodisk.htm
>>
>>     
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>   



From cwgordon at carolina.rr.com  Thu Mar 12 12:39:19 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 11:39:19 -0500
Subject: [Coco] Run program by typing DOS
In-Reply-To: <49B91F56.2080600@worldnet.att.net>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>	<49B91278.1000104@worldnet.att.net>	<008901c9a325$756c7790$604566b0$@rr.com>
	<49B91F56.2080600@worldnet.att.net>
Message-ID: <009001c9a331$17a4efa0$46eecee0$@rr.com>

They are all .dmk images. And it downloaded as 26-3254.ace

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Thursday, March 12, 2009 9:43 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Run program by typing DOS
> 
> You can get a copy of Disk EDTASM+ that will run on an emulator or on a
> real Coco if you convert the .dsk image to a real disk.
> http://www.discover-net.net/~dmkeil/coco/software/cocodisk.htm
> 



From cwgordon at carolina.rr.com  Thu Mar 12 12:40:22 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 11:40:22 -0500
Subject: [Coco] Run program by typing DOS
In-Reply-To: <009001c9a331$17a4efa0$46eecee0$@rr.com>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>	<49B91278.1000104@worldnet.att.net>	<008901c9a325$756c7790$604566b0$@rr.com>	<49B91F56.2080600@worldnet.att.net>
	<009001c9a331$17a4efa0$46eecee0$@rr.com>
Message-ID: <009101c9a331$3d098990$b71c9cb0$@rr.com>

OOPS! Sorry I turned blonde for a sec or two. I figured it out now.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Bill
> Sent: Thursday, March 12, 2009 11:39 AM
> To: 'CoCoList for Color Computer Enthusiasts'
> Subject: Re: [Coco] Run program by typing DOS
> 
> They are all .dmk images. And it downloaded as 26-3254.ace
> 



From snhirsch at gmail.com  Thu Mar 12 13:37:33 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Thu, 12 Mar 2009 13:37:33 -0400 (EDT)
Subject: [Coco] Run program by typing DOS
In-Reply-To: <49B91F56.2080600@worldnet.att.net>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>
	<49B91278.1000104@worldnet.att.net>
	<008901c9a325$756c7790$604566b0$@rr.com>
	<49B91F56.2080600@worldnet.att.net>
Message-ID: <alpine.DEB.2.00.0903121334170.12255@duo>

On Thu, 12 Mar 2009, Robert Gault wrote:

> You can get a copy of Disk EDTASM+ that will run on an emulator or on a real 
> Coco if you convert the .dsk image to a real disk.
> http://www.discover-net.net/~dmkeil/coco/software/cocodisk.htm

I'm a little confused about those .dsk files.  Are these supposed to be 
physical images of CoCo floppy?  When I look at the files, I see basically 
garbage: pages full of 0ffh and a few blocks of 4eh sprinkled in between.

These downloaded as .ace files and I unpacked them with the Linux unace 
binary.

Steve

-- 


From mechacoco at gmail.com  Thu Mar 12 13:48:04 2009
From: mechacoco at gmail.com (Darren A)
Date: Thu, 12 Mar 2009 11:48:04 -0600
Subject: [Coco] Run program by typing DOS
In-Reply-To: <alpine.DEB.2.00.0903121334170.12255@duo>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>
	<49B91278.1000104@worldnet.att.net>
	<008901c9a325$756c7790$604566b0$@rr.com>
	<49B91F56.2080600@worldnet.att.net>
	<alpine.DEB.2.00.0903121334170.12255@duo>
Message-ID: <5d802cd0903121048j49a4cfc3m2e2eda51d22366e5@mail.gmail.com>

On 3/12/09, Steven Hirsch wrote:
>
> I'm a little confused about those .dsk files.  Are these supposed to be
> physical images of CoCo floppy?  When I look at the files, I see basically
> garbage: pages full of 0ffh and a few blocks of 4eh sprinkled in between.
>
--

Those sound like disk image files that use the DMK format.  The blocks
of $FF are unused sectors (formatting initializes sector data to $FF).
 The $4E bytes are used in gaps between the sector data and ID fields.
  Following a run of $4E bytes you should see a run of $00 bytes, then
three bytes of $A1 and finally an $FE or $FB.

Darren


From snhirsch at gmail.com  Thu Mar 12 14:46:23 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Thu, 12 Mar 2009 14:46:23 -0400 (EDT)
Subject: [Coco] Run program by typing DOS
In-Reply-To: <5d802cd0903121048j49a4cfc3m2e2eda51d22366e5@mail.gmail.com>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>
	<49B91278.1000104@worldnet.att.net>
	<008901c9a325$756c7790$604566b0$@rr.com>
	<49B91F56.2080600@worldnet.att.net>
	<alpine.DEB.2.00.0903121334170.12255@duo>
	<5d802cd0903121048j49a4cfc3m2e2eda51d22366e5@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.0903121445190.12255@duo>

On Thu, 12 Mar 2009, Darren A wrote:

> On 3/12/09, Steven Hirsch wrote:
>>
>> I'm a little confused about those .dsk files.  Are these supposed to be
>> physical images of CoCo floppy?  When I look at the files, I see basically
>> garbage: pages full of 0ffh and a few blocks of 4eh sprinkled in between.
>>
> --
>
> Those sound like disk image files that use the DMK format.  The blocks
> of $FF are unused sectors (formatting initializes sector data to $FF).
> The $4E bytes are used in gaps between the sector data and ID fields.
>  Following a run of $4E bytes you should see a run of $00 bytes, then
> three bytes of $A1 and finally an $FE or $FB.

Is there a tool I can use to turn them into proper DSK images?  Also, it 
would seem that they should not be using an extension of 'DSK' if that' 
not what they are.


-- 


From jps.subscriptions at gmail.com  Thu Mar 12 14:52:06 2009
From: jps.subscriptions at gmail.com (J.P. Samson)
Date: Thu, 12 Mar 2009 12:52:06 -0600
Subject: [Coco] Run program by typing DOS
In-Reply-To: <alpine.DEB.2.00.0903121445190.12255@duo>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>
	<49B91278.1000104@worldnet.att.net>
	<008901c9a325$756c7790$604566b0$@rr.com>
	<49B91F56.2080600@worldnet.att.net>
	<alpine.DEB.2.00.0903121334170.12255@duo>
	<5d802cd0903121048j49a4cfc3m2e2eda51d22366e5@mail.gmail.com>
	<alpine.DEB.2.00.0903121445190.12255@duo>
Message-ID: <D23CD8AE-76EE-4A09-8AC1-D7F248835BB0@gmail.com>

On Mar 12, 2009, at 12:46 PM, Steven Hirsch wrote:
> Is there a tool I can use to turn them into proper DSK images?   
> Also, it would seem that they should not be using an extension of  
> 'DSK' if that' not what they are.

I believe I used VCC to do the conversion--I think it can mount DSK  
and DMK images.  All you'd need to do is create a blank DSK image, and  
then do a backup in RS-DOS from the DMK image to the DSK image.

-- JP



From mechacoco at gmail.com  Thu Mar 12 15:08:24 2009
From: mechacoco at gmail.com (Darren A)
Date: Thu, 12 Mar 2009 13:08:24 -0600
Subject: [Coco] Run program by typing DOS
In-Reply-To: <alpine.DEB.2.00.0903121445190.12255@duo>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>
	<49B91278.1000104@worldnet.att.net>
	<008901c9a325$756c7790$604566b0$@rr.com>
	<49B91F56.2080600@worldnet.att.net>
	<alpine.DEB.2.00.0903121334170.12255@duo>
	<5d802cd0903121048j49a4cfc3m2e2eda51d22366e5@mail.gmail.com>
	<alpine.DEB.2.00.0903121445190.12255@duo>
Message-ID: <5d802cd0903121208h76ad04fcr98e398ad2a5cf363@mail.gmail.com>

On 3/12/09, Steven Hirsch wrote:
> On Thu, 12 Mar 2009, Darren A wrote:
>> Those sound like disk image files that use the DMK format.  The blocks
>> of $FF are unused sectors (formatting initializes sector data to $FF).
>> The $4E bytes are used in gaps between the sector data and ID fields.
>>  Following a run of $4E bytes you should see a run of $00 bytes, then
>> three bytes of $A1 and finally an $FE or $FB.
>
> Is there a tool I can use to turn them into proper DSK images?  Also, it
> would seem that they should not be using an extension of 'DSK' if that'
> not what they are.
>
--

VCC, MESS and David Keil's emulator all support DSK files in this
format.  It sounds like you want the JVC format (sector data only).
You could use one of these emulators to BACKUP the DMK disk image to a
JVC disk image.

Another method I have used to convert between formats is to download
the software utilities for the SVD (semi virtual disk) from this site:

<http://www.thesvd.com/SVD/pcsoftware.php>

You can use this utility to open a DMK format disk image and then save
it back out in JVC format (and vise-versa).  You don't need to have
the SVD device to use this feature of the software.

You should be aware that the main purpose of the DMK format is to
allow copy-protected disks to be used in an emulator.  Converting to
the JVC format will discard the data that encodes the copy-protection
details.  If the program(s) in the DSK file utilize copy protection,
they probably won't work when used from a JVC format file.

Darren


From robert.gault at worldnet.att.net  Thu Mar 12 15:49:36 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 15:49:36 -0400
Subject: [Coco] Run program by typing DOS
In-Reply-To: <008d01c9a32c$10685010$3138f030$@rr.com>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>	<49B91278.1000104@worldnet.att.net>	<008901c9a325$756c7790$604566b0$@rr.com>	<49B91F56.2080600@worldnet.att.net>
	<008d01c9a32c$10685010$3138f030$@rr.com>
Message-ID: <49B96750.5010800@worldnet.att.net>

Bill wrote:
> Well, I apologize for being such a pain in the ***, but I don't see a way to
> download from that page
> 
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Robert Gault
>> Sent: Thursday, March 12, 2009 9:43 AM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] Run program by typing DOS
>>
>> You can get a copy of Disk EDTASM+ that will run on an emulator or on a
>> real Coco if you convert the .dsk image to a real disk.
>> http://www.discover-net.net/~dmkeil/coco/software/cocodisk.htm
>>
> 
> 

Yes, that page is not set up correctly. Nevertheless, when you click on 
the buttons for a .rar package and it opens in your browser's window, 
just do a "save page". The page saved as a .rar can be opened in Winzip 
or other programs that handle .rar archives.


From robert.gault at worldnet.att.net  Thu Mar 12 16:05:21 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 16:05:21 -0400
Subject: [Coco] Using PC printer
In-Reply-To: <200903121116.48878.gene.heskett@verizon.net>
References: <008601c9a31d$cdf7adb0$69e70910$@rr.com>	<57001EF8-66A7-4FFA-87D4-01E840D4469A@tee-boy.com>	<49B91CD8.4090408@worldnet.att.net>
	<200903121116.48878.gene.heskett@verizon.net>
Message-ID: <49B96B01.2030305@worldnet.att.net>

Gene Heskett wrote:

> Do you see traffic on the usb-serial adaptor's leds when you do a 'list 
> filename >/p'?
> 
> Also, for 9600 baud out the bitbanger, I had to use a hugely different value 
> for the timer in tuneport to actually get truly 9600 baud according to my 
> oscilloscope.  By a factor of about 3/1 or 1/3, I've forgotten which way now 
> as it's coded into my startup file.
> 
> Also, the pl2303 based usb-serial adaptors sold by the shack are broken, use 
> one with an FDTI chipset, they are very transparent and haven't dropped a byte 
> on me yet.
> 

There is no usb-serial adapter. The signal goes via DriveWire to the PC 
and from the PC out the PC USB port to the printer. Boisy and I are 
trying to troubleshooting this and when it is resolved, the list will 
find out and if necessary the Cloud-9 download will be updated.

Far as tuneport goes, the default value from the DW3 NitrOS-9 6309 
Level2 package is 40960. That may be way off but I don't think that is 
the problem.


From robert.gault at worldnet.att.net  Thu Mar 12 16:07:24 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 16:07:24 -0400
Subject: [Coco] Run program by typing DOS
In-Reply-To: <49B96750.5010800@worldnet.att.net>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>	<49B91278.1000104@worldnet.att.net>	<008901c9a325$756c7790$604566b0$@rr.com>	<49B91F56.2080600@worldnet.att.net>	<008d01c9a32c$10685010$3138f030$@rr.com>
	<49B96750.5010800@worldnet.att.net>
Message-ID: <49B96B7C.4030506@worldnet.att.net>

Robert Gault wrote:

> Yes, that page is not set up correctly. Nevertheless, when you click on 
> the buttons for a .rar package and it opens in your browser's window, 
> just do a "save page". The page saved as a .rar can be opened in Winzip 
> or other programs that handle .rar archives.
> 

Sorry those are .ace files not .rar. WinACE I think is the archiver needed.


From cwgordon at carolina.rr.com  Thu Mar 12 17:10:37 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 16:10:37 -0500
Subject: [Coco] Run program by typing DOS
In-Reply-To: <49B96B7C.4030506@worldnet.att.net>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>	<49B91278.1000104@worldnet.att.net>	<008901c9a325$756c7790$604566b0$@rr.com>	<49B91F56.2080600@worldnet.att.net>	<008d01c9a32c$10685010$3138f030$@rr.com>	<49B96750.5010800@worldnet.att.net>
	<49B96B7C.4030506@worldnet.att.net>
Message-ID: <009e01c9a356$fdfed0e0$f9fc72a0$@rr.com>

Winrar will work. The images themselves, however, will not without
manipulation

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Thursday, March 12, 2009 3:07 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Run program by typing DOS
> 
> Robert Gault wrote:
> 
> > Yes, that page is not set up correctly. Nevertheless, when you click
> on
> > the buttons for a .rar package and it opens in your browser's window,
> > just do a "save page". The page saved as a .rar can be opened in
> Winzip
> > or other programs that handle .rar archives.
> >
> 
> Sorry those are .ace files not .rar. WinACE I think is the archiver
> needed.
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From robert.gault at worldnet.att.net  Thu Mar 12 16:21:41 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 16:21:41 -0400
Subject: [Coco] Using PC printer
In-Reply-To: <49B96B01.2030305@worldnet.att.net>
References: <008601c9a31d$cdf7adb0$69e70910$@rr.com>	<57001EF8-66A7-4FFA-87D4-01E840D4469A@tee-boy.com>	<49B91CD8.4090408@worldnet.att.net>	<200903121116.48878.gene.heskett@verizon.net>
	<49B96B01.2030305@worldnet.att.net>
Message-ID: <49B96ED5.50209@worldnet.att.net>

Robert Gault wrote:
> Gene Heskett wrote:
> 
>> Do you see traffic on the usb-serial adaptor's leds when you do a 
>> 'list filename >/p'?
>>
>> Also, for 9600 baud out the bitbanger, I had to use a hugely different 
>> value for the timer in tuneport to actually get truly 9600 baud 
>> according to my oscilloscope.  By a factor of about 3/1 or 1/3, I've 
>> forgotten which way now as it's coded into my startup file.
>>
>> Also, the pl2303 based usb-serial adaptors sold by the shack are 
>> broken, use one with an FDTI chipset, they are very transparent and 
>> haven't dropped a byte on me yet.
>>
> 
> There is no usb-serial adapter. The signal goes via DriveWire to the PC 
> and from the PC out the PC USB port to the printer. Boisy and I are 
> trying to troubleshooting this and when it is resolved, the list will 
> find out and if necessary the Cloud-9 download will be updated.
> 
> Far as tuneport goes, the default value from the DW3 NitrOS-9 6309 
> Level2 package is 40960. That may be way off but I don't think that is 
> the problem.
> 

Turned out to be simple. I was using a version of Winserver obtained on 
March 6th. There is a later one posted March 8th that works correctly.

When you print something from NitrOS-9, a new window on the server opens 
containing the text material. This window is used to send the text to 
the Windows printer and does not care if the connection is parallel or USB.


From robert.gault at worldnet.att.net  Thu Mar 12 16:23:25 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 16:23:25 -0400
Subject: [Coco] Run program by typing DOS
In-Reply-To: <009e01c9a356$fdfed0e0$f9fc72a0$@rr.com>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>	<49B91278.1000104@worldnet.att.net>	<008901c9a325$756c7790$604566b0$@rr.com>	<49B91F56.2080600@worldnet.att.net>	<008d01c9a32c$10685010$3138f030$@rr.com>	<49B96750.5010800@worldnet.att.net>	<49B96B7C.4030506@worldnet.att.net>
	<009e01c9a356$fdfed0e0$f9fc72a0$@rr.com>
Message-ID: <49B96F3D.3030704@worldnet.att.net>

Bill wrote:
> Winrar will work. The images themselves, however, will not without
> manipulation
> 

Mount then in MESS or VCC. Do a BACKUP to a fresh .dsk image mounted in 
a second "drive". Use the new .dsk image to create a floppy.


From dml_68 at yahoo.com  Thu Mar 12 16:44:03 2009
From: dml_68 at yahoo.com (Derek)
Date: Thu, 12 Mar 2009 13:44:03 -0700 (PDT)
Subject: [Coco] ADOS 3 Rom Question
Message-ID: <577154.62535.qm@web30202.mail.mud.yahoo.com>

I just got a 28 pin ADOS 3 ROM chip and would like some help on installing into an FD-502 Controller if possible. The Controller I have as 2 ROM Sockets the 28 PIN ROM installed says WDC'83 with a chip number WD1773-ph. The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced the 28 PIN ROM with the Ados chip I bought it comes up with the standard Disk Extended Basic screen. (I put back the original ROM chip and the controller works fine so I did not destroy anything)

My questions are
1: Is this chip compatible with this controller?
2: If yes how do I engage ADOS?
3: If no what controlls will work with it?

I do have an old FD-500 controller that has the same configuration (24 Pin ROM has Disk Extdnded Basic and 28 Pin ROM is WDC'83 Chip) But I have not tried on this controller as I wanted to get some help 1st.

Thank you




** Mistrust Authority. Promote Decentralization **


 


       


From coconut at pritchard.ca  Thu Mar 12 16:48:51 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Thu, 12 Mar 2009 15:48:51 -0500
Subject: [Coco] ADOS 3 Rom Question
In-Reply-To: <577154.62535.qm@web30202.mail.mud.yahoo.com>
References: <577154.62535.qm@web30202.mail.mud.yahoo.com>
Message-ID: <1806abd60903121348p6e1d6c12ye9e2f4d02680b5f1@mail.gmail.com>

The WD1773-ph chip is the controller chip for the floppy drive, not a
ROM chip.  I hope you did not blow you ADOS chip.  I believe you want
to buy the DOS Adapter board at http://www.cloud9tech.com/, to put in
the 24pin socket to convert the 28pin ROM to fit in the 24pin ROM
socket.

On Thu, Mar 12, 2009 at 3:44 PM, Derek <dml_68 at yahoo.com> wrote:
> I just got a 28 pin ADOS 3 ROM chip and would like some help on installing into an FD-502 Controller if possible. The Controller I have as 2 ROM Sockets the 28 PIN ROM installed says WDC'83 with a chip number WD1773-ph. The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced the 28 PIN ROM with the Ados chip I bought it comes up with the standard Disk Extended Basic screen. (I put back the original ROM chip and the controller works fine so I did not destroy anything)
>
> My questions are
> 1: Is this chip compatible with this controller?
> 2: If yes how do I engage ADOS?
> 3: If no what controlls will work with it?
>
> I do have an old FD-500 controller that has the same configuration (24 Pin ROM has Disk Extdnded Basic and 28 Pin ROM is WDC'83 Chip) But I have not tried on this controller as I wanted to get some help 1st.
>
> Thank you
>
>
>
>
> ** Mistrust Authority. Promote Decentralization **
>
>
>
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From devries.bob at gmail.com  Thu Mar 12 16:49:45 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Fri, 13 Mar 2009 06:49:45 +1000
Subject: [Coco] ADOS 3 Rom Question
References: <577154.62535.qm@web30202.mail.mud.yahoo.com>
Message-ID: <004401c9a354$15fd6c40$0701a8c0@master>

Derek,

The chip that says WDC'83 is NOT a ROM. That is the controller chip for the 
disk drives.

The 24 pin chip is the ROM. You'll need a small daughter board to make the 
28 pin ROM work in that controller.

HTH.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Derek" <dml_68 at yahoo.com>
To: "CoCo List" <coco at maltedmedia.com>
Sent: Friday, March 13, 2009 6:44 AM
Subject: [Coco] ADOS 3 Rom Question


>I just got a 28 pin ADOS 3 ROM chip and would like some help on installing 
>into an FD-502 Controller if possible. The Controller I have as 2 ROM 
>Sockets the 28 PIN ROM installed says WDC'83 with a chip number WD1773-ph. 
>The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced the 28 PIN 
>ROM with the Ados chip I bought it comes up with the standard Disk Extended 
>Basic screen. (I put back the original ROM chip and the controller works 
>fine so I did not destroy anything)
>
> My questions are
> 1: Is this chip compatible with this controller?
> 2: If yes how do I engage ADOS?
> 3: If no what controlls will work with it?
>
> I do have an old FD-500 controller that has the same configuration (24 Pin 
> ROM has Disk Extdnded Basic and 28 Pin ROM is WDC'83 Chip) But I have not 
> tried on this controller as I wanted to get some help 1st.
>
> Thank you
>
>
>
>
> ** Mistrust Authority. Promote Decentralization **
>
>
>
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From dml_68 at yahoo.com  Thu Mar 12 16:54:15 2009
From: dml_68 at yahoo.com (Derek)
Date: Thu, 12 Mar 2009 13:54:15 -0700 (PDT)
Subject: [Coco] ADOS 3 Rom Question
In-Reply-To: <1806abd60903121348p6e1d6c12ye9e2f4d02680b5f1@mail.gmail.com>
Message-ID: <73162.11915.qm@web30204.mail.mud.yahoo.com>

Many thanks!



Ryan Pritchard <coconut at pritchard.ca> wrote: The WD1773-ph chip is the controller chip for the floppy drive, not a
ROM chip.  I hope you did not blow you ADOS chip.  I believe you want
to buy the DOS Adapter board at http://www.cloud9tech.com/, to put in
the 24pin socket to convert the 28pin ROM to fit in the 24pin ROM
socket.

On Thu, Mar 12, 2009 at 3:44 PM, Derek  wrote:
> I just got a 28 pin ADOS 3 ROM chip and would like some help on installing into an FD-502 Controller if possible. The Controller I have as 2 ROM Sockets the 28 PIN ROM installed says WDC'83 with a chip number WD1773-ph. The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced the 28 PIN ROM with the Ados chip I bought it comes up with the standard Disk Extended Basic screen. (I put back the original ROM chip and the controller works fine so I did not destroy anything)
>
> My questions are
> 1: Is this chip compatible with this controller?
> 2: If yes how do I engage ADOS?
> 3: If no what controlls will work with it?
>
> I do have an old FD-500 controller that has the same configuration (24 Pin ROM has Disk Extdnded Basic and 28 Pin ROM is WDC'83 Chip) But I have not tried on this controller as I wanted to get some help 1st.
>
> Thank you
>
>
>
>
> ** Mistrust Authority. Promote Decentralization **
>
>
>
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



** Mistrust Authority. Promote Decentralization **


 


       


From snhirsch at gmail.com  Thu Mar 12 17:35:48 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Thu, 12 Mar 2009 17:35:48 -0400 (EDT)
Subject: [Coco] Run program by typing DOS
In-Reply-To: <5d802cd0903121208h76ad04fcr98e398ad2a5cf363@mail.gmail.com>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>
	<49B91278.1000104@worldnet.att.net>
	<008901c9a325$756c7790$604566b0$@rr.com>
	<49B91F56.2080600@worldnet.att.net>
	<alpine.DEB.2.00.0903121334170.12255@duo>
	<5d802cd0903121048j49a4cfc3m2e2eda51d22366e5@mail.gmail.com>
	<alpine.DEB.2.00.0903121445190.12255@duo>
	<5d802cd0903121208h76ad04fcr98e398ad2a5cf363@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.0903121733440.12255@duo>

On Thu, 12 Mar 2009, Darren A wrote:

>> Is there a tool I can use to turn them into proper DSK images?  Also, it
>> would seem that they should not be using an extension of 'DSK' if that'
>> not what they are.
>>

> Another method I have used to convert between formats is to download
> the software utilities for the SVD (semi virtual disk) from this site:
>
> <http://www.thesvd.com/SVD/pcsoftware.php>
>
> You can use this utility to open a DMK format disk image and then save
> it back out in JVC format (and vise-versa).  You don't need to have
> the SVD device to use this feature of the software.

Actually, this function is provided by a standalone binary called 'tosvd'. 
You can run it on the command line or in a shell script.  Neat!  Thanks 
for the tip.  I own an SVD, btw.  Cool gadget.

> You should be aware that the main purpose of the DMK format is to
> allow copy-protected disks to be used in an emulator.  Converting to
> the JVC format will discard the data that encodes the copy-protection
> details.  If the program(s) in the DSK file utilize copy protection,
> they probably won't work when used from a JVC format file.

I still feel that the file extensions should be '.DMK' instead of '.DSK', 
but maybe I'm just out-of-step here...

Steve


-- 


From t.fadden at cox.net  Thu Mar 12 17:43:46 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Thu, 12 Mar 2009 14:43:46 -0700
Subject: [Coco] HDB-DOS-Drivewire 3
In-Reply-To: <alpine.DEB.2.00.0903121733440.12255@duo>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>	<49B91278.1000104@worldnet.att.net>	<008901c9a325$756c7790$604566b0$@rr.com>	<49B91F56.2080600@worldnet.att.net>	<alpine.DEB.2.00.0903121334170.12255@duo>	<5d802cd0903121048j49a4cfc3m2e2eda51d22366e5@mail.gmail.com>	<alpine.DEB.2.00.0903121445190.12255@duo>	<5d802cd0903121208h76ad04fcr98e398ad2a5cf363@mail.gmail.com>
	<alpine.DEB.2.00.0903121733440.12255@duo>
Message-ID: <49B98212.1000207@cox.net>

Just got my ROM and cable today.  Had it going in about 35 seconds!   
And it works great!

I might be dreaming, but I think it boots nitros9 faster than a real 
floppy!  I am dsave'ing the modules right to a real floppy to use in 
another os9 system to create a new kernel.  SWEET!

Thanks Coud-9!

Tim Fadden


From snhirsch at gmail.com  Thu Mar 12 17:49:19 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Thu, 12 Mar 2009 17:49:19 -0400 (EDT)
Subject: [Coco] HDB-DOS-Drivewire 3
In-Reply-To: <49B98212.1000207@cox.net>
References: <008701c9a31e$38ebbe90$aac33bb0$@rr.com>
	<49B91278.1000104@worldnet.att.net>
	<008901c9a325$756c7790$604566b0$@rr.com>
	<49B91F56.2080600@worldnet.att.net>
	<alpine.DEB.2.00.0903121334170.12255@duo>
	<5d802cd0903121048j49a4cfc3m2e2eda51d22366e5@mail.gmail.com>
	<alpine.DEB.2.00.0903121445190.12255@duo>
	<5d802cd0903121208h76ad04fcr98e398ad2a5cf363@mail.gmail.com>
	<alpine.DEB.2.00.0903121733440.12255@duo>
	<49B98212.1000207@cox.net>
Message-ID: <alpine.DEB.2.00.0903121748280.12255@duo>

On Thu, 12 Mar 2009, Tim Fadden wrote:

> Just got my ROM and cable today.  Had it going in about 35 seconds!   And it 
> works great!
>
> I might be dreaming, but I think it boots nitros9 faster than a real floppy! 
> I am dsave'ing the modules right to a real floppy to use in another os9 
> system to create a new kernel.  SWEET!

Not only is it faster than a floppy, but I actually think it's equal to or 
faster than my IDE hard disk.



-- 


From mmarlette at frontiernet.net  Thu Mar 12 18:03:23 2009
From: mmarlette at frontiernet.net (Mark Marlette)
Date: Thu, 12 Mar 2009 22:03:23 +0000 (UTC)
Subject: [Coco] HDB-DOS-Drivewire 3
In-Reply-To: <alpine.DEB.2.00.0903121748280.12255@duo>
Message-ID: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>


Testing I did using MegaRead under NitrOS-9 and SuperDriver......

SCSI, ~11 seconds
SuperIDE/CF, ~19 seconds.

We only know one speed, to the floorboard!

Mark
Cloud-9



----- Original Message -----
From: "Steven Hirsch" <snhirsch at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, March 12, 2009 4:49:19 PM GMT -06:00 US/Canada Central
Subject: Re: [Coco] HDB-DOS-Drivewire 3

On Thu, 12 Mar 2009, Tim Fadden wrote:

> Just got my ROM and cable today.  Had it going in about 35 seconds!   And it 
> works great!
>
> I might be dreaming, but I think it boots nitros9 faster than a real floppy! 
> I am dsave'ing the modules right to a real floppy to use in another os9 
> system to create a new kernel.  SWEET!

Not only is it faster than a floppy, but I actually think it's equal to or 
faster than my IDE hard disk.



-- 

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco


From lamune at doki-doki.net  Thu Mar 12 18:47:11 2009
From: lamune at doki-doki.net (Mike Pepe)
Date: Thu, 12 Mar 2009 15:47:11 -0700
Subject: [Coco] FD-502
In-Reply-To: <008f01c9a32e$d949df10$8bdd9d30$@rr.com>
References: <008f01c9a32e$d949df10$8bdd9d30$@rr.com>
Message-ID: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1BA@fenestra.lamunet.local>

How do you know they don't work? Because you don't have a controller to
test them with, or because they fail with a known good disk controller?

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com]
On Behalf Of Bill
Sent: Thursday, March 12, 2009 9:23 AM
To: CoCoList for Color Computer Enthusiasts
Subject: [Coco] FD-502

I was foolish enough to buy two FD-502 drives off eBay, and neither one
works. One has a cable, and the other does not. Neither has controller.

I'd like to swap both units for two bare working drives. I know this
sound
stupid, but maybe someone can use the box and power supply. I want one
drive
to put into my existing FD-500 and the other to put into my PC.

Thanks.

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



From flexser at fiu.edu  Thu Mar 12 20:20:49 2009
From: flexser at fiu.edu (Arthur Flexser)
Date: Thu, 12 Mar 2009 20:20:49 -0400
Subject: [Coco] ADOS 3 Rom Question
In-Reply-To: <577154.62535.qm@web30202.mail.mud.yahoo.com>
References: <577154.62535.qm@web30202.mail.mud.yahoo.com>
Message-ID: <dbdeb2610903121720h1e4da7b9t8ec6dd6fd6496f9e@mail.gmail.com>

Are you sure that's an FD-502?  According to my notes, the FD-502 is
the one controller Tandy made that has a 28-pin ROM socket, which
should therefore be directly compatible with your 28-pin ADOS-3 EPROM
(though it requires a small modification to enable the upper 8K of ROM
space to accommodate Extended ADOS-3.)  I suspect you actually have an
FD-500 or FD-501.

Art

On Thu, Mar 12, 2009 at 4:44 PM, Derek <dml_68 at yahoo.com> wrote:
> I just got a 28 pin ADOS 3 ROM chip and would like some help on installing into an FD-502 Controller if possible. The Controller I have as 2 ROM Sockets the 28 PIN ROM installed says WDC'83 with a chip number WD1773-ph. The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced the 28 PIN ROM with the Ados chip I bought it comes up with the standard Disk Extended Basic screen. (I put back the original ROM chip and the controller works fine so I did not destroy anything)
>
> My questions are
> 1: Is this chip compatible with this controller?
> 2: If yes how do I engage ADOS?
> 3: If no what controlls will work with it?
>
> I do have an old FD-500 controller that has the same configuration (24 Pin ROM has Disk Extdnded Basic and 28 Pin ROM is WDC'83 Chip) But I have not tried on this controller as I wanted to get some help 1st.
>
> Thank you
>
>
>
>
> ** Mistrust Authority. Promote Decentralization **
>
>
>
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From snhirsch at gmail.com  Thu Mar 12 20:27:11 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Thu, 12 Mar 2009 20:27:11 -0400 (EDT)
Subject: [Coco] HDB-DOS-Drivewire 3
In-Reply-To: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
References: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
Message-ID: <alpine.DEB.2.00.0903122026340.12255@duo>

On Thu, 12 Mar 2009, Mark Marlette wrote:

>
> Testing I did using MegaRead under NitrOS-9 and SuperDriver......
>
> SCSI, ~11 seconds
> SuperIDE/CF, ~19 seconds.
>
> We only know one speed, to the floorboard!

What did the Drivewire drive benchmark as?

-- 


From mechacoco at gmail.com  Thu Mar 12 20:52:59 2009
From: mechacoco at gmail.com (Darren A)
Date: Thu, 12 Mar 2009 18:52:59 -0600
Subject: [Coco] ADOS 3 Rom Question
In-Reply-To: <dbdeb2610903121720h1e4da7b9t8ec6dd6fd6496f9e@mail.gmail.com>
References: <577154.62535.qm@web30202.mail.mud.yahoo.com>
	<dbdeb2610903121720h1e4da7b9t8ec6dd6fd6496f9e@mail.gmail.com>
Message-ID: <5d802cd0903121752j32d1c12byac98a73e4609bb87@mail.gmail.com>

Yeah... that doesn't sound like an FD-502.  In addition to having a
28-pin ROM socket, the 502 (as supplied by Tandy) has the controller
chip soldered directly to the board.  Perhaps he has a 501 inside a
502 case.  The edge connector contacts are gold on a 501, but not on a
502.

Darren

-----

On 3/12/09, Arthur Flexser  wrote:
> Are you sure that's an FD-502?  According to my notes, the FD-502 is
> the one controller Tandy made that has a 28-pin ROM socket, which
> should therefore be directly compatible with your 28-pin ADOS-3 EPROM
> (though it requires a small modification to enable the upper 8K of ROM
> space to accommodate Extended ADOS-3.)  I suspect you actually have an
> FD-500 or FD-501.
>
> Art
>
> On Thu, Mar 12, 2009 at 4:44 PM, Derek <dml_68 at yahoo.com> wrote:
>> I just got a 28 pin ADOS 3 ROM chip and would like some help on installing
>> into an FD-502 Controller if possible. The Controller I have as 2 ROM
>> Sockets the 28 PIN ROM installed says WDC'83 with a chip number WD1773-ph.
>> The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced the 28
>> PIN ROM with the Ados chip I bought it comes up with the standard Disk
>> Extended Basic screen. (I put back the original ROM chip and the
>> controller works fine so I did not destroy anything)


From flexser at fiu.edu  Thu Mar 12 21:04:54 2009
From: flexser at fiu.edu (Arthur Flexser)
Date: Thu, 12 Mar 2009 21:04:54 -0400
Subject: [Coco] ADOS 3 Rom Question
In-Reply-To: <5d802cd0903121752j32d1c12byac98a73e4609bb87@mail.gmail.com>
References: <577154.62535.qm@web30202.mail.mud.yahoo.com>
	<dbdeb2610903121720h1e4da7b9t8ec6dd6fd6496f9e@mail.gmail.com>
	<5d802cd0903121752j32d1c12byac98a73e4609bb87@mail.gmail.com>
Message-ID: <dbdeb2610903121804u6e3d11a7p3dd00a3a259c9534@mail.gmail.com>

As I recall, the FD-502 is also shorter than the 500 and 501, so doubt
there could be such a thing as a 501 inside a 502 case.  Does the
FD-502 actually identify itself as such on the case?

Art

On Thu, Mar 12, 2009 at 8:52 PM, Darren A <mechacoco at gmail.com> wrote:
> Yeah... that doesn't sound like an FD-502. ?In addition to having a
> 28-pin ROM socket, the 502 (as supplied by Tandy) has the controller
> chip soldered directly to the board. ?Perhaps he has a 501 inside a
> 502 case. ?The edge connector contacts are gold on a 501, but not on a
> 502.
>
> Darren
>
> -----
>
> On 3/12/09, Arthur Flexser ?wrote:
>> Are you sure that's an FD-502? ?According to my notes, the FD-502 is
>> the one controller Tandy made that has a 28-pin ROM socket, which
>> should therefore be directly compatible with your 28-pin ADOS-3 EPROM
>> (though it requires a small modification to enable the upper 8K of ROM
>> space to accommodate Extended ADOS-3.) ?I suspect you actually have an
>> FD-500 or FD-501.
>>
>> Art
>>
>> On Thu, Mar 12, 2009 at 4:44 PM, Derek <dml_68 at yahoo.com> wrote:
>>> I just got a 28 pin ADOS 3 ROM chip and would like some help on installing
>>> into an FD-502 Controller if possible. The Controller I have as 2 ROM
>>> Sockets the 28 PIN ROM installed says WDC'83 with a chip number WD1773-ph.
>>> The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced the 28
>>> PIN ROM with the Ados chip I bought it comes up with the standard Disk
>>> Extended Basic screen. (I put back the original ROM chip and the
>>> controller works fine so I did not destroy anything)
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From t.fadden at cox.net  Thu Mar 12 21:27:56 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Thu, 12 Mar 2009 18:27:56 -0700
Subject: [Coco] ADOS 3 Rom Question
In-Reply-To: <dbdeb2610903121804u6e3d11a7p3dd00a3a259c9534@mail.gmail.com>
References: <577154.62535.qm@web30202.mail.mud.yahoo.com>	<dbdeb2610903121720h1e4da7b9t8ec6dd6fd6496f9e@mail.gmail.com>	<5d802cd0903121752j32d1c12byac98a73e4609bb87@mail.gmail.com>
	<dbdeb2610903121804u6e3d11a7p3dd00a3a259c9534@mail.gmail.com>
Message-ID: <49B9B69C.4090607@cox.net>

 From what I remember, the latest 501 was in a short case. Also the 
502's were gold except for the very last model where the gold was dropped.
There is a website that shows pictures of all of them, but I don't 
remember exactly where!  If I find it I will post it.

Tim
Arthur Flexser wrote:
> As I recall, the FD-502 is also shorter than the 500 and 501, so doubt
> there could be such a thing as a 501 inside a 502 case.  Does the
> FD-502 actually identify itself as such on the case?
>
> Art
>
> On Thu, Mar 12, 2009 at 8:52 PM, Darren A <mechacoco at gmail.com> wrote:
>   
>> Yeah... that doesn't sound like an FD-502.  In addition to having a
>> 28-pin ROM socket, the 502 (as supplied by Tandy) has the controller
>> chip soldered directly to the board.  Perhaps he has a 501 inside a
>> 502 case.  The edge connector contacts are gold on a 501, but not on a
>> 502.
>>
>> Darren
>>
>> -----
>>
>> On 3/12/09, Arthur Flexser  wrote:
>>     
>>> Are you sure that's an FD-502?  According to my notes, the FD-502 is
>>> the one controller Tandy made that has a 28-pin ROM socket, which
>>> should therefore be directly compatible with your 28-pin ADOS-3 EPROM
>>> (though it requires a small modification to enable the upper 8K of ROM
>>> space to accommodate Extended ADOS-3.)  I suspect you actually have an
>>> FD-500 or FD-501.
>>>
>>> Art
>>>
>>> On Thu, Mar 12, 2009 at 4:44 PM, Derek <dml_68 at yahoo.com> wrote:
>>>       
>>>> I just got a 28 pin ADOS 3 ROM chip and would like some help on installing
>>>> into an FD-502 Controller if possible. The Controller I have as 2 ROM
>>>> Sockets the 28 PIN ROM installed says WDC'83 with a chip number WD1773-ph.
>>>> The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced the 28
>>>> PIN ROM with the Ados chip I bought it comes up with the standard Disk
>>>> Extended Basic screen. (I put back the original ROM chip and the
>>>> controller works fine so I did not destroy anything)
>>>>         
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>     
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From t.fadden at cox.net  Thu Mar 12 21:32:04 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Thu, 12 Mar 2009 18:32:04 -0700
Subject: [Coco] ADOS 3 Rom Question
In-Reply-To: <49B9B69C.4090607@cox.net>
References: <577154.62535.qm@web30202.mail.mud.yahoo.com>	<dbdeb2610903121720h1e4da7b9t8ec6dd6fd6496f9e@mail.gmail.com>	<5d802cd0903121752j32d1c12byac98a73e4609bb87@mail.gmail.com>	<dbdeb2610903121804u6e3d11a7p3dd00a3a259c9534@mail.gmail.com>
	<49B9B69C.4090607@cox.net>
Message-ID: <49B9B794.2060304@cox.net>

Here it is.
http://www.thecocolounge.com/accessories.htm

I was correct about the size, but wrong about the gold contacts.

Tim


Tim Fadden wrote:
> From what I remember, the latest 501 was in a short case. Also the 
> 502's were gold except for the very last model where the gold was 
> dropped.
> There is a website that shows pictures of all of them, but I don't 
> remember exactly where!  If I find it I will post it.
>
> Tim
> Arthur Flexser wrote:
>> As I recall, the FD-502 is also shorter than the 500 and 501, so doubt
>> there could be such a thing as a 501 inside a 502 case.  Does the
>> FD-502 actually identify itself as such on the case?
>>
>> Art
>>
>> On Thu, Mar 12, 2009 at 8:52 PM, Darren A <mechacoco at gmail.com> wrote:
>>  
>>> Yeah... that doesn't sound like an FD-502.  In addition to having a
>>> 28-pin ROM socket, the 502 (as supplied by Tandy) has the controller
>>> chip soldered directly to the board.  Perhaps he has a 501 inside a
>>> 502 case.  The edge connector contacts are gold on a 501, but not on a
>>> 502.
>>>
>>> Darren
>>>
>>> -----
>>>
>>> On 3/12/09, Arthur Flexser  wrote:
>>>    
>>>> Are you sure that's an FD-502?  According to my notes, the FD-502 is
>>>> the one controller Tandy made that has a 28-pin ROM socket, which
>>>> should therefore be directly compatible with your 28-pin ADOS-3 EPROM
>>>> (though it requires a small modification to enable the upper 8K of ROM
>>>> space to accommodate Extended ADOS-3.)  I suspect you actually have an
>>>> FD-500 or FD-501.
>>>>
>>>> Art
>>>>
>>>> On Thu, Mar 12, 2009 at 4:44 PM, Derek <dml_68 at yahoo.com> wrote:
>>>>      
>>>>> I just got a 28 pin ADOS 3 ROM chip and would like some help on 
>>>>> installing
>>>>> into an FD-502 Controller if possible. The Controller I have as 2 ROM
>>>>> Sockets the 28 PIN ROM installed says WDC'83 with a chip number 
>>>>> WD1773-ph.
>>>>> The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced 
>>>>> the 28
>>>>> PIN ROM with the Ados chip I bought it comes up with the standard 
>>>>> Disk
>>>>> Extended Basic screen. (I put back the original ROM chip and the
>>>>> controller works fine so I did not destroy anything)
>>>>>         
>>> -- 
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>     
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>>   
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>



From mechacoco at gmail.com  Thu Mar 12 21:43:44 2009
From: mechacoco at gmail.com (Darren A)
Date: Thu, 12 Mar 2009 19:43:44 -0600
Subject: [Coco] ADOS 3 Rom Question
In-Reply-To: <dbdeb2610903121804u6e3d11a7p3dd00a3a259c9534@mail.gmail.com>
References: <577154.62535.qm@web30202.mail.mud.yahoo.com>
	<dbdeb2610903121720h1e4da7b9t8ec6dd6fd6496f9e@mail.gmail.com>
	<5d802cd0903121752j32d1c12byac98a73e4609bb87@mail.gmail.com>
	<dbdeb2610903121804u6e3d11a7p3dd00a3a259c9534@mail.gmail.com>
Message-ID: <5d802cd0903121843l5b4242ccg100e0578173ffc92@mail.gmail.com>

On 3/12/09, Arthur Flexser wrote:
> As I recall, the FD-502 is also shorter than the 500 and 501, so doubt
> there could be such a thing as a 501 inside a 502 case.  Does the
> FD-502 actually identify itself as such on the case?
>
> Art


FD-501 and FD-502 are the same size (small).  The FD-500 and all
predecessors are in the long case.

Darren


From cwgordon at carolina.rr.com  Thu Mar 12 22:58:01 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 21:58:01 -0500
Subject: [Coco] FD-502
In-Reply-To: <4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1BA@fenestra.lamunet.local>
References: <008f01c9a32e$d949df10$8bdd9d30$@rr.com>
	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1BA@fenestra.lamunet.local>
Message-ID: <00da01c9a387$867b26a0$937173e0$@rr.com>

They fail with a known good controller. I have another controller, and the
one works well with it, but the other two drives fail.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Mike Pepe
> Sent: Thursday, March 12, 2009 5:47 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] FD-502
> 
> How do you know they don't work? Because you don't have a controller to
> test them with, or because they fail with a known good disk controller?
> 



From robert.gault at worldnet.att.net  Thu Mar 12 22:19:45 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Thu, 12 Mar 2009 22:19:45 -0400
Subject: [Coco] FD-502
In-Reply-To: <00da01c9a387$867b26a0$937173e0$@rr.com>
References: <008f01c9a32e$d949df10$8bdd9d30$@rr.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1BA@fenestra.lamunet.local>
	<00da01c9a387$867b26a0$937173e0$@rr.com>
Message-ID: <49B9C2C1.6080600@worldnet.att.net>

Bill wrote:
> They fail with a known good controller. I have another controller, and the
> one works well with it, but the other two drives fail.
> 

What is the failure mode? Can they read disks from another drive? Can 
they format disks? Does the drive spin and if so is the strobe speed 
correct? Does the head move along the rails? Check for fuses.

There are several failure modes that can be fixed by cleaning, 
lubrication, adjusting drive speed, and adjusting the track0 stop. Other 
failure modes would need a scope and special calibration disk to repair.


From cwgordon at carolina.rr.com  Thu Mar 12 23:41:00 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Thu, 12 Mar 2009 22:41:00 -0500
Subject: [Coco] FD-502
In-Reply-To: <49B9C2C1.6080600@worldnet.att.net>
References: <008f01c9a32e$d949df10$8bdd9d30$@rr.com>	<4C8EB9FD6963BD4C8BA6B0B60FE8E4DD04B1BA@fenestra.lamunet.local>	<00da01c9a387$867b26a0$937173e0$@rr.com>
	<49B9C2C1.6080600@worldnet.att.net>
Message-ID: <00ec01c9a38d$871200b0$95360210$@rr.com>

The one of them will act like it's formatting a disk. But when it gets its
FIRST scan and is supposed to go back and verify (seems like a quicker scan)
it just stays in place with the disk spinning.

The other one won't even do that much. It goes through about 1/2 of the
first scan, and just sits there with the disk spinning. I have access to 2
controllers, and the drives do the same thing, regardless of which
controller is used.

Unfortunately, with my poor eyesight and arthritis in my joints, I'm unable
to work on them like I used to. 

It would be easier for me to sell them "as-is" on eBay and get back a little
of what I spent, or just trade both full units to someone for 2 bare drives
that I could use.

> -----Original Message-----
> From: coco-bounces at maltedmedia.com [mailto:coco-
> bounces at maltedmedia.com] On Behalf Of Robert Gault
> Sent: Thursday, March 12, 2009 9:20 PM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] FD-502
> 
> What is the failure mode? Can they read disks from another drive? Can
> they format disks? Does the drive spin and if so is the strobe speed
> correct? Does the head move along the rails? Check for fuses.
> 
> There are several failure modes that can be fixed by cleaning,
> lubrication, adjusting drive speed, and adjusting the track0 stop.
> Other failure modes would need a scope and special calibration disk to
> repair.
> 



From jdaggett at gate.net  Thu Mar 12 22:46:27 2009
From: jdaggett at gate.net (jdaggett at gate.net)
Date: Thu, 12 Mar 2009 22:46:27 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <D5D4DBC62543475C88E8F4F3B52BF46C@FANTASYWARE>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>,
	<D5D4DBC62543475C88E8F4F3B52BF46C@FANTASYWARE>
Message-ID: <49B990C3.5797.2FB1A7@jdaggett.gate.net>

On 11 Mar 2009 at 19:49, RJLCyberPunk wrote:

> Frankly I have no idea how fast the new wireless buetooth "RS232" pak
> is, I'll have to check
> 

It is not how fast the bluetooth wireless portion is. It is the UART speed of 
the Coco that is the limiting issue. RS232 inherently is limited to about 
256Kbs mainly due to cabling. Short runs can have speeds  upwards to 3 
Mbps. A stock Coco3 at best is about 115Kbps. That is twice dial up 
speeds. 

james


> > BT to serial albeit slow it will work. About as a fast as 56K dial
> > up.
> >
> > BT to USB would be better.
> >
> > After being on DSL for over five years there is no way I want to go
> > back to dial up speeds. Not even fro the novalty of a Coco3 having a
> > browser.
> >
> > just my thouhts
> >
> > james
> >> ----- Original Message ----- 
> >> From: <jdaggett at gate.net>
> >> To: "CoCoList for Color Computer Enthusiasts"
> >> <coco at maltedmedia.com> Sent: Tuesday, March 10, 2009 10:37 PM
> >> Subject: Re: [Coco] How about a CoCo Web Browser?
> >>
> >>
> >> > First off you need some means of connecting to the internet
> >> > either through a modem or through a PC/MAC. Then you can think
> >> > about a web browser. Can't put the cart before the horse or the
> >> > cart wont go anywhere.
> >> >
> >> > james
> >> >
> >> >
> >>
> >>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> http://five.pairlist.net/mailman/listinfo/coco
> >
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> > 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco




From dml_68 at yahoo.com  Thu Mar 12 22:48:25 2009
From: dml_68 at yahoo.com (Derek)
Date: Thu, 12 Mar 2009 19:48:25 -0700 (PDT)
Subject: [Coco] ADOS 3 Rom Question
In-Reply-To: <dbdeb2610903121720h1e4da7b9t8ec6dd6fd6496f9e@mail.gmail.com>
Message-ID: <437657.59753.qm@web30207.mail.mud.yahoo.com>

My mistake its an FD-501 controller just like it says on the label, in big lettering, in english..FD-501.. I blame 20 years of marriage for a mushy mind

Arthur Flexser <flexser at fiu.edu> wrote: Are you sure that's an FD-502?  According to my notes, the FD-502 is
the one controller Tandy made that has a 28-pin ROM socket, which
should therefore be directly compatible with your 28-pin ADOS-3 EPROM
(though it requires a small modification to enable the upper 8K of ROM
space to accommodate Extended ADOS-3.)  I suspect you actually have an
FD-500 or FD-501.

Art

On Thu, Mar 12, 2009 at 4:44 PM, Derek  wrote:
> I just got a 28 pin ADOS 3 ROM chip and would like some help on installing into an FD-502 Controller if possible. The Controller I have as 2 ROM Sockets the 28 PIN ROM installed says WDC'83 with a chip number WD1773-ph. The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced the 28 PIN ROM with the Ados chip I bought it comes up with the standard Disk Extended Basic screen. (I put back the original ROM chip and the controller works fine so I did not destroy anything)
>
> My questions are
> 1: Is this chip compatible with this controller?
> 2: If yes how do I engage ADOS?
> 3: If no what controlls will work with it?
>
> I do have an old FD-500 controller that has the same configuration (24 Pin ROM has Disk Extdnded Basic and 28 Pin ROM is WDC'83 Chip) But I have not tried on this controller as I wanted to get some help 1st.
>
> Thank you
>
>
>
>
> ** Mistrust Authority. Promote Decentralization **
>
>
>
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco



** Mistrust Authority. Promote Decentralization **


 


       


From jdaggett at gate.net  Thu Mar 12 22:56:55 2009
From: jdaggett at gate.net (jdaggett at gate.net)
Date: Thu, 12 Mar 2009 22:56:55 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <20090311225306.2D04020A13@qs281.pair.com>
References: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>,
	<49B7F533.2027.C7583@jdaggett.gate.net>,
	<20090311225306.2D04020A13@qs281.pair.com>
Message-ID: <49B99337.26604.394996@jdaggett.gate.net>

On 11 Mar 2009 at 17:52, Roger Taylor wrote:

> At 04:30 PM 3/11/2009, you wrote:
> > > John
> >
> >Yes that would work if you don't mind 56K dial up speeds.
> 
> Correction in order.  With today's "56K dialup" connections, you
> almost always only get 26.4k.
> 
> The 6551 has a 115200 bps mode.   The CoCo tells the PC to fetch a web
> page, and the speed of the PC's internet connection is the speed used.
>  The data appears to the CoCo on one of the remote virtual disks where
> it can be read any way you like @ 115200 bps.  Even considering
> overhead, it's extremely faster than a dial-up experience.
> 
> -- 
> Roger Taylor
> 
 I used to average about 31K with 56K dial up. On good days I saw about 
36K. So what that 115K is about three to four times faster. 

Then again it may very well be a first if one is enfactuated with doing web 
browsing on an 8 bit machine. Even with some of the pictures the browser 
mentioned was doing text only and not rendering any graphics. There is 
where speed increase beyond 115K will be benificial. 

My personal opinion with networking with a Coco is best left to telnet, FTP, 
NNTP and SNTP. HTTP is doable but not time wise economical.
 
james




From jdaggett at gate.net  Thu Mar 12 22:59:14 2009
From: jdaggett at gate.net (jdaggett at gate.net)
Date: Thu, 12 Mar 2009 22:59:14 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <20090311215622.GB20056@tuxdriver.com>
References: <20090311182803.GE8761@tuxdriver.com>,
	<49B7F533.2027.C7583@jdaggett.gate.net>,
	<20090311215622.GB20056@tuxdriver.com>
Message-ID: <49B993C2.4735.3B68FC@jdaggett.gate.net>

On 11 Mar 2009 at 17:56, John W. Linville wrote:

> On Wed, Mar 11, 2009 at 05:30:27PM -0400, jdaggett at gate.net wrote: >
> On 11 Mar 2009 at 14:28, John W. Linville wrote: > > > On Tue, Mar 10,
> 2009 at 10:37:03PM -0400, jdaggett at gate.net wrote: > > > First off you
> need some means of connecting to the internet either > > through > a
> modem or through a PC/MAC. Then you can think about a web > > browser.
> > Can't put the cart before the horse or the cart wont go > >
> anywhere. > > > > I think he was presuming to use the "get any file
> via http" feature of > > CoCoNet to account for the communications
> piece... > > > > John > > Yes that would work if you don't mind 56K
> dial up speeds. 
> 
> Probably 115k or so FWIW, but I doubt the coco could eat the data much
> faster than that anyway.
> 
> > Better off would be to have a dedicated hardware that floated on the
> > buss that did all the TCP/IP stuff and hooked up to a router to do
> > the PPPOE stuff. It would be faster. 
> 
> Sure, but so would just using a PC... :-)
> 
> > Sorry I am not thrilled with dial up speeds for internet
> > connections. Even on  Coco3. Roger's BT and Boisey's Drivewire are
> > fine products for what they do and do best. Trying to put web
> > browser traffic over it to a PC or a MAC to gain internet is not
> > efficient or cost effective in my opinion. 
> 
> No probably not.  But it would be a damned cool project for someone
> that would enjoy that as a hobby. :-)
> 
> John


Yes it is one of those projects to say I did it so that I can prove it can be 
done type feelings. 

james




From t.fadden at cox.net  Thu Mar 12 23:06:31 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Thu, 12 Mar 2009 20:06:31 -0700
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <49B993C2.4735.3B68FC@jdaggett.gate.net>
References: <20090311182803.GE8761@tuxdriver.com>,
	<49B7F533.2027.C7583@jdaggett.gate.net>,
	<20090311215622.GB20056@tuxdriver.com>
	<49B993C2.4735.3B68FC@jdaggett.gate.net>
Message-ID: <49B9CDB7.4050006@cox.net>

Cost/time effective?  We are talking about a COCO right?  If these are 
your concerns, why do you even mess with a CoCo in the first place?

I do it for the fun of it.   If I wanted fast and glitzy, I would be 
using my quad core 3 gig machine.

Tim.

jdaggett at gate.net wrote:
> On 11 Mar 2009 at 17:56, John W. Linville wrote:
>
>   
>> On Wed, Mar 11, 2009 at 05:30:27PM -0400, jdaggett at gate.net wrote: >
>> On 11 Mar 2009 at 14:28, John W. Linville wrote: > > > On Tue, Mar 10,
>> 2009 at 10:37:03PM -0400, jdaggett at gate.net wrote: > > > First off you
>> need some means of connecting to the internet either > > through > a
>> modem or through a PC/MAC. Then you can think about a web > > browser.
>>     
>>> Can't put the cart before the horse or the cart wont go > >
>>>       
>> anywhere. > > > > I think he was presuming to use the "get any file
>> via http" feature of > > CoCoNet to account for the communications
>> piece... > > > > John > > Yes that would work if you don't mind 56K
>> dial up speeds. 
>>
>> Probably 115k or so FWIW, but I doubt the coco could eat the data much
>> faster than that anyway.
>>
>>     
>>> Better off would be to have a dedicated hardware that floated on the
>>> buss that did all the TCP/IP stuff and hooked up to a router to do
>>> the PPPOE stuff. It would be faster. 
>>>       
>> Sure, but so would just using a PC... :-)
>>
>>     
>>> Sorry I am not thrilled with dial up speeds for internet
>>> connections. Even on  Coco3. Roger's BT and Boisey's Drivewire are
>>> fine products for what they do and do best. Trying to put web
>>> browser traffic over it to a PC or a MAC to gain internet is not
>>> efficient or cost effective in my opinion. 
>>>       
>> No probably not.  But it would be a damned cool project for someone
>> that would enjoy that as a hobby. :-)
>>
>> John
>>     
>
>
> Yes it is one of those projects to say I did it so that I can prove it can be 
> done type feelings. 
>
> james
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>   



From jdaggett at gate.net  Thu Mar 12 23:07:34 2009
From: jdaggett at gate.net (jdaggett at gate.net)
Date: Thu, 12 Mar 2009 23:07:34 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <49B85685.3010308@adinet.com.uy>
References: <002001c9a191$51357ec0$f3a07c40$@rr.com>,
	<D5D4DBC62543475C88E8F4F3B52BF46C@FANTASYWARE>,
	<49B85685.3010308@adinet.com.uy>
Message-ID: <49B995B6.12604.4309ED@jdaggett.gate.net>

On 11 Mar 2009 at 21:25, Diego Barizo wrote:

> Besides web access, another good reason to have a browser like program
> for the CoCo, is to be able to open HTML files, which are the real
> Portable Document File, - not that other format :-) That was the idea
> behind my attempt to create what is an HTML renderer, not a web
> browser. To allow me to create a formatted text file in the PC, and
> open it in the CoCo keeping most of the formatting.
> 
> Diego
> 

Fifteen years ago when the HTML was still in its adolescent years yes. Now 
that HTML has matured into XML there is no way that a stock Coco3 could 
have the graphics power to do all that XML or even HTML can do. Heck not 
even the two popular browsers on PCs today support all the features of 
HTML or even XML. 

You would have to redign the 6309 processor to run on 45 nM silicon to just 
think of getting enough computing power. A separate graphics processor 
with accelleration. 

Yes you could do a small subset of the HTML language on a Coco3.  But it 
may very well be highly limited to make surfing the net not a pretty sight.

just my opinion

james
> RJLCyberPunk wrote:
> > Frankly I have no idea how fast the new wireless buetooth "RS232"
> > pak is, I'll have to check
> >
> >> BT to serial albeit slow it will work. About as a fast as 56K dial
> >> up.
> >>
> >> BT to USB would be better.
> >>
> >> After being on DSL for over five years there is no way I want to go
> >> back to dial up speeds. Not even fro the novalty of a Coco3 having
> >> a browser.
> >>
> >> just my thouhts
> >>
> >> james
> >>> ----- Original Message ----- From: <jdaggett at gate.net>
> >>> To: "CoCoList for Color Computer Enthusiasts"
> >>> <coco at maltedmedia.com> Sent: Tuesday, March 10, 2009 10:37 PM
> >>> Subject: Re: [Coco] How about a CoCo Web Browser?
> >>>
> >>>
> >>> > First off you need some means of connecting to the internet
> >>> > either through a modem or through a PC/MAC. Then you can think
> >>> > about a web browser. Can't put the cart before the horse or the
> >>> > cart wont go anywhere.
> >>> >
> >>> > james
> >>> >
> >>> >
> >>>
> >>>
> >>> -- 
> >>> Coco mailing list
> >>> Coco at maltedmedia.com
> >>> http://five.pairlist.net/mailman/listinfo/coco
> >>
> >>
> >>
> >> -- 
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> http://five.pairlist.net/mailman/listinfo/coco
> >>
> >
> >
> > -- 
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> >
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco




From gene.heskett at verizon.net  Fri Mar 13 00:20:57 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Fri, 13 Mar 2009 00:20:57 -0400
Subject: [Coco] FD-502
In-Reply-To: <00ec01c9a38d$871200b0$95360210$@rr.com>
References: <008f01c9a32e$d949df10$8bdd9d30$@rr.com>
	<49B9C2C1.6080600@worldnet.att.net>
	<00ec01c9a38d$871200b0$95360210$@rr.com>
Message-ID: <200903130020.57932.gene.heskett@verizon.net>

On Thursday 12 March 2009, Bill wrote:
>The one of them will act like it's formatting a disk. But when it gets its
>FIRST scan and is supposed to go back and verify (seems like a quicker scan)
>it just stays in place with the disk spinning.
>
>The other one won't even do that much. It goes through about 1/2 of the
>first scan, and just sits there with the disk spinning. I have access to 2
>controllers, and the drives do the same thing, regardless of which
>controller is used.
>
That pretty much verifies my thoughts on it Bill.  Those drives need to come 
out of the box, and have the head sliders cleaned and lubricated again.  The 
stepper motor that drives the heads simply cannot overcome the friction 
because the sliders are dirty, and the lubricant that was there 20 years ago 
has now turned into an almost varnish like substance with zero lubrication 
ability.  All its doing today is gluing the dirt in place.  A can of paint 
thinner alcohol and a bag of Sherwood Q-Tips from your druggist (they aren't 
on the shelf except in the pharmacy and they may have to order, in which case 
its a box of 10 bags, 100 to the bag, and about a $15 bill the last time I 
bought some.)  These are wooden sticked Q-Tips, cotton on one end only, and 
the sticks are a good 6" long so you can reach places the common q-tip can't.
The paint thinner alcohol is far more effective than any rubbing alcohol, and 
comes in qt cans at ACE Hdwe or similar places for about a 5ver per can.

Clean the slider parts up till they look like new, and a drop of 10w30 on 
them, and those drives will likely be as good as new.  10 minute job per drive 
for me once they are out laying out on the table. Maybe it like the piece of 
furniture or a toy that a 6 year old can assemble, so maybe you can find a 
youngster with good eyesight & no arthritis?  And who knows  what a gentle 
touch means?

>Unfortunately, with my poor eyesight and arthritis in my joints, I'm unable
>to work on them like I used to.
>
>It would be easier for me to sell them "as-is" on eBay and get back a little
>of what I spent, or just trade both full units to someone for 2 bare drives
>that I could use.

Which, because there haven't been floppy drives made in the 5.25" sizes for a 
good ten years now, are likely very near the 'use by' date too.

One thing that is rarely discussed on the net is where we are, but sometimes 
knowing where one is might lead to a visit from one of our group who lives 
nearby.  That of course is up to you.  Most of this group knows where I am 
within a few miles, in Weston WV.  County seat town, about 5500 population, 
and I'm in the phone book.
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com [mailto:coco-
>> bounces at maltedmedia.com] On Behalf Of Robert Gault
>> Sent: Thursday, March 12, 2009 9:20 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] FD-502
>>
>> What is the failure mode? Can they read disks from another drive? Can
>> they format disks? Does the drive spin and if so is the strobe speed
>> correct? Does the head move along the rails? Check for fuses.
>>
>> There are several failure modes that can be fixed by cleaning,
>> lubrication, adjusting drive speed, and adjusting the track0 stop.
>> Other failure modes would need a scope and special calibration disk to
>> repair.
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
sticktion



From fwp at deepthought.com  Fri Mar 13 01:13:30 2009
From: fwp at deepthought.com (Frank Pittel)
Date: Fri, 13 Mar 2009 00:13:30 -0500
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <49B995B6.12604.4309ED@jdaggett.gate.net>
References: <49B85685.3010308@adinet.com.uy>
	<49B995B6.12604.4309ED@jdaggett.gate.net>
Message-ID: <20090313051330.GA19273@warlock.deepthought.com>

On Thu, Mar 12, 2009 at 11:07:34PM -0400, jdaggett at gate.net wrote:
> On 11 Mar 2009 at 21:25, Diego Barizo wrote:
> 
> > Besides web access, another good reason to have a browser like program
> > for the CoCo, is to be able to open HTML files, which are the real
> > Portable Document File, - not that other format :-) That was the idea
> > behind my attempt to create what is an HTML renderer, not a web
> > browser. To allow me to create a formatted text file in the PC, and
> > open it in the CoCo keeping most of the formatting.
> > 
> > Diego
> > 
> 
> Fifteen years ago when the HTML was still in its adolescent years yes. Now 
> that HTML has matured into XML there is no way that a stock Coco3 could 
> have the graphics power to do all that XML or even HTML can do. Heck not 
> even the two popular browsers on PCs today support all the features of 
> HTML or even XML. 
> 
> You would have to redign the 6309 processor to run on 45 nM silicon to just 
> think of getting enough computing power. A separate graphics processor 
> with accelleration. 
> 
> Yes you could do a small subset of the HTML language on a Coco3.  But it 
> may very well be highly limited to make surfing the net not a pretty sight.
> 
> just my opinion

I"m interested in seeing how the cocoweb people handle flash and javascript! :-)


From flexser at fiu.edu  Fri Mar 13 00:53:47 2009
From: flexser at fiu.edu (Arthur Flexser)
Date: Fri, 13 Mar 2009 00:53:47 -0400
Subject: [Coco] ADOS 3 Rom Question
In-Reply-To: <437657.59753.qm@web30207.mail.mud.yahoo.com>
References: <dbdeb2610903121720h1e4da7b9t8ec6dd6fd6496f9e@mail.gmail.com>
	<437657.59753.qm@web30207.mail.mud.yahoo.com>
Message-ID: <dbdeb2610903122153v189a31bah6eb3d3fd11b987e2@mail.gmail.com>

Here's some ancient notes of mine on what needs to be connected to
what in order to get a 28-pin EPROM to work in a 24-pin socket.  Maybe
you could wire it up yourself, if you don't want to purchase a
satellite board:

>The FD501 has a 24-pin ROM socket, so you will need to jumper things.
>
>Here's what you need to do to get it to take a 28-pin EPROM. First, on the
>EPROM, bend pins 20, 23, and 26 outward slightly so that they don't plug
>into the socket.  The EPROM will plug into the socket with its pins 1, 2,
>27, and 28 hanging off the end of the socket.
>
>An E stands for a pin of the EPROM, S for a pin of the socket.
>
>Connect:
>  1E to 27E, 28E, 24S (alongside bent-out 26E)
>
>  2E to 21S (alongside bent-out 23E)
>
>  18S (alongside bent-out 20E) to bent-out 23E
>
>  22E to bent-out 20E
>
>  bent-out 26E to pin 37 of the edge connector
>
>
>
>That last connection, involving running a wire to the edge connector, is
>only necessary if you anticipate using a 16K EPROM in the controller (Disk
>BASIC, ADOS, and ADOS-3 take up only 8K; you'd probably only need this if you later
>acquire Extended ADOS-3, which requires a 16K
>27128 EPROM.)

On Thu, Mar 12, 2009 at 10:48 PM, Derek <dml_68 at yahoo.com> wrote:
> My mistake its an FD-501 controller just like it says on the label, in big lettering, in english..FD-501.. I blame 20 years of marriage for a mushy mind
>
> Arthur Flexser <flexser at fiu.edu> wrote: Are you sure that's an FD-502? ?According to my notes, the FD-502 is
> the one controller Tandy made that has a 28-pin ROM socket, which
> should therefore be directly compatible with your 28-pin ADOS-3 EPROM
> (though it requires a small modification to enable the upper 8K of ROM
> space to accommodate Extended ADOS-3.) ?I suspect you actually have an
> FD-500 or FD-501.
>
> Art
>
> On Thu, Mar 12, 2009 at 4:44 PM, Derek ?wrote:
>> I just got a 28 pin ADOS 3 ROM chip and would like some help on installing into an FD-502 Controller if possible. The Controller I have as 2 ROM Sockets the 28 PIN ROM installed says WDC'83 with a chip number WD1773-ph. The 24 Pin ROM is a Tandy Chip number SCM92128P. When I replaced the 28 PIN ROM with the Ados chip I bought it comes up with the standard Disk Extended Basic screen. (I put back the original ROM chip and the controller works fine so I did not destroy anything)
>>
>> My questions are
>> 1: Is this chip compatible with this controller?
>> 2: If yes how do I engage ADOS?
>> 3: If no what controlls will work with it?
>>
>> I do have an old FD-500 controller that has the same configuration (24 Pin ROM has Disk Extdnded Basic and 28 Pin ROM is WDC'83 Chip) But I have not tried on this controller as I wanted to get some help 1st.
>>
>> Thank you
>>
>>
>>
>>
>> ** Mistrust Authority. Promote Decentralization **
>>
>>
>>
>>
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>
> ** Mistrust Authority. Promote Decentralization **
>
>
>
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From nutz4coco at gmail.com  Fri Mar 13 02:08:56 2009
From: nutz4coco at gmail.com (Jim Cox)
Date: Thu, 12 Mar 2009 23:08:56 -0700
Subject: [Coco] Amazing video of a large vintage computer collection
Message-ID: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com>

Hey Gang!

I just came across an amazing video of someone's very large vintage computer
collection on YouTube, and posted the video to my blog at:

http://8-bit-retro-computing.blogspot.com/

The video is 9 and 1/2 minutes long, and feature a CoCo2, and a black
CoCo1!  There is also a Dragon 64.  This guy has systems I have never heard
of.  Swing by and take a look, and let me know what you think.

Cheers,

Jim Cox
http://miba51.blogspot.com/
http://geekswhocare.blogspot.com/
http://8-bit-retro-computing.blogspot.com/


From jps.subscriptions at gmail.com  Fri Mar 13 02:42:13 2009
From: jps.subscriptions at gmail.com (J.P. Samson)
Date: Fri, 13 Mar 2009 00:42:13 -0600
Subject: [Coco] Amazing video of a large vintage computer collection
In-Reply-To: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com>
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com>
Message-ID: <484B91E0-DDEE-4C5D-911B-542A53696878@gmail.com>

On Mar 13, 2009, at 12:08 AM, Jim Cox wrote:
> I just came across an amazing video of someone's very large vintage  
> computer
> collection on YouTube, and posted the video to my blog at:
>
> http://8-bit-retro-computing.blogspot.com/
>
> The video is 9 and 1/2 minutes long, and feature a CoCo2, and a black
> CoCo1!  There is also a Dragon 64.  This guy has systems I have  
> never heard
> of.  Swing by and take a look, and let me know what you think.

He's missing a CoCo 3!  I suspect the CoCo 1 is the gunmetal silver  
version.  The lighting in the video is quite poor, so the image of the  
CoCo 1 in the corner of the shelf looks dark.

-- JP



From georgeramsower at gmail.com  Fri Mar 13 03:57:39 2009
From: georgeramsower at gmail.com (George Ramsower)
Date: Fri, 13 Mar 2009 01:57:39 -0600
Subject: [Coco] How about a CoCo Web Browser?
References: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>,
	<49B7F533.2027.C7583@jdaggett.gate.net>,
	<20090311225306.2D04020A13@qs281.pair.com>
	<49B99337.26604.394996@jdaggett.gate.net>
Message-ID: <002701c9a3b1$621e46a0$6401a8c0@OLDGEORGE>

 Could a Coco do what a cell phone browser does?

 Cell phones have limited graphics and the bandwidth isn't that good, I 
expect. I don't know about this.
.It would seem that if it can be done on a 1.5 inch screen, perhaps the PC 
interface can make it happen, simplify things for the coco and then it may 
work.
 But I wonder... Why bother?
 I think it would be cool to make a system for retro computers to simulate a 
dial up connection. Build a network just for this application and not even 
try to "Browse The Net". The PC can take care of interfacing to the "NET" 
and  direct the data from our retro computers to other retro computers and 
we will be right where it all started many years ago. Apples can talk to 
Amigas, Cocos can talk to Commodors... etc.
 This way, all the OTHER retro computer users could join in on the fun. We 
could get out our old BBS software and begin to do what we were doing many 
years ago on our old dialup modems, only faster.
 Us old farts could have fun emulating the FidoNet and the like. Text 
graphics and all that.

 I could put my OS9 L2 BBS back into operation! That would be fun! .
 This system would be emulated on a PC, whether it be Winderz, Linux, or OSx 
Apple.  No special software for the old computers would be required, I 
expect.
 The PC software would have to emulate a modem. I would think the Hayes 
system is in order.
 I would not have a clue how this would be done, expecially with a BBS 
system that can handle multiple modems, unless it uses multiple RS232 ports 
to the PC. Otherwise, the Retro computer would have to be modified.

 I have no interest in "Browsing The Net" on a Coco. Sorry. However, it 
would be a novelty to play with for a couple of hours and then I would just 
go back to the PC and do it there.

 If one were to make software on a PC to enable this, then we could begin 
contacting the other retro computer users and let them know about this.
 I betcha there would be some interest!


  This might be a dumb idea, but after a few brewskies, it sounds good right 
now!

George 



From georgeramsower at gmail.com  Fri Mar 13 04:18:16 2009
From: georgeramsower at gmail.com (George Ramsower)
Date: Fri, 13 Mar 2009 02:18:16 -0600
Subject: [Coco] FD-502
References: <008f01c9a32e$d949df10$8bdd9d30$@rr.com><49B9C2C1.6080600@worldnet.att.net><00ec01c9a38d$871200b0$95360210$@rr.com>
	<200903130020.57932.gene.heskett@verizon.net>
Message-ID: <007a01c9a3b4$437df9e0$6401a8c0@OLDGEORGE>

I'm wondering if there might be some ripple on the power supply that 
different drives that draw different current could affect that ripple and 
give different results. Old caps, you know!

George
----- Original Message ----- 
From: "Gene Heskett" <gene.heskett at verizon.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, March 12, 2009 10:20 PM
Subject: Re: [Coco] FD-502


> On Thursday 12 March 2009, Bill wrote:
>>The one of them will act like it's formatting a disk. But when it gets its
>>FIRST scan and is supposed to go back and verify (seems like a quicker 
>>scan)
>>it just stays in place with the disk spinning.
>>
>>The other one won't even do that much. It goes through about 1/2 of the
>>first scan, and just sits there with the disk spinning. I have access to 2
>>controllers, and the drives do the same thing, regardless of which
>>controller is used.
>>
> That pretty much verifies my thoughts on it Bill.  Those drives need to 
> come
> out of the box, and have the head sliders cleaned and lubricated again. 
> The
> stepper motor that drives the heads simply cannot overcome the friction
> because the sliders are dirty, and the lubricant that was there 20 years 
> ago
> has now turned into an almost varnish like substance with zero lubrication
> ability.  All its doing today is gluing the dirt in place.  A can of paint
> thinner alcohol and a bag of Sherwood Q-Tips from your druggist (they 
> aren't
> on the shelf except in the pharmacy and they may have to order, in which 
> case
> its a box of 10 bags, 100 to the bag, and about a $15 bill the last time I
> bought some.)  These are wooden sticked Q-Tips, cotton on one end only, 
> and
> the sticks are a good 6" long so you can reach places the common q-tip 
> can't.
> The paint thinner alcohol is far more effective than any rubbing alcohol, 
> and
> comes in qt cans at ACE Hdwe or similar places for about a 5ver per can.
>
> Clean the slider parts up till they look like new, and a drop of 10w30 on
> them, and those drives will likely be as good as new.  10 minute job per 
> drive
> for me once they are out laying out on the table. Maybe it like the piece 
> of
> furniture or a toy that a 6 year old can assemble, so maybe you can find a
> youngster with good eyesight & no arthritis?  And who knows  what a gentle
> touch means?
>
>>Unfortunately, with my poor eyesight and arthritis in my joints, I'm 
>>unable
>>to work on them like I used to.
>>
>>It would be easier for me to sell them "as-is" on eBay and get back a 
>>little
>>of what I spent, or just trade both full units to someone for 2 bare 
>>drives
>>that I could use.
>
> Which, because there haven't been floppy drives made in the 5.25" sizes 
> for a
> good ten years now, are likely very near the 'use by' date too.
>
> One thing that is rarely discussed on the net is where we are, but 
> sometimes
> knowing where one is might lead to a visit from one of our group who lives
> nearby.  That of course is up to you.  Most of this group knows where I am
> within a few miles, in Weston WV.  County seat town, about 5500 
> population,
> and I'm in the phone book.
>>> -----Original Message-----
>>> From: coco-bounces at maltedmedia.com [mailto:coco-
>>> bounces at maltedmedia.com] On Behalf Of Robert Gault
>>> Sent: Thursday, March 12, 2009 9:20 PM
>>> To: CoCoList for Color Computer Enthusiasts
>>> Subject: Re: [Coco] FD-502
>>>
>>> What is the failure mode? Can they read disks from another drive? Can
>>> they format disks? Does the drive spin and if so is the strobe speed
>>> correct? Does the head move along the rails? Check for fuses.
>>>
>>> There are several failure modes that can be fixed by cleaning,
>>> lubrication, adjusting drive speed, and adjusting the track0 stop.
>>> Other failure modes would need a scope and special calibration disk to
>>> repair.
>>
>>--
>>Coco mailing list
>>Coco at maltedmedia.com
>>http://five.pairlist.net/mailman/listinfo/coco
>
>
> -- 
> Cheers, Gene
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> sticktion
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From flexser at fiu.edu  Fri Mar 13 03:24:08 2009
From: flexser at fiu.edu (Arthur Flexser)
Date: Fri, 13 Mar 2009 03:24:08 -0400
Subject: [Coco] Amazing video of a large vintage computer collection
In-Reply-To: <484B91E0-DDEE-4C5D-911B-542A53696878@gmail.com>
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com>
	<484B91E0-DDEE-4C5D-911B-542A53696878@gmail.com>
Message-ID: <dbdeb2610903130024h358c1b23ib83f660372c4a43f@mail.gmail.com>

I think the CoCo 1 was black plastic, under the silver paint.
When the paint got too scratched up, some folks removed it and voila,
black CoCo 1.

Art

On Fri, Mar 13, 2009 at 2:42 AM, J.P. Samson
<jps.subscriptions at gmail.com> wrote:
> On Mar 13, 2009, at 12:08 AM, Jim Cox wrote:
>>
>> I just came across an amazing video of someone's very large vintage
>> computer
>> collection on YouTube, and posted the video to my blog at:
>>
>> http://8-bit-retro-computing.blogspot.com/
>>
>> The video is 9 and 1/2 minutes long, and feature a CoCo2, and a black
>> CoCo1! ?There is also a Dragon 64. ?This guy has systems I have never
>> heard
>> of. ?Swing by and take a look, and let me know what you think.
>
> He's missing a CoCo 3! ?I suspect the CoCo 1 is the gunmetal silver version.
> ?The lighting in the video is quite poor, so the image of the CoCo 1 in the
> corner of the shelf looks dark.
>
> -- JP
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From snhirsch at gmail.com  Fri Mar 13 06:56:04 2009
From: snhirsch at gmail.com (Steven Hirsch)
Date: Fri, 13 Mar 2009 06:56:04 -0400 (EDT)
Subject: [Coco] FD-502
In-Reply-To: <007a01c9a3b4$437df9e0$6401a8c0@OLDGEORGE>
References: <008f01c9a32e$d949df10$8bdd9d30$@rr.com><49B9C2C1.6080600@worldnet.att.net><00ec01c9a38d$871200b0$95360210$@rr.com>
	<200903130020.57932.gene.heskett@verizon.net>
	<007a01c9a3b4$437df9e0$6401a8c0@OLDGEORGE>
Message-ID: <alpine.DEB.2.00.0903130653420.12255@duo>

On Fri, 13 Mar 2009, George Ramsower wrote:

> I'm wondering if there might be some ripple on the power supply that 
> different drives that draw different current could affect that ripple and 
> give different results. Old caps, you know!

Very likely.  Most external drive enclosures from that vintage had analog 
power supplies with cheap electrolytic caps.  Every one I've dug out of 
the garage has needed them replaced.  It's surprising how close some 
drives can come to working properly with 120Hz. AC power from a bridge 
rectifier :-).


-- 


From cwgordon at carolina.rr.com  Fri Mar 13 08:19:07 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Fri, 13 Mar 2009 07:19:07 -0500
Subject: [Coco] Coco to parallel printer
Message-ID: <011601c9a3d5$e8bd2040$ba3760c0$@rr.com>

Does anyone have an adapter to allow a Coco to print to a "regular" printer?

Thanks

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784





From mark at cloud9tech.com  Fri Mar 13 07:43:36 2009
From: mark at cloud9tech.com (Mark Marlette)
Date: Fri, 13 Mar 2009 06:43:36 -0500
Subject: [Coco] HDB-DOS-Drivewire 3
In-Reply-To: <alpine.DEB.2.00.0903122026340.12255@duo>
References: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<alpine.DEB.2.00.0903122026340.12255@duo>
Message-ID: <6.2.5.6.2.20090313064141.02ae5a40@cloud9tech.com>


I currently do not have a DW3 setup in place as I am working on other 
Cloud-9 projects.

Boisy and or, all it takes is megaread and NitrOS-9.

Regards,

Mark
Cloud-9


At 3/12/2009 07:27 PM, you wrote:
>On Thu, 12 Mar 2009, Mark Marlette wrote:
>
>>
>>Testing I did using MegaRead under NitrOS-9 and SuperDriver......
>>
>>SCSI, ~11 seconds
>>SuperIDE/CF, ~19 seconds.
>>
>>We only know one speed, to the floorboard!
>
>What did the Drivewire drive benchmark as?
>
>--
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco
>
>
>No virus found in this incoming message.
>Checked by AVG - www.avg.com
>Version: 8.0.237 / Virus Database: 270.11.11/1997 - Release Date: 
>03/12/09 10:38:00


From coconut at pritchard.ca  Fri Mar 13 08:39:55 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Fri, 13 Mar 2009 07:39:55 -0500
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <002701c9a3b1$621e46a0$6401a8c0@OLDGEORGE>
References: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>,
	<49B7F533.2027.C7583@jdaggett.gate.net>,
	<20090311225306.2D04020A13@qs281.pair.com>
	<49B99337.26604.394996@jdaggett.gate.net>
	<002701c9a3b1$621e46a0$6401a8c0@OLDGEORGE>
Message-ID: <C716DAA8-FC8E-4CA3-89B3-4E8FD80D8EE7@pritchard.ca>

I finally bought a USB to serial adapter to hook up to my Mac OS X  
system so that I can use a built in Linux/BSD port routing command to  
route a TCP/IP port to the serial adapter which will be connecting to  
either my CoCo 1, my Apple IIgs, or one of my GIMIX Ghost systems.  I  
know the functionality you look for already exists, in the various  
Linux and BSD distributions, and others on this list have pointed to  
TCP/IP to comm port packages in the past and have in fact hooked up  
their old school systems to the net to run their old BBS software or  
just to make their C64 or other server up web pages.

So hop to it! ;)

Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies



On 13-Mar-09, at 2:57 AM, George Ramsower wrote:

> Could a Coco do what a cell phone browser does?
>
> Cell phones have limited graphics and the bandwidth isn't that good,  
> I expect. I don't know about this.
> .It would seem that if it can be done on a 1.5 inch screen, perhaps  
> the PC interface can make it happen, simplify things for the coco  
> and then it may work.
> But I wonder... Why bother?
> I think it would be cool to make a system for retro computers to  
> simulate a dial up connection. Build a network just for this  
> application and not even try to "Browse The Net". The PC can take  
> care of interfacing to the "NET" and  direct the data from our retro  
> computers to other retro computers and we will be right where it all  
> started many years ago. Apples can talk to Amigas, Cocos can talk to  
> Commodors... etc.
> This way, all the OTHER retro computer users could join in on the  
> fun. We could get out our old BBS software and begin to do what we  
> were doing many years ago on our old dialup modems, only faster.
> Us old farts could have fun emulating the FidoNet and the like. Text  
> graphics and all that.
>
> I could put my OS9 L2 BBS back into operation! That would be fun! .
> This system would be emulated on a PC, whether it be Winderz, Linux,  
> or OSx Apple.  No special software for the old computers would be  
> required, I expect.
> The PC software would have to emulate a modem. I would think the  
> Hayes system is in order.
> I would not have a clue how this would be done, expecially with a  
> BBS system that can handle multiple modems, unless it uses multiple  
> RS232 ports to the PC. Otherwise, the Retro computer would have to  
> be modified.
>
> I have no interest in "Browsing The Net" on a Coco. Sorry. However,  
> it would be a novelty to play with for a couple of hours and then I  
> would just go back to the PC and do it there.
>
> If one were to make software on a PC to enable this, then we could  
> begin contacting the other retro computer users and let them know  
> about this.
> I betcha there would be some interest!
>
>
> This might be a dumb idea, but after a few brewskies, it sounds good  
> right now!
>
> George
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From boisy at tee-boy.com  Fri Mar 13 08:46:12 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 13 Mar 2009 07:46:12 -0500
Subject: [Coco] HDB-DOS-Drivewire 3
In-Reply-To: <6.2.5.6.2.20090313064141.02ae5a40@cloud9tech.com>
References: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net>
	<alpine.DEB.2.00.0903122026340.12255@duo>
	<6.2.5.6.2.20090313064141.02ae5a40@cloud9tech.com>
Message-ID: <AA21ADED-1031-4BA7-9734-EF58130C36FA@tee-boy.com>

I just ran a megaread on under NitrOS-9/6309 Level 2 running DriveWire  
3 to an eMac G4 1.42GHz server, and here's what I got:

228 seconds

A more recent system could probably do better, but not by a large  
margin.  Even if you were to cut this in half (114 seconds, which is a  
stretch to think that it could be cut in half) it is still an order of  
magnitude slower than SCSI and way slower than IDE.  A more comparable  
test would be against a floppy system, though current floppies don't  
hold a megabyte.

I'm not sure how much slower or faster DriveWire 3 is than a floppy at  
raw reads/writes but there is something to be said for NitrOS-9  
booting faster from DriveWire 3 than from a floppy disk, and this has  
a lot to do fact that DriveWire 3 is not encumbered by the time  
consuming head movement and track seeks of a floppy disk drive.

If someone has the time (hint hint!), they could modify megaread.asm  
in the NitrOS-9 Project to take an optional parameter: the number of  
1K blocks to read (currently 1,024).  This would allow megaread to  
work with smaller sized devices and results could be extrapolated from  
that.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com

On Mar 13, 2009, at 6:43 AM, Mark Marlette wrote:

>
> I currently do not have a DW3 setup in place as I am working on  
> other Cloud-9 projects.
>
> Boisy and or, all it takes is megaread and NitrOS-9.
>
> Regards,
>
> Mark
> Cloud-9
>
>
> At 3/12/2009 07:27 PM, you wrote:
>> On Thu, 12 Mar 2009, Mark Marlette wrote:
>>
>>>
>>> Testing I did using MegaRead under NitrOS-9 and SuperDriver......
>>>
>>> SCSI, ~11 seconds
>>> SuperIDE/CF, ~19 seconds.
>>>
>>> We only know one speed, to the floorboard!
>>
>> What did the Drivewire drive benchmark as?
>>
>> --
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.237 / Virus Database: 270.11.11/1997 - Release Date:  
>> 03/12/09 10:38:00
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From coconut at pritchard.ca  Fri Mar 13 08:48:40 2009
From: coconut at pritchard.ca (Ryan Pritchard)
Date: Fri, 13 Mar 2009 07:48:40 -0500
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <C716DAA8-FC8E-4CA3-89B3-4E8FD80D8EE7@pritchard.ca>
References: <052725A568B14D9882FEA6B8836135BA@FANTASYWARE>
	<49B7F533.2027.C7583@jdaggett.gate.net>
	<20090311225306.2D04020A13@qs281.pair.com>
	<49B99337.26604.394996@jdaggett.gate.net>
	<002701c9a3b1$621e46a0$6401a8c0@OLDGEORGE>
	<C716DAA8-FC8E-4CA3-89B3-4E8FD80D8EE7@pritchard.ca>
Message-ID: <1806abd60903130548l1639028dq97da9e1a670bd991@mail.gmail.com>

One adder I should make is that I am still waiting on the USB adapter
as I just won the eBAY auction for it this week, so probably won't
receive it for another 2-3 weeks.  So I have not put said
understanding into practice, but I will likely blog about it on my
retrocomputing.ca site when I get the TCP/IP to serial port routing
working.  Not to mention posting my findings here.

On Fri, Mar 13, 2009 at 7:39 AM, Ryan Pritchard <coconut at pritchard.ca> wrote:
> I finally bought a USB to serial adapter to hook up to my Mac OS X system so
> that I can use a built in Linux/BSD port routing command to route a TCP/IP
> port to the serial adapter which will be connecting to either my CoCo 1, my
> Apple IIgs, or one of my GIMIX Ghost systems. ?I know the functionality you
> look for already exists, in the various Linux and BSD distributions, and
> others on this list have pointed to TCP/IP to comm port packages in the past
> and have in fact hooked up their old school systems to the net to run their
> old BBS software or just to make their C64 or other server up web pages.
>
> So hop to it! ;)
>
> Regards,
>
> Ryan Pritchard
> Fun Extends All Basic Life Expectancies
>
>
>
> On 13-Mar-09, at 2:57 AM, George Ramsower wrote:
>
>> Could a Coco do what a cell phone browser does?
>>
>> Cell phones have limited graphics and the bandwidth isn't that good, I
>> expect. I don't know about this.
>> .It would seem that if it can be done on a 1.5 inch screen, perhaps the PC
>> interface can make it happen, simplify things for the coco and then it may
>> work.
>> But I wonder... Why bother?
>> I think it would be cool to make a system for retro computers to simulate
>> a dial up connection. Build a network just for this application and not even
>> try to "Browse The Net". The PC can take care of interfacing to the "NET"
>> and ?direct the data from our retro computers to other retro computers and
>> we will be right where it all started many years ago. Apples can talk to
>> Amigas, Cocos can talk to Commodors... etc.
>> This way, all the OTHER retro computer users could join in on the fun. We
>> could get out our old BBS software and begin to do what we were doing many
>> years ago on our old dialup modems, only faster.
>> Us old farts could have fun emulating the FidoNet and the like. Text
>> graphics and all that.
>>
>> I could put my OS9 L2 BBS back into operation! That would be fun! .
>> This system would be emulated on a PC, whether it be Winderz, Linux, or
>> OSx Apple. ?No special software for the old computers would be required, I
>> expect.
>> The PC software would have to emulate a modem. I would think the Hayes
>> system is in order.
>> I would not have a clue how this would be done, expecially with a BBS
>> system that can handle multiple modems, unless it uses multiple RS232 ports
>> to the PC. Otherwise, the Retro computer would have to be modified.
>>
>> I have no interest in "Browsing The Net" on a Coco. Sorry. However, it
>> would be a novelty to play with for a couple of hours and then I would just
>> go back to the PC and do it there.
>>
>> If one were to make software on a PC to enable this, then we could begin
>> contacting the other retro computer users and let them know about this.
>> I betcha there would be some interest!
>>
>>
>> This might be a dumb idea, but after a few brewskies, it sounds good right
>> now!
>>
>> George
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>



-- 
Regards,

Ryan Pritchard
Fun Extends All Basic Life Expectancies


From cwgordon at carolina.rr.com  Fri Mar 13 10:43:02 2009
From: cwgordon at carolina.rr.com (Bill)
Date: Fri, 13 Mar 2009 09:43:02 -0500
Subject: [Coco] Saving ML programs
Message-ID: <011a01c9a3ea$0381c200$0a854600$@rr.com>

I'm trying to save machine language programs to disk, but have no idea where
to save them to: savem "program.bin", first address, last address, execution
address

Help??

______________________________________
*Square One Christian BBS
Web access: http://www.sq1bbs.com/index.php
Telnet access: telnet://sq1bbs.com

A Taste of CoCo Forum
http://www.sq1bbs.com/coco/index.php

Live chat room - Ventrilo 3.x required
Host name or IP: www.sq1bbs.com
Port: 3784




From robert.gault at worldnet.att.net  Fri Mar 13 10:06:43 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Fri, 13 Mar 2009 10:06:43 -0400
Subject: [Coco] Saving ML programs
In-Reply-To: <011a01c9a3ea$0381c200$0a854600$@rr.com>
References: <011a01c9a3ea$0381c200$0a854600$@rr.com>
Message-ID: <49BA6873.8020406@worldnet.att.net>

Bill wrote:
> I'm trying to save machine language programs to disk, but have no idea where
> to save them to: savem "program.bin", first address, last address, execution
> address
> 
> Help??
> 

Your question does not make any sense. Do you mean you don't know what 
values to enter for "first address, last address, execution address"?

If true, then you must be trying to save an ml program you did not 
write. If not, I haven't a clue what you mean.

Presumably these programs were loaded from a disk although tape is a 
possibility. You can download a program from my web site, MLFinder, that 
will read a disk to determine these addresses.
http://home.att.net/~robert.gault/Coco/Downloads/Downloads.htm


From georgeramsower at gmail.com  Fri Mar 13 11:52:14 2009
From: georgeramsower at gmail.com (George Ramsower)
Date: Fri, 13 Mar 2009 09:52:14 -0600
Subject: [Coco] Saving ML programs
References: <011a01c9a3ea$0381c200$0a854600$@rr.com>
	<49BA6873.8020406@worldnet.att.net>
Message-ID: <001601c9a3f3$ae85e240$6401a8c0@OLDGEORGE>

From: "Robert Gault"

> Bill wrote:
>> I'm trying to save machine language programs to disk, but have no idea 
>> where
>> to save them to: savem "program.bin", first address, last address, 
>> execution
>> address
>>
>> Help??
>>
>
> Your question does not make any sense. Do you mean you don't know what 
> values to enter for "first address, last address, execution address"?
>
> If true, then you must be trying to save an ml program you did not write. 
> If not, I haven't a clue what you mean.
>
> Presumably these programs were loaded from a disk although tape is a 
> possibility. You can download a program from my web site, MLFinder, that 
> will read a disk to determine these addresses.
> http://home.att.net/~robert.gault/Coco/Downloads/Downloads.htm

 Not being a real programmer, I understood that question totally. He wants 
to know how to find the start, end and execution addresses of a given 
program.
 At one time, a long time ago.... far, far away, someone had the answer to 
that. It seems that after loading a machine language program, this info was 
stored at specific addresses in the coco and some PEEKING would reveal those 
values. I just don't remember how to do it.

 George 



From mechacoco at gmail.com  Fri Mar 13 11:18:36 2009
From: mechacoco at gmail.com (Darren A)
Date: Fri, 13 Mar 2009 09:18:36 -0600
Subject: [Coco] Saving ML programs
In-Reply-To: <001601c9a3f3$ae85e240$6401a8c0@OLDGEORGE>
References: <011a01c9a3ea$0381c200$0a854600$@rr.com>
	<49BA6873.8020406@worldnet.att.net>
	<001601c9a3f3$ae85e240$6401a8c0@OLDGEORGE>
Message-ID: <5d802cd0903130818x1dfc595eh5f1569f3c908c8b3@mail.gmail.com>

On 3/13/09, George Ramsower wrote:
>
>  Not being a real programmer, I understood that question totally. He wants
> to know how to find the start, end and execution addresses of a given
> program.
>  At one time, a long time ago.... far, far away, someone had the answer to
> that. It seems that after loading a machine language program, this info was
> stored at specific addresses in the coco and some PEEKING would reveal those
> values. I just don't remember how to do it.
>

--

You can PEEK at $9D:9E to get the EXEC address after loading an ML
program. Sometimes that will be the same as the START address.  There
are no PEEKs that will tell you the actual START and END addresses.
Furthermore, the ML file could be a multi-segment file meaning that it
can have code and data loaded into multiple non-contiguous regions of
memory.

Darren


From jcewy at swbell.net  Fri Mar 13 11:18:55 2009
From: jcewy at swbell.net (Joel Ewy)
Date: Fri, 13 Mar 2009 10:18:55 -0500
Subject: [Coco] Amazing video of a large vintage computer collection
In-Reply-To: <dbdeb2610903130024h358c1b23ib83f660372c4a43f@mail.gmail.com>
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com>	<484B91E0-DDEE-4C5D-911B-542A53696878@gmail.com>
	<dbdeb2610903130024h358c1b23ib83f660372c4a43f@mail.gmail.com>
Message-ID: <49BA795F.4050704@swbell.net>

Arthur Flexser wrote:
> I think the CoCo 1 was black plastic, under the silver paint.
> When the paint got too scratched up, some folks removed it and voila,
> black CoCo 1.
>
>   
However, if you go to Benway's web site, he has a photo of what 
presumably is the the CoCo 1 in the video, and in better light it 
appears to be a normal silver CoCo:  
http://www.benwaysworld.co.uk/computersnconsoles/TRS80ColorComputer.html#coco

JCE
> Art
>
> On Fri, Mar 13, 2009 at 2:42 AM, J.P. Samson
> <jps.subscriptions at gmail.com> wrote:
>   
>> On Mar 13, 2009, at 12:08 AM, Jim Cox wrote:
>>     
>>> I just came across an amazing video of someone's very large vintage
>>> computer
>>> collection on YouTube, and posted the video to my blog at:
>>>
>>> http://8-bit-retro-computing.blogspot.com/
>>>
>>> The video is 9 and 1/2 minutes long, and feature a CoCo2, and a black
>>> CoCo1!  There is also a Dragon 64.  This guy has systems I have never
>>> heard
>>> of.  Swing by and take a look, and let me know what you think.
>>>       
>> He's missing a CoCo 3!  I suspect the CoCo 1 is the gunmetal silver version.
>>  The lighting in the video is quite poor, so the image of the CoCo 1 in the
>> corner of the shelf looks dark.
>>
>> -- JP
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>     
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>   



From n6il at ocs.net  Fri Mar 13 11:52:26 2009
From: n6il at ocs.net (Michael Furman)
Date: Fri, 13 Mar 2009 08:52:26 -0700
Subject: [Coco] Coco to parallel printer
In-Reply-To: <011601c9a3d5$e8bd2040$ba3760c0$@rr.com>
References: <011601c9a3d5$e8bd2040$ba3760c0$@rr.com>
Message-ID: <0B545BEC-3006-445C-A52D-3EECAF233C29@ocs.net>

Bill,

To connect a Coco to a printer with a 36-pin Centronics Parallel  
connector (which is what I assume you meant by a "regular" printer)  
you need a serial to parallel printer adapter.  These used to be  
common but are a lot harder to find now that everything uses USB.   
Pretty much any will do as long as it supports 600 or 1200 baud and  
hardware (DTR) flow control.  Here is an example, you should be able  
to find something cheaper elsewhere:

http://www.pccables.com/30200.htm


This one supports 1200 baud which will work:

http://www.provantage.com/aten-sxp320a~7ATEN02J.htm

Refer to pages 38 and 39 of the Coco1 Technical Reference  Manual for  
the printer settings and connection information (this is more complete  
than the Coco3 manual pp 313-314)
ftp://ftp.maltedmedia.com/coco/MANUALS1/TANDY_HW/COCO/COCO1/CoCo1TM.pdf

On Mar 13, 2009, at 5:19 AM, Bill wrote:

> Does anyone have an adapter to allow a Coco to print to a "regular"  
> printer?
>
> Thanks
>
> ______________________________________
> *Square One Christian BBS
> Web access: http://www.sq1bbs.com/index.php
> Telnet access: telnet://sq1bbs.com
>
> A Taste of CoCo Forum
> http://www.sq1bbs.com/coco/index.php
>
> Live chat room - Ventrilo 3.x required
> Host name or IP: www.sq1bbs.com
> Port: 3784
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From badfrog at gmail.com  Fri Mar 13 12:43:00 2009
From: badfrog at gmail.com (Sean)
Date: Fri, 13 Mar 2009 11:43:00 -0500
Subject: [Coco] Coco to parallel printer
In-Reply-To: <0B545BEC-3006-445C-A52D-3EECAF233C29@ocs.net>
References: <011601c9a3d5$e8bd2040$ba3760c0$@rr.com>
	<0B545BEC-3006-445C-A52D-3EECAF233C29@ocs.net>
Message-ID: <9efa17da0903130943x14cb3b2n45e1ee3eefcc19f4@mail.gmail.com>

I have one available I would be willing to part with.  And it's CoCo specific.

http://picasaweb.google.com/lh/photo/thOZYPoFkZnIf2EYFqgWyA?authkey=Gv1sRgCIKYvLL49PucmQE&feat=directlink

Make an offer that's reasonable enough to get off the couch, dig
through some boxes, and go mail it.  I think I may have the
instructions somewhere too.

But I think the other issue is finding a printer it would work with.
Don't most printers rely on the PC and drivers to do most of the work
now?

On Fri, Mar 13, 2009 at 10:52 AM, Michael Furman <n6il at ocs.net> wrote:
> Bill,
>
> To connect a Coco to a printer with a 36-pin Centronics Parallel connector
> (which is what I assume you meant by a "regular" printer) you need a serial
> to parallel printer adapter. ?These used to be common but are a lot harder
> to find now that everything uses USB. ?Pretty much any will do as long as it
> supports 600 or 1200 baud and hardware (DTR) flow control. ?Here is an
> example, you should be able to find something cheaper elsewhere:
>
> http://www.pccables.com/30200.htm
>
>
> This one supports 1200 baud which will work:
>
> http://www.provantage.com/aten-sxp320a~7ATEN02J.htm
>
> Refer to pages 38 and 39 of the Coco1 Technical Reference ?Manual for the
> printer settings and connection information (this is more complete than the
> Coco3 manual pp 313-314)
> ftp://ftp.maltedmedia.com/coco/MANUALS1/TANDY_HW/COCO/COCO1/CoCo1TM.pdf
>
> On Mar 13, 2009, at 5:19 AM, Bill wrote:
>
>> Does anyone have an adapter to allow a Coco to print to a "regular"
>> printer?
>>
>> Thanks
>>
>> ______________________________________
>> *Square One Christian BBS
>> Web access: http://www.sq1bbs.com/index.php
>> Telnet access: telnet://sq1bbs.com
>>
>> A Taste of CoCo Forum
>> http://www.sq1bbs.com/coco/index.php
>>
>> Live chat room - Ventrilo 3.x required
>> Host name or IP: www.sq1bbs.com
>> Port: 3784
>>
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From operator at coco3.com  Fri Mar 13 15:16:47 2009
From: operator at coco3.com (Roger Taylor)
Date: Fri, 13 Mar 2009 14:16:47 -0500
Subject: [Coco] Saving ML programs
In-Reply-To: <011a01c9a3ea$0381c200$0a854600$@rr.com>
References: <011a01c9a3ea$0381c200$0a854600$@rr.com>
Message-ID: <20090313191744.C3CAB20A14@qs281.pair.com>

At 09:43 AM 3/13/2009, you wrote:
>I'm trying to save machine language programs to disk, but have no idea where
>to save them to: savem "program.bin", first address, last address, execution
>address
>
>Help??



Bill, it's hard to keep up with your questions they're coming so frequent.
So, let me be the one to say it...   you're trying to bite off more 
than you can chew at once.  Slow down.  :)


-- 
Roger Taylor

http://www.wordofthedayonline.com



From bronco2078p at yahoo.com  Fri Mar 13 15:00:09 2009
From: bronco2078p at yahoo.com (Nathan Verrocchi)
Date: Fri, 13 Mar 2009 12:00:09 -0700 (PDT)
Subject: [Coco] [Color Computer] Re: looking for speech sound module
In-Reply-To: <196601.64901.qm@web55903.mail.re3.yahoo.com>
Message-ID: <784261.80297.qm@web54501.mail.re2.yahoo.com>

If he doesn't have it?? I just posted one on my ecrater site



      


From jdaggett at gate.net  Fri Mar 13 16:49:52 2009
From: jdaggett at gate.net (jdaggett at gate.net)
Date: Fri, 13 Mar 2009 16:49:52 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <49B9CDB7.4050006@cox.net>
References: <20090311182803.GE8761@tuxdriver.com>,
	<49B993C2.4735.3B68FC@jdaggett.gate.net>,
	<49B9CDB7.4050006@cox.net>
Message-ID: <49BA8EB0.28201.EA091@jdaggett.gate.net>

On 12 Mar 2009 at 20:06, Tim Fadden wrote:

> Cost/time effective?  We are talking about a COCO right?  If these are
> your concerns, why do you even mess with a CoCo in the first place?
> 
> I do it for the fun of it.   If I wanted fast and glitzy, I would be
> using my quad core 3 gig machine.
> 
> Tim.
> 

Actually to surf the net with the PC that you mentioned is a bit overkill 
there. A single Pentium at 250 MHz is more than sufficient. 

I am not trying to be negative but trying to point out that a Coco is a slow 
machine to be surfing the net. As I stated before other than the fascination 
of doing it for the fun of it there is no real practical reason to do so. Again I 
reiterate that doing it would be a project to do it so as to say that it can be 
done. 

Besides the Coco was the first computer that I ever had and the 6809 
assembly was the first that I learned. So I still have an affinity to the 
machine and assembly code. 

james
> jdaggett at gate.net wrote:
> > On 11 Mar 2009 at 17:56, John W. Linville wrote:
> >
> >   
> >> On Wed, Mar 11, 2009 at 05:30:27PM -0400, jdaggett at gate.net wrote:
> >> > On 11 Mar 2009 at 14:28, John W. Linville wrote: > > > On Tue,
> >> Mar 10, 2009 at 10:37:03PM -0400, jdaggett at gate.net wrote: > > >
> >> First off you need some means of connecting to the internet either
> >> > > through > a modem or through a PC/MAC. Then you can think about
> >> a web > > browser.
> >>     
> >>> Can't put the cart before the horse or the cart wont go > >
> >>>       
> >> anywhere. > > > > I think he was presuming to use the "get any file
> >> via http" feature of > > CoCoNet to account for the communications
> >> piece... > > > > John > > Yes that would work if you don't mind 56K
> >> dial up speeds. 
> >>
> >> Probably 115k or so FWIW, but I doubt the coco could eat the data
> >> much faster than that anyway.
> >>
> >>     
> >>> Better off would be to have a dedicated hardware that floated on
> >>> the buss that did all the TCP/IP stuff and hooked up to a router
> >>> to do the PPPOE stuff. It would be faster. 
> >>>       
> >> Sure, but so would just using a PC... :-)
> >>
> >>     
> >>> Sorry I am not thrilled with dial up speeds for internet
> >>> connections. Even on  Coco3. Roger's BT and Boisey's Drivewire are
> >>> fine products for what they do and do best. Trying to put web
> >>> browser traffic over it to a PC or a MAC to gain internet is not
> >>> efficient or cost effective in my opinion. 
> >>>       
> >> No probably not.  But it would be a damned cool project for someone
> >> that would enjoy that as a hobby. :-)
> >>
> >> John
> >>     
> >
> >
> > Yes it is one of those projects to say I did it so that I can prove
> > it can be done type feelings. 
> >
> > james
> >
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> >
> >
> >   
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco




From jdaggett at gate.net  Fri Mar 13 16:51:55 2009
From: jdaggett at gate.net (jdaggett at gate.net)
Date: Fri, 13 Mar 2009 16:51:55 -0400
Subject: [Coco] How about a CoCo Web Browser?
In-Reply-To: <20090313051330.GA19273@warlock.deepthought.com>
References: <49B85685.3010308@adinet.com.uy>,
	<49B995B6.12604.4309ED@jdaggett.gate.net>,
	<20090313051330.GA19273@warlock.deepthought.com>
Message-ID: <49BA8F2B.17818.108176@jdaggett.gate.net>

On 13 Mar 2009 at 0:13, Frank Pittel wrote:

> On Thu, Mar 12, 2009 at 11:07:34PM -0400, jdaggett at gate.net wrote: >
> On 11 Mar 2009 at 21:25, Diego Barizo wrote: > > > Besides web access,
> another good reason to have a browser like program > > for the CoCo,
> is to be able to open HTML files, which are the real > > Portable
> Document File, - not that other format :-) That was the idea > >
> behind my attempt to create what is an HTML renderer, not a web > >
> browser. To allow me to create a formatted text file in the PC, and >
> > open it in the CoCo keeping most of the formatting. > > > > Diego >
> > > > Fifteen years ago when the HTML was still in its adolescent
> years yes. Now > that HTML has matured into XML there is no way that a
> stock Coco3 could > have the graphics power to do all that XML or even
> HTML can do. Heck not > even the two popular browsers on PCs today
> support all the features of > HTML or even XML. > > You would have to
> redign the 6309 processor to run on 45 nM silicon to just > think of
> getting enough computing power. A separate graphics processor > with
> accelleration. > > Yes you could do a small subset of the HTML
> language on a Coco3.  But it > may very well be highly limited to make
> surfing the net not a pretty sight. > > just my opinion
> 
> I"m interested in seeing how the cocoweb people handle flash and
> javascript! :-)
> 


I am not even going to go there. Granted it would be something to do just 
to prove it could be done but not up my alley. 

james 




From devries.bob at gmail.com  Fri Mar 13 17:06:20 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Sat, 14 Mar 2009 07:06:20 +1000
Subject: [Coco] HDB-DOS-Drivewire 3
References: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net><alpine.DEB.2.00.0903122026340.12255@duo><6.2.5.6.2.20090313064141.02ae5a40@cloud9tech.com>
	<AA21ADED-1031-4BA7-9734-EF58130C36FA@tee-boy.com>
Message-ID: <001e01c9a41f$91925e80$0701a8c0@master>

Boisy,

IIRC, there's an OS9 programme called QMEGREAD which is similar to megaread, 
but reads just a quarter megabyte of data.
It should be on RTSI.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Boisy Pitre" <boisy at tee-boy.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Friday, March 13, 2009 10:46 PM
Subject: Re: [Coco] HDB-DOS-Drivewire 3


>I just ran a megaread on under NitrOS-9/6309 Level 2 running DriveWire  3 
>to an eMac G4 1.42GHz server, and here's what I got:
>
> 228 seconds
>
> A more recent system could probably do better, but not by a large  margin. 
> Even if you were to cut this in half (114 seconds, which is a  stretch to 
> think that it could be cut in half) it is still an order of  magnitude 
> slower than SCSI and way slower than IDE.  A more comparable  test would 
> be against a floppy system, though current floppies don't  hold a 
> megabyte.
>
> I'm not sure how much slower or faster DriveWire 3 is than a floppy at 
> raw reads/writes but there is something to be said for NitrOS-9  booting 
> faster from DriveWire 3 than from a floppy disk, and this has  a lot to do 
> fact that DriveWire 3 is not encumbered by the time  consuming head 
> movement and track seeks of a floppy disk drive.
>
> If someone has the time (hint hint!), they could modify megaread.asm  in 
> the NitrOS-9 Project to take an optional parameter: the number of  1K 
> blocks to read (currently 1,024).  This would allow megaread to  work with 
> smaller sized devices and results could be extrapolated from  that.
>
> Regards,
> Boisy G. Pitre
> --
> Tee-Boy
> Mobile: 337.781.3570
> Email: boisy at tee-boy.com
> Web: http://www.tee-boy.com
>
> On Mar 13, 2009, at 6:43 AM, Mark Marlette wrote:
>
>>
>> I currently do not have a DW3 setup in place as I am working on  other 
>> Cloud-9 projects.
>>
>> Boisy and or, all it takes is megaread and NitrOS-9.
>>
>> Regards,
>>
>> Mark
>> Cloud-9
>>
>>
>> At 3/12/2009 07:27 PM, you wrote:
>>> On Thu, 12 Mar 2009, Mark Marlette wrote:
>>>
>>>>
>>>> Testing I did using MegaRead under NitrOS-9 and SuperDriver......
>>>>
>>>> SCSI, ~11 seconds
>>>> SuperIDE/CF, ~19 seconds.
>>>>
>>>> We only know one speed, to the floorboard!
>>>
>>> What did the Drivewire drive benchmark as?
>>>
>>> --
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com
>>> Version: 8.0.237 / Virus Database: 270.11.11/1997 - Release Date: 
>>> 03/12/09 10:38:00
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From gene.heskett at verizon.net  Fri Mar 13 17:23:14 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Fri, 13 Mar 2009 17:23:14 -0400
Subject: [Coco] Coco to parallel printer
In-Reply-To: <9efa17da0903130943x14cb3b2n45e1ee3eefcc19f4@mail.gmail.com>
References: <011601c9a3d5$e8bd2040$ba3760c0$@rr.com>
	<0B545BEC-3006-445C-A52D-3EECAF233C29@ocs.net>
	<9efa17da0903130943x14cb3b2n45e1ee3eefcc19f4@mail.gmail.com>
Message-ID: <200903131723.14277.gene.heskett@verizon.net>

On Friday 13 March 2009, Sean wrote:
>I have one available I would be willing to part with.  And it's CoCo
> specific.
>
>http://picasaweb.google.com/lh/photo/thOZYPoFkZnIf2EYFqgWyA?authkey=Gv1sRgCI
>KYvLL49PucmQE&feat=directlink
>
>Make an offer that's reasonable enough to get off the couch, dig
>through some boxes, and go mail it.  I think I may have the
>instructions somewhere too.
>
>But I think the other issue is finding a printer it would work with.
>Don't most printers rely on the PC and drivers to do most of the work
>now?

Yes, there hasn't been a smart printer made in a decade plus now, and what we 
do have are all equipt with usb interfaces.

I have a kluge rigged up that did work for a while, and then the printer 
driver didn't work anymore.  I was feeding the bitbanger, as /p, to an FDTI 
serial to usb adapter, and then capturing whatever came up the pipe to a file, 
and when there was no more new data for several seconds, printing it using the 
normal facilities of this linux box, sending it back over the same cable to a 
$120 Brother laser printer plugged into another port on the hub so the printer 
was actually on the coco's desk.  That, when it worked, worked very well 
indeed as the laser is the fastest printer here by about 2 magnitudes.  The 
color ink squirters are many times slower.

It's all in a couple of bash scripts.  Ugly, worked a treat.  Anybody wants 
them, yell.

>On Fri, Mar 13, 2009 at 10:52 AM, Michael Furman <n6il at ocs.net> wrote:
>> Bill,
>>
>> To connect a Coco to a printer with a 36-pin Centronics Parallel connector
>> (which is what I assume you meant by a "regular" printer) you need a
>> serial to parallel printer adapter. ?These used to be common but are a lot
>> harder to find now that everything uses USB. ?Pretty much any will do as
>> long as it supports 600 or 1200 baud and hardware (DTR) flow control.
>> ?Here is an example, you should be able to find something cheaper
>> elsewhere:
>>
>> http://www.pccables.com/30200.htm
>>
>>
>> This one supports 1200 baud which will work:
>>
>> http://www.provantage.com/aten-sxp320a~7ATEN02J.htm
>>
>> Refer to pages 38 and 39 of the Coco1 Technical Reference ?Manual for the
>> printer settings and connection information (this is more complete than
>> the Coco3 manual pp 313-314)
>> ftp://ftp.maltedmedia.com/coco/MANUALS1/TANDY_HW/COCO/COCO1/CoCo1TM.pdf
>>
>> On Mar 13, 2009, at 5:19 AM, Bill wrote:
>>> Does anyone have an adapter to allow a Coco to print to a "regular"
>>> printer?
>>>
>>> Thanks
>>>
>>> ______________________________________
>>> *Square One Christian BBS
>>> Web access: http://www.sq1bbs.com/index.php
>>> Telnet access: telnet://sq1bbs.com
>>>
>>> A Taste of CoCo Forum
>>> http://www.sq1bbs.com/coco/index.php
>>>
>>> Live chat room - Ventrilo 3.x required
>>> Host name or IP: www.sq1bbs.com
>>> Port: 3784
>>>
>>>
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
A political man can have as his aim the realization of freedom,
but he has no means to realize it other than through violence.
		-- Jean Paul Sartre



From boisy at tee-boy.com  Fri Mar 13 17:25:10 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 13 Mar 2009 16:25:10 -0500
Subject: [Coco] HDB-DOS-Drivewire 3
In-Reply-To: <001e01c9a41f$91925e80$0701a8c0@master>
References: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net><alpine.DEB.2.00.0903122026340.12255@duo><6.2.5.6.2.20090313064141.02ae5a40@cloud9tech.com>
	<AA21ADED-1031-4BA7-9734-EF58130C36FA@tee-boy.com>
	<001e01c9a41f$91925e80$0701a8c0@master>
Message-ID: <DEF3AA5E-EB81-403E-AADE-437FFBC0F5AD@tee-boy.com>

Bob,

That sounds like the functionality we need.

You took a stab at adding some functionality to some utilities in the  
NitrOS-9 project some time back. Do you think you could add this to  
our current megaread?  I would envision a syntax like this:

megaread ###  (where ### is a decimal number of 1K blocks to read)  If  
no option is given, then the default would be 1024 blocks.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com

On Mar 13, 2009, at 4:06 PM, Bob Devries wrote:

> Boisy,
>
> IIRC, there's an OS9 programme called QMEGREAD which is similar to  
> megaread, but reads just a quarter megabyte of data.
> It should be on RTSI.
>
> --
> Regards, Bob Devries, Dalby, Queensland, Australia
>
> Isaiah 50:4 The sovereign Lord has given me
> the capacity to be his spokesman,
> so that I know how to help the weary.
>
> website: http://www.home.gil.com.au/~bdevasl
> my blog: http://bdevries.invigorated.org/
>
> ----- Original Message ----- From: "Boisy Pitre" <boisy at tee-boy.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Friday, March 13, 2009 10:46 PM
> Subject: Re: [Coco] HDB-DOS-Drivewire 3
>
>
>> I just ran a megaread on under NitrOS-9/6309 Level 2 running  
>> DriveWire  3 to an eMac G4 1.42GHz server, and here's what I got:
>>
>> 228 seconds
>>
>> A more recent system could probably do better, but not by a large   
>> margin. Even if you were to cut this in half (114 seconds, which is  
>> a  stretch to think that it could be cut in half) it is still an  
>> order of  magnitude slower than SCSI and way slower than IDE.  A  
>> more comparable  test would be against a floppy system, though  
>> current floppies don't  hold a megabyte.
>>
>> I'm not sure how much slower or faster DriveWire 3 is than a floppy  
>> at raw reads/writes but there is something to be said for NitrOS-9   
>> booting faster from DriveWire 3 than from a floppy disk, and this  
>> has  a lot to do fact that DriveWire 3 is not encumbered by the  
>> time  consuming head movement and track seeks of a floppy disk drive.
>>
>> If someone has the time (hint hint!), they could modify  
>> megaread.asm  in the NitrOS-9 Project to take an optional  
>> parameter: the number of  1K blocks to read (currently 1,024).   
>> This would allow megaread to  work with smaller sized devices and  
>> results could be extrapolated from  that.
>>
>> Regards,
>> Boisy G. Pitre
>> --
>> Tee-Boy
>> Mobile: 337.781.3570
>> Email: boisy at tee-boy.com
>> Web: http://www.tee-boy.com
>>
>> On Mar 13, 2009, at 6:43 AM, Mark Marlette wrote:
>>
>>>
>>> I currently do not have a DW3 setup in place as I am working on   
>>> other Cloud-9 projects.
>>>
>>> Boisy and or, all it takes is megaread and NitrOS-9.
>>>
>>> Regards,
>>>
>>> Mark
>>> Cloud-9
>>>
>>>
>>> At 3/12/2009 07:27 PM, you wrote:
>>>> On Thu, 12 Mar 2009, Mark Marlette wrote:
>>>>
>>>>>
>>>>> Testing I did using MegaRead under NitrOS-9 and SuperDriver......
>>>>>
>>>>> SCSI, ~11 seconds
>>>>> SuperIDE/CF, ~19 seconds.
>>>>>
>>>>> We only know one speed, to the floorboard!
>>>>
>>>> What did the Drivewire drive benchmark as?
>>>>
>>>> --
>>>>
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>>
>>>>
>>>> No virus found in this incoming message.
>>>> Checked by AVG - www.avg.com
>>>> Version: 8.0.237 / Virus Database: 270.11.11/1997 - Release Date:  
>>>> 03/12/09 10:38:00
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From t.fadden at cox.net  Fri Mar 13 18:11:07 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Fri, 13 Mar 2009 15:11:07 -0700
Subject: [Coco] Coco to parallel printer
In-Reply-To: <200903131723.14277.gene.heskett@verizon.net>
References: <011601c9a3d5$e8bd2040$ba3760c0$@rr.com>	<0B545BEC-3006-445C-A52D-3EECAF233C29@ocs.net>	<9efa17da0903130943x14cb3b2n45e1ee3eefcc19f4@mail.gmail.com>
	<200903131723.14277.gene.heskett@verizon.net>
Message-ID: <49BAD9FB.6010808@cox.net>



Well, you got me wondering, so I hooked up my coco3 to my Brother 
HL-1850 laser printer, parallel port, and it works like a champ!  text 
any how.
Will have to see if it will emulate an epson printer, then I can do 
graphics to.  I used to have a laser printer that emulated an epson, and 
it worked with os9, cocomax, max10 etc just dandy.

Tim Fadden


Gene Heskett wrote:
> On Friday 13 March 2009, Sean wrote:
>   
>> I have one available I would be willing to part with.  And it's CoCo
>> specific.
>>
>> http://picasaweb.google.com/lh/photo/thOZYPoFkZnIf2EYFqgWyA?authkey=Gv1sRgCI
>> KYvLL49PucmQE&feat=directlink
>>
>> Make an offer that's reasonable enough to get off the couch, dig
>> through some boxes, and go mail it.  I think I may have the
>> instructions somewhere too.
>>
>> But I think the other issue is finding a printer it would work with.
>> Don't most printers rely on the PC and drivers to do most of the work
>> now?
>>     
>
> Yes, there hasn't been a smart printer made in a decade plus now, and what we 
> do have are all equipt with usb interfaces.
>
> I have a kluge rigged up that did work for a while, and then the printer 
> driver didn't work anymore.  I was feeding the bitbanger, as /p, to an FDTI 
> serial to usb adapter, and then capturing whatever came up the pipe to a file, 
> and when there was no more new data for several seconds, printing it using the 
> normal facilities of this linux box, sending it back over the same cable to a 
> $120 Brother laser printer plugged into another port on the hub so the printer 
> was actually on the coco's desk.  That, when it worked, worked very well 
> indeed as the laser is the fastest printer here by about 2 magnitudes.  The 
> color ink squirters are many times slower.
>
> It's all in a couple of bash scripts.  Ugly, worked a treat.  Anybody wants 
> them, yell.
>
>   
>> On Fri, Mar 13, 2009 at 10:52 AM, Michael Furman <n6il at ocs.net> wrote:
>>     
>>> Bill,
>>>
>>> To connect a Coco to a printer with a 36-pin Centronics Parallel connector
>>> (which is what I assume you meant by a "regular" printer) you need a
>>> serial to parallel printer adapter.  These used to be common but are a lot
>>> harder to find now that everything uses USB.  Pretty much any will do as
>>> long as it supports 600 or 1200 baud and hardware (DTR) flow control.
>>>  Here is an example, you should be able to find something cheaper
>>> elsewhere:
>>>
>>> http://www.pccables.com/30200.htm
>>>
>>>
>>> This one supports 1200 baud which will work:
>>>
>>> http://www.provantage.com/aten-sxp320a~7ATEN02J.htm
>>>
>>> Refer to pages 38 and 39 of the Coco1 Technical Reference  Manual for the
>>> printer settings and connection information (this is more complete than
>>> the Coco3 manual pp 313-314)
>>> ftp://ftp.maltedmedia.com/coco/MANUALS1/TANDY_HW/COCO/COCO1/CoCo1TM.pdf
>>>
>>> On Mar 13, 2009, at 5:19 AM, Bill wrote:
>>>       
>>>> Does anyone have an adapter to allow a Coco to print to a "regular"
>>>> printer?
>>>>
>>>> Thanks
>>>>
>>>> ______________________________________
>>>> *Square One Christian BBS
>>>> Web access: http://www.sq1bbs.com/index.php
>>>> Telnet access: telnet://sq1bbs.com
>>>>
>>>> A Taste of CoCo Forum
>>>> http://www.sq1bbs.com/coco/index.php
>>>>
>>>> Live chat room - Ventrilo 3.x required
>>>> Host name or IP: www.sq1bbs.com
>>>> Port: 3784
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>>         
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>       
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>     
>
>
>   



From devries.bob at gmail.com  Fri Mar 13 18:44:53 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Sat, 14 Mar 2009 08:44:53 +1000
Subject: [Coco] HDB-DOS-Drivewire 3
References: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net><alpine.DEB.2.00.0903122026340.12255@duo><6.2.5.6.2.20090313064141.02ae5a40@cloud9tech.com><AA21ADED-1031-4BA7-9734-EF58130C36FA@tee-boy.com><001e01c9a41f$91925e80$0701a8c0@master>
	<DEF3AA5E-EB81-403E-AADE-437FFBC0F5AD@tee-boy.com>
Message-ID: <004f01c9a42d$55b700b0$0701a8c0@master>

Boisy, I'll look into adding that function to megaread.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Boisy Pitre" <boisy at tee-boy.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Saturday, March 14, 2009 7:25 AM
Subject: Re: [Coco] HDB-DOS-Drivewire 3


> Bob,
> 
> That sounds like the functionality we need.
> 
> You took a stab at adding some functionality to some utilities in the  
> NitrOS-9 project some time back. Do you think you could add this to  
> our current megaread?  I would envision a syntax like this:
> 
> megaread ###  (where ### is a decimal number of 1K blocks to read)  If  
> no option is given, then the default would be 1024 blocks.
> 
> Regards,
> Boisy G. Pitre
> --
> Tee-Boy
> Mobile: 337.781.3570
> Email: boisy at tee-boy.com
> Web: http://www.tee-boy.com
> 
> On Mar 13, 2009, at 4:06 PM, Bob Devries wrote:
> 
>> Boisy,
>>
>> IIRC, there's an OS9 programme called QMEGREAD which is similar to  
>> megaread, but reads just a quarter megabyte of data.
>> It should be on RTSI.
>>
>> --
>> Regards, Bob Devries, Dalby, Queensland, Australia
>>
>> Isaiah 50:4 The sovereign Lord has given me
>> the capacity to be his spokesman,
>> so that I know how to help the weary.
>>
>> website: http://www.home.gil.com.au/~bdevasl
>> my blog: http://bdevries.invigorated.org/
>>
>> ----- Original Message ----- From: "Boisy Pitre" <boisy at tee-boy.com>
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Sent: Friday, March 13, 2009 10:46 PM
>> Subject: Re: [Coco] HDB-DOS-Drivewire 3
>>
>>
>>> I just ran a megaread on under NitrOS-9/6309 Level 2 running  
>>> DriveWire  3 to an eMac G4 1.42GHz server, and here's what I got:
>>>
>>> 228 seconds
>>>
>>> A more recent system could probably do better, but not by a large   
>>> margin. Even if you were to cut this in half (114 seconds, which is  
>>> a  stretch to think that it could be cut in half) it is still an  
>>> order of  magnitude slower than SCSI and way slower than IDE.  A  
>>> more comparable  test would be against a floppy system, though  
>>> current floppies don't  hold a megabyte.
>>>
>>> I'm not sure how much slower or faster DriveWire 3 is than a floppy  
>>> at raw reads/writes but there is something to be said for NitrOS-9   
>>> booting faster from DriveWire 3 than from a floppy disk, and this  
>>> has  a lot to do fact that DriveWire 3 is not encumbered by the  
>>> time  consuming head movement and track seeks of a floppy disk drive.
>>>
>>> If someone has the time (hint hint!), they could modify  
>>> megaread.asm  in the NitrOS-9 Project to take an optional  
>>> parameter: the number of  1K blocks to read (currently 1,024).   
>>> This would allow megaread to  work with smaller sized devices and  
>>> results could be extrapolated from  that.
>>>
>>> Regards,
>>> Boisy G. Pitre
>>> --
>>> Tee-Boy
>>> Mobile: 337.781.3570
>>> Email: boisy at tee-boy.com
>>> Web: http://www.tee-boy.com
>>>
>>> On Mar 13, 2009, at 6:43 AM, Mark Marlette wrote:
>>>
>>>>
>>>> I currently do not have a DW3 setup in place as I am working on   
>>>> other Cloud-9 projects.
>>>>
>>>> Boisy and or, all it takes is megaread and NitrOS-9.
>>>>
>>>> Regards,
>>>>
>>>> Mark
>>>> Cloud-9
>>>>
>>>>
>>>> At 3/12/2009 07:27 PM, you wrote:
>>>>> On Thu, 12 Mar 2009, Mark Marlette wrote:
>>>>>
>>>>>>
>>>>>> Testing I did using MegaRead under NitrOS-9 and SuperDriver......
>>>>>>
>>>>>> SCSI, ~11 seconds
>>>>>> SuperIDE/CF, ~19 seconds.
>>>>>>
>>>>>> We only know one speed, to the floorboard!
>>>>>
>>>>> What did the Drivewire drive benchmark as?
>>>>>
>>>>> --
>>>>>
>>>>> --
>>>>> Coco mailing list
>>>>> Coco at maltedmedia.com
>>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>>>
>>>>>
>>>>> No virus found in this incoming message.
>>>>> Checked by AVG - www.avg.com
>>>>> Version: 8.0.237 / Virus Database: 270.11.11/1997 - Release Date:  
>>>>> 03/12/09 10:38:00
>>>>
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


From t.fadden at cox.net  Fri Mar 13 19:05:38 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Fri, 13 Mar 2009 16:05:38 -0700
Subject: [Coco] Nitros9-6809L2 clock weirdness
Message-ID: <49BAE6C2.4000508@cox.net>

Cheers!

 I started with an existing COCO3 os9L2 hard drive system.  I had been 
using the latest nitros9 clock and clock for a DistoSuperII-4in1.  It 
worked perfectly.

I put the nitros distribution diskett on my hard drive, did a chx to its 
cmds dir, edited the standard.bl file for my hard ware config, adding 
scsisy driverers descripters etc along with the drivewire stuff.

Booted great,  had to change the t2_sc6551.dd to address of FF54 to 
work, one problem solved.

Next I noticed that the clock was not working properly.  never picked up 
the date from the clock chip on the disto. 
I did an ident on the clock and clock2 modules that were loaded, and 
compared it to the modules that had been previously working.  They were 
identical!

Ok, so i copied the clock and clock2 that was working into the nitros 
modules/clock dir, edited the standard.bl file to point to them, created 
a new boot disk and low and behold it worked!  Seems strange to me. I 
thought that if there was any difference whatsoever, the checksum would 
be different at least.  Not the case.

Whats with that?

Tim Fadden


From t.fadden at cox.net  Fri Mar 13 19:24:38 2009
From: t.fadden at cox.net (Tim Fadden)
Date: Fri, 13 Mar 2009 16:24:38 -0700
Subject: [Coco] Nitros9 security breach.
Message-ID: <49BAEB36.3010906@cox.net>

When using the login command with the latest nitros9 release, the 
password is echo'd back to the screen. Is this by design, or an 
oversight?  It's a feature that I am not used to! :-)

Tim Fadden


From exwn8jef at gmail.com  Fri Mar 13 19:38:14 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Fri, 13 Mar 2009 19:38:14 -0400
Subject: [Coco] Latest version of NitrOS-9
In-Reply-To: <49BAEB36.3010906@cox.net>
References: <49BAEB36.3010906@cox.net>
Message-ID: <49BAEE66.1000103@gmail.com>

What is the current version of Nitros9? Is it still 3.02.08 (May 2008)?

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home





From jps.subscriptions at gmail.com  Fri Mar 13 19:44:03 2009
From: jps.subscriptions at gmail.com (J.P. Samson)
Date: Fri, 13 Mar 2009 17:44:03 -0600
Subject: [Coco] Coco to parallel printer
In-Reply-To: <49BAD9FB.6010808@cox.net>
References: <011601c9a3d5$e8bd2040$ba3760c0$@rr.com>	<0B545BEC-3006-445C-A52D-3EECAF233C29@ocs.net>	<9efa17da0903130943x14cb3b2n45e1ee3eefcc19f4@mail.gmail.com>
	<200903131723.14277.gene.heskett@verizon.net>
	<49BAD9FB.6010808@cox.net>
Message-ID: <B4AC6CA5-BA86-41D2-A1AA-5B5FFC599D6D@gmail.com>

On Mar 13, 2009, at 4:11 PM, Tim Fadden wrote:
> Well, you got me wondering, so I hooked up my coco3 to my Brother  
> HL-1850 laser printer, parallel port, and it works like a champ!   
> text any how.
> Will have to see if it will emulate an epson printer, then I can do  
> graphics to.  I used to have a laser printer that emulated an epson,  
> and it worked with os9, cocomax, max10 etc just dandy.

I certainly would be curious to find out.  I have an HL-1870N (step-up  
model from yours) that has a parallel port, and it too claims Epson  
compatibility in the specs.  I bought it many years ago to use for my  
Mac, but even with 144MB of internal memory, it chokes on printing  
documents with graphics (taking an hour per page or erroring out).   
Absolutely useless.  But maybe it'll work great as a CoCo text printer!

-- JP



From devries.bob at gmail.com  Fri Mar 13 19:56:44 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Sat, 14 Mar 2009 09:56:44 +1000
Subject: [Coco] Latest version of NitrOS-9
References: <49BAEB36.3010906@cox.net> <49BAEE66.1000103@gmail.com>
Message-ID: <006c01c9a437$5f691ad0$0701a8c0@master>

Yes, that's the currently available version from sourceforge.

http://sourceforge.net/project/showfiles.php?group_id=174026&package_id=199460&release_id=602149

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "N8WQ" <exwn8jef at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Saturday, March 14, 2009 9:38 AM
Subject: [Coco] Latest version of NitrOS-9


> What is the current version of Nitros9? Is it still 3.02.08 (May 2008)?
>
> Alan Jones
>
> -- 
> N8WQ - Canal Winchester, Ohio
> http://exwn8jef.googlepages.com/home
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From devries.bob at gmail.com  Fri Mar 13 20:23:13 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Sat, 14 Mar 2009 10:23:13 +1000
Subject: [Coco] HDB-DOS-Drivewire 3
References: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net><alpine.DEB.2.00.0903122026340.12255@duo><6.2.5.6.2.20090313064141.02ae5a40@cloud9tech.com><AA21ADED-1031-4BA7-9734-EF58130C36FA@tee-boy.com><001e01c9a41f$91925e80$0701a8c0@master>
	<DEF3AA5E-EB81-403E-AADE-437FFBC0F5AD@tee-boy.com>
Message-ID: <007301c9a43b$12c2ecc0$0701a8c0@master>

Boisy,

Is there a stylesheet for programme modules in NitrOS9? Thinks such as the 
recommended way to accept command line arguments?

I notice that a lot of the modules in the NitrOS9 CVS are disassembled from 
the original (Level 1) modules, which had no such rules.

In various command line based OS's including OS9/68K, the usual method is to 
precede the command line argument with a hyphen (-) and sometimes a letter. 
Is this recommended in NitrOS9?

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Boisy Pitre" <boisy at tee-boy.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Saturday, March 14, 2009 7:25 AM
Subject: Re: [Coco] HDB-DOS-Drivewire 3


> Bob,
>
> That sounds like the functionality we need.
>
> You took a stab at adding some functionality to some utilities in the 
> NitrOS-9 project some time back. Do you think you could add this to  our 
> current megaread?  I would envision a syntax like this:
>
> megaread ###  (where ### is a decimal number of 1K blocks to read)  If  no 
> option is given, then the default would be 1024 blocks.
>
> Regards,
> Boisy G. Pitre
> --
> Tee-Boy
> Mobile: 337.781.3570
> Email: boisy at tee-boy.com
> Web: http://www.tee-boy.com
>
> On Mar 13, 2009, at 4:06 PM, Bob Devries wrote:
>
>> Boisy,
>>
>> IIRC, there's an OS9 programme called QMEGREAD which is similar to 
>> megaread, but reads just a quarter megabyte of data.
>> It should be on RTSI.
>>
>> --
>> Regards, Bob Devries, Dalby, Queensland, Australia
>>
>> Isaiah 50:4 The sovereign Lord has given me
>> the capacity to be his spokesman,
>> so that I know how to help the weary.
>>
>> website: http://www.home.gil.com.au/~bdevasl
>> my blog: http://bdevries.invigorated.org/
>>
>> ----- Original Message ----- From: "Boisy Pitre" <boisy at tee-boy.com>
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Sent: Friday, March 13, 2009 10:46 PM
>> Subject: Re: [Coco] HDB-DOS-Drivewire 3
>>
>>
>>> I just ran a megaread on under NitrOS-9/6309 Level 2 running  DriveWire 
>>> 3 to an eMac G4 1.42GHz server, and here's what I got:
>>>
>>> 228 seconds
>>>
>>> A more recent system could probably do better, but not by a large 
>>> margin. Even if you were to cut this in half (114 seconds, which is  a 
>>> stretch to think that it could be cut in half) it is still an  order of 
>>> magnitude slower than SCSI and way slower than IDE.  A  more comparable 
>>> test would be against a floppy system, though  current floppies don't 
>>> hold a megabyte.
>>>
>>> I'm not sure how much slower or faster DriveWire 3 is than a floppy  at 
>>> raw reads/writes but there is something to be said for NitrOS-9 
>>> booting faster from DriveWire 3 than from a floppy disk, and this  has 
>>> a lot to do fact that DriveWire 3 is not encumbered by the  time 
>>> consuming head movement and track seeks of a floppy disk drive.
>>>
>>> If someone has the time (hint hint!), they could modify  megaread.asm 
>>> in the NitrOS-9 Project to take an optional  parameter: the number of 
>>> 1K blocks to read (currently 1,024).   This would allow megaread to 
>>> work with smaller sized devices and  results could be extrapolated from 
>>> that.
>>>
>>> Regards,
>>> Boisy G. Pitre
>>> --
>>> Tee-Boy
>>> Mobile: 337.781.3570
>>> Email: boisy at tee-boy.com
>>> Web: http://www.tee-boy.com
>>>
>>> On Mar 13, 2009, at 6:43 AM, Mark Marlette wrote:
>>>
>>>>
>>>> I currently do not have a DW3 setup in place as I am working on   other 
>>>> Cloud-9 projects.
>>>>
>>>> Boisy and or, all it takes is megaread and NitrOS-9.
>>>>
>>>> Regards,
>>>>
>>>> Mark
>>>> Cloud-9
>>>>
>>>>
>>>> At 3/12/2009 07:27 PM, you wrote:
>>>>> On Thu, 12 Mar 2009, Mark Marlette wrote:
>>>>>
>>>>>>
>>>>>> Testing I did using MegaRead under NitrOS-9 and SuperDriver......
>>>>>>
>>>>>> SCSI, ~11 seconds
>>>>>> SuperIDE/CF, ~19 seconds.
>>>>>>
>>>>>> We only know one speed, to the floorboard!
>>>>>
>>>>> What did the Drivewire drive benchmark as?
>>>>>
>>>>> --
>>>>>
>>>>> --
>>>>> Coco mailing list
>>>>> Coco at maltedmedia.com
>>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>>>
>>>>>
>>>>> No virus found in this incoming message.
>>>>> Checked by AVG - www.avg.com
>>>>> Version: 8.0.237 / Virus Database: 270.11.11/1997 - Release Date: 
>>>>> 03/12/09 10:38:00
>>>>
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From joef6809 at gmail.com  Fri Mar 13 20:51:33 2009
From: joef6809 at gmail.com (Joe)
Date: Fri, 13 Mar 2009 20:51:33 -0400
Subject: [Coco] Amazing video of a large vintage computer collection
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com><484B91E0-DDEE-4C5D-911B-542A53696878@gmail.com>
	<dbdeb2610903130024h358c1b23ib83f660372c4a43f@mail.gmail.com>
Message-ID: <F3E9C8D8260049E28FBB28BAF96905FB@LT1>

Or you could just go to the webpage and see thats its a silver COCO1.
Its the later Silver with the Logo in the center and no ram bubble. Nothing 
special.
----- Original Message ----- 
From: "Arthur Flexser" <flexser at fiu.edu>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Friday, March 13, 2009 3:24 AM
Subject: Re: [Coco] Amazing video of a large vintage computer collection


I think the CoCo 1 was black plastic, under the silver paint.
When the paint got too scratched up, some folks removed it and voila,
black CoCo 1.

Art

On Fri, Mar 13, 2009 at 2:42 AM, J.P. Samson
<jps.subscriptions at gmail.com> wrote:
> On Mar 13, 2009, at 12:08 AM, Jim Cox wrote:
>>
>> I just came across an amazing video of someone's very large vintage
>> computer
>> collection on YouTube, and posted the video to my blog at:
>>
>> http://8-bit-retro-computing.blogspot.com/
>>
>> The video is 9 and 1/2 minutes long, and feature a CoCo2, and a black
>> CoCo1! There is also a Dragon 64. This guy has systems I have never
>> heard
>> of. Swing by and take a look, and let me know what you think.
>
> He's missing a CoCo 3! I suspect the CoCo 1 is the gunmetal silver 
> version.
> The lighting in the video is quite poor, so the image of the CoCo 1 in the
> corner of the shelf looks dark.
>
> -- JP
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco 



From nutz4coco at gmail.com  Fri Mar 13 21:11:22 2009
From: nutz4coco at gmail.com (Jim Cox)
Date: Fri, 13 Mar 2009 18:11:22 -0700
Subject: [Coco] Amazing video of a large vintage computer collection
In-Reply-To: <F3E9C8D8260049E28FBB28BAF96905FB@LT1>
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com>
	<484B91E0-DDEE-4C5D-911B-542A53696878@gmail.com>
	<dbdeb2610903130024h358c1b23ib83f660372c4a43f@mail.gmail.com>
	<F3E9C8D8260049E28FBB28BAF96905FB@LT1>
Message-ID: <889830d00903131811k7504efb3t9f285d693fa869c5@mail.gmail.com>

Well, I guess it was the trick of the lighting, because it looked black to
me.  By the way, I am always adding links to the blog's link list, so if you
have suggestions feel free to send me your list and I will add them.

PS - It's nice to get back to this list again.  I have been busy with other
stuff, and it looks like I have missed a lot.

Cheers,

Jim Cox
http://miba51.blogspot.com/
http://geekswhocare.blogspot.com/
http://8-bit-retro-computing.blogspot.com/

----- Original Message ----- From: "Arthur Flexser" <flexser at fiu.edu>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Friday, March 13, 2009 3:24 AM
> Subject: Re: [Coco] Amazing video of a large vintage computer collection
>
>
>
> I think the CoCo 1 was black plastic, under the silver paint.
> When the paint got too scratched up, some folks removed it and voila,
> black CoCo 1.
>
> Art
>
> On Fri, Mar 13, 2009 at 2:42 AM, J.P. Samson
> <jps.subscriptions at gmail.com> wrote:
>
>> On Mar 13, 2009, at 12:08 AM, Jim Cox wrote:
>>
>>>
>>> I just came across an amazing video of someone's very large vintage
>>> computer
>>> collection on YouTube, and posted the video to my blog at:
>>>
>>> http://8-bit-retro-computing.blogspot.com/
>>>
>>> The video is 9 and 1/2 minutes long, and feature a CoCo2, and a black
>>> CoCo1! There is also a Dragon 64. This guy has systems I have never
>>> heard
>>> of. Swing by and take a look, and let me know what you think.
>>>
>>
>> He's missing a CoCo 3! I suspect the CoCo 1 is the gunmetal silver
>> version.
>> The lighting in the video is quite poor, so the image of the CoCo 1 in the
>> corner of the shelf looks dark.
>>
>> -- JP
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From boisy at tee-boy.com  Fri Mar 13 22:11:31 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Fri, 13 Mar 2009 21:11:31 -0500
Subject: [Coco] HDB-DOS-Drivewire 3
In-Reply-To: <007301c9a43b$12c2ecc0$0701a8c0@master>
References: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net><alpine.DEB.2.00.0903122026340.12255@duo><6.2.5.6.2.20090313064141.02ae5a40@cloud9tech.com><AA21ADED-1031-4BA7-9734-EF58130C36FA@tee-boy.com><001e01c9a41f$91925e80$0701a8c0@master>
	<DEF3AA5E-EB81-403E-AADE-437FFBC0F5AD@tee-boy.com>
	<007301c9a43b$12c2ecc0$0701a8c0@master>
Message-ID: <1A94F41E-1D6A-4ED0-B070-33D2299F25EC@tee-boy.com>

On Mar 13, 2009, at 7:23 PM, Bob Devries wrote:

> Boisy,
>
> Is there a stylesheet for programme modules in NitrOS9? Thinks such  
> as the recommended way to accept command line arguments?
>
> I notice that a lot of the modules in the NitrOS9 CVS are  
> disassembled from the original (Level 1) modules, which had no such  
> rules.
>
> In various command line based OS's including OS9/68K, the usual  
> method is to precede the command line argument with a hyphen (-) and  
> sometimes a letter. Is this recommended in NitrOS9?

Bob, for commands with multiple arguments, NitrOS-9 adopts the  
OS-9/68K method of preceding options with a dash.  In the case of  
megaread, you can forego this convention since at this point, I  
envision the parameter to be just a number, and because of the  
specific utility of the program.

>
> --
> Regards, Bob Devries, Dalby, Queensland, Australia
>
> Isaiah 50:4 The sovereign Lord has given me
> the capacity to be his spokesman,
> so that I know how to help the weary.
>
> website: http://www.home.gil.com.au/~bdevasl
> my blog: http://bdevries.invigorated.org/
>
> ----- Original Message ----- From: "Boisy Pitre" <boisy at tee-boy.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Saturday, March 14, 2009 7:25 AM
> Subject: Re: [Coco] HDB-DOS-Drivewire 3
>
>
>> Bob,
>>
>> That sounds like the functionality we need.
>>
>> You took a stab at adding some functionality to some utilities in  
>> the NitrOS-9 project some time back. Do you think you could add  
>> this to  our current megaread?  I would envision a syntax like this:
>>
>> megaread ###  (where ### is a decimal number of 1K blocks to read)   
>> If  no option is given, then the default would be 1024 blocks.
>>
>> Regards,
>> Boisy G. Pitre
>> --
>> Tee-Boy
>> Mobile: 337.781.3570
>> Email: boisy at tee-boy.com
>> Web: http://www.tee-boy.com
>>
>> On Mar 13, 2009, at 4:06 PM, Bob Devries wrote:
>>
>>> Boisy,
>>>
>>> IIRC, there's an OS9 programme called QMEGREAD which is similar to  
>>> megaread, but reads just a quarter megabyte of data.
>>> It should be on RTSI.
>>>
>>> --
>>> Regards, Bob Devries, Dalby, Queensland, Australia
>>>
>>> Isaiah 50:4 The sovereign Lord has given me
>>> the capacity to be his spokesman,
>>> so that I know how to help the weary.
>>>
>>> website: http://www.home.gil.com.au/~bdevasl
>>> my blog: http://bdevries.invigorated.org/
>>>
>>> ----- Original Message ----- From: "Boisy Pitre" <boisy at tee-boy.com>
>>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>>> Sent: Friday, March 13, 2009 10:46 PM
>>> Subject: Re: [Coco] HDB-DOS-Drivewire 3
>>>
>>>
>>>> I just ran a megaread on under NitrOS-9/6309 Level 2 running   
>>>> DriveWire 3 to an eMac G4 1.42GHz server, and here's what I got:
>>>>
>>>> 228 seconds
>>>>
>>>> A more recent system could probably do better, but not by a large  
>>>> margin. Even if you were to cut this in half (114 seconds, which  
>>>> is  a stretch to think that it could be cut in half) it is still  
>>>> an  order of magnitude slower than SCSI and way slower than IDE.   
>>>> A  more comparable test would be against a floppy system, though   
>>>> current floppies don't hold a megabyte.
>>>>
>>>> I'm not sure how much slower or faster DriveWire 3 is than a  
>>>> floppy  at raw reads/writes but there is something to be said for  
>>>> NitrOS-9 booting faster from DriveWire 3 than from a floppy disk,  
>>>> and this  has a lot to do fact that DriveWire 3 is not encumbered  
>>>> by the  time consuming head movement and track seeks of a floppy  
>>>> disk drive.
>>>>
>>>> If someone has the time (hint hint!), they could modify   
>>>> megaread.asm in the NitrOS-9 Project to take an optional   
>>>> parameter: the number of 1K blocks to read (currently 1,024).    
>>>> This would allow megaread to work with smaller sized devices and   
>>>> results could be extrapolated from that.
>>>>
>>>> Regards,
>>>> Boisy G. Pitre
>>>> --
>>>> Tee-Boy
>>>> Mobile: 337.781.3570
>>>> Email: boisy at tee-boy.com
>>>> Web: http://www.tee-boy.com
>>>>
>>>> On Mar 13, 2009, at 6:43 AM, Mark Marlette wrote:
>>>>
>>>>>
>>>>> I currently do not have a DW3 setup in place as I am working  
>>>>> on   other Cloud-9 projects.
>>>>>
>>>>> Boisy and or, all it takes is megaread and NitrOS-9.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Mark
>>>>> Cloud-9
>>>>>
>>>>>
>>>>> At 3/12/2009 07:27 PM, you wrote:
>>>>>> On Thu, 12 Mar 2009, Mark Marlette wrote:
>>>>>>
>>>>>>>
>>>>>>> Testing I did using MegaRead under NitrOS-9 and  
>>>>>>> SuperDriver......
>>>>>>>
>>>>>>> SCSI, ~11 seconds
>>>>>>> SuperIDE/CF, ~19 seconds.
>>>>>>>
>>>>>>> We only know one speed, to the floorboard!
>>>>>>
>>>>>> What did the Drivewire drive benchmark as?
>>>>>>
>>>>>> --
>>>>>>
>>>>>> --
>>>>>> Coco mailing list
>>>>>> Coco at maltedmedia.com
>>>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>>>>
>>>>>>
>>>>>> No virus found in this incoming message.
>>>>>> Checked by AVG - www.avg.com
>>>>>> Version: 8.0.237 / Virus Database: 270.11.11/1997 - Release  
>>>>>> Date: 03/12/09 10:38:00
>>>>>
>>>>> --
>>>>> Coco mailing list
>>>>> Coco at maltedmedia.com
>>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>>
>>>>
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



From devries.bob at gmail.com  Fri Mar 13 23:33:09 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Sat, 14 Mar 2009 13:33:09 +1000
Subject: [Coco] reading the command line in assembler
Message-ID: <009d01c9a455$cfed2350$0701a8c0@master>

hi all,

No, I don't need to know *how* to read the command line; I already know that 
:)

When a command in NitrOS9 executes, X points to the command line, which is 
terminated in a carriage return. I'd like to know if the memory after the 
last character can be assumed to be $00?

In C, the number of command line arguments and the array of arguments are 
nicely packaged. Not so in assembler, I fear.

If this information is in the manual, will some kind soul point me to the 
page?

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/



From gene.heskett at verizon.net  Sat Mar 14 00:08:38 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sat, 14 Mar 2009 00:08:38 -0400
Subject: [Coco] Amazing video of a large vintage computer collection
In-Reply-To: <F3E9C8D8260049E28FBB28BAF96905FB@LT1>
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com>
	<dbdeb2610903130024h358c1b23ib83f660372c4a43f@mail.gmail.com>
	<F3E9C8D8260049E28FBB28BAF96905FB@LT1>
Message-ID: <200903140008.38273.gene.heskett@verizon.net>

On Friday 13 March 2009, Joe wrote:
>Or you could just go to the webpage and see thats its a silver COCO1.
>Its the later Silver with the Logo in the center and no ram bubble. Nothing
>special.
>----- Original Message -----
>From: "Arthur Flexser" <flexser at fiu.edu>
>To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>Sent: Friday, March 13, 2009 3:24 AM
>Subject: Re: [Coco] Amazing video of a large vintage computer collection
>
>
>I think the CoCo 1 was black plastic, under the silver paint.
>When the paint got too scratched up, some folks removed it and voila,
>black CoCo 1.
>
>Art

I have 2 of those Art, and the paint has long since worn off from in front of 
the keyboard, and its hardly noticeable as the plastic under that silver paint 
is a quite well matched gray.  I don't recall ever seeing a black one.  Taint 
saying there aren't any, just that I haven't seen a black one.

>On Fri, Mar 13, 2009 at 2:42 AM, J.P. Samson
>
><jps.subscriptions at gmail.com> wrote:
>> On Mar 13, 2009, at 12:08 AM, Jim Cox wrote:
>>> I just came across an amazing video of someone's very large vintage
>>> computer
>>> collection on YouTube, and posted the video to my blog at:
>>>
>>> http://8-bit-retro-computing.blogspot.com/
>>>
>>> The video is 9 and 1/2 minutes long, and feature a CoCo2, and a black
>>> CoCo1! There is also a Dragon 64. This guy has systems I have never
>>> heard
>>> of. Swing by and take a look, and let me know what you think.
>>
>> He's missing a CoCo 3! I suspect the CoCo 1 is the gunmetal silver
>> version.
>> The lighting in the video is quite poor, so the image of the CoCo 1 in the
>> corner of the shelf looks dark.
>>
>> -- JP
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Creativity is no substitute for knowing what you are doing.



From gene.heskett at verizon.net  Sat Mar 14 00:12:29 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sat, 14 Mar 2009 00:12:29 -0400
Subject: [Coco] reading the command line in assembler
In-Reply-To: <009d01c9a455$cfed2350$0701a8c0@master>
References: <009d01c9a455$cfed2350$0701a8c0@master>
Message-ID: <200903140012.30037.gene.heskett@verizon.net>

On Friday 13 March 2009, Bob Devries wrote:
>hi all,
>
>No, I don't need to know *how* to read the command line; I already know that
>
>:)
>
>When a command in NitrOS9 executes, X points to the command line, which is
>terminated in a carriage return. I'd like to know if the memory after the
>last character can be assumed to be $00?
>
I don't believe so.  A proper program, presumes it is done with the command 
parsing when it finds the $0D.  There could be anything beyond that.

>In C, the number of command line arguments and the array of arguments are
>nicely packaged. Not so in assembler, I fear.
>
>If this information is in the manual, will some kind soul point me to the
>page?
>
>--
>Regards, Bob Devries, Dalby, Queensland, Australia
>
>Isaiah 50:4 The sovereign Lord has given me
>the capacity to be his spokesman,
>so that I know how to help the weary.
>
>website: http://www.home.gil.com.au/~bdevasl
>my blog: http://bdevries.invigorated.org/
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The solution of this problem is trivial and is left as an exercise for
the reader.



From flexser at fiu.edu  Sat Mar 14 01:01:27 2009
From: flexser at fiu.edu (Arthur Flexser)
Date: Sat, 14 Mar 2009 01:01:27 -0400
Subject: [Coco] Amazing video of a large vintage computer collection
In-Reply-To: <200903140008.38273.gene.heskett@verizon.net>
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com>
	<dbdeb2610903130024h358c1b23ib83f660372c4a43f@mail.gmail.com>
	<F3E9C8D8260049E28FBB28BAF96905FB@LT1>
	<200903140008.38273.gene.heskett@verizon.net>
Message-ID: <dbdeb2610903132201s6cf6c1edx371b2d2adf8a2041@mail.gmail.com>

Thanks, Gene.  I was most likely mistaken.  Possibly, I was thinking
of a CoCo where someone had painted it black after removing the
original paint.

Art

On Sat, Mar 14, 2009 at 12:08 AM, Gene Heskett <gene.heskett at verizon.net> wrote:
> On Friday 13 March 2009, Joe wrote:
>>Or you could just go to the webpage and see thats its a silver COCO1.
>>Its the later Silver with the Logo in the center and no ram bubble. Nothing
>>special.
>>----- Original Message -----
>>From: "Arthur Flexser" <flexser at fiu.edu>
>>To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>>Sent: Friday, March 13, 2009 3:24 AM
>>Subject: Re: [Coco] Amazing video of a large vintage computer collection
>>
>>
>>I think the CoCo 1 was black plastic, under the silver paint.
>>When the paint got too scratched up, some folks removed it and voila,
>>black CoCo 1.
>>
>>Art
>
> I have 2 of those Art, and the paint has long since worn off from in front of
> the keyboard, and its hardly noticeable as the plastic under that silver paint
> is a quite well matched gray. ?I don't recall ever seeing a black one. ?Taint
> saying there aren't any, just that I haven't seen a black one.
>
>>On Fri, Mar 13, 2009 at 2:42 AM, J.P. Samson
>>
>><jps.subscriptions at gmail.com> wrote:
>>> On Mar 13, 2009, at 12:08 AM, Jim Cox wrote:
>>>> I just came across an amazing video of someone's very large vintage
>>>> computer
>>>> collection on YouTube, and posted the video to my blog at:
>>>>
>>>> http://8-bit-retro-computing.blogspot.com/
>>>>
>>>> The video is 9 and 1/2 minutes long, and feature a CoCo2, and a black
>>>> CoCo1! There is also a Dragon 64. This guy has systems I have never
>>>> heard
>>>> of. Swing by and take a look, and let me know what you think.
>>>
>>> He's missing a CoCo 3! I suspect the CoCo 1 is the gunmetal silver
>>> version.
>>> The lighting in the video is quite poor, so the image of the CoCo 1 in the
>>> corner of the shelf looks dark.
>>>
>>> -- JP
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>--
>>Coco mailing list
>>Coco at maltedmedia.com
>>http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>>--
>>Coco mailing list
>>Coco at maltedmedia.com
>>http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Cheers, Gene
> "There are four boxes to be used in defense of liberty:
> ?soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Creativity is no substitute for knowing what you are doing.
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>


From gene.heskett at verizon.net  Sat Mar 14 01:07:50 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sat, 14 Mar 2009 01:07:50 -0400
Subject: [Coco] Amazing video of a large vintage computer collection
In-Reply-To: <dbdeb2610903132201s6cf6c1edx371b2d2adf8a2041@mail.gmail.com>
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com>
	<200903140008.38273.gene.heskett@verizon.net>
	<dbdeb2610903132201s6cf6c1edx371b2d2adf8a2041@mail.gmail.com>
Message-ID: <200903140107.50129.gene.heskett@verizon.net>

On Saturday 14 March 2009, Arthur Flexser wrote:
>Thanks, Gene.  I was most likely mistaken.  Possibly, I was thinking
>of a CoCo where someone had painted it black after removing the
>original paint.
>
>Art
>
That is always a possibility.  It seems that for the last 15 years, one can 
have his electronics in any color, as long as its black...  Then you have to 
get out a 200 watt lamp just to be able to read the raised printing around the 
darned jacks to make sure you plug it in right.  I don't know how others feel, 
but that scene to me is a PIMA.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Denver, n.:
	A smallish city located just below the `O' in Colorado.



From devries.bob at gmail.com  Sat Mar 14 01:29:46 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Sat, 14 Mar 2009 15:29:46 +1000
Subject: [Coco] Amazing video of a large vintage computer collection
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com><200903140008.38273.gene.heskett@verizon.net><dbdeb2610903132201s6cf6c1edx371b2d2adf8a2041@mail.gmail.com>
	<200903140107.50129.gene.heskett@verizon.net>
Message-ID: <00ac01c9a465$e5d7ff40$0701a8c0@master>

Gene,
you're right of course, but I need that same 200 watter to read chip numbers 
too nowadays. SIGH.

The joys of getting older.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Gene Heskett" <gene.heskett at verizon.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Saturday, March 14, 2009 3:07 PM
Subject: Re: [Coco] Amazing video of a large vintage computer collection


> On Saturday 14 March 2009, Arthur Flexser wrote:
>>Thanks, Gene.  I was most likely mistaken.  Possibly, I was thinking
>>of a CoCo where someone had painted it black after removing the
>>original paint.
>>
>>Art
>>
> That is always a possibility.  It seems that for the last 15 years, one 
> can
> have his electronics in any color, as long as its black...  Then you have 
> to
> get out a 200 watt lamp just to be able to read the raised printing around 
> the
> darned jacks to make sure you plug it in right.  I don't know how others 
> feel,
> but that scene to me is a PIMA.
>
> -- 
> Cheers, Gene
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Denver, n.:
> A smallish city located just below the `O' in Colorado.
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From devries.bob at gmail.com  Sat Mar 14 01:41:26 2009
From: devries.bob at gmail.com (Bob Devries)
Date: Sat, 14 Mar 2009 15:41:26 +1000
Subject: [Coco] HDB-DOS-Drivewire 3
References: <1264551044.211241236895403434.JavaMail.root@cl04-host03.roch.ny.frontiernet.net><alpine.DEB.2.00.0903122026340.12255@duo><6.2.5.6.2.20090313064141.02ae5a40@cloud9tech.com><AA21ADED-1031-4BA7-9734-EF58130C36FA@tee-boy.com><001e01c9a41f$91925e80$0701a8c0@master>
	<DEF3AA5E-EB81-403E-AADE-437FFBC0F5AD@tee-boy.com>
Message-ID: <00ba01c9a467$86f21a90$0701a8c0@master>

OK,

I've written/hacked megaread to take a command line argument.

The command line is now:

megaread #####

where the ##### is the number of 1K blocks of data to read from STDIN. If no 
number is supplied, 1024 is used, giving 1 megabyte. As before, the device 
to be read from must be redirected into megaread; viz:

megaread 256 </dd@

I've emailed my source code to Boisy, and if he approves, he'll likely store 
it in the appropriate place in the NitrOS9 repository on sourceforge.

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "Boisy Pitre" <boisy at tee-boy.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Saturday, March 14, 2009 7:25 AM
Subject: Re: [Coco] HDB-DOS-Drivewire 3


> Bob,
>
> That sounds like the functionality we need.
>
> You took a stab at adding some functionality to some utilities in the 
> NitrOS-9 project some time back. Do you think you could add this to  our 
> current megaread?  I would envision a syntax like this:
>
> megaread ###  (where ### is a decimal number of 1K blocks to read)  If  no 
> option is given, then the default would be 1024 blocks.
>
> Regards,
> Boisy G. Pitre
> --
> Tee-Boy
> Mobile: 337.781.3570
> Email: boisy at tee-boy.com
> Web: http://www.tee-boy.com
>
> On Mar 13, 2009, at 4:06 PM, Bob Devries wrote:
>
>> Boisy,
>>
>> IIRC, there's an OS9 programme called QMEGREAD which is similar to 
>> megaread, but reads just a quarter megabyte of data.
>> It should be on RTSI.
>>
>> --
>> Regards, Bob Devries, Dalby, Queensland, Australia
>>
>> Isaiah 50:4 The sovereign Lord has given me
>> the capacity to be his spokesman,
>> so that I know how to help the weary.
>>
>> website: http://www.home.gil.com.au/~bdevasl
>> my blog: http://bdevries.invigorated.org/
>>
>> ----- Original Message ----- From: "Boisy Pitre" <boisy at tee-boy.com>
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Sent: Friday, March 13, 2009 10:46 PM
>> Subject: Re: [Coco] HDB-DOS-Drivewire 3
>>
>>
>>> I just ran a megaread on under NitrOS-9/6309 Level 2 running  DriveWire 
>>> 3 to an eMac G4 1.42GHz server, and here's what I got:
>>>
>>> 228 seconds
>>>
>>> A more recent system could probably do better, but not by a large 
>>> margin. Even if you were to cut this in half (114 seconds, which is  a 
>>> stretch to think that it could be cut in half) it is still an  order of 
>>> magnitude slower than SCSI and way slower than IDE.  A  more comparable 
>>> test would be against a floppy system, though  current floppies don't 
>>> hold a megabyte.
>>>
>>> I'm not sure how much slower or faster DriveWire 3 is than a floppy  at 
>>> raw reads/writes but there is something to be said for NitrOS-9 
>>> booting faster from DriveWire 3 than from a floppy disk, and this  has 
>>> a lot to do fact that DriveWire 3 is not encumbered by the  time 
>>> consuming head movement and track seeks of a floppy disk drive.
>>>
>>> If someone has the time (hint hint!), they could modify  megaread.asm 
>>> in the NitrOS-9 Project to take an optional  parameter: the number of 
>>> 1K blocks to read (currently 1,024).   This would allow megaread to 
>>> work with smaller sized devices and  results could be extrapolated from 
>>> that.
>>>
>>> Regards,
>>> Boisy G. Pitre
>>> --
>>> Tee-Boy
>>> Mobile: 337.781.3570
>>> Email: boisy at tee-boy.com
>>> Web: http://www.tee-boy.com
>>>
>>> On Mar 13, 2009, at 6:43 AM, Mark Marlette wrote:
>>>
>>>>
>>>> I currently do not have a DW3 setup in place as I am working on   other 
>>>> Cloud-9 projects.
>>>>
>>>> Boisy and or, all it takes is megaread and NitrOS-9.
>>>>
>>>> Regards,
>>>>
>>>> Mark
>>>> Cloud-9
>>>>
>>>>
>>>> At 3/12/2009 07:27 PM, you wrote:
>>>>> On Thu, 12 Mar 2009, Mark Marlette wrote:
>>>>>
>>>>>>
>>>>>> Testing I did using MegaRead under NitrOS-9 and SuperDriver......
>>>>>>
>>>>>> SCSI, ~11 seconds
>>>>>> SuperIDE/CF, ~19 seconds.
>>>>>>
>>>>>> We only know one speed, to the floorboard!
>>>>>
>>>>> What did the Drivewire drive benchmark as?
>>>>>
>>>>> --
>>>>>
>>>>> --
>>>>> Coco mailing list
>>>>> Coco at maltedmedia.com
>>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>>>
>>>>>
>>>>> No virus found in this incoming message.
>>>>> Checked by AVG - www.avg.com
>>>>> Version: 8.0.237 / Virus Database: 270.11.11/1997 - Release Date: 
>>>>> 03/12/09 10:38:00
>>>>
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 



From coder32768 at gmail.com  Sat Mar 14 02:46:54 2009
From: coder32768 at gmail.com (Rick Taylor)
Date: Fri, 13 Mar 2009 23:46:54 -0700
Subject: [Coco] Do you recognize PI Day
In-Reply-To: <91EF1B1C-2F20-481F-8345-2F6D004032B1@ocs.net>
References: <49B73479.10906@sbcglobal.net>
	<91EF1B1C-2F20-481F-8345-2F6D004032B1@ocs.net>
Message-ID: <fc509d260903132346o1656fd30mc94833349edbde6f@mail.gmail.com>

Hey! I'm in Alameda!

On Wed, Mar 11, 2009 at 8:50 AM, Michael Furman <n6il at ocs.net> wrote:

> I am going to two different SFBay events on PI Day:
>
> - Electronics Flea Market @De Anza College
> http://www.electronicsfleamarket.com/
>
> - Super Happy Dev House #31 http://superhappydevhouse.org/ - I should
> start bringing a Coco to this event :)
>
>
> On Mar 10, 2009, at 8:48 PM, Brian Goers wrote:
>
>  Since this Saturday is One of the PI days, does anyone on the list here
>> have a party/celebrate around 2:00 pm in the afternoon to acknowledge this
>> important number.
>> Why this date and time? Because PI=3.14159. That's 3-14 at 1:59 pm.
>> I am going to have a cake with the numbers on the circumference. ;-)
>> Later
>> Brian
>>
>> --
>> Brian Goers                                         Glenside Color
>> Computer Club URL
>> Glenside Vice-President of Special Events
>> http://GlensideCCC.com
>> IDE Boards are available.
>> Show cost $45.00                                   The 18th Annual ?LAST?
>> Chicago CoCoFEST!
>> Includes items in the picture                      Will be held March 28 &
>> 29 2009
>>                                                  Holiday Inn & Suites
>> Elgin.
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
All of this machinery making modern music can still be open hearted -
not so coldly charted; it's really just a question of your honesty.

- Neil Peart, Rush, _The Spirit of Radio_


From stinger30au at yahoo.com.au  Sat Mar 14 08:00:52 2009
From: stinger30au at yahoo.com.au (stinger30au)
Date: Sat, 14 Mar 2009 12:00:52 -0000
Subject: [Coco] [Color Computer] Buzzard Bait by Rugby Circle sold by Tom Mix
Message-ID: <gpg69k+g8pu@eGroups.com>

Who was Rugby Circle???
Was it one or more programmers or what???

Any ideas?



From brucewcalkins at charter.net  Sat Mar 14 08:19:12 2009
From: brucewcalkins at charter.net (Bruce W. Calkins)
Date: Sat, 14 Mar 2009 08:19:12 -0400
Subject: [Coco] Amazing video of a large vintage computer collection
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com><200903140008.38273.gene.heskett@verizon.net><dbdeb2610903132201s6cf6c1edx371b2d2adf8a2041@mail.gmail.com><200903140107.50129.gene.heskett@verizon.net>
	<00ac01c9a465$e5d7ff40$0701a8c0@master>
Message-ID: <C760DA72FDA9423D9F9B5E4A437D4C98@speedy>

> Gene,
> you're right of course, but I need that same 200 watter to read chip 
> numbers too nowadays. SIGH.
>
> The joys of getting older.
>
> --
> Regards, Bob Devries,



It still beats the alternative all hollow.


Bruce W. 



From gene.heskett at verizon.net  Sat Mar 14 09:47:31 2009
From: gene.heskett at verizon.net (Gene Heskett)
Date: Sat, 14 Mar 2009 09:47:31 -0400
Subject: [Coco] Amazing video of a large vintage computer collection
In-Reply-To: <00ac01c9a465$e5d7ff40$0701a8c0@master>
References: <889830d00903122308k3c0d5416o705dca68c58541f3@mail.gmail.com>
	<200903140107.50129.gene.heskett@verizon.net>
	<00ac01c9a465$e5d7ff40$0701a8c0@master>
Message-ID: <200903140947.31878.gene.heskett@verizon.net>

On Saturday 14 March 2009, Bob Devries wrote:
>Gene,
>you're right of course, but I need that same 200 watter to read chip numbers
>too nowadays. SIGH.
>
>The joys of getting older.
>
Yeah, and don't forget the magnifying lens too, I find an old projector lens 
with about a 10mm focal length a great help.  Gets right up close and personal 
with those microscopic bits of swarf that get into your fingers around a 
milling machine too.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Police are examining all internet packets in the search for a narco-net-
trafficker



From boisy at tee-boy.com  Sat Mar 14 10:59:11 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Sat, 14 Mar 2009 09:59:11 -0500
Subject: [Coco] NitrOS-9 Project Changes
Message-ID: <D3A18695-57B7-4832-AFB6-C1A756A6F543@tee-boy.com>

Starting tomorrow, the NitrOS-9 Project will have available from its  
main web page at http://www.nitros9.org, nightly builds of ALL of the  
disk images in the project.  Below is a list of all of the various  
disk images that will be available in the ZIP file.

Nightly builds will give us a quick turn around cycle for getting bug  
fixes and enhancements out to everyone.

The current stable release, 3.2.8 will still be available for download.


DISK IMAGE MANIFEST

MICROWARE C COMPILER
cc.dsk

FLIGHT SIMULATOR II
fsim2.dsk

KYUM_GAI: TO BE NINJA
kyumgai.dsk

MULTI-VUE
multivue_6309.dsk
multivue_6809.dsk

MICROSCOPIC MISSION
mm.dsk

KORONIS RIFT
koronis.dsk

SIERRA GAMES
blackcauldron_80d.dsk
blackcauldron_d1_40d.dsk
blackcauldron_d2_40d.dsk
christmas86.dsk
kingquest3_80d.dsk
kingquest3_d1_40d.dsk
kingquest3_d2_40d.dsk
kingquest3_d3_40d.dsk
kingsquest1_40d.dsk
kingsquest2_80d.dsk
kingsquest2_d1_40d.dsk
kingsquest2_d2_40d.dsk
leisuresuitlarry.dsk
spacequest0_d1_40d.dsk
spacequest0_d1_80d.dsk
spacequest0_d2_40d.dsk
spacequest0_d2_80d.dsk
spacequest1_80d.dsk
spacequest1_d1_40d.dsk
spacequest1_d2_40d.dsk
spacequest2_80d.dsk
spacequest2_d1_40d.dsk
spacequest2_d2_40d.dsk
spacequest2_d3_40d.dsk

NITROS-9/6309 LEVEL 2
nos96309l2v030209coco3_40d_1.dsk
nos96309l2v030209coco3_40d_1_50hz.dsk
nos96309l2v030209coco3_40d_2.dsk
nos96309l2v030209coco3_80d.dsk
nos96309l2v030209coco3_80d_50hz.dsk
nos96309l2v030209coco3_dw3.dsk

NITROS-9/6809 LEVEL 1
nos96809l1v030209coco1_dw3.dsk
nos96809l1v030209coco2_dw3.dsk
nos96809l1v030209coco_40d_1.dsk
nos96809l1v030209coco_40d_2.dsk
nos96809l1v030209coco_80d.dsk
nos96809l1v030209d64_40d_1.dsk
nos96809l1v030209d64_40d_2.dsk
nos96809l1v030209d64_40s_1.dsk
nos96809l1v030209d64_40s_2.dsk
nos96809l1v030209d64_80d.dsk
nos96809l1v030209dalpha_80d.dsk
nos96809l1v030209dalpha_80s_1.dsk
nos96809l1v030209dalpha_80s_2.dsk
nos96809l1v030209tano_40d_1.dsk
nos96809l1v030209tano_40d_2.dsk
nos96809l1v030209tano_80d.dsk

NITROS-9/6809 LEVEL 2
nos96809l2v030209coco3_40d_1.dsk
nos96809l2v030209coco3_40d_1_50hz.dsk
nos96809l2v030209coco3_40d_2.dsk
nos96809l2v030209coco3_80d.dsk
nos96809l2v030209coco3_80d_50hz.dsk
nos96809l2v030209coco3_dw3.dsk

RESCUE ON FRACTALUS
rof.dsk

SUB BATTLE SIMULATOR
subsim.dsk

UUCPBB 2.1
uucpbb21_6309.dsk
uucpbb21_6809.dsk


Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From boisy at tee-boy.com  Sat Mar 14 12:34:25 2009
From: boisy at tee-boy.com (Boisy Pitre)
Date: Sat, 14 Mar 2009 11:34:25 -0500
Subject: [Coco] DriveWire MacServer now on SourceForge
Message-ID: <EADDD42E-2DFA-47AD-BBAD-55F459A2DE00@tee-boy.com>

This morning I posted the source to DriveWire MacServer up on  
SourceForge.  The project page is at https://sourceforge.net/projects/drivewireserver/ 
.  Now all three major platforms (Mac, Windows and Linux) have  
DriveWire servers there.

Have fun.

Regards,
Boisy G. Pitre
--
Tee-Boy
Mobile: 337.781.3570
Email: boisy at tee-boy.com
Web: http://www.tee-boy.com



From jps.subscriptions at gmail.com  Sat Mar 14 14:28:58 2009
From: jps.subscriptions at gmail.com (J.P. Samson)
Date: Sat, 14 Mar 2009 12:28:58 -0600
Subject: [Coco] [Color Computer] Buzzard Bait by Rugby Circle sold by
	Tom Mix
In-Reply-To: <gpg69k+g8pu@eGroups.com>
References: <gpg69k+g8pu@eGroups.com>
Message-ID: <74837F12-A407-428A-A9F0-BD6003D63644@gmail.com>

On Mar 14, 2009, at 6:00 AM, stinger30au wrote:
> Who was Rugby Circle???
> Was it one or more programmers or what???
>
> Any ideas?

It was more than one person.  One of those programmers was Rob Lech.   
Curtis Boyle may know more.

http://nitros9.lcurtisboyle.com/approvals/the_rugby_circle.txt

-- JP



From georgeramsower at gmail.com  Sat Mar 14 17:32:02 2009
From: georgeramsower at gmail.com (George Ramsower)
Date: Sat, 14 Mar 2009 15:32:02 -0600
Subject: [Coco]  MESS
Message-ID: <002a01c9a4ec$510a33b0$6401a8c0@OLDGEORGE>

 I've tried MESS on my computer and can't seem to get it working correctly.
 I have a 1GHZ Celeron computer, running XP SP2
 So, I went to MESS.ORG and I see that I have a choice of mess0130B for 
Windows and mess0130B i686 OPTIMIZED.
 Is one better suited for my system? or would the one for <all platforms> be 
better?

 Thanks

 George 



From cyberpunk at prtc.net  Sat Mar 14 16:52:03 2009
From: cyberpunk at prtc.net (RJLCyberPunk)
Date: Sat, 14 Mar 2009 16:52:03 -0400
Subject: [Coco] MESS
References: <002a01c9a4ec$510a33b0$6401a8c0@OLDGEORGE>
Message-ID: <8B1FA58FFB2B4619AE62F4F7CA1FABC9@FANTASYWARE>

Hmm.. First I hear of this when I downloaded MESS I dowloaded the lattest 
version they had which is 0128 so far. You will probably still need to get 
the roms separately and they are provided in CoCo3.net but I do recall the 
URL for it.



----- Original Message ----- 
From: "George Ramsower" <georgeramsower at gmail.com>
To: "Cocolist" <coco at maltedmedia.com>
Sent: Saturday, March 14, 2009 5:32 PM
Subject: [Coco] MESS


> I've tried MESS on my computer and can't seem to get it working correctly.
> I have a 1GHZ Celeron computer, running XP SP2
> So, I went to MESS.ORG and I see that I have a choice of mess0130B for 
> Windows and mess0130B i686 OPTIMIZED.
> Is one better suited for my system? or would the one for <all platforms> 
> be better?
>
> Thanks
>
> George
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> 



From robert.gault at worldnet.att.net  Sat Mar 14 17:11:51 2009
From: robert.gault at worldnet.att.net (Robert Gault)
Date: Sat, 14 Mar 2009 17:11:51 -0400
Subject: [Coco] MESS
In-Reply-To: <002a01c9a4ec$510a33b0$6401a8c0@OLDGEORGE>
References: <002a01c9a4ec$510a33b0$6401a8c0@OLDGEORGE>
Message-ID: <49BC1D97.5010207@worldnet.att.net>

George Ramsower wrote:
> I've tried MESS on my computer and can't seem to get it working correctly.
> I have a 1GHZ Celeron computer, running XP SP2
> So, I went to MESS.ORG and I see that I have a choice of mess0130B for 
> Windows and mess0130B i686 OPTIMIZED.
> Is one better suited for my system? or would the one for <all platforms> 
> be better?
> 
> Thanks
> 
> George
> 

Start with the MESS 0130b.zip file. If it works for you, and it should, 
you can see if the i686 version is any better.


From georgeramsower at gmail.com  Sat Mar 14 18:22:02 2009
From: georgeramsower at gmail.com (George Ramsower)
Date: Sat, 14 Mar 2009 16:22:02 -0600
Subject: [Coco] MESS
References: <002a01c9a4ec$510a33b0$6401a8c0@OLDGEORGE>
	<49BC1D97.5010207@worldnet.att.net>
Message-ID: <003501c9a4f3$4d425210$6401a8c0@OLDGEORGE>


----- Original Message ----- 
From: "Robert Gault"

> George Ramsower wrote:
>> I've tried MESS on my computer and can't seem to get it working 
>> correctly.
>> I have a 1GHZ Celeron computer, running XP SP2
>> So, I went to MESS.ORG and I see that I have a choice of mess0130B for 
>> Windows and mess0130B i686 OPTIMIZED.
>> Is one better suited for my system? or would the one for <all platforms> 
>> be better?
>>
>> Thanks
>>
>> George
>>
>
> Start with the MESS 0130b.zip file. If it works for you, and it should, 
> you can see if the i686 version is any better.

Where do I put the ROM image for this/ 



From exwn8jef at gmail.com  Sat Mar 14 17:35:01 2009
From: exwn8jef at gmail.com (N8WQ)
Date: Sat, 14 Mar 2009 17:35:01 -0400
Subject: [Coco] MESS
In-Reply-To: <003501c9a4f3$4d425210$6401a8c0@OLDGEORGE>
References: <002a01c9a4ec$510a33b0$6401a8c0@OLDGEORGE>	<49BC1D97.5010207@worldnet.att.net>
	<003501c9a4f3$4d425210$6401a8c0@OLDGEORGE>
Message-ID: <49BC2305.7040809@gmail.com>

put in "bios" subdirectory
mess0130B/bios

Alan Jones

-- 
N8WQ - Canal Winchester, Ohio
http://exwn8jef.googlepages.com/home



G