Serial File Tranfer on 3.2r4.2
bob
onto, in this case, an OpenBSD machine. (That's my 'lug around to where
it's needed' box.) I have a null modem cable and terminal emulation
(minicom) with X, Y and Zmodem running on the obsd machine.
I don't know what to expect on the old SCO in the way of, say, an 'sz'
command that would initiate a transfer. I note on SCO's ftp site, in
/TLS, source code for sz but I don't think this SCO system has make or a
compiler on it.
So, once hooked up and logged into the SCO, what in the way of 'original
equipment' (we're talking a real bare-bones 3.2.r4.2 here) may one
expect to find that could start up a file transfer? Does anyone have sz
binaries available for download? I don't know my way around Kermit that
well, but has that been compiled for the old SCO?
--
Bob Bernstein
at
Esmond, Rhode Island, USA
--==++*++==--
"RMS's "curmudgeon-like" griping that he didn't like the term "Open
Source" looked silly to many last year; it's not looking so dumb
today..." Christopher B. Browne
Frank da Cruz
: I have a need to copy a few megs worth of files off a 3.2.r4.2 system
: onto, in this case, an OpenBSD machine. (That's my 'lug around to where
: it's needed' box.) I have a null modem cable and terminal emulation
: (minicom) with X, Y and Zmodem running on the obsd machine.
:
: I don't know what to expect on the old SCO in the way of, say, an 'sz'
: command that would initiate a transfer. I note on SCO's ftp site, in
: /TLS, source code for sz but I don't think this SCO system has make or a
: compiler on it.
:
: So, once hooked up and logged into the SCO, what in the way of 'original
: equipment' (we're talking a real bare-bones 3.2.r4.2 here) may one
: expect to find that could start up a file transfer? Does anyone have sz
: binaries available for download? I don't know my way around Kermit that
: well, but has that been compiled for the old SCO?
Yes, and for OpenBSD too. See:
http://www.columbia.edu/kermit/ck70.html
Prebuilt binaries are listed at the bottom of the page.
- Frank
bob
> : I don't know my way around Kermit that
> : well, but has that been compiled for the old SCO?
> :
> Yes, and for OpenBSD too. See:
>
> http://www.columbia.edu/kermit/ck70.html
How about sz and rz? Anyone seen any binaries for 3.2r4.2?
Jean-Pierre Radley
| Frank da Cruz wrote:
|
| > : I don't know my way around Kermit that
| > : well, but has that been compiled for the old SCO?
| > :
| > Yes, and for OpenBSD too. See:
| > http://www.columbia.edu/kermit/ck70.html
In fact the latest kermit has also been compiled for Xenix 2.3.4.
| How about sz and rz? Anyone seen any binaries for 3.2r4.2?
They've been languishing in the LIBraries of SCOFORUM on CompuServe for
years.
--
Jean-Pierre Radley <j...@jpr.com> XC/XT Custodian Sysop, CompuServe SCOForum
bob
> http://www.columbia.edu/kermit/ck70.html
>
> Prebuilt binaries are listed at the bottom of the page.
I am going to try kermit! A little test run between Linux and OpenBSD
both running kermit showed I could even jack up the serial line to
19200, which I haven't been successful with running dumb terminals on
DOS boxes.
bob
> | How about sz and rz? Anyone seen any binaries for 3.2r4.2?
>
> They've been languishing in the LIBraries of SCOFORUM on CompuServe for
> years.
There's no way for a Compuserve non-customer to get those, yes?
Jean-Pierre Radley
| Jean-Pierre Radley wrote:
|
| > | How about sz and rz? Anyone seen any binaries for 3.2r4.2?
| >
| > They've been languishing in the LIBraries of SCOFORUM on CompuServe for
| > years.
|
| There's no way for a Compuserve non-customer to get those, yes?
Correct. You'll have to find binaries in some other repository.
May I ask WHY you're so keen on getting rzsz?
bob
> May I ask WHY you're so keen on getting rzsz?
I started this thread with a description of my little project of copying
a fair number of files off a 3.2r4.2 system, eventually to reside on a
Linux box. My experience with serial file transfer is (it will come as
no shock to anyone <g>) limited, and playing around with Linux tools
such as minicom I became familiar with sz and rz. So I couched my query
in terms of "what is there available for SCO that resembles the rz and
sz I find on Linux."
The answer so far seems to be: rz and sz, or kermit. I have the kermit
binary for 3.2.r4.2 and plan to try that, but today I heard yet again
from one of the folks I'm working with that she had used sz and rz on
this flavor of SCO, so I am interested in finding them also.
Any thoughts about how a null modem cable might be put to use between a
SCO system and a Linux one (or, in this case, OpenBSD) in order to copy
a lot of files from the one to the other?
Jean-Pierre Radley
| Jean-Pierre Radley wrote:
|
| Any thoughts about how a null modem cable might be put to use between a
| SCO system and a Linux one (or, in this case, OpenBSD) in order to copy
| a lot of files from the one to the other?
This is getting to be a bit circular.
Why go hunting around for rzsz or kermit, when this is a a one time
project, and both machines already have uucp?
Connect them with a null-modem between two serial ports and just do the
deed with uucp.
David Woolley
>| How about sz and rz? Anyone seen any binaries for 3.2r4.2?
>
>They've been languishing in the LIBraries of SCOFORUM on CompuServe for
>years.
They were in the TLS when I looked, but it would be illegal to use them
with minicom, as they are NOT the public domain or GPL versions, but ones
which must be used with a licensed Z-modem client.
Of course, the real answer in this case is UUCP.
bob
> They were in the TLS when I looked, but it would be illegal to use them
> with minicom, as they are NOT the public domain or GPL versions, but ones
> which must be used with a licensed Z-modem client.
IAC these are source code, no? The only binaries I've found were on the
Freebird site, and I'm not clear if they'll run on 3.2r4.2. Time will
tell.
> Of course, the real answer in this case is UUCP.
So I gather. Time to plunge into docs again!
Bill Vermillion
>> They were in the TLS when I looked, but it would be illegal to
>> use them with minicom, as they are NOT the public domain or GPL
>> versions, but ones which must be used with a licensed Z-modem
>> client.
>IAC these are source code, no? The only binaries I've found were on the
>Freebird site, and I'm not clear if they'll run on 3.2r4.2. Time will
>tell.
The old freely distributable rs/sz source code is still out there
somewhere - at least on some of the CD's of the usenet source
archives - 1989/90 time frame. I've seen it somewhere in the past
year.
>> Of course, the real answer in this case is UUCP.
>So I gather. Time to plunge into docs again!
It works. Quite well too. It's like so many things in Unix -
there is a legend built up that says it's so hard to understand,
but it's not really.
--
Bill Vermillion bv @ wjv.com
bob
> The old freely distributable rs/sz source code is still out there
> somewhere - at least on some of the CD's of the usenet source
> archives - 1989/90 time frame. I've seen it somewhere in the past
> year.
Hi Bill. I found source in various places, but I want to avoid bringing
the SCO system up to compile-speed. The binaries found on Freebird do
not want to run on 3.2r4.2, and complain by way of reference to a C
shared lib of syntax errors. I grabbed the kermit binary for 3.2r4.2 and
it seems to work ok. Monday will be the acid test with the two machines.
It will be slow but my guess is it'll start to get the job done while I
figure out UUCP!
> >> Of course, the real answer in this case is UUCP.
> It works. Quite well too. It's like so many things in Unix -
> there is a legend built up that says it's so hard to understand,
> but it's not really.
I am going to muck ahead this weekend to see if I can get it working
between my Linux and OpenBSD computers.
One more query: in testing kermit between those two computers just
mentioned I was able to up the speed on the Linux port to 19200: just
edit inittab and issue the command 'init q'. Come Monday I would like to
do the same to the SCO machine; I am going to be placing my null modem
cable on a port set to 9600 for a Wyse terminal. Are there an equivalent
set of moves (or an equivalently simple set of moves <g>) I can make on
the SCO system to achieve that end?
Frank da Cruz
: ... I grabbed the kermit binary for 3.2r4.2 and
: it seems to work ok. Monday will be the acid test with the two machines.
: It will be slow but my guess is it'll start to get the job done while I
: figure out UUCP!
Why do you think it will be slow? Please visit:
http://www.columbia.edu/kermit/kermit.html
to clear up this unfortunate but apparently still widespread misconception.
Short story: In file transfer protocols, there is a tradeoff between speed
and robustness. Kermit was tuned for robustness by default on the mistaken
impression that people would appreciate it more if it tended to work out
of the box. Then if they wanted to see how fast it would go, they would give
it a command like "fast". C-Kermit 7.0:
http://www.columbia.edu/kermit/ck70.html
(which, I hope, is the one you picked up) no longer has this default tuning,
since in the real world, people tend to read documentation only when something
doesn't work at all, rather than when it works slowly.
In any case, if you have any trouble with Kermit, you can send email to:
to get help and you can visit the website:
http://www.columbia.edu/kermit/
to read the FAQ, etc, and you can also read and post to the newsgroup:
comp.protocols.kermit.misc
: One more query: in testing kermit between those two computers just
: mentioned I was able to up the speed on the Linux port to 19200: just
: edit inittab and issue the command 'init q'.
:
You don't need to edit external files in order to use Kermit -- this sets it
off from most other UNIX-based communication software. However, you *do*
need to install it with needed user, group, and permissions to access the
dialout device and lockfile -- the same as cu and friends.
In Linux, C-Kermit 7.0 supports speeds up to 460800 bps. I don't have an SCO
3.2v4.2 system handy at the moment, but it should allow any speed up to 38400,
maybe 57600 ("set speed ?" will tell you). Unfortunately, I don't think SCO
3.2v4.2 supports hardware flow control so you'll have trouble with high-speed
null-modem transfers from Linux to SCO, but it shouldn't be to bad in the
other direction.
Of course, the common cautions about misconfigured PCs (interrupt conflicts,
etc) and unbuffered UARTs apply.
- Frank
Jean-Pierre Radley
| In Linux, C-Kermit 7.0 supports speeds up to 460800 bps. I don't have an SCO
| 3.2v4.2 system handy at the moment, but it should allow any speed up to 38400,
| maybe 57600 ("set speed ?" will tell you). Unfortunately, I don't think SCO
| 3.2v4.2 supports hardware flow control so you'll have trouble with high-speed
| null-modem transfers from Linux to SCO, but it shouldn't be to bad in the
| other direction.
SCO Unix 3.2v4.2 admits no serial port speeds beyond 38400.
But it supports hardware flow control quite handily.
ruptur...@home.com
> Why do you think it will be slow?
Firstly, thank you for all this info!
I guess I am hogtied by my experience setting up the dumb terminal session on
that serial port; 9600, perhaps 19200, seems to be the limit depending on
what I have running as the terminal. IAC I can't arrange a login at speeds
in excess of those.
But I am off in search of more how-to knowledge.
Frank da Cruz
: : ... I grabbed the kermit binary for 3.2r4.2 and
:
: In Linux, C-Kermit 7.0 supports speeds up to 460800 bps. I don't have an
: SCO 3.2v4.2 system handy at the moment...
:
But now I do...
: but it should allow any speed up
: to 38400, maybe 57600 ("set speed ?" will tell you). Unfortunately, I
: don't think SCO 3.2v4.2 supports hardware flow control so you'll have
: trouble with high-speed null-modem transfers from Linux to SCO, but it
: shouldn't be to[o] bad in the other direction.
:
Correction: SCO 3.2v4.2 *does* support RTS/CTS, and so does C-Kermit:
$ ./wermit
C-Kermit 7.0.195 Beta.07, 21 May 1999, for SCO UNIX/386 V4
Copyright (C) 1985, 1999,
Trustees of Columbia University in the City of New York.
Default file-transfer mode is AUTOMATIC
Type ? or HELP for help.
(/u/fdc/kermit/) C-Kermit>set speed ?
Transmission rate for /dev/tty in bits per second, one of the following:
110 134.5 1800 200 300 4800 600 9600
1200 150 19200 2400 38400 50 75
(/u/fdc/kermit/) C-Kermit>set flow ?
Flow control type, one of the following:
keep none rts/cts xon/xoff
or connection type, one of the following:
/direct-serial /modem /remote /tcpip
(/u/fdc/kermit/) C-Kermit>
And, as JPR said, the highest speed in SCO 3.2v4.2 is 38400. In Linux:
$ ./wermit
C-Kermit 7.0.195 Beta.07, 21 May 1999, for Linux
Copyright (C) 1985, 1999,
Trustees of Columbia University in the City of New York.
Default file-transfer mode is AUTOMATIC
Type ? or HELP for help.
(/home/fdc/kermit/) C-Kermit>set speed ?
Transmission rate for /dev/tty in bits per second, one of the following:
110 1200 150 19200 230400 300 460800 50 600 9600
115200 134.5 1800 200 2400 38400 4800 57600 75
(/home/fdc/kermit/) C-Kermit>
Thus you should be able to use C-Kermit 7.0 to transfer files between Linux
and SCO 3.2v4.2 at 38400 bps with hardware flow control, and get transfer
rates close to or better than 3840 cps, depending what kind of data it is.
- Frank
ruptur...@home.com
> : In Linux, C-Kermit 7.0 supports speeds up to 460800 bps. I don't have an
> : SCO 3.2v4.2 system handy at the moment...
> :
> But now I do...
Ah...someone will be missing a system when they show up Monday morning? <g>
> Correction: SCO 3.2v4.2 *does* support RTS/CTS, and so does C-Kermit:
Well, Monday will be when I next get my hands on the SCO system, but today
I was able to get a Linux and an OpenBSD to transfer files easily in 3500 cps
range, and in one case (the connection seems faster one way than the other - a
hardware difference?) the rate went to 4063, this with both machines set for
38400. So I'm sold on Kermit for this job. Thanks again.
I will have to disable the getty in SCO on the serial line I'm going to use,
so if that proves a stumbling block I'll be back!
Jean-Pierre Radley
|
| And, as JPR said, the highest speed in SCO 3.2v4.2 is 38400.
Now JPR amends that:
38400 is the best that the SCO serial driver can do. But speed mapping
of 50 ==> 57600 and 75 ==> 76800 was long ago possible on smart serial
boards that Specialix, Digi and other vendors sold for SCO Unix 3.2v4.2.
Jean-Pierre Radley
| Well, Monday will be when I next get my hands on the SCO system, but today
| I was able to get a Linux and an OpenBSD to transfer files easily in 3500 cps
| range, and in one case (the connection seems faster one way than the other - a
| hardware difference?) the rate went to 4063, this with both machines set for
| 38400. So I'm sold on Kermit for this job. Thanks again.
|
| I will have to disable the getty in SCO on the serial line I'm going to use,
| so if that proves a stumbling block I'll be back!
Why would you have to disable the getty? I never do, all of my modems
are fully DIDO-capable, and they stay enabled at all times.
Bob Bernstein
> Why would you have to disable the getty? I never do, all of my modems
> are fully DIDO-capable, and they stay enabled at all times.
The two serial ports on this SCO machine are configured for dumb terminals
and are set to 9600. Since I have hands-on access to it, if I disable the
getty
I can have kermit "run" the port, and then set speeds higher than 9600. The
null modem cable can obviously do better than that.
This scenario is a little different. Instead of logging into the SCO from a
Linux box acting as a dumb terminal, and thereby surrending the line to the
getty's 9600, I can start kermit on the SCO, use kermit's 'set line' and
'set speed' to configure the port (not possible if getty is running on it) and
then put kermit in 'server' mode. At this point there's no 'login' from the
Linux machine: just start kermit and issue 'get' commands.
> --
> Jean-Pierre Radley <j...@jpr.com> XC/XT Custodian Sysop, CompuServe SCOForum
--