Monster Media 1994 #1

home *** CD-ROM | disk | FTP | other *** search

/ Monster Media 1994 #1 / monster.zip / monster / BBS_UTIL / HROUTEB9.ZIP / HOTROUTE.DOC < prev next >

Wrap

Text File | 1994-03-12 | 16KB | 310 lines

┌──────────────┐ │ HOTRoute ß.8 │ └──────────────┘ A HOTware Utility from Rob Roesch ────────────────────────────────────────────────────────────── History ────────────────────────────────────────────────────────────── 2-24-94 Ver ß.1 Not Released For Public Testing 2-25-94 Ver ß.2 Public BETA Test Release 2-26-94 Ver ß.3 Removed .COM extension from PKARC and PKXARC. Evidently some were using a version of PKARC and PKXARC with a .EXE extension. The HOTRoute Statistics report at the end of the execution now reflects the number of bags processed and the number of encrypted messages processed. 2-27-94 Ver ß.4 Fixed a problem in ß.3 that was removing Archive comments from B Bags. This version will properly retain the comments when the Bag is reconstructed. Any Bags that go through you system that have no archive comments, BBags or GBags will get "????" installed as the Archive comment. There should be very few of these after the ones that ß.3 has been creating find final destinations. This version will not display Archive Comments that start with a ';'. This represents a flag in your routing file that tells the netmail suite of programs not to display the Bag Comments. HOTroute will display ;XXXXXXXX (Non Displayable Comment) when one of these comments are encountered. The third change includes a /NC parameter, ie. NOCLEAR (Don't clear the window at the end of execution, this one was put in especially for Jim Knight. (You Reading This Jim? ) 3-03-94 Ver ß.5 This version has freshly tweaked code to attempt to speed up the execution of HOTRoute. This version also adds a new parameter /BIOS. (Bios Video Screen Writing). 3-04-94 Ver ß.6 This version is a bug fix release for version ß.5. Version ß.5 should NOT be used. It had a serious bug that would delete any ABags from within a BBag. Fortunately this version did not hit auto distribution because it deleted itself from the outgoing bags before it was distributed. 3-09-94 Ver ß.7 1) HOTRoute now has "Looping Route" Intelligence. HOTRoute will detect when a bag travels through your system multiple times, ie a looping bag that is not arriving at it's final destination. When the offending bag hits your system the 3rd time it will automatically be removed from the G or Bbag (even imbedded GBags) and be placed in \MAILOUT\LOOPING. HOTRoute will then leave you a message in your private sysop message area (as configured in GT.CNF) letting you know that the bag has been placed in the LOOPING directory. At that time you may either delete the bag, or repair the routing and copy the bag back into the MAILOUT directory. 2) HOTRoute can now be told a maximum size the LOG file should be allowed to grow with a /MAXLEN:<size> command line parameter. If this parameter is used the LOG entries will be treated in a FIFO fashion (First In First Out). See command line options below for a full discussion on the usage of this parameter. 3-10-94 Ver ß.8 A really pesky bug has been squashed with this release. HOTRoute had a nasty bug that was duplicating imbedded GBags in multiple GBags. If a GBag contained an imbedded GBag but no BBags, the imbedded GBags were appearing in multiple bags. This was causing some very large and repetitive bags for several systems. Everyone should replace all previous versions with ß.8 immediately. 3-12-94 Ver ß.9 This release will now check to see if the destination routing has been changed when a bag is identified as a "Looping Bag". Previously even if you corrected the routing and copyied bags from the \MAILOUT\LOOPING directory back into the \MAILOUT directory, HOTRoute would still see the bag as "Looping" even if the destination routing was changed. The only was to avoid having the bag moved back to the LOOPING directory was to edit the Route: line in the imbedded MBag. Now HOTRoute will recognize the fact that the destination routing has changed and not view the bag as a "Looper". A new command line parameter has also been added, /NOMSG. This will tell HOTRoute not to write you a personal message when it detects a looping bag, just move it to \MAILOUT\LOOPING and be quiet about it. ────────────────────────────────────────────────────────────── Purpose ────────────────────────────────────────────────────────────── This utility produces a "Route:" line in messages produced on your system and updates any Route: lines passing through your system - hence providing a method of tracing the route taken by messages as they go through a GT network. HOTRoute will also use this route line to take "Looping" bags out of the stream. When an offending bag hits your system the 3rd time it will automatically be removed from the G or Bbag (even imbedded GBags) and be placed in \MAILOUT\LOOPING. HOTRoute will then leave you a message in your private sysop message area (as configured in GT.CNF) letting you know that the bag has been placed in the LOOPING directory. At that time you may either delete the bag, or repair the routing and copy the bag back into the MAILOUT directory. As you have probably guessed by now, this is a PKZip version 1.1 and 2.04 compatible replacement for the popular MSRoute program. HOTRoute is fully compatible with the latest releases of MSRoute and RKRoute. ────────────────────────────────────────────────────────────── EXECUTION ────────────────────────────────────────────────────────────── The MSRoute program is simply run after EVERY MBAGGER run, including when it is called from G_UNPAK. There are no parameters required for execution, although there are two optional log file parameters that may be used. These parameters are explained below under COMMAND LINE PARAMETERS. Please remember to insert in every .BAT file you may have that currently calls MBAGGER. ────────────────────────────────────────────────────────────── COMMAND LINE PARAMETERS ────────────────────────────────────────────────────────────── HOTRoute currently recognizes six individual command line parameters. Three of these parameters may be used to turn off the HOTRoute.LOG, to have HOTRoute overwrite existing log files, or to tell HOTRoute the maximum size the log file should be allowed to grow to. /NEWLOG = Overwrite any existing Log File and start fresh. /NOLOG = DO NOT Keep a log file. /MAXLOG:<size> Where: <size> = The maximum length in bytes of the log file: Examples: /MAXLOG:100000 or /MAXLOG:100K (If the last character is 'K' three trailing zero's will be added) If this parameter is used the LOG entries will be treated in a FIFO fashion (First In First Out), and HOTRoute will maintain the log size for you so the log does not eat your entire hard disk. HOTRoute by default creates <GTPATH>\HOTWARE\HOTROUTE.LOG and appends to this log file on every execution. This can grow quickly so if you are short of disk space you should erase/archive, use the /NEWLOG or /NOLOG parameters, or specifically tell HOTRoute how large the log should be allowed to grow. You should try to keep a day or two's log just in case it is required for queries or debugging. The fourth parameter tells HOTRoute NOT to write you a message if it moves a "Looping" bag. The default is for HOTROUTE to leave you a message in your Private Sysop Message area. If you do not want this message use the following parameter: /NOMSG = Don't write to me if you move a looping bag out of the stream. The fifth parameter controls video mode. The default for HOTRoute is to use Direct Video Ram writes. You may request HOTRoute to use BIOS writes with... /BIOS = Use the BIOS to write to video. The sixth parameter controls the window handling at the end of execution. The default for HOTRoute is to use clear the execution window at the end of execution. You may request HOTRoute to leave this window at the end of execution with.... /NC = NO CLEAR Of execution window. ────────────────────────────────────────────────────────────── EXECUTION EXAMPLES ────────────────────────────────────────────────────────────── If Jim Knight at 064/001 sent a message to Perry Alexander at 032/001, the message would be created at Jim's board and the HOTRoute program would insert a line... Route: 64/1m2 64/3 Jim's system knows that it is passing it on to 064/003. Also note that HOTRoute time stamps the entry when it was processed. The 64/1 entry indicates that it was processed Monday and 2:00am (24 hour format). Continuing down the line, the above Route: line, when it gets to 064/003 my system knows to pass it on to Perry so will update the line to... Route: 64/1m2 64/3m4 32/1 Note the above route line now tells us that the message was bagged on Monday at 2am on 064/001, passed to 064/003 and processed on Monday at 4am. The message was then directed toward 032/001. Gaps in routings will be indicated with at */*. For example if I were to send a message to Red Gambrell at 025/001, the final route line should appear at Red's system with the following: Route: 64/3m2 64/1m4 21/0m6 25/1 However lets assume that Jim Knight is not running HOTRoute. Therefore when the message arrives at 25/0 it will have the following route line. Route: 64/3m2 64/1 HOTRoute recognizes that it was not processed somewhere along the line and that the route is not accurate. HOTRoute will amend this situation by creating the following route line to indicate that gaps in routing may exist. Route: 64/3m2 64/1 */* 21/0m6 25/1 ────────────────────────────────────────────────────────────── STATISTICS ────────────────────────────────────────────────────────────── HOTRoute will report the following results at the end of each execution: HOTRoute Execution Statistics ───────────────────────────────────────────────────────────────── Started Route: 0 Updated Route: 0 Updated Route (gaps): 0 Changed Route: 0 Left Route: 0 Trapped Looping Bags: 0 ZIP B-Bags: 0 ARC B-Bags 0 Encrypted Bag: 0 19 Bags Processed In 1 min 12 seconds Thank You For Using HOTRoute ß.7 ───────────────────────────────────────────────────────────────── Started Route = No previous Route Line was found, Route started. Updated Route = The Route Line appears intact, HOTRoute has updated the route line with your Net/Node number. Update Route (gaps) = The Route Line appears to have gaps. The route line will be updated with a */* to indicate that the message has traveled through at least one system that is not running HOTRoute. HOTRoute will update the line with your Net/Node after the */*. Changed Route = The destination after leaving your system has changed. Changed routes indicate that a message is now headed to an alternate system that HOTRoute had originally updated. Left Route = The Routing has not changed since the last execution. The line will be left intact. Trapped Looping Bags = This indicates that bags were found that were "Looping" ie, they have hit your system at least three times. These bags were removed and were placed in \\MAILOUT\\HOTROUTE. ZIP B-Bags = The number of BBags that were processed that were created with PKZIP. ARC B-Bags = The number of BBags that were processed that were created with PKARC. Encrypted Bag = This message was encrypted on the source system. HOTRoute cannot update a route line on encrypted messages. ────────────────────────────────────────────────────────────── Registration ────────────────────────────────────────────────────────────── I am not requesting any money for this program, but I would not turn any down either <g>. If you want to slip $5.00 into and envelope I'll accept it. Although I don't require a registration fee I would appreciate knowing that you are using the program on a normal basis. Therefore I have provided a simple and easy way for you to register this program. From the DOS prompt type: HOTROUTE /REGISTER HOTROUTE will the proceed to send me a netmail message informing me that you are using the program. Please use this feature ONCE. ────────────────────────────────────────────────────────────── Who Is Responsible for This? ────────────────────────────────────────────────────────────── Rob Roesch The HOTware BBS GT Power Net-Node 064/003 Rt 7 Box 566 Mocksville, NC 27028 704-492-2081 (USR 16.8 DS) If you start using this utility, and get a chance, let me know what you think of it. If you don't have any use for it, delete it for your total refund of all the disk space that it was occupying. This program comes with no warranty, no guarantee, and no promises. If it works GREAT, if not let me know and I will gladly take a look at it in my spare time. If you really really really like the program and want to make any donations, feel free, but it is not a requirement.....