home *** CD-ROM | disk | FTP | other *** search
-
-
- RUNNING FROM WAKEUP.BB.................................WAKEUP.DOC page 1
-
-
-
- W5TOO's LOOKUPDT System
-
- Below is what my WAKEUP file looks like. I've had trouble getting
- Roy's "EX" commands to work for me. It seems the directories in which
- everything resides are critical! I now keep WAKEUP.BB in the directory
- with BB.EXE.
-
- **** BE SURE TO USE THE CORRECT DIRECTORY PATHS IN THE COMMANDS BELOW ****
-
- 900506/1509 ==/==/== +0:30 KF
- 900506/0500 ==/==/== 05:00 GL
- 900506/0501 ==/==/== 05:00 GE
- 900506/0502 ==/==/== 05:00 KO
- 900506/0700 ==/==/== 05:00 GI
- 900506/0646 ==/==/== 06:45 EXPORTK C:\MSGS\LOOKUP.IN E LOOKUP
- 900506/0410 ==/==/== 06:50 EX C:\MSGS\HDRSTRIP.EXE
- 900506/1522 ==/==/== 06:54 EX C:\MSGS\LOOKUPDT.EXE
- 900506/0801 ==/==/== 08:00 GM
- 900506/0605 ==/==/== 07:15 GO TYPE B 10 * 30
-
- The entries are...
-
- EXPORTK C:\MSGS\LOOKUP.IN E LOOKUP - Use if it works for you. See
- detail below. If you use it, I suggest
- (USE CORRECT PATH) running daily, or even more often.
- It integrates messages from N2MH's
- stripper and from W5TOO into your
- process. YOU CAN DO MANUAL EXPORTs
- WHEN YOU SEE THESE MSGS COME IN.
-
- EX C:\MSGS\HDRSTRIP.EXE - Does the header stripping. Run it daily,
- BEFORE you execute GM (reorg msgs). I
- (USE CORRECT PATH) recommend an hour when the board isn't
- too busy, though it takes only a minute
- or so.
-
- EX C:\MSGS\LOOKUPDT.EXE - This module updates your HLOOKUP.BB file.
- It should be run AFTER the above two. It
- (USE CORRECT PATH) also generates a file, NEWADR.IN, which
- is a record of all the new/revised entries
- you've added to HLOOKUP.BB. Kill it
- periodically. (I append to it, so it will
- just continue to grow.)
-
-
-
- NOTES ON OPERATION FROM WAKEUP.........................WAKEUP.DOC page 2
-
-
-
- NOTE: ESPECIALLY if you're an HF/VHF gateway, handling lots of traffic, it is
- necessary to run these modules often. In order to let LOOKUPDT.EXE run
- as a server (memory constraints), the number of HEADERS it can process
- is limited to 500. If you let more than that build up before running,
- it trashes the extras! The raw, stripped headers are found in a file
- called LOOKUP.IN, so you can watch them for a while and judge
- how often you'll need to run. This file is built and added to each time
- you run HDRSTRIP.EXE or execute the EXPORTK line discussed below.
-
- - - - - - -
-
- To AUTOMATICALLY include new header data received from N2MH's system, it
- is necessary to create a NEWHDR.CC file. See INSTALL.DOC for specific
- instructions.
- - END -