home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-385-Vol-1of3.iso
/
t
/
tickdupe.zip
/
TICKDUPE.DOC
< prev
next >
Wrap
Text File
|
1991-06-08
|
4KB
|
90 lines
TickDupe.Doc 06/03/91
TickDupe v1.00
FraggleWare
In the legal sense this Software will actually only reside on magnetic
media. No warranties are implied or expressed by the author, his family
or any of his friends.
We do however _hope_ you find it useful and in the spirit of FTSC Networks
and the Telecommunications Community we are giving this program away. Gawd,
with a price like that -- you can't loose. :)
You actually don't have to be a fraggle to use Fraggle ware ...Just thought
you'd like to know that.
Let me get right to the point and Say that This program is not recommended
for Major Hubs who should have only one File Echo per directory anyway But
If you are an end system and perhaps deposit more than one file echo in a
download directory or move uploaded files to that directory this may be the
program you've been waiting for. And like me, now maybe you won't be so
tired at work :)
TickDupe is a rather Simple utility which can help you as a SysOp (End
Receiver) of File Echoes actually match your download directory with your
Tick STOPDUP Files. Simply put Tick creates a Dupe file in your STOPDUP
directory which matches the flow of files from a particular File Echo. For
example; in SOFTDIST your Dupe file is SOFTDIST.DUP (in your STOPDUP
directory).
Often we have cases of where we point File Echoes to a directory which is
already inhabited by files we carefully placed there. If you are like me
and do not run Tick with Dupe by CRC you want all the file names in the
DUPE file, cause sure enough, one night, the one you do not have a copy of
will get overwritten (or at least you feel that way). TickDupe will match
the File Echo Tag Dupe file with the directory it points to. i.e. If your
Tic.Cfg says, you get SDSRA in your D:\Files\RA directory, TickDupe
(when run) will make the SDSRA.DUP include every file in that directory.
Very simple -- TickDupe reads your Tic.Cfg for the location of your STOPDUP
files and reads every File Echo Tag and matches up the contents of your
directory with the StopDup files. The files may get a tad bigger but not
much (Actually the School BBS here gets approximately 100 file echoes and
the space the additional "protection" takes up is very little considering
the alternatives). I would say it is fairly fast also -- It can be run in
an event from a batch file (If you are like me, you are always diddling in
the file areas and want them to match up).
We realize there are many more features which are present in Tick (our
extreme thanks the Author Barry Geller) which TickDupe does not address.
For instance the CRC (if you have CRC enabled Tick will place a CRC beside
the file name) ...Well perhaps we will address some of this in the future
...We are open to suggestions...
The Director and Founder of Fraggleware:
TickDupe.Exe By Stan Bimson 1:116/32
And The Writer of these here Doc:
(all credit for bad grammar, no punctuation, run on sentences
and mis speltings go to this fellow <smile>.
TickDupe.Doc by Kevin Snively 1:116/29 & 1:116/24
Two SysOps who work together perhaps as close as Boyce and Hart, Rogers and
Hammerstien, Bert and Earnie ...Though, I doubt you would actually recognize
them if they were out in public together.
- Anonymous
p.s. (by author) Command syntax: TICKDUPE <enter> except as noted
TICKDUPE will find your TIC.CFG in the same manner
that TICK does and that is in the following order:
1) Checks the command line first for the switch
/c[d:][path]filename.ext
2) Checks for the environment statement
set tic=[d:][path]filename.ext
3) Checks the current directory for TIC.CFG