Copyright 1991-Steve Lewis
Please note that starting with Version 5.0, JBATCH.COM and JBA.COM
are used for Jmodem file transfers, rather than JMODEM.COM. If you've
been using earlier versions of TRANSFER, you must update your protocol
library by obtaining these two files.
Version 5.6 fixes the problem with Versions 5.0 through 5.5, whereby
JMODEM/Batch (#8) tries to upload in the manual mode, without pausing for
the filename(s) to be entered.
Version 5.6, when REGISTERED, checks all filenames (paths included), when
uploading in the manual mode. If a file is not found, the user will be
prompted to re-enter the filename. If uploading is from a floppy drive,
user is prompted if drive door is open.
Note also that TRANSFER may be used with the new GSZ.EXE and GSZ.COM
programs. To use these programs, simply rename them DSZ.EXE or DSZ.COM.
Version 5.6 of TRANSFER is distributed in its NONREGISTERED state. By
registering TRANSFER, you will receive a file named "AUTHORIZ". This
file contains your personal serial number and checksum, and when present in
the SAME directory as TRANSFER, it will UNLOCK the SPECIAL features of
Version 5.6. Your copy of AUTHORIZ will be compatible with ALL future
versions of TRANSFER. You will NOT need to purchase AUTHORIZ again!
These special features are;
(1) May be configured for a FIXED PROTOCOL, thus
eliminating the need to manually select the protocol.
(2) May be configured for "Hotkeys", eliminating
the necessity for carriage returns whenever
(3) When configured for BOTH the program-selectable protocol
AND the "Hotkeys" modes, a carriage return entered
in response to a question returns the user to the "Enter
protocol" line of text, permitting the user to re-enter
the protocol number.
********* NEW! (4) When MANUALLY entering a filename for uploading, it is
checked to make sure that it actually exists. If it
doesn't exist, the user is prompted to re-enter the
filename. If uploading is from a floppy drive, then
user is prompted if drive door is open.
Version 5.6 of TRANSCFG.EXE prompts for the additional information, but
UNREGISTERED versions will NOT be able to take advantage of this information.
Future versions of TRANSFER will have MANY more SPECIAL features!
Version 5.6 corrects a defect in earlier versions that permitted other than
integral values to be entered for the protocol number. Additionally,
Version 5.6 does not permit the entering of a blank line for the filename.
When batch uploading with the MEGALINK protocol, A-L-L filenames MUST be
from the S-A-M-E directory! The directory of the FIRST filename MUST be the
directory for ALL the others. This limitation is due to the MLINK.EXE
PROTOCOL, and is NOT due to the "TRANSFER.EXE" program.
When changing versions of TRANSFER.EXE, A-L-W-A-Y-S change the following
files as well;
..... BECAUSE THEY MAY DIFFER FROM THOSE
PACKED WITH THE PREVIOUS VERSION OF
When installing a new version of TRANSFER, always RE-CONFIGURE with the
latest TRANSCFG.EXE program!
TRANSFER was written primarily as a file transfer shell for a communications
program. If you are using PCPLUS, configure PCPLUS so you can shell out
to TRANSFER by using the J or U keys.
TRANSFER can be used in the MODEM mode, or in the DIRECT mode by using a
"Null Modem" cable. In the MODEM mode, TRANSFER assumes that communications
have already been established by the communications program, therefore,
neither the modem nor COM port are initialized. In the DIRECT mode, the COM
port is initialized to the communications speed specified in the configuration
routine, and in addition is set to 8 data bits, 1 stop bit, and no parity.
After exiting TRANSFER in the DIRECT mode, you may want to manually reset
your COM port.
The following transfer protocols are supported by TRANSFER;
(1) Xmodem/CHK SUM
(3) Ymodem/(1K Xmodem)
(8) Jmodem/Batch (NOW TRUE BATCH!)
(9) Zmodem/Batch (Z-MODEM 90)
(23) Tasy/Batch (REGISTRATION REQUIRED!)
XFR56.ZIP contains five files;
On some Bulletin Boards, the files may be contained in XFR56.LZH,
XFR56.ARC, or XFR56.PAK.
TRANSFER.EXE requires the following files to operate;
DSZ.COM (or DSZ.EXE) * (Required for Protocols #4-#6, #9) See par. 2
SUPERK.COM * (Required for Protocols #1-#3, #10-#19)
SUPERK.000 * (Comes w/SUPERK.COM) (Required for Protocols #1-#3, #10-#19)
JBATCH.COM * (Required for Protocols #7, #8)
JBA.COM * (Required for Protocols #7, #8)
TMODEM.EXE * (Required for Protocol #20)
PUMA.EXE * (Required for Protocol #21)
NMODEM.EXE * (Required for Protocol #22)
TASY.EXE * (Required for Protocol #23) *(REGISTRATION REQUIRED)
CMODEM.EXE * (Comes w/SUPERK.COM) (Required for Protocols #16, #17)
MLINK.EXE * (Required for Protocol #24)
HYPERP.EXE * (Required for Protocols #25, #26)
TRANSFER.BAT (Created by TRANSCFG.EXE)
TRANSFER.CFG (Created by TRANSCFG.EXE)
MODE.COM * (DOS file-Resides in DOS directory)
BATCHFLE (Optional. Created by MAKBATCH.EXE)
AUTHORIZ (Optional. Needed to unlock special features)
The TRANSFER.EXE program needs to be able to locate the TRANSFER.CFG file
in order to operate. TRANSCFG.EXE automatically creates a batch file named
TRANSFER.BAT, and places it in the root directory. This batch file
automatically changes the drive and directory to the location of the
TRANSFER.EXE and TRANSFER.CFG files, which must exist in the SAME directory.
All the transfer protocol files may exist in ONE separate directory. If
SUPERK.COM and SUPERK.000 do not exist in the same directory as TRANSFER,
then SUPERK.COM must be configured so that it can find its overlay file,
SUPERK.000. To do this, type SUPERK @, which will bring SUPERK into the
Configuration Mode, and then specify both the "wrkpath" to SUPERK.COM and the
"Ovlpath" to SUPERK.000. They must BOTH be set to point to the directory where
the SUPERK and other protocol files reside. If the directory is named "FILES",
then SUPERK expects the two paths to be shown in the following format;
Note that when running TRANSCFG.EXE, the path to the above directory
must be entered in the following format;
C:\FILES (NO ending backslash!!!)
The same rule applies to JBATCH.COM, which must be able to locate the JBA.COM
file. Type JBATCH @, and specify the path to JBA.COM using the same format
NOTE:To take FULL advantage of the features of the user-supplied protocol
files, ALWAYS use REGISTERED versions of these files!!!!!!!
UNREGISTERED versions of NMODEM will N-O-T support file transfers
outside of the directory that NMODEM resides in!
UNREGISTERED versions of TMODEM do NOT support batch downloading of
more than ONE file. If you requst more than one file, only the first
file requested will be sent!
Later versions of the PUMA protocol have been renamed "MPT.EXE", rather
than "PUMA.EXE". To use these later versions, simply rename the
"MPT.EXE" FILE as PUMA.EXE".
When uploading in Cmodem, if the file is located in the root directory,
it must be entered as;
Yes, TWO backslashes are used!
If however, the file is located in the directory C:\TEST\, then it must be
A-L-W-A-Y-S READ THE DOCUMENTATION FOR THE PROTOCOL DRIVER YOU ARE USING,
IN ORDER TO KNOW ITS LIMITATIONS!
The TRANSFER.CFG file is created by using the TRANSCFG.EXE configuration
program. To run the program, simply type "TRANSCFG" and enter the requested
information. The configuration program creates the configuration file, named
TRANSFER.CFG, which MUST be present for TRANSFER to operate, as well as
TRANSFER.BAT, which is placed in the root directory of the drive where the
TRANSFER files reside.
If the download directory is named FILES, and is a subdirectory of a directory
named PCPLUS, it should be entered in the TRANSCFG program as;
If the DOWNLOAD directory is a subdirectory of the root directory, it
should be entered as;
If the DOWNLOAD directory is the root directory, simply enter the drive
letter followed by a colon;
Do NOT enter it as;
The above rules also apply for specifying the location of the protocol files,
and the location of the TRANSFER files.
************** IMPORTANT **************
TRANSFER.EXE WILL AUTOMATICALLY CHECK FOR THE PRESENCE OF THE NECESSARY
PROTOCOL FILES. IT WILL CHECK FOR BOTH THE COM AND EXE VERSIONS OF THE SAME
FILES. IT WILL ALSO CHECK FOR NECESSARY SUPPORTING FILES. IF THE REQUIRED
FILES FOR A GIVEN PROTOCOL ARE NOT PRESENT IN THE DIRECTORY INDICATED IN THE
CONFIGURATION FILE, THEN THE LISTING OF THAT PROTOCOL IN THE MENU WILL BE
BLANKED-OUT! KEEP IN MIND THAT IF AN ATTEMPT IS MADE TO SELECT ANY OF THE
LOCKED-OUT PROTOCOLS, A MESSAGE WILL APPEAR, INFORMING THE USER THAT THE
REQUIRED FILES ARE NOT PRESENT IN THE SPECIFIED DIRECTORY, AND TRANSFER WILL
If it is desired to operate in the "TEXTFILE" mode, listing files to be
uploaded in a textfile named BATCHFLE, then BATCHFLE needs to be created by
running the MAKBATCH.EXE program. To run this program, simply type "MAKBATCH"
and follow the instructions. This will AUTOMATICALLY cause the file BATCHFLE to
be created, conforming to the following format;
*** (The 3 asterisks denote the END of the list)
If TRANSFER is configured to operate in the "TEXTFILE" mode, rather than the
"MANUAL" mode, then if a batch protocol is chosen and (U)pload is selected,
file transfer will AUTOMATICALLY proceed, the files being chosen from the
listing in BATCHFLE.
Written by Steve Lewis for the IBM PC using DOS 2.0 or
later, including DOS 5.0
TRANSFER is supplied for personal, private use. Feel free to
distribute TRANSFER given these restrictions:
o the program shall be supplied in its original,
unmodified form, which includes this documentation;
o no fee is charged.
o commercial use is prohibited, except when operated with
a legal copy of AUTHORIZ.
o the program may not be included - or bundled - with
other goods or services. Exceptions may be granted
upon written request only.
If you are using TRANSFER and find it of value, you are urged
to register it by sending $15 to the address shown below. In return
you will receive a copy of AUTHORIZ, containing your personal serial
number. An order form, entitled "MAILER", is enclosed for your
Please make checks payable to:
405 South Sunnyvale Ave.
Sunnyvale, CA 94086
Voice: (415) 469-6854