informis/textfiles
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
textfiles/bbs/FIDONET/FIDONEWS/fido0838.nws

1396 lines
65 KiB
Plaintext
Raw Permalink Normal View History

Initial commit
2021-04-15 13:31:59 -05:00
F I D O N E W S -- | Vol. 8 No. 38 (23 September 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: more of same ....................................... 1
2. FIDONET NEWS .................................................. 3
(No FidoNetNews this week) .................................... 3
3. ARTICLES ...................................................... 4
European DEMO(FIDO)CRACY or POWER POLITICAL Platforms? ........ 4
NEW LAW RESTRICTS BBS'S IN NEW YORK ........................... 6
How Caller ID Helped Me ....................................... 7
Indianapolis PC-Pursuitable Bulletin Boards ................... 9
Once upon a long time ago ..................................... 11
Fort Worth Nodelist v3.2.1 .................................... 13
Animal_Rights Conference ...................................... 17
4. RANTS AND FLAMES .............................................. 20
5. CLASSIFIEDS ................................................... 21
6. NOTICES ....................................................... 22
The Interrupt Stack ........................................... 22
7. LATEST VERSIONS ............................................... 23
FidoNews 8-38 Page 1 23 Sep 1991
======================================================================
EDITORIAL
======================================================================
Editorial: More of same
by Tom Jennings (1:1/1)
Another editorial devoted to the FidoNews article
submission policy. So far, all I have heard (even from myself) is all or
nuttin' -- FidoNet/technology related, or wide open, willy nilly include
*.ART. I think there are other possibilities. One is outlined below.
The issue boils down to the very basics of Western Law. We want to
formulate a fair and predictable policy that satisfies the needs of
authors, readers, and lastly, the editor. Fairness here means every
reasonable voice is heard. We're trying to define reasonable, and at the
same time, prevent individual(s) from excluding text for arbitrary
reasons. (Arbitrary to the authors that is.)
--> I subscribe to the theory that it is better to be able to make the
choice yourself, even at the slight expense of getting annoyed or
offended occasionally.
--> A minority claims that receiving "offensive" material is an assault,
that offensive material should not be published in the first place.
If you claim to have such a "right", then I do as well, and if I would
not be offended, then causing the removal of such things before I see
them is *a priori* interfering with my personal affairs, which you have
*no right* to do. *Especially* if you don't agree with me -- if we all
always agreed, there would be no controversy in the first place!
--> If something is excluded, I cannot choose; I am deprived of the
information, good or bad. The choice was made for me.
--> If something is included, you then have the information by which to
choose. And others can exercise their right as well, independent from
yours.
If you are repeatedly offended you can simply cut off the offending
communication channel -- in this case, FidoNews. FidoNews is not the
only
game in town. I have been reviewing other electronic newsletters, and
this is a free country still, you can start your own. I'll even help --
even if I don't like it!
A NEW PROPOSAL:
FidoNews 8-38 Page 2 23 Sep 1991
I now propose that the policy remain "wide open". However --
If a particular article generates a cascade of responses, the editor
does two things: (1) chooses one or few of them as representative; (2)
passes them on to the original author, who is asked to write a response
within 2 weeks. The resulting representative response(s), and the
original authors response, are run in one (3rd week?) FidoNews issue.
This is done ONCE ONLY. Interested parties can then pick up the torch
and march with it off the long or short pier of their choice.
I'm sure I'm reinventing the wheel here, it's something we here in
Fidoland seem to do a lot. Hopefully we learn from our mistakes.
----------------------------------------------------------------------
FidoNews 8-38 Page 3 23 Sep 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.
################################################################
----------------------------------------------------------------------
There were no FidoNetNews submissions this week. Tune again in
next week!
----------------------------------------------------------------------
FidoNews 8-38 Page 4 23 Sep 1991
======================================================================
ARTICLES
======================================================================
Michael Pereira, SysOp
2:253/69@fidonet.org
66:66/1@S<tm>.I.A.C.S., London U.K.
European DEMO(FIDO)CRACY or POWER POLITICAL Platforms?
Why did I join FidONET?
In August of 1990, I joined FidONet. Why? Because I wanted to belong to
an organized collective group of individuals who shared the same idea's
of communication, irrespective of age, religion, creed, colour, society
or nationality. I wanted to communicate with like minded people around
the World. FidONet appealed to me because it held this principle in an
easily accessible, OPEN and financially unrestrictive environment.
This was THE Philosophy and 'Spirit of FidONet' which has now resulted
in 51 Regions in 6 Zones WORLDWIDE and in excess of 11,000+ BB Systems.
Policy as DOGMA or CONCEPTUAL Ideology?
Quantitatively speaking we have an immense Network governed by A POLICY
in many respects OPEN, subject to interpretation, allowing flexibility
and scope for change. Indeed, since it's inception FidONet has changed
and will continue to change to accomodate different technologies, needs
purposes, attitudes &c.,&c. Throughout Policy 'themes' of expandability
and interpretation are relayed to the SysOp, conveying the message that
little apart from the 'TECHNICAL ROLES' of Coordinators are NOT SUBJECT
to interpretation.This belief that the role of the *C Structure is ONLY
in coordination and NOT GOVERNMENT, forms the backbone of a technically
stable, competant FidONet, continuing a tradition of accessibility and
CONNECTIVITY for ALL.
Democracy in OPPOSITION to the *C Structure?
I am in Zone 2. Z2 compromises 26 Regions ideologically, sociologically
(in fact ALL the 'ologically's' you can think of ;) DIFFERENT.
I'm in U.K. Z2 Region 25. Where we have seen a DRAMATIC increase in the
amount of dissent,disatisfaction, anger and finally mutiny resulting in
a resignation, reinstatement / retraction (via Vote of Confidence) and
finally a firm resignation by a 'democratically' elected R.C. Why? I'll
tell you why. Because, he sought to UNILATERALLY CHANGE U.K. FidONet.
Interfering with NetWork operations, Electronic Mail and the conduct of
BBS Systems within Region. It's not isolated to Region 25. In Region 23
(Denmark), in Region 29 (Belgium) &c.,&c., we see the same by those who
were democratically elected into technical/coordinatorial positions and
NOT into a psuedo-presidential office.
FidoNews 8-38 Page 5 23 Sep 1991
A Coordinator is NOT required to provide any sort of 'Leadership' in an
environment where his primary responsibility is one of coordination and
technical/administrative scope. His ONLY RIGHT as coordinator is to TRY
(not unilaterally). Democracy is not the same as 'Autocracy'. In Europe
and the U.K. we've seen a dangerous progression to the latter,resulting
in states of defragmentation and bureaucracy, by these overly political
ambitious, power crazed zealots, who are turning the FidONet philosophy
of communication into ' Power-Platforms' for their mandates on morality
judgement, sociological ideologies, based on a Policy, which *DOES NOT*
allow them these self-adopted (or self-inflicted) priviledges.
We therefore see the creation of states of anarchy, in the process as
more ' grunt ' SysOp's rebel against benign dictatorships or autocratic
regimes analogous to the Eastern Block which 'Democratic' Europe fought
against and WON.
Reconciliation of the FUNDAMENTAL - How?
In coming to a solution to said problems,which are by no means isolated
to European FidO we have to re-examine the role of COORDINATOR as it is
described in Policy and within a DIRECT context to the changing face of
FidONet in the 1990's. We therefore need to find ( at the very least )
proximate solutions to what apparently seem insoluble problems.
We NEED to ask ourselves some questions:
1) Do we NEED Leaders and/or figurheads ?
2) Do we NEED a Democracy ?
3) Do we NEED a CENTRALIZED government ?
4) Do we NEED to re-examine our DECENTRALIZED autonomy ?
5) Do we NEED to review *C Structure responsibility ?
6) Do we NEED to review Policy ?
In pursuit of these answers, re-examination of the primary fundamental
philosopy that propels FidONet on continuing success, is a necessity to
establish codes of practice for the *C Structure. Most importantly the
acceptance that FidONet is a non-commercial, amateur EMail NetWork with
a technical / managerial heirarchy which specifically abstains and DOES
NOT aspire to ANY 'Leadership' heirarchy, existing solely to provide an
End User with an independant EMail resource,to advance their individual
interests and/or pursuits freely and without compromise.
In Closing:
To express this eloquently, I'll end by quoting a fellow NET253 SysOp
who has captured the idea humourously though pointedly in reference to
the above.
----------------------------------------------------------------------
'But that is no licence to any of us 'fleas' on FidO's back, aspire to
become the tail that tries to wag the dog'.
----------------------------------------------------------------------
FidoNews 8-38 Page 6 23 Sep 1991
We as Members of FidONet have a responsibilty not only to ourselves in
maintaining the ' Spirit of FidONet ' but we owe it to ALL User's that
patronise our Systems' and who *COMMUNICATE* through us, to offer them
those services that we as SysOp's take for granted. We cannot do this
effectively if our own house is in disarray,due to a small minority of
individuals who insist on propagating the ideals of a strongly led and
controlled - commercially effective NetWork. We need our *C Structure
to COORDINATE FidONet but we cannot tolerate a *C Structure who's main
aims and objectives are that of CONTROL.
Regards,
Michael Pereira.
----------------------------------------------------------------------
Author's name?!
IF THIS IS TRUE, IT MAY BE THE BEGINNING OF THE
END OF BBS'S AS WE KNOW THEM. I AM ATTEMPTING
TO VERIFY THIS INFORMATION AT THIS TIME. I
FEEL IF ONE STATE GETS AWAY WITH THIS THEN
EVERY STATE WILL ENACT A SIMILAR LAW!
OVERVIEW:
In brief summary, the law which stands, says that a SysOp
that allows the transfer of software from his BBS, is in
violation of the NYS Tax and Finance Law, and is subject
to substantial fines, and penalties.
NYS has begun taxing software based on the "value" of the
software, regardless of the authors asking price, on PD
or FW software. I am adamantly opposed to this taxation, as
SysOps receive no compensation for our efforts!
"Effective September 1, 1991, the sale of all prewritten
software will be subject to New York State and local sales
tax. The sale of prewritten software includes any transfer
of title or possession, any exchange, barter, rental, lease
or license to use, including merely the right to reproduce.
The only software which will now be considered exempt is
software designed or written to the specification of a
specific purchaser. The medium by which the software is
transferred to the purchaser has no effect on its
taxability."
----------------------------------------------------------------------
FidoNews 8-38 Page 7 23 Sep 1991
By: Fred Vobbe, SysOp 1:234/16.
How Caller ID Helped Me.
The controversial talk over the Caller ID issue has really spawned
some interesting debates in the various echoes. If you don't know what
Caller ID is, it's a device placed on your telephone line that allows you
to see the number of the person who is calling, before you pick up the
phone. This is done by a datastream which is sent during the ring-cycle.
I should point out that not all telephone systems have this feature
available.
In some areas they are treating the issue as taboo, while other telcos
(telephone companies) are offer it willingly to customers. It is also
received in the same way by customers, clients, and the general public. In
reading the echoes I have seen everything from lighthearted debate to out
and out war complete with threats. Why all the excitement over Caller ID?.
For some people, calling someone and having their number displayed to
person they are calling is quite threatening. These folks don't want
anyone to know where they are calling from, for whatever reason. In 25% of
the messages read, by reading the context of the message or noting the type
of tag/origin lines, I always had the feeling that the person doing the
most yelling and screaming against Caller ID had something to hide. Others
just didn't like the idea of their "privacy" being invaded. (Hmmmmm, what
about the privacy of the person they are calling?)
Now if it seems like I am for Caller ID, you have guessed right. I was
not sold on it until the last 6 months proved to me that the system is an
acceptable utility in todays communications.
About two years ago, I had a very abusive user on my system. This
person would leave flames in public areas, slandered the sysops and users,
and log on under several names at a time. We were finally able to nail him
when we noticed that he logged on using his real name, and another users
password, dropped carrier, and called back immediately using his "abusive"
user name and the same password. After getting booted from they system, he
made the rounds to other systems kicking and yelling, telling people how
were out to get him.
A short time afterwards he started his own system, and later installed
a mailer system. It was then that our real problems surfaced. For a while
we had a mailer calling us using the node number 1:234/56. There is no 56
in our net. The mailer was FREQing our echomail from us using *.MO* *.TU*
*.WE* etc. The sysop name on the log was blank, as was the boards name.
Later, the board's name came up as "HA!", with sysop name of Fuk Ewe. I
then passworded the node number 1:234/56 and removed all FREQ access to my
e:\fd\files area.
The mailer continued to call, and later it assumed the number, name,
and sysop name of my NEC. Problem was, my NEC was running Binkley and the
mailer calling was FD 199C. My NEC also ran an HST at 9600 baud, while the
mystery mailer continued to call at 2400 baud. This nonsense continued for
a while with the system trying to FREQ files, nodelists, anything just to
tie up my system during ZMH.
FidoNews 8-38 Page 8 23 Sep 1991
Then more trouble started when my mail processing was choked at least
eleven times by the mailer dropping off echomail bombs. The mail was from
some Si-Fi echo and had the origins and seen-bys altered. It was also
presented to us as the HA! echo. Later we got real mail bombs, which
unpacked from 12.MSG to 772.MSG, with each message being around 10-18k in
length, (the text being random characters). This crippled our mail, as
well as brought our system down for up to twelve hours till we could sort
things out.
Keep in mind that over the past year my NEC/NC could not do anything.
I could not do anything because the bulk of the abuse was happening when I
was sleeping at night or away on business. I was forced into passwording,
and putting security on my entire system, (which I hated to do because I
always kept my system open so anyone could get anything they wanted at
anytime). Because my system passed mail to other boards, and hubbed files,
it was killing our productivity.
It was then that I spoke to a couple friends, one which works for a
telephone company and is experienced in tracing and tracking calls on
digital systems. The other is a lawyer who worked for a -very- large
corporation and worked directly with the F.C.C. on all the corporations
broadcast interests. From past history, and their recommendations, I make
the decision to install Caller ID.
All telephone lines on our system were hooked up, and a message was
generated which after a person calls, the first thing they see is "CALLER
ID ENABLED". Within 48 hours after the Caller ID box was installed, and
users saw the message, all the shit stopped! No bogus log-ons leaving
flames in public areas. No mailers using false numbers dropping off bombs
and requesting 12 meg worth of files.
Am I happy? Yes, I think that Caller ID served it's purpose! For the
money invested in the box, it was well worth getting rid of all the hassles
and unnecessary hours I had to spend cleaning out message bases, and
straightening up my mail. Anyone with legitimate reasons to call has
nothing to fear, but the ones calling just to trash our board can't call
now because they can be found out.
As a point of interest, having documented everything in the past couple
of years, (60 disks worth), and having the contacts with some heavy hitters
in the legal world, it is plain to see that should anything start up again
the abusive caller could wind up with a multi- million dollar law suit and
jail time. Just to defend themselves in a court of law could cost them
every asset they have.
My local telco was unwilling to tell me what they would do if they
caught the person, and seemed very much apathetic to the matter. They
refused to discuss any penalty or what they would do. However, removing
the issue from the local telco and placing it directly into a court of law
with substantial evidence, and using federal telecommunications laws, it is
obvious that I now have a weapon to protect myself from abuse.
FidoNews 8-38 Page 9 23 Sep 1991
I also have to commend at least one software company who has written
software that interfaces with the Caller ID box to provide a database of
callers. I would hope that other authors of mailer and BBS software take
note of this feature, and write it into their product.
In conclusion, I know that some people are opposed to Caller ID. Fine,
you have your right to your opinion. My writing is not to promote the
device, only to inform those here how I regained a lot of my free time,
sanity, and lost the aggravation of abuse on my system, just because of
-one- abusive user. I'm not going to debate the issue, but I will shake
the hand of the guy who invented the device. He provided me with a very
valuable tool to curb abuse on my system.
Fred Vobbe @ The Black Hole BBS
Home of: CHART.ARC the weekly ChR/AC Music List.
STARFIND.ZIP the satellite location program.
Radio/Television & Amateur Radio Files.
(419) 228-7236 for BBS Access.
----------------------------------------------------------------------
Dave Appel
a user on 1:231/30, or point 1:231/250.3
Bulletin Boards in the Indianapolis area as of September 13, 1991.
These boards should be reachable via Starlink Node 9349 and via
PC-PURSUIT (D/ININD). All area codes are 317. These groupings are
based on the kinds of computers supported, not necessarily the
computer which runs the BBS.
AMIGA
Allegro Vivace 297-0683 Amiga-Soft BBS 546-4944
AmigaVisions 839-1356 ClassiComputerFieds 359-5199
Data Central BBS 543-2007 Falx Cerebri QBBS 290-9070
Files of Memory Alpha 290-0119 Guru Meditation 486-9245
IndyServe 849-4007 PalNet 861-4498
APPLE
Message Center 573-9409 PalNet 861-4498
Sanitarium BBS 293-1665 TARDIS BBS 271-5059
ATARI
Falx Cerebri QBBS 290-9070 IndyServe 849-4007
ST Archive 353-9326
COCO
Communicator BBS 462-1672
COMMODORE
7.5 Alive 297-4292 Brice's Library TBBS 353-0410
C*H*U*G BBS 784-9755 Chatter Box 899-1942
ClassiComputerFieds 359-5199 Communicator BBS 462-1672
GilSue Island 549-0407 INDIANA BBS 297-4224
Indy * X BBS 297-2260 Midnight Flyer 293-8522
Sherwood Forest 244-1146
FidoNews 8-38 Page 10 23 Sep 1991
CP/M
Brice's Library TBBS 353-0410 ClassiComputerFieds 359-5199
Data Central BBS 543-2007 PalNet 861-4498
MAC
ClassiComputerFieds 359-5199 Data Central BBS 543-2007
Falx Cerebri QBBS 290-9070 IndyServe 849-4007
Montgomery's Ward 486-0000 PalNet 861-4498
MS-DOS
7.5 Alive 297-4292 Access Line BBS 546-6926
Adult BBS 784-6975 Allegro Vivace 297-0683
AmigaVisions 839-1356 Berean QuickBBS 328-9244
Brice's Library TBBS 353-0410 Cape of Lost Hope ][ 578-8533
Circle-City BBS 243-0755 ClassiComputerFieds 359-5199
Command Central II 782-8094 Communication Exch. Svc. 899-0929
Communicator BBS 462-1672 CompuAdd Superstore 885-0820
CompuSTUFF 293-8630 Connections 894-4758
Crossroads Broadcast 878-4069 CyberSoftWorks 547-1162
Data Central BBS 543-2007 Direct Access BBS 291-7827
Elfstone 247-1367 Explorer Indy 921-4122
Falx Cerebri QBBS 290-9070 Gamers BBS 357-0198
Grafted Branch 881-4369 Graphics Unlimited 875-9712
Gulf Stream Systems 841-8156 Gun/Link BBS 745-1544
Handy Services BBS 831-1827 IBM NET Connection #1 882-5575
IBM NET Connection #2 247-1347 INDIANA BBS 297-4224
Indpls Computer Soc. 251-2067 Indpls Computer Society 251-2418
Indpls Computer Soc. 251-2379 Indy Net One 845-6391
INDY-PC BBS 257-5882 IndyServe 849-4007
IUPUI BBoard 274-2405 JoBBS, Job Oriented BBS 244-7760
Loading Zone BBS 831-3498 M&L Northeast 576-0896
MediaNET Pro-Line BBS 547-6204 Mega Board 2000 236-8748
Microcosm 545-0930 MotherBoard 881-2743
Northeast Golf Soc. 576-0896 OPUS Pocus 848-1701
Ordovician Ooze 636-7406 Paladen BBS 353-2973
PalNet 861-4498 Pandaemoniun 894-9862
Paradise Cafe 773-1463 PC Solutions 579-6319
PC-Den 862-5965 PCjr Little OPUS 636-3961
Prime Cuts 839-9558 Professional's Choice 925-7273
Public Brand Software 856-2087 Riddle's Comp. Systems 889-6669
Road House BBS 784-2147 Sierra Connection 357-8145
Someplace BBS 353-9981 Something DifferNet 297-1358
Southport Connection 784-2128 SouthSide QuickBBS 535-9097
SW Indy BBS 856-7562 Teen Angel BBS 881-6154
User's Choice 894-1378 Watch Word BBS 247-1382
Westside Too! 839-0728 Widow's Walk 539-5566
OS/2
PC Solutions 579-6319
PDP
PalNet 861-4498
FidoNews 8-38 Page 11 23 Sep 1991
TI 99/4A
HUG, Hoosier Users Group 782-9942
TRS-80
Access Line BBS 546-6926 Communicator BBS 462-1672
Handy Services BBS 831-1827 PalNet 861-4498
UNIX
Grafted Branch 881-4369 Indy Net One 845-6391
Northern Star 251-7421
VAX
PalNet 861-4498
UNKNOWN
Fun Factory 873-3729
Home of Big Time Wrestling 244-2794 Latenight BBS 251-5119
Neverest Mountain 786-6824 Off-The-Wall 862-6691
ROAOBBS 578-4238 Tony's Room 926-4450
----------------------------------------------------------------------
Once upon a long time ago...
G. Joseph Peck
VETLink #1 - Berkshire Veterans' Center, Inc.
Post Office Box 2056 - Pittsfield, MA 01202
(413) 443-6313
Once upon a long time ago "advisors" were sent to a little country
across the sea. Soon thereafter, a US President said "Ask not
what your country can do for YOU... ask what YOU can do for your
country!" Almost immediately, there thronged to military
recruitment centers around the country hordes of young Americans,
eager and willing to do what proud countrymen had done in ages
past: Defend America and her principles - this time in a country
called Viet Nam.
With leaders that often pulled in different directions, objectives
taken only to be quickly abandoned, America super-examining HER
conscience and losing many of her finest, military strength began
to decrease and "Project 100,000" (A Great Society "brainchild"
instituted to get America's disadvantaged youth 'off the streets'
and teach military discipline and skills) was instituted. Soon
that, too, disturbed the conscience of America.
Proud defenders of freedom they, returning soldiers were treated
with less-than-honorable regard as America "punished the warriors"
for doing what their country had asked them to do.
Once upon a long time ago, too, on a cold and quiet Wyoming night,
a computer-using veteran tap-tap-tapped out a message on his
keyboard to another veteran who "understood" and "talked the same
language" into an echo called VIETNAM_VETS. A "bouncing betty" had
taken the legs from that veteran and he was confined to his home
"for the duration".
FidoNews 8-38 Page 12 23 Sep 1991
Soon, heavens that once were filled with tears melted into a link
of brotherhood. And that "brotherhood" grew and grew and grew as
more and more veterans discovered they weren't alone in their
nightmares, troubles and successes - and they began to communicate
with one another. Other "echoes" (message bases that were
exchanged with other BBSs and their users) were created as
VIETNAM_VETS discovered the wide range of topics that America's
veterans had in common - or wanted to learn more about... and
VETNet was born.
On Veterans' Day, 1987 (11/11/87) there entered into the computer-
using veterans' world an electronic newsletter that would distill
some of the information from VIETNAM_VETS and the VETNet echoes
and add other articles that all veterans (and their families)
might like to know about. "NamVet" - the electronic newsletter
by, for and about veterans and the issues that concern them -
became a monthly reality!
No "magic wand" was waved, nor was there anyone "behind the
scenes" casting spells or other incantations upon the messages in
VIETNAM_VETS and the VETNet echoes. Almost miraculously, a
"loosening of the chains" began to take place. Veterans, once
solely focused on the "rejection" they endured when they returned
to civilian life, began to communicate about BASIC training,
weaponry used in battle, tracers, dustoffs, medevacs, soldier
"games" and happenings, EARNED veteran benefits that often were
being denied by a cold an' sterile Veterans Administration and
other agencies ... and VETLink #1 - on the scene from almost day
one - increased its efforts to touch ALL veterans.
VETLink #2 (703-471-8010), with SysOp Ray "Frenchy" Moreau at the
Herndon, VA helm, added his efforts, equipment and expertise;
VETLink #3 (314-334-6359) in Cape Girardeau, MO with SysOp Mike
Bryeans continuously added his programming expertise and an awful
lot of needed help; VETLink #4 (301-261-5644) in Shady Side, MD
with SysOp Jim Hildwine added his communications expertise; and
VETLink #5 (201-778-1879) in Passaic, NJ with SysOp Fred Sochacki
"Semper Fidelis"-ing all the way <grin> ... and the VETLink #?
BBS, each carrying the VETNet echoes, important veteran text files
and many issues of NamVet, became truly a LINKing of the proud
VETerans of our nation - with each new VETLink BBS adding a new
and sometimes colorful hue to the word VETERAN. (VETLink's 4 and
5 will soon be adding special and unique echoes to the VETNet
echoes)
Once upon a long time ago on a cold and quiet Wyoming night, a
computer-using veteran tap-tap-tapped out a message on his
keyboard to another veteran who "understood" and "talked the same
language" into an echo called VIETNAM_VETS --
...and his brothers and sisters, in an electronic way, have
answered the call!
FidoNews 8-38 Page 13 23 Sep 1991
The MORAL of this story? "Ya ain't alone, brother and sister
veteran! If you wanna talk to a brother/sister veteran or you
need veteran benefit information or want to find out about a
reunion or try to find out about a veteran you've lost contact
with, or anything else veteran-related, pop into the VIETNAM_VETS
echo or call a VETLink near you. If there ISN'T one, think about
BEING one... or ask your friendly SysOp about VETLink!!!"
'til next time
Show a brother or sister veteran
That YOU care!!!
and we might ALL "live happily ever after" <smilez>
Ci'ao for Ni'ao
- Joe -
----------------------------------------------------------------------
Aaron Goldblatt Will Schlichtman
1:130/32.1 FidoNet 1:350/59.0 FidoNet
50:5817/150 EchoNet
The Distribution Nodelist
The Fort Worth Format Version 3.2
-=* Part I *=-
by Aaron Goldblatt (1:130/32.1@fidonet)
Development Manager: Will Schlichtman (1:350/59.0@fidonet)
September 14, 1991
This week we begin the release of Version 3.2 of the Fort Worth Nodelist
format. Because it has been completely rewritten and expanded it is
necessary to break into chunks to fit within FidoNews guidelines. This
was somewhat tricky, so the decision was made to make it as close to 10k
as possible, while not breaking up sections.
Versions 3.0 and 3.1 were never released. They were developmental
versions only, seen by Aaron Goldblatt and Will Schlichtman in the
development of their Fort Worth Nodelist conversion program.
Certain portions of this document have been deleted. The whole thing is
an FSC-style document, and much of the verbage that goes into one can be
dropped for FidoNews. Other portions have been edited slightly for
verbage, but the ideas expressed remain unaltered.
This week we begin with an overview of the nodelist format and its
individual fields. Next week we will define each field in detail.
The last week we will define the optional files and difference files,
and we will give a numerical analysis of the space savings of the Fort
Worth Format over the St. Louis Format nodelist.
FidoNews 8-38 Page 14 23 Sep 1991
So, without further ado . . .
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1.0 Overview
------------
This document defines the format and content of the nodelist for the
FidoNet Network (FidoNet) as published each Friday.
The nodelist is published as an ASCII text file named NODELIST.nnn,
where nnn is the day-of-year of the Friday publication date.
One companion file, CITYLIST.nnn, contains optional data which an
individual sysop may choose to use, or may not to. CITYLIST.nnn contains
the city and state (or city and country) location of each node.
This companion file is also an ASCII text file.
NODELIST and CITYLIST SYSLIST contain two kinds of lines, comment lines
and data lines. Each line is terminated with an ASCII CR/LF pair
without extra white space. The file is terminated with an end-of-file
character (EOF = decimal character value 26).
Comments lines contain a semicolon (;) in the first character position
followed by zero or more alphabetic characters called "interest flags".
The remainder of a comment line (with one exception, treated below) is
free-form ASCII text. There are five interest flags defined as follows:
[Several paragraphs have been deleted from the FidoNews article.
They cover:
o Comment flags
o CRC notation
o CRC checks
o Definition of "alphanumeric character" as any ASCII
character between hex 20 and 7E
All of these items remain unchanged from the St. Louis Nodelist.]
2.0 NODELIST.nnn
----------------
The following discussion is of the 12 individual types of nodelist
entries, first the format for each, second a brief definition of each
field, and then a discussion of how each line and field is used. In
line definitions, an UPPERCASE character is defined as a static,
unchanging character, and lowercase is defined as a variable field
to be filled with alphanumeric characters.
2.1 Field Definitions
---------------------
Zone --
Z,z_num,area,sysop,fphone,bps,mdmflg,ho,frq,opt
FidoNews 8-38 Page 15 23 Sep 1991
Region --
R,r_num,area,sysop,fphone,bps,mdmflg,ho,frq,opt
Net --
N,n_num,area,sysop,ac,phone,bps,mdmflg,ho,frq,opt
Hub --
H,h_num,sysop,phone,bps,mdmflg,ho,frq,opt
Hub Override --
U,h_num,sysop,ac,phone,bps,mdmflg,ho,frq,opt
Phone Override --
O,num,sysop,fphone,bps,mdmflg,ho,frq,opt
Normal Entries --
num,sysop,phone,bps,mdmflg,ho,frq,opt
Private --
P,num,sysop
Down --
D,num,sysop
Keep --
K,num,sysop,phone,bps,mdmflg,ho,frq,opt
Zone Service --
S,num,sysop,fphone,bps,mdmflg,ho,frq,opt
Region Independant --
I,num,sysop,fphone,bps,mdmflg,ho,frq,opt
2.2 Fields
----------
z_num - Zone number, 1 to 32767
r_num - Region number, unique to a Zone, 1 to 32767
n_num - Net number, unique to a Zone, 1 to 32767
h_num - Hub number, unique to a Net, 1 to 32767
num - Individual node number, unique to a Net, 1 to 32767
area - Area of administration
sysop - Name of System Operator, person responsible for system
ac - Area code or other repeating information of a given local area
Net
fphone - Phone number of a node, including area code or other
repeating information of a given local area Net
phone - Phone number of a node, not including area code or other
repeating information of a given local are Net
bps - Flag indicating DTE/DCE speed for system's modem
mdmflg - Flag indicating any special protocols used by modem
ho - Hours of operation
FidoNews 8-38 Page 16 23 Sep 1991
frq - Flag indicating file request capability of a front-end mailer
opt - Any optional flag the IC may designate
2.3 Explanations
----------------
Zone --
Begins the definition of a geographic zone and defines its
coordinator. All the data lines following a line with the "Z" key
letter down to, but not including, the next occurrence of a "Z"
keyword, are regions, networks, and nodes within the defined zone.
All data lines following a line with the "Z" keyword down to, but
not including, the next occurrence of a "Z", "R", or "N" keyword,
are Zone Service Nodes (see Zone Service).
Region --
Begins the definition of a geographic region and defines its
coordinator. All the data lines following a line with the
"R" keyword down to, but not including, the next occurrence
of a "Z", "R", or "N" keyword, are independent nodes within
the defined region (see Region Independants).
Net --
Begins the definition of a local network and defines its
coordinator. All the data lines following a line with the "N"
keyword down to, but not including, the next occurrence of a "Z",
"R", or "N" keyword, are local nodes, members of the defined
local network.
Hub --
Begins the definition of a routing subunit within a multilevel
local network. The hub is the routing focal point for nodes
listed below it until the next occurrence of a "Z", "R", "N",
or "H" keyword. The hub entry MUST be a redundant entry, with
a unique number, for one of the nodes listed below it. This
is necessary because some nodelist processors eliminate these
entries in all but the local network.
Hub Override --
Same as Hub, except that it allows nets to span area codes using a
hub-based routing system. If an area code-based routing system does
not exist in a given Net, a Net may still span area codes by adding
a null Hub Override field, in the following format:
U,NUL,ac
Phone Override --
Same as a normal entry (below), except that it allows an individual
node to exist outside the normal area code of an individual net.
Normal Entry --
FidoNews 8-38 Page 17 23 Sep 1991
Defines the "standard" member of FidoNet. All other nodelist lines
are based on this one. Any node meeting the minimum requirements
for membership in FidoNet as defined in FTS-0001 and current
policy may use this line.
Private --
Defines a private node with unlisted number. Private nodes
are only allowed as members of local networks.
Down --
Defines a node which is not operational. Mail may NOT be sent to
it. This keyword may not be used for longer than a period to be
defined by FidoNet policy, at which point the node is to be removed
from the nodelist.
Keep --
Defines a node which is temporarily down. Mail may be sent to
it and is held by its host or coordinator.
Zone Service --
Defines a node which is not part of any Region or Zone. These may
be duplicate addresses ONLY. For example, the FidoNews Editor,
1:1/1, is a Zone 1 Service node, while NotiFido, 4:4/4, is a Zone 4
Service node. The Net number is the same as the Zone number.
Region Independant --
Defines a node which is not part of any local area Net, but is still
part of FidoNet and communicates with the rest of it.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Next week we continue with field definitions.
For a copy of the full FSC-style document, including all text that was
deleted from the FidoNews article, FREQ magic name FWNLSPEC from
1:130/28, USR HST/V.32/V.42bis. It is archived in SEA ARC v6.00.
(cont'd)
----------------------------------------------------------------------
By Mike Adams, 1:19/10
Information On The Animal Rights Conference
When you mention "animal rights" to many people, you immediately start
getting some pretty strange looks from them. Much of the reason for
this is that the only impression that many people have of those who are
interested in animal rights and welfare is based upon the various
reports which hit the news media. For the most part, those news reports
have been negative in nature, detailing break-ins at animal research
facilities, attacks on those involved in the production and selling of
meat, and attempts to impede hunters. The reports generally don't tell
of the people who are involved in working with animal shelters to adopt
out unwanted and abandoned pets. They generally don't detail the
efforts of those who are working positively towards alternatives to
using animals in medical research. They don't tell of the many people
FidoNews 8-38 Page 18 23 Sep 1991
who volunteer their time and talents to work with injured animals.
The ANIMAL_RIGHTS conference was designed by its originator, Doris
Marsh, to serve as a means of spreading information about the positive
aspects of the animal rights movement. She explicitly invited those
with differing opinions to come into the conference to discuss both the
pro and con aspects of "animal rights," and that was a pretty bold thing
to do considering the emotional involvement that many people have on
both sides of the issue.
I became involved in the conference virtually by accident. One of the
callers on my bulletin board was closely involved with animal rights,
and when she said that she was having to call long distance to
participate in the echo, I started looking for it. Fortunately, it was
on the BackBone, so it was a relatively easy process to pick it up.
What I saw as a favor for a local caller soon turned into an interesting
experience for me. I started reading the messages, and I started
getting involved with the discussions which were going on. From the
beginning, it was obvious to me that there were radicals on both sides
of the issue, but I was increasingly impressed with those who were able
to express their interests without giving in to the emotion of the
moment.
In the months I've been involved in the echo, discussions have ranged
from simple announcements of sources for animal rights material to
knock-down drag-out fights regarding the mere concept of attributing
"rights" to animals. While we always welcome the former, we are working
to discourage the latter because they're always unproductive. Everyone
is encouraged to speak their minds, to express their thoughts and to
debate the concepts put forward by others in the conference. The
conference rules have recently been revamped to start restricting the
number of personal attacks and off-topic messages. Since then, message
traffic has increased considerably, and a great deal of positive
information is being passed back and forth.
Whatever your stand on the issue of animal rights (or animal respect as
I have come to call it recently), you're welcome to participate in the
echo and express yourself. We want every side of the issue to be
discussed freely and openly, and the primary restrictions are that no
one is to make a personal attack on another participant of the echo and
off-topic messages are to be held to an absolute minimum.
If you're interested in the echo, it can be picked up from the BackBone.
Netmail requests for information may be made to either Doris or myself
as shown below:
Mike Adams, Animal_Rights Moderator at 1:19/10
Doris Marsh, Animal_Rights Co-Moderator at 1:125/20
We're looking forward to increased participation in the conference and
the "polite" discussion of the issues involved in animal rights.
FidoNews 8-38 Page 19 23 Sep 1991
----------------------------------------------------------------------
FidoNews 8-38 Page 20 23 Sep 1991
======================================================================
RANTS AND FLAMES
======================================================================
_(*#$_(*@#(* (*^$+)#(%&+| #$)%(&*#_$ @_#( @$
^@#+)(#&%$*+)$%&*+$*%&#@(@#_|)*%|)#%&)#*%&+(@#&*_+(@#*^&@###
*&#_($*&#$_(*#&$_(#*$&$ _(#$*#$+)#($&*+#)$ &#+$*&#
()*&#$_(&^#$_(#*$_#($^&#_$(^&#_$(&^#$_(&#^ damn right _(#^&$_(#^&
$*&#$_+(* #)$&(%($%+)($%*+$)%($* it's ugly _#&%^# &
#($_*#$_ FidoNet (*$&%_@#_(*&@#_(@*#&_ @#_(*&@#_(*
)*&#$ Flames *^$+)#(% (not for the timid) @_#(
(*#$_(*^@#+) and #_|)*% &+(@#&*_+(@#*^&@###
(#$*&#_($*&#$_(*#&$_(#* Rants *&+#$*&#+$*&#
)*&#$_(a regular feature)^&#_$(&^#$_ $^&#$_(#^
(*^#$_*#^&$)*#&$^%)#*$&^_#($*^&#_($ Section #&%^_
_(*#&$_(#* #($*& #$* _(*&@#_(@*# *&@#_(*&
)&*+_)*&+)*&+))&*(*&
(*&_(*&_(*&
----------------------------------------------------------------------
FidoNews 8-38 Page 21 23 Sep 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-38 Page 22 23 Sep 1991
======================================================================
NOTICES
======================================================================
The Interrupt Stack
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.
2 Nov 1991
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.
3 May 1992
The areacode for northern and central Georgia will change from 404 to
702. The Atlanta metro area will remain area code 404. Area code 912 in
southern Georgia will remain the same. Affected areas will share both
the 404 and the 702 area code from May 3, 1992 until August 3, 1992 when
the change will become permanent.
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-38 Page 23 23 Sep 1991
======================================================================
LATEST VERSIONS
======================================================================
Latest Greatest Software Versions
Last Update: 09/12/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.01* 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
SimplexBBS 1.04.02*+ EditNL 4.00 GUS 1.30
SLBBS 2.15b* FDND 1.10*@ HeadEdit 1.18
Socrates 1.10 MakeNL 2.31 IMAIL 1.10
SuperBBS 1.10 Parselst 1.30 InterPCB 1.31
TAG 2.5g Prune 1.40 MSG 4.1
TBBS 2.1 SysNL 3.14 MSGED 2.06
TComm/TCommNet 3.4 XlatList 2.90 MsgMstr 1.21*
Telegard 2.5 XlaxNode/Diff 2.52* MSGTOSS 1.3
TPBoard 6.1 Oliver 1.0a
TriTel 1.11*@ PolyXarc 2.1a*
Wildcat! 2.55 QM 1.0
WWIV 4.12 Compression QSort 4.04
XBBS 1.17 Utilities ScanToss 1.28
Name Version Sirius 1.0x
-------------------- SLMAIL 1.36
ARC 7.00 StarLink 1.01
ARJ 2.20* TagMail 2.41
HYPER 2.50 TCOMMail 2.2
LHA 2.13* Telemail 1.27
PAK 2.51 TMail 1.21
PKPak 3.61 TPBNetEd 3.2
PKZip 1.10 Tosscan 1.00
UFGATE 1.03
XRS 4.50
FidoNews 8-38 Page 24 23 Sep 1991
XST 2.3e
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
SimplexBBS 1.04.02*+ BinkleyTerm/2-MT ConfMail 4.00
1.40.02*@ 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/15 or 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 + 8.0* Fruity Dog 2.0 deARC2e 2.1
GBBS Pro 2.1 ProSel 8.70*
FidoNews 8-38 Page 25 23 Sep 1991
ShrinkIt 3.30*
|Contact: Dennis McClain-Furmanski 1:275/42| 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.6.1* 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-38 Page 26 23 Sep 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-38 Page 27 23 Sep 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-38 Page 28 23 Sep 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-38 Page 29 23 Sep 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
----------------------------------------------------------------------
Reference in New Issue Copy Permalink