[Coco] Serial Port file transfers

[Gene Heskett]

On Friday 10 November 2006 16:32, Jim Hickle wrote:

>"L. Curtis Boyle" <curtisboyle at sasktel.net> wrote: On Mon, 06 Nov 2006

> 00:30:52 -0600, Gene Heskett

>

> wrote:

>> On Sunday 05 November 2006 23:03, Jim Hickle wrote:

>>> What sort of speeds should I be expecting from a 512k CoCo running

>>> NitrOS9, with an RS-232 pack connected to a Linux system's serial

>>> port? I'm trying to transfer files and it's taking forever using

>>> floppies and the PCDos program.

>>

>> Years ago now, I was using an amiga-2000-040 and Olaf Barthels term4.7

>> to measure that.  I was getting around 740 cps with the interfaces set

>> for 9600 on a nitros9-1.15 system, and about 430 cps with a stock 512k

>> coco3. This was using the auto-trigger of rz/sz-3.36 with supercom-2.3

>> for the term program on the coco3's.  Using the 7-wire protocol for

>> flow control, not xon/xoff.

>

>     This was using Nitros9 as originally intended on a 6309 chip... I

>don't know if Jim is using a 6809 or 6309 chip in his scenario. I know I

>used to get about 700-800 CPS with a 9600 connection with RZ/SZ (which

>really needs a rewrite to use proper buffering to speed it up), and with

> a 38400 connection (Eliminator from Frank Hogg Labs), I could get 2000+

> cps with Ymodem/Ymodem batch. If you have the Randy RS-232 pak, then

> about 1700-1800 cps would probably be the max with X/Ymodem (x is

> slower, since it has more overhead) using a decent term program like

> Supercomm or OSTerm. Once again, running the 6809 version of Nitros9

> might be a bit slower; I am basing on the 6309 version.

>

>

>I have a stock 512k 6809 CoCo 3 running Nitros9  v 3.2.6.

>Using X-Modem, with the port set at 4800 bps, downloads to the coco are

> 380 cps.  With the port set to 9600 bps, downloads drop to 188 cps.

>

>I found my old SACIA disk, which keeps giving me CRC errors when I try

> to read it.  Haven't put SACIA into a bootfile yet because I've been

> fighting a bootlist order problem whilst adding a ram disk.

>

>(OOOO! I just remembered that the SACIA driver and a t2 descriptor can

> be loaded AFTER system boot. )

>

>

>Ever the optimist, I tried 'xmode /t2 par=2 xtp=8' like in the SACIA

> instructions, but it didn't help.

>

Can you repost those instructions, Jim?  That help file was one of the 
casualties of my buggy B&B setup.


>I shall keep trying.

>

>-jim

>

>

>

>---------------------------------

>Want to start your own business? Learn how on Yahoo! Small Business.


-- 
Cheers, Gene