home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
BBS_UTIL
/
BM0406_A.ZIP
/
DOCS.ZIP
/
BTCH174.DOC
< prev
next >
Wrap
Text File
|
1993-03-30
|
19KB
|
378 lines
BU174v54.ZIP
(c) 1992,1993 by Richie Molinell
Date: 05/15/92 - - for RBBS v17.3c - BTCH173C
Date: 06/27/92 - v1.0 - for RBBS v17.4
Date: 07/27/92 - v2.0 - for RBBS v17.4 - complete revamp - see notes *
Date: 07/31/92 - v3.0 - not released to public - "/HS" switch for bidirectional
transfer installed
Date: 08/02/92 - v3.1 - not released to public
Date: 08/04/92 - v3.2 - not released to public
Date: 08/28/92 - v3.3 - had bug with dropped carriers
Date: 08/29/92 - v3.4 - All commands from command line - BiDirectional Transfer
determined by protocol selected!
Date: 08/30/92 - v3.5 - fix for DSZ and lower case file names
Date: 10/15/92 - v3.6 - fix for AutoLogoff with BiDirectional Transfer
Date: 10/24/92 - v3.7 - fix for local upload/abort,categorizing and ext desc
Date: 10/28/92 - v4.0 - fix for v3.7 & DIZ support
Date: 11/08/92 - v4.1 - fix for Personal files stacked for download
Date: 11/15/92 - v5.0 - added ability to reject duplicate additional files
Date: 12/10/92 - v5.1 - fixed local upload oops and VCHKx file bug in RBBS
Date: 02/23/93 - v5.2 - automagically removes high/low ASCII from FILE_ID.DIZ
Date: 03/29/93 - v5.3 - not released to public
Date: 03/30/93 - v5.4 - minor bug fix and upgrade for RBBS v17.4a/031293
One great drawback to the files system in RBBS is it's inability to allow true
batch uploads. It's system of taking one file at a time and then asking for
the description only saves the user the keystokes of entering the file name
just before each upload. This tends to discourage users from uploading since
they can not set up a batch upload, set to auto logoff and leave their machine
unattended during the transfer.
Hence, this merge. This merge installs true batch uploading with RBBS. It has
been tested using DSZ and ZSX and is known to work with both of these.
July 27, 1992
The Batch Upload mod now takes all parameters from the command line. Users can
enter all files to upload, the transfer protocol (if desired) and the "/G" if
they wish to Auto-Logoff on the same command line. RBBS will check to see if
the file already exists, prompt for descriptions, complete the transfer and
update the directories. The user will be logged off after 30 seconds if they
select the Auto-Logoff feature.
Sept. 1st, 1992
This is the version everyone is waiting for! This version allows batch
uploading with any protocol which permits it.....EVEN BiDirectional TRANSFERS!!
A Sample PROTO.DEF file is included for reference. The user is able to select
a "High Speed" protocol, tell the system which files he/she wants to download,
tell the system the files he/she wants to upload, give descriptions and
transfer files to and from the system at the same time. As long as you tell
the protocol to create a DSZ log, the system will check for files that the
user may have uploaded, without telling the system. If any files are found
that the system was not informed about before hand, the user will be prompted
for the descriptions and, optionally, if the user security level permits, the
category for the files.
Setup is pretty straightforward. You must place an "H" in the 5th position in
your PROTO.DEF file when installing the protocol. Yes, this is the same
position that you would place an "R" if the protocol were to require a reliable
connection. Next, there is a new parameter that RBBS is able to pass to
protocols...that being UPDIR. This new parameter is the location of the upload
directory for the conference. This parameter is passed to the protocol just
like any other (BAUD, CBAUD, FILE, PORT#, etc.). A sample line for HSLink
would be:
"H)SLink (BiDirectional)
",5,S,8,H,B,1024,,0.95,,1=E,"C:\RBBS\XFER\HSLINK.EXE -P[PORT#] -E[CBAUD]
-U[UPDIR] [FILE]","C:\RBBS\XFER\HSLINK.EXE -P[PORT#] -E[CBAUD] [FILE]
You must have either the enviroment variable "SET DSZLOG=XFER%node%.DEF" set
or tell the protocol to create a DSZ type log named XFER%node%.DEF (%node% is
the number of the node) located in the same directory as the RBBS-PC.EXE file.
This log is necessary to check if any additional files have been uploaded
besides the files that the user told the system.
PLEASE BE ADVISED: You are passing the upload directory to the sending
protocol...the user can upload many files without telling you before hand!
Without the DSZ log, there would be no way of telling. The system will
prompt the user for the information...and if the user drops carrier, it will
write out >>> Description Unavailable <<< to let you know that there was no
prior notification!
This safety feature will work with all protocols which permit batch uploading
(DSZ, ZSX, etc) and create a DSZ type log.
With this version of batch uploading, all commands are taken from the command
line as with stock RBBS. The user can stack the files to upload along with
the protocol and the "/G" for auto logoff. The user can even set the
bidirectional protocol as his/her default protocol. The internal protocols
(Xmodem, Ymodem and ASCII) function properly as well.
When using a bidirectional protocol, the user is credited with the upload
time at the rate the SysOp has preset in CONFIG param 10. Naturally, this
time will be credited against the download time if it is longer than the
upload time. If the Sysop has CONFIG param 10 set to 0 then no credit will be
given. If 1, the user time stands still ONLY for the upload, 2, the user will
get credit for extra time equal to the upload, etc.
All statistics concerning number of files transferred will be updated. The
user will get credit for uploaded files and downloaded files. The same holds
true for byte counts.
This mod has been tested with HS-Link. It should work with any bidirectional
protocol requiring the upload directory be passed, the file names to be
downloaded passed and the DSZ log file to be checked for any additional files.
Files created by this modification are:
NODE%node%FDN - List of files for downloading by the user.
NODE%node%FUP - List of files for uploading by the user.
NODE%node%FUP.LST - List of files, descriptions, and categories for files
to be uploaded.
* %node% is the node number
These files will reside in your node work directory.
If a malfucntion of your system should cause the system to crash, these
files may still exist. These files should be erased automatically on the next
transfer.
Oct. 15th, 1992
There was a bug with the BiDirectional transfer and the auto logoff when
initiated from an Download. This was pointed out by Geoffrey Nolasco of the
MegaMixers BBS in Wheaton, MD. (301-949-0183). While searching for the
cause, I found some redundant code which is now removed. The Auto Logoff
now works properly with all batch uploads, downloads, and bidirectional
transfers. The new code is more efficient with the removal of the "extra"
code. Once again, thanks Geoffrey.
Oct. 24rd, 1992
Found a minor bug when doing local upload and describing an existing file.
If you entered "ABORT" to abort the description, the system would crash with
an error in RBBSSUB5.BAS. This is now fixed.
Decided to clean up the sequencing a bit. If security permits, you will no
longer be asked to categorize and upload if it is a personal upload.
If security permits, you will no longer be asked if you wish to leave an
extended description on a personal upload.
Minor bug with an occasional file being written to the wrong directory
when doing a personal upload is now fixed.
Oct. 28th, 1992
Introduced major bug in v3.7 due to the different ways RBBS handles uploads
from local to remote. I only tested locally (oops!) and missed the fact that
remotely the system would crash on uploads due to the fact that the user
wasn't asked who the file was to before asking to categorize or leave an
extended description. This only occurred if you had the security
level set to permit users to make personal uploads and categorize uploads.
I moved the SetWhoTo call into the UpdtUpload routine so both local and remote
uploads follow the same sequencing. This fixed the major bug introduced and
permitted the elimination of asking the user to categorize a personal upload
and leave an extended description on personal uploads (if security level
permits).
With this version, support for FILE_ID.DIZ and DESC.SDI files is introduced.
The RBBS software, in conjunction with the archive test file (ie: TZIP.BAT,
TARJ.ZIP, etc.), will now replace the users description of a file with the
description written by the author. This is accomplished by copying the
description file to the node work directory as a file named NODExDIZ (where
x = node number) during execution of the test file. You will need to add
2 lines to your test file similiar to:
...
IF EXIST <path1>\FILE_ID.DIZ COPY <path1>\FILE_ID.DIZ <path2>\NODE%node%DIZ
IF EXIST <path1>\DESC.SDI COPY <path1>\DESC.SDI <path2>\NODE%node%DIZ
...
with <path1> being the path of your testing directory and <path2> being the
path to your node work directory. I have included a sample of my TZIP.BAT
file which I use for testing xxx.ZIP files. On completion of a successful
upload RBBS will look to the node work directory for the NODExDIZ file, and
if found, import the text contained within as the file description. You will
have to modify all your test files to copy the description files to the node
work directory.
Another file will now be found in your Node Work Directory. The name of this
file is:
NODE%node%DIZ - Description of file copied from FILE_ID.DIZ or
DESC.SDI
This file will be erased on the next upload if it remains for any reason.
Nov. 8th, 1992
Found another bug.......hopefully the last! If you entered "P" from the files
menu and stacked personal files for download, when prompted for a protocol the
system would go into a loop if you selected "N" to abort. If you then
selected a protocol (to exit the loop), the system would create, and send a
bogus 0 byte file. This is now fixed.
Nov. 24th, 1992
Additonal files are those files uploaded during a batch upload which the user
did not tell the system were coming. The system will automatically detect
these files through the DSZ log. Prior to this version, the additional files
were not checked to see if they duplicated files on the system. The system
just prompted the user for the description and treated the files like any other
uploaded file. Now these additional files will be checked just like the check
prior to uploading, and, if found to be duplicates, they will be erased and
all credit removed. This was added for protocols like DSZ and ZSX which, while
allowing batch transfers, do not check for a list of directories to search for
duplicates like HS-Link or BiModem will. You should make sure that the
protocol will not allow overwrites so if a file exists in the upload directory
they will be refused. The combination of the two, will insure any files
uploaded, will not be duplicates.
The batch upload mod now has additional files which pass the screening
become personal uploads to the SysOp if the user should drop carrier right
after the upload process. This allows the SysOp to check these files before
posting to the general users of the board since the carrier drop might be
intentional (for whatever reason).
RBBS now uses only one archive test file named TEST.BAT. RBBS will pass the
file extension to this test file as %6. You no longer need those half dozen
test files hanging around in your root directory. RBBS now passes the
communication port (as COMx) to this TEST.BAT file for processing. This makes
it fairly simple to use ECHO statements to the user since you only need one
statement on multinode systems. Look at the enclosed TEST.BAT file for
reference. I run a two node system, so I don't need to check which node is
testing to determine which port to send my messages out. This new parameter is
passed as %3 to the batch file.
RBBS will also pass the users first name (%4) and last name (%5) to your
archive test file. This means you can display messages that appear to be
custom by incorporating the users name into the message.
Summary of parameters that RBBS will pass to the archive test file:
%1 - The name of the file to be tested - stock in RBBS
%2 - The file to which you write out a failure string - stock in RBBS
%3 - The communications port in use - new
%4 - users first name - new
%5 - users last name - new
%6 - file extension - new
Please be advised that with the passing of these additional parameters, you
may have to increase your enviroment size to accomodate the added length.
This version of BTCH174 also contains the NE174V10 (NEXT174) mod. If you wish
to disable this feature, you can either remove the lines commented with
' NEXT174 or do nothing. The modification will be ignored if the NOEXT.DEF
file does not exist. See the NEXT174.DOC for information about this mod.
Dec. 10th, 1992
I had built upon existing merge files and when typing in the changes from
the previous version, typed in a line in RBBSSUB5.BAS which caused local
uploads to crash with a Divide by Zero error. Sorry! Fixed in this version.
(Was hoping not to have a 5.x version). Anyways, while I was at it, I decided
to fix a bug in RBBS whereby the node VCHKx file isn't erased and can cause
subsequent uploads after a bad upload to be considered bad and removed by the
system if they are untested (by SysOp choice). The "old" VCHKx message is
read and the system determines that the upload was bad. The system will now
erase the VCHKx file if it indicates that an upload is unacceptable thereby
eliminating subsequent files from being removed.
Feb. 23rd, 1993
Now automagically removes high/low ASCII from FILE_ID.DIZ and DESC.SDI files
for importing into your RBBS files directory. Plug and play with prior
version.
*****************************************************************************
Mar. 30th, 1993
Minor bug fix for single file bidirectional transfer abort and asking for
extended description if allowed.
Also, upgraded for RBBS v17.4a/031293 mods with installation of RFIX0312
from Ken Goosens.
*****************************************************************************
As with all my merges, my recommendation is to istall this modification by hand
if you have installed any other merge(s) which may have accessed any of the
lines used by this merge. If you so decide, you may install this merge using
Ken Goosens BLED v2.2. A batch file is included to assist you with BLED.
Simply copy the files in this archive to a directory, copy your RBBS v17.4
source code to the same directoy, copy BLED v2.2 to this directory and run
the enclosed batch file. The old .BAS files will be renamed to .OLD and the
new files will be renamed to .BAS. You can then replace your RBBS-VAR.BAS file
with the one enclosed in this archive, and using the new source files,
recompile.
Files included in this archive are:
R-PCBTCH.MRG - Mod for RBBS-PC.BAS
RSB1BTCH.MRG - Mod for RBBSSUB1.BAS
RSB3BTCH.MRG - Mod for RBBSSUB3.BAS
RSB4BTCH.MRG - Mod for RBBSSUB4.BAS
RSB5BTCH.MRG - Mod for RBBSSUB5.BAS
RBBS-VAR.NEW - Replacement RBBS-VAR.BAS file
BTCH174.BAT - batch file for BLED v2.2
BTCH174.DOC - this document file
PROTO.REF - PROTO.DEF file for reference
TEST.BAT - sample archive test file
FD.HLP - Download Help file
FU.HLP - Upload Help file
FILE_ID.DIZ - Description of this ZIP archive
NEXT174.DOC - document file for NEXT174
NOEXT.DEF - sample file for NEXT174
Have fun and let me know how things work out.
Richie Molinelli
The Small Time BBS
Runnin RBBS v17.4a/STUNY
1200 thru 14400 bps
516-579-7929
1:107/272@fidonet
8:954/272@rbbsnet
10:110/3@busilink
LEGALITIES:
RBBS is Copyright (c) 1986,1992 by D. Thomas Mack
BTCH174 and BU174Vxx merge is Copyright (c) 1992,1993 by Richard Molinelli.
This mod is for personal use by the SysOp. This merge can not be used in part
or in whole in any package without prior written permission from the author.
To do so would be in violation of the copyright laws of the United States. This
merge can only be included in stock "RBBS" as released by the RBBS development
team, the HSLink package as distributed by Samuel Smith, the STUNY mods released
by Richie Molinelli and Gary Glueckert, and it's own package labeled BU174Vxx
(the xx being the version number).
This merge is to be distributed in it's own, freestanding file. It is
forbidden to distribute this merge in any modified form. It is forbidden to
distribute this merge bundled with any merge package other than the
aforementioned packages.
WARRANTY AND DISCLAIMER:
Simple. None. Narda. Zip. Nothing. I am not responsible for any
damage that occurs by using this merge nor am I responsible for any good that
occurs from using this merge. I'm just plain not responsible. My mother has
been telling me that since I was a kid.
REGISTRATION:
None required!
If you are the author of a program, please consider u/l a registered copy of
your program to my BBS.
If you are the author of a merge, please consider u/l a copy of your merge to
my BBS.
If you are neither of the above, please consider sending me a postcard to the
address listed below telling me how you love/hate/don't care about the merge.
I happen to like postcards.
Richie Molinelli
P.O. Box 961
Levittown, NY 11756