F I D O N E W S -- Volume 14, Number 20 19 May 1997 +----------------------------+-----------------------------------------+ | The newsletter of the | ISSN 1198-4589 Published by: | | FidoNet community | "FidoNews" | | _ | 1-904-409-7040 [1:1/23] | | / \ | | | /|oo \ | | | (_| /_) | | | _`@/_ \ _ | | | | | \ \\ | Editor: | | | (*) | \ )) | Christopher Baker 1:18/14 | | |__U__| / \// | | | _//|| _\ / | | | (_/(_|(____/ | | | (jm) | Newspapers should have no friends. | | | -- JOSEPH PULITZER | +----------------------------+-----------------------------------------+ | Submission address: FidoNews Editor 1:1/23 | +----------------------------------------------------------------------+ | MORE addresses: | | | | submissions=> cbaker84@digital.net | +----------------------------------------------------------------------+ | For information, copyrights, article submissions, | | obtaining copies of FidoNews or the internet gateway FAQ | | please refer to the end of this file. | +----------------------------------------------------------------------+ IS IT JUST A TECHNICALITY? Table of Contents 1. EDITORIAL ................................................ 1 Moving right along? ...................................... 1 2. ARTICLES ................................................. 2 Bulletin Boards vs the InterNet .......................... 2 3. GETTING TECHNICAL ........................................ 4 Proposed Update of FTS-0001 Product Codes ................ 4 Proposed Update to FTS-0005 .............................. 6 Suggested use of Nodelist Fields ......................... 18 Proposal For Standard Fidonet Addressing ................. 19 4. COORDINATORS CORNER ...................................... 24 Nodelist-statistics as seen from Zone-2 for day 136 ...... 24 5. NET HUMOR ................................................ 25 Redneck's Guide to Computer Lingo ........................ 25 6. COMIX IN ASCII ........................................... 26 IT'S Everywhere? ......................................... 26 7. ANSWERS OF THE WEEK ...................................... 27 Old Nodelist Answer #1 ................................... 27 8. NOTICES .................................................. 28 Future History ........................................... 28 9. FIDONET SOFTWARE LISTING ................................. 30 Latest Greatest Software Versions ........................ 30 10. FIDONEWS PUBLIC-KEY ..................................... 35 FidoNews PGP public-key listing .......................... 35 11. FIDONET BY INTERNET ..................................... 36 And more! FIDONEWS 14-20 Page 1 19 May 1997 ================================================================= EDITORIAL ================================================================= The ZEC Election did get called off in Zone 1. ZEC1 now has a temporary appointee. The ZEC Echo has a temporary Moderator. The more things change the more they stay the same. Unfortunately, there is still no International Coordinator. But do we really need one after all? Do we need any of these Coordinators? The Technical section contains no old stuff this week. There's a batch of new stuff from Z2. What a relief. [grin] There has been only one response to the call for sources for old Nodelists from last week's Issue. It appears later. If you have old Nodelists available on your system or webpage, please let us know by sending in a note to FidoNews or a file with the .ANS extension for Answer of the Week. The R19 page moved again and there is a new entry for REC17 in the Internet section. There is still no update for the ZEC2 page. C.B. ----------------------------------------------------------------- FIDONEWS 14-20 Page 2 19 May 1997 ================================================================= ARTICLES ================================================================= Bulletin Boards vs the InterNet by Bobby Darin, (1:285/82.0), Bellevue, NE There has been much about the death of Fido-Net lately in different sysop conferences. These premature death calls I think are both over rated and short lived. The largest group of such claim are coming from the InterNet circle. The InterNet -- We hear about it everywhere. We know what it is, but do we really know what it is not? Hopefully, I will describe what the InterNet is not. I have been in the computer arena since way back when.... about 17 years. In the early days of computers, things were very different from the way they are now as I'm sure they are going to be different in the future. The biggest difference, in my opinion, are the trends. I believe the InterNet is just another trend, like the Atari 2600, the Commodore 64, and much like the Sega systems of today. While these trends have come and gone - old trends being replaced with new ones, the bulletin board community has not "come and gone." Since RBBS' first release, the bulletin board or BBS has been a steady and stable platform for communications. Its rather ironic how the faltering trends have always said the BBS was dead. When in actuality, it was they who where dying. I personally have been a BBS sysop for 11 years and have seen many changes. Perhaps none as dramatic as the InterNet. Since its commercialization I have constantly watched it embroil its self in a tangled web of various crimes, from QUAKE being stolen off of their home page to people being murdered and children being molested. If this is the future of communications, then I'll gladly accept my place in a dying bread of computer users. I can honestly say the worse thing that happened on my system is I got complaint because the users did not like my ANSI. I feel the InterNet (in its current state) will not be able to hold its captive audiences the way it does now for the following reason. This is probably my greatest complaint against the InterNet. There are inadequate measure to provide a secure environment for children. Many companies have jumped on the band wagon of writing programs the can supposedly block sites. This is total gibberish. Companies selling paranoia in place of proper parental guidance is idiotic. The level of greed in these companies ask for their "programs" is just as preposterous. Filters and blockers are NOT the answer to controlling unwanted garbage on the InterNet. If we wanted to rid the InterNet of the kind of trash (pornography in inappropriate places, child molesters, and scam artists) then we first must deal with reputable InterNet Service Providers (ISP) and rid the FIDONEWS 14-20 Page 3 19 May 1997 market of ISPs that only want to line their pockets. An ISP that will let any one on for the money is 75% of the reason as to why the InterNet has become what it is. Adult material has its place, but NOT in a missing child news group or of a similar place. At one time I was devout reader of MISSING_CHILD, after the InterNet connection was made, the trash that came from the InterNet was intolerable. I no longer carry the echo. I do NOT like the idea of my users reading about how some moron who supposedly raped a ten year old girl, especially since my system is family oriented. I like it even less when ISP such as AOL call the NewsGroups (message areas) Bulletin Boards. Not only do they drop their unwanted trash in the NewsGroups, but they have the audacity to compare themselves with the Bulletin Board community. Talk about a frame up, they pollute and WE (the true Bulletin Boards) get the black eye. This is truly pathetic. We all know about acid boards, pirate BBSes, and hackers clubs. They have been around since the start of the Bulletin Board circuit. None of these, in my opinion, even remotely have damaged the integrity of the BBS community compared to the InterNet. I have no place for anarchy, chaos, unruliness. These three components are the heart of the demise of the InterNet. The InterNet has its place, but NOT as the expense of our morals and dignity. I believe the InterNet will survive ONLY if the ISP owners take more community responsibility. The lawlessness of the InterNet will be its own undoing. ----------------------------------------------------------------- FIDONEWS 14-20 Page 4 19 May 1997 ================================================================= GETTING TECHNICAL ================================================================= Proposed Update of FTS-0001 Product Codes by Lee Kindness, 2:259/7 The following text is an updated section of fts-0001.016 to allow use of 16 bit product codes. 16bit product codes used in type 2+_ and type 2.2 packet headers break a type 2 8bit product code. This solution preserves the 8 bit code while permitting a 16 bit code. Changes are marked by '|' This was submitted to the FTSC over 7 months ago with no result. If a 'new FTSC' is reading then consider this a submission. Keep me posted. F Network Layer: the Network's View of the System, Routing and Packets 1. Network Layer Data Definition : the Packet Header The packet contains messages in packed format to be transferred over the net during a connection. As this data structure is transferred, its definition is critical to FidoNet. A packet may contain zero or more packed messages. A packet without messages is often generated as a poll packet. Every packet begins with a packet header. The fields of the packet header are of fixed length. Packet Header Offset dec hex .-----------------------------------------------. 0 0 | origNode (low order) | origNode (high order) | +-----------------------+-----------------------+ 2 2 | destNode (low order) | destNode (high order) | +-----------------------+-----------------------+ 4 4 | year (low order) | year (high order) | +-----------------------+-----------------------+ 6 6 | month (low order) | month (high order) | +-----------------------+-----------------------+ 8 8 | day (low order) | day (high order) | +-----------------------+-----------------------+ 10 A | hour (low order) | hour (high order) | +-----------------------+-----------------------+ 12 C | minute (low order) | minute (high order) | +-----------------------+-----------------------+ 14 E | second (low order) | second (high order) | +-----------------------+-----------------------+ 16 10 | baud (low order) | baud (high order) | +-----------------------+-----------------------+ FIDONEWS 14-20 Page 5 19 May 1997 18 12 | 0 | 2 | 0 | 0 | +-----------------------+-----------------------+ 20 14 | origNet (low order) | origNet (high order) | +-----------------------+-----------------------+ 22 16 | destNet (low order) | destNet (high order) | +-----------------------+-----------------------+ | 24 18 | prodCode1 | serialNo | +-----------------------+-----------------------+ 26 1A | | | password (some impls) | | eight bytes | | null padded | | | +-----------------------+-----------------------+ 34 22 | origZone (low) (opt) | origZone (high) (opt) | +-----------------------+-----------------------+ 36 24 | destZone (low) (opt) | destZone (high) (opt) | +-----------------------+-----------------------+ 38 26 | fill | | ~ 18 bytes ~ | | +-----------------------+-----------------------+ | 56 38 | prodCode2 (low byte) | prodCode2 (high byte) | +-----------------------+-----------------------+ 58 3A | zero or more | ~ packed ~ | messages | +-----------------------+-----------------------+ | 0 | 0 | 0 | 0 | `-----------------------+-----------------------' Packet = PacketHeader { PakdMessage } 00H 00H PacketHeader = origNode (* of packet, not of messages in packet *) destNode (* of packet, not of messages in packet *) year (* of packet creation, e.g. 1986 *) month (* of packet creation, 0-11 for Jan-Dec *) day (* of packet creation, 1-31 *) hour (* of packet creation, 0-23 *) minute (* of packet creation, 0-59 *) second (* of packet creation, 0-59 *) baud (* max baud rate of orig and dest, 0=SEA *) PacketType (* old type-1 packets now obsolete *) origNet (* of packet, not of messages in packet *) destNet (* of packet, not of messages in packet *) | prodCode1 (* see below *) serialNo (* binary serial number (otherwise null)*) password (* session password (otherwise FIDONEWS 14-20 Page 6 19 May 1997 null) *) origZone (* zone of pkt sender (otherwise null) *) destZone (* zone of pkt receiver (otherwise null)*) fill[18] | prodCode2 (* see below *) PacketType = 02H 00H (* 01H 00H was used by Fido versions before 10 which did not support local nets. The packed message header was also different for those versions *) | prodCode1 contains the packers Fidonet product code (see | FSC-0090, ftscprod.doc) if it is in the range 0x00 to 0xFE | (0xFE being reserved for products 'in development'). If the | Fidonet product code is in the range 0x100 to 0xFFF0 then it is | stored in prodCode2, with 0xFF being inserted into prodCode1. | Codes 0xFFF1 to 0xFFFF are reserved. The remainder of the packet consists of packed messages. Each packed message begins with a message type word 0200H. A pseudo-message beginning with the word 0000H signifies the end of the packet. ----------------------------------------------------------------- Proposed Update to FTS-0005 by Lee Kindness, 2:259/7 A number of months (at least 7) back i submitted this proposed update to the FTSC with no response... So for your comments... If a 'new FTSC' is reading then consider this a submission. Keep me posted. The Distribution Nodelist, FTS-0005 Proposal for revision 4, 15 May 1997 Originally by Ben Baker Amended by Rick Moore, 1:115/333, February 5, 1989 Amended by David Nugent, 3:632/348, February 27, 1996 Amended by Lee Kindness, 2:259/7, May 15, 1997 Copyright 1986-1996 by the FidoNet Technical Standards Committee. All rights reserved. Duplication and/or distribution permitted for non-commercial purposes only. This document supersedes and replaces the document known under | the names of FSC002, FSC-0002, and FTS-0002. Significant changes, | which excludes mere formatting changes, to revision 3 of this FIDONEWS 14-20 Page 7 19 May 1997 | document have been marked by ':' the the leftmost column. This document defines the format and content of the nodelist for the Public FidoNet Network (PFN) as published on Friday of each week. This format is historically known as the "St. Louis nodelist format". The PFN is an international network of independently owned electronic mail systems, most with interlocking electronic bulletin board systems. The distribution nodelist, or simply "nodelist", is the glue which holds the network together. It is the PFN's "phone book" and it defines the top-level network structure and is the means by which FidoNet retains its integrity as a point-to-point mail network. THE NODELIST The nodelist is published as an ASCII text file named NODELIST.nnn, where nnn is a three digit number representing the day-of-year of the Friday publication date, with zeros filling positions to the left if necessary. This file is packed into a archive file named NODELIST.?nn, where 'nn' are the last two digits of day-of-year, and the character at the position of the '?' indicating the type of compression used. Conventions as to which compression method is used for the distributed nodelist is a matter of local policy and is usually determined by each zone's | Zone Coordinator. Common conventions are: | NODELIST.Znn : Zip | NODELIST.Ann : Arc | NODELIST.Lnn : Lzh/Lha | NODELIST.Jnn : ARJ As stated above, NODELIST.nnn is an ASCII text file. It contains two kinds of lines; comment lines and data lines. Each line is terminated with an ASCII carriage return and line feed character sequence, and contains no trailing white-space (spaces, tabs, etc.). The file is terminated with a DOS end-of-file character (character value 26 decimal, or "control-Z"). Comment lines contain a semicolon (;) in the first character position followed by zero or more alphabetic characters called "interest flags". A program which processes the nodelist may use comment interest flags to determine the disposition of a comment line. The remainder of a comment line (with one exception, treated below) is free-form ASCII text. There are five types of comments flags: ;S This is of particular interest to Sysops ;U This is of particular interest to BBS users ;F This should appear in any formatted "Fido List" ;A This is of general interest (shorthand for ;SUF) ;E This is an error message inserted by the nodelist generator ; This comment may be ignored by a nodelist processor FIDONEWS 14-20 Page 8 19 May 1997 The first line of a nodelist is a special comment line containing identification data for the particular edition of the nodelist. The following is an example of the first line of a nodelist: ;A FidoNet Nodelist for Friday, July 3, 1987 -- Day number 184 : 15943 This line contains the general interest flag, the day, date, and three-digit (zero-filled) day-of-year number of publication, and ends with a 5 digit decimal number with leading zeros, if necessary. This number is the decimal representation of a check value derived as follows: Beginning with the first character of the second line, a 16 bit cyclic redundancy check (CRC) is calculated for the entire file, including carriage return and line feed characters, but not including the terminating EOF character. The check polynomial used is the same one used for many file transfer protocols: 2**16 + 2**12 + 2**5 + 2**0 The CRC may be used to verify that the file has not been edited. The importance of this will become evident in the discussion of NODEDIFF, below. CRC calculation techniques are well documented in various technical references, and will not be treated further here. The content of the remaining comments in the nodelist are intended to be informative. Beyond the use of interest flags for distribution, a processing program need not have any interest in them. A nodelist data line contains eight variable length "fields" separated by commas (,). No space characters are allowed in a data line, and underscore characters are used in lieu of spaces. The term "alphanumeric character" is defined as the portion of the ASCII character set from 20 hex through 7E hex, inclusive. The following discussion defines the contents of each field in a data line. Field 1: Keyword The keyword field may be empty, or may contain one of the following: Zone Begins the definition of a geographic zone and define its coordinator. All the data lines following a line with the "Zone" keyword down to, but not including, the next occurrence of a "Zone" keyword, are regions, networks, and nodes within the defined zone. Node entries defined immediately after the "Zone" keyword and before the next region or host entry are known as zone administrative nodes. These are allocated by the Zone Coordinator for use by nodes FIDONEWS 14-20 Page 9 19 May 1997 in the entire zone; for example, mail gateways between FidoNet zones. Region Begins the definition of a geographic region and defines its coordinator. All the data lines following a line with the "Region" keyword down to, but not including, the next occurrence of a "Zone", "Region", or "Host" keyword, are independent nodes within the defined region. Host Begins the definition of a local network and defines its network coordinator. All the data lines following a line with the Host keyword down to, but not including, the next occurrence of a "Zone", "Region", or "Host" keyword, are local nodes, members of the defined local network. Hub Begins the definition of a routing sub-unit within a multi-level local network. The hub is the routing focal point for nodes listed below it until the next occurrence of a "Zone", "Region", "Host", or "Hub" keyword. The hub entry MUST be a redundant entry, with a unique number, for one of the nodes listed below it, within its hub segment. This is necessary because some nodelist processors eliminate these entries in all but the local network. Pvt Defines a private node with unlisted number. Private nodes are only allowed as members of local networks. | Point | Defines a private point off a node. Should not be used in | the Fidonet nodelist, but rather private 'pointlists', | local net level nodelists and nodelists in other Fidonet | technology networks. Hold Defines a node which is temporarily down. Mail may be sent to it and is held by its host or coordinator. Down Defines a node which is not operational. Mail may NOT be sent to it. This keyword may not be used for longer than two weeks on any single node, at which point the "down" node is to be removed from the nodelist. FIDONEWS 14-20 Page 10 19 May 1997 The field contains no text (not the sequence ""), and defines a normal node entry. Only one of these may be used in any individual data line. | Field 2: Zone/Region/Net/Node/Point number This field contains only numeric digits and is a number in the range of 0 to 32767. If the line had the "Zone", "Region", "Host" | or "Point" keyword, the number is the zone, net, region or point number, and the node has an implied node number of 0. Otherwise, the number is the node number. The zone number, region or net number, and the node number, taken together, constitute a node's FidoNet address. Zone numbers must be unique. Region or net numbers must be unique within their zone, hub numbers unique be within their net, node numbers unique within their net (and region, for regional independent nodes, zone for zone administrative entries). Duplicate node numbers under different hubs within the same net | are not allowed. Point numbers must be unique within their node. Field 3: Node name This field may contain any alphanumeric characters other than commas and spaces. Underscores are used to represent spaces, and a comma delimits the end of the field. This is the name by which the node is known, usually as determined by the node or the | coordinator responsible for compiling the segment. For zone, | region and host entries this field should indicate its (rough) | geographical area. Field 4: Location This field may contain any alphanumeric characters other than commas and spaces. Underscores are used to represent spaces. This field contains the location of the node. It is usually expressed as the primary local location (town, suburb, city, etc.) plus an identifier of the regional geopolitical administrative district (state, province, department, county, etc.). Wherever possible, standard postal abbreviations for the major regional district should be used (IL, BC, NSW, etc.). Field 5: Sysop name This field may contain any alphanumeric characters other than commas and spaces. Underscores are used to represent spaces. This | is the name of the SYSTEM OPERATOR, entries such as "postmaster", | "uucp" and aliases are not permitted. Field 6: Phone number FIDONEWS 14-20 Page 11 19 May 1997 This field contains at least three and usually four numeric sub- fields separated by dashes (-). The fields are country code, city or area code, exchange code, and number. The various parts of the phone number are frequently used to derive cost and routing information, as well as what number is to be dialed. A typical example of the data in a phone number field is 1-800-555- 1212, corresponding to country 1 (USA), area 800 (inbound WATS), exchange 555, and number 1212. Alternatively, this field may contain the notation | "-Unpublished-" in the case of a private node or point. In this | case, the keyword "Pvt" or "Point" must appear at the start of the line. Field 7: Baud rate This field contains one of the values: 300, 1200, 2400, 9600, 19200, or 38400. This baud rate is indicative only of the maximum baud rate that may be expected when connecting to a node and is generally of use only where a calling node needs to adjust the baud rate used to dial to the caller's modem speed in order to achieve a connection, a requirement that with modem technology available in 1996 is rarely if ever needed. This information is largely superseded by modem protocol flags (see next section) where any two nodes using a common protocol may have other expectations with regards to actual transfer rates. Use of the baud rate field | alone is therefore depreciated. FSC-0091 should be consulted with | regard to the special use of '300' Field 8 - Flags This optional field contains data about the specific operation of the node, such as file requests, modem protocol supported, etc. Any text following the seventh comma on a data line is taken collectively to be the flags field. The required format is zero or more sub-fields, separated by commas. Each sub-field consists | of a flag, possibly followed by a value. Entries here are update | to or succeeded in the epilogue of the Nodelist. The flags field | has no maximum size. The following flags define special operating conditions: Flag Meaning CM Node accepts mail 24 hours a day MO Node does not accept human callers LO Node accepts calls only from valid listed node numbers in the current FidoNet nodelist The following flags define modem protocols supported: FIDONEWS 14-20 Page 12 19 May 1997 Flag Meaning V21 ITU-T V21 300 bps full duplex V22 ITU-T V22 1200 bps full duplex V29 ITU-T V29 9600 bps half duplex V32 ITU-T V32 9600 bps full duplex V32b ITU-T V32bis 14400 bps full duplex V33 ITU-T V33 V34 ITU-T V34 28800 bps full duplex | V110L ITU-T V.110 19k2 async ('low'). | V110H ITU-T V.110 38k4 async ('high'). | V120L ITU-T V.120 56k async, layer 2 framesize 259, | window 7, modulo 8. | V120H ITU-T V.120 64k async, layer 2 framesize 259, | window 7, modulo 8. | X75 ITU-T X.75 SLP (single link procedure) | with 64kbit/s B channel; | layer 2 max.framesize 2048, window 2, non-ext.mode | (modulo 8); | layer 3 transparent (no packet layer). | ISDN Other ISDN configurations. Use *only* if none of the | above fits | NOTE: ISDN nodes which do not accept modem calls must use | '300' in the baud field, see FSC-0091 for more details. H96 Hayes V9600 HST USR Courier HST H14 USR Courier HST up to 14.4Kbps H16 USR Courier HST up to 16.8Kbps PEP Packet Ensemble Protocol CSP Compucom Speedmodem | V32T V.32 Terbo mode (implies V32b) VFC Rockwell's V.Fast Class | ZYX Zyxel 16.8 Kbps (implies V32b & V42b) | Z19 Zyxel 19.2 Kbps (implies V32b, V42b & ZYX) NOTE: Many V22 modems also support Bell 212A. | If no modem flag is given, ITU-T V.22 is assumed within zone 2 | for 1200bps, while Bell 212A is assumed for 1200 bps systems in | other zones, ITU-T V22bis is assumed for 2400 bps systems. | A separate modem capability flag should not be used when it can be | determined by the modem flag. For instance, a modem flag of HST | implies MNP. V32B implies V32 and V42B implies V42. MNP,HST and | V32,V32B and V42,V42B flag pairs are unnecessary. H14 implies HST | and H16 implies H14 as well as V42b. The following flags define type of error correction available. A separate error correction flag should not be used when the error correction type can be determined by the modem flag. For instance, a modem flag of HST implies MNP, V32b implies V32 and V42b implies V42. Therefore MNP+HST, H14+MNP, H16+MNP, V32+V32b FIDONEWS 14-20 Page 13 19 May 1997 and V42+V42b flag pairs are redundant and should not be used. Flag Meaning MNP Microcom Networking Protocol error correction V42 ITU-T LAP-M error correction w/fallback to MNP 1-4 V42b ITU-T LAP-M error correction w/fallback to MNP 1-5 | (V42 implied) The following flags define the type(s) of compression of mail | packets supported plus message encoding. Flag Meaning MN No compression supported | ENC The node accepts inbound encrypted mail NOTE: While FidoNet nodes usually exchange mail using a variety of different file compression formats negotiated between individual systems, the presence of this flag indicates the INABILITY TO RECEIVE MAIL compressed using the SEA ARC version 5 compression format and/or named according to the ARCmail 0.6 mail bundle naming method. This is, by convention, the most common mail compression format in use within FidoNet. The presence of this flag would normally indicate that all mail should be sent uncompressed unless there is some overriding arrangement with the receiving system. The following flags indicate the types of file and file update requests supported. Flag Meaning XA Bark and WaZOO file/update requests XB Bark file/update requests, WaZOO file requests XC Bark file requests, WaZOO file file/update XP Bark file/update requests XR Bark and WaZOO file requests XW WaZOO file requests XX WaZOO file/update requests The following flag defines gateways to other domains (mail networks). Flag Meaning Gx..x Gateway to domain 'x..x', where 'x..x` is a string of alphanumeric characters. NOTE: Valid values for 'x..x' are assigned by the FidoNet International Coordinator or the person appointed as Internetworking Coordinator by the FidoNet FIDONEWS 14-20 Page 14 19 May 1997 International Coordinator. Current valid values of 'x..x' may usually be found in the notes at the end of the current FidoNet nodelist. The most common gateway flag is "GUUCP", to denote a gateway to the Internet mail system that gates on behalf of the fidonet.org internet domain. The following flags define the dedicated mail periods supported. They have the form "#nn" or "!nn" where nn is the UTC hour the mail period begins, '#' indicates Bell 212A compatibility, and '!' indicates incompatibility with Bell 212A. Flag Meaning #01 Zone 5 mail hour (01:00 - 02:00 UTC) #02 Zone 2 mail hour (02:30 - 03:30 UTC) #03 Zone 4 mail hour (08:00 - 09:00 UTC) #09 Zone 1 mail hour (09:00 - 10:00 UTC) #18 Zone 3 mail hour (18:00 - 19:00 UTC) #20 Zone 6 mail hour (20:00 - 21:00 UTC) NOTE: When applicable, the mail period flags may be strung together with no intervening commas, e.g.. "#02#09" or "!02!09". Only mail hours other than that standard within a node's zone should be given. Since observance of mail hour within one's zone is mandatory, it should not be indicated. | Txx Availability flag for non-CM nodes indicating the | hours during which the node is available in addition | to ZMH. This must be in accordance with the recommen- | dations in FSC-0062 and the reference table reproduced | below. ATTENTION : All times must be UTC! | | Letter Time Letter Time Letter Time Letter Time Letter Time | ------+----+------+----+------+----+------+----+------+----+ | A 0000 F 0500 K 1000 P 1500 U 2000 | a 0030 f 0530 k 1030 p 1530 u 2030 | B 0100 G 0600 L 1100 Q 1600 V 2100 | b 0130 g 0630 l 1130 q 1630 v 2130 | C 0200 H 0700 M 1200 R 1700 W 2200 | c 0230 h 0730 m 1230 r 1730 w 2230 | D 0300 I 0800 N 1300 S 1800 X 2300 | d 0330 i 0830 n 1330 s 1830 x 2330 | E 0400 J 0900 O 1400 T 1900 | e 0430 j 0930 o 1430 t 1930 The following flag defines user-specific values. If present, this flag MUST be the last flag present in a nodelist entry. Flag Meaning Ux..x A user-specified string, which may contain any alphanumeric character except blanks. This string FIDONEWS 14-20 Page 15 19 May 1997 may contain one to thirty-two characters of information that may be used to add user-defined data to a specific nodelist entry. NOTE: Ux..x flags are the mechanism by which new flags may be experimentally introduced into the nodelist for a trial period to assess their worth. They are therefore of a temporary nature, and after their introduction they are eventually either promoted to a non-U flag or dropped from use altogether. | The FTSC recognizes that the FidoNet International Coordinator(IC) is the ultimate authority over what appears in the FidoNet nodelist. Also, FTSC is by definition a deliberative body, and adding or changing a flag may take a considerable amount of time. Therefore, the FidoNet International Coordinator may temporarily make changes or additions to the flags as defined in this document. The FidoNet International Coordinator will then consult with FTSC over the changes needed to this document to reflect these temporary changes. The following are examples of nodelist data lines: Host,102,SOCALNET,Los_Angeles_CA,Richard_Martz,1-213-874-9484,2400,XP ,101,Rainbow_Data,Culver_City_CA,Don_Brauns,1-213-204-2996,2400, THE NODEDIFF With more than thirty-five thousand nodes as of this date (1996), the nodelist, even in archive form, is a document of substantial size. Since distribution of the nodelist occurs via electronic file transfer, this file is NOT routinely distributed. Instead, when a new nodelist is prepared weekly, it is compared with the previous week's nodelist, and a file containing only the differences is created and distributed. The distribution difference file, called NODEDIFF.nnn, where nnn is the day-of-year of publication, is actually an editing script which will transform the previous week's nodelist into the current nodelist. A definition of its format follows: The first line of NODEDIFF.nnn is an exact copy of the first line of LAST WEEK'S nodelist (i.e. the first line of the nodelist to which the current difference file applies). This is used as a first-level confidence check to insure that the correct file is being edited. The second and subsequent lines are editing commands and data. There are three editing commands and all have the same format: is a 1 letter command, one of A, C, or D. FIDONEWS 14-20 Page 16 19 May 1997 is a decimal number greater than zero, and defines the number of lines to be operated on by the command. Each command appears on a line by itself. The commands have the following meanings: Ann Add the following nn lines to the output file. Cnn Copy nn unchanged lines from the input to the output file. Dnn Delete (or skip) nn lines from the input file. The following illustrate how the first few lines of a hypothetical NODEDIFF.213 might look: ;A Friday, July 25, 1986 -- Day number 206 : 27712 D2 A2 ;A Friday, August 1, 1986 -- Day number 213 : 05060 ;A C5 This fragment illustrates all three editing commands. The first line is the first line from the previous nodelist, NODELIST.206. The next line says "delete the first two lines" from NODELIST.206. These are the identification line and the line following it. The next command says "add the next two lines" to NODELIST.213 at the "current" location. The two data lines are followed by a command which says "copy five unchanged lines" from NODELIST.206 to NODELIST.213. Notice that the first line added will ALWAYS contain the new nodelist CRC, so that the software applying the changes to the old nodelist may check the result of its editing. Since only the differences will be distributed, it is important to insure the accuracy of the newly created nodelist. This is the function of the CRC mentioned above. It is sufficient for a program designed to perform the above edits to pick the CRC value from the first line added to the output file, then compute the CRC of the rest of the output file. If the two CRCs do not agree, one of the input files has been corrupted. If they do agree, the probability is very high (but not 100%) that the output file is accurate. For actual distribution, NODEDIFF.nnn is packed into an archive file named NODEDIFF.?nn, where 'nn' are the last two digits of day-of-year, and '?' indicates the compression format used. NODELIST COMPILATION This section is included for tutorial reasons and is not intended as a definition of any specific method by which FidoNet MUST compile its weekly nodelist. It merely represents an attempt to document the method by which it currently does so. It is intended to be explanatory, and seeks to answer commonly asked questions, such as how the nodelist is compiled and where the information comes from, why the nodelists used in different FidoNet zones are FIDONEWS 14-20 Page 17 19 May 1997 not the same document, and why the difference file generated for use in one FidoNet zone cannot be applied to the nodelist generated for use in a different zone, even though the week numbers match. Nodelists are compiled via a distributed method, which follows the same structure as the FidoNet coordinator hierarchy. At the lowest level, network coordinators maintain a list of the nodes in their network and are responsible for the addition, removal and correction of individual node's listings in their "segment" (as portions of the full nodelist are called). In some larger networks, it is common for this job to be shared with hub coordinators appointed by the net coordinator, though the responsibility for those hub segments still remains with the network coordinator. At a nominated day during the week, before the regional level segment is submitted to the zone coordinator, individual net coordinators submit their segments to the regional coordinator who subsequently compiles these segments and transmits the merged copy to the zone coordinator. These are combined by the zone coordinator with the separate segments of other zones and compiled into that zone's version of the world nodelist. This world nodelist is then compared with the previous week's version, a difference file is generated and subsequently distributed throughout the zone. In some cases, in the interest of saving in transmission times and therefore costs, the compilation process itself may be better served by the submission of DIFFERENCE FILES rather than full net- or region-level segments. Each coordinator therefore retains a copy of the previously submitted segments and applies difference files to those to derive the new one. This process is exactly identical to the NODEDIFF/NODELIST scenario described earlier in this document, with the same first line and CRC validation method used to guard the integrity of the nodelist segments. For a number of reasons, it is important that publication of the nodelist be as timely as possible. These reasons include: the nodelist is a definitive list of valid FidoNet addresses that may receive mail, and must therefore be as correct and up-to-date as possible to save nodes the unnecessary expense of mail routed to possibly non-existing addresses; the nodelist contains the list of telephone numbers that may be called by any user of the FidoNet nodelist and should therefore be accurate so as not to unduly annoy owners of those phone numbers should a listed node go down and an unsuspecting telephone subscriber inherit the same telephone number. Given this constraint, the expense of international calls and the fact that FidoNet is a worldwide network that exists in many time zones, it may be unreasonable to expect the compilation of the nodelist to be delayed until each zone coordinator can transmit their most up-to-date zone segment to a central authority for compilation and subsequent redistribution in any week. For the FIDONEWS 14-20 Page 18 19 May 1997 sake of expedience, each zone instead maintains its own separate world nodelist which contains a compilation of the current zone's latest segments and including the most current copy to hand of all other FidoNet zone's segments. The zone level nodelist generated each week by each zone coordinator is then transmitted to all other zone coordinators for inclusion into their separate world nodelist as timing permits. In theory, then, the only difference between nodelists distributed in each zone in any week are accounted for by timing differences in the exchange of each zone's separate segment. In practice, other constraints may interfere with timeliness, such as the difficulty and expense of international telephonic communications. Also, another point of variance is introduced by the fact that each zone usually includes its own zone segment first into its world nodelist to assist - amongst other things - software that uses the nodelist for index generation. Some software in common use in FidoNet indexes the nodelist according to its sequential order (e.g. version 5 and 6 compiled nodelist formats), and including the current zone first before others will have a beneficial effect on software performance. ----------------------------------------------------------------- Suggested use of Nodelist Fields by Lee Kindness, 2:259/7 A FTSC proposal I would submit to the FTSC if they actually done something... For your comments... If a 'new FTSC' is reading then consider this a submission. Keep me posted. Suggested use of Nodelist Fields Revision: 1, 15 May 1997 Lee Kindness 2:259/7, wangi@earthling.net FIDONEWS 14-20 Page 19 19 May 1997 http://www.scms.rgu.ac.uk/students/cs_yr94/lk/fido.html Introduction ============ This document makes recommendations on the use of various fields in the distribution nodelist (St. Louis nodelist format", fts-0005). Naturally it is the choice of the *C's if they want to use them. Remember the fts-0005 requirements should till be adhered to. Field 3, Node Name ================== The node name field should be no more than 20 characters long. For comparison in nodelist.122'1997 the minimum entry was 1, maximum 51! and the average was 14. For zone entries this field should contain a description of the zones area, (eg North America, Europe). For region entries it should contain the country/state, for host entries the local area name and for hub entries a description of the area the hub serves. Field 4, Location ================= This field contains the location of the node. It should usually be expressed as the primary local location (town, suburb, city, etc.) plus an identifier of the regional geopolitical administrative district (state, province, department, county, etc.). Wherever possible, standard postal abbreviations for the major regional district should be used (IL, BC, NSW, UK, etc.). For zone and region entries this field should also have the julian day of segment creation appended to it (eg "Somearea_(122)") to aid checks on the validity of the nodelist. Field 5, Sysop Name =================== This field contains the name of the system operator. Entries such as "postmaster" and "uucp" should not be used. Aliases should not be permitted in this field (as they give Fidonet a 'less respectable' image). ----------------------------------------------------------------- Proposal For Standard Fidonet Addressing by Lee Kindness, 2:259/7 A FTSC proposal I would submit to the FTSC if they actually done something... For your comments... FIDONEWS 14-20 Page 20 19 May 1997 If a 'new FTSC' is reading then consider this a submission. Keep me posted. Standard Fidonet Addressing Revision: 1, 15 May 1997 Lee Kindness 2:259/7, wangi@earthling.net http://www.scms.rgu.ac.uk/students/cs_yr94/lk/fido.html Introduction ============ This document describes the standard form of addressing in Fidonet today along with the common method of addressing via internet gateways. In addition it proposes an extended addressing syntax, useful for routing purposes. This is a draft for comments and suggestions. Standard Fidonet Addressing =========================== Fidonet addressing uses the following format: ZZ:NN/FF.PP@DO where the fields refer to... ZZ - Zone Number: The zone the node is part of. Min: 1 Max: 32767 If 'ZZ:' is missing then assume 1 as the zone. NN - Net Number: The network the node is a member of. Min: 1 Max: 32767 Must be present. FF - Node Number: The actual node number. Min: -1 Max: 32767 Must be present. PP - Point Number: If the system is a point rather than a node then this is their point number off the node. Min: 0 Max: 32767 If '.PP' is missing then assume 0 (ie not a point) as the point number. DO - Domain: The name of the 'Fidonet Technology Network'. Maximum length of 8 characters. The domain should not include periods, thus 'fidonet.org' is invalid (should be fidonet). If '@DO' is missing then fidonet can be assumed. The following are all valid examples: FIDONEWS 14-20 Page 21 19 May 1997 1:234/5.6@fidonet (a '5D' address) => 1:234/5.6@fidonet 2:34/6.78 (a '4D' address) => 2:34/6.78@fidonet 4:610/34 (a '3D' address) => 4:610/34.0@fidonet 123/45 (a '2D' address) => 1:123/45.0@fidonet 955:95/2@othernet (another FTN) => 955:95/2.0@othernet 2:259/-1 (node application) => 2:259/-1.0@fidonet The limits on each various part of the address are a result of fts-0005 (zone, net, node, point), fsc-0045 (domain) and Policy 4 (-1 node address for node application). Internet Gateway Addressing =========================== An internet user can send email/netmail to a fidonet user via one of the fidonet->internet gateway systems (it's out-with the scope of this document to describe the semantics of posting). The internet user would send an email to a Fidonet user by using an email address of the following syntax: user.name@pPP.fFF.nNN.zZZ.gateway.domain where the fields refer to... user.name - Name: Name of the user the email is being sent to, spaces replaced by periods. PP - Point Number: As Fidonet address (FA) If '.pPP' is missing 0 is assumed. FF - Node Number: As FA Must be present. NN - Net Number: As FA Must be present. ZZ - Zone Number: As FA Must be present. gate.way - Gateway: Internet domain of the gateway, for example 'fidonet.org'. Must be present. The following are all valid examples (assuming 'fidonet.org' is an internet gateway): joe.bloggs@p6.f5.n234.z1.fidonet.org => 1:234/5.6@fidonet harry.cat@p78.f6.n34.z2.fidonet.org => 2:34/6.78@fidonet i.be.jolly@f34.n610.z4.fidonet.org => 4:610/34.0@fidonet and if 'foo.bar.org.uk' is a gateway for 'othernet': louise.hat@f2.n95.z955.foo.bar.org.uk => 955:95/2.0@othernet FIDONEWS 14-20 Page 22 19 May 1997 Routing Address Syntax ====================== The two previous address types (Fidonet and Internet->Fidonet gateway) are common practice, this however is a suggested standard of addressing for routing tables. The routing address has the following syntax: DD:ZZ:RR:NN:HH:FF:PP where the fields refer to: DD - Domain: As FA Must be present, even if blank (ie a leading ':') to ensure we always have 6 ':'s in an address to aid pattern matching. ZZ - Zone Number: As FA Must be present. RR - Region Number: The region (from fts-0005 nodelist) that the following network is in. Min: 1 Max: 32767 Must be present. NN - Net Number: As FA Must be present. HH - Hub: The hub (from fts-0005 nodelist) that the node is under, or 0 (host hub). Min: 1 Max: 32767 Must be present. FF - Node Number: As FA Must be present. PP - Point Number: As FA Must be present. ':' has been chosen as the separator as it is not a POSIX regular expression character or globing character (where as '.' is) and thus always easy use of wildcards on the address. The following points should be noted: 1. All addresses have 6 ':'s 2. The domain is at the front, the address gets more specific to the right 3. Nodes have 0 as their point number 4. A zone net has identical zone, region and net fields 5. A region net has identical region and net fields Example fidonet addresses converted to routing addresses: fidonet:2:25:259:0:7:0 => 2:259/7.0@fidonet, region 25, hub 0 fidonet:1:1:1:0:23:0 => 1:1/23.0@fidonet, zone 1 net :955:9551:95:300:45:0 => 955:95/45.0, region 9551, hub 300 FIDONEWS 14-20 Page 23 19 May 1997 fidonet:2:25:25:0:0:0 => 2:25/0.0@fidonet, R25C cnet:12:34:341:100:1:7 => 12:341/1.7@cnet, region 34, hub 100 :2:25:259:300:300:0 => 2:259/300.0, region 25, hub 300 Example POSIX regular expression patterns on routing addresses: [a-z]*:[0-9]+:[0-9]+:[0-9]+:[0-9]+:[0-9]+:[0-9]+ (any address) [a-z]*(:[0-9]+)+ (any address) fidonet:2:25:[0-9]+:[0-9]+:[0-9]+:[0-9]+ (region 25 node) fidonet:2:25(:[0-9]+)+ (region 25 node) fidonet:1:12:125(:[0-9]+)+ (all net 1:125 nodes) fidonet:1:12:125:200(:[0-9]+)+ (all hub 1:125/200 downlinks) fidonet:1:12:125:200:2:[0-9]+ (all 1:125/2 points) fidonet:1:12:125:[0-9]+:(25|34|56):0 (nodes 1:125/25.0, 1:125/34.0 and 1:125/56.0) Example 'DOS style' patterns on routing addresses: *:*:*:*:*:*:* (any address) fidonet:2:25:*:*:*:* (region 25 node) fidonet:1:12:125:*:*:* (all net 1:125 nodes) fidonet:1:12:125:200:*:* (all hub 1:125/200 downlinks) fidonet:1:12:125:200:2:* (all 1:125/2 points) fidonet:1:12:125:*:3*:0 (any net 1:125 nodes starting with 3) fidonet:1:12:125:*:3?:0 (net 1:125 nodes 30 thru 39) The standard doesn't define which standard of pattern matching to use, only the format of the addresses. These routing addresses would be used in routing tables and configurations. ----------------------------------------------------------------- FIDONEWS 14-20 Page 24 19 May 1997 ================================================================= COORDINATORS CORNER ================================================================= Nodelist-statistics as seen from Zone-2 for day 136 By Ward Dossche, 2:292/854 ZC/2 +----+------+------------+------------+------------+------------+--+ |Zone|Nl-108|Nodelist-115|Nodelist-122|Nodelist-129|Nodelist-136|%%| +----+------+------------+------------+------------+------------+--+ | 1 | 8675| 8675 0 | 8519 -156 | 8430 -89 | 8367 -63 |31| | 2 | 15993|15992 -1 |15952 -40 |15904 -48 |15879 -25 |59| | 3 | 800| 800 0 | 800 0 | 800 0 | 800 0 | 3| | 4 | 547| 547 0 | 548 1 | 543 -5 | 543 0 | 2| | 5 | 87| 87 0 | 87 0 | 87 0 | 87 0 | 0| | 6 | 1083| 1083 0 | 1083 0 | 1083 0 | 1083 0 | 4| +----+------+------------+------------+------------+------------+--+ | 27185|27184 -1 |26989 -195 |26847 -142 |26759 -88 | +------+------------+------------+------------+------------+ ----------------------------------------------------------------- FIDONEWS 14-20 Page 25 19 May 1997 ================================================================= NET HUMOR ================================================================= Date: Sat, 10 May 1997 01:03:58 -0700 From: Shari Organization: OREGON - USA To: webheads@softdisk.com Subject: Red Necks Guide to Computer Lingo References: Sender: owner-webheads@softdisk.com Reply-To: webheads@softdisk.com RED NECKS GUIDE TO COMPUTER LINGO ================================== Log On: Makin' the wood stove hotter. Log Off: Don't add no wood. Monitor: Keepin' an eye on the wood stove. Download: Gettin' the firewood off the pickup. Mega Hertz: When yer not careful down loadin'. Floppy Disk: Whatcha git from pilin' too much firewood. Ram: The hydrolic thingy that splits the firewood. Hard Drive: Getting' home in the winter season. Prompt: What you wish the mail was in the winter. Windows: What to shut when it's below 15.degrees. Screen: What 'cha need for the black fly season. Byte: That's what the flies do. Chip: What to munch on. Micro Chip: What's left in the bottom of the bag. Infrared: Where the left-overs go when Fred's around. Modem: What 'cha did to the hay fields. Dot Matrix: Farmer Matrix's wife. Lap Top: Where little kids feel comfy. Keyboard: Where ya hang your keys. Software: Them plastic eatin' utensils. Mouse: Whats eats the horses grain. Main Frame: Hold up the barn roof. Port: Fancy wine. Enter: C'mon in. Random Access Memory: You can't remember whatcha' paid for that new rifle when your wife asks. ==================================================== ----------------------------------------------------------------- FIDONEWS 14-20 Page 26 19 May 1997 ================================================================= COMIX IN ASCII ================================================================= Reason #173 to fear technology... o o o o o o ^|\ ^|^ v|^ v|v |/v |X| \| | /\ >\ /< >\ /< >\ /< >\ o> o o o o o o o \ x <\> <)> |\ /< >\ /< >\ /< >\ >> L Mr. ASCII does the Macarena. ----------------------------------------------------------------- FIDONEWS 14-20 Page 27 19 May 1997 ================================================================= ANSWERS OF THE WEEK ================================================================= --- Following message extracted from NETMAIL @ 1:18/14 --- By Christopher Baker on Thu May 15 12:06:53 1997 From: Michele Stewart @ 1:369/21 To: Christopher Baker @ 1:1/113 Date: 13 May 97 10:17:28 Subj: Page Thirty, FidoNews cc: Ron Amos > Ron Amos at 1:138/102 is looking for very old Nodelists that > he can file-request or download from an Internet site. > > Have you got any? > > If so, please send him a Netmail or send me an answer for next > week's Issue of FidoNews. A FidoNews .ANS would probably be > better since there are others who are also interested in > finding a source for old Nodelists for historical purposes. I've got 2 from 1989... June 16th and July 28th. You can f/req them as NL89_167.ZIP and NL89_209.ZIP. :) .\\ichele -30- ----------------------------------------------------------------- FIDONEWS 14-20 Page 28 19 May 1997 ================================================================= NOTICES ================================================================= Future History 3 Jun 1997 2 years since FidoNet had an International Coordinator. 6 Jun 1997 National Commemoration Day, Sweden. 12 Jun 1997 Independence Day, Russia. 1 Jul 1997 Canada Day - Happy Birthday Canada. 9 Jul 1997 Independence Day, Argentina. 1 Aug 1997 International FidoNet PENPAL [Echo] meeting in Dijon, France 13 Oct 1997 Thanksgiving Day, Canada. 1 Dec 1997 World AIDS Day. 10 Dec 1997 Nobel Day, Sweden. 12 Jan 1998 HAL 9000 is one year old today. 22 May 1998 Expo '98 World Exposition in Lisbon (Portugal) opens. 1 Dec 1998 Fifteenth Anniversary of release of Fido version 1 by Tom Jennings. 31 Dec 1999 Hogmanay, Scotland. The New Year that can't be missed. 1 Jan 2000 The 20th Century, C.E., is still taking place thru 31 Dec. 15 Sep 2000 Sydney (Australia) Summer Olympiad opens. 1 Jan 2001 This is the actual start of the new millennium, C.E. -- If YOU have something which you would like to see in this FIDONEWS 14-20 Page 29 19 May 1997 Future History, please send a note to the FidoNews Editor. ----------------------------------------------------------------- FIDONEWS 14-20 Page 30 19 May 1997 ================================================================= FIDONET SOFTWARE LISTING ================================================================= [This is a repeat of the SOF from 1419.] Ed. Latest Greatest Software Versions by Peter E. Popovich, 1:363/264 Note: Mid-May, I will phase out the entire "Old Info" section. As always, I'll be happy to process any information I get, either before or after it is phased out. -=- Snip -=- Submission form for the Latest Greatest Software Versions column OS Platform : Software package name : Version : Function(s) - BBS, Mailer, Tosser, etc. : Freeware / Shareware / Commercial? : Author / Support staff contact name : Author / Support staff contact node : Magic name (at the above-listed node) : Please include a sentence describing what the package does. Please send updates and suggestions to: Peter Popovich, 1:363/264 -=- Snip -=- MS-DOS: Program Name Version F C Contact Name Node Magic Name ---------------------------------------------------------------------- Act-Up 4.6 G D Chris Gunn 1:15/55 ACT-UP ALLFIX 4.40 T S Harald Harms 2:281/415 ALLFIX Announcer 1.11 O S Peter Karlsson 2:206/221 ANNOUNCE BGFAX 1.60 O S B.J. Guillot 1:106/400 BGFAX Binkley Docs 2.60 M F Bob Juge 1:1/102 BDOC_260.ZIP BinkleyTerm 2.60 M F Bob Juge 1:1/102 BDOS_260.ZIP BinkleyTerm-XE XR4 M F Thomas Waldmann 2:2474/400 BTXE_DOS CFRoute 0.92 O G C. Fernandez Sanz 2:341/70 CFR CheckPnt 1.0a O G Michiel vd Vlist 2:500/9 CHECKPNT FastEcho 1.45a T S Tobias Burchhardt 2:2448/400 FASTECHO FastEcho/16 1.45a T S Tobias Burchhardt 2:2448/400 FE16 FidoBBS (tm) 12u B S Ray Brown 1:1/117 FILES FrontDoor 2.12 M S JoHo 2:201/330 FD FrontDoor 2.20c M C JoHo 2:201/330 FDINFO GEcho 1.00 T S Bob Seaborn 1:140/12 GECHO GEcho/Plus 1.11 T C Bob Seaborn 1:140/12 GECHO GEcho/Pro 1.20 T C Bob Seaborn 1:140/12 GECHO GIGO 07-14-96 G S Jason Fesler 1:1/141 INFO GoldED 2.50 O S Len Morgan 1:203/730 GED GoldED/386 2.50 O S Len Morgan 1:203/730 GEX FIDONEWS 14-20 Page 31 19 May 1997 GoldED Docs 2.50 O S Len Morgan 1:203/730 GEM GoldNODE 2.50 O S Len Morgan 1:203/730 GEN Imail 1.75 T S Michael McCabe 1:1/121 IMAIL ImCrypt 1.04 O G Michiel vd Vlist 2:500/9 IMCRYPT InfoMail/86 1.21 O F Damian Walker 2:2502/666 INFOMAIL InfoMail/386 1.21 O F Damian Walker 2:2502/666 INFO386 InterEcho 1.19 T C Peter Stewart 1:369/35 IEDEMO InterMail 2.29k M C Peter Stewart 1:369/35 IMDEMO InterPCB 1.52 O S Peter Stewart 1:369/35 INTERPCB IPNet 1.11 O S Michele Stewart 1:369/21 IPNET JD's CBV 1.4 O S John Dailey 1:363/277 CBV Jelly-Bean 1.01 T S Rowan Crowe 3:635/727 JELLY Jelly-Bean/386 1.01 T S Rowan Crowe 3:635/727 JELLY386 JMail-Hudson 2.81 T S Jason Steck 1:285/424 JMAIL-H JMail-Goldbase 2.81 T S Jason Steck 1:285/424 JMAIL-G MakePl 1.9 N G Michiel vd Vlist 2:500/9 MAKEPL Marena 1.1 beta O G Michiel vd Vlist 2:500/9 MARENA Maximus 3.01 B P Tech 1:249/106 MAX McMail 1.0 M S Michael McCabe 1:1/148 MCMAIL MDNDP 1.18 N S Bill Doyle 1:388/7 MDNDP Msged 4.10 O G Andrew Clarke 3:635/728 MSGED41D.ZIP Msged/386 4.10 O G Andrew Clarke 3:635/728 MSGED41X.ZIP Opus CBCS 1.79 B P Christopher Baker 1:374/14 OPUS O/T-Track 2.66 O S Peter Hampf 2:241/1090 OT PcMerge 2.8 N G Michiel vd Vlist 2:500/9 PCMERGE PlatinumXpress 1.3 M C Gary Petersen 1:290/111 PX13TD.ZIP QuickBBS 2.81 B S Ben Schollnick 1:2613/477 QUICKBBS RAR 2.00 C S Ron Dwight 2:220/22 RAR RemoteAccess 2.50 B S Mark Lewis 1:3634/12 RA Silver Xpress Door 5.4 O S Gary Petersen 1:290/111 FILES Reader 4.4 O S Gary Petersen 1:290/111 SXR44.ZIP Spitfire 3.51 B S Mike Weaver 1:3670/3 SPITFIRE Squish 1.11 T P Tech 1:249/106 SQUISH StealTag UK 1.c... O F Fred Schenk 2:284/412 STEAL_UK StealTag NL 1.c... O F Fred Schenk 2:284/412 STEAL_NL T-Mail 2.599I M S Ron Dwight 2:220/22 TMAIL Telegard 3.02 B F Tim Strike 1:259/423 TELEGARD Terminate 4.00 O S Bo Bendtsen 2:254/261 TERMINATE Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK TosScan 1.01 T C JoHo 2:201/330 TSINFO TransNet 1.00 G S Marc S. Ressl 4:904/72 TN100ALL.ZIP TriBBS 11.0 B S Gary Price 1:3607/26 TRIBBS TriDog 11.0 T F Gary Price 1:3607/26 TRIDOG TriToss 11.0 T S Gary Price 1:3607/26 TRITOSS WaterGate 0.92 G S Robert Szarka 1:320/42 WTRGATE WWIV 4.24a B S Craig Dooley 1:376/126 WWIV WWIVTOSS 1.36 T S Craig Dooley 1:376/126 WWIVTOSS xMail 2.00 T S Thorsten Franke 2:2448/53 XMAIL XRobot 3.01 O S JoHo 2:201/330 XRDOS OS/2: Program Name Version F C Contact Name Node Magic Name ---------------------------------------------------------------------- ALLFIX/2 1.10 T S Harald Harms 2:281/415 AFIXOS2 BGFAX 1.60 O S B.J. Guillot 1:106/400 BGFAX FIDONEWS 14-20 Page 32 19 May 1997 Binkley Docs 2.60 M F Bob Juge 1:1/102 BDOC_260.ZIP BinkleyTerm 2.60 M F Bob Juge 1:1/102 BOS2_260.ZIP BinkleyTerm-XE XR4 M F Thomas Waldmann 2:2474/400 BTXE_OS2 CFRoute 0.92 O G C. Fernandez Sanz 2:341/70 CFR FastEcho 1.45a T S Tobias Burchhardt 2:2448/400 FE2 FleetStreet 1.19 O S Michael Hohner 2:2490/2520 FLEET GEcho/Pro 1.20 T C Bob Seaborn 1:140/12 GECHO GIGO 07-14-96 G S Jason Fesler 1:1/141 INFO GoldED 2.50 O S Len Morgan 1:203/730 GEO GoldED Docs 2.50 O S Len Morgan 1:203/730 GEM GoldNODE 2.50 O S Len Morgan 1:203/730 GEN ImCrypt 1.04 O G Michiel vd Vlist 2:500/9 IMCRYPT Maximus 3.01 B P Tech 1:249/106 MAXP Msged/2 4.10 O G Andrew Clarke 3:635/728 MSGED41O.ZIP PcMerge 2.3 N G Michiel vd Vlist 2:500/9 PCMERGE RAR 2.00 C S Ron Dwight 2:220/22 RAR2 Squish 1.11 T P Tech 1:249/106 SQUISHP T-Mail 2.599I M S Ron Dwight 2:220/22 TMAIL2 Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK XRobot 3.01 O S JoHo 2:201/330 XROS2 Windows (16-bit apps): Program Name Version F C Contact Name Node Magic Name ---------------------------------------------------------------------- BeeMail 1.0 M C Andrius Cepaitis 2:470/1 BEEMAIL FrontDoor APX 1.12 P S Mats Wallin 2:201/329 FDAPXW Windows (32-bit apps): Program Name Version F C Contact Name Node Magic Name ---------------------------------------------------------------------- BeeMail 1.0 M C Andrius Cepaitis 2:470/1 BEEMAIL Binkley Docs 2.60 M F Bob Juge 1:1/102 BDOC_260.ZIP BinkleyTerm 2.60 M F Bob Juge 1:1/102 BW32_260.ZIP CFRoute 0.92 O G C. Fernandez Sanz 2:341/70 CFR GoldED 2.50 O S Len Morgan 1:203/730 GEO GoldED Docs 2.50 O S Len Morgan 1:203/730 GEM Maximus 3.01 B P Tech 1:249/106 MAXN Msged/NT 4.10 O G Andrew Clarke 3:635/728 MSGED41W.ZIP PlatinumXpress 2.00 M C Gary Petersen 1:290/111 PXW-INFO T-Mail 2.599I M S Ron Dwight 2:220/22 TMAILNT WinFOSSIL/95 1.12 r4 F S Bryan Woodruff 1:343/294 WNFOSSIL.ZIP WinFOSSIL/NT 1.0 beta F S Bryan Woodruff 1:343/294 NTFOSSIL.ZIP Unix: Program Name Version F C Contact Name Node Magic Name ---------------------------------------------------------------------- ifmail 2.10 M G Eugene Crosser 2:293/2219 IFMAIL ifmail-tx ...tx8.2 M G Pablo Saratxaga 2:293/2219 IFMAILTX ifmail-tx.rpm ...tx8.2 M G Pablo Saratxaga 2:293/2219 IFMAILTX.RPM Msged 4.00 O G Paul Edwards 3:711/934 MSGED Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK Amiga: Program Name Version F C Contact Name Node Magic Name ---------------------------------------------------------------------- CrashMail 1.23 T X Fredrik Bennison 2:205/324 CRASHMAIL FIDONEWS 14-20 Page 33 19 May 1997 CrashTick 1.1 O F Fredrik Bennison 2:205/324 CRASHTICK DLG Pro BBOS 1.15 B C Holly Sullivan 1:202/720 DLGDEMO GMS 1.1.85 M S Mirko Viviani 2:331/213 GMS Msged 4.00 O G Paul Edwards 3:711/934 MSGED Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK TrapDoor 1.86.b2 M S Maximilian Hantsch 2:310/6 TRAPDOOR TrapDoor 1.86.b2 M S Maximilian Hantsch 2:310/6 TRAPBETA TrapToss 1.50 T S Rene Hexel 2:310/6 TRAPTOSS Atari: Program Name Version F C Contact Name Node Magic Name ---------------------------------------------------------------------- BinkleyTerm/ST 3.18pl2 M F Bill Scull 1:363/112 BINKLEY JetMail 0.99beta22 T S Joerg Spilker 2:2432/1101 JETMAIL Semper 0.80beta M S Jan Kriesten 2:2490/1624 SMP-BETA Function: B-BBS, P-Point, M-Mailer, N-Nodelist, G-Gateway, T-Tosser, C-Compression, F-Fossil, O-Other. Note: Multifunction will be listed by the first match. Cost: P-Free for personal use, F-Freeware, S-Shareware, C-Commercial, X-Crippleware, D-Demoware, G-Free w/ Source Old info from: 01/27/92 --------------------------------------------------------------------- MS-DOS Systems Other Utilities Other Utilities -------------- Name Version Name Version -------------------- -------------------- Network Mailers 2DAPoint 1.50* Netsex 2.00b Name Version 4Dog/4DMatrix 1.18 OFFLINE 1.35 -------------------- ARCAsim 2.31 Oliver 1.0a D'Bridge 1.30 ARCmail 3.00* OSIRIS CBIS 3.02 Dreamer 1.06 Areafix 1.20 PKInsert 7.10 Dutchie 2.90c ConfMail 4.00 PolyXarc 2.1a Milqtoast 1.00 Crossnet 1.5 QM 1.00a PreNM 1.48 DOMAIN 1.42 QSort 4.04 SEAdog 4.60 DEMM 1.06 RAD Plus 2.11 SEAmail 1.01 DGMM 1.06 Raid 1.00 TIMS 1.0(mod8) DOMAIN 1.42 RBBSMail 18.0 EEngine 0.32 ScanToss 1.28 Compression EMM 2.11* ScMail 1.00 Utilities EZPoint 2.1 ScEdit 1.12 Name Version FGroup 1.00 Sirius 1.0x -------------------- FidoPCB 1.0s@ SLMail 2.15C ARC 7.12 FNPGate 2.70 StarLink 1.01 ARJ 2.20 GateWorks 3.06e TagMail 2.41 LHA 2.13 GMail 2.05 TCOMMail 2.2 PAK 2.51 GMD 3.10 Telemail 1.5* PKPak 3.61 GMM 1.21 TGroup 1.13 PKZip 1.10 GROUP 2.23 TIRES 3.11 FIDONEWS 14-20 Page 34 19 May 1997 GUS 1.40 TMail 1.21 NodeList Utilities Harvey's Robot 4.10 TosScan 1.00 Name Version HeadEdit 1.18 UFGATE 1.03 -------------------- HLIST 1.09 VPurge 4.09e EditNL 4.00 ISIS 5.12@ WEdit 2.0@ FDND 1.10 Lola 1.01d WildMail 2.00 MakeNL 2.31 Mosaic 1.00b WMail 2.2 Parselst 1.33 MailBase 4.11a@ WNode 2.1 Prune 1.40 MSG 4.5* XRS 4.99 SysNL 3.14 MsgLnk 1.0c XST 2.3e XlatList 2.90 MsgMstr 2.03a YUPPIE! 2.00 XlaxNode/Diff 2.53 MsgNum 4.16d ZmailH 1.25 MSGTOSS 1.3 ZSX 2.40 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Key to old info: + - Netmail Capable (Doesn't Require Additional Mailer Software) * - Recently Updated Version @ - New Addition -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Please send updates and suggestions to: Peter Popovich, 1:363/264 ----------------------------------------------------------------- FIDONEWS 14-20 Page 35 19 May 1997 ================================================================= FIDONEWS PUBLIC-KEY ================================================================= [this must be copied out to a file starting at column 1 or it won't process under PGP as a valid public-key] -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 Comment: Clear-signing is Electronic Digital Authenticity! mQCNAzINVLcAAAEEAM5dZN6t6j5Yc0kl7qegVFfiBeVoteuhDg4ay8h43u38Q4kO eJ9Mm7J89wXFb9vgouBVb4biIN6bTWCwcXTbGhBe5OIceLvluuxuEKsaIs/UwXNe Ogx5azIPhRfC7MJDe41Z8tMEBuHY/NE88cuxQ8yXWO126IRttavu6L/U5BwRAAUR tCRGaWRvTmV3cyBFZGl0b3IgPDE6MS8yM0BmaWRvbmV0Lm9yZz6JAJUDBRAyGwFS JZMgw7eCKz0BAZl0A/9xrfhpsEOqGiPfjy2qd9dv6tvSVPPVFu+Wy1lGTHYtuTtg FIN3fQ47AM3XzqHxWRWvp/xZYgR6sRICL7UFx94ShYBQc7CyqBBZKA0IvIWqXP/g c4Br+gQJR6CLiQK7TUyjUbqNbs6QAxuNUi4xFQM+O2Gene5/iTjHFmmSDj2C9YkB FQMFEDIOmHDTQ6/52IG1SQEBQ78H/Rz/mleIrtZwFIOhzy3JH4Z6FUTfZuM9nPcs 1ZLjZCPptHvY7wEYJWGr03lPPJ6tj1VBXwTrWJTf/hOLsoi00GKV8t1thjqGDo23 O91/bSQ+Vn0vBQ2vOEJys8ftxdoLJAyI5YLzHVT+RsMTQLIXVuPyrNcKs1vC2ql+ UDHpU1R+9cG9JUEHpGI6z0DPnQ74SKbQH3fiVBpHhYx4BmvcBC4gWQzKMkDWFiq3 8AssIZ7b9lWl3OBgQ4UM1OIDKoJyjRewIdKyl7zboKSt6Qu8LrcsXO3kb81YshOW ZpSS3QDIqfZC4+EElnB15l4RcVwnPHBaQY0FxUr4Vl4UWM36jbuJAJUDBRAyDpgY q+7ov9TkHBEBAQGoA/sFfN07IFQcir456tJfBfB9R5Z6e6UKmexaFhWOsLHqbCq6 3FGXDLeivNn6NTz81QeqLIHglTuM3NP1mu8sw215klAG8G3M1NA2xLw7Eqhspze2 raGvNeEwxl8e+PY9aZwBj4UWU+CmIm6QNiP0MtvR7QYDIKn5mZCDc3CLmr942IkB FQMFEDIOh0O8AhTPqRipPQEB4EYH/1gkDmdHL6lbEkFuQLrylF+weBl0XQ+kv7ER vWXYrvIrkppxtc4VAge6CXXEbOGJnvkFHgyNZzO9Q9O64QsmZvjip+4lhDLeNrdH X9DizS4YKXxkSKr9Yltmn2/AlBCx6jwcDIfkqy/P1tNWcikxZZMd6KryK0Wsres9 Ik12OmVmJjQSxb5bS6Q8aYUbV3qwosGXTqy+BzYh/UYAX/XJIWa5kxFVSPKFSZ+5 toiSzANd9SpHPEogGvQDHJlJ23lmsMx/6uHsR1LTsQ8su8zIk92XyqePJTjlMx2j D7KJWNR7Zzu4QHCXBkga5W8l2FfPk7D3+o7bXTLRuR1yTYGdNoiJAJUCBRAyDhwt SlKLwP4OFW0BAdaMA/9rcWQlSq44K9JuJ7fZUgt9fwxGreTud9fC8DvlbUW79+CA AHLTLLagcEF1OKsWzVBWcA2JEAp+TUTqktRN0oD8vnaw3uNJd1G5KK59hw0WR8x1 v4ivypbSjiq95Y3gBunb7WjpyiFRWDlm0PrKrWHtbWzjnpPIpetln1UuqsSfbokB FQIFEDIOG9C3N61ZQ4Dr/QEBIzMH/1VxxztmBPBszbjZLDO8Svcax9Ng8IcWpcDy WqHCAA2Hoe5VtMD0v6w31ZgVqTPIvCark2Y/aTR1GofiuN9NUqbVV534AgAYLzYk DMT1swsPvqDTpOYgQl6PCGh6A5JGAbWJfKkX9XCUHJAAmiTsEVRNnjOgL+p6qjoh EfIG8CGehghWSRKl5eGeDAtbXupZKNjFI1t2XV+ks0RFQ/RPuTH7pF7pk7WO6Cyg +Dk2ZMgua0HRL1fXvHKb5Xzr3MVgsbAl5gP8ooIiD9MI/x5Irh3oo58VyoEZNBs/ Kz+drGFDPljcS6fdiVCFtYIzMrshY6YsfLi0aB8fwOvFtxgBqli0J0NocmlzdG9w aGVyIEJha2VyIDwxOjE4LzE0QGZpZG9uZXQub3JnPrQoQ2hyaXN0b3BoZXIgQmFr ZXIgPGNiYWtlcjg0QGRpZ2l0YWwubmV0Pg== =61OQ -----END PGP PUBLIC KEY BLOCK----- File-request FNEWSKEY from 1:1/23 [1:18/14] or download it from the Rights On! BBS at 1-904-409-7040 anytime except 0100-0130 ET and Zone 1 ZMH at 1200-9600+ HST/V32B. The FidoNews key is also available on the FidoNews homepage listed in the Masthead information. ----------------------------------------------------------------- FIDONEWS 14-20 Page 36 19 May 1997 ================================================================= FIDONET BY INTERNET ================================================================= This is a list of all FidoNet-related sites reported to the Editor as of this appearance. ============ FidoNet: Homepage http://www.fidonet.org FidoNews http://ddi.digital.net/~cbaker84/fidonews.html HTML FNews http://www.geocities.com/Athens/6894/ WWW sources http://www.scms.rgu.ac.uk/students/cs_yr94/lk/fido.html FTSC page http://www2.blaze.net.au/ftsc.html Echomail http://www.portal.ca/~awalker/index.html WebRing http://ddi.digital.net/~cbaker84/fnetring.html ============ Zone 1: http://www.z1.fidonet.org Region 10: http://www.psnw.com/~net205/region10.html Region 11: http://oeonline.com/~garyg/region11/ Region 13: http://www.smalltalkband.com/st01000.htm Region 14: http://www.netins.net/showcase/fidonet/ Region 15: http://www.smrtsys.com/region15/ [disappeared?] Region 16: http://www.tiac.net/users/satins/region16.htm Region 17: http://www.portal.ca/~awalker/region17.htm REC17: http://www.westsound.com/ptmudge/ Region 18: http://www.citicom.com/fido.html Region 19: http://rhub.hex.net ============ Zone 2: http://www.z2.fidonet.org ZEC2: http://fidoftp.paralex.co.uk/zec.htm [shut down?] Zone 2 Elist: http://www.fidonet.ch/z2_elist/z2_elist.htm Region 20: http://www.fidonet.pp.se (in Swedish) Region 24: http://www.swb.de/personal/flop/gatebau.html (in German) Region 25: http://members.aol.com/Net254/ FIDONEWS 14-20 Page 37 19 May 1997 Region 27: http://telematique.org/ft/r27.htm Region 29: http://www.rtfm.be/fidonet/ (in French) Region 30: http://www.fidonet.ch (in Swiss) Region 34: http://www.pobox.com/cnb/r34.htm (in Spanish) REC34: http://pobox.com/~chr Region 36: http://www.geocities.com/SiliconValley/7207/ Region 41: http://www.fidonet.gr (in Greek and English) Region 48: http://www.fidonet.org.pl ============ Zone 3: http://www.z3.fidonet.org ============ Zone 4: (not yet listed) Region 90: Net 904: http://members.tripod.com/~net904 (in Spanish) ============ Zone 5: (not yet listed) ============ Zone 6: http://www.z6.fidonet.org ============ ----------------------------------------------------------------- FIDONEWS 14-20 Page 38 19 May 1997 ================================================================= FIDONEWS INFORMATION ================================================================= ------- FIDONEWS MASTHEAD AND CONTACT INFORMATION ------- Editor: Christopher Baker Editors Emeritii: Tom Jennings, Thom Henderson, Dale Lovell, Vince Perriello, Tim Pozar, Sylvia Maxwell, Donald Tees "FidoNews Editor" FidoNet 1:1/23 BBS 1-904-409-7040, 300/1200/2400/14400/V.32bis/HST(ds) more addresses: Christopher Baker -- 1:18/14, cbaker84@digital.net cbaker84@aol.com cbaker84@msn.com (Postal Service mailing address) FidoNews Editor P.O. Box 471 Edgewater, FL 32132-0471 U.S.A. voice: 1-904-409-3040 [1400-2100 ET only, please] [1800-0100 UTC/GMT] ------------------------------------------------------ FidoNews is published weekly by and for the members of the FIDONET INTERNATIONAL AMATEUR ELECTRONIC MAIL system. It is a compilation of individual articles contributed by their authors or their authorized agents. The contribution of articles to this compilation does not diminish the rights of the authors. OPINIONS EXPRESSED in these articles ARE THOSE OF THE AUTHORS and not necessarily those of FidoNews. Authors retain copyright on individual works; otherwise FidoNews is Copyright 1997 Christopher Baker. All rights reserved. Duplication and/or distribution permitted for noncommercial purposes only. For use in other circumstances, please contact the original authors, or the Editor. =*=*=*=*=*=*=*=*= OBTAINING COPIES: The most recent issue of FidoNews in electronic form may be obtained from the FidoNews Editor via manual download or file-request, or from various sites in the FidoNet and Internet. PRINTED COPIES may be obtained by sending SASE to the above postal address. File-request FIDONEWS for the current Issue. File-request FNEWS for the current month in one archive. Or file-request specific back Issue filenames in distribution format [FNEWSEnn.ZIP] for a FIDONEWS 14-20 Page 39 19 May 1997 particular Issue. Monthly Volumes are available as FNWSmmmy.ZIP where mmm = three letter month [JAN - DEC] and y = last digit of the current year [7], i.e., FNWSFEB7.ZIP for all the Issues from Feb 97. Annual volumes are available as FNEWSn.ZIP where n = the Volume number 1 - 14 for 1984 - 1997, respectively. Annual Volume archives range in size from 48K to 1.4M. INTERNET USERS: FidoNews is available via: http://www.fidonet.org/fidonews.htm ftp://ftp.fidonet.org/pub/fidonet/fidonews/ ftp://ftp.aminet.org/pub/aminet/comm/fido/ *=*=* You may obtain an email subscription to FidoNews by sending email to: jbarchuk@worldnet.att.net with a Subject line of: subscribe fnews-edist and no message in the message body. To remove your name from the email distribution use a Subject line of: unsubscribe fnews-edist with no message to the same address above. *=*=* You can read the current FidoNews Issue in HTML format at: http://www.geocities.com/Athens/6894/ STAR SOURCE for ALL Past Issues via FTP and file-request - Available for FReq from 1:396/1 or by anonymous FTP from: ftp://ftp.sstar.com/fidonet/fnews/ Each yearly archive also contains a listing of the Table-of-Contents for that year's issues. The total set is currently about 11 Megs. =*=*=*= The current week's FidoNews and the FidoNews public-key are now also available almost immediately after publication on the Editor's new homepage on the World Wide Web at: http://ddi.digital.net/~cbaker84/fidonews.html There are also links there to jim barchuk's HTML FidoNews source and to John Souvestre's FTP site for the archives. There is also an email link for sending in an article as message text. Drop on over. =*=*=*=*=*=*=*=*= A PGP generated public-key is available for the FidoNews Editor from FIDONEWS 14-20 Page 40 19 May 1997 1:1/23 [1:18/14] by file-request for FNEWSKEY or by download from Rights On! BBS at 1-904-409-7040 as FIDONEWS.ASC in File Area 18. It is also posted twice a month into the PKEY_DROP Echo available on the Zone 1 Echomail Backbone. *=*=*=*=* SUBMISSIONS: You are encouraged to submit articles for publication in FidoNews. Article submission requirements are contained in the file ARTSPEC.DOC, available from the FidoNews Editor, or file-requestable from 1:1/23 [1:18/14] as file "ARTSPEC.DOC". ALL Zone Coordinators also have copies of ARTSPEC.DOC. Please read it. "Fido", "FidoNet" and the dog-with-diskette are U.S. registered trademarks of Tom Jennings, P.O. Box 410923, San Francisco, CA 94141, and are used with permission. "Disagreement is actually necessary, or we'd all have to get in fights or something to amuse ourselves and create the requisite chaos." -Tom Jennings -30- -----------------------------------------------------------------