home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1993 #2
/
Image.iso
/
comm
/
sfcopy.zip
/
SFC.DOC
next >
Wrap
Text File
|
1993-06-11
|
44KB
|
1,186 lines
Serial File Copy
Version 2.1
Copyright (C) 1989 & 1990
By MarshallSoft
All rights are reserved.
MarshallSoft
PO Box 4543
Huntsville, AL. 35815
(205) 881-4630
page 1
TABLE OF CONTENTS
Chapter Page
------- ----
1.0 Introduction..................... 3
2.0 Summary of SFC Features.......... 3
3.0 Distribution Files............... 4
4.0 Purchasing a Null Modem Cable.... 4
5.0 Building a Null Modem Cable...... 5
6.0 Running SFC...................... 7
6.1 Startup Menu................ 7
6.2 Startup Problems............ 8
6.3 Status Window............... 9
6.4 Command Menu................ 10
6.5 Terminating SFC............. 11
7.0 Cloning SFC...................... 12
8.0 Support Programs................. 13
8.1 CLONE, GETSFC, and PUTSFC... 13
8.2 LOOPBACK.................... 13
8.3 TERMINAL.................... 13
8.4 MODEM....................... 13
8.5 PORTEXAM.................... 13
8.6 GETFILE and PUTFILE......... 14
8.7 CHECKCRC.................... 14
8.8 CRYPT....................... 14
8.9 SPACE....................... 14
9.0 Performance...................... 15
9.1 Test 1...................... 15
9.2 Test 2...................... 15
9.3 Test 3...................... 15
9.4 Other Tests..................15
10.0 CRC Calculations................. 16
11.0 User Registration................ 16
12.0 Revision History................. 17
13.0 Warranty......................... 18
14.0 Final Comments................... 18
page 2
1.0 Introduction
The Serial File Copy program SFC is designed to allow the
transfer of disk files ( including entire directories which may
themselves contain directories ) between any two IBM PC
compatible computers using standard RS232 serial ports. The SFC
program is particularly useful in copying files between IBM PC
compatibles with 5.25" disks and those with 3.5" disks such as
the IBM PS/2 and the various IBM PC compatible laptops. The
computers must both be IBM PC compatible ( this includes the
TANDY 1000 ) with 256 KB or more of RAM.
Both computers ( between which you want to transfer files ) must
have RS232 serial ports configured for use with a modem. COM1,
COM2, COM3 or COM4 may be used. Baud rate of 1200, 2400, 4800,
9600, 19200, or 38400 may be selected. Baud rates of 57600 and
115200 are available in the registered version.
There are only two differences between the shareware version and
the registered version of the SFC program. The first is that the
registered version can run at baud rates of 57600 and 115200
baud. The second is that the registered version does not have the
opening shareware screen.
2.0 Summary of SFC Features
o Supports COM1, COM2, COM3 and COM4.
o Supports baud rates from 1200 to 115200.
o Select groups of files with DOS wildcards ( eg: *.DOC )
o Select entire directories ( recursively ).
o Complete disk & transfer status on screen.
o On line help provided for all SFC commands.
o Option to send only files with a later timestamp.
o Load DOS Shell from within SFC.
o Full 16 bit CRC checksum is used.
o Bad file packets are automatically retransmitted.
o Change logged drive and path from within SFC.
o Display directories from within SFC.
o File date & time preserved after copying.
o Supports command line parameters.
o Supports batch file lists ( lists of files to send ).
o Option to send or skip any file from selected group.
o Can print files on remote computer.
page 3
3.0 Distribution Files
If a previous version of SFC is used to copy the distribution
files be sure to rename the older version ( eg: rename sfc.exe
sfc_old.exe ) so that there is no attempt to run the older
version with the newer version. The following files should be on
the SFC distribution disk:
SFC.EXE -- The executable Serial File Copy ( SFC ) program.
SFC.DOC -- This documentation file.
SFC.HLP -- File required for on-line help ( Type F1 for help ).
SFC.QRC -- Quick reference card.
SFC.INV -- Invoice ready to print.
SFCSW.EXE - Displays shareware screen for SFC.
Registered users are also provided with the following support
programs. None are necessary in order to run SFC, but are
provided as a "Thank You" for registering. For a description of
these programs see the sections on "Support Programs" and
"Cloning SFC".
CLONE.COM -- 'Clones' SFC on the target computer.
GETSFC.COM -- Created by CLONE on the target computer.
PUTSFC.COM -- Sends SFC to GETSFC on the target computer.
LOOPBACK.COM -- Performs loopback testing on specified port.
TERMINAL.COM -- Communications program with XMODEM & scripts.
TERMINAL.DOC -- TERMINAL documentation file.
MODEM.EXE -- Controls and displays modem control status.
PORTEXAM.EXE -- Displays all information about specified port.
GETFILE.COM -- Small file transfer program used with PUTFILE.
PUTFILE.COM -- Small file transfer program used with GETFILE.
CHECKCRC.EXE -- Computes the CRC for any file.
CRYPT.EXE -- Encrypts and decrypts any file.
SPACE.COM -- Displays free disk space and allocation units.
4.0 Purchasing a Null Modem Cable
A 'null modem cable' is necessary to connect the two computers
together using the RS232 ports ( the port used to talk to a modem
). A null modem cable can be purchased ready for use or can be
assembled by connecting a 'null modem adapter' to a normal RS232
modem cable.
Null modem adapters and cables can be purchased from several
sources such as Radio Shack and most electronics parts houses.
"Computer Shopper" regularly carries advertisements for null
modem adapters and cables. Be advised that not all null modem
adapters and cables connect all the lines that may be necessary.
Although all should work for SFC some may not work for the MSDOS
CTTY command which is used by the CLONE program.
Read the following section on building a null modem cable for a
discussion on cable requirements.
page 4
5.0 Building a Null Modem Cable
Building the null modem cable is easy. The only tricky part is
being absolutely positive that you have identified the correct
pins. Refer to the diagrams below as necessary. The pin numbering
is shown for the front of each connector, where the pins ( male )
or holes ( female ) are located. When viewed from the back side (
where the wires are soldered ) the pins and holes run in the
opposite direction. Soldering is recommended, although solderless
connectors which use crimp pins can be used instead. You can also
solder each wire to a crimp pin as its much easier than soldering
the wire directly onto the connector.
Male DB 25 Male DB 9
***************************************** *****************
* 1 2 3 4 5 6 7 8 9 10 11 12 13 * * 1 2 3 4 5 *
* 14 15 16 17 18 19 20 21 22 23 24 25 * * 6 7 8 9 *
*************************************** ***************
Female DB 25 Female DB 9
***************************************** *****************
* 13 12 11 10 9 8 7 6 5 4 3 2 1 * * 5 4 3 2 1 *
* 25 24 23 22 21 20 19 18 17 16 15 14 * * 9 8 7 6 *
*************************************** ***************
DB 25 DB 9 Pin Definition
===== ==== ==============
7 5 Signal Ground ( SG )
2 3 Transmit Data ( TX )
3 2 Receive Data ( RX )
20 4 Data Terminal Ready ( DTR )
6 6 Data Set Ready ( DSR )
4 7 Request to Send ( RTS )
5 8 Clear to Send ( CTS )
8 1 Carrier Detect ( CD )
SFC itself requires only signal ground (SG), transmit (TX), and
receive (RX) lines in order to operate. The first step is to
determine the type of connectors required. Examine the RS232
connectors on your computers. You will need to purchase
connectors that mate with the computers connectors. For example,
lets say that you have a laptop with a male DB 9 connector and a
desktop with a female DB 25 connector. Then you need a female DB
9 and a male DB 25 connector for your cable. IBM ATs and laptops
require a female DB 9 to mate while most XT class machines
require a female DB 25 to mate.
The DB 25 and DB 9 connectors can be purchased at most
electronics parts houses. Radio Shack also stocks both solder
type and solderless DB connectors.
Next you will need about 6 feet of ordinary 4-wire solid phone
cable, although any 3-wire cable of 24 to 20 gauge can be
page 5
substituted. If the CLONE program is to be used then 5 wires are
required. Up to 50 feet of cable can be used. Shielded cable is
even better but not necessary. Cable can be purchased by the foot
at most stores that sell it.
Once the connectors and cable have been purchased you are ready
to assemble your null modem cable. First connect the signal
ground ( SG ) line straight between connectors. Then connect
Transmit Data ( TX ) from one connector to Receive Data ( RX ) on
the other. If you wish to use the SFC cloning program CLONE you
must also connect Data Terminal Ready ( DTR ) from the end
connected to the computer running CLONE to Data Set Ready ( DSR )
on the other end. Some computers ( like my TANDY 3000 ) also
require you to connect Request To Send ( RTS ) from the end
connected to the computer running CLONE to Clear To Send ( CTS )
on the other end.
You then should have either 3 ( or 5 in order to use CLONE )
lines connected between connectors. Once completed, test the TX
and RX connections by running the TERMINAL ( or any terminal
emulator ) program on both sides. Whatever is typed on one side
is displayed on the other. Finally, test the remaining
connections by cloning SFC from one computer to the other.
Refer to the Pin Definition Table above in order to identify the
correct pins for your connector. When viewing the connector side
of both the DB 9 and DB 25 with the wide part at the top, the
pins are numbered left to right, top to bottom. Most connectors
have the pin numbers on the connector itself but are often
difficult to read because they are very small.
If you have never soldered before, you should use either
solderless connectors ( you crimp the wires on ) or find a friend
who has some experience soldering. Remember that soldering
doesn't have to be pretty in order to work. Practice a little
first with some spare wire if you are out of practice. When you
have completed construction of your null modem cable, verify that
the correct pins have been connected. If you cannot get SFC to
operate, then most likely you made a mistake in constructing your
cable.
page 6
6.0 Running SFC
Connect your PC compatible computers together with a null modem
cable between the RS232 ports ( the port used to talk to a modem
). Be sure that you are using a proper null modem cable rather
than a standard cable.
Normally, SFC can be started on both computers by typing 'SFC' on
each. This is referred to as the AUTOSYNC startup. On some
computers, AUTOSYNC will not work well. In this case, choose one
computer to be the MASTER and the other the SLAVE. It makes no
difference which is which. Start SFC on the MASTER by typing "SFC
M" followed by the ENTER key. Start SFC on the SLAVE by typing
"SFC S" followed by the ENTER key.
Additionally, both the COM port and the baud rate can be
specified on the command line by typing "SFC X Y Z" where X is A
for AUTOSYNC, M for MASTER or S for SLAVE; Y is 1 for COM1 to 4
for COM4; and Z is the baud rate ( 1200 to 115200 ). For example,
"SFC M 2 57600" will start up SFC on COM2 at 57600 baud as the
MASTER, and "SFC S 1" will start up SFC on COM1 at the default
baud rate as the SLAVE. If AUTOSYNC is specified on one side, it
must also be specified on the other. Any errors on the command
line are ignored and defaults are used.
6.1 Startup Menu
After startup, a menu will be displayed at the bottom of the
screen with 4 options. Use up and down arrow keys to move the
menu bar -- use ENTER to make selection. Note that on-line help
is available by typing function key 1 ( F1 ).
CONNECT: Attempts to connect to the other computer. The baud
rate must be the same on both computers.
SET BAUD: Allows the user to select the baud rate. 57600 baud
and 115200 baud are available only in the registered version.
Note that some 4.77 MHZ PC compatibles won't run at 115200
baud.
SET PORT: Allows the user to select the communications port,
COM1 to COM4. Of course, hardware must exist for the port
selected.
SET PRINTER: Allows the user to select the printer port, PRN1
or PRN2 for printing by the remote system.
QUIT: Quits and returns to MSDOS.
Set the port and/or baud rate on both computers if the default (
COM1 at 38400 in shareware version and 115200 in registered
version ) is not acceptable. Then select the CONNECT option. SFC
will now attempt connection to the other computer.
page 7
6.2 Startup Problems
If the message "Connection completed" is not displayed then the
computers are not talking to each other. The problem may be one
of the following:
(1) You must start SFC on both computers! SFC should be
started on both computers within one minute of each other.
(2) The wrong port is selected. For example, if SFC is told
to use COM1 but COM2 is actually connected to the cable.
(3) You may have selected different baud rates. They must
match! The default baud rate is 38400 for the shareware
version and 115200 for the registered version.
(4) The selected baud rate is too fast. Run at the fastest
processor speed possible ( for multi speed machines ) or
select a slower baud rate.
(5) You do not have a null modem cable connecting the two. A
normal cable ( without a null modem adapter ) will not work.
Test the null modem cable by running TERMINAL or any terminal
emulation program. Whatever is typed on one side is displayed
on the other. If this does not happen then you have a problem
with your null modem cable.
(6) One of the computers may be configured as DCE ( in order
to talk to a serial printer ) instead of DTE ( in order to
talk to a modem ). In this case, a normal cable ( instead of
a null modem cable ) will work.
(7) Your serial port is defective. This is unlikely.
Registered users can run LOOPBACK to test the port.
(8) COM1 & COM2 work but COM3 & COM4 don't. There are some
differences in the way COM3 and COM4 are set up among various
IBM compatibles. Use COM1 or COM2 instead. ( MSDOS should
place the address of the COM3 port at 40:0004 and COM4 at
40:0006 ).
(9) Your PC is not IBM hardware compatible! For example, the
TANDY 2000 is not hardware compatible with respect to the
serial ports.
If this is the first attempt to run SFC then use the manual mode:
Type "SFC M" on one computer and "SFC S" on the other. If you
still cannot get communication between computers, registered
users can call the technical support telephone number (205)
881-4630 after 5:00 PM CST Monday through Friday or Saturday
after 2:00 PM CST for assistance.
page 8
6.3 Status Window
The "Status" window contains information having to do with the
status of SFC. The definition of each field follows:
PORT: The Communications port ( COM1 to COM4 ) is displayed.
BAUD: The baud rate ( 1200 to 115200 ) is displayed.
UNIT: # bytes per allocation unit is displayed. Space for
disk files is always allocated as a multiple of this value.
DRIVE: The currently logged drive is displayed.
PATH: The current directory path is displayed.
MODE: Runtime mode is displayed.
"ready" -- Displayed when ready to accept keyboard input.
"MENU" -- Displayed after having selected a menu command.
"send" -- Displayed while sending files.
"receive" -- Displayed while receiving files.
FREE: Free disk space in bytes is displayed.
Three runtime options ( ASK, DIR, CHK ) are also displayed as
either "On" or "Off". All options can be toggled between "On" and
"Off" by use of the "Toggle Options" selection of the command
menu ( See section 6.4 ).
ASK: Asks the user for permission before sending each file.
Normally off. Typically selected when using wildcards in
specifying a range of files for which you wish to exclude
some files.
DIR: Enables sending of directories ( recursively ). Normally
on, toggle this off if you wish to ignore directories.
CHK: Send only files with a later date & time if file already
exists. Normally off, toggle this on if you want to do a
backup of more recently modified files. "...skipped..." is
displayed if the file is not copied because of the CHK
option.
Notes: (1) All options need only be set on the sending computer.
(2) Be sure that the clocks on your two computers are set to the
same date and time ( to within a few seconds ) if you plan on
using the CHK option.
page 9
6.4 Command Menu
The Command Menu contains the choices the user has once SFC has
connected. Use the up and down arrow keys to move the menu bar
and ENTER to make your selection. Once one of the choices is
selected, the user can return without SFC performing the selected
function by typing the ESC key. Type the F1 function key for
help.
QUIT: Quits SFC and returns to MSDOS.
SET CURRENT DRIVE: Changes the currently selected drive. The
user can "log onto" any legal DOS drive ( A, B, etc. ). If
you change diskettes then you must always select the SET
DRIVE option before continuing.
SET CURRENT PATH: Changes the currently selected path. When
this option is selected, a "Enter Path:" prompt is displayed.
The user then edits the current path which is displayed.
All paths must start with a backslash ( full path name ).
When the user is satisfied, typing ENTER will save the path.
Then MSDOS will attempt to change the "current" path. If
successful, the new path will be displayed in the "Status"
window.
DIRECTORY: Displays a directory of files requested. When this
option is selected, a "Enter files" prompt is displayed. The
user then types the file or files ( using the MSDOS wildcards
* and ? ). Filenames can be edited similarly to paths.
SEND FILE(S): Sends files to the other computer. No special
action is required on the receiving side except that both
sides must have previously selected CONNECT. The user will be
prompted for the filename in the same way as when "Directory"
was selected including the use of the MSDOS wildcards * and
?. If you specify that a directory is to be sent and the DIR
option is set to "On", then all files in that directory (
including other directories ) will be sent. In this way
entire directory structures can be copied. The date and time
for normal files ( but not directories ) will be preserved.
An indirect file can also be specified by prefixing the
filename by the '@' character. An indirect file is a standard
ASCII text file containing the list of files to be sent. The
indirect file must have been previously prepared and contain
one filename ( wildcards accepted ) per line. Indirect files
are typically used to specify a list of files that are
transferred on a regular basis.
page 10
REMOTE PRINT: Sends the specified file to the remote ( other
) computer for printing. No wildcards are allowed. The
printing can be canceled at any time by typing any key before
the normal end of the print job.
TOGGLE OPTIONS: Allows the user to toggle each of the three
runtime options ( ASK, DIR, and CHK ). The current setting is
always displayed in the status area. For a definition of the
runtime options, see SFC Status Window above.
DOS SHELL: Loads the DOS shell, allowing the user to execute
DOS commands. The user must be very careful not to execute
any command that changes the serial ports or modifies the
screen environment. Please note that many application
programs do change the screen environment. It is safer to
stay with the standard DOS commands unless a particular
executable has been previously tested.
When entering text in response to any of the above commands, type
ESC to return back to the main menu without selecting. The editor
starts in "Overstrike" mode ( each typed character overlays the
previous character ), but can be switched to "Insert" mode ( each
typed character is inserted at the cursor, shifting all
characters to the right over one space) by typing the INSERT key
( which toggles between Overstrike and Insert mode ). The DELETE
key deletes the character underneath the cursor. The END key
moves the cursor to the end of the string, while the HOME key
moves the cursor to the start of the string.
6.5 Terminating SFC
A series of files being transmitted can be terminated ( without
aborting the system ) by typing ESC during transmission. The user
will be returned to the SFC menu after the completion of the
current file transmission.
The user may break out of SFC at any time and return to MSDOS by
typing "CTRL" and "BREAK" simultaneously. This should only be
used when the program hangs for some reason and SFC does not
respond to the keyboard. Always try to use the menu selection
QUIT to quit SFC and return to MSDOS rather than Control Break.
SFC is bi-directional ( files can be sent in both directions ).
However, do not attempt to send files from one computer while you
are editing a path or filename on the other.
page 11
7.0 Cloning SFC
Registered users are provided with a 'cloning' capability for
SFC. This enables the user to get a copy of SFC on another
computer via a null modem cable. The only requirement is that the
receiving ( target ) computer have the standard MSDOS programs
MODE and DEBUG available in the currently logged directory. Also,
Data Set Ready ( DSR ) and ( for some computers ) Clear To Send (
CTS ) must be set to high on the target computer before the CTTY
command will work. See the section on null modem cables.
We first assume that the SFC programs are all available on one
computer ( we'll call it the source computer ) and that the other
computer ( we'll call it the target ) has only the standard MSDOS
programs DEBUG and MODE. In addition, we'll assume that a null
modem is connected between the two using port COM1 on both. The
task is to get SFC on the target computer.
The first step is to boot the target computer and then verify
that both DEBUG and MODE are in the currently logged directory.
Then type "MODE COM1:1200,N,8,2" to set the baud rate, parity,
and stop bits on the target computer.
The second step is to force DSR and CTS to high on the target
computer. This is required by the MSDOS CTTY command. If you have
a null modem cable in which DTR from the source computer is
connected to DSR on the target and RTS on the source computer is
connected to CTS on the target computer ( as described in the
cable construction section ) then the CLONE program will force
DSR and CTS high on the target computer.
The third ( optional ) step is to test step 2 by typing 'CTTY
COM1' on the target computer followed by typing 'MODE
COM1:1200,N,8,2' and then 'TERMINAL' on the source computer. Once
done, all commands typed on the keyboard of the source computer
will be executed by the target computer. Type "CTTY CON" on the
source computer. If control is then returned to the target
computer then we are ready for the next step. If the target
computer does not respond to commands typed on the source
computer then either the cable is not right or DSR and CTS are
not high on the target computer. Remember to type ESC to get out
of the TERMINAL program.
The fourth step is to type 'CLONE' on the source computer
followed by typing 'CTTY COM1' on the target computer. CLONE will
create the program GETSFC on the target computer. It takes about
a minute to run. Once done, CLONE breaks the connection between
the computers. Do a directory on the target computer and you
should now see the program GETSFC.COM.
The fifth and last step is to first run GETSFC on the target
computer followed by running PUTSFC on the source computer. Be
sure that SFC.EXE is in the same directory as PUTSFC. The process
takes about a minute and results in SFC.EXE being copied to the
target computer.
page 12
8.0 Support Programs
8.1 CLONE, PUTSFC, and PUTSFC.
Don't have SFC on the target computer ? The CLONE program
provides a way to 'clone' SFC onto another computer. The program
PUTSFC is used to send a copy of SFC to GETSFC which is created
by CLONE on the target computer. With CLONE you only need your
null modem cable to connect to computers with a different disk
format. See the section entitled "CLONING SFC" for a complete
discussion.
8.2 LOOPBACK
If you suspect that your serial port may be defective, then use
LOOPBACK to test the internal circuitry. The serial ports have a
built in 'loop back' test capability which is used by the
LOOPBACK program. For example, to test the COM1 port, type
'LOOPBACK 1'
8.3 TERMINAL
Looking for a small no frills communications program with XMODEM
file transfer protocol and a script command language ? TERMINAL
may be what you are looking for. Use TERMINAL to download files
from bulletin boards or to help test null modem cables. TERMINAL
is documented in the TERMINAL.DOC file.
8.4 MODEM
The MODEM program is used to turn the modem control lines DTR and
RTS on and off, and to display DTR, DSR, RTS, and CTS. MODEM can
help you test out your null modem cable. For example, to work
with COM3, type 'MODEM 3'. A menu will be displayed providing all
options.
8.5 PORTEXAM
The PORTEXAM program will tell you all you ever wanted to know
about the status of any serial port. It reports the serial port
address, the interrupt vector, the location of the ISR code, the
status of all modem control and modem status lines, and if the
serial interrupt is enabled. Very useful as a cable testing
program and for advanced users. For example, to examine COM1 type
'PORTEXAM 1'.
page 13
8.6 GETFILE and PUTFILE
GETFILE and PUTFILE are very small ( and fast to load ) programs
designed to send only a few files between computers when the
capabilities of SFC are not needed. They run at 38400 baud using
COM1 and do checksum data verification. Run GETFILE first on the
target computer followed by "PUTFILE filename" on the source
computer where 'filename' is the name of the file to be
transferred.
8.7 CHECKCRC
The CHECKCRC program is used to compute the Cyclic Redundancy
Check ( CRC ) of any file ( sort of a 16-bit file 'fingerprint'
). For example, to compute the CRC of all files ending with the
extension .DOC type 'CHECKCRC *.DOC'. Use the CHECKCRC program to
verify that two copies of the same file are indeed the same file.
8.8 CRYPT
Need to protect your data ? The CRYPT program is used to encrypt
and decrypt any file. To use, type 'CRYPT filename1 filename2
key' and the file 'filename1' will be encryted to produce
'filename2' using the numeric key 'key'. If 'key' is not
specified then you will be prompted for it. The same key performs
both encryption and decryption. For example 'CRYPT MYFILE.C
MYFILE.X 123' will encrypt MYFILE.C using the key 123 and create
file 'MYFILE.X'. To decrypt, repeat the process using the same
key: 'CRYPT MYFILE.X MYFILE.C 123'.
8.9 SPACE
Need a quick and easy way to determine how much free disk space
is available ? Use the SPACE program to display the remaining
free disk space and the allocation unit size of the specfied
disk. For example, type 'SPACE C' to display free space on drive
C.
page 14
9.0 Performance
The following benchmark results were obtained using a Tandy 1000
( 4.77 MHZ), a Tandy 1400LT ( 4.77 & 9.16 MHZ ), and a Tandy 3000
( 10 MHZ ) computer. Note that the 'standard' IBM PC runs at 4.77
MHZ. Virtual disks ( ramdisks ) were used in order to measure
performance as independent of disk speed as possible. The use of
hard disks will result in a little slower times than shown while
the use of floppy disks will result in slower times still. The
use of faster computers will result in faster times than shown.
Three files were used: file A is 10,000 bytes long, file B is
50,000 bytes and file C is 100,000 bytes long. All times are in
seconds and are from start to finish including ramdisk access.
Your results should be very similiar.
9.1 Test 1 ( 10 MHZ Tandy 3000 to 4.77 MHZ Tandy 1000 )
baud rate File A File B File C
--------- ------ ------ ------
38400 4.0 16.5 32.3
115200 2.2 9.8 14.7
9.2 Test 2 ( 10 MHZ Tandy 3000 to 4.77 MHZ Tandy 1400LT )
baud rate File A File B File C
--------- ------ ------ ------
38400 3.3 15.3 30.3
115200 1.6 6.7 12.7
9.3 Test 3 ( 9.16 MHZ Tandy 1400LT to 10 MHZ Tandy 3000 )
baud rate File A File B File C
--------- ------ ------ ------
115200 1.5 6.1 12.1
9.4 Other Tests
Serial File Copy has been benchmarked against several other
shareware programs. All that we have tried ( 3 ) are slower when
using the same baud rate. One program took almost twice as long
to transfer files. If anyone finds a faster file transfer utility
than SFC please write or call!
page 15
10.0 CRC Calculations
A full 16 bit Cyclic Redundancy Check ( CRC ) using the CCITT (
The Consultative Committee in International Telegraphy and
Telephony ) polynomial is used by SFC. The CRC of each file is
computed before transmission by the sender and sent along with
the file being transmitted. The receiver then computes the CRC of
the received file and compares it to the CRC sent. If the CRCs
match, then the file is considered to be correct and a "OK" is
displayed. CRC calculations are considered to be the best
available method for verifing data integrity. They are much
superior to checksums and detect 99.99 percent of data errors. If
an error is detected, the offending packet ( part of the file )
will be re-transmitted up to 3 times.
11.0 User Registration
The shareware version of SFC is provided so that you may
personally determine the usefulness of SFC for yourself. If you
can use SFC please register your use with us.
MarshallSoft
P.O. Box 4543
Huntsville, AL.
35815-4543
Please pay by check. Payment must accompany purchase orders.
Print the file SFC.INV if an invoice is needed. Two packages are
available. The "Personal Package" is available for $15 postpaid
and includes:
o High Speed Version - 115200 baud. No shareware screens.
o All 12 support programs - See 'Support Programs' section.
o Notices of upgrades and related products.
o A dozen of my favorite public domain & shareware utilities.
The "Business Package" is available for $25 postpaid and includes all
of the Personal Package plus:
o Telephone support for 1 year.
o 1/2 off all future releases of SFC.
o Backbone bound printed Users Manual.
The registered user will receive the latest version by return mail. A
720 KB 3.5" diskette is provided ( unless a 5.25" is requested )
page 16
12.0 Revision History
Version 1.0 -- 10 April 1989 -- Original release
Version 1.1 -- 30 July 1989
Added ASK option.
Added CHK option.
Moved DIR option from separate menu item to options menu.
Fixed bug in disk file size reporting.
Changed units of FREE from kilobytes to bytes.
Changed internal parameters for easier synchronization.
Increased PATH length from 58 to a full 64 characters.
SLAVE side must start SFC with "SFC /S".
Could not generate backslash on Tandy 1000.
Version 1.2 -- 16 October 1989 ( no shareware version )
Added a new AUTOSYNC mode as well as manual startup mode.
Added help file support.
Greatly expanded documention file.
Version 1.3 -- 1 November 1989 ( no shareware version )
Fixed problem with port COM2.
Support the port and baud rate specified on command line.
Simplified operation of AUTOSYNC.
Added indirect file ( '@' file ) support.
Added support for COM3 and COM4.
Version 2.0 -- 10 November 1989
Internal change to allow 4.77 MHZ PCs to run at 115200.
Allows transfer of read only files.
Version 2.1 -- 16 February 1990
Added DOS Shell menu option.
Modified AUTOSYNC for increased reliability.
Increased buffer size to 2000 bytes for 57600 & 115200 baud.
Provide cloning program and other supporting programs.
Added ability to do remote printing.
'NO RESPONSE' error does not abort system.
page 17
13.0 Warranty
The user of this software assumes all liability for its use. In
no case shall MarshallSoft be liable for any damages, including
any incidental or consequential damages. The prudent user will
keep multiple backups of all important programs and data.
14.0 Final Comments
An update to SFC is planned about twice a year for the next
several years. It is amazing that as one gets into programming
something like SFC new ideas are constantly occurring. Future
upgrades will add new features, make SFC easier to use, make SFC
faster, add new supporting programs, or enhance the
documentation.
If you find any errors or have any suggestions for improvement
please write or call (205) 881-4630 after 5:00 PM CST Monday
through Friday or after 2:00 PM Saturday.
Consulting services for serial communications projects are
available. If you have a project in mind, write or give me a
call. I may very likely already have something close to what you
need.
Thanks for trying out SERIAL FILE COPY. I hope that SFC will meet
your expectations. --- Mike Marshall ( Author ).
page 18