Date: Tue, 07 Nov 2000 07:29:25 -800
From: "Ronald C. Dailey" <[EMAIL PROTECTED]>
Subject: Re: will someone remind me why....
On 2000-11-07 [EMAIL PROTECTED] said:
>Date: Tue, 07 Nov 2000 11:36:41
>AFAIK, sz - and thus DSZ - came out ot the *nix network realm; and
>there sure is the Linux "sz" - so that (or its DOS port) should run
>on an appropriate packet driver socket in DOS too, shouldn't it ?
>// Heimo Claasen // < hammer at inti dot be > // Brussels
>2000-11-07 The WebPlace of ReRead - and much to read ==> http://www.
>inti.be/hammer
The problem with DSZ seems to be mostly with telnet, and not necessarily
with PPP. Since zmodem works with Windows telnet clients, even that can
be overcome, it would appear.
Here's an excerpt from the DSZ Background Doc relative to telnet and
zmodem:
Terminals on some timesharing systems are connected indirectly to the
host with TERMINAL SERVERS operating over networks. Terminal servers
often interfere with file transfers by "eating" control characters
and/or losing data.
Accessing a distant system using telnet on a local Unix system entails
the same problems. If telnet does not work well, try rlogin with the
-8 option. Set the escape character to ^P (control P) which is
protected by ZMODEM.
When terminal servers interfere with file transfers, server commands
are often available to help the problem. When possible, enable the
server and modems for hardware flow control in and out. Set the
terminal server to telnet transparent mode. Some typical commands are
"SET TERMINAL DOWNLOAD", "set session passall", and "SET TERMINAL NO
ESC", but there is no standard set of commands suitable for all
terminal servers. Normally these commands are given before attempting
file transfers, but one user has reported that the command must be
given after the file transfer is started(!). Until terminal server
vendors improve the quality of their product, you may have to get on
their case until they adequately support high performance file
transfers.
The telnet protcol used by the telnet program and terminal servers
uses 0xFF (377 octal) for special control functions. The 0xFF
character may cause problems if it appears in the data stream,
especially uploading at high speeds. With ZCOMM or Professional-YAM
the 0xFF character can be protected by giving the command:
set zmtxesc ?
Escaping control characters with ZMODEM (sz -e) may help if the
transfer gets stuck in the same place on every attempt.
Professional-YAM and ZCOMM allow selection of which control characters
need to be escaped. In extreme cases 7-bit transmission may be
required (see the Professional-YAM/ZCOMM manual). If you encounter
problems with control characters you should identify which control
characters are causing the problem. Please refer to the sz -T command
in sz.doc for more help.
The catch is that several references are made to Professional-YAM and
ZCOMM rather than DSZ itself. DSZ may not have all the options
necessary to allow it to work well with telnet and not everyone will
have access to rlogin, especially those using Net-Tamer since Net-Tamer
doesn't offer rlogin as an option. I used to use rlogin when I accessed
a remote BBS to upload and download SOUP mail packets. With that BBS,
zmodem would work for downloads via telnet, but not for uploads. Using
rlogin, I could do both. However, I didn't use the -8 option, just
plain "rlogin <URL>" and went there. I then used the options on the BBS
to download and upload using zmodem as the protocol.
Ronald Dailey
--
RCD
Net-Tamer V 1.12.0 - Registered
********************************************************
To unsubscribe from this list,
send a message to [EMAIL PROTECTED] with the single word
Unsubscribe
as the subject.
You MUST use the same address with which you subscribed!
********************************************************
