home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Current Shareware 1994 January
/
SHAR194.ISO
/
modem
/
digibord.zip
/
ZSX201.ZIP
/
README.ZSX
< prev
next >
Wrap
Text File
|
1991-06-24
|
9KB
|
207 lines
ZSX v2.00 - a general purpose protocol driver
(C) 1990, 1991 by Jan R. Terpstra (FIDO 2:512/10.0)
WHAT IS ZSX
===========
ZSX is a general purpose protocol driver for Bulletin Board Systems. It
features SEAlink (with overdrive), Xmodem, Ymodem, Ymodem-Batch, Ymodem-G
and Zmodem protocols and requires only 55KB free RAM to run.
ZSX requires a FOSSIL driver like OPUS!COMM, x00 or BNU to drive the
communication port. With x00 and BNU, up to 8 ports are supported.
NOTE: When using x00, use version 1.23j or later.
ZSX is a protocol driver for Bulletin Board systems, NOT a universal file
transfer program like DSZ, PCKERMIT, JMODEM, SuperK or Lynx. Compared to
other (tm) programs, DSZ is slightly crippled:
- Zmodem receive has no crash-recovery. This prevents files on your BBS
from being overwritten or changed by a user. Zmodem send does support
recovery so aborted downloads from your BBS can be picked up at the point
where they aborted.
- NAK, CANcel and Carrier drop are ignored for the last block of a download.
This is to prevent the nasty users to evade the up/download counter of
your BBS. The bozos do so by aborting the download between the last block
of the file and the subsequent NAK/ACK sequence on the EOT signal. That
trick won't work with ZSX!
- During Zmodem, Ymodem and SEAlink receive, one can optionally refuse any
additional files to prevent existing files from being overwritten.
Running ZSX
===========
To run ZSX, type ZSX followed by one or more of these options:
port N speed N <D d e f o y Z> [list <file>] [log <file>] <cmd> <[@]file>
NOTE: Options are case sensitive!!!!
port communications port to be used. Can be 1....8, defaults to
com 1. When ZSX is used with OPUS!COM, only 2 ports are
supported.
speed linespeed. Can be 300....38400, defaults to 2400.
D (upper case D) Drop DTR when carrier is lost. Some BBS
programs act a little odd when an external protocol does not
reset the modem on carrier loss.
d (lower case d) Disable carrier monitor. Comes in handy when
sending files over a null-modem.
e Escape all control characters for Zmodem. This slows down
transfer by up to 50%, but it allows Zmodem transfer over
non-transparent networks
L Length overrride for Zmodem send blocks (32.....1024).
r Be forgiving for Xmodem, Ymodem and SEAlink timing. Usefull if
transferring files over a satellite link ("relaxed" timing).
o Run SEAlink in Overdrive mode.
y Allow receive to overwrite existing files.
Z Use Zmodem RLE compression. Option is disabled automatically
when transferring ARC, ARJ, DWC, GIF, LZH, PAK, ZIP and ZOO
files, since those files are already compressed.
log Filename to log succeeded or failed transfers to. The logfile
is compatible with DSZ's log file. ZSX will recognize the
"DSZLOG=" environment variable.
list Filename where the names and sizes of received files are stored
when receiving multiple files. This file can later used by the
BBS program to prompt the user to enter the descriptions of the
uploaded files.
cmd: sz = ZMODEM send file(s)
ss = SEAlink send file(s)
sb = Ymodem-Batch (True-Ymodem) send file(s)
sy = Ymodem (Xmodem-1K) send file
sg = Ymodem-G send file
sx = Xmodem send file
rz = Zmodem receive file(s)
rs = SEAlink receive file(s)
rb = Ymodem-Batch (True-Ymodem) receive file(s)
ry = Ymodem (Xmodem-1K) receive file
rg = Ymodem-G receive file
rx = Xmodem receive file
file filename to be send/received.
@file Name of the response file that lists the files to be send in
one batch.
SOME EXAMPLES
=============
ZSX port 1 speed 2400 Z rz C:\MYFILES\AAA.BBB
receive Zmodem/Compressed file AAA.BBB to subdir C:\MYFILES via port 1
at 2400 bps Only AAA.BBB will be received, additional file(s) will be
refused.
ZSX port 1 speed 9600 o ss @FIL.LST
send Sealink-Overdrive files listed in FIL.LST via port 1 at 9600 bps
ZSX port 2 speed 9600 rb C:\FILES\
receive Ymodem-Batch via port 2 at 9600 bps. Received file(s) will be
written to subdir C:\FILES\
ZSX port 8 speed 300 rx C:\FILES\FILE.NEW
receive Xmodem FILE.NEW into subdir C:\FILES\ via port 8 at 300 bps
ZSX port 5 speed 38400 list UPLOADED.LST d y rz C:\FILES\
receive Zmodem via port 5 at 38400 bps. Omit carrier check. Received
file(s) will be written to subdir C:\FILES\ and existing file(s) will
be overwritten. Names and filesizes of received files will be written
to list-file UPLOADED.LST.
ZSX port 2 speed 19200 o sg *.*
send all files in the current directory using Ymodem-G via port 2 at
19200 bps.
ZSX port 1 speed 2400 sx C:\FILES\*.*
Send all files in the current directory using Xmodem via port 2 at 2400 bps.
Because Xmodem and Ymodem (rather, Xmodem-1K) are not batch protocols, ZSX
will send the name of the file about to be sent as a readable string to the
receiver's end, right before the file is transmitted.
Notice: ZSX reports the relative throughput at the end of the transfer.
Contrary to other popular transfer utiltities, ZSX reports the ACTUAL
efficiency, including the protocol's overhead (init handshake, header
block transfer and EOF handshake). Thus the relative througput reported
will be slightly less (but more honest) when compared to other protocol
drivers.
Because the granularity of the throughput timer is 1 second, transferring
small files (i.e. less then about 30 seconds) may report an efficiency of
over 100% or an efficiency that seems way to low.
COPYRIGHTS AND SUCH
===================
Apart from the rights on those parts of the code by Omen Tech and System
Enhancement Associates, this program is free of idiosyncratic license
requirements. You may use this program in a non-commercial environment in
whatever way you like. You may use it as a doorstop or feed it to your dog.
Use in a commercial environment may require you to enter a license agreement
with either Omen Tech or System enhancement Associates. I don't want to get
involved in all sorts of legal discussions, so ask them and don't you dare
to bug me about it!!!!!
However, a simple registration of this product is required! Register by
sending a postcard to:
J.R. Terpstra
P.O.Box 66
1462 ZH Beemster
The Netherlands
Registration won't buy you anything and you're not entitled to anything
special when registering this program. I just happen to like postcards.
RELEASE NOTES
=============
June 24, 1991 - v2.01
Fixed a minor bug in carrier detect of Zmodem routines
June 16, 1990 - v2.00
Added Zmodem/Compressed (RLE compression) and Zmodem variable headers.
Changed all CRC routines to assembler.
Changed logging, ZSX now writes a DSZ style logfile.
Bugs fixed:
- SEAlink/Overdrive timeout problem.
- Zmodem receive failure on last block.
December 1, 1990 - v1.70
After several beta-test releases, version 1.70 is now released to the
general public. The documentation is a bit sparse and the program needs
some minor cosmetic fixes, but the program is functional.
KUDOS
=====
ZSX was based on (and contains parts of) Chuck Forsberg's Zmodem routines
and SEAlink routines by Thom Henderson. Some of the ideas in this program
were blatantly stolen from Opus' Zmodem download driver and BinkleyTerm.
You have to thank the original authors for whatever quality is present in
this program. I merely glued the existing pieces together as a learning
project and to sink my teeth in some C code.
Many thanks to Doug Azzarito for scrutinizing the code. Also my thanks to
Heiko Rommelman for sending me the Proficient C book, which was the main
reason for me to start programming in C. Though my wife didn't understand
why I wanted to learn yet another programming language, I think it was
worth doing it :-)
"Backward? Yes. Compatible? Dunno."
<JT>