UNIX sz/rz (zmodem) transfers <-->Amiga (xpr)zmodem
newton
to 9600 baud UNIX with the UNIX rz (zmodem receive) program. I have
no trouble at all with (UNIX zmodem send) sz -b "somefile" -> (Amiga)
zmodem receive. When sending files to UNIX, rz eventually locks up
and has a time out error. Nothing will stop the program short of
logging off. I have been advised of trying to change the receive
packet size of rz to 512 bytes so that the UNIX server might not lock
up from the speed. However, I don't see this option in the man pages
or how to set the receive packet to something other than 1024, which
is the default of both send and receive. If anyone has experience
with this protocol with UNIX, please email with advice. I havee used
kermit and xmodem exclusively until I upgraded to a faster 14.4k
v32bis modem and am looking for a speedier transfer program.
Tips appreciated.
Thanks.
************************************************************
*Dale E. Newton new...@stolaf.edu *
*Blue Earth Ensemble *
*718 Saint Olaf Ave. 507-645-6817 *
*Northfield, MN 55057 //////////////////////////// *
************************************************************
Andy Wolff
Are you by any chance running through some kind of terminal server when you dial in to
your UNIX system? When I dial in I have to log in to a terminal server and then connect
via telnet from there. The terminal server has a default escape character; if I don't
turn it off, I end up interrupting the connection when transferring a binary file that
happens to contain the escape character.
I use sz/rz with xprzmodem both with a direct serial connection to a Sun workstation
at 19200 baud and via modem at 9600 with no serious problems going in either direction.
I did have to reduce the size of the input buffer on the Amiga because otherwise when
the Amiga flushed the buffers out I got timeouts from the sender. I use the VLT terminal
program.
Andy Wolff
a...@cray.com
Graham Reed
: I have had difficulty transmitting files using (xpr)zmodem from Amiga
: to 9600 baud UNIX with the UNIX rz (zmodem receive) program. I have
: no trouble at all with (UNIX zmodem send) sz -b "somefile" -> (Amiga)
: zmodem receive. When sending files to UNIX, rz eventually locks up
: and has a time out error. Nothing will stop the program short of
: logging off. I have been advised of trying to change the receive
: packet size of rz to 512 bytes so that the UNIX server might not lock
: up from the speed. However, I don't see this option in the man pages
I don't know which side has the bugs, my vote is for the UNIX software.
I think you need to change the "Frame size" setting on the Amiga end to
affect RZ. I've had problems with RZ as well, and I haven't really
spent a lot of time trying to fix them. Until recently, KERMIT to the
mainframe worked well, but today that failed... Sigh. Plus, with my
slick new USRobotics Sportster 14,400, KERMIT is UGLY and SLOW!
--
____ Graham Reed
\ / 301...@QUCDN.QueensU.ca Bug: A feature you cannot turn off.
\/ (Formerly gr...@bnr.ca) -- Me.
Michael T Pins
>newton (new...@mari.acc-admin.stolaf.edu) wrote:
>: I have had difficulty transmitting files using (xpr)zmodem from Amiga
>: to 9600 baud UNIX with the UNIX rz (zmodem receive) program. I have
>: no trouble at all with (UNIX zmodem send) sz -b "somefile" -> (Amiga)
>: zmodem receive. When sending files to UNIX, rz eventually locks up
>: and has a time out error. Nothing will stop the program short of
>: logging off. I have been advised of trying to change the receive
>: packet size of rz to 512 bytes so that the UNIX server might not lock
>: up from the speed. However, I don't see this option in the man pages
>I don't know which side has the bugs, my vote is for the UNIX software.
>I think you need to change the "Frame size" setting on the Amiga end to
>affect RZ. I've had problems with RZ as well, and I haven't really
>spent a lot of time trying to fix them. Until recently, KERMIT to the
>mainframe worked well, but today that failed... Sigh. Plus, with my
>slick new USRobotics Sportster 14,400, KERMIT is UGLY and SLOW!
Get the new version of Kermit for both ends.
Kermit 5A(188) runs about 80% the speed of zmodem, and is considerably
more reliable. Of course, I never haven't had any trouble uploading
with zmodem since I tweaked the zmodem params in VLT.
--
*****************************************************************************
* Michael Pins | Internet: ami...@isca.uiowa.edu *
* ISCA's Amiga & Unix Librarian | #include <std.disclaimer> *
*****************************************************************************
dse...@kuhub.cc.ukans.edu
> : I have had difficulty transmitting files using (xpr)zmodem from Amiga
> : to 9600 baud UNIX with the UNIX rz (zmodem receive) program. I have
> : no trouble at all with (UNIX zmodem send) sz -b "somefile" -> (Amiga)
> : zmodem receive. When sending files to UNIX, rz eventually locks up
> : and has a time out error. Nothing will stop the program short of
> : logging off. I have been advised of trying to change the receive
> : packet size of rz to 512 bytes so that the UNIX server might not lock
> : up from the speed. However, I don't see this option in the man pages
>
> I don't know which side has the bugs, my vote is for the UNIX software.
> I think you need to change the "Frame size" setting on the Amiga end to
> affect RZ. I've had problems with RZ as well, and I haven't really
> spent a lot of time trying to fix them. Until recently, KERMIT to the
> mainframe worked well, but today that failed... Sigh. Plus, with my
> slick new USRobotics Sportster 14,400, KERMIT is UGLY and SLOW!
I have basically the same problem. At either 2400 or 9600 baud after
just a few blocks the transfer fails. I gather this is a problem with
RZ and not xprzmodem. With term 3.1 when I open the xprKermit library,
it automatically jumps into download mode and locks up. :( So I can't
upload at all.
Derek
--
DSe...@kuhub.cc.ukans.edu
Derek Seaman
mneylon@jupiter
I originally wrote the first guy cause I thought this is a simple problem,
but obviously, many seem to have problems.
Anyway, I have found that using the following sz/rz commands do NOT
cause a lock up of your term...
sz -l 512 -o -e {files}
rz -o (or is it '-e'....its one or the other)
The important flag is the one that causes the UNIX side to IGNORE control
characters. A std .lha file has almost every singal control character in
it, and at least one of them is bound to lock up your unix shell. Forcing
them to ignore them may slow down your download (at 2400, I get ~160 cps),
but I haven't had any other problems with sz/rz yet.
Another tip is to make sure the filename(S) you pass to sz are absolutely
correct. At least in the version of sz I use, sz does not check as to the
existance of the file requested. My solution: either (1) type it in REALLY
carefully (2) use file-completion (3) use wildcards.
One further tip: if you have problems with sz/rz still, but you either
have a really good data connection or a term program with ascii upload, then
try using the UUencode/decode stuff. Although file sizes are a lot bigger,
it is much easier to transfer a UU file. Amiga side equivalents can be
found at a local ftp site near you. ASCII send is the easiest for this,
but if you lack that, then try capturing (with your term) the output from
'cat {file}'. Of course, I strong recommend a very good data line and file
sizes bordering 100k.
Finally, you may want to check with others that are on your campus/worksite,
whatever, as to what they use. For example, I normally log on to this
computer via a Gandlaf (sp) system, thru a number server, to here. However,
I cannot use sz/rz as normal...nothing is sent across the server.
Alternatively, I found that if I log into the gandlaf, go to number server,
JUMP to another server, then to this computer, sz/rz works fine. check
with local people on the particularities of your own system.
Hope this helps!
--
Michael Neylon aka Masem the Great and Almighty Thermodynamics GOD!
| Senior, Chemical Engineering, Univ. of Toledo
// Only the | Summer Intern, NASA Lewis Research Center
\X/ AMIGA! | Will-Be Grad Student, Univ. of Michigan
\ | mne...@jupiter.cse.utoledo.edu /
--------+ How do YOU spell 'potato'? How 'bout 'lousy'? +----------
Physical Chemistry - An attempt to apply y=mx+b to everything in the
entire universe
Faith and Devotion
<dse...@kuhub.cc.ukans.edu wrote:
<
<> > : I have had difficulty transmitting files using (xpr)zmodem from Amiga
<> > : to 9600 baud UNIX with the UNIX rz (zmodem receive) program. I have
<> > : no trouble at all with (UNIX zmodem send) sz -b "somefile" -> (Amiga)
<> > : zmodem receive. When sending files to UNIX, rz eventually locks up
<> > I don't know which side has the bugs, my vote is for the UNIX software.
<> > I think you need to change the "Frame size" setting on the Amiga end to
<> > affect RZ. I've had problems with RZ as well, and I haven't really
<> > spent a lot of time trying to fix them. Until recently, KERMIT to the
<> > mainframe worked well, but today that failed... Sigh. Plus, with my
<> > slick new USRobotics Sportster 14,400, KERMIT is UGLY and SLOW!
Very ugly and very slow. Back when I had a 2400 baud modem. I would
occasionally go up to campus and use Kermit on the PC's there which were hooked
up to the campus network at 9600 baud. I swear it was only 30-50% faster than
doing it on my 2400 baud! I finally wised up and brought Telix w/ me. Kermit
stinks and I always try to sway users away from it whenever they call me for
help.
<> I have basically the same problem. At either 2400 or 9600 baud after
<> just a few blocks the transfer fails. I gather this is a problem with
<> RZ and not xprzmodem. With term 3.1 when I open the xprKermit library,
<> it automatically jumps into download mode and locks up. :( So I can't
<> upload at all.
A possible cause is actually your terminal server. If your campus network uses
a Xyplex terminal server, see below.
<I originally wrote the first guy cause I thought this is a simple problem,
<but obviously, many seem to have problems.
<
<Anyway, I have found that using the following sz/rz commands do NOT
<cause a lock up of your term...
<
<sz -l 512 -o -e {files}
<rz -o (or is it '-e'....its one or the other)
<
<The important flag is the one that causes the UNIX side to IGNORE control
<characters. A std .lha file has almost every singal control character in
<it, and at least one of them is bound to lock up your unix shell. Forcing
<them to ignore them may slow down your download (at 2400, I get ~160 cps),
<but I haven't had any other problems with sz/rz yet.
-e does filter out the control chars but I believe someone mentioned a while
back that xprzmodem doesn't have -e built in. I've tried it on our Unix
machine and indeed it doesn't work. This is a shame 'cause for now, you have
to log in, send a break and at the local prompt, type 'set session passall'.
This turns off the filtering that the Xyplex will do which will screw up your
transfers. Although I do work for our campus network, I'm definitely no expert
and am very bad about getting facts skewed ;)
Note: you have to start a session first for the above to work.
<Another tip is to make sure the filename(S) you pass to sz are absolutely
<correct. At least in the version of sz I use, sz does not check as to the
<existance of the file requested. My solution: either (1) type it in REALLY
<carefully (2) use file-completion (3) use wildcards.
Ours will just give up if it's not there.
<Finally, you may want to check with others that are on your campus/worksite,
<whatever, as to what they use. For example, I normally log on to this
<computer via a Gandlaf (sp) system, thru a number server, to here. However,
<I cannot use sz/rz as normal...nothing is sent across the server.
<Alternatively, I found that if I log into the gandlaf, go to number server,
<JUMP to another server, then to this computer, sz/rz works fine. check
<with local people on the particularities of your own system.
This is an excellent suggestion. Although, I work at the center that controls
all of the Texas A&M's network throughout Texas and handles problems related to
it. I've had only 1 person call me with this problem. Of course, it was
looked into 'cause I had the problem too so I knew it wasn't just me :)
-Judas
Raoul Rodriguez
>
>> > : I have had difficulty transmitting files using (xpr)zmodem from Amiga
>> > : to 9600 baud UNIX with the UNIX rz (zmodem receive) program. I have
>> > : no trouble at all with (UNIX zmodem send) sz -b "somefile" -> (Amiga)
>> > : zmodem receive. When sending files to UNIX, rz eventually locks up
>> > : and has a time out error. Nothing will stop the program short of
>> > : logging off. I have been advised of trying to change the receive
>> > : packet size of rz to 512 bytes so that the UNIX server might not lock
>> > : up from the speed. However, I don't see this option in the man pages
I am not sure how your site works, but I have to log onto an ethernet
server and then go to the system to download... downloading (with the
-b optin on) isn't a problem... but uploading is, the solution?
Send a Bresk (RTAmiga-B in JRComm) and then "set session passall" and
then type an "r" in order to get back to your session... and then
upload whatever you want too...
Raoul
Dan Bachmann
>I have had difficulty transmitting files using (xpr)zmodem from Amiga
>to 9600 baud UNIX with the UNIX rz (zmodem receive) program. I have
>no trouble at all with (UNIX zmodem send) sz -b "somefile" -> (Amiga)
>zmodem receive. When sending files to UNIX, rz eventually locks up
>and has a time out error. Nothing will stop the program short of
I had the same problem, but if I do:
rz -e
then all works fine. (I'm also only at 2400 though)
- Dan
stephen walton
and Devotion) writes:
>[Kermit is]
>Very ugly and very slow. Back when I had a 2400 baud modem. I would
>occasionally go up to campus and use Kermit on the PC's there which were hooked
>up to the campus network at 9600 baud. I swear it was only 30-50% faster than
>doing it on my 2400 baud! I finally wised up and brought Telix w/ me. Kermit
>stinks and I always try to sway users away from it whenever they call me for
>help.
As the messages leading up to this comment show, Zmodem works great---provided
you are transferring files from one ASCII machine to another over a clean
8-bit-transparent data path. On the other hand, Kermit:
1) allows binary transfers over 7-bit lines
2) escapes control characters, so having XON/XOFF flow control on, for
example, will not prevent the transfer
3) can transfer files between machines which use different character sets,
like IBM mainframes using EBCDIC
4) is, in my experience, much better at transferring files over noisy
lines than Zmodem
5) can be put into "server mode," so you only have to type commands at
one end to transfer files or even execute system commands on the remote
machine
6) is freely distributable, though copyright by Columbia University
7) runs on several hundred different computers
8) can switch between text-mode and binary-mode transfers on a per-file
basis
9) with the sliding windows option, is nearly as fast as anything
else. I regularly get transfers at 920 characters per second on a
9600 baud line with windowed Kermit. The slightly smaller (15%) data
rate compared to zmodem is more than compensated for by the fewer
(zero, in fact) times I have to retry sending the files
10) can translate files between national character sets on the fly;
for example, a u-umlaut can be transliterated into ue when
transferring from a German to an English-speaking machine
Now, I admit, as the co-author, that the current version of XPR
Kermit, which is what most of you out there are using, doesn't have
items 8 to 10 above. However, C Kermit 5A(188), which I worked hard
at getting and keeping running on the Amiga, does. There is, in fact,
a special appendix in the recently published book "Using C Kermit" by
Frank da Cruz and Christine Giannone describing how to use C Kermit on
the Amiga.
I hope to have a new version of XPR Kermit with the sliding windows and
attribute packet options available for generaly use within a few weeks;
it is presently in beta test.
--
Stephen Walton, Cal State Northridge
"Anyone who remembers the sixties probably wasn't there."---Robin Williams