F I D O N E W S -- | Vol. 8 No. 34 (26 August 1991) The newsletter of the | FidoNet BBS community | Published by: _ | / \ | "FidoNews" BBS /|oo \ | (415)-863-2739 (_| /_) | FidoNet 1:1/1 _`@/_ \ _ | Internet: | | \ \\ | fidonews@fidonews.fidonet.org | (*) | \ )) | |__U__| / \// | Editors: _//|| _\ / | Tom Jennings (_/(_|(____/ | Tim Pozar (jm) | ----------------------------+--------------------------------------- Published weekly by and for the Members of the FidoNet international amateur network. Copyright 1991, Fido Software. All rights reserved. Duplication and/or distribution permitted for noncommercial purposes only. For use in other circumstances, please contact FidoNews. Paper price: . . . . . . . . . . . . . . . . . . . . . . . $5.00US Electronic Price: . . . . . . . . . . . . . . . . . . . . . free! For more information about FidoNews refer to the end of this file. -------------------------------------------------------------------- Table of Contents 1. EDITORIAL ..................................................... 1 Editorial: Huh?! .............................................. 1 2. FIDONET NEWS .................................................. 2 FidoNet <-> uucp Approved Gateways -- Dated 8-15-91 ........... 2 3. ARTICLES ...................................................... 5 Region 16 Mourns .............................................. 5 The Fort Worth Revision ....................................... 5 by Frederick Lo, .............................................. 14 A Correction Concerning the Suggested Change in Nodelist Fla .. 15 4. RANTS AND FLAMES .............................................. 17 5. CLASSIFIEDS ................................................... 18 6. NOTICES ....................................................... 19 The PRIME Network ............................................. 19 The Interrupt Stack ........................................... 19 7. LATEST VERSIONS ............................................... 21 FidoNews 8-34 Page 1 26 Aug 1991 ====================================================================== EDITORIAL ====================================================================== It is surprisingly quiet this week. Absolutely no reports came in on last week's FidoCon '91! I have not had time to write anytthing at all. I will say, it was a great time. Hardly any flames at all. I'll try to elaborate on it for next week's issue. I assume everyone else was swamped and a bit tired after three days of non-stop talking and drinking bad coffee. It seemed to me the biggest influence, content-wise, was Mitch Kapor and John Barlow of the Electronic Frontier Foundation, explaining the goings on in the electronic communication world outside FidoNet. I think it was an eye-opener for a lot of sysops, which is good. Response was quite positive. Well, it's nearly midnight Sunday, and this has gotta ship out now, so until next week... ---------------------------------------------------------------------- FidoNews 8-34 Page 2 26 Aug 1991 ====================================================================== FIDONET NEWS ====================================================================== ################################################################ FidoNetNews -- a weekly section devoted to technical and factual issues within the FidoNet -- FidoNet Technical Standards Committee reports, *C reports, information on FidoNet standards documents and the like. ################################################################ ---------------------------------------------------------------------- FidoNet <-> uucp Approved Gateways -- Dated 8-15-91 (Authorized to use Guucp in Fidonet nodelist) Corrections to: Hostmaster (David Dodell) Fidonet = 1:114/15 Internet = hostmaster@fidonet.fidonet.org SiteName Node Gateway for Net afitamy 1:110/300 [ 110 ] arma 1:139/670 [ none ] blkcat 1:109/401 [ 109, 261, 265, 276 ] bmug 1:161/445 [ none ] branch 1:369/11 [ 135, 369, 3609 ] buscard 1:324/121 [ 324 ] busker 1:105/14 [ 17, 40, 105, 345 ] business 1:363/42 [ 363 ] casino 2:515/800 [ 2:220, 2:221, 2:222, 2:227, 2:490 ] camphq 1:143/42 [ none ] catpe 5:7104/2 [ none ] ccfcc 1:205/42 [ 205 ] cmhgate 1:226/20 [ 226 ] dawggon 1:105/6 [ none ] eddysf 2:285/406 [ none ] egsgate 1:250/98 [ 250 ] ehsnet 1:233/13 [ 233 ] eilc 1:3610/60 [ none ] emdisle 1:300/14 [ 300 ] fidogate 1:125/777 [ 125 ] fidosw 1:125/111 [ none ] fquest 1:19/23 [ none ] gisatl 1:133/411 [ 133 ] gnfido 2:254/70 [ 2:254, 2:25] halluc 1:109/345 [ none ] hlthnt 1:381/68 [ 305, 381] hndymn 1:114/30 [ none ] hnews 1:141/420 [ none ] idic 1:104/424 [ 104 ] FidoNews 8-34 Page 3 26 Aug 1991 ijcr 1:130/49 [ none ] isengard 1:234/15 [ 234 ] isishq 1:163/162 [ none ] jadpc2 1:202/723 [ 202 ] kcufgat 1:280/500 [ 280 ] kennel 1:143/8 [ none ] kisbbs 1:3624/11 [ 360, 3624 ] klbbs 1:141/370 [ 141 ] lansend 1:143/3 [ 143 ] linn 2:320/101 [ 2:320 ] lri 1:105/126 [ none ] malymi 1:102/463 [ none ] masnet 1:259/404 [ 259 ] mcastl 1:107/528 [ none ] mcws 1:102/851 [ 102, 103, 206, 207 ] mdf 1:382/39 [ 382 ] memco 1:139/610 [ 139 ] neis 1:267/201 [ 267 ] newport 1:107/820 [ 107, 278 ] nss 1:129/104 [ none ] nwark 1:391/1060 [ 391 ] oamicus 1:367/9 [ 367 ] ofa123 1:103/302 [ none ] ohiont 1:157/512 [ 157 ] orioneb 1:141/705 [ none ] pacifier 1:105/101 [ none ] palind 1:124/3107 [ none ] paranet 1:104/422 [ none ] psycho 1:3610/75 [ 374, 3610 ] puddle 1:105/42 [ 2,3,4,5,17,134,138,153,340,342,343,344, 346,347,348,349,350,351 ] quadrant 1:105/209 [ none ] redstar 1:115/639 [ none ] resq 1:269/133 [ none ] rochgte 1:260/222 [ 260 ] royaljok 1:120/183 [ 11,108,115,120,121,154,159,201,227,228, 230,231,232,236,237,238,239,2200,2201, 2210,2220,2222,2230,2240,2250,2260,2270 2280,2290 ] rrgate 1:101/660 [ none ] shire 1:114/55 [ none ] slinky 1:147/63 [ 147 ] spuzz 1:143/642 [ none ] srrt 1:322/337 [ none ] sscreen 1:141/9 [ none ] stjhmc 1:114/15 [ 1, 114, default gateway for all un-gated nets ] sunbrk 1:343/15 [ none ] tdkt 1:282/31 [ none ] terrabit 1:282/341 [ 282 ] therip 1:228/24 [ none ] tinylk 1:170/500 [ 170 ] umagic 1:373/12 [ 373 ] urchin 1:106/88 [ none ] w8grt 1:234/1 [ none ] FidoNews 8-34 Page 4 26 Aug 1991 weyr 1:140/22 [ 140 ] yantar 1:129/128 [ none ] zorro9 1:16/390 [ 16, 101, 322 ] -- ------------------------------------------------------------------------- St. Joseph's Hospital and Medical Center, Phoenix, Arizona uucp: {gatech, ames, rutgers}!ncar!asuvax!stjhmc!ddodell Bitnet: ATW1H @ ASUACAD FidoNet=> 1:114/15 Internet: ddodell@stjhmc.fidonet.org FAX: +1 (602) 451-1165 ---------------------------------------------------------------------- FidoNews 8-34 Page 5 26 Aug 1991 ====================================================================== ARTICLES ====================================================================== Cheryl Buzzell 322/200 Region 16 Mourns Well I hope this article does not hit the streets. I hope someone who knew Steve a little better than I writes in but if not at least this much has been said. On Tuesday August 13th region 16 lost a loved and valued member of it's community. Steve Ahola our beloved REC (and just about everything else) coordinator died unexpectedly. Little did we know it when our echomail was interrupted that a few days later we would find that our lives will never again be the same. The fidonet node numbers of 322/1 and 322/210 would no longer take us to Steve. That yes our echomail will return but Steve will not. I am sure that anyone and everyone who knew Steve even the sloghtest would agree with me when I say his death will leave a big empty spot in all our lives. The good times and the bad will be foever in our memories. I hope that this horrible event will instill in each and every one of you the fact that we are mortal. That our time on this planet is number and that we should all take the time to smell the roses. To appreciate those who love us and show our love to others. In parting. I wish each and every one of you reading this article to take a moment and say a prayer/wish or good though to Steve as he journeys onto the next phase of existence and to his family who need all the good wishes etc that they can get. Cheryl Buzzell Fidonet 1:322/200 Ournet 65:713/0 TC-Trader 508-840-8017 ---------------------------------------------------------------------- Aaron Goldblatt 1:130/32.1 FidoNet 20:491/110.0 MailNet 50:5817/9999 (pending) EchoNet The Fort Worth Format Nodelist - A Proposal v2.0 FidoNews 8-34 Page 6 26 Aug 1991 A number of discussions have taken place on the state of the nodelist, both within and outside FidoNet. In FidoNews 820 I outlined a proposal for a new, smaller nodelist format. In FidoNews 826, after a lot of thought and discussion with others, I published a short revision (it was short because I was going on vacation two days after it came out, and I felt pressed to get it out before I left for six weeks). This is the third submission of this format. It still isn't a full FSC-type document, but in due course I expect it will be. I've elected to do another full-length draft and call it Fort Worth Version 2.0. I wrote this article using NODELIST.228, with a length of 1,019,934 bytes. I don't use any nodelist pre-processors to delete zones for me because that makes applying the NODEDIFF much harder, in my opinion. However, I do compile a full Zone 1 nodelist and can add the rest in under 10 minutes if I want to. Several ideas have been proposed, such as changing the format, splitting the nodelist into sections, etc. I find myself supporting a combination of both - change the format and then segment. I am still in favor of a pure ASCII nodelist. A couple weeks ago in FidoNews the gentleman from 3:680/828 (I'm sorry - I don't remember the name) asked why there was no software for any of the current proposals, the Fort Worth nodelist format included. I can not answer for others, but with respect to the Fort Worth format, the primary reason there is no software is that the specifications aren't complete. You can not write a software package if you don't know what you want it to do. You must first define the problem to be solved, and the method used to solve it, and finally write the implementation of the solution. The problem is already well defined, but not the method to solve. On I ramble. Anyway, here it is. Comments are, of course, welcome sent any way you want to send them, letter-bombs excepted. :-) Again, let's start at the top. - - - - - - - - - - - - - - - - - - - o Each line in the nodelist will still be CR/LF terminated. o CRC calculation and notation on the first line of the nodelist will remain the same. o Each comment flag now in use will remain the same, with FidoNews 8-34 Page 7 26 Aug 1991 current comment formats remaining, as well. o The nodelist must still be a pure ASCII file, with characters between 32 and 127 (space to tilde) allowed. o The nodelist will be organized along the same lines we see today - that is, Zone/Region/Net/Hub/Node organization. o Each Zone number must still be unique to a nodelist. Each Region and Net number must be unique to a Zone, and each node number must be unique to a Net. o Each field in the nodelist is still divided by a comma (,) character, ASCII 44, hex 0x2C. Spaces (ASCII 32, hex 0x20) are not allowed except in comments. Underscore (_) characters (ASCII 95, hex 0x5F) represent spaces in nodelist entries. o Current maximum integers for Zone, Region, Net, and node numbers will apply. * * * * Normal Nodelist Entries * * * * * * For a normal public node a listing is as follows: num,sys_name,sysop,phone,bps,mtype,hrs,Uxflag,mailcap The NUM field is the individual node address, unique to a net, assigned according to current policy. SYS_NAME is the system name, such as "Shadowdale_BBS". Maximum field length is 20 characters. SYSOP is the sysop name, such as "Mike_Wilson". Maximum field length is 20 characters. PHONE is the phone number of a BBS, without extra dialing information such as an area code. The number placed in this field is the same one you would dial if you were calling from right next door. For example, "732-6157" is a valid value, while "1-817-732-6157" is not. Because phone systems vary there is no field maximum. In order to faciliate nets without a standard dialing scheme (such as those which cover more than one area code), a dash "-" may be added in front of the phone number, like so: -1-817-... This will indicate that the DIAL_TRANS field (defined below) should not be added to the front of the phone number. FidoNews 8-34 Page 8 26 Aug 1991 BPS is a one character representation of the maximum transmission rate of the node. Valid values are: 3 - 300 bps 9 - 9600 bps 1 - 1200 bps 4 - 14,400 bps 2 - 2400 bps 5 - 19,200 bps Other values may be added as technology becomes available. MTYPE is a one or two character representation of modem type. Valid values include: M - MNP error correction H - USRobotics HST V3 - CCITT V.32 P - Telebit Packet Ensamble Protocol H9 - Hayes V-Series 3B - CCITT V.32bis V4 - CCITT V.42 4B - CCITT V.42bis Redundant listings should be avoided. For example, because HST implies MNP error correction no MNP flag should be present. More than one flag may be present if the modem type warrants it. For example, a USRobotics Dual Standard with V.42bis could be listed as: ...,9,H,V3,4B,... HRS is a two or nine character representation of the hours during which a node accepts mail. If a node runs 24 hours this flag should be "CM". A nine character representation should be used for nodes that don't run the entire day but are up for part. The format is: HHMM-hhmm "HH" is the 24-hour representation of the hour in which a node goes online to accept mail, translated to Greenwhich Mean Time (GMT). Valid values are 00 - 23 (midnight to 11:xx pm). "MM" is the two digit representation of the part of the hour in which the node goes online. Valid values are 00 - 59. "hh" is the 24-hour representation of the hour in which a node goes offline, and ceases to accept mail, translated FidoNews 8-34 Page 9 26 Aug 1991 to GMT. Valid values are still 00 - 23. "mm" is the two digit representation of the part of the hour in which the node goes offline and ceases to accept mail. Valid values are still 00 - 59. Thus, a node with this flag, listed as 0600-0900 is able to accept mail for three hours, from 06:00 to 09:00 GMT. A node listed as 1330-1800 is able to accept mail from 1:30 pm to 6:00 pm GMT. If the flag is "CM" the node is able to accept mail 24 hours a day. Absence of this flag indicates that a node only accepts mail during ZMH. ZMH shuld not be indicated by this flag because all nodes are required to accept mail during ZMH. Only mail times different than ZMH should be noted in this field. This field is optional and may be left out. UXFLAG is an informational flag used for special comments. The International Coordinator is the ultimate authority over what goes into the nodelist, and it is up to that person to decide upon valid values for this flag, as well as their meaning. Suggested values include: UNEC - Net Echomail Coordinator UREC - Region Echomail Coordinator UZEC - Zone Echomail Coordinator USDS - SDS Distribution point USDC - SDS Distribution Coordinator This field is optional and may be omitted. MAILCAP is the "mailer capability" flag. In the current nodelist format an X preceeds a second letter. In the Fort Worth format, the mailer capability flag is reduced to one letter, dropping the X. Second letters remain the same (A for Bark/WaZoo update/requests, X for WaZoo update/requests, etc.). If a node does not use a front-end mailer or software with mailer capability (such as Fido or Opus) this flag is ommitted. * * * * Pvt and Hub System Notation * * * * * Two optional flags may be used at the beginning of a nodelist entry. These flags, P and H, are abbreviations of the Pvt and Hub flags, and retain these meanings. FidoNews 8-34 Page 10 26 Aug 1991 If one of these flags is used it placed before the node number, with a comma (,) ending the field, like this: H,num,sys_name,sysop,phone,bps,mtype,Uxflag,mailcap If the P flag is used the PHONE, BPS, and MTYPE fields are left blank, and the MAILCAP flag is ommitted, like this: P,sys_name,sysop,,,Uxflag * * * * * * Host System Notation * * * * * For net coordinators a different set of fields is used, preceeded by the N flag (for Net) as follows: N,net_num,net_name,area_admin,sysop,phone,dial_trans, bps,mtype,hrs,Uxflag,mailcap Field names duplicated from the previous section remain the same except as noted below. NET_NUM is the number of the network, assigned according to current policy. A valid value of this is "130". NET_NAME is the name of the network, created according to policy. A valid value of this might be "FTW_Gateway". Maximum field length is 20 characters. AREA_ADMIN is the name of the region administered. A value for this field might be "Ft_Worth_Metro". Maximum field length is 20 characters. SYSOP is the person holding the NC position. "Tom_Dobbins" is a valid value. DIAL_TRANS is a portion of a phone number added to the beginning of the PHONE field on a call outside your local net. An example of this would be "1-817-" for all nodes in Net 130. If you must dial something special to call long distance (for example, from New York City to Fort Worth) put that here. This does not include 011- for international calls, nor does it include special sequences to get an "outside line" on office phones, or strange digit codes not used by a normal phone network. * * * * Region and Zone System Notation * * * * Each Region and Zone coordinator listing will be be preceeded by either keyword "R" or "Z", as appropriate. The formats for Zone and Region Coordinators are as follows: FidoNews 8-34 Page 11 26 Aug 1991 R,reg_num,area_admin,sysop,fphone,bps,mtype,hrs,Uxflag Z,zon_num,area_admin,sysop,fphone,bps,mtype,hrs,Uxflag Unless defined below, each flag retains the meanings given in the previous sections. "R" and "Z" are unchanging flags, in the same manner as P, N, and H are unchanging flags. REG_NUM and ZONE_NUM are Region and Zone numbers, respectively. Each Region number must be unique to a Zone, and each Zone number must be unique to a nodelist. AREA_ADMIN means the area contained within that section of the nodelist, such as "North_America" (for Zone 1) or "TX.AR.OK.LA" (for Region 19). FPHONE is the full phone number of the system, including area code. A valid value would be "1-817-732-6157" while "732-6157" would not. * * * * * * Down Nodes * * * * * * * The D flag preceeds a down node's number, in the following formats. For a standard node (a net member): D,num,sys_name,sysop,phone,bps,mtype,hrs,Uxflag,mailcap For a Zone Service Node (1:1/x) or Regional Independant Node (1:19/x): D,num,sys_name,sysop,fphone,bps,mtype,hrs,Uxflag,mailcap * * * Zone Service and Regional Independants * * * For Zone service nodes (1:1/x, 2:2/x, etc.) and regional independant nodes (1:19/x, 2:23/x, etc.) one last format is used. num,sys_name,sysop,fphone,bps,mtype,hrs,Uxflag The only difference between this flag and a normal (networked) node is that there is a full phone number, not a partial one. * * * * * * NODEDIFFs * * * * * * * The current system of NODEDIFF production using the A, C, and D commands will not change. FidoNews 8-34 Page 12 26 Aug 1991 * * * * * * Explanation * * * * * * * Here's the part you've been waiting for, but the one that I dread. Here are my reasons for the suggested changes. There's no preceeding comma before a node number because there's no need for one. It's just an extra byte to transmist and keep around. If it doesn't need to be there, zap it. If it's not a keyword it's a node number, and there's no need to create a field to tell it that. Fields are limited to 20 characters because that encourages sysops and coordinators comments succinct. It discourages extra information that doesn't need to be there. For example, "The_Shadowdale_BBS" and "Shadowdale" in the SYS_NAME field convey exactly the same information but one is shorter, thus taking less disk space. Sysop names are included in the nodelist to make sure that someone is responsable for what goes on at a node, so that it's not just an address with nobody on the other end. Some may argue that if you don't know who the sysop is you don't need to be sending mail there (and thus you don't need to list the name in the nodelist), but it must be clear who is responsable for the actions of a node. Including the name seems the reasonable way to go. Since it's limited to 20 bytes per entry anyway, that's not too hefty. Drop the first name if necessary. Phone numbers have been shortened because it just carries redundant information. There are about 60 nodes in Net 130 and all carry 1-817- before their real phone numbers, which, on my system, gets deleted anyway. In net 124 there are over 100 nodes, and most had 1-214- in front of the number. Assuming 125 nodes that's 750 bytes of information that can be cut to 6 bytes. Do that for every net in FidoNet and we might just have a good size cut. BPS is cut to one characters because the trailing zeros just aren't needed, and one character can convey the required information. Every listing has those two zeros, so it can be universally understood that they're there. Zap them and, at 10,000 nodes that's 20k saved. Less disk space, less transmission time, less money. Mtype is included because some mailers allow the capability to modify how a calling modem will react to the called modem's carrier. For example, if you have a Dual Standard and you call another Dual Standard you can choose if you want an HST or V.32 connection. Also, some modems require special commands be sent to be able to connect with modems that offer different communications protocols, and identifying the type of modem present is a good way to facilitate this. FidoNews 8-34 Page 13 26 Aug 1991 Hours online allow someone to send mail outside of ZMH to a node that isn't CM. If the node is online 24 hours CM is used to indicate this. Some say that since most nodes are CM, only systems which do not support CM should be flagged, instead of using a CM flag. I believe that, because every FidoNet member is required to operate during ZMH only that any capabilities outside of this hour require a flag.` Uxflags allow the conveyance of additional information to sysops and (maybe) mailers, such as who is the local NEC or SDS distributor. Elections have been conducted using this flag and it could be helpful. Dropping the location field in the current nodelist eliminates much of the redundant information, as does dropping area codes. Does anybody really care what city 1:130/28 is in, so long as the mail gets through? If it's that important you can send a netmail message rather than have it sit on everybody's system. Some have suggested dropping private (Pvt) systems from the nodelist. However, because they currently exist I feel obligated to support their inclusion. Removal of private systems is a matter left to policy, not to technical specifications. Ditto for Down nodes. I have retained the current net/node system (Z:NNN/nnn.pt) because all current mailer software supports some version of it. Thus, mailers won't have to be completely rewritten to use a new addressing scheme. Besides, would you remember that Shadowdale, sysop Mike Wilson, is node 1-817-732-6157 if node numbers were phone numbers? Everything would have to be rewritten. With this change relatively minor modifications would have to be made to nodelist compilers and mailers. Most of the changes suggested here are designed to save space. To see if it works, let's use a large net in Zone 1 - Net 1:124, Dallas, Texas. I chose it because it's large, has several private nodes, some which are down, and a hub-based mail distribution system. Because Net 124 is SO large, however, I chose only to use the 1000 and 2000 hub series, as well as the first two lines from the 3000 nodes. All line formats except Zone and Region are represented in these three sections. N,124,The_Hat,Dallas_TX,Robert_Eskridge,416-2162,,1-214,9,H,CM,X H,1000,Friendly_Hub,RC_Gorman,289-2668,9,H,3b,4b,CM,A 1001,Carrier_Pigeon,James_Marple,530-5526,9,H,CM,X 1002,Texas_Trails,Randy_Gorman,289-2668,9,H,3b,4b,CM,A 1005,Polar_Den,Darrel_Exline,361-8992,2,CM,A 1006,Castle,Jack_Schofield,988-1053,9,H,4b,CM,X 1007,Kimball_Video_Tech,Stan_Carman,869-2857,2,CM,X 1009,Mac_Exchange,Tom_Fitzsimmons,394-9324,9,H,3b,4b,CM,W 1010,User-To-User,William_Pendergast,394-1929,9,H,3b,4b,CM,A 1011,Camelot,Jim_Stanford,339-8283,2400,CM,XX 1012,IEEE_DeVRY_Branch,Dave_Johnson,257-0125,9,H,4b,CM,C 1013,UTD_Student_Connect,Craig_Olson,437-3247,9,H,3b,4b,CM,XA 1014,The_Critical_Mass,Glenn_Heights_TX,Tim_Herum,617-0617,9,CM,A FidoNews 8-34 Page 14 26 Aug 1991 1015,Hot_Tub_Club,Brian_Housley,960-2464,2,CM,X 1016,Psychlo_Empire,Mark_Corona,251-1175,9,H,CM,A 1017,Omnia_Vincet_Amor,Pamela_Mikos,285-4393,2,CM,X D,1107,Mainframe_Exchange,Doug_Light,221-8931,9,H,CM,A 1113,Nibbles_&_Bytes,231-3841,9,H,CM,A 1213,DFW_Freq_Coord,Gerry_Dalton,647-0670,2,CM,R 1701,NCC-1701,Bill_Bailey,771-3226,9,H,3b,4b,CM,A Hub,2000,DFW_124,Tom_Haycraft,437-2906,9,H,4b,CM,C 2101,Software_Mechanics,Lewis_Sheriff,422-0632,9,H,CM,R 2103,Magna_Carta_Technica,Andrew_Chalk,226-8088,2,CM,R 2105,Amiga_LANd,Eric_Fisher,222-2510,9,H,CM,R 2107,Firing_Line,Tom_Haycraft,437-2906,9,H,CM,C 2108,County_Line,Don_Click,475-3610,9,H,CM,A 2109,Hobby_Hut,Ed_Underwood,462-9124,9,CM,B 2110,INOVAtronics,Martin_Murray,357-8511,2,CM,R 2112,System_Control,Bob_Wolverton,709-4056,2,CM,X 2121,Psychology_Forum,Gary_Lefkof,368-5474,2,CM,X 2122,ACCESS,Trey_Reeves,315-0420,9,H,V3b,4b,CM,A 2124,DeadHead's,John_Gresham,988-0124,9,H,3b,4b,CM,A 2203,Biz_Link,Jerry_Mawhinney,227-8040,2,CM,A 2204,Writers_Block,Thomas_Drone,259-3700,2,CM,A 2206,The_Interocitor,Steve_Rainwater,258-1832,9,3b,4b,CM,A 2211,Amiga_Scope,Mark_McBreen,288-1537,9,H,CM,R 2213,The_Chess_Board,Ken_Givens,641-1136,9,H,USDS,UDDS,UWIN,U... 2221,Night_Lights,Robert_Williams,298-7909,2,CM,A 2222,J._R.'s_Palace,John_Reynolds,299-5425,9,H,CM,A H,3000,DFW_108,Baxter_Banowsky,340-6393,9,H,CM,X P,3006,Firing_Line,Steve_Oglesby All but one of these nodes fits within the FidoNews specs, less than 65 characters per line. Only 124/2113 had to be cut short. In the nodelist ALL lines exceeded 65 characters. Some went past 80 characters. There is a very signifigant space savings. Please consider this proposal. If you'd like to suggest changes you may netmail me at any address listed at the beginning of this article. Of not, well, okay. :-) It's not final, I'm not done, it's not an FSC yet. Take a look and see what you think. Aaron ---------------------------------------------------------------------- 6:700/159. A proposal of new nodelist formating ------------------------------------ I propose to use following method to save the volume of nodelist. The baud rate and flags are now represented by using a 32-bit flag type and written on the nodelist by hexdecimal. FidoNews 8-34 Page 15 26 Aug 1991 bit 1 1200 bit 17 V34 bit 2 2400 bit 18 V42 bit 3 4800 bit 19 V42b bit 4 9600 bit 20 H96 bit 5 14400 bit 21 HST bit 6 19200 bit 22 MAX bit 7 38400 bit 23 PEP bit 8 MN bit 24 CSP bit 9 CM bit 25 MNP bit 10 MO bit 26 XA bit 11 V21 bit 27 XB bit 12 V22 bit 28 XC bit 13 V29 bit 29 XP bit 14 V32 bit 30 XW bit 15 V32b bit 31 [reserved] bit 16 V33 bit 32 [reserved] For example, a BBS with using a V32 modem with MNP V42B accept Crash Mail should be: ,1,Example_BBS,Hong_Kong,Some_One,852-123-4567,04108108 (^ the 32bit number in HEX) Hope this can help! ---------------------------------------------------------------------- by Danny Mingle @ 1:116/9 A Correction Concerning the Suggested Change in Nodelist Flags I overlooked something in my previous article: all flags after the baud_rate field in the nodelist are lumped together in one field called the "Flags" field. I mistakenly thought there were separate fields for special operating conditions, modem capabilitites, etc. The changes proposed in last week's article about converting from the current multi-character flags to one-character flags can still be implemented because by using the numbers "0" through "9" and the letters "A" through "Z", you will get 36 possible flags. So, to recap my thoughts on reducing the size of the nodelist: 1) Change all baud rates to single-character codes: "300" would become "0" "1200" would become "1" FidoNews 8-34 Page 16 26 Aug 1991 "2400" would become "2" "4800" would become "3" "9600" would become "4" 2) Change all flags to single-character codes. For example: "CM" would become "0" "MO" would become "1" "LO" would become "2" "V21" would become "3" . . . "V42" would become "9" "MNP" would become "A" "H96" would become "B" etc. etc. I do apologize for any confusion last week's article may have caused. I hope this helps clear things up somewhat. ---------------------------------------------------------------------- FidoNews 8-34 Page 17 26 Aug 1991 ====================================================================== RANTS AND FLAMES ====================================================================== _(*#$_(*@#(* (*^$+)#(%&+| #$)%(&*#_$ @_#( @$ ^@#+)(#&%$*+)$%&*+$*%&#@(@#_|)*%|)#%&)#*%&+(@#&*_+(@#*^&@### *&#_($*&#$_(*#&$_(#*$&$ _(#$*#$+)#($&*+#)$ &#+$*&# ()*&#$_(&^#$_(#*$_#($^&#_$(^&#_$(&^#$_(&#^ damn right _(#^&$_(#^& $*&#$_+(* #)$&(%($%+)($%*+$)%($* it's ugly _#&%^# & #($_*#$_ FidoNet (*$&%_@#_(*&@#_(@*#&_ @#_(*&@#_(* )*&#$ Flames *^$+)#(% (not for the timid) @_#( (*#$_(*^@#+) and #_|)*% &+(@#&*_+(@#*^&@### (#$*&#_($*&#$_(*#&$_(#* Rants *&+#$*&#+$*&# )*&#$_(a regular feature)^&#_$(&^#$_ $^&#$_(#^ (*^#$_*#^&$)*#&$^%)#*$&^_#($*^&#_($ Section #&%^_ _(*#&$_(#* #($*& #$* _(*&@#_(@*# *&@#_(*& )&*+_)*&+)*&+))&*(*& (*&_(*&_(*& ---------------------------------------------------------------------- FidoNews 8-34 Page 18 26 Aug 1991 ====================================================================== CLASSIFIEDS ====================================================================== ADVERTISEMENT POLICY: Submissions must be 20 lines or less each, maximum two ads per advertiser, 70 characters per line maximum. No control codes except CR and LF. (Refer to contact info at the end of this newsletter for details.) Please notify us if you have any trouble with an advertiser. FidoNews does not endorse any products or services advertised here. ---------------------------------------------------------------------- FidoNews 8-34 Page 19 26 Aug 1991 ====================================================================== NOTICES ====================================================================== Steve Winter FidoNet 1:151/208 209 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + __________ __________ ___ ________ + + | | | | | |\ /| | + + | | | | | | \ / | | + + |________| |________| | | \ / | |______ + + | | \ | | \/ | | + + | | \ | | | | + + | | \ | | | | + + | | \ _|_ | | |_______ + + + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + PreRapture(tm) International Message Exchange + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Both Religious (Christian) and non-religious conferences. Strict policy against profanity, lewdness, etc.. Supporting FidoNet, PCRelay, and QWK message networking. + Intense Bible Debate + False Preachers Exposed + + Popular Cults Unmasked in the light of the Bible + 919-286-3962 + 919-286-3606 + 919-286-3266 Using USRobotics Dual Standard Modems HST/V.32bis 14,400bps FidoNet Nodes 1:151/208 209 & 210 ---------------------------------------------------------------------- The Interrupt Stack 8 Sep 1991 7 Oct 1991 Area code 415 fragments. Alameda and Contra Costa Counties will begin using area code 510. This includes Oakland, Concord, Berkeley and Hayward. San Francisco, San Mateo, Marin, parts of Santa Clara County, and the San Francisco Bay Islands will retain area code 415. 1 Nov 1991 Area code 301 will split. Area code 410 will consist of the northeastern part of Maryland, as well as the eastern shore. This will include Baltimore and the surrounding area. Area 301 will include southern and western parts of the state, including the areas around Washington DC. Area 410 phones will answer to calls to area 301 until November, 1992. 1 Feb 1992 Area code 213 fragments. Western, coastal, southern and eastern portions of Los Angeles County will begin using area code 310. This includes Los Angeles International Airport, West Los Angeles, San Pedro and Whittier. Downtown Los Angeles and surrounding communities (such as Hollywood and Montebello) will retain area code 213. FidoNews 8-34 Page 20 26 Aug 1991 1 Dec 1993 Tenth anniversary of Fido Version 1 release. 5 Jun 1997 David Dodell's 40th Birthday If you have something which you would like to see on this calendar, please send a message to FidoNet node 1:1/1. ---------------------------------------------------------------------- FidoNews 8-34 Page 21 26 Aug 1991 ====================================================================== LATEST VERSIONS ====================================================================== Latest Greatest Software Versions Last Update: 08/15/91 MS-DOS Systems -------------- BBS Software Network Mailers Other Utilities Name Version Name Version Name Version -------------------- -------------------- -------------------- DMG 2.93 BinkleyTerm 2.40 2DAPoint 1.10* Fido/FidoNet 12.21+ D'Bridge 1.30 ARCAsim 2.30 Genesis Deluxe 3.1* Dutchie 2.90c ARCmail 2.07 GSBBS 3.02 FrontDoor 2.00 ConfMail 4.00 Kitten 2.16 InterMail 2.01* Crossnet 1.5 Lynx 1.30 PRENM 1.47 DOMAIN 1.42 Maximus 1.02 SEAdog 4.60* EEngine 0.30* Opus 1.71* TIMS 1.0(Mod8) EMM 2.02 PCBoard 14.5a 4Dog/4DMatrix 1.18 Phoenix 1.3 FNPGate 2.70 QuickBBS 2.66 GateWorks 3.06c*@ RBBS 17.3b NodeList Utilities Gmail 2.05 RBBSmail 17.3b Name Version GMD 2.00* RemoteAccess 1.01 -------------------- GROUP 2.16 SLBBS 2.15b* EditNL 4.00 GUS 1.30 Socrates 1.10 MakeNL 2.31 HeadEdit 1.18 SuperBBS 1.10 Parselst 1.30 IMAIL 1.10 TAG 2.5g Prune 1.40 InterPCB 1.31 TBBS 2.1 SysNL 3.14 MSG 4.1 TComm/TCommNet 3.4 XlatList 2.90 MSGED 2.06 Telegard 2.5 XlaxNode/Diff 2.52* MsgMstr 1.21* TPBoard 6.1 MSGTOSS 1.3 TriTel 1.11*@ Oliver 1.0a Wildcat! 2.55 PolyXarc 2.1a* WWIV 4.12 QM 1.0 XBBS 1.17 QSort 4.04 ScanToss 1.28 Sirius 1.0x Compression SLMAIL 1.36 Utilities StarLink 1.01 Name Version TagMail 2.41 -------------------- TCOMMail 2.2 ARC 7.00 Telemail 1.27 ARJ 2.20* TMail 1.21 HYPER 2.50 TPBNetEd 3.2 LHA 2.13* Tosscan 1.00 PAK 2.51 UFGATE 1.03 PKPak 3.61 XRS 4.50* PKZip 1.10 XST 2.3e FidoNews 8-34 Page 22 26 Aug 1991 ZmailH 1.16a* OS/2 Systems ------------ BBS Software Network Mailers Other Utilities Name Version Name Version Name Version -------------------- -------------------- -------------------- Maximus-CBCS 1.02 BinkleyTerm 2.40 ARC2 6.00 ConfMail 4.00 EchoStat 6.0 LH2 0.50 MsgEd 2.06 MsgLink 1.0c MsgNum 4.14 oMMM 1.52 Omail 3.1 Parselst 1.32 PKZip 1.02 PolyXarc 2.1a* QSort 2.1 Raid 1.0 Remapper 1.2 Tick 2.0 VPurge 2.07 Xenix/Unix 386 -------------- BBS Software Network Mailers Other Utilities Name Version Name Version Name Version -------------------- -------------------- -------------------- BinkleyTerm 2.32b ARC 5.21 C-LHARC 1.00 MsgEd 2.06 |Contact: Jon Hogan-uran 3:711/909,| MSGLNK 1.01 |Willy Paine 1:343/12or Eddy van Loo| oMMM 1.42 |2:285/406 | Omail 1.00 Parselst 1.32 Unzip 3.10 Vpurge 4.08 Zoo 2.01 Apple II -------- BBS Software Network Mailers Other Utilities Name Version Name Version Name Version -------------------- -------------------- -------------------- DDBBS + 7.4* Fruity Dog 2.0* deARC2e 2.1 GBBS Pro 2.1 ProSel 8.69* FidoNews 8-34 Page 23 26 Aug 1991 ShrinkIt 3.23 ShrinkIt GS 1.04 Apple CP/M ---------- BBS Software Network Mailers Other Utilities Name Version Name Version Name Version -------------------- -------------------- -------------------- Daisy 2j Daisy Mailer 0.38 Filer 2-D MsgUtil 2.5 Nodecomp 0.37 PackUser 4 UNARC.COM 1.20 Macintosh --------- BBS Software Network Mailers Other Software Name Version Name Version Name Version -------------------- -------------------- -------------------- FBBS 0.91 Copernicus 1.0 ArcMac 1.3 Hermes 1.5 Tabby 2.2 AreaFix 1.6 Mansion 7.15 Compact Pro 1.30 Precision Sys. 0.95b* Eventmeister 1.0 Red Ryder Host 2.1 Export 3.21 TeleFinder Import 3.2 Host 2.12T10 LHARC 0.41 MacArc 0.04 Mantissa 3.21 Point System Mehitable 2.0 Software OriginatorII 2.0 Name Version PreStamp 3.2 -------------------- StuffIt Classic 1.6 Copernicus 1.0 SunDial 3.2 CounterPoint 1.09 TExport 1.92 Timestamp 1.6 TImport 1.92 Tset 1.3 TSort 1.0 UNZIP 1.02c Zenith 1.5 Zip Extract 0.10 Amiga ----- BBS Software Network Mailers Other Software Name Version Name Version Name Version -------------------- -------------------- -------------------- Falcon CBBS 0.45 BinkleyTerm 1.00 AmigArc 0.23 Paragon 2.082+ TrapDoor 1.50 AReceipt 1.5 TransAmiga 1.07 WelMat 0.44 booz 1.01 FidoNews 8-34 Page 24 26 Aug 1991 ChameleonEdit 0.10 ConfMail 1.12 ElectricHerald 1.66 LHARC 1.30 Login 0.18 MessageFilter 1.52 oMMM 1.49b ParseLst 1.64 PkAX 1.00 PolyxAmy 2.02 RMB 1.30 Roof 44.03 RoboWriter 1.02 Rsh 4.06 Skyparse 2.30 Tick 0.75 TrapList 1.12 UNZIP 1.31 Yuck! 1.61 Zippy (Unzip) 1.25 Zoo 2.01 Atari ST/TT ----------- BBS Software Network Mailers Other Utilities Name Version Name Version Name Version -------------------- -------------------- -------------------- FIDOdoor/ST 2.4.0* BinkleyTerm 2.40l BINK2TB 1.00 GS Point 0.61 The BOX 1.20 ComScan 1.02 LED ST 1.00 ConfMail 4.03 MSGED 1.96s EchoFix 1.20 FastPack 1.20 FDrenum 2.4.0* Compression FiFo 2.1n* Utilities Import 1.14 Name Version oMMM 1.40 -------------------- Pack 1.00 ARC 6.02 Parselst 1.30 LHARC 1.32* sTICK/Hatch 5.50 PKZip 1.10 TB2BINK 1.00 STZIP 0.80* Trenum 0.10 Xlist 1.12 Archimedes ---------- BBS Software Network Mailers Other Utilities Name Version Name Version Name Version -------------------- -------------------- -------------------- ARCbbs 1.44 BinkleyTerm 2.03 ARC 1.03 FidoNews 8-34 Page 25 26 Aug 1991 BatchPacker 1.00 Parselst 1.30 !Spark 2.00d Unzip 2.1TH -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Key: + - Netmail Capable (Doesn't Require Additional Mailer Software) * - Recently Updated Version @ - New Addition # - Commercial SoftWare(Not In Use Yet) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Utility Authors: Please help keep this list up to date by reporting all new versions to 1:103/950. Note: It is not our intent to list all utilities here, only those which verge on necessity. If you want it updated in the next FidoNews, get it to me by Thursday evening. --David French, 1:103/950 ---------------------------------------------------------------------- FidoNews 8-34 Page 26 26 Aug 1991 ------- FIDONEWS MASTHEAD AND CONTACT INFORMATION ---------------- Editors: Tom Jennings, Tim Pozar Editors Emeritii: Thom Henderson, Dale Lovell, Vince Periello Special thanks to Ken Kaplan, 1:100/22, aka Fido #22 "FidoNews" BBS FidoNet 1:1/1 Internet fidonews@fidonews.fidonet.org BBS (415)-863-2739 (9600 HST/V32) (Postal Service mailing address) FidoNews Box 77731 San Francisco CA 94107 USA 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. FidoNews is copyright 1991 Fido Software. All rights reserved. Duplication and/or distribution permitted for noncommercial purposes only. For use in other circumstances, please contact FidoNews (we're easy). OBTAINING COPIES: FidoNews in electronic form may be obtained from the FidoNews BBS via manual download or Wazoo FileRequest, or from various sites in the FidoNet and via uucp. PRINTED COPIES mailed may be obtained from Fido Software for $5.00US each PostPaid First Class within North America, or $7.00US elsewhere, mailed Air Mail. (US funds drawn upon a US bank only.) Periodic subscriptions are not available at this time; if enough people request it I will implement it. 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 BBS, or Wazoo filerequestable from 1:1/1 as file "ARTSPEC.DOC". FidoNews 8-34 Page 27 26 Aug 1991 "Fido", "FidoNet" and the dog-with-diskette are U.S. registered trademarks of Tom Jennings of Fido Software, Box 77731, San Francisco CA 94107, USA and are used with permission. -- END ----------------------------------------------------------------------