|Very nice file transfer protocol manager for Procom, Telix etc.|
|File Name||File Size||Zip Size||Zip Type|
Download File XFER47.ZIP Here
Contents of the TRANSFER.DOC file
Copyright 1991-Steve Lewis
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 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
Version 4.7 of TRANSFER is configured with the NEW Version 4.1 of TRANSCFG.EXE.
If you are updating your version of TRANSFER (Version 4.4 and below), be sure
that you re-configure TRANSFER with this latest version of TRANSCFG.EXE or
your screen will ALWAYS be in the MONOCHROME mode! If you're already
configured for Version 4.5 of TRANSFER.EXE, it's not necessary to re-configure,
as the only difference between Versions 4.0 and 4.1 of TRANSCFG.EXE is
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
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)
(9) Zmodem/Batch (NEW Zmodem-90)
XFER47.ZIP contains four files;
On some Bulletin Boards, the files may be contained in XFER47.LZH or
TRANSFER.EXE requires the following files to operate;
DSZ.COM (or DSZ.EXE) * (Required for Protocols #4-#6, #9)
SUPERK.COM * (Required for Protocols #1-#3, #10-#19)
SUPERK.000 * (Comes w/SUPERK.COM) (Required for Protocols #1-#3, #10-#19)
JMODEM.COM (or JMODEM.EXE) * (Required for Protocols #7, #8)
TMODEM.EXE * (Required for Protocol #20)
PUMA.EXE * (Required for Protocol #21)
NMODEM.EXE * (Required for Protocols #22, #23)
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)
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!!!)
NOTE:TO TAKE FULL ADVANTAGE OF THE FEATURES OF THE USER-SUPPLIED PROTOCOL
PROGRAMS, ALWAYS USE REGISTERED VERSIONS OF THESE PROGRAMS!!!!!!!
UNREGISTERED VERSIONS OF NMODEM WILL N-O-T SUPPORT FILE TRANSFERS
OUTSIDE OF THE DIRECTORY THAT NMODEM RESIDES IN!
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; "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 "FILENAME" were located in the directory C:\TEST\ , then you would
specify it as;
A-L-W-A-Y-S READ THE DOCUMENTATION FOR THE PROTOCOL DRIVER YOU ARE USING,
IN ORDER TO KNOW ITS LIMITATIONS!
The reason why JMODEM.COM, rather than SUPERK.COM is used for Jmodem file
transfers is because the writer of TRANSFER has been unable to get
SUPERK.COM to operate properly in the Jmodem mode.
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;
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 4.01
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.
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, your gift in
any amount ($15 suggested) will be greatly appreciated.
Makes checks payable to:
405 South Sunnyvale Ave.
Sunnyvale, CA 94086
Voice: (415) 469-6604
December 27, 2017 Add comments