Full Description of File
Graphical, multi-tasking compliant,
replacement for DOS' copy command.
Accepts the @ directive, thus may
be used as an "External batch protocol" on
local nodes of BBS systems. Progress status
bars, multi-disk copies, etc...
Contents of the MEGACOPY.DOC file
A Multi-tasking "Copy" File Utility
What is Mega-Copy ?
Mega-Copy was designed to be used as a "Local" file transfer
protocol for multi-node Searchlight BBS systems, but works
fine from the DOS command-line, and should work fine for any
BBS that can use external protocols such as DSZ.
Why Mega-Copy ?
Mega-Copy was written to be used on our BBS as an alternative to
the DOS copy command for 2 reasons:
1) DOS' copy command would slow the BBS down to a crawl anytime
we tried to copy files to a floppy drive.
2) Most of the files we copied to floppies where from our files
section, either for users that stopped by, or for us to use/
test on another system. Though I have searched, I was unable
to find a replacement copy command that would accept the
@ directive - as used by batch file transfer protocols,
such a Zmodem. Thus requiring opening a DOS window any time
we wanted to copy multiple files to a floppy from the BBS -
A lot more difficult than tagging files .
What can Mega-Copy do, that DOS' copy can't ?
Graphical user interface.
Mega-Copy will attempt to detect any of the following
multi-tasking operating environments:
OS/2 (DOS Box)
If such an environment is found, Mega-Copy will use a small
4k buffer, for uploading/downloading (copying) files, in the
1) Read 4k of the source file into the buffer.
2) Write the 4k buffer to the destination file.
3) Pass 6 time-slices to the OS environment.
4) Repeat until the file is copied.
5) Repeat until all queued files copied.
If you are running under DOS, with no multi-tasking environment,
Mega-Copy will use a larger 64k buffer, and skip the above time-
slice routines - copying at about the same speed as DOS' copy
Mega-Copy can be used as an external protocol on any BBS system
that allows such. If used on a "Local Only" node, it will be
invisible to remote callers. Any BBS that uses DSZ or a like
protocol engine for batch uploading and downloading should create
a temporary "batch queue" file - a file that lists each file to be
transferred, one file per line.
Mega-Copy will accept this "batch queue" as a command-line argument.
Multi-Disk file copies:
If you queue more files than will fit on your destination drive,
Mega-Copy will prompt you to replace your disk prior to starting
the copy procedure on the file that would exceed the disk's capacity.
Mega-Copy will accept the "*" and "?" wildcards as part of the
file spec of any/all files being copied. The wildcards may be
in the "queue list" or on the command-line.
MC [@] [d:][path]
ex. mc @tempfile.txt a:\
Would copy all files listed in "TEMPFILE.TXT" to the root
of drive a:
ex. mc a:\*.*
Would copy all files from A: drives root directory to the
Searchlight Sysops :
To run Mega-Copy as a "Local" protocol on your Searchlight
multi-node BBS, run CONFIG.EXE from your local node's home
directory, select "A. General Configuration", then select
"E. Xfer Protocols Setup".
Either select an empty spot, or replace a current protocol
with the following:
Searchlight BBS External Protocols Setup Menu
1. Protocol Name ................. Mega-Copy A:
2. Protocol Type ................. External
3. External Send Command ......... c:\utils\mc.exe @d:\NODEx\tempfile
4. External Receive Command ...... c:\utils\mc.exe a:%F
Line 1: This is optional