ftp.wwiv.com

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

/ ftp.wwiv.com / ftp.wwiv.com.zip / ftp.wwiv.com / pub / MISC / LN2V100.ZIP / LN2V100.DOC < prev next >

Wrap

Text File | 1998-08-26 | 166KB | 3,274 lines

█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ ██ ██▄ ██ ██▀▀▀▀▀▀ ▀▀▀██▀▀▀ ▀▀▀██▀▀▀ ▀▀▀██▀▀▀ █ █ ██ ██▀█▄ ██ ██▄▄▄▄ ██ ▄▄▄▄ ██ ██ █ █ ██ ██ ▀███ ██ ██ ██ ██ █ █ ▀▀▀▀▀▀▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀▀▀ ▀▀ ▀▀▀▀▀▀▀▀ ▀▀▀▀▀▀▀▀ █ █ ██ ██ ▄█▀▀▀▀█▄ ██▀▀▀▀▀▀ ██▀▀▀▀█▄ █ █ ██ ██ ▀█▄▄▄▄▄ ██▄▄▄▄ ██▄▄▄▄█▀ █ █ ██ ██ ▄▄ ██ ██ ██ ██ █ █ ▀▀▀▀▀▀ ▀▀▀▀▀▀ ▀▀▀▀▀▀▀▀ ▀▀ ▀▀ █ █ ██▄ ▄██ ▄█▀▀▀▀█▄ ██▄ ██ ██ ██ ▄█▀▀▀▀█▄ ██ █ █ ██▀██▀██ ██▄▄▄▄██ ██▀█▄ ██ ██ ██ ██▄▄▄▄██ ██ █ █ ██ ██ ██ ██ ██ ▀███ ██ ██ ██ ██ ██ █ █ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀▀▀ █ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ LNET-II v1.00 - Copyright 1996-1998 by Ken Harris / CMI Software █ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ ▄▀▀▀▀▀██▀▀▀▀▀▄ ▄█▀▀▀▀█▄ ██▄ ▄██ ▀▀▀██▀▀▀ █ █ ▄▀ ▄▀ █▄▄▄▄▄▄█▄ ██ ▀▀ ██▀██▀██ ██ █ █ ▀▄ ▀▄ ▄▄▄▄▄▄▄▄▄ ██ ██ ██ ██ █ █ ▀▄ ▀▄█ ▄▀ ██ ██ ██ ██ ██ █ █ ▀▀▀▀▀▀▀▀▀▀▀▀ ▀▀▀▀▀▀ ▀▀ ▀▀ ▀▀▀▀▀▀▀▀ █ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ┌─────────────────────────────────────────────────────────────────── ┌┬┐┌┬┬┐┌┐ │ THIS IS AN UNRELEASED BETA COPY OF LNET-II 1.00 FROM CMI SOFTWARE │├┤│├┤│││ └─────────────────────────────────────────────────────────────────── └┴┘└┘└┘└┘ Use of this program is restricted to the operators of CMI Software distribution and support sites, and to other persons designated by the author. A release notice will be posted when this program is ready for general distribution. Four letters: RTFM! I've been asked several questions that were already clearly answered in this manual. Please look here first. The "Revision History" section of the documentation may show a release date for this program; this DOES NOT mean the program has been released on that date! Again, you may consider the program released when a notice has been posted. At that time, please be sure you have the most recent revision on your system, and move it to a public directory for download. As this program is still in development, it is subject to frequent changes and additions. New versions will generally be sent to beta testers as soon as they are available; however, it would be a good idea to check with me periodically to make sure you have the most recent version. I have discovered that the XLNET name is in fact trademarked, by ExcellTech in 1988. This predates my use of the name by five years and is registered with the U.S. Patent & Trademark Office. As such, I am legally required to stop using the name. The packet reader formerly known as XLNET v2.00 is now called LNET-II v1.00. New name, new version number, same program. IDEAS ARE ALWAYS WELCOME. I can't think of everything. <grin> If you have an idea for a feature to be added to this program, feel free to pass it along, and I'll try to add it if I think it is feasible. Please keep in mind that the release date will PROBABLY be Wednesday, August 26th, 1998; I would rather not delay the release any further with major new features to be tested. From this point onward, please submit ideas only for simple features and cosmetic patches. In order to detect bugs, a program must be used! Please run this program as often as possible, and try to use all available features. If you believe you have found a bug, please send me a description of it and the conditions which caused it to appear. A copy of the packet which was being read at the time could also be helpful. If you need to send a copy of a packet, the best ways are to attach it to an Internet e-mail and send it to xfire905@aol.com, send it via K9NFX to 1@1 USLink, or send it via NFT to 1@571 FILEnet. ┌─────────────────────────────────────────────────── ┌┬┐┌┬┬┐┌┐ │ C M I P R O D U C T R E G I S T R A T I O N S │├┤│├┤│││ └─────────────────────────────────────────────────── └┴┘└┘└┘└┘ This is a SHAREWARE product. License is granted to use the program without charge for an evaluation period of not more than 30 days. After this time, users are required to register or cease their use of the program. The registration fee for this program is $20 U.S. for each installed copy. Mail your payment in a check or money order to: Ken Harris 9948 Duffy St. Temple City, CA 91780-2607 NOTE: DO NOT make your check or money order payable to CMI Software, as this is only my trade name - I do not have a business checking account under that name. I am not equipped to handle credit card orders. ═════════════════════════════════════════════════ Registration of this CMI Software product is now handled through your WWIV.INI file. On receipt of payment, you will receive e-mailed instructions for installing your personal registration code. Please include a network address to which you would like to have your regi- stration code mailed [preferably on one of the following: DigiNet, FILEnet, IceNET, TerraNET, USLink, WWIVLink, WWIVnet, Internet]. Certain features in this program are not available to unregistered users. When your payment is received and a registration code is returned to you, and that code has been entered in WWIV.INI, those features will be available. "Registered Only" features are clearly indicated in this manual. A registration form can be found on the next page. Please print the form, fill it out completely, and submit it with your payment. [Please do not edit or modify the form before printing! Use only fixed-width fonts to print the registration form.] ╔════════════════════════════════════════════════════════════════════╗ ║ LNET-II v1.00 REGISTRATION - CMI SOFTWARE DISTRIBUTION ║ ╚════════════════════════════════════════════════════════════════════╝ Date: ___/___/___ Amount enclosed: $__________ Your name: ___________________________________________________________ [Enter name as you want it to appear in registration] Address : ___________________________________________________________ ___________________________________________________________ ___________________________________________________________ BBS name : ___________________________________________________________ [Enter BBS name as it appears in INIT, not in WWIV.INI] BBS phone: ___________________________________________________________ [Enter BBS phone as it appears in INIT, not in WWIV.INI] Net Addr.: ___________________________________________________________ ┌────────────────────────────────────────────────────────────────────┐ │ U S E R S U R V E Y │ └────────────────────────────────────────────────────────────────────┘ Have you used a previous version of this program? [n/a] Will you consider using future versions? [Y] [N] Does this program contain all the features you want? [Y] [N] How would you rate this program on a scale of 1 to 10? __________ How would you rate the documentation on a scale of 1 to 10? __________ Comments/Suggestions: ________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________ ┌─────────────────────────────────────────────────────────── ┌┬┐┌┬┬┐┌┐ │ LNET-II 1.00 - Copyright (C) 1996-1998 by Ken Harris / CMI │├┤│├┤│││ └─────────────────────────────────────────────────────────── └┴┘└┘└┘└┘ ╒════════════════════════════════════════════════════════════════════╕ │░░░░░░░░░░░░░░░░░░░░░░░░░ C O N T E N T S ░░░░░░░░░░░░░░░░░░░░░░░░░░│ ├────────────────────────────────────────────────────────────────────┤ │ OVERVIEW / INSTALLATION ........................................ 1 │ │ Remote Operation ........................................... 2 │ │ RUNNING LNET-II ................................................ 2 │ │ THE MAIN SCREEN DISPLAY ........................................ 5 │ │ F1: Help ............................................... 7 │ │ ENTER: Reading Item Text .................................. 7 │ │ Special Item Recognition .................................. 10 │ │ COMMAND KEYS .................................................. 10 │ │ SELECTING ITEMS AND PACKETS │ │ Cursor Pad ............................................ 11 │ │ ALT+K: Select Packet ................................. 12 │ │ ALT+I: Select Item [List] ............................ 13 │ │ ALT+G: Go To Item # .................................. 14 │ │ DELETING AND RESTORING ITEMS │ │ ALT+D: Delete Item ................................... 14 │ │ CTRL+D: Mass Delete [Reg'd Only] ...................... 15 │ │ ALT+T: Truncate Packet ............................... 15 │ │ ALT+R: Restore Item .................................. 16 │ │ CTRL+R: Mass Restore [Reg'd Only] ..................... 16 │ │ ALT+C: Clean Up Packet ............................... 16 │ │ VIEWING ITEM / NODE DATA │ │ ALT+F: View Item Origin .............................. 17 │ │ ALT+L: View Destinations ............................. 18 │ │ ALT+N: View Network Node List ........................ 19 │ │ ALT+U: View Sub Info ................................. 20 │ │ EXTRACTING ITEMS TO TEXT │ │ ALT+E: Extract Message ............................... 20 │ │ CTRL+E: Mass Extract [Reg'd Only] ..................... 22 │ │ LEAVING LNET-II │ │ ALT+X: Exit .......................................... 22 │ │ CONFIGURATION / TOGGLES │ │ ALT+O: Toggle Optional Lines ............................. 23 │ │ CTRL+O: Set Optional Lines Value .......................... 23 │ │ ALT+P: Toggle Pause ...................................... 24 │ │ ALT+S: Toggle Sound ...................................... 24 │ │ ALT+V: Toggle MaxRez Video ............................... 25 │ │ CTRL+V: Select Video Mode ................................. 26 │ │ WWIV.INI Settings ......................................... 26 │ │ ALT+W: Write WWIV.INI .................................... 33 │ │ F2: Configuration Menu ................................ 34 │ │ SEARCHING FOR ITEMS [Reg'd Only] .............................. 35 │ │ ITEM TAGGING / TAG COMMAND MENU [Reg'd Only] .................. 38 │ │ THE NONEXISTENT NODE LIST EDITOR .............................. 39 │ ╘════════════════════════════════════════════════════════════════════╛ ┌─────────────────────────────────────────────────────────── ┌┬┐┌┬┬┐┌┐ │ LNET-II 1.00 - Copyright (C) 1996-1998 by Ken Harris / CMI │├┤│├┤│││ └─────────────────────────────────────────────────────────── └┴┘└┘└┘└┘ ╒════════════════════════════════════════════════════════════════════╕ │░░░░░░░░░░░░░░░░░░░░░░░ A P P E N D I C E S ░░░░░░░░░░░░░░░░░░░░░░░░│ ├────────────────────────────────────────────────────────────────────┤ │ A1. WWIV Network Item Types ................................... 41 │ │ A2. CMI NetUp Item Types ...................................... 44 │ │ B. LNET-II Item Validation ................................... 46 │ │ C. Revision History .......................................... 48 │ │ D. Contacting The Author ..................................... 49 │ │ E. Copyright / Shareware Notice .............................. 50 │ │ F. Trademarks And Credits .................................... 51 │ ╘════════════════════════════════════════════════════════════════════╛ ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ OVERVIEW / INSTALLATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ LNET-II is a fast and powerful WWIV network packet viewer. Features include automatic detection of readable network packets, highly detailed displays of header data and item destinations, automatic detection and validation of CMI NetUp items, scroll-bar selection of packets and items, and full ANSI / WWIV- ansi / pipe code color / ANSI music decoding. The message text display can be toggled between 25-line mode or 30/43/50/60-line modes, depending on the type of display being used. Available modes are automatically detected. 132-column display modes are not supported. Optional pull-down menus are available. The pull-down colors are configurable; see pages 30-31 for details. Two icons are included with this archive - LNET2WIN.ICO is formatted for Windows, and LNET2OS2.ICO is formatted for OS/2. Installation of LNET-II generally requires nothing more than placing the program in, or calling it from, a directory in which it can locate the CONFIG.DAT and WWIV.INI files [see page 26]. If WWIV.INI is not found, or the [LNET2] con- figuration block does not exist in WWIV.INI, LNET-II will create the file if necessary and write the [LNET2] block with the default program settings. The program will still be able to operate without an [LNET2] configuration block in WWIV.INI as long as it can find NETWORKS.DAT or BBSDATA.NET in your DATA\ directory, but it will not be able to load your registration code or default settings. LNET-II cannot run if CONFIG.DAT cannot be read. It needs CONFIG.DAT in order to find your DATA\ and GFILES\ paths and the BBS info for its registration. The extended help file LNET2.HLP must be in the directory from which LNET-II was called - generally the main BBS directory. If LNET2.HLP cannot be found, extended online help will not be available. [NOTE: LNET2.HLP is a formatted text file, not a Windows .HLP file. It cannot be read with WINHELP.EXE.] LNET-II reads the path to the DATA\ directory from CONFIG.DAT and attempts to detect whether your system is multi-netted or is running an older single-net version of the BBS. If DATA\NETWORKS.DAT is found, LNET-II will take its network data from that file. If NETWORKS.DAT does not exist, LNET-II will assume you have a single net, which would be in your DATA\ directory, and it will attempt to open DATA\BBSDATA.NET. NETWORKS.DAT will exist if you are running WWIV 4.21a or newer, even if you have only one network. LNET-II DOES NOT ALLOW DIRECT MODIFICATION OF MOST HEADER DATA. For instance, it will not allow an item's type or origin to be changed except to delete an item. This is for obvious reasons of network security - it is not within LNET-II's purpose to be a packet editor, as this could be used to forge messages. Such capabilities will not be included in any future releases. ────────────────────┤ LNET-II v1.00 User Manual - Page 1 ├───────────────────── LNET-II is a DOS-native application; however, file sharing and locking routines are included which should enhance compatibility with multi-tasking environments. File sharing/locking are automatically detected, and used if they are present. LNET-II has been tested under MS-DOS 6.22, Windows 3.11, Windows 95 / MS-DOS 7.00, Novell NetWare Lite, and OS/2 Warp. No tests have yet been made under Linux or DESQview. LNET-II does not include mouse support. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ REMOTE OPERATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ LNET-II is not specifically designed for remote operation. However, this may be possible by using a driver such as DOORWAY.EXE. At this time, no tests have been made using LNET-II under DOORWAY - if you can manage to make such a setup work, please let me know how you did it. LNET-II uses CTRL+F5 as a "fast abort" command; have DOORWAY send this sequence to execute a controlled shutdown of LNET-II if carrier is lost or DOORWAY times out. When running LNET-II under DOORWAY, use LNET-II's /NOHI command line switch to disable detection and use of high-resolution text modes [/NOHI forces 25-line mode for all displays]. LNET-II may be installed in your DATA\MACROS.TXT file to be used as a "pop-up" command from the BBS; however, keep in mind that it would usually be best to run LNET-II only from within the BBS instance which normally handles network mail transfers and processing. If LNET-II is installed in //CHAINEDIT, it should probably not be set for multi- users. Leave the "DOS Intercept" toggle OFF. Set the SL requirement at your discretion, but keep in mind that LNET-II has no SL-dependent security features except that it can require the system password to be entered before the program can be used [see page 32]. ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ RUNNING LNET-II ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ There are four command-line options recognized by LNET-II: /LOG, /LOMEM, /NOHI, and /NOINI. It is not necessary to specify a packet name or a network number, since all readable packets in network directories are detected and shown in a list. [Only the DATA\ directory and the network directories defined in INIT are searched for packets.] The /LOG option enables LNET-II's error log, which writes to ERRLOG.LN2 whenever the program's internal error handler is triggered. Some errors will cause the program to abort, while others are recovered internally and are not shown on the screen. LNET-II logs "invisible" internally-recovered errors as well as those which cause the program to abort. /LOG is essentially a debugging option and has limited use except in tracing errors. ────────────────────┤ LNET-II v1.00 User Manual - Page 2 ├───────────────────── The /LOMEM option conserves memory by not loading any BBSDATA.NET or REGIONS.DAT data. However, this does disable certain features, such as the ALT+N network node list [see page 19], the node detail displays, and the item text display. /LOMEM also forces the DROP_BAD_NODE option OFF [see page 29], because the absence of network node data in memory would cause ALL nodes to be "nonexistent" if DROP_BAD_NODE were to be left ON. The /NOHI option prevents LNET-II from using, or even trying to detect, any high-resolution text modes. In most cases, /NOHI will not be necessary. It was added during beta testing to eliminate a lockup on one tester's system. When /NOHI is active, LNET-II forces 25-line displays at all times and ignores all other video setting commands. [It would be a good idea to use /NOHI if LNET-II is being run remotely under DOORWAY.EXE.] The /NOINI option forces LNET-II to ignore all settings in WWIV.INI [except for REG_NAME and REG_CODE] and use the program's default settings instead. See page 26 for details on WWIV.INI settings. If you are running an unregistered copy of LNET-II, the program will display a logo screen and shareware notice and will execute a 15-second non-abortable countdown immediately after the initialization process. Registration will remove this delay. Registered copies still display a smaller a logo screen upon loading, but this has an abortable delay of only two seconds. Detection of available packets is automatic and limited to the paths shown in NETWORKS.DAT, or in the DATA\ directory for systems running WWIV 4.21 or older. Do not attempt to use LNET-II on any packet which does not follow the standard WWIV format, as LNET-II's validation and correction routines are designed exclusively for WWIV packets. Non-WWIV packets could be corrupted by LNET-II's validation algorithms. You will be given a list of available packets when the program loads, assuming at least one readable packet exists. Use the cursor bar to select a packet, then press ENTER. LNET-II will then perform a pre-scan of the selected packet in order to count the number of items in the packet and to determine the validity of each item. This process will generally take very little time except perhaps for extremely large packets. The first step in the pre-scan process checks the very first 24 bytes of a file to see whether it appears to be a valid net packet. If the first item does not appear to be valid, you will be given a warning notice indicating that the file might not be a valid WWIV network packet. Use caution on such files; load them ONLY if you are absolutely sure they contain valid items in the standard WWIV format. While a packet is being pre-scanned, LNET-II writes a temporary index file in the same directory as the selected packet. This file is used to index the starting byte locations of each item in the packet for extremely fast access and to allow easy forward/backward movement without having to load this data into memory. This has a secondary advantage of allowing a virtually unlimited packet size - LNET-II can handle packets up to 2,147,483,647 bytes in length. A packet this large could contain up to 89,478,485 items. LNET-II only needs to load the ────────────────────┤ LNET-II v1.00 User Manual - Page 3 ├───────────────────── index and header data into memory for one item at a time, so available memory will usually not be a concern even with such a huge packet. [Use the /LOMEM command line option if LNET-II needs more memory - see page 3 for more info.] The name of a packet's index file will be *.LN2, where the '*' wildcard repre- sents the packet name [such as DEAD.NET -> DEAD.LN2]. The same packet cannot be opened simultaneously by two instances of LNET-II. When checking for readable packets, LNET-II searches only the WWIV-type network directories given in NETWORKS.DAT, or the DATA\ directory if NETWORKS.DAT is not found. There is currently no provision for selecting packets which are not in a defined network directory. If no readable packets are detected, LNET-II will abort. A text message on the screen will indicate this condition when it occurs. [This is not an error con- dition! If there are no packets to read, there's no reason to continue.] Packet names which are detected by LNET-II are: CHECK.NET, DEAD.NET, LOCAL.NET, NETEDIT.DAT, *.OUT, P*.NET, P*.0??, S*.HLD, S*.NET, TEMP*.NET, and UNWANTED.NET. S*.NET packets are loaded only when the text represented by the '*' wildcard is purely numeric, and in the range 1 - 65535. This is because some older versions of WWIV used SA*.NET files for automatic e-mailing of sub rules to new sub- scribers. [The text after 'SA' would be the subtype.] So, S12345.NET would be considered a readable packet, while SA12345.NET would not. P*.NET and P*.0?? files can have any alphanumerics in place of the '*' wildcard; the '??' wild- cards in P*.0?? files are generally numeric and indicate the BBS instance under which the files were written. CHECK.NET is written by StripIt [Copyright (C) Matt Hucke]. UNWANTED.NET is written by AutoSend [Copyright (C) Cris McRae]. NETEDIT.DAT and *.OUT are packets for NetEdit [Copyright (C) D. Stussy / Black Dragon Enterprises]. TEMP*.NET files are written by NETWORK2 prior to calling a type 27 post-processor [type 27 items are extracted from LOCAL.NET and placed into a temporary packet for handling after NETWORK2 finishes with LOCAL.NET]. Z*.NET packets, which are compressed, are not readable by LNET-II and will not appear in the list of available packets. LNET-II detects compressed packets regardless of their names and will not attempt to load them. Z*.NET packets may be decompressed, if necessary, by following these steps: 1. Remove the ';' [packet compression] modifier from your CALLOUT.NET for the node receiving the Z*.NET packet. For instance, Z123.NET would be going to node @123. 2. Run NETWORK3.EXE to analyze the network. This will rename the Z*.NET packet to a P*.NET packet. [Rename the packet manually if you have an older version of the net software which does not rename pending packets after NETWORK3 analysis.] Make sure you use the .# net_num parameter to tell the NET*.EXE software which network to analyze [your first network would be number 0 - for example, NETWORK3 .0]. 3. Run NETWORK1.EXE. The renamed Z*.NET packet will be decompressed and analyzed, and its contents placed into an uncompressed S*.NET packet. The packet can then be read by LNET-II. To recompress the packet, restore the ';' modifier to CALLOUT.NET, then run NETWORK3 and NETWORK1 again. ────────────────────┤ LNET-II v1.00 User Manual - Page 4 ├───────────────────── LNET-II has context-sensitive help available at most points, which can be accessed with the F1 key. Online help requires the presence of the file LNET2.HLP, which must be located in the directory from which LNET-II was loaded. NOTE: If you are running a multi-instance BBS, it would be best to run LNET-II in the instance which processes your network mail. This is to prevent LNET-II and the BBS/NET## software from interfering with each other by attempting to process packets which may already be in use. LNET-II locks out all read/write access to all open packets and their index files until it closes those packets. Only one packet will be opened at any given time, except when a packet is being rewritten, in which case there will be two packets open during the rewrite process [the second packet is a temporary output file]. ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ THE MAIN SCREEN DISPLAY ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ ■ Main Screen Example ■ ╒════════╤══════════════════╤══════════════╤═════════════════════╕ │ Packet │ WhateverNet │ S905.NET │ 12,345 Bytes │ ╞════════╪══════════════════╧═══╤══════════╧═════════════════════╡ │ Item │ 5 of 10 │ ■■■■■■■■■■■■∙∙∙∙∙∙∙∙∙∙∙∙∙ 50% │ ╞════════╪══════════════════════╧════════════════════════════════╡ │ Type │ 26/0 [ ] Tagged [ ] Deleted [ ] Match │ │ Name │ Post By Name [SubType TESTSUB] │ │ Age │ 123 Hours │ │ Size │ 2468 Bytes │ │ Method │ 0 │ │ From │ #1 @1 [Dr. Quartlow's Funhouse] │ │ To │ 14 Nodes │ ╘════════╧═══════════════════════════════════════════════════════╛ The main display consists of a large window for item header data [see example above] and a smaller window for various text messages and prompts. At the top left corner of the main screen is the total megabytes free on the drive on which the current network's directory resides. At the top right is a clock/calendar [the clock "chimes" on the hour when sound is on; it can be turned off with CLOCK = OFF in WWIV.INI]. At the bottom of the main screen is a status bar which shows the current settings for Sound, Pause, MaxRez, and OptLines. In the header data window, LNET-II will show the network, name, and size of the current packet. Below this data is an indicator of the current item number, the total number of items in the packet, and a bar-graph display indicating your approximate position in the packet [by item count, not by byte count]. The bar graph is divided into 25 segments indicating 4% each. Below the packet data is a list of the header data from the current item. This list will show the item's main/minor type [or, if the item has been deleted, its original type if it is known], the name of the item, the size of the item in bytes [not including its destination list], the age of the item in hours, the ────────────────────┤ LNET-II v1.00 User Manual - Page 5 ├───────────────────── "method" of the item [meaning whether or not it has been DE* encrypted], the origin of the item, and the destination of the item. If the item is "stacked" for multiple destinations, the display will show a count of the destination nodes. BBS names are shown, if they are known, for the item's originating node and for the item's destination if there is only one. [If the /LOMEM option was used, the main screen will not show BBS names.] The ALT+L key can be used to view additional data on the destination(s) of any item [see page 18]. When CMI NetUp items are encountered, the main screen will show the update or diagnostic poll types/names from the CMI NetUp subheaders. If the item is a post, or an add/drop request for a sub, the display will show the subtype to which the item belongs. Other types are also shown by their full names - for instance, type 27/905 belongs to CMI NetUp on USLink, so LNET-II will display these items' names as "New External [CMI NetUp (USLink)]" when they are encountered. LNET-II also recognizes the types used by NetEdit, AutoSend, PackScan, Linker, K9NFX, FLINK, NFT, and DMail. Because networked games tend to use variable minor types, LNET-II will not try to recognize them except to display their main/minor types [generally main type 27]. NET37 will probably contain a new main type 28 specifically for networked games. The check boxes next to the item type indicate various flags for each item - "Tagged" indicates a tagged item, "Deleted" indicates an item which has been marked for deletion, and "Match" indicates an item which matched the most recent search criteria [see page 35]. The batch processes associated with item tagging are available only in registered copies. As of this writing, the current version of the WWIV network software is NET36. LNET-II recognizes all item types used by NET36 - main types 1 through 27. Note that main types 4, 10, 13, and 21 through 25 are not used by the net software, but they may be in use by other programs, such as Linker for main type 10. See Appendix A: WWIV Network Item Types [pages 41-45] for a listing of the allocated main/minor types used by NET36 and various external programs. Main types up to 64 will be passed by the net software even though it currently does not directly support or recognize any types above 27. Main types above 64 are considered invalid and will be deleted by LNET-II during the packet pre-scan. [The WWIV NET## software also does this; it is standard procedure.] Certain third-party network utilities use existing types for carrying their own data - for instance, it is somewhat common for programmers to use the 'SSM' main type 15 to transmit network updates or other material. LNET-II attempts to detect these items and display them by their owner names if they are known. As a rule, these items will have Method<>0, and the corresponding DE*.EXE file processes and deletes them before NETWORK2 can read them. If an item has a subheader which is specifically recognized by LNET-II, pressing ENTER will cause LNET-II to display all available data from that item's subheader. Press ENTER again to read the item's text, or press ESC to return to the main screen. NOTICE TO PROGRAMMERS: If you would like to have LNET-II recognize the main/ minor type(s) used by a network program you have written and display them by name, please submit this data to the author [see page 48]. It will be included in the next release of LNET-II. Please include any subheader declarations [C, QuickBASIC, or Pascal] if you would like LNET-II to display extended data on ────────────────────┤ LNET-II v1.00 User Manual - Page 6 ├───────────────────── your program's items. Networked games with variable sysop-defined minor types will not be included for specific recognition by LNET-II because their minor types are not fixed and might be reused on other networks or by other programs. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ F1: HELP ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ At the main screen, the F1 key will bring up a help screen listing the various command keys for LNET-II. While viewing the help screen, you may get extended help on any of the listed commands by typing that command. [This requires the LNET2.HLP file to be in the directory from which LNET-II was loaded - generally your main BBS directory.] Help is not available at input prompts. LNET2.HLP may be edited if desired; however, please study the format of the file before you attempt to edit it. If it is not properly formatted, LNET-II may not be able to read it correctly. DO NOT change any of the identifiers between the ^P/^Q [ASCII 16/17] markers! If you edit any help text, keep in mind that each line must be no longer than 76 characters. Save the file as plain ASCII only. DO NOT distribute modified versions of the LNET2.HLP file - any edited version is for your own use only. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ENTER: READING ITEM TEXT ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ While at the main screen, the current item's text can be viewed by pressing ENTER. The text viewer contains full support for ANSI, WWIVansi, pipe code color, and ANSI music. Because this feature can use quite a bit of memory when displaying the text of large items, the /LOMEM command line option disables it. NOTE: In the VGA 30-line and 60-line text modes, background colors cannot be displayed - these modes can accept only foreground color values, because it is necessary to switch the display into graphics mode in order to get 30 or 60 lines. [Text color #0 serves as the global background color in the VGA modes.] Blinking colors in these modes are remapped to solid colors. ANSI, WWIVansi, and pipe code colors may be affected and may not display exactly as expected. This note does not apply to the 25, 43, or 50-line text modes. Text will tend to display somewhat slowly in the 30-line and 60-line modes. Because the 30-line and 60-line modes are actually graphics screens, it might be necessary to load GRAFTABL.COM in order to see high ASCII characters in these modes. [GRAFTABL.COM is a TSR which maps high ASCII characters - above ASCII 127 - for display in graphics screen modes. It is not needed in the text-only 25, 43, and 50-line modes.] This generally applies to older versions of MS-DOS, prior to v6.00. If your version of DOS includes GRAFTABL.COM, it might be a good idea to load it in your AUTOEXEC.BAT if you intend to use the VGA 30-line or 60-line modes to read message text. ────────────────────┤ LNET-II v1.00 User Manual - Page 7 ├───────────────────── Item text CANNOT be displayed if any of the following conditions exist: ■ The item has a text segment length greater than 32K [32,767 bytes to be exact]. These will always be deleted [main type 65535] items; no valid undeleted item can have a text segment over 32K. Note that deleted items may be segments of corrupt data which may not display properly. ■ The item has a text segment length of 0. [Nothing to display; why try?] ■ The item belongs to a recognized third-party utility and contains only that program's subheader [for instance, an "empty" CMI NetUp item will have a text segment length of 20 bytes]. ■ The /LOMEM command line option was used. Some items may not use DE* encryption but may still contain binary data which cannot be properly displayed. Network file transfer utilities are a good example of this. LNET-II will attempt to display all text when possible; an error message will appear if an item's text cannot be displayed. Items with recognized subheaders will not have their subheaders' contents displayed as part of the message text. While an item's text is being displayed, the following keys may be used: P = Pause Display R = Re-read Item SPACE = Abort Display ALT+P = Toggle Screen Pause ALT+S = Toggle Sound [prompts, keystrokes, ANSI music, = ASCII 7 beeps, hourly clock "chimes"] LEFT/RIGHT = Read Previous/Next Item CTRL+LEFT/RIGHT = Search Previous/Next Item [Registered Only] ALT+LEFT/RIGHT = Read Previous/Next Tagged Item NOTE: For the sake of speed, keystrokes in the message text display are checked only between lines, not between characters. As such, LNET-II's response to key- presses might not always be immediate if it is displaying a long line of ANSI data. ANSI music is played in the foreground, so pressing ALT+S to toggle sound will stop music decoding as soon as the system's music buffer is empty. If the item being viewed is a post [types 3, 5, and 26], e-mail [types 2 and 7], SSM [type 15/0, method 0], or sub add/drop response [types 18 and 19], LNET-II will display a box header containing the item's number, its intended subtype or destination, title, author, and date. FIDO items will be indicated as such if they contain a ^D0FidoAddr: line. Here is a sample boxed header: ╔════════╤════════════════════════════════════════════════════════════════════╗ ║ Item # │ 7 of 9 ║ ║ Post │ TerraNET SubType QBASIC ║ ║ Title │ Yes, you CAN write WWIV packet readers in BASIC! ║ ║ Author │ Crossfire #1 @8854 ║ ║ Date │ Fri May 23 12:34:56 1997 ║ ╚════════╧════════════════════════════════════════════════════════════════════╝ ────────────────────┤ LNET-II v1.00 User Manual - Page 8 ├───────────────────── LNET-II uses WWIVansi codes to colorize this header. WWIVansi color #7 is used for the box borders, and the text is shown in color #4. These colors may be configured; see page 27 for details. The item text display will show a status bar at the bottom of the screen while the text is being displayed. The status bar looks like this: ║ [■] Pause │ [■] Sound ║ Line 52 of 100 ║ ■■■■■■■■■■■■■∙∙∙∙∙∙∙∙∙∙∙∙ 52% ║ "Pause" and "Sound" are indicated by a cyan block in the square brackets. When the screen is paused and LNET-II is waiting for a keypress, the "Pause" indi- cator will turn from solid cyan to blinking red. [NOTE: The indicator cannot blink in the VGA 30/60-line modes.] Status bar colors are not configurable. The right half of the status bar is a numeric and bar-graph indicator of how much of the item's text has been displayed so far [by line count]. Each block in the graph represents 4% of the total lines of item text. NOTE: Because the status bar uses the bottom line of the screen, any ANSI sequences which cause the cursor to move into this line or beyond it will be ignored. As a result, only the top "maxlines - 1" lines of any animated ANSI screen can be displayed. For LNET-II's purposes, animation is considered to be any ANSI data which moves the cursor vertically without using a CR/LF "newline" sequence. Non-animated ANSI sequences are handled in the same manner as plain text and will scroll normally. Only valid ANSI sequences are displayed; invalid sequences are simply ignored and are not shown on the screen. LNET-II does not support the ANSI codes which change screen modes or remap the keyboard. LNET-II's ANSI decoder is internal and does not require ANSI.SYS or an equivalent driver to be present. If screen pauses are toggled ON, and the message text contains a "clear screen" command such as an ASCII 12 character or an ANSI <esc>[J sequence, LNET-II will wait for a keypress before clearing the screen. This allows you to finish viewing the current screen page before proceeding to the next page. If the line of text being displayed has more than 80 printable characters before its end-of-line marker, LNET-II will attempt to compensate for this by adding one line to the "total lines" count of the item and updating its "lines displayed" counter when the line wraps around to column one. This helps LNET-II adjust for screen pauses on excessively long lines; however, on occasion, such lines still might not be handled correctly. The item text display will attempt to handle some of WWIV's control characters. The ^A "line wrap" flag is not displayed if it is immediately followed by a CR [ASCII 13] character; otherwise, it is shown. [NOTE: LNET-II does not attempt to produce true WWIV line wraps on ^A flags and does not perform word wraps.] ^B will center a line of text if it is the first character on the line [after the "optional line" prefix if one exists], the line does not contain ANSI, and the length of the line without color codes and CR/LF sequences is between 1 and 78. ^C and ^D characters [the "heart code" color and "optional lines" prefixes, respectively] are handled as WWIV would handle them if they are followed by a ────────────────────┤ LNET-II v1.00 User Manual - Page 9 ├───────────────────── digit from 0 to 9. ^D is treated as an "optional line" prefix only if it is the first character in a line of text and is immediately followed by a digit. The WWIV 4.24a ^O [ASCII 15] substitution codes are not supported; these will be displayed as-is without translation. The following characters CANNOT be displayed: ASCII 9, 10, 11, 12, 28, 30, and 31. ASCII 9 does not produce a tab, since tab widths can vary depending on the editor used to create a message, and attempting to translate them can produce incorrect results in the display - line wraps where they don't belong, and so on. ASCII 7 produces a short beep if sound is on. ASCII 8 and 29 are treated as backspaces. ASCII 12 clears the screen [if pause is ON, the program will wait for a keypress before clearing the screen, to allow you to finish viewing the current screen page]. All other characters are either displayed or treated as WWIV controls. WWIVansi translation can be configured by setting COLOR[n] = v in WWIV.INI - see page 27 for details. Pipe code color translation is not configurable. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ SPECIAL ITEM RECOGNITION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ LNET-II attempts to recognize a wide variety of network item types, both the standard types used by the NET## software and types used by third-party utilities such as CMI NetUp, K9NFX, FLINK, Linker, and so on. The subheader structures used by CMI NetUp, FLINK, Linker, and PackScan are supported and displayed. LNET-II does not currently recognize the K9NFX subheader, although it does recognize K9NFX's type 27/398. DMail [type 27/2121] and NFT are also recognized by name, but no subheader data is currently displayed. When CMI NetUp items are found, their subheader data is displayed on the main screen with the items' regular net header data. Other third-party items generally have their own subheader data screens in LNET-II, accessed by pressing ENTER at the main screen. You can then press ENTER again to view these items' text or press ESC to return to the main display. Main type 15, normally used for network SSM's, is also used by several other network utilities, including FLINK, NetSend, NetPing, and NFT. LNET-II will attempt to display these items by name when they are encountered, assuming their names have been encoded into the program. Third-party use of main type 15 is usually indicated by Method<>0 rather than Minor<>0. ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ COMMAND KEYS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ Navigation of the loaded packet is accomplished with the cursor keys [arrows, PgUp/PgDn, Home/End] and with various ALT-key and CTRL-key combinations. F1 may be used at the main screen to view a listing of available commands. While at the help screen, pressing any of the listed command keys will display extended help for that key, provided the LNET2.HLP file is available. ────────────────────┤ LNET-II v1.00 User Manual - Page 10 ├───────────────────── The ESC key at the main screen will activate LNET-II's pull-down menus if USE_PULL_DOWN is ON in WWIV.INI [see page 32]; otherwise, it will step back to the packet select list screen. Pull-down menus are available at the packet list, main screen, item list, node detail screen, destination list, sub info screen, and network list. LNET-II command keys are detailed on the following pages. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ CURSOR PAD ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ The PgUp/PgDn, Home/End, and arrow keys are used to step forward/back through the items in the packet. The functions of these keys are as follows: UP/DOWN = Forward/Back 1 Item RIGHT/LEFT = Forward/Back 10 Items PGUP/PGDN = Forward/Back 100 Items HOME = Jump To First Item END = Jump To Last Item CENTER "5" = Jump To Middle Of Packet ENTER = Read Text Of Item CTRL+LEFT/CTRL+RIGHT = Search Previous/Next [Reg'd Only] ALT+LEFT/ALT+RIGHT = Jump To Previous/Next Tagged Item If there are less than 10 items in a packet, Left/Right and PgUp/PgDn will result in jumps to the first/last items in the packet. The same applies to PgUp/PgDn if the packet has less than 100 items. The Up/Down arrow keys will wrap around from the first item to the last, or from the last item to the first; Left/Right and PgUp/PgDn do not wrap around to the beginning/end of the packet. The DELETE key does not delete the item currently being displayed; the ALT+D key [see page 14] performs this function. The CTRL+LEFT and CTRL+RIGHT keys require that a search form has been defined; see page 35 for details. Search features are available in registered copies only. The ALT+LEFT and ALT+RIGHT keys will jump to the previous/next tagged item IF at least one item has been tagged with the SPACEBAR or with the search form. [Items can be tagged with the spacebar at the main screen and in the ALT+I item list screen.] Note that these two commands can be accessed only from the gray secondary cursor pad on extended AT-class keyboards; they cannot be used on XT-class keyboards - which do not have the secondary cursor pad - or from the numeric/cursor keypad. ALT+LEFT and ALT+RIGHT can be used at the main screen, in the ALT+I item list screen, and while reading item text. The cursor pad keys will work regardless of whether NUM LOCK is on or off. ────────────────────┤ LNET-II v1.00 User Manual - Page 11 ├───────────────────── ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+K: SELECT PACKET ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ■ Packet List Screen Example ■ ╒══════════════════╤══════════════╤═══════════════╕ │ Network │ Packet │ Packet Size │ ╞══════════════════╪══════════════╪═══════════════╡ │ AlphaNet │ P1.002 │ 999 │ │ BetaNet │ P1-0-1.NET │ 12345 │ │ GammaNet │ S12345.NET │ 2468 │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ╘══════════════════╧══════════════╧═══════════════╛ When ALT+K is pressed at the main screen, you will be given a list of readable packets, shown by network, filename, and packet size. [The list is sorted by network names and packet names.] Use the cursor bar to select a packet, then press ENTER. LNET-II will then load the packet by pre-scanning it and creating a temporary index file. Press ESC in the packet list screen to exit to DOS. If any items in the current packet have been marked for deletion but may be recoverable, LNET-II will ask you to confirm whether you wish to change packets. If you answer "Yes" at this prompt, the current packet will be rewritten, skipping over the marked items and making them permanently deleted. If the resulting new packet is empty, its name will be removed from the list of available packets and the empty packet will be deleted. If no more readable packets exist, LNET-II will exit to DOS. When the ALT+K key is pressed, LNET-II will unlock and close the current packet before displaying the packet list. Note that this might cause the NET## soft- ware in another instance of the BBS to begin analyzing the packet, making it unavailable to LNET-II. LNET-II might also lock a packet which the BBS is trying to process. For these reasons, it is advisable to run LNET-II only in the BBS instance which normally processes network callouts and mail, to prevent one process from interfering with the other. Some packets belong only to one instance of the BBS and are not processed until the current user logs off. For instance, a packet named P0.002 belongs to BBS instance #2 and will not be processed by the BBS until the user on instance #2 logs off, at which point the packet is renamed. It is usually safe to load these packets, since interference between the BBS and LNET-II is unlikely, but it is still advisable to load such a packet only from within the BBS instance which wrote it. ────────────────────┤ LNET-II v1.00 User Manual - Page 12 ├───────────────────── ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+I: SELECT ITEM ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ■ Item List Screen Example ■ ╒═════╤══════════╤══════════╤════════╤════════════╤════════════╤════════╕ │ Tag │ Item # │ Type │ From │ To │ Age │ Size │ ╞═════╪══════════╪══════════╪════════╪════════════╪════════════╪════════╡ │ │ 1 │ 26/0 │ @11111 │ 4 Nodes │ 21 Hours │ 987 │ │ │ 2 │ 27/905 │ @1 │ 11 Nodes │ 19 Hours │ 1111 │ │ │ 3 │ 26/0 │ @11111 │ 4 Nodes │ 18 Hours │ 1234 │ │ │ 4 │ 16/0 │ @1234 │ @2468 │ 4 Hours │ 8 │ │ │ 5 │>26/0 │ @1234 │ 4 Nodes │ 2 Hours │ 1357 │ │ │ 6 │ 2/0 │ @1234 │ @24680 │ 2 Hours │ 12345 │ │ │ 7 │ 26/0 │ @11111 │ 4 Nodes │ 1 Hour │ 9948 │ ╞═════╧══════════╧══════════╧════════╧════════════╧════════════╧════════╡ │ Post By Name [SubType QBASIC] │ ╘═══════════════════════════════════════════════════════════════════════╛ When ALT+I is pressed at the main screen, you will be given a list of the items in the packet. This list will show the item numbers, their main/minor types, origin nodes, destination nodes [by number for single destinations, or a count of nodes for stacked items], sizes, and ages in hours. The current item will be at the top of the list, or as close to the top as possible, and indicated by a small arrow. Use the cursor pad keys to select an item, then press ENTER. LNET-II will then jump to that item and display its header data. Press ESC to exit this list without selecting a new item. The "Tag" column will display up to three different flags for each item - the letters T, D, and/or M. 'T' indicates a tagged item. 'D' indicates an item which has been marked for deletion. 'M' indicates an item which matched the most recent search criteria. The small window at the bottom of this list will display the name of the item indicated by the cursor bar. Whereas the item list would only show, for example, "19 Nodes" if an item is stacked to go to 19 different nodes, placing the cursor bar on that item and pressing ALT+L would enable you to see a summary of the data for all 19 of those nodes. This list will show the node numbers, BBS names, next hops, and number of hops. Use the cursor keys to scroll through this list. Press ENTER on a node to see ALL of its data, including its flags and identifiers from the BBSLIST.* files. [NOTE: The /LOMEM command line option disables this feature!] Pressing ALT+F on an item in the list will let you view the complete BBS data for the selected item's originating node. [/LOMEM disables this feature.] When an item in this list screen is more than 999 hours old, its age will be shown as +999 Hours. The main screen will show the item's true age. If an item appears to be less than zero hours old - which can happen when an item is being moved westward across one or more time zones - its age will be shown as 0 Hours. ────────────────────┤ LNET-II v1.00 User Manual - Page 13 ├───────────────────── As a general rule, older items will tend to be at the top of the list, and newer items will tend to be at the bottom. NOTE: An incorrect nh.daten timestamp value may make an item appear far older than it actually is, and often older than it could possibly ever be. The fault lies with the program which wrote the item. K9NFX is one example of a program which does not write the nh.daten timestamp correctly. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+G: GO TO ITEM # ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ The ALT+G key is similar in purpose to the ALT+I key, except that ALT+G prompts you for the number of the item you wish to read instead of having you select an item from a list. This can simplify navigation of very large packets, since it is a direct jump to a specific item number. Enter a number in the range 1 to 'max items' at the prompt, or press ENTER on an empty line to abort. Out-of- range entries will be ignored. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+D: DELETE ITEM ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ALT+D allows you to delete the item which is currently being displayed. Note that the item IS NOT physically removed from the packet when the ALT+D key is pressed; rather, LNET-II simply places a flag in the packet index file to show that the item has been marked to be deleted when the packet is closed. If any items in the current packet are deleted or marked to be deleted, and you load a new packet, rewrite the current packet with the ALT+C command key [see page 16], or exit LNET-II, the current packet is rewritten without the deleted items, making them permanently deleted. If an item is marked for deletion by LNET-II, it may be recovered -IF- you do not change packets or exit LNET-II before trying to recover the item. Provided an item was not already deleted [main type 65535] when the packet was loaded, it can be undeleted as long as the packet remains open. WARNING: It generally against most networks' policies to delete items which do not belong to you. Use discretion and common sense when deleting items with LNET-II! The program is not intended to be used to interfere with the normal flow of network traffic. ────────────────────┤ LNET-II v1.00 User Manual - Page 14 ├───────────────────── ┌──────────────────────────────────────────────────────────────────────────────┐ │░ CTRL+D: MASS DELETE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ■ THIS FEATURE IS AVAILABLE IN REGISTERED COPIES ONLY ■ The CTRL+D key will allow you to perform a mass-delete on a range of items in the packet. You will be prompted to enter the starting and ending item numbers of the range you wish to delete, then to confirm your selection with a Yes/No response. If you are registered and have defined a search form, you will be given the option to delete only those items which match the search criteria. Note that these items will still be recoverable as long as you do not load a new packet, use the ALT+C command key to rewrite the current packet [see page 16], or exit LNET-II. There are no defaults for these prompts - pressing ENTER on the "Starting Item" prompt would NOT mean "start at the current item." You must enter the numbers directly, even if you wish to start deleting at the current item or end at the last item. This is done as a safety precaution. Simply pressing ENTER at either prompt, without entering any numbers, tells LNET-II to cancel the mass- delete operation. The ending item number may be less than the starting number; in this case, LNET-II will delete from the starting item backward instead of forward. The starting item number does not necessarily have to be the current item number, but of course it must be between 1 and the total number of items in the packet. If invalid numbers are entered, no items will be deleted. If you exit LNET-II or load a new packet, or use the ALT+C key to clean up the packet, these items will be permanently deleted. When deleted items exist in the current packet, LNET-II rewrites the packet on change, exit, or cleanup, skipping over these items. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+T: TRUNCATE PACKET ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ALT+T allows you to truncate a packet, effectively deleting every item from the current item to the end of the packet. You will be prompted for a double "Yes/ No" confirmation before LNET-II will truncate the packet. While other packet readers may truncate a packet by marking the current item as "deleted" and giving its size as the number of remaining bytes in the packet - effectively making one large "deleted" item - LNET-II individually marks each item for deletion in the index file. This allows those items to be recovered as long as the packet is not rewritten. If you exit LNET-II or load a new packet, or use the ALT+C key to clean up the packet, these items will be permanently deleted. When deleted items exist in the current packet, LNET-II rewrites the packet on change, exit, or cleanup, skipping over these items. ────────────────────┤ LNET-II v1.00 User Manual - Page 15 ├───────────────────── ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+R: RESTORE ITEM ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ALT+R allows you to recover or "undelete" an item which LNET-II has marked to be deleted, provided the packet is kept open. LNET-II CANNOT RECOVER ITEMS WHICH WERE ALREADY MARKED AS DELETED WHEN THE PACKET WAS LOADED, and it will not allow direct editing of any item's header data. The main screen will indicate whether an item can be recovered. If an item has an indicator in the "Deleted" check box but shows a full list of header data, the item CAN be recovered. If the main screen shows the item as Main Type 65535 and its name as <<< Deleted >>>, then the item CANNOT be recovered. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ CTRL+R: MASS RESTORE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ■ THIS FEATURE IS AVAILABLE IN REGISTERED COPIES ONLY ■ The CTRL+R key is the functional opposite of the CTRL+D "Mass Delete" key - it allows recovery of a range of items, as long as those items were not already deleted [main type 65535] when the packet was loaded. You will be prompted to enter the starting and ending item numbers of the range you wish to restore. LNET-II CANNOT RECOVER ITEMS WHICH WERE ALREADY MARKED AS DELETED WHEN THE PACKET WAS LOADED, and it will not allow direct editing of any item's header data. There are no defaults for these prompts - pressing ENTER on the "Starting Item" prompt would NOT mean "start at the current item." You must enter the numbers directly, even if you wish to start restoring at the current item or end at the last item. Simply pressing ENTER at either prompt, without entering any num- bers, tells LNET-II to cancel the mass-restore operation. The ending item number may be less than the starting number; in this case, LNET-II will restore from the starting item backward instead of forward. The starting item number does not necessarily have to be the current item number, but of course it must be between 1 and the total number of items in the packet. If invalid numbers are entered, no items will be restored. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+C: CLEAN UP PACKET ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ The ALT+C key forces LNET-II to "clean up" the current packet. This process in- volves rewriting the packet, skipping over any items which have been previously deleted or marked for deletion, and removing any references to nonexistent nodes if DROP_BAD_NODE is set ON in WWIV.INI [see page 29]. Note that this makes any marked items permanently deleted. ────────────────────┤ LNET-II v1.00 User Manual - Page 16 ├───────────────────── After the packet has been rewritten, LNET-II will reload the packet if it still contains readable items, return to the packet select screen if the rewritten packet has been completely deleted, or exit to DOS if no more readable packets exist. The WWIV.INI option DROP_BAD_NODE determines whether references to nonexistent nodes will be removed from items' destination lists when a packet is being re- written. If an item has only one destination, and that node does not exist, this will cause the item to be deleted. If an item has a destination list, the entire list will be checked, and nonexistent nodes will be removed from it. The item will be deleted if its entire destination list consists of nonexistent nodes. DROP_BAD_NODE is OFF by default; it can be turned on by setting DROP_BAD_NODE = ON in WWIV.INI. When DROP_BAD_NODE is OFF, items will be rewritten as-is with no checking or modification of their destinations. DROP_BAD_NODE does not affect references to nodes which do exist but are isolated, nor does it affect nonexistent originating nodes. The /LOMEM command line option forces DROP_BAD_NODE = OFF! This is because /LOMEM tells LNET-II not to load any BBSDATA.NET files. With this data not resident in memory, LNET-II would think ALL nodes were "nonexistent." This would cause every last item in a packet to be permanently deleted when ALT+C is used. So, to prevent this, /LOMEM must force DROP_BAD_NODE = OFF. It cannot be turned on while /LOMEM is active. Please note that having the DROP_BAD_NODE option set ON can cause an entire packet, particularly a DEAD.NET packet, to be completely deleted if it consists entirely of items for nonexistent nodes. LNET-II will inform you when a packet has items for nonexistent nodes and will ask you to confirm whether you wish to proceed with closing and/or rewriting the packet. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+F: VIEW ITEM ORIGIN ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ■ Node Data Screen Example ■ ╒═════════════════════════════════╤════════════════════════════╕ │ Network: FishNet │ Item #123 of 456 │ │ Node Number: @12345 Group: 2 │ Hops: 5 Next: @2468 │ ╞═══════════╤═════════════════════╧════════════════════════════╡ │ BBS Name │ Starbase Orion │ │ BBS Phone │ 213-555-2075 │ │ Region │ Los Angeles, California │ ╞═══════════╧═══╤═══════════════╤═══════════════╤══════════════╡ │ Baud: 33600 │ [■] Server │ [ ] FIDO │ [ ] Compucom │ │ [ ] NC │ [ ] End Node │ [ ] Telebit │ [■] v.32 │ │ [■] GC (3) │ [■] Fax │ [ ] USR HST96 │ [■] v.32bis │ │ [■] AC (213) │ [ ] PCPursuit │ [ ] HayesVS96 │ [■] v.34 │ ╘═══════════════╧═══════════════╧═══════════════╧══════════════╛ ────────────────────┤ LNET-II v1.00 User Manual - Page 17 ├───────────────────── ALT+F allows you to view details on the originating node of an item - node number, group, hops, next hop, name, phone, region, and BBSLIST.* identifier flags. Identifiers are taken from bitmaps in the BBSDATA.NET file. Region information is taken from your DATA\REGIONS.DAT file, which is read into memory and sorted when LNET-II first loads. [LNET-II does not support the data files used by "extended region info" mods.] The ALT+F key may be used either at the main screen or in the ALT+I item list. When viewing a node's data, the ALT+H key can be used to display the data for the next hop if the node is more than one hop away and is reachable. NOTE: The /LOMEM command line option disables this feature! ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+L: VIEW DESTINATIONS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ■ Destination List Screen Example ■ ╒════════════════════════════════════════════════════════════════════╕ │ Destination Nodes - Item #5 of 10 4 Nodes │ ╞════════╤══════════════════════════════════════════╤════════╤═══════╡ │ Node │ BBS Name │ Next │ Hops │ ╞════════╪══════════════════════════════════════════╪════════╪═══════╡ │ @2614 │ Airlane BBS │ @123 │ 5 │ │ @4427 │ Telekon │ @123 │ 4 │ │ @3440 │ The Joy Circuit │ @123 │ 3 │ │ @9948 │ Down In The Park │ @9948 │ 1 │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ╘════════╧══════════════════════════════════════════╧════════╧═══════╛ The main screen and item list can show only the node numbers of items' desti- nations, or a count of destinations when an item is "stacked." For instance, if an item has 19 destinations, LNET-II will show "19 Nodes" for that item. The actual node number will be shown if an item has only one destination. [Per WWIV network specifications, no valid item can have more than 4096 desti- nations. LNET-II will delete items with more than 4096 destination nodes.] The ALT+L key brings up a more detailed list of the items' destination(s), showing the node numbers, BBS names, next hops, and numbers of hops. Use the cursor keys to scroll through this list. Press ENTER on a node to view its complete data, or press ESC to exit back to the item list or main screen. The ALT+L node list can be used regardless of whether an item is stacked or has a single destination. It can be used from the main screen and "Select Item" list [ALT+I at the main screen]. ────────────────────┤ LNET-II v1.00 User Manual - Page 18 ├───────────────────── If an item has more than one destination, and the ENTER key is used to display the full BBS data for a node in the item's destination list, the LEFT/RIGHT arrows can then be used to cycle through the full BBS data for all nodes in the list without having to exit back to the destination list screen. If the current packet has more than one item, then pressing LEFT/RIGHT in the destination list screen will list the destination(s) of the previous/next item. If the STICKY_LIST option is ON in WWIV.INI [see page 32], these keys will also change the current item number, affecting your position in the main screen and "item select list" displays. The ALT+F key at the main screen and item list screen displays the full BBS data for an item's originating node. ALT+N [see page 19] displays the full network node list. NOTE: The /LOMEM command line option [see page 3] disables the BBS name, "next hop," and "number of hops" displays in the item list screen. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+N: VIEW NETWORK NODE LIST ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ Whereas the ALT+L key displays the destination node(s) of the current item, the ALT+N key will allow you to view the entire network list. The cursor keys per- form the same functions as when viewing an item's destination list. Pressing ENTER on a node will display its complete data - this includes all of the usual number, name, phone, group, region, and hops/next data, and also includes all of its flags from the BBSLIST.* files. Press ESC to exit back to the main screen. If a node is reachable and is more than one hop away, pressing ALT+H while viewing that node's data will display the data for the next hop to that node. When viewing the full BBS data for a node in the network list, the LEFT/RIGHT arrow keys can be used to display the full BBS data for the previous/next node in the list without having to exit back to the network list screen. NOTE: The /LOMEM command line option disables this feature. This is because /LOMEM prevents BBSDATA.NET from being read, so node data is not available. ────────────────────┤ LNET-II v1.00 User Manual - Page 19 ├───────────────────── ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+U: VIEW SUB INFO ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ■ Sub Info Screen Example ■ ╒═════════════════════════════════════╤═════════════════╤═════════════╕ │ Sub Info Item #111 of 123 │ SubType QBASIC │ Host @3800 │ │ ┌───────────┬─────────────┬───┴───────┬─────────┴┬────────────┤ ├───────┤ [■] Gated │ [■] AutoReq │ [ ] NoTag │ [ ] ANSI │ [■] NetVal │ │ Topic └───────────┴─────────────┴───────────┴──────────┴────────────┤ │ QuickBASIC Forum [QB/PDS Programming] │ ╘═════════════════════════════════════════════════════════════════════╛ If the currently selected item belongs to a sub [main types 3, 5, 16 to 19, and 26], then the ALT+U key can be used to display the data for that sub - subtype, host, topic, and flags [AutoReq, ANSI, NoTag, Gated, and NetVal]. This data is read from the network's SUBS.* files. ALT+U can be used either at the main screen or in the ALT+I item select list. LNET-II assumes that the SUBS.* files follow the standard format, with the subtype in column 1, the host in column 9, flags in column 15, and the sub topic in column 21. A type 20/1 SUBS.INF "pong" returns data in this format. If the SUBS.* files do not follow this format, then LNET-II might not be able to find a sub's info or display that data correctly. If a sub cannot be found in the SUBS.* files, or no SUBS.* files exist, then LNET-II will display an error message. If a sub CAN be found in SUBS.* and be displayed, then the ALT+H key can be used to view the full node data for the sub host [provided the host exists and the /LOMEM option was not used]. NOTE: Occasionally, different subs on the same network use the same subtype. LNET-II will attempt to determine the correct entry in SUBS.* by checking the listed host node against the item's origin or destination, depending on the item's main type: Main Types 5, 16, 17: Assumed to be TO the sub host [ToSys = Host] 18, 19: Assumed to be FROM the sub host [FromSys = Host] 3, 26: May be from any node - first match is displayed ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+E: EXTRACT MESSAGE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ The ALT+E key allows you to extract the current message to a text file IF that message is a post or e-mail, is not deleted, and is not DE* encrypted. [Posts and e-mails are main types 2, 3, 5, 7, and 26.] When the ALT+E key is pressed, you will be prompted to select whether the extracted text is to go into the GFILES directory or into the current network's directory. [No other directories may be selected; the generated file can be ────────────────────┤ LNET-II v1.00 User Manual - Page 20 ├───────────────────── moved to another directory later if desired.] After the directory is selected, you will be prompted for a filename. If the file already exists, you will have the option to append to it, overwrite it, or cancel the extraction. After the filename is entered, you will be given several "yes/no" prompts to select the formatting of the extracted text: INCLUDE HEADERS? This determines whether the extracted text will also include the "Title / Author / Date" information from the post or e-mail. This information will be boxed if it is written, in the same way that it appears on the screen when the item text is viewed. INCLUDE OPTIONAL LINES? This determines whether any existing "optional lines" in the message will be written. NOTE: The "optional lines" value [see page 23] has no effect on which optional lines will be written and which of them will not be written. If you answer "No" at this prompt, none of the optional lines will be written. If you answer "Yes," ALL of them will be written, including any NET33+ routing stamps. Optional lines will be written without their ^D# prefixes. INCLUDE WWIVANSI / PIPE CODE COLOR? If you answer "No" at this prompt, LNET-II will strip any existing WWIVansi and pipe code colors from the message text. Note that this does not apply to pure ANSI color codes, which are always written as-is. [If Registered]: EXTRACT ONLY ITEMS MATCHING DEFINED SEARCH FORM? If you have registered LNET-II, are performing a mass extract [see below], and a search form is currently defined [see page 35], you may force LNET-II to extract only those items which match the defined search criteria. For instance, if you have 26 entered in the "MainType" field and QBASIC entered in the "Subtype" field, only posts belonging to subtype QBASIC will be extracted. Note that the search form must be set to find posts and/or e-mails for this to work, since those are the only items which LNET-II will extract. [If Registered]: EXTRACT ONLY TAGGED ITEMS? If you have registered LNET-II, are performing a mass extract [see below], and have tagged one or more items, you will have the option to extract only items which have been tagged. If you answered YES to the "extract only matching items" prompt above, then answering YES to this prompt will tell LNET-II to extract only those items which have been tagged AND match the search criteria. See page 38 for more details on using the item tagging features. PROCEED USING THESE SETTINGS? Answer "yes" or "no" to proceed with the text extraction using the options you have defined. NOTE: LNET-II does not extract messages to net packet formats - it writes them to TEXT FILES ONLY. LNET-II will attempt to determine whether the specified output file is a net packet and will warn you if the file appears to be a packet. If this does appear to be the case, LNET-II will NOT extract to that file. This is to avoid accidental corruption or loss of valid packets. ────────────────────┤ LNET-II v1.00 User Manual - Page 21 ├───────────────────── ┌──────────────────────────────────────────────────────────────────────────────┐ │░ CTRL+E: MASS EXTRACT ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ■ THIS FEATURE IS AVAILABLE IN REGISTERED COPIES ONLY ■ This works in the same way as the "Extract Message" command above, except that it allows extraction of multiple messages. After responding to the formatting prompts, you will be asked to enter the starting and ending numbers of the range of items you wish to extract. The ending item number may be less than the starting number; in this case, LNET-II will simply extract from the starting item backward instead of forward. The starting item number does not necessarily have to be the current item number, but of course it must be between 1 and the total number of items in the packet. If invalid numbers are entered, no items will be extracted. When a valid range of numbers is entered, LNET-II will search that range for any items which can be extracted [undeleted and unencrypted posts and e-mails, main types 2, 3, 5, 7, and 26]. If any are found, LNET-II will write them to the selected output file using the given formatting options. If the starting and ending item numbers are not equal, LNET-II will ask you whether you wish to individually confirm each item. If you answer "No" at this prompt, LNET-II will extract all post/e-mail items in the specified range without prompting you for confirmation. If you answer "Yes" at this prompt, LNET-II will display each item's header data and ask you whether you wish to extract that item. [You will not be able to read the items' text at the "Yes/No" prompt.] If a search form has been defined [see page 35], LNET-II will ask you if you want to extract only those items which match the defined search criteria. Keep in mind that only posts and e-mails can be extracted, regardless of the main type specified in the search form, but the search form must be set to find posts and/or e-mails. A mass extract of tagged items can be performed at the F3 "Tag Commands" menu - see page 38 for further details. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+X: EXIT ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ Use ALT+X to quit LNET-II and return to DOS. You will be prompted as to whether or not you actually want to exit; answer [Y]es or [N]o at the prompt. If any items in the current packet have been marked for deletion but may be recoverable, LNET-II will inform you of this fact and ask you to confirm whether you wish to exit LNET-II. If you exit, and the current packet has items which are marked to be deleted, the packet will be rewritten, skipping over the marked items and making them permanently deleted. ────────────────────┤ LNET-II v1.00 User Manual - Page 22 ├───────────────────── Packets are not rewritten on exit if they do not contain deleted items and do not contain references to nonexistent nodes; use the ALT+C command [see page 16] if you wish to force a packet to be rewritten. If the DROP_BAD_NODE option is ON, and the packet contains references to one or more nonexistent nodes, you will have the option to edit the list of nonexistent nodes referenced in the packet before the packet is rewritten [see page 39]. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+O: TOGGLE OPTIONAL LINES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ "Optional Lines" are lines in a post or e-mail which may or may not be shown to the reader. These lines begin with a ^D [ASCII 4] prefix character, followed by a digit from 0 to 9. The NET33+ routing stamps, for instance, begin with a ^D0 prefix. The user signatures and "WWIVEDIT.DIV" file written by WWIVedit usually begin with a ^D9 prefix. The "BBS tags" often added to posts generally begin with a ^D8 prefix and work downward to ^D1 at the bottom. When optional lines are toggled OFF in LNET-II, any lines with a ^D# prefix will be skipped over and not displayed when a message's text is read. Users can set the "optional lines" value to determine which optional lines will be displayed. [See "Set Optional Lines Value" below.] The default value for this setting is 0, which means that ALL optional lines will be shown if they are toggled on. If the setting is 1, then only those optional lines beginning with ^D1 or higher will be shown. This would have the effect of not displaying NET33+ routing stamps but generally including all other optional lines - as a rule, these will be user signatures and BBS tags added by such editors as WWIVedit. Optional lines are ON by default. They can be turned off by setting OPT_LINES = OFF in WWIV.INI. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ CTRL+O: SET OPTIONAL LINES VALUE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ When "Optional Lines" are toggled ON [see above], LNET-II will display any optional lines if their prefix is equal to, or greater than, the value set with the CTRL+O key. For instance, if this value is set to 1, then any optional lines having a prefix of ^D1 through ^D9 will be displayed, but any lines with a prefix of ^D0 would be ignored. If it is set to 0, then all optional lines will be displayed, including any NET33+ routing stamps. A setting of 1 would tend to display all optional lines EXCEPT the NET33+ routing stamps. The allowable range for this setting is 0 to 9. Note that a setting of 9 will cause LNET-II to display only those optional lines beginning with ^D9 - as a rule, these lines will usually be just the user signature and "WWIVEDIT.DIV" added by WWIVedit and will not include the BBS tag. Use the ALT+O key to turn optional lines off completely. ────────────────────┤ LNET-II v1.00 User Manual - Page 23 ├───────────────────── The default "optional lines" value is 0 [all lines shown]. This default can be changed by setting OPT_VAL = n in WWIV.INI. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+P: TOGGLE PAUSE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ The ALT+P key toggles screen pauses when viewing item text. It can be used either at the main screen or in the item text display. When pause is active, LNET-II will execute a pause after every full screen of text. [The item display routine generally will not pause after every 'x' lines of ANSI data if that data has not caused the display to scroll.] A screen pause will also be executed if 'pause' is on and the text being displayed contains a 'clear screen' command such as an ASCII 12 or an ANSI <esc>[J sequence. Pause is ON by default. It can be turned off by setting PAUSE = OFF in WWIV.INI. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+S: TOGGLE SOUND ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ The ALT+S key toggles sound when displaying item text, confirming keystrokes, decoding ANSI music, and "chiming" the clock/calendar at the top of the hour. It can be used either at the main screen or in the item text display. When sound is ON while item text is being displayed, ANSI music will be decoded and played, and ASCII 7 characters will produce a beep. The status bar will indicate "Sound On" with a solid cyan block. If ANSI music is being played, this block will change to a blinking yellow musical note. [The "musical note" indicator will not blink in the VGA 30-line and 60-line text modes.] When sound is off, any ASCII 7 characters in an item's text will be ignored and will not produce a beep. When ANSI music is present but is not being played, the "Sound" indicator on the status bar will change to a solid cyan musical note, but no sound will be produced. This is done only to provide a visual indication that ANSI music sequences are present. Sound is ON by default. It can be turned off by setting SOUND = OFF in WWIV.INI. ────────────────────┤ LNET-II v1.00 User Manual - Page 24 ├───────────────────── ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+V: TOGGLE MAXREZ VIDEO ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ LNET-II can display item text in 25, 30, 43, 50, or 60-line mode, depending on the type of display being used. The program automatically determines which modes are available by testing for them during the initialization process. [This may cause a very brief period of visible display blinking before the LNET-II logo screen is displayed; this is a normal side-effect of the video mode detection process.] When "MaxRez" is active, the main screen's status bar will show an indicator and display the mode being used. ALT+V toggles between plain 25-line mode and the selected high-resolution mode [see next page]. When more than one of the above modes are available, the CTRL+V key can be used to rotate among the available modes [see below]. Unlike ALT+P and ALT+S, the ALT+V and CTRL+V keys cannot be used while an item's text is being displayed; they can be used only at the main screen. Changing video modes DOES NOT affect the GUI screens, which are always shown in 25-line mode. "MaxRez" applies only to the message text display [ENTER at the main screen]. "MaxRez" is OFF by default. It can be turned on by setting SCR_MAX_REZ = ON in WWIV.INI. The /NOHI command line switch will force LNET-II to completely ignore all high- resolution text modes, as well as all command keys and WWIV.INI settings related to video modes. /NOHI forces 25-line mode for all displays - it is a trouble- shooting option which was added during beta testing to cure a lockup on one tester's system. If you experience lockups when using LNET-II, try running it with the /NOHI switch [see TECHNOTE.TXT in the LN2V100 archive]. /NOHI might also be necessary when running LNET-II under DESQview if VIDRAM is loaded. NOTE: The VGA 30-line and 60-line displays are actually graphics modes. Text will tend to display slowly in these modes. Older versions of DOS [prior to 6.00] might require you to load GRAFTABL.COM in your AUTOEXEC.BAT before you can display high ASCII characters [codes 128 to 255] in the 30-line and 60-line text modes. Support for high ASCII in graphics screens appears to be internal to newer versions of DOS. [If you see garbage where there would normally be high ASCII characters when an item's text is being displayed, you do need to load GRAFTABL.COM.] ────────────────────┤ LNET-II v1.00 User Manual - Page 25 ├───────────────────── ┌──────────────────────────────────────────────────────────────────────────────┐ │░ CTRL+V: SELECT VIDEO MODE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ The CTRL+V key selects which video mode to use when displaying message text if your display is at least EGA and supports the 30, 43, 50, and/or 60-line modes. As a rule, the 30, 50, and 60-line modes require VGA. 43-line mode is generally available on EGA and VGA displays. If your display is not at least EGA, LNET-II probably will use only the 25-line mode. LNET-II rotates among the available video modes when CTRL+V is pressed. The current video mode is shown on the status bar at the bottom of the screen. CTRL+V does not affect the GUI screens, which are always shown in 25-line mode. If "MaxRez" is off [see above], CTRL+V will be ignored. Users can set the default video mode by using VID_DEFAULT = v in WWIV.INI, where 'v' equals 25, 30, 43, 50, or 60. Unsupported or invalid mode values will be ignored and will force 25-line mode. If the /NOHI command line option is used when LNET-II is loaded, only the standard 25-line video mode will be available - the ALT+V and CTRL+V command keys will be ignored, as will the SCR_MAX_REZ and VID_DEFAULT options in WWIV.INI. ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ WWIV.INI SETTINGS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ If you have registered, you will have received your personal registration code from the author. This would be entered in your WWIV.INI file as follows: [LNET2] ; Start of LNET-II configuration block REG_NAME = your user name REG_CODE = your registration code If LNET-II determines that the entered code is valid, it will allow usage of various program features which are locked out in unregistered copies and will disable the initial 15-second countdown when the program is loaded. If WWIV.INI does not exist when LNET-II is loaded, or does not contain the [LNET2] configuration block, the file will be created if necessary and the program's default settings will be written. WWIV.INI settings are shown in detail below. Spacing and capitalization for LNET-II's settings in WWIV.INI are generally not significant except in the REG_NAME value. Options may be listed in any order. Comments with a ';' semicolon prefix are allowed. An option which is ON can be specified as Y, YES, ON, 1, or TRUE. Conversely, an option which is OFF can be specified as N, NO, OFF, 0, or FALSE. This manual uses the ON/OFF convention; LNET-II uses ON/OFF when writing its settings. ────────────────────┤ LNET-II v1.00 User Manual - Page 26 ├───────────────────── The ALT+W key can be used at the main screen to save the current settings to WWIV.INI. When LNET-II writes its settings to WWIV.INI, it groups them by related purposes for easier management, but again, they can be listed in any order. All settings except REG_NAME and REG_CODE can also be configured via the F2 "config menu" at the main screen. LNET-II's WWIV.INI settings are as follows: Option : CBAR_BACK = n Default: 7 [White] Sets the background color of the cursor bar, used in list screens. The default value is 7 [white], with a default foreground of 1 [blue]. Allowable range is 0 [black] to 7 [white]. See the color chart below. Option : CBAR_FORE = n Default: 1 [Blue] Sets the foreground color of the cursor bar, used in list screens. The default value is 1 [blue], with a default background of 7 [white]. Allowable range is 0 [black] to 15 [bright white]. See the color chart below. NOTE: The CBAR_FORE and CBAR_BACK colors are also used for text input prompts. However, they do NOT apply to the pull-down menus - these have their own color values for highlighting selected items [see page 30]. Option: CLOCK = ON | OFF Default: On Determines whether LNET-II will display its clock/calendar. When it is ON, the clock will "chime" at the top of the hour if sound is also on. When it is OFF, the clock will not be displayed and will not chime. It may be a good idea to turn the clock/calendar off if you are running LNET-II remotely under DOORWAY to prevent buffered modems at low connect rates from becoming lagged with constant clock/calendar updates. Option : COLOR[n] = v Default: See next page Changes the default colors when translating WWIVansi in the item text display. Examples: COLOR[0] = 9 ; Sets color #0 to light blue on black COLOR[6] = 12 ; Sets color #6 to light red on black Allowable ranges are 0 to 9 for 'n' and 0 to 255 for 'v'. Colors are encoded by the following formula: Fore + (Back * 16) + (128 if blinking fore) Black = 0 Red = 4 Light Fore : Add 8 Blue = 1 Magenta = 5 Blinking Fore: Add 128 Green = 2 Yellow = 6 Cyan = 3 White = 7 ────────────────────┤ LNET-II v1.00 User Manual - Page 27 ├───────────────────── So, to change a color to light yellow on blue, that color code would be (6 + 8) + (1 * 16) = 30. For blinking light yellow on blue, the code would be (6 + 8 + 128) + (1 * 16) = 158. Background colors must be in the range 0 to 7. Foreground colors must be in the range 0 to 15 or 128 to 143. This formula is the same as the formula used by the BBS for its own color settings in WWIV.INI [in fact, it is used by the display hardware itself for mapping text color attributes in memory]. These settings DO NOT change the colors used in the GUI screens, which are not configurable, nor do they affect pipe code color translation. They affect only WWIVansi "heart code" color translation when viewing item text. Internal WWIVansi default colors are listed in the following chart: ╔═══════════════════════════════════════╗ ║ ■ WWIVansi Default Colors ■ ║ ╠═══╤════════════════════════════╤══════╣ ║ # │ Color Used [Fore / Back] │ Code ║ ╟───┼────────────────────────────┼──────╢ ║ 0 │ Light White / Black │ 15 ║ ║ 1 │ Light Cyan / Black │ 11 ║ ║ 2 │ Light Yellow / Black │ 14 ║ ║ 3 │ Magenta / Black │ 5 ║ ║ 4 │ Light White / Blue │ 31 ║ ║ 5 │ Green / Black │ 2 ║ ║ 6 │ Blinking Light Red / Black │ 140 ║ ║ 7 │ Light Blue / Black │ 9 ║ ║ 8 │ Yellow / Black │ 6 ║ ║ 9 │ Cyan / Black │ 3 ║ ╚═══╧════════════════════════════╧══════╝ "Pipe code" color values are fixed and cannot be changed in WWIV.INI except by adjusting the VGA text color palette [see page 30]. Color codes must be entered as decimal values only; hexadecimal values will either be rejected or will not give the expected results. NOTE: Some displays might map blinking foreground colors into solid colors with light backgrounds. For instance, they might map "light blinking white on blue" to "light white on light blue," thus using the high bit of the color attribute byte to intensify the background color instead of using it to blink the foreground color. This is most common on EGA displays [43-line mode]. In the VGA 30-line and 60-line modes, background colors are ignored, and any blinking foreground color codes are remapped to solid colors by LNET-II. The VGA text color palette may be configured; see page 30. ────────────────────┤ LNET-II v1.00 User Manual - Page 28 ├───────────────────── Option : DROP_BAD_NODE = ON | OFF Default: Off Determines whether references to nonexistent nodes will be removed from items' destinations when a packet is being rewritten. When it is ON, items being rewritten will have their destinations checked; when an item is going to a node which does not exist, that node is removed from the item's destination list. [This will cause the item to be deleted if it has only one destination node and that node does not exist.] This option does not affect nodes which do exist but are isolated. When DROP_BAD_NODE is OFF, items being rewritten will NOT have their desti- nation nodes checked; they are written as-is without modification. DROP_BAD_NODE applies only to item destinations; item origins are not checked. The /LOMEM command line option forces DROP_BAD_NODE = OFF. Option : MAX_RETRY = n Default: 5 Selects the maximum number of tries, in one-second intervals, before LNET-II times out on a locked file [one in use by another process]. The default value of 5 means that LNET-II would make five tries in five seconds to open a file, after which it will display a warning message and either exit to DOS or return you to the "Packet Select" list screen. As a rule, any packets which are locked by another process will not be shown in the available packet list; the retry counter is a safety precaution to help prevent LNET-II from hanging on a file it can't open. The allowable range for MAX_RETRY is 1 to 60. The list of available packets is re-scanned whenever the packet select list screen is called. Option : OPT_LINES = ON | OFF Default: On Determines whether LNET-II will print the "optional lines" in a post or e-mail's text when viewing the message. If OPT_LINES is OFF, these lines will be skipped while a message's text is being displayed. The ALT+O key may also be used at the main screen to toggle optional lines. See page 23 for further details. Option : OPT_VAL = n Default: 0 Selects which optional lines will be shown when their display is toggled ON. The value of 'n' must be a single digit from 0 to 9. A value of 0 would cause ALL optional lines to be shown, including any NET33+ routing stamps. A value of 1 would tend to display all optional lines EXCEPT the NET33+ routing stamps. A value of 9 would cause only those optional lines beginning with ^D9 to be displayed. See page 23 for further details. OptVal can also be set with the CTRL+O key at the main screen. The ALT+O key and "OPT_LINES =" setting can be used to turn optional lines off completely. ────────────────────┤ LNET-II v1.00 User Manual - Page 29 ├───────────────────── Option : PALETTE[c] = r,g,b Default: See below Adjusts the colors used in the VGA 30-line and 60-line text modes. DOES NOT AFFECT THE GUI SCREENS OR ANY OTHER TEXT MODES. The value of 'c' must be in the range 0 to 15, corresponding to the 16 available text colors. R, G, and B are the individual intensity values for the red, green, and blue guns, respectively. Each of these must be in the range 0 to 63 and must be specified in decimal values only; hexadecimal values will either be ignored or will not produce the expected results. If any color in the palette is changed, all three R,G,B values must be specified. For example: PALETTE[9] = 0,0,63 These settings will usually not need to be changed unless your monitor is out of adjustment. The default values are as follows: ╔═══════════════════════════════════════════════════════════════╗ ║ ■ LNET-II Default RGB Color Values - VGA Text Palette ■ ║ ╠════╤═══════════════╤══════════╦════╤═══════════════╤══════════╣ ║ ## │ Color │ R/G/B ║ ## │ Color │ R/G/B ║ ╠════╪═══════════════╪══════════╬════╪═══════════════╪══════════╣ ║ 0 │ Black │ 0,0,0 ║ 8 │ Dark Grey │ 15,15,15 ║ ║ 1 │ Blue │ 0,0,31 ║ 9 │ Light Blue │ 0,0,63 ║ ║ 2 │ Green │ 0,31,0 ║ 10 │ Light Green │ 0,63,0 ║ ║ 3 │ Cyan │ 0,31,31 ║ 11 │ Light Cyan │ 0,63,63 ║ ║ 4 │ Red │ 31,0,0 ║ 12 │ Light Red │ 63,0,0 ║ ║ 5 │ Magenta │ 31,0,31 ║ 13 │ Light Magenta │ 63,0,63 ║ ║ 6 │ Yellow │ 31,31,0 ║ 14 │ Light Yellow │ 63,63,0 ║ ║ 7 │ Light Grey │ 31,31,31 ║ 15 │ White │ 63,63,63 ║ ╚════╧═══════════════╧══════════╩════╧═══════════════╧══════════╝ Note that adjusting the VGA text color palette WILL have an effect on WWIVansi and pipe code color translation in the 30-line and 60-line modes. Adjusting VGA color #0 will change the global background color [normally black] for the 30-line and 60-line modes. Option : PAUSE = ON | OFF Default: On When this is ON, the item text display will execute a screen pause after every 'x' lines of text, where 'x' is the number of lines in the display minus one [the status bar uses the bottom line of the display]. When PAUSE is on, the screen will also pause when a "clear screen" command is encountered in an item's text, in order to allow the current screen page to be viewed before proceeding to the next page. PAUSE can also be toggled with the ALT+P key at the main screen or in the item text display. Option : PBAR_SEL_BACK Default: 0 [Black] Sets the background color for the selected item on the pull-down menu bar. Range: 0 [black] to 7 [white]. ────────────────────┤ LNET-II v1.00 User Manual - Page 30 ├───────────────────── Option : PBAR_SEL_FORE Default: 14 [Bright Yellow] Sets the foreground color for the selected item on the pull-down menu bar. Range: 0 [black] to 15 [bright white]. Option : PBAR_TEXT_BACK Default: 7 [White] Sets the background color for the pull-down menu bar. Range: 0 [black] to 7 [white]. Option : PBAR_TEXT_FORE Default: 4 [Red] Sets the foreground color for the pull-down menu bar. Range: 0 [black] to 15 [bright white]. Option : PBOX_BORDER Default: 14 [Bright Yellow] Sets the border foreground color for the pull-down menu boxes. There is no setting for the border background color; this is shared with the PBOX_TEXT_BACK value below. Range: 0 [black] to bright white [15]. Option : PBOX_SEL_BACK Default: 7 [White] Sets the background color for the selected item in the pull-down menu boxes. Range: 0 [black] to 7 [white]. Option : PBOX_SEL_FORE Default: 0 [Black] Sets the foreground color for the selected item in the pull-down menu boxes. Range: 0 [black] to 15 [bright white]. Option : PBOX_TEXT_BACK Default: 0 [Black] Sets the background color for the pull-down menu boxes and for the box borders. Range: 0 [black] to 7 [white]. Option : PBOX_TEXT_FORE Default: 15 [Bright White] Sets the foreground color for the pull-down menu boxes. Range: 0 [black] to 15 [bright white]. Option : SCR_MAX_REZ = ON | OFF Default: Off Determines whether LNET-II will display message text in a screen mode other than plain 25-line, if any other modes are detected. Supported high-resolution modes are 43-line [EGA] and 30, 50, or 60-line [VGA]. LNET-II does not use 132-column modes. MaxRez can also be toggled with the ALT+V key at the main screen. ────────────────────┤ LNET-II v1.00 User Manual - Page 31 ├───────────────────── The /NOHI command line option completely disables all detection and use of high-resolution text modes, forcing 25-line displays in all cases. When /NOHI is used, all command keys and WWIV.INI settings related to video modes are ignored. /NOHI was added during beta testing to cure an unusual lockup being experienced by one of the testers' systems. It is, more than anything, a troubleshooting option, and will usually not be needed. Option : SOUND = ON | OFF Default: On Determines whether LNET-II will enable sound effects and ANSI music translation. When sound is ON, LNET-II will emit a short tone to con- firm command keystrokes, "chime" the clock/calendar on the hour, decode and play ANSI music sequences, and emit a short tone on any ASCII 7 'beep' characters in the item text. When it is OFF, all sounds are disabled. Sound can also be toggled with the ALT+S key at the main screen or in the item text display. Option : STICKY_LIST = ON | OFF Default: Off Determines whether certain actions in list screens and node detail screens [ALT+F, ALT+I, ALT+L] will change the current item number. For instance, when viewing items' destinations with ALT+L, the LEFT/RIGHT keys can be used to view the destination(s) of the previous/next item - if STICKY_LIST is ON, then the most recently selected item becomes the current item at the main screen. The same applies when viewing items' origins with the ALT+F command. If the STICKY_LIST option if OFF, then the original item number is saved, and restored when you exit back to the previous screen. [It's easy to understand once you try it.] Option : USE_PULL_DOWN = ON | OFF Default: On Determines whether the ESC key will activate LNET-II's pull-down menus or return to the previous screen. When it is ON, the pull-down menus will be used. Pull-down menus are available at the packet list, main screen, item list, node detail screen, destination list, sub info screen, and network list. Option : USE_SYS_PASS = ON | OFF Default: Off When this option is ON, LNET-II will require users to enter your BBS system password before the program can be used. The prompt is shown after the program initializes, but before the packet list is shown. Option : VID_DEFAULT = 25 | 30 | 43 | 50 | 60 Default: 25 lines LNET-II detects the available text resolutions on your display, and defaults to using the highest available mode [generally 30, 50, or 60 lines for VGA, 43 for EGA, 25 otherwise] unless SCR_MAX_REZ is OFF. ────────────────────┤ LNET-II v1.00 User Manual - Page 32 ├───────────────────── The VID_DEFAULT option allows users having at least an EGA screen to set the default text mode, which may override the maximum detected mode. This value applies only to the message text display [ENTER key at the main screen]; the GUI screens are always shown in 25-line mode. If an unsupported mode is set, LNET-II will use the 25-line mode. Most displays are backward-compatible with lower-resolution modes - for instance, a VGA screen is also generally capable of using the EGA 43- line mode. Using the /NOHI command line option, setting SCR_MAX_REZ = OFF, or toggling MaxRez off with the ALT+V key at the main screen will nullify the VID_DEFAULT setting and force all message text to be shown in 25-line mode. NOTE: Because the VGA 30-line and 60-line modes are graphics screens, these modes can display text only in foreground colors - background colors are not shown. These modes cannot accept blinking colors; any blinking color codes will be remapped to solid colors by LNET-II. Text will tend to display slowly in the 30-line and 60-line modes. The CTRL+V key can be used at the main screen to cycle among the available screen modes, as long as "MaxRez" is on and/or the /NOHI command line option is not active. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ ALT+W: WRITE WWIV.INI ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ When ALT+W is pressed, LNET-II will write the current program settings to WWIV.INI. All previous LNET-II settings are overwritten. The current video mode will be saved as the VID_DEFAULT=n value. REG_NAME and REG_CODE are saved only if they are valid. If you loaded LNET-II with the /NOINI option, you will be warned that the current settings will overwrite your original settings; answer 'Yes' at the prompt to proceed, or answer 'No' to keep your original settings. If WWIV.INI does not exist when LNET-II is loaded, the file will be created. If WWIV.INI does exist but does not contain the [LNET2] block, LNET-II will append its default settings to WWIV.INI under [LNET2]. When LNET-II writes its settings to WWIV.INI, it will group them by related purposes - registration, toggles, video modes, cursor bar color, pull-down menu color, WWIVansi color, VGA color, optional lines, and miscellaneous - and prefix each group with a ';' remark. Again, options may be listed in any order in WWIV.INI; LNET-II groups them by purpose only to make them easier to handle when editing them. ────────────────────┤ LNET-II v1.00 User Manual - Page 33 ├───────────────────── ┌──────────────────────────────────────────────────────────────────────────────┐ │░ F2: CONFIGURATION MENU ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ The F2 command key at the main screen brings up a configuration menu which will allow you to edit all LNET-II settings except REG_NAME and REG_CODE [these must be entered manually from within your text editor]. Command keys for the configuration menu are as follows: [A] Toggle Sound [I] Set Retry Timer [B] Toggle Pause [J] Toggle "Drop Bad Node" [C] Toggle Clock [K] Toggle "Sticky List" [D] Toggle OptLines [L] Use System Password [E] Set OptLines Value [M] Set WWIVansi Colors [F] Toggle Pull-Down Menus [N] Set VGA Text Colors [G] Toggle MaxRez Video [O] Set Cursor Bar Colors [H] Set Vid Default [P] Set Pull-Down Menu Colors Type the letter corresponding to the setting you wish to change. Toggles will switch from ON to OFF and vice-versa. Numeric fields [OptLines Value, Video Default, Retry Timer] will show an input prompt in the config menu box. The allowable ranges for these fields are: OptLines : 0-9 Vid Default: 25, 30, 43, 50, or 60 Retry Timer: 1-60 If the /LOMEM command line option was used, the "Drop Bad Node" option CANNOT be turned on from the configuration menu. If the /NOHI option was used, then no video mode other than 25 will be accepted. The color configuration options [M through P] will pop up secondary input boxes for editing the color values. For WWIVansi colors, use the LEFT/RIGHT arrow keys to select the WWIVansi code you wish to edit [range 0-9], then use 'F' to set the foreground value [0-15], 'B' to set the background value [0-7], and 'K' to toggle blinking foreground colors. Press ESC when you have finished entering your settings. These settings correspond to COLOR[n] = v. For VGA text palette colors, use the LEFT/RIGHT arrow keys to select the VGA text palette color you wish to edit [0-15], then use the R, G, and B keys to set the red, green, and blue values, respectively [range 0-63 for all]. Press ESC when you have finished entering your settings. These settings correspond to PALETTE[n] = r,g,b. For the cursor bar color, use 'F' to set the foreground color [0-15] and 'B' to set the background color [0-7]. Press ESC when you have finished entering your settings. These settings correspond to CBAR_BACK = n and CBAR_FORE = n. The WWIVansi and cursor bar configuration boxes will display sample text to show you how the current settings for these colors will look. ────────────────────┤ LNET-II v1.00 User Manual - Page 34 ├───────────────────── The pull-down menu configuration screen has nine options ['A' through 'I'] which correspond to the settings listed on pages 30-31. The "Use System Password" option, when it is ON, forces LNET-II to ask for your BBS system password before the program can be used. This setting corresponds to USE_SYS_PASS = ON | OFF [see page 32]. The password is not echoed as it is typed; keystrokes are replaced with '*' asterisks on the screen. After you have finished entering your settings in the configuration menu, press ESC to return to the main screen. If any settings have been changed, you will have the option to save them to WWIV.INI. If you do not save them, they will apply only until you exit LNET-II. ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ SEARCHING FOR ITEMS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ ■ THIS FEATURE IS AVAILABLE IN REGISTERED COPIES ONLY ■ LNET-II contains a user-defined item search feature. This can be used to locate items by their main/minor types, subtypes, origins, destinations, ages, sizes, DE* methods, and/or by the contents of their text segments. Deleted items can also be searched, but these items will only be checked for sizes, ages, and text [only those items having a text size of 32K or less will be searched for text]. By default, LNET-II does not search deleted items. Before a search can be executed, it is necessary to define a SEARCH FORM. The command key to define the search form is F10 at the main screen. This will bring up the following form: ╒════════════════════════════════════════════════════════════════════════════╕ │ ■ L N E T - I I S E A R C H F O R M ■ │ ╞══════════════════════════════════════╤═════════════════════════════════════╡ │ [A] Main Type [ ] │ [F] Age (Days) [ ] │ │ [B] Minor Type [ ] │ [G] Size (Bytes) [ ] │ │ [C] Subtype [ ] │ [H] Method [ ] │ │ [D] From (#@#) [ ] │ [I] Deleted (Y/N) [ ] │ │ [E] To (#@#) [ ] │ [J] Match On All (Y/N) [ ] │ ├──────────────────────────────────────┴─────────────────────────────────────┤ │ [K] Text In Message: [Z] Clear All Fields │ │ [ ] │ ╘════════════════════════════════════════════════════════════════════════════╛ Press the key corresponding to the field you wish to edit, input the field's value, then press ENTER. To clear the search form, press 'Z'. [Clearing the search form removes all "M" tags from the packet index file.] When the desired fields have been defined, press ESC to return to the main screen. The following fields are NUMERIC and may have logical symbols applied to them: Main Type, Minor Type, Age, Size, and Method. Logical symbols which may be used are shown on the next page. ────────────────────┤ LNET-II v1.00 User Manual - Page 35 ├───────────────────── = Exact match [default] <> Not Equal To < Less Than <= Less Than Or Equal To > More Than >= More Than Or Equal To The default logic is an EXACT MATCH. Prefix a field's value with a logical symbol to search for something other than an exact match. For example, setting Main Type <=10 would cause LNET-II to search for all items having a main type of 10 or less. It is not necessary to use a '=' prefix when searching for an exact match. It is not possible to use multiple logical cases in a single field - for example, MainType >5<10 could NOT be used to find items whose main types are more than 5 but less than 10. LNET-II will reject such input. IMPORTANT NOTE: By default, LNET-II forces an 'AND' match - this means that a match will be assumed only if ALL of the search form's defined fields match the item being searched. If you set Main Type 26 and From 1@1, the search will stop on any item which has main type 26 -AND- is from 1@1. To force LNET-II to match on ANY defined field, set "Match On All" OFF with the 'J' key. You must have at least one field defined before LNET-II can perform a search. The allowable types of input for each field are as follows: MAIN TYPE - Numeric, range 1 - 64. May use logical symbols. Ignored for deleted items. MINOR TYPE - Numeric, range 0 - 65535. May use logical symbols. Ignored for deleted items. SUBTYPE - Alphanumeric, seven characters maximum. Cannot use logical sym- bols. Ignored for deleted items. NOTE: Per WWIV specifications, the first character in an alphanumeric subtype must be non-numeric. For example, SUB1 would be legal, while 1SUB would not. FROM - User@Node. Format as user@node or just as @node. Range is 0 - 32767 for 'user' and @1 - @65535 for 'node.' When entered as user@node, LNET-II will check the originating user AND node number; both must match the field's value. When entered as @node, LNET-II will check only the originating node, regardless of the user number. If the '@' character is not used as a prefix, LNET-II will assume the entered value is a node number and will add the '@' prefix by itself. Cannot use logical symbols. Ignored for deleted items. TO - Same as 'from,' but checks items' destinations. If an item has a destination list, the list is included in the search. Ignored for deleted items. AGE - Numeric, range 0 - 999. Applies to item age in DAYS. Deleted items are included in 'age' searches. May use logical symbols. [NOTE: One day is considered by LNET-II to be 24 hours prior to the current date and time.] ────────────────────┤ LNET-II v1.00 User Manual - Page 36 ├───────────────────── SIZE - Numeric, range 0 - 32767. Applies to item size in bytes. Deleted items are included in 'size' searches. May use logical symbols. METHOD - Numeric, range 0 - 65535. Applies to items' DE* encryption methods. May use logical symbols. Ignored for deleted items. TEXT - Printable alphanumeric and high/low ASCII, 72 characters. Deleted items are included in 'text' searches IF their sizes are no more than 32767 bytes and "Deleted" has been toggled ON with the 'J' key. Note that the text search is NOT case-sensitive - uppers and lowers are considered to be the same. When entering data in the 'Text' field, all letters will be converted to upper-case as they are being typed. The search form has two YES/NO toggles - "Deleted" and "Match On All." When "Deleted" is set ON, LNET-II will include deleted items in its searches under certain conditions [checks age, size, and text]. If it is OFF, then only non- deleted items will be searched. "Deleted" is OFF by default. Note that in this context, "Deleted" refers only to items which were already deleted [main type 65535] when the packet was loaded - it does not refer to items which have been marked for deletion by the CTRL+D, ALT+D, or ALT+T command keys. "Match On All" forces LNET-II to match ALL defined fields. If it is OFF, then LNET-II needs to match only one of the defined fields to consider an item 'found.' If it is ON, then an item must match ALL defined fields. [Remember, when "Match On All" is OFF, LNET-II performs an "OR" search - this field "OR" that field. If it is ON, LNET-II performs an "AND" search - this field "AND" that field.] After the search form has been defined, press ESC to return to the main screen or tag command menu. LNET-II will scan the entire packet from the first item to the last item and flag all items which match the defined search criteria. You will have the option to "tag" all matching items for batch processing [see next page] and/or untag items which do not match the search criteria. If any items match the defined search, the CTRL+LEFT and CTRL+RIGHT keys can be used at the main screen, at the item list screen, and in the item text display to jump to the previous or next match. CTRL+LEFT searches backward from the current item; CTRL+RIGHT searches forward. In both cases, the search will wrap around from the start or end of the packet. When a match is found, LNET-II stops on the matching item. [NOTE: The matching data is not visually high- lighted.] If no match is found, the search will end up back at the current item. The search form can also be used to mass-extract [CTRL+E key] and mass-delete [CTRL+D key] only those items which match the defined search criteria. Note that the search form must be set to find posts [main types 3, 5, and 26] and/or e-mails [main types 2 and 7] before it can be used to selectively mass-extract items - LNET-II does not extract any other types. Unregistered copies cannot use the item search features. ────────────────────┤ LNET-II v1.00 User Manual - Page 37 ├───────────────────── ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ ITEM TAGGING / TAG COMMAND MENU ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ LNET-II contains item tagging features which can be used for batch processing of tagged items. The SPACEBAR at the main screen and ALT+I item list is used to toggle an item's tag. Once items have been tagged, they can be batch deleted, restored, extracted, and/or searched. Some tag functions require registration. The item list screen has a "Tag" column which may contain the letters T, D, and/or M next to each item. 'T' indicates a tagged item, 'D' indicates an item which has been marked to be deleted, and 'M' indicates an item which matches the most recent search criteria. These will also be indicated in check boxes on the main screen. [Note: Clearing the search form turns all "M" tags off.] The F3 key at the main screen will bring up the TAG COMMAND MENU. From this menu, you may tag or untag entire groups of items, delete them, restore them, extract them, search them, or toggle [invert] their tags. The right half of the tag command menu shows four data items: ■ "Tagged" indicates how many items are currently tagged ■ "Matched" indicates how many items matched the most recent search criteria ■ "MarkDel" indicates how many items are marked to be deleted ■ "WasDel" indicates how many items were already deleted [main type 65535] when the packet was loaded - these items cannot be undeleted by LNET-II All of the tag menu commands except F10 will prompt you to enter the starting and ending item numbers for the range you wish to process. The available commands at the tag command menu are as follows: [T] Tag Items [D] Delete Tagged [U] Untag Items [R] Restore Tagged [I] Invert Tags [E] Extract Tagged [M] Tag Matched [S] Search Tagged [F10] Define Search Form TAG ITEMS: This command lets you set the tags for a range of items. You will be prompted for the starting and ending item numbers. The defaults are 1 for the starting item and "max items" for the ending item. LNET-II will then scan the index file for items which are not already tagged and turn those items' tags on. If all items are already tagged, you will be informed of this. UNTAG ITEMS: Similar to the "tag items" command above, except that it turns items' tags off. There must be at least one item tagged. INVERT TAGS: Toggles or "inverts" the tags in a range of items - items which are tagged will be untagged, and vice-versa. TAG MATCHED [Reg'd Only]: Tags all items in a specified range IF they match the most recent search criteria. A search form must be defined [see page 35]. Note that the search feature can also be used to automatically tag matching items and/or untag non-matching items. ────────────────────┤ LNET-II v1.00 User Manual - Page 38 ├───────────────────── DELETE TAGGED [Reg'd Only]: Prompts you to enter the starting and ending item numbers, and deletes all tagged items within that range. [Remember, deletion is not permanent until you close the packet.] There must be at least one item tagged and at least one item not yet deleted. RESTORE TAGGED [Reg'd Only]: Similar to "delete tagged" above, except that it restores or "undeletes" a range of items. There must be at least one item tagged and at least one item marked to be deleted. EXTRACT TAGGED [Reg'd Only]: Extracts to a text file all tagged post [main types 3, 5, and 26] and e-mail [main types 2 and 7] items within the specified range. There must be at least one item tagged. See page 20 for details on extracting items. SEARCH TAGGED [Reg'd Only]: Applies the current search criteria only to tagged items in the specified range. There must be at least one item tagged. DEFINE SEARCH FORM [Reg'd Only]: This is the same as using the F10 command at the main screen; see page 35. ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ THE NONEXISTENT NODE LIST EDITOR ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ ■ Nonexistent Node List Example ■ ╒════════════════════════════════════════════════════╕ │ ■ N O N E X I S T E N T N O D E S ■ │ ╞════════╤══════════╤══════════╤══════════╤══════════╡ │ Node │ Items │ Oldest │ Newest │ Cutoff │ ╞════════╪══════════╪══════════╪══════════╪══════════╡ │ @1234 │ 5 │ 4 Days │ 1 Day │ -DelAll- │ │ @5678 │ 2 │ 1 Day │ 1 Day │ -DelAll- │ │ @24680 │ 11 │ 15 Days │ 6 Days │ 7 Days │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ╘════════╧══════════╧══════════╧══════════╧══════════╛ When a packet is being rewritten, and the DROP_BAD_NODE option is ON [see page 29], LNET-II scans the destination nodes in the packet to see if any are "non- existent" [meaning no data was found for them in the BBSDATA.NET file]. You will then be asked if you want to edit the list of nonexistent nodes. If you answer NO at this prompt, then ALL references to nonexistent nodes will be deleted from the packet as it is being rewritten. If you answer YES, you will be shown a list of all the nonexistent nodes referenced by the current packet. The list shows the node numbers, the ages of the oldest and newest items for those nodes [in days, range 0 to 999], and the "cutoff age" for each node. ────────────────────┤ LNET-II v1.00 User Manual - Page 39 ├───────────────────── Selecting a node with the cursor keys and pressing SPACE will allow you to switch between using a cutoff age for that node or deleting every reference to that node. The "Cutoff" column will show "-DelAll-" when all references to a node are to be deleted from the packet. Pressing ENTER on a node will let you edit the cutoff age. The cutoff age means that items OLDER than the given age will be deleted and items equal to, or newer than, the given age will be saved. In the example on the previous page, node @24680 has a cutoff of 7 days, which means that any references to that node in items aged 8 days or older would be deleted and references 7 days old or newer would be kept. Note that LNET-II considers one day, in this context, to be 24 hours prior to the current date and time. [The time is more significant than the date.] Because the nodes in this list are there because they were not found in BBSDATA.NET, it is not possible to view BBS details for those nodes. If a node being deleted is referenced in the destination list of a stacked item, the node will simply be removed from the destination list - LNET-II does not delete the entire item unless its destination list consists solely of nodes which are to be deleted. The ALT+D key lets you delete a node from the list. This causes LNET-II to KEEP all references to that node even though it does not exist. A node cannot be added back into the list once it has been deleted. If no more nodes are in the list, the editor will exit back to the main screen and LNET-II will continue with the rewrite process. The ALT+C key clears the entire list. This causes LNET-II to treat all desti- nation nodes in the packet as being existent and valid; it has an effect similar to turning the DROP_BAD_NODE option OFF. If the list is cleared, LNET-II will return to the main screen and perform the packet rewrite. After you have finished editing the list, press ESC to return to the main screen and continue with the rewrite process. Setting the DROP_BAD_NODE option OFF disables the nonexistent node editor. The /LOMEM command line option also disables it, because the /LOMEM option forces DROP_BAD_NODE = OFF. The nonexistent node list is built in memory only when LNET-II is preparing to rewrite a packet. As such, it will be available only at those times - when a packet is being rewritten with the ALT+C command key or when deleted items are being removed from a packet before it is closed. Existing nodes - meaning nodes which do appear in BBSDATA.NET - will never appear in the nonexistent node list, whether they are isolated or not. The nonexistent node editor will never appear if DROP_BAD_NODE is OFF. ────────────────────┤ LNET-II v1.00 User Manual - Page 40 ├───────────────────── ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ APPENDIX A1: WWIV NETWORK ITEM TYPES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ This listing is current as of December 1995 [NET36 release]. Items are shown by main type, and by minor type where applicable. All types MAY have DE* encryp- tion; some require it. 1 - NETWORK UPDATE These items must always use valid Method 1 encryption and require DE1.EXE to decode. Minor Type 0 = Mail-To-All-Sysops 1 = BBSLIST.NET 2 = CONNECT.NET 3 = SUBS.LST 4 = WWIVNEWS.NET 5 = FBACKHDR.NET 6 = Extra WWIVNEWS.NET Text 7 = CATEG.NET 8 = NETWORKS.LST 9 = File From NC 2 - E-MAIL BY USER NUMBER Minor type is usually 0. These items cannot have a destination list [no multiple destinations for mass-mail allowed]. Minor Type 0 = Standard e-mail 1 = Mail from NetPurge [Black Dragon Ent.] 2 = Mail from AutoSend [Cris McRae] 3 = Mail from Dead-Fix [CMI Software] 10 = Mail from NetEdit [Black Dragon Ent.] 3 - POST BY NUMERIC TYPE [TO SUBSCRIBERS] Minor type is numeric subtype. 4 - [ not used, or third-party use unknown ] 5 - PRE-POST BY NUMERIC TYPE [TO HOST] Minor type is numeric subtype. These items cannot have multiple desti- nations. 6 - EXTERNAL MSG. Rarely used, if at all; superseded by main type 27. 7 - E-MAIL BY USER NAME [ALSO FOR GATED MAIL] Minor type is usually 0. Recipient's name is held in the first few bytes of the message text; this name may be a gated network address. These items cannot have multiple destinations. Minor Type 0 = Standard e-mail 1 = Mail from NetPurge [Black Dragon Ent.] 2 = Mail from AutoSend [Cris McRae] 3 = Mail from Dead-Fix [CMI Software] 10 = Mail from NetEdit [Black Dragon Ent.] ────────────────────┤ LNET-II v1.00 User Manual - Page 41 ├───────────────────── 8 - NETEDIT ITEMS NetEdit is a utility to manage network connection data and other related network files. It is apparently no longer being supported by its author [D. Stussy / Black Dragon Enterprises]. Minor Type 0 = Partial BBSLIST Update 1 = BBSLIST Change Request 2 = Partial CONNECT Update 3 = CONNECT Change Request 4 = NetEdit Registration Record Update 5 = Install Notice To Author 6 = Request To Send Registration Record 7 = Registration Record Response 8 = Remote Analysis Request 9 = Remote Analysis Response 10 = NetEdit Auto Feedback 11 = Error Report 12 = Request For Version/Install Info 13 = Version/Install Response 14 = Request For Aliases 15 = Aliases Response 411 = BBS_DIR Item [not used by NetEdit] 9 - SUBS.* Minor Type 0 = SUBS.LST * = SUBS.* [numeric extension, up to 999?] 10 - Used By LINKER [Net Update/Packet Transfer Utility] Minor Type 0 = SSM 512 = Packet Transfer 513 = Registration Ping 514 = Registration Pong 11 - BBSLIST.* UPDATE These items require encryption by Method 1 or Method ((minortype mod 256) + 256). Minor Type 0 to 255 = Full upd. NC to net 257 to 511 = Full upd. GC to NC 513 to 767 = Partial upd. NC to net 12 - CONNECT.* UPDATE These items require encryption by Method 1 or Method ((minortype mod 256) + 256). Minor Type 0 to 255 = Full upd. NC to net 257 to 511 = Full upd. GC to NC 513 to 767 = Partial upd. NC to net 13 - [ not used, or third-party use unknown ] 14 - GROUP INFO [GC TO NC, OR GC TO GROUP] These items require Method (group + 256) encryption. Minor Type 0 = Mail-To-All-Sysops [GC source-verified] * = Group number from GC to NC? ────────────────────┤ LNET-II v1.00 User Manual - Page 42 ├───────────────────── 15 - SSM Some third-party utilities use this type to transmit files, updates, and other such items; these items are usually EN* encrypted by the sender and processed by the DE* decoder upon receipt. The following types belong to third-party programs and are not a standard part of the NET## software: Method 2 = NetSend Update From NC 3 = FDL Net Ping [Outdated?] 512 = Linker 555 = FLINK Item 556 = Add-A-FLINK 600 = FDL Add/Drop 601 = FDL NetFile 602 = FDL NetFile Request 603 = FDL Net Ping 16 - SUB ADD REQUEST Minor type is numeric type of sub, or 0 if the subtype is alphanumeric. 17 - SUB DROP REQUEST Minor type is numeric type of sub, or 0 if the subtype is alphanumeric. 18 - SUB ADD RESPONSE Minor type is numeric type of sub, or 0 if the subtype is alphanumeric. Rewritten as type 2/0 e-mail on receipt. 19 - SUB DROP RESPONSE Minor type is numeric type of sub, or 0 if the subtype is alphanumeric. Rewritten as type 2/0 e-mail on receipt. 20 - SUB INFO Minor Type 0 = 'Ping' From SUBS.LST Coordinator 1 = 'Pong' To SUBS.LST Coordinator 21 to 25 - [ not used, or third-party use unknown ] 26 - POST BY NAME [ALPHANUMERIC SUBTYPE] This type is used for posts going from the host to a subscriber and vice- versa; there is no corresponding "pre-post" type as with main types 3 and 5. Minor type is always 0. Subtype is held as the first few bytes of the message text [up to eight bytes] preceding the message title. Main type 26 is used only for alphanumeric subtypes; for numeric subtypes, main types 3 and 5 are used instead. ────────────────────┤ LNET-II v1.00 User Manual - Page 43 ├───────────────────── 27 - NEW EXTERNAL [DATA FOR EXTERNAL PROGRAMS] Items using main type 27 are passed by NETWORK2 to an external program for processing if such a program has been installed to handle the item's minor type. LNET-II contains the names of all allocated 27/# minor types known to the author of LNET-II as of this release. The following types belong to third-party programs and are not a standard part of the NET## software: Minor Type 69 = PackScan 169 = CMI NetUp [GWARnet] 398 = K9NFX NetFile 500 = AutoSend Registration Ping 501 = AutoSend Registration Pong 905 = CMI NetUp [USLink] 976 = CMI NetUp [HerpsNET] 2121 = DMail As of this writing, there are no allocated main types above 27. [NOTE: NET37 is expected to have a new main type 28 for use by networked games.] The NET## software will accept main types up to 64 although these do not yet have any allocated purpose. As with the NET## software, LNET-II will refuse to accept any main type above 64. LNET-II will still pass main types in the range 28 to 64 even though it cannot identify them by their names. Updates will be made to LNET-II as new main and minor types are allocated. ┌──────────────────────────────────────────────────────────────────────────────┐ │░ APPENDIX A2: CMI NETUP ITEM TYPES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ CMI NetUp items contain a 20-byte subheader at the beginning of the items' text segments. This subheader indicates the types of updates and diagnostic pings, and includes the source authentication codes. CMImajor types currently range from 1 to 11; CMIminor types range from 0 to 255, depending on the CMImajor type. Item types used in the CMI NetUp subheader are as follows: Type 1 = BBSLIST.NET CMIminor type is always 0. Type 2 = BBSLIST.* CMIminor type indicates the extension, 0 to 255. Type 3 = CONNECT.NET CMIminor type is always 0. Type 4 = CONNECT.* CMIminor type indicates the extension, 0 to 255. Type 5 = SUBS.* CMIminor type 0 = SUBS.LST. Any other type indicates the extension. Type 6 = FBACKHDR.NET CMIminor type is always 0. ────────────────────┤ LNET-II v1.00 User Manual - Page 44 ├───────────────────── Type 7 = NETNEWS.MSG CMIminor type is always 0. Size is limited to 32K at this time. Type 8 = CATEG.NET CMIminor type is always 0. Type 9 = FEEDBACK TO ALL SYSOPS CMIminor type is always 0. These items are rewritten as WWIV type 2/0 e-mails to LOCAL.NET on receipt. Type 10 = DIAGNOSTICS PINGS [RETURNED AS TYPE 11] CMI NetUp contains a set of network diagnostics pings which can be sent by the NC to help spot routing problems, dead packets, and so on. Pings are sent as CMImajor type 10. Pongs are returned to the NC as CMImajor type 11, using the same minor types. CMI NetUp items are never DE* encrypted; they are always plain text and can be viewed at any time. Diagnostics minor types are as follows: 1 = LOOP TEST Times the transfer of a packet from the NC to a node and back. 2 = PROCESSOR VERSION Returns the version number of a node's CMI NetUp update processor. 3 = CONTACT.NET DATA Returns data from a node's CONTACT.NET file. This lets the NC view the callout history for a node to see if net connects are being made on a regular basis. 4 = NETWORKS DATA Returns data from NETWORKS.DAT, indicating the network names and node numbers of a system. Used for building a gateway list. 5 = PENDING DATA Returns the names and sizes of any unsent packets which may exist in the network's directory. 6 = CALLOUT.NET DATA Returns the node numbers listed in a node's CALLOUT.NET, along with flags indicating whether passwords have been set, indicating established connections. DOES NOT return the passwords! 7 = TIMESTAMPS Returns the UNIX-style timestamps from a node's BBSLIST.* and CONNECT.* files. Used to check the age of a node's data. 8 = CONTROL NUMBER CMI NetUp places an encoded date/time control number in the FBACKHDR.NET file. This is used to help authenticate updates and to check the age of a node's data. 9 = DEAD.NET ANALYSIS Lists the contents of a node's DEAD.NET packet if it has one. 10 = BBSDATA.NET ANALYSIS Lists the contents of BBSDATA.NET. Used to ensure that a node's BBS list data is current and correct. ────────────────────┤ LNET-II v1.00 User Manual - Page 45 ├───────────────────── ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ APPENDIX B: LNET-II ITEM VALIDATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ LNET-II contains extended packet and net item validation code in order to de- tect, handle, and repair possibly corrupt net packets during its pre-scan pro- cess. If an invalid item is encountered by LNET-II, the program will then scan the packet one byte at a time from that point, searching for the beginning of a valid net item header. [NOTE: This scan may take a LONG time, particularly with a large packet on a slow system. Installing a disk cache will help speed up the process. CTRL+C may be used to abort LNET-II during this scan.] If a valid header is then detected, or the scan reaches the end of the packet without a valid item being located, LNET-II will mark the invalid portion of the packet as a deleted item. This will allow LNET-II, the NET## software, and other programs to automatically skip those segments of the packet during sub- sequent processing. The algorithm used in item validation follows the specifications used in the NET## software, plus a few extra checks added by the author of LNET-II. These specifications are as follows. Note that ALL of these cases must be met for an item to be considered valid: ■ Item size [nh.length] does not exceed end of packet. ■ If MainType is not = 65535, Length <= 32767. [see note below] ■ MainType > 0. ■ MainType <= 64 OR MainType = 65535. ■ ToUser <= 32767. ■ FromUser <= 32767. ■ ListLen <= 4096. ■ FromSys > 0. ■ ListLen > 0 OR ToSys > 0. * NOTE: Deleted [MainType 65535] items may have any length; NET## and LNET-II both use this type to indicate deleted items and scan past them. A deleted item may have a length greater than 32767 bytes, but this value must still be within the limits of the packet's size. If an item is marked as deleted, the only other specification which applies is the item size. * New for NET36: Prior versions of the NET## software allowed user numbers only in the range of 0 to 4096. This was expanded to 32767 to accommodate WWIV-to-Internet mail gateway software, which generally aliases Internet addresses to a database of temporary WWIV user numbers. LNET-II includes all of the standard NET## checks above, plus: ■ ToSys and ListLen cannot both be non-zero [an item can have either a ToSys or a destination list, but never both - ToSys must be 0 if ListLen is not 0, and vice-versa]. The NET## software apparently doesn't take this into account, perhaps because it ignores ToSys if ListLen is non-zero, but LNET-II treats such items as improperly formatted and invalid. ■ Main types 2, 5, 7, and 16 to 19 cannot have a destination list. ────────────────────┤ LNET-II v1.00 User Manual - Page 46 ├───────────────────── ■ Main types 16 to 19 must have Length > 0 if minor type is 0. [This check is included to help ensure that these items are properly formatted.] ■ Main types 18 and 19 must have Length >= 1 for numeric subtypes [minor type <> 0] and Length >= 3 for alphanumeric subtypes [minor type = 0]. ■ Main type 20 cannot have a destination list if its minor type is 1. [Mass SUBS.INF pongs? I don't think so!] ■ Items requiring DE* encryption must have the proper methods for their main/minor types. [These items are main types 1, 11, 12, and 14.] If an item is found to be deleted [main type 65535] and is valid in regards to its size, no other checks are made on that item. LNET-II cannot determine whether an item's encryption envelope is valid; it merely checks the "Method" field in the net item header to ensure a proper value when an item's type specifically requires Method<>0. The minimum possible size for any single item is 24 bytes, which is the length of the WWIV network header. The maximum possible size for an undeleted item is 24 + 8192 + 32767 bytes, or 40,983 bytes total. The dest_list is not counted in the 32K item size limit, but has a maximum value of 4096 nodes [8192 bytes]. While the item validation specs outlined for the NET## software are usually sufficient to detect most errors, the additional checks above provide even more robust and reliable detection of packet corruption and allow LNET-II to repair a much greater range of possible errors. Such advanced error correction features will usually not be needed, but it is safer to include them than to have LNET-II operate improperly because of bad data in a packet. Items which do not pass LNET-II's additional error checks may not necessarily be corrupt items, but their headers contain data which is inconsistent with normal network operations [for instance, type 20/1 subs info "pongs" should not be stacked as mass-mail]. Because of these inconsistencies, LNET-II treats such items as invalid. NOTE: In some rare cases, the pre-scan process may determine that segments of an invalid item or packet are actually valid items. It is better to delete these "false valid" items than to let them get sent out into the network. They are relatively easy to spot - they can have unusual main/minor types, impossible ages, and be to/from nonexistent nodes. CMI NetUp items are validated according to the structure of their subheaders and the authentication built into them. These items must have a length of at least 20 bytes, pass the internal source authentication checks, and contain a valid range of types in their subheaders. If an item has a main type of 27, LNET-II checks to see if that item passes CMI NetUp authentication. If so, then the item will be displayed as belonging to CMI NetUp, with the owner network shown if it is known [as of this writing, valid owner networks for CMI NetUp are USLink, GWARnet, and HerpsNET]. So, CMI NetUp items are automatically detected by LNET-II even if their 27/# minor types have not been encoded into LNET-II. If an item's type has been allocated to CMI NetUp but the item does not pass authentication, the item will still be shown as belonging to CMI NetUp, but the main screen will not display any CMI NetUp subheader data. LNET-II does not delete items whose types belong to CMI NetUp but which do not pass CMI NetUp authentication, and it does not attempt to authenticate items belonging to third-party utilities other than CMI NetUp. ────────────────────┤ LNET-II v1.00 User Manual - Page 47 ├───────────────────── ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ APPENDIX C: REVISION HISTORY ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ Unfortunately, I haven't kept track of the really fun stuff, like the exact dates when various features were added, but here's a general history... 09/27/1996 Development started on LNET-II v1.00. Originally named XLNET v2.00, it was intended to replace XLNET v1.00, which was removed from distribution on 02/02/1998. Some code taken from the Dead-Fix v2.30 source [not released at this time]. New features galore. Full GUI screens replace the drab plain-text display of XLNET v1.00. 07/1997 Began limited distribution of v2.00 in beta test phase. Development continues. 02/12/1998 Due to discovery of a prior registered trademark on the XLNET name [owned by ExcellTech], this program was renamed to LNET-II v1.00. Since this a completely new program, the version number 1.00 is used. Development and beta testing continues. 08/26/1998 LNET-II v1.00 finally released, after nearly two years of development and testing. ────────────────────┤ LNET-II v1.00 User Manual - Page 48 ├───────────────────── ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ APPENDIX D: CONTACTING THE AUTHOR ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ The author may be reached by e-mailing any one of the following: ╒══════════════════════════════════════════════════════════════╕ │ ModeMANIA BBS - 626-451-0936 [33.6K] │ ╞════════════════════╤════════════════════╤════════════════════╡ │ DigiNet .... @5401 │ FILEnet ..... @571 │ GLOBALnet .. @8854 │ │ IceNET ..... @8854 │ SierraLink . @8854 │ TerraNET ... @8854 │ │ USLink ........ @1 │ WWIVLink .. @18867 │ WWIVnet .... @3800 │ ╞════════════════════╧════════════════════╧════════════════════╡ │ Internet: xfire905@aol.com -or- kharris@voyager.com │ ╘══════════════════════════════════════════════════════════════╛ A CMI Product Support forum is available on all of the above WWIV networks under the subtype CMISUPP [autoreq allowed, gating by permission]. Support can also be obtained by posting in the Usenet newsgroup alt.bbs.wwiv. CMI Software's web page is at http://members.aol.com/xfire905/cmihome.htm. The most current release versions of nearly all CMI Software products can be found on this site. A partial library can also be found at ftp://ftp.wwiv.com/pub/cmi. ────────────────────┤ LNET-II v1.00 User Manual - Page 49 ├───────────────────── ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ APPENDIX E: COPYRIGHT / SHAREWARE NOTICE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ This program and its accompanying documentation are copyrighted material property of Ken W. Harris. License is granted to use the program without charge for an evaluation period of 30 days, after which the user is required to register. The registration fee is $20 U.S. for each installed copy, payable by check or money order to: Ken Harris 9948 Duffy St. Temple City, CA 91780-2607 Please state which CMI product and version number you are registering, the exact name you would like to have displayed on the screen as part of your registration code, and a network address to which your registration code can be e-mailed [preferably on one of the following: DigiNet, FILEnet, IceNET, TerraNET, USLink, WWIVLink, WWIVnet, Internet]. REGISTRATIONS ARE NOW HANDLED BY E-MAIL. Upon receipt of payment, the author will e-mail you a registration code to be entered in your WWIV.INI file. This code will unlock the registered-only features of the program, if any features are locked out in unregistered copies, and will be valid through all future versions of this program unless otherwise notified. Note that the registration code you receive will be valid for this program only - each CMI Software product has a slightly different encoding method for its registrations. Registered users who are upgrading from previous versions of this program are requested to contact the author [see page 49] in order to obtain their new WWIV.INI registration codes if they have not already received them and their old codes no longer work. Registration codes do not expire after a certain time, but the encoding method being used may have changed. Registration codes are keyed to your real name and to your BBS name and BBS phone as entered in INIT. If any of these are changed, contact CMI Software for a new registration code keyed to the new data. [Include the original code in your request.] ┌──────────────────────────────────────────────────────────────────────────────┐ │░ VENDORS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ Software vendors may distribute this program provided it is kept in its complete and unmodified original form, including all accompanying documentation, and pro- vided that persons receiving the program are made aware that any fees charged for receipt of the program by any agent other than the author DO NOT constitute purchase or registration of the program. These restrictions also apply to bulletin board operators and to users of the program. Commercial vendors are requested to contact the author at the above address prior to distributing this program in any medium. Vendors may request reasonable fees for the medium carrying the program and/or for shipping and handling of the medium, but NOT for the program itself. All applicable domestic [United States] and international rights remain the exclusive property of the author. ────────────────────┤ LNET-II v1.00 User Manual - Page 50 ├───────────────────── ╔══════════════════════════════════════════════════════════════════════════════╗ ║░ APPENDIX F: TRADEMARKS AND CREDITS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░║ ╚══════════════════════════════════════════════════════════════════════════════╝ This program and its documentation are registered with the United States Library of Congress Copyright Office. CMI [California Microdata International] is an unregistered trade name of the author, who is not affiliated with, or a representative of, any other group or organization bearing the initials CMI or the name CMI Software. CMI Software products are written in Microsoft PDS [Professional Development System] v7.1, a high-powered variant of QuickBASIC. LNET-II's GUI screens were created in TheDraw and use TheDraw's crunched .OBJ save format and screen display routine. TheDraw is copyrighted material property of Ian E. Davis / TheSoft Programming Services. LNET-II's ANSI decoder is a heavily modified version of the ANSIprint() routine from Tom Hanlin's BASWIZ library. This documentation was composed in QEdit v3.00, which is copyrighted material property of SemWare Inc. QEdit, or forget it! WWIV, WWIVedit, and the WWIV network software are copyrighted material property of WWIV Software Services. Contact 1@3 FILEnet. Dead-Fix and CMI NetUp are copyrighted material property of Ken Harris / CMI Software. See page 49 for contact info. K9NFX is copyrighted material property of J. Johnson / K9000 Systems. AutoSend is copyrighted material property of Cris McRae. NetEdit, NetPurge, and BBS_DIR are copyrighted material property of D. Stussy / Black Dragon Enterprises. Linker is copyrighted material property of John Wheeler / Microtech Solutions. Contact 1@20750 WWIVnet. DMail is copyrighted material property of Chuck Bensinger. Contact 1@2121 WWIVnet. StripIt is copyrighted material property of Matt Hucke. MS-DOS, Windows, and Windows 95 are trademarks of Microsoft Inc. DESQview is a trademark of Quarterdeck Inc. OS/2 is a trademark of IBM Corp. XLNET is a trademark of ExcellTech. ────────────────────┤ LNET-II v1.00 User Manual - Page 51 ├───────────────────── ┌──────────────────────────────────────────────────────────────────────────────┐ │░ CREDITS AND KUDOS TO... ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ └──────────────────────────────────────────────────────────────────────────────┘ ...Wayne Bell, for supplying information used to create LNET-II's item vali- dation and packet repair algorithms, and for supplying other information used to help create CMI NetUp. ...Wayne Heyward, author of the WW4NTECH technical manual for WWIV networking. ...Dean Nash, for beta testing and for his decision to use LNET-II [the packet reader formerly known as XLNET v2.00] as the replacement for LNET in the NET37 software archive. ...Deltigar, for supplying information on the types and structures used by FLINK. ...Cris McRae, for supplying information on the structures used by Linker and PackScan. ...Steven Hancock, for supplying information on detecting file sharing/locking and for giving me the occasional big idea. ...various others who supplied information used in the development of LNET-II. ...John Joha, for creating the update software used in the very early days of USLink, and for indirectly giving me the idea to write CMI NetUp and a packet reader which could recognize its updates. ...Jim Johnson, without whom I might still be programming in GWBASIC. <shudder> ...Chris Yarnell and Peter Losher, operators of the ftp.wwiv.com site. ...Nocturnal1, for beta testing, for pointing out the occasional tiny bug, for giving me the "view sub info" idea, and for suggesting that the item text display should allow stepping between items without having to return to the main screen. ...Randy Miller, for beta testing and for supplying a test packet to assist in adding recognition of WWIV->FIDO items. ...Chris Cone, Mike Craig, Michael Deweese, Craig Dooley, Mike Dunston, Bob Geary, Brian Harris, Brandon Hendricks, Mark Hofmann, Art Johnston, Ronda Kelly, Matt Munson, Dennis Myers, Dean Nash, Frank Reid, Scott Robinson, Preston Rosser, and Richard Zaidi, for beta testing. ...Steven Hancock and Glen Carlzen, for their dedicated beta testing, support of CMI Software, and various hardware donations. ...Jim Edwards, Dennis Thompson, Ed Walker, Preston Rosser, Bob Geary, and Dave Carpenter, and Dennis Hancock, for other hardware donations. ...ModeMANIACS everywhere. ────────────────────┤ LNET-II v1.00 User Manual - Page 52 ├─────────────────────