home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
UPCHECK
/
H_RUCK10.ZIP
/
H-RUCK.DOC
< prev
next >
Wrap
Text File
|
1993-11-03
|
8KB
|
227 lines
H-Ruck, Hack Report Upload Checker, Copyright 1993, Maritime Computer Services
The "Hack Report," is of course, the one and only Hack Report,
created monthly by Lee Jackson and the FidoNet International Echos
Shareware and Warnings (1:124/4007). A special thanks to Lee Jackson
and the rest of the Hack Squad for providing us with this invaluable
service, of which makes this program possible.
I created the program out of personal need for my board, and
that is mainly to protect myself and my users from dangerous files. I
searched for a program to do what this one does, but was unable to find
one suitable for PCBoard. There are hack searchers and hack mergers,
but not a hack report upload checker...until now. ;-)
OK, down and dirty-
Files that you should have in this archive:
H-RUCK.EXE The program executable
H-RUCK.DOC This file
H-RUCK.CNF Configuration File
HISTORY.DOC Version history
FILE_ID.DIZ Description file
ORDER.FRM Order form for registration
PCBTEST.BAT Sample PCB batch file
UPGRADE.DOC How to upgrade from previous version
Files you will need:
The most recent version of the Hack Report. The file
name convention of the archive is HACK9308.ZIP.
YRMO
(YearMonth)
Specifically, you will need the HACK92FA.IDX file, and
until 1994, will probably want the HACK9308.COL file. When it
becomes obsolete, H-Ruck is ready for that too.
General Overview: (Details to come later)
1. Ensure that PCBoard is set to test uploads. If you already
test uploads, don't worry about it. If not, it's a switch
in PCBSetup.
2. You will need to alter your PCBTEST.BAT file, the batch
file that PCB uses to execute any upload testing. There
is a sample PCBTEST.BAT included that shows how to use it
with Ziplab, a GREAT upload checker by Jeff Morley.
3. You will need to create a seperate directory for H-Ruck.
4. You will need to customize the Configuration file.
5. You will need to send me money, so you can get rid of that
nasty UNREGISTERED and 10 second pause. (grin)
Steps to setting it up: (It's really quite easy)
1. Make a directory for H-Ruck. I suggest :\PCB\HRUCK , but
you can put it anywhere you like.
2. Take a look at your PCBTEST.BAT file. Take a look at my
PCBTEST.BAT file. This is the part where system differences
come in to play. Hopefully, since you are a sysop, you are
fairly familiar with batch files. If you know anything
about errorlevels, thats even better. If you don't, not to
worry, you can still set this up. Here are a few facts you
need to know:
In the PCBTEST.BAT file, PCBoard passes the following
parameters:
%1 the filename
%2 the word UPLOAD or the word TEST
The only time %2 will not be UPLOAD is when a user invokes
the Test command from PCBoard.
The following errorlevels are used by H-Ruck:
errorlevel 95 means the file PASSED
errorlevel 1 means the file FAILED
When H-Ruck is invoked from the PCBTEST batch file, it
uses the following command line:
Drive\Path\H-RUCK.EXE Drive\Path\H-RUCK.CNF %1 %2
For example, if H-Ruck is in the c:\pcb\h-ruck directory:
c:\pcb\h-ruck\h-ruck.exe c:\pcb\h-ruck\.cnf %1 %2
Based on the above, here is a sample PCBTEST.BAT to run
H-Ruck along with Ziplab:
@echo off
c:\pcb\h-ruck\h-ruck c:\pcb\h-ruck\h-ruck.cnf %1 %2
if errorlevel == 95 goto ziplab
if errorlevel == 1 goto end
goto end
:ziplab
c:\ziplab\zlab.exe %1 c:\pcb c:\ziplab %2
:end
cd c:\pcb
if exist h-ruck.txt copy h-ruck.txt pcbpass.txt > nul
if exist h-ruck.txt del h-ruck.txt > nul
*************The last 3 lines are new! They MUST now be added!*************
Now, if errorlevel is 95, meaning the file passed, it now is
sent to Ziplab (or your checker of choice). If it fails, it skips to
the end, since there is no need for ZipLab to look at it. In fact, do
NOT let another checker look at it if it already failed (errorlevel 1).
3. All you have to do is modify the 7 line CNF file, which is
self-documented, BTW.
Line 1: Put your BBS name here
Line 2: Put Your name here
Line 3: Put your registration code here.
If unregistered, leave it as 0.
Line 4: Put your main pcb directory here.
(ex. c:\pcb )
Line 5: Put the H-Ruck directory name here.
This would be the one you just made.
(ex. c:\pcb\h-ruck )
Line 6: Put the name of the Hack Report IDX
file here. Not the path, just the name.
(ex. HACK92FA.IDX )
Line 7: You have a choice. Either put the name
of the Hack Report COL file here,
(ex. HACK9308.COL ) or if you choose
not to use it put the word NONE in all
caps. Soon enough you will be forced
to do this since it is being discontinued.
4. You must put the IDX file and the COL file in the H-ruck
directory. Let me repeat, ALL of the files in this archive
must be in the H-Ruck directory AND the IDX file AND the COL
file (if that one is used).
Of course, you will want to replace these files as they are
updated by the Hack Squad, and when you do, REMEMBER to change
the NAMES in the CONFIGURATION file (H-RUCK.CNF).
5. You're done. Just test it yourself before opening it up to
the masses.
This program is fully functional and not crippled in any way. I only ask
that if you use it, please register it. H-Ruck is shareware, not freeware.
Registration is ONLY $10.00 (US) - help support shareware authors!
Registration will also give you extended access to our support BBS, and
free upgrades of newer versions - and there will be newer versions with
more functions.
The Glazer's Guild BBS
(804) 739-9315
Maritime Computer Services
PO Box 1846
Midlothian, VA 23113
To register, please send check or money order to the above address. You
will receive access to the Guild, and free updates for new versions.
Please include the program name, version number, along with your pertinent
information : (name, address, phone, etc.). Please use the order form,
ORDER.FRM for faster processing on your registration.
*** Registration will remove the 10 second delay and will remove the
*** UNREGISTERED message and replace it with your Board Name.
DISCLAIMER:
We ("Maritime Computer" or "Michael W. Graham") are not responsible
for any damages of any kind, including profit losses and data losses,
that relate directly or indirectly to these programs and files.
You may distribute this program, as long as it is in unmodified form
with all the files originally included. Do not "reverse engineer" or
unassemble this program.
This program and associated files may not be distributed for a fee
without express written consent from the author.