     Volume 6, Number 47                              20 November 1989
     +---------------------------------------------------------------+
     |                                                  _            |
     |                                                 /  \          |
     |                                                /|oo \         |
     |        - FidoNews -                           (_|  /_)        |
     |                                                _`@/_ \    _   |
     |        International                          |     | \   \\  |
     |     FidoNet Association                       | (*) |  \   )) |
     |         Newsletter               ______       |__U__| /  \//  |
     |                                 / FIDO \       _//|| _\   /   |
     |                                (________)     (_/(_|(____/    |
     |                                                     (jm)      |
     +---------------------------------------------------------------+
     Editor in Chief:                                  Vince Perriello
     Editors Emeritii:                                     Dale Lovell
                                                        Thom Henderson
     Chief Procrastinator Emeritus:                       Tom Jennings
     
     FidoNews  is  published  weekly  by  the  International   FidoNet
     Association  as  its  official newsletter.  You are encouraged to
     submit articles for publication in FidoNews.  Article  submission
     standards  are contained in the file ARTSPEC.DOC,  available from
     node 1:1/1.    1:1/1  is  a Continuous Mail system, available for
     network mail 24 hours a day.
     
     Copyright 1989 by  the  International  FidoNet  Association.  All
     rights  reserved.  Duplication  and/or distribution permitted for
     noncommercial purposes only.  For  use  in  other  circumstances,
     please contact IFNA at (314) 576-4067. IFNA may also be contacted
     at PO Box 41143, St. Louis, MO 63141.
     
     Fido  and FidoNet  are registered  trademarks of  Tom Jennings of
     Fido Software,  164 Shipley Avenue,  San Francisco, CA  94107 and
     are used with permission.
     
     We  don't necessarily agree with the contents  of  every  article
     published  here.  Most of these materials are  unsolicited.    No
     article submitted  by  a  FidoNet SysOp will be rejected if it is
     properly attributed and  legally  acceptable.    We  will publish
     every responsible submission received.


                        Table of Contents
     1. ARTICLES  .................................................  1
        A Final Word on IFNA Voting  ..............................  1
        HST (DS) Setup Notes  .....................................  3
        IFNA Bylaws and Rules Committee Report  ...................  9
        IFNA/FidoNet Bylaws Proposal Draft  ....................... 11
        IFNA/FidoNet Policy Appendix Format  ...................... 20
        IFNA/FidoNet Policy Proposal Draft  ....................... 23
        A Visit From My Daisy Maid  ............................... 31
     2. LATEST VERSIONS  .......................................... 33
        Latest Software Versions  ................................. 33
     3. NOTICES  .................................................. 36
     And more!
     FidoNews 6-47                Page 1                   20 Nov 1989


     =================================================================
                                 ARTICLES
     =================================================================

     A Final Word on IFNA Voting

     Phil Buonomo, 1:107/583@FidoNet
                     520/583@AlterNet
                   9:807/1@PNet
                   1-201-935-1485@NJBell

     Well, it all comes down to this.

     Six months ago, I was tired of hearing/reading about the abuses
     of some misguided *C's.  While the great majority of them were
     good folks, we had no guarantees that the nodes would have their
     say under Policy 4.  That's when I had the idea of instilling
     democracy through the legitimacy of IFNA.  I campaigned for
     director seats, went to FidoCon, and forced the issue.  What we
     came out with was a network wide election to determine the
     legitimacy of IFNA.

     Quite simply, if this vote fails, if less than 50% of the
     network votes FOR IFNA, I don't believe we'll see democracy in
     FidoNet at all.  All other major proposals to replace Policy 4
     are based on a vote of the *C structure, not on a vote of the
     nodes like the IFNA vote.  That means that any new policies will
     be decided by the people that're going to lose their guaranteed
     positions under any new policies.  This vote decides policies by
     YOUR vote.  But if it fails, the sysops have only themselves to
     blame.  IFNA will dissolve and FidoNet will be back at Policy 4,
     with the *C's holding all the cards again.  Frankly, I'm
     satisfied that we had the election.  In my opinion, no one will
     be able to say that FidoNet "never had" a chance at democracy
     again.

     If you haven't voted yet, I urge you to read thru the draft
     policy and bylaws published in this issue (if all goes well...).
     The new IFNA calls for network wide votes for the Board of
     Directors.  It guarantees seats on the board for zones outside
     the US, and gives a minimum of 2 seats out of 8 to SOMEONE other
     than the north americans.  It gives any zone a maximum of three
     seats, so that the masses may also be represented.  It calls for
     election of *C members all the way up to the ZC, and since YOU
     elect the BoD, you in essence elect the IC, as well.

     Most importantly, the draft policy eliminates the "excessively
     annoying" clause that's been such a thorn in the side of FidoNet
     for so many years.  Non-technical policy complaints would be a
     thing of the past.  If you can send/receive mail during ZMH, and
     don't interfere with the technical operations of others, you're
     in.  And if you're in the nodelist, you're a full voting member
     of IFNA.

     FidoNews 6-47                Page 2                   20 Nov 1989


     Some people have said that this was all a "power grab", that we
     intend to dictate to FidoNet what it can/cannot do.  To them I
     ask, if that were so, why are we holding a network wide
     election, something Policy 4 and the *C's never did?  Why is the
     entire BoD going to be reseated by next FidoCon?  Why are we
     giving the sysops of FidoNet a chance to vote on accepting or
     rejecting the proposed policy and bylaws.  Some might think that
     those types are interested in maintaining the power of the *C's,
     but thats for others to decide.

     As for the *C's let me say one thing.  I've had my doubts about
     some of them in the past, but most have conducted this election
     in the spirit in which it was intended.  Only one case of
     'election rigging' has reached the election committee, and the
     NC who violated that trust we spoke so much about in September
     is no longer in FidoNet.  I think that speaks a lot about the
     *C's in general, that they are willing to police themselves when
     necessary.  I would like to thank the *C structure and Matt
     Whelan and Steve Bonine especially, for carrying out this
     election.  Unless there's massive reports of voter fraud at the
     last minute, I feel they've done a great job.

     As a last word, I would just ask that if you haven't voted yet,
     that you please do so.  It would be nice if we could show the
     world that when it counts, sysops are NOT apathetic.  This
     election could become a shining example of what people can do
     when they put their minds to it.

     Let's tear down that "Berlin Wall".  Let's have a democratic
     IFNA.

     Thank you for your time.

     -----------------------------------------------------------------
     FidoNews 6-47                Page 3                   20 Nov 1989


     Jim King & John Souvestre
     FidoNet 1:396/1.3 & 396/1.0


                           HST (DS) Setup Notes
                          ----------------------

                             November 12, 1989


     This note describes how to set up the U S Robotics Courier HST
     (14.4K bps), or HST Dual Standard, modem and various IBM-type PC
     communications programs and FOSSILs, including:

             BinkleyTerm 2.30
             BNU 1.70
             DSZ 10/24/89
             Opus 1.03b
             OpusComm 5.31
             ProComm Plus 1.1b
             QModem 4.1b
             X00 1.20c

     The first section has some miscellaneous information about
     running a high speed modem.  The next section covers the setup
     for the HST itself.  The remaining sections cover the various
     communications programs and FOSSILs.

     If you have any questions, suggestions, or setup information for
     other programs, please contact us on the New Orleans Tech BBS,
     FidoNet 1:396/1, 504-885-5928.  On this board you will also find
     a current version of this file under the name HST_SET.ZIP.


     ================================================================


                    General Notes on High Speed Modems
                   ------------------------------------


     The RS-232C cable connecting the modem to the computer's serial
     port should have at least the following pins connected:  1, 2,
     3, 4, 5, 6, 7, 8, and 20.  Get an Ohm Meter, Multimeter, or
     other form of continuity tester and check your cable.  Some
     connectors have pins which are looped back, and are not
     connected to the connector at the other end of the cable.

     To get the "most" out of your HST you will have to set the
     computer-to-modem speed higher than the modem-to-modem speed.
     This is called "locking" the serial port, since it won't be
     operating at the same speed as the modem itself is.  Why is this
     necessary?

     FidoNews 6-47                Page 4                   20 Nov 1989


     For a few reasons:  Most computer serial ports don't operate at
     14400 bps, the basic speed of the HST.  Thus the computer has to
     operate at a higher speed.  Because of this, however, the
     computer and the modem have to be able to "handshake" to prevent
     overrun, and loss of data.  Hardware handshaking, using the RTS
     and CTS lines (in the cable mentioned above) does the job.
     Avoid software handshaking, as it is protocol sensitive.

     Another reason is that the HST does not need to send the start
     and stops bit which make up part of the the asynchronous data
     from/to the computer.  This means that for every 10 bits of
     computer-to-modem data, there is only 8 bits of modem-to-modem
     data.

     Given that each of these represents one character, the cps
     (characters per second) rating of both links is the same.  When
     talking about bps (bits per second) however, this means that the
     computer-to-modem link needs to be 25% faster to keep up with
     the modem-to-modem link, even though both are at the same cps
     rate!

     Now you can see how it is possible to get more that 100%
     throughput with an HST.  Now let's talk about data compression.
     This adds about 5% overhead to the data you are sending.  So, if
     the data is already compressed, with PKZip for example, then you
     will probably just end up losing the 5%.  If you are sending
     ASCII text however, the HST's compression will buy you about
     50-100% improvement.

     The HST allows you to set up compression in one of 3 ways:
     Always on, always off, and do what the other end wants.  In
     general, the calling modem should be set to match the type of
     transfers it expects to be doing.  The answering modem should
     allow the caller to choose whether he wants compression or not.

     Transfers using compression, at 14400 bps, should generally lock
     the serial port at 38400 bps.  19200 bps probably won't be fast
     enough to allow the modem to run at full speed, depending on the
     type of file being compressed.

     In general, unless you expect to be doing lots of transfers
     using compression, it is our opinion that locking the serial
     port at 19200 bps is a better way to go.  It is less demanding
     of the computer, thus reducing the changes of losing data in
     marginal cases.  For transferring previously compressed data,
     where the modem is not doing the compression, 19200 bps will
     suffice, as the maximum rate you will be able to achieve will
     approximately 1650 cps, or 16500 bps on the computer-to-modem
     link.  [Note:  1650 cps is 14400 bps, plus 25% due to start/stop
     bit stripping, minus about 8% for modem-to-modem overhead.]

     FidoNews 6-47                Page 5                   20 Nov 1989


     For the rest of this note we will assume that you want to lock
     the serial port at 19200 bps.  If you want to lock at 38400 bps
     instead, just change the "19200"s to "38400"s.

     Some communications programs and most FOSSILs allow you to
     specify the size of the receive and/or transmit buffers.  The
     best size will depend on many factors, and may require a bit of
     testing on your part.  For starters however, we recommend that
     you make the transmit buffer 1K and the receiver buffer 2K.  If
     you are running under a multi-tasking operating system then you
     might want to start with both set to 4K.

     One thing that you will notice when running a high speed modem
     is that all file protocols are not created equal!  Protocols
     which require an "Ack" for every block sent do not perform well.
     Thus you will want to avoid XModem, for example.  YModem does
     better because it uses a larger block size.

     Streaming protocols, such as ZModem, work fine.  However, avoid
     protocols like YModem-G, which use error detection, but no error
     recovery, simply aborting the transfer upon an error.  Although
     the modem-to-modem transfer is guaranteed by a 16 bit CRC used
     by the modems themselves, errors can still occur between the
     computer and the modem at either end.  In some situations it is
     not uncommon to lose an occasional character (see below).  It is
     not worth this chance for a less than 1% speed advantage.

     We highly recommend replacing the serial interface chip (UART),
     a 8250 or 16450, with a 16550a.  This chip contains a 16
     character FIFO, as opposed to a double buffer.  If your
     communications program makes use of the FIFO, it will allow you
     longer interrupt latency and/or less interrupt overhead.

     Various manufacturers make versions of the 16550a.  National
     Semiconductor was the first.  Their full part number for the
     40-pin DIP is NS16550AN.

     In all the cases that follow we recommend installing a 16550a.
     In some of the cases alternatives are also presented.

     Some computers (particularly 4.77 MHz, 8088 machines) are not
     fast enough to support 19200 or 38400 bps.  If you have this
     type of computer, you can use 9600 bps instead, but this will
     not give you the HST's full speed.

     Certain disk controllers, with 1:1 track buffers, can cause
     problems.  Perstor disk controllers can also cause problems.  We
     understand that Perstor has a BIOS upgrade which helps.

     If you are running a program that makes heavy use of extended
     memory, like a RAM Disk or a Cache, you may lose characters.
     This is mainly a problem on 286 machines.  With some programs,
     like VDisk, reducing the sector size and/or the number of
     sectors transferred at a time will help.

     FidoNews 6-47                Page 6                   20 Nov 1989


     Certain TSRs interfere with communications programs.  If you
     find that you are having trouble, one thing that you should try
     is to reboot with only the bare essentials in your Config.Sys
     and AutoExec.Bat.  If this makes a difference, then you get to
     play detective.

     If you are running DesqView with EEMS or EMS 4.0 memory which
     only has only 1 (or no) alternate map register then you should
     run the communications program in window #1.  Newer AST memory
     boards have multiple registers.  On 386s, using QEMM, you can
     specify how many registers to provide (default is 8).

     Under OS/2, running a communications program in the DOS
     compatibility box at 9600 bps or above, you will probably lose
     characters, unless you have a 16550a and a program that makes
     use of it.  All of the communications programs and FOSSILs
     described in this note will work fine except for ProComm Plus.
     Or, you could always get a communications program written for
     OS/2.

     At the end of this note there is a list of some distributors who
     sell the 16550a.


     ================================================================


                  Setup for U S Robotics Courier HST (DS)
                 -----------------------------------------


     First, check to make sure that you have current ROMs.  Use the
     I7 command.  Compare the version and release dates with these:

         Supervisor date   08/25/89 or 09/29/89
         Supervisor rev      1.1    or   1.2

         IOP date          12/19/88 or 05/17/89 / 08/08/89 / 09/20/89
         IOP rev             1.0    or   1.0    /   1.1    /   1.2

         DSP date          09/18/89
         DSP rev              2

     If any of your ROMs are older, call USR's tech support at
     1-800-982-5151 and get current versions.  USR claims that both
     versions of the Supervisor, and all four versions of the IOP are
     functionally equivalent.  If you find that you are having
     problems connecting with "low cost" 2400 bps modems, make sure
     that you have the current ROMs, especially the DSP!

     Also, if you have an old manual, be sure to get the April 1989
     Addendum.  The DIP switch setting supplement is not very
     accurate, however.

     FidoNews 6-47                Page 7                   20 Nov 1989


     Check the DIP Switches at the rear of the HST.  Please note that
     USR has changed the factory default settings, so check them all:

         1 - Up      [Necessary - Data Terminal Ready follows pin 20]
         2 - Up      [Probably - Most programs use the verbal codes]
         3 - Down    [Probably - Enables result codes]
         4 - Up      [Your choice - Local Echo, confuses some prog's]
         5 - Down    [Probably - Auto Answer disabled]
         6 - Up      [Necessary - Carrier Detect follows signal]
         7 - Up      [Probably - Both originate and answer results]
         8 - Down    [Necessary - Enables command mode]
         9 - Down    [Probably - Escape code maintains connection]
        10 - Up      [Necessary - Power up to NRAM settings]
        11 - Up      [Probably - Normal, see manual]

     Note:  We consider it bad form for a communications program to
     expect the modem to auto-answer the phone.  This allows a modem
     to continue answering the phone after the program has crashed.
     Certainly, any program which demands this anyway should make it
     part of its modem init string, and not expect the modem to
     power-up in that mode.

     The following assumes a locked line rate between the computer
     and the modem.  Also, the settings favor dialing out and
     transferring previously compressed data, because this is the
     most common case and because a BBS can take care of any
     differences in its modem init string.

     Start by setting your communications program to 19200 bps, N81
     (no parity, 8 bits per character, 1 stop bit).  Reset the HST to
     factory defaults (&F command), then change the following:

         S7=50       [Optional - Longer for international calls]
         S10=10      [Recommended - Helps with line dropouts]
         S11=50      [Optional - Increase dialing speed, test to see
                      how fast your exchange will allow it]
         S15=8       [Optional - Reduce Tx buffer for non-ARQ connect]
         S19=5       [Optional - Set inactivity timer]
         B1          [Recommended - DS only - Try for HST connect
                      1st, if fails will try for V.32 connect]
         T           [Optional - Touch-tone dialing]
         X7          [Necessary - X6 gives false "voice" sometimes]
         &A2         [Recommended - Unless it confuses your software]
         &B1         [Necessary - Locked computer-to-modem line rate]
         &H1         [Necessary - Hardware flow control for transmit]
         &K0         [Optional - No compression, or use &K1 for auto]
         &R2         [Necessary - Hardware flow control for receive]
         &S1         [Necessary - Modem controls DSR]

     Finally, save the new settings (&W command).

     FidoNews 6-47                Page 8                   20 Nov 1989


     In the modem strings which follow, drop the B0/B1 if you are not
     using a DS.


     [The second half of this article will be in the next issue]


     -----------------------------------------------------------------
     FidoNews 6-47                Page 9                   20 Nov 1989


     John Roberts
     FidoNet 1:385/49

     We've had some very good response to the IFNA Bylaws and
     IFNA/FidoNet Policy drafts so far, and I want to thank everyone
     who has contributed with their comments and observations so far.

     Once again with Vince's help, the current versions of both
     proposals should appear in this issue of FidoNews.  Changed
     paragraphs in both documents are annotated by a "|" character in
     the second column for clarity.

     If you'd like to request copies of the current version of these
     drafts, they're available as I_POLICY.ARC and I_BYLAWS.ARC from
     1:385/49 (XP/9600/HST/V32) and should also be available for
     request from 1:104/424 (XA/2400) and 1:107/583 (XP/9600/HST/V32)
     as well.

     Also, after the drafts you should find the general format for
     submission of proposed appendices.  This information may be
     requested from 1:385/49 as I_POLAPP.FMT.

     And finally, it's certainly not too late for changes.  We're all
     still listening!





     You may well notice that I said "the current version" above.
     That's because these are both Draft documents at this time, and
     while I feel they're pretty solid overall, it's quite likely that
     there will be further changes before the due date for the final
     proposals to be submitted for vote.

     The point is that they're not carved in stone, and it's
     absolutely not too late for you to be heard if there's something
     you feel strongly about.  As a matter of fact, I'd sincerely like
     to hear your opinions.  If you're not interested in establishing
     a link to the IFNA_POL conference, by all means send me netmail.
     While I can't promise a personal reply to each and every message
     that comes in, I will promise to make sure that your opinions go
     before the committee for consideration.

     The IFNA_POL conference itself is still active and available for
     your comments and discussion, and will remain so as long as
     necessary.  The primary EchoMail link for the conference is Fabian
     Gordon at 1:107/323, and it's available in GroupMail format from
     both myself at 1:385/49 and Phil Buonomo at 1:107/583.

     Getting back to the documents themselves, in particular the
     Policy document, you'll notice that a lot of things simply aren't
     covered.  This is the way it was designed.  We've put into the
     basic policy only the things that we feel are absolutely
     necessary to the operation of the network.  The idea is that you,
     the "grunt sysop" (hasn't anyone got a better term for that?),
     FidoNews 6-47                Page 10                  20 Nov 1989


     are the one who should make the decisions on the details of how
     you want your network to operate, and that you should have a vote
     on each and every item that affects your operation within the
     network.

     Thus the modular approach.  Details such as geographic
     boundaries, selection of coordinators, complaint and grievance
     procedures and other such things that have historically been such
     large points of contention will be added to the basic document as
     Appendices.  Each of these will be voted on separately to and
     independent of the basic policy and each other, and there may
     well be more than one choice for each major issue on the ballot
     along with "none of the above", which will also be a valid choice
     in this sort of election based on preference.

     I'm going to be presumptuous for a moment and ask you for two
     favors, even though I've never met or even corresponded with most
     of you before.  The first is related directly to the two
     documents I've been speechifying about, while the second is much
     more general.

     First, when reading these proposals, try not to read anything
     into them that isn't there.  Take them at face value - that's the
     way we've written them.  There's no "hidden agenda" or hidden
     anything else there, just an honest effort by a few people to put
     the control of FidoNet back into the hands of the sysops of
     FidoNet itself.

     Second, when you're given the opportunity to make your voice
     heard, whether by making comments and suggestions or by casting a
     vote in an election, take the few minutes needed to do so.  If
     you don't, then no one can know what your feelings and opinions
     are on whatever issues may be at hand.  I'm not talking just
     about FidoNet here, but about many of the other aspects of life
     as well.  Communication is a two-way process.  It's been said so
     often that it's rather cliche, but that hasn't made it any less
     true.

     Thanks!

     -----------------------------------------------------------------
     FidoNews 6-47                Page 11                  20 Nov 1989


     IFNA Bylaws and Rules Committee
     Jason Steck, 1:104/424, Member
     Phil Buonomo, 1:107/583, Member
     John Roberts, 1:385/49, Chairman


              BYLAWS OF THE INTERNATIONAL FIDONET ASSOCIATION
                          (Proposed)(Draft v0.04)
                              prepared by the
                        Bylaws and Rules Committee
                                  of the
                     International FidoNet Association

                             November 19, 1989

     ARTICLE I - OFFICES

         Section 1. PRINCIPLE OFFICE.

             The principal office of the corporation shall be in the
             city of Saint Louis, State of Missouri.

         Section 2. OTHER OFFICES.

             The corporation may also have offices at such other
             places within or without the State of Missouri as the
             Board of Directors may from time to time determine or the
             activities of the corporation may require.

         Section 3. REGISTERED OFFICE.

             The registered office of the corporation shall be
             established and maintained at 120 S. Central, Suite 1400,
             St. Louis, Missouri, 63105.

     ARTICLE II - MEETING OF MEMBERS

         Section 1. ANNUAL MEETINGS.

             Annual meetings of members for the election of directors
             and for such other business as may be stated in the
             notice of the meeting, or as many properly come before
             the meeting, shall be held at such places, either within
             or without the State of Missouri, and at such times and
             dates as the Board of Directors, by resolution, shall
             determine and as set forth in the notice of the meeting.
             in the event the Board of Directors fails to so determine
             the time, date and place of the meeting, the annual
             meeting of members shall be held at the principal office
             of the corporation on the 1st day of August at 1 o'clock
             P.M. in each year.

     FidoNews 6-47                Page 12                  20 Nov 1989


         Section 2. OTHER MEETINGS.

             Meetings of members for any purpose other than the
             election of directors may be held at such a time and
             place, within or without the State of Missouri, as shall
             be stated in the notice of the meeting.

         Section 3. VOTING.

             Each member entitled to vote in accordance with the terms
             and provisions of the Articles of Association and these
             Bylaws shall be entitled to one vote, in person or by
             proxy, but no proxy shall be voted after three years from
             its date unless such proxy provides for a longer period.
             Upon the demand of any member, the vote for directors and
             upon any question before the meeting shall be by ballot.
             All elections for directors shall be decided by plurality
             vote; all other questions shall be decided by majority
             vote, except as otherwise provided by the Articles of
             Association or the laws of the State of Missouri.

         Section 4. MEMBERSHIP.

             The officer who has charge of the membership ledger of
             the corporation shall at least ten days before each
             meeting of members prepare a complete alphabetically
             addressed list of the members entitled to vote at the
             ensuing election.  Said list shall be open to the
             examination of any member, for a period of at least 10
             days prior to the meeting, either at a place within the
             city where the meeting is to be held, which place shall
             be specified in the notice of the meeting, or, if not so
             specified, at the place where the meeting is to be held.
             The list shall be available for inspection at the
             meeting.

         Section 5. QUORUM.

             Except as otherwise required by law, by the Articles of
             Association, or by these Bylaws, the presence, in person
             or by proxy, of a majority of the members of the
             corporation entitled to vote thereat shall constitute a
             quorum at a meeting for the transaction of any business.

         Section 6. SPECIAL MEETINGS.

             Special meetings of the members for any purpose, unless
             otherwise prescribed by statute or by the Articles of
             Association, may be called by the Chairman of the Board
             and shall be called by the Chairman of the Board or by
             the secretary at the request of a majority of the
     FidoNews 6-47                Page 13                  20 Nov 1989


             directors or 10 percent of the number of members entitled
             to vote.  Such request shall state the purpose of the
             proposed meeting.

         Section 7. NOTICE OF MEETINGS.

             Notice, stating the place, date, and time of the meeting,
             and the general nature of the business to be considered,
             shall be given to each member entitled to vote thereat at
             his address (electronic or otherwise), or shall be
             published in the corporate newsletter, not less than ten
             nor more than fifty days before the date of the meeting.

         Section 8. BUSINESS TRANSACTED.

             No business other than that stated in the notice shall be
             transacted at any meeting without the unanimous consent
             of all the members entitled to vote thereat.

         Section 9. ACTION WITHOUT MEETING.

             Except as otherwise provided by the Articles of
             Association, whenever the vote of members at a meeting
             thereof is required or permitted to be taken in
             connection with any corporate action by any provisions of
             the statutes of the Articles of Association or of these
             Bylaws, the meeting and vote of members may be dispensed
             with, if all the members who would have been entitled to
             vote upon the action if such meeting were held, shall
             consent (electronically or otherwise) to such corporate
             action being taken.

     ARTICLE III - DIRECTORS

         Section 1. NUMBER AND TERM.

      |      The number of directors shall be equal to the number of
      |      geographical areas known as zones in the list of systems
      |      published by the corporation, known as the IFNA or
      |      FidoNet nodelist, plus an additional 3 directors who
      |      shall be known as At-Large directors.  No Zone may have
      |      more than 3 directors representing it on the Board.  The
      |      Directors shall be elected from the membership during the
      |      annual meeting of members by the members of their
      |      respective Zones, with the exception of the At-Large
      |      Directors, who shall be elected by the membership as a
      |      whole.  Each director shall be elected to serve until his
      |      successor shall be elected and shall qualify.

         Section 2. RESIGNATIONS.

     FidoNews 6-47                Page 14                  20 Nov 1989


             Any director, members of a committee, or other officer
             may resign at any time.  Such resignation shall take
             effect at the time specified, and if no time be
             specified, at the time of its receipt by the president or
             secretary.  The acceptance of a resignation shall not be
             necessary to make it effective.

         Section 3. VACANCIES.

             If the office of any director, member of a committee or
             other officer becomes vacant, the remaining directors in
             office, though less than a quorum by a majority vote, may
             appoint any qualified person to fill such vacancy, and to
             hold office for the unexpired term and until his
             successor shall be duly chosen.

         Section 4. REMOVAL.

             Any director or directors may be removed either for or
             without cause at any time by the affirmative vote of the
             members or holders of a majority of all the membership
             votes of those entitled to vote, at a special meeting of
             the members called for the purpose, and the vacancies
             thus created may be filled, at the meeting held for the
             purpose of removal, by the affirmative vote of the
             members or holders of a majority of all the membership
             votes of those entitled to vote.

         Section 5. INCREASE IN NUMBER.

             The number of directors may be increased by amendment of
             these Bylaws by the affirmative vote of a majority of the
             directors, though less than a quorum, by the affirmative
             vote of the majority of the members, at the annual
             meeting or by a special meeting called for that purpose,
             and by like vote the additional directors may be chosen
             at such meeting to hold office until the next annual
             election and until their successors are elected and
             qualify.

         Section 6. COMPENSATION.

             Directors shall not receive any stated salary for their
             services as directors or as members of committees, but by
             resolution of the Board a fixed fee and expenses of
             attendance may be allowed for attendance at each meeting.
             Nothing herein contained shall be construed to preclude
             any director from serving the corporation in any other
             capacity as an officer, agent or otherwise, and receiving
             compensation therefore.

     FidoNews 6-47                Page 15                  20 Nov 1989


         Section 7. ACTION WITHOUT MEETING.

             Any action required or permitted to be taken at any
             meeting of the Board of Directors, or of any committee
             thereof, may be taken without a meeting, if prior to such
             action a written consent thereto is signed by all members
             of the Board, or of such committee as the case may be,
             and such written consent is filed with the minutes of
             proceedings of the board or committee.

     ARTICLE IV - OFFICERS

         Section 1. OFFICERS.

      |      The officers of the corporation shall consist of a
      |      Chairman of the Board of Directors, a president, a
      |      treasurer, a secretary, and an International Coordinator,
      |      and shall be elected from the membership by the Board of
      |      Directors and shall hold office until their successors
      |      are elected and qualified.  In addition, the Board of
      |      Directors may elect one or more vice-presidents and such
      |      assistant secretaries and assistant treasurers as it may
      |      deem proper.  None of the officers of the corporation
      |      need be directors.  The officers shall be elected at the
      |      first meeting of the Board of Directors after each annual
      |      meeting.  More than two offices may be held by the same
      |      person, except the offices of president and secretary,
      |      unless there is only one member.

         Section 2. OTHER OFFICERS AND AGENTS.

             The Board of Directors may appoint such officers and
             agents as it may deem advisable, who shall hold their
             offices for such terms and shall exercise such power and
             perform such duties as shall be determined from time to
             time by the Board of Directors.

         Section 3. CHAIRMAN.

             The Chairman of the Board of Directors, shall preside at
             all meetings of the Board of Directors, shall appoint the
             chairs of all standing committees, and he shall have and
             perform such other duties as from time to time may be
             assigned to him by the Board of Directors.

         Section 4. PRESIDENT.

             The President shall be the chief executive officer of the
             corporation and shall have the general powers and duties
             of supervision and management usually vested in the
             office of the president of a corporation.  He shall
     FidoNews 6-47                Page 16                  20 Nov 1989


             preside at all meetings of the members if present
             thereat, and in the absence of the Chairman, at all
             meetings of the Board of Directors, and shall have
             general supervision, direction and control of the affairs
             of the corporation.  Except as the Board of Directors
             shall authorize the execution thereof in some manner, he
             shall execute bonds, mortgages, and other contracts in
             behalf of the corporation, and shall cause the seal to be
             affixed to any instrument requiring it and when so
             affixed the seal shall be attested by the signature of
             the secretary or treasurer or an assistant secretary or
             assistant treasurer.

         Section 5. VICE-PRESIDENT.

             Each vice-president shall have such powers and shall
             perform such duties as shall be assigned to him by the
             directors.

         Section 6. TREASURER.

             The treasurer shall have the custody of the corporate
             funds and securities and shall keep full and accurate
             account of receipts and disbursements in books belonging
             to the corporation.  He shall deposit all moneys and
             other valuables in the name and to the credit of the
             corporation in such depositories as may be designated by
             the Board of Directors.

             The treasurer shall disburse the funds of the corporation
             as may be ordered by the Board of Directors, or the
             president, taking proper vouchers for such disbursements.
             He shall render to the president and Board of Directors
             at the regular meetings of the Board of Directors, or
             whenever they may request it, an account of all his
             transactions as treasurer and of the financial condition
             of the corporation.  If required by the Board of
             Directors, he shall give the corporation a bond for the
             faithful discharge of his duties in such amount and with
             such surety as the Board shall prescribe.

         Section 7. SECRETARY.

             The secretary shall give, or cause to be given, notice of
             all meetings of members and directors, and all other
             notices required by law or by these Bylaws, and in case
             of his absence, or refusal or neglect to do so, any such
             notice may be given by any other person so directed by
             the president, or by the directors, or members, upon
             whose requisition the meeting is called as provided by
             these Bylaws.  He shall record all the proceedings of the
     FidoNews 6-47                Page 17                  20 Nov 1989


             meetings of the corporation and of directors in a book to
             be kept for that purpose, and shall affix the seal to all
             instruments requiring it, when authorized by the
             directors or the president, and attest the same.

         Section 8. INTERNATIONAL COORDINATOR.

             The Board of Directors shall elect an International
             Coordinator to serve as the head of the nodelist
             administrative structure.  The International Coordinator
             shall be responsible for maintaining the technical
             integrity of the network and for publishing the list of
             nodes which bears the trademark of this corporation, and
             for establishing new zones in that nodelist at the
             direction of a majority vote of the Board of Directors.

         Section 9. ASSISTANT TREASURERS AND ASSISTANT SECRETARIES.

             Assistant treasurers and assistant secretaries, if any,
             shall have such powers and shall perform such duties as
             shall be assigned to them, respectively, by the
             directors.

     ARTICLE V - MEMBERSHIP

         Section 1. MEMBERSHIP.

             Any person who is the system operator in good standing of
             a PUBLIC ACCESS NODE as listed in the FidoNet nodelist
             shall be a Regular member without making any application
             or paying any dues, and shall be entitled to one vote.

     ARTICLE VI - PROHIBITION OF DIVIDENDS.

         Section 1. PROHIBITION OF DIVIDENDS.

             No part of the net earnings of the corporation shall
             inure to the benefit of, or be distributable to, as
             dividends or in any other manner, its members, directors,
             officers or other private persons, except that the
             corporation shall be authorized and empowered to pay
             reasonable compensation for services rendered and to make
             payments and distributions in furtherance of the purposes
             set forth in the Articles of Association.

             Further, upon the dissolution of the corporation, the
             Board of Directors shall, after paying or making
             provision for the payment of all of the liabilities of
             the corporation, dispose of all of the assets of the
             corporation exclusively for charitable, education,
             religious, or scientific purposes as shall at the time
     FidoNews 6-47                Page 18                  20 Nov 1989


             qualify as an exempt organization or organizations under
             Section 501(c)(3) of the Internal Revenue Code of 1954
             (or the corresponding provisions of any future United
             States Law) as the Board of Directors shall determine.
             Any such assets not so disposed of shall be disposed of
             by the Court of Common Pleas of the County in which the
             principal office of the corporation is then located,
             exclusively for such purposes or to such organization or
             organizations, as said Court shall determine, which are
             organized and operated exclusively for such purposes.

     ARTICLE VII - CORPORATE SEAL.

         Section 1. SEAL.

             The corporate seal shall be circular in form and shall
             contain the name of the corporation, the year of its
             creation and the words "CORPORATE SEAL OF THE
             INTERNATIONAL FIDONET ASSOCIATION.  " Said seal may be
             used by causing it or a facsimile thereof to be impressed
             or affixed or otherwise reproduced.

     ARTICLE VIII - FISCAL YEAR

         Section 1. FISCAL YEAR.

             The fiscal year of the corporation shall be determined by
             resolution of the Board of Directors.

     ARTICLE IX - EXECUTION OF CORPORATION INSTRUMENTS.

         Section 1. INSTRUMENTS.

             All checks, drafts, or other orders for the payment of
             money, notes or other evidences of indebtedness issued in
             the name of the corporation shall be signed by officer or
             officers, agent or agents of the corporation, and in such
             manner as shall be determined from time to time by
             resolution of the Board of Directors.

     ARTICLE X - NOTICE AND WAIVER OF NOTICE.

         Section 1. NOTICE.

             Whenever any notice is required by these Bylaws to be
             given, personal notice is not meant unless expressly
             stated, and any notice so required shall be deemed to be
             sufficient if given by depositing the same in the mail,
             postage prepaid, addressed to the person entitled thereto
             at his address as it appears on the records of the
             corporation, or by the sending of electronic mail in the
     FidoNews 6-47                Page 19                  20 Nov 1989


             same fashion, or by the posting of such notice in the
             newsletter of the corporation.  Such notice shall be
             deemed to have been given on the day of such mailing or
             publishing of said notice.  Members not entitled to vote
             shall not be entitled to receive notice of any meetings,
             except as otherwise provided by statute.

         Section 2. WAIVER OF NOTICE.

             Whenever any notice whatever is required to be given
             under the provisions of any law, or under the provisions
             of the Certificate of Incorporation of the corporation or
             these Bylaws, a waiver thereof in writing signed by the
             person or persons entitled to said notice, whether before
             or after the time stated therein, shall be deemed proper
             notice.

     ARTICLE XI - AMENDMENTS.

         Section 1. AMENDMENTS.

      |      These Bylaws may be altered and repealed and Bylaws may
      |      be made at any annual meeting of the members or any
      |      special meeting thereof if notice thereof is contained in
      |      the notice of such special meeting, by the affirmative
      |      vote of a majority of the members entitled to vote
      |      thereat.

     ARTICLE XII - LOCAL ORGANIZATIONS.

         Section 1. LOCAL ORGANIZATIONS

             The International Fidonet Association recognizes the need
             for and encourages the formation of locally based
             independent organizations for the furtherance of
             electronic communications at the Zone, Region, and Net
             levels.

     -----------------------------------------------------------------
     FidoNews 6-47                Page 20                  20 Nov 1989


     John Roberts
     FidoNet 1:385/49

     The following information is provided for those who have
     expressed an interest in developing proposals for appendices to
     the IFNA/FidoNet Policy document.  It's a bit rough, but should
     be close enough to get you in the ballpark so that your proposals
     will conform to the same format as others under development.

     Each proposal should be generated in straight ASCII text, each
     line terminated with a carriage return/line feed sequence, and
     the file terminated with the ^Z end of file marker, left margin
     set to column 1 and the right margin set to column 65, normally
     spaced (right margin *not* justified).

     The proposal should begin with a blank line, followed by a
     centered title block in the same format as the following sample:

                      Appendix xxx (Proposed)(Draft)
                                   to
                           IFNA/FidoNet Policy

                             January 1, 1980

                        GENERAL SUBJECT OF APPENDIX
                        ===========================

     The "xxx" in the first line will be the proposal identifier.
     Either use "xxx" here or leave blank, as these sequence numbers
     will be assigned by the chairman or secretary of the Bylaws and
     Rules committee upon receipt of your proposal.  The word
     "(Proposed)" should always appear.  The word "(Draft)" should
     appear if your proposal is not in its final form and may be
     followed by a version number, i.e., "(Draft v1.03)" or similar.

     The date shown should be the date of submission of your proposal.

     The subject line should be very brief, yet descriptive enough to
     reflect the primary issue your proposal addresses, and be
     followed by one blank line.

     The remainder of the document should continue in standard outline
     format with four-space indentation as used in the basic Policy
     document:

     I. FIRST MAJOR HEADING/PARAGRAPH

         A. First degree subheading/paragraph

             1. Second degree subheading/subparagraph

     FidoNews 6-47                Page 21                  20 Nov 1989


                 a. Third degree subheading/subparagraph

                     i. Fourth degree subheading/subparagraph

     Each heading/paragraph and subheading/paragraph should be
     separated by a single blank line.

     As a minimum, each proposed appendix should contain the following
     sections:

     I. PURPOSE

         This section should consist of a brief synopsis of your
         proposal.

     II. GENERAL

         This section should contain any general statements or other
         information that you feel are necessary to understanding your
         proposal.

     III. DEFINITIONS

         This section would contain definitions of any unusual terms
         that may be necessary for the understanding of your proposal.
         If only common terms are used, this section is not required.

     Section IV (or III if definitions are not necessary) would then
     be the start of the "meat" of your proposal, and would continue
     as long as necessary.  Keep in mind that your proposal should
     primarily address policy - responsibilities and requirements -
     rather than procedures to meet those responsibilities and
     requirements.

     The last numbered section of your proposal should be:

     (?). RATIFICATION

         This section would detail any special requirements required
         for implementation of the appendix should it be ratified,
         such as providing for the removal of the "Proposed" and
         "Draft" designations in the title block, phase-in periods and
         procedures, and possibly even removal of the "RATIFICATION"
         section itself after the appendix is ratified.

     The proposal should end with a trailer, with information similar
     to the header, in a format similar to:

            --------------------------------------------------
            IFNA/FidoNet Policy Appendix xxx (Proposed)(Draft)
              Developed by:  IFNA Bylaws and Rules Committee
     FidoNews 6-47                Page 22                  20 Nov 1989


                Drafted by:  John Roberts, FidoNet 1:385/49
                              Ratified (date)
                                   *end*

     Here again, the "xxx" would be the sequence number as assigned by
     the committee, and a draft "version" may be included if desired.
     "Developed by" could be "The Policy5.DEM working group", "The
     Zone 1 FidoNet RC's", etc, and "Drafted by" would be the
     individual responsible for presenting and maintaining the current
     version of the proposal prior to ratification.  The ratification
     date would be filled in by the committee should the proposal be
     ratified.

     As I said when I started out, this description is a bit rough -
     but I hope it should suffice to get anyone wanting to present and
     Appendix proposal going in the right direction.

     -----------------------------------------------------------------
     FidoNews 6-47                Page 23                  20 Nov 1989


     IFNA Bylaws and Rules Committee
     Jason Steck, 1:104/424, Member
     Phil Buonomo, 1:107/583, Member
     John Roberts, 1:385/49, Chairman


              IFNA/FidoNet Policy v5 (Proposed)(Draft v0.21)
                              prepared by the
                        Bylaws and Rules Committee
                                  of the
                     International FidoNet Association

                             November 18, 1989

     I. PURPOSE

         This document prescribes the responsibilities of any given
         system to be listed in the IFNA nodelist, the
         responsibilities of coordinators at various levels within the
         network, and the requirements for ratification and future
         modification of this document and/or its appendices.

         There shall be no other mandatory requirements for FidoNet
         membership above and beyond those directly stipulated or for
         which specific allowance is made within this document and/or
         its appendices.

     II. GENERAL

         FidoNet is dedicated to the exchange of information among the
         general public, and as such no one may be denied a node
         address based on race, creed, color, sex, sexual orientation,
         philosophy, software used, or affiliation with any other
         network.

         The usage of the personal pronouns "he" and "his" within this
         document shall be considered to be gender neutral and equally
         applicable to members of either sex.

         This document and its Appendices are prepared in English, and
         translation to other languages is expressly encouraged.  This
         is not to be construed as a direct endorsement of any given
         language as the official language of FidoNet.

     III. DEFINITIONS

         NODE:  The smallest subdivision of the network, defined as a
         single system operating within the network.  The
         responsibilities of a node are defined in the section NODE
         RESPONSIBILITIES within this document.

     FidoNews 6-47                Page 24                  20 Nov 1989


         NET:  A group of nodes, usually established within a specific
         geographic area, associated with each other by choice for
         administrative purposes and to facilitate mail transfer.

         REGION:  A group of nets and nodes that are not part of any
         net, usually in a specific geographic area, associated with
         each other for administrative purposes.

         ZONE:  A group of regions, usually in a specific geographic
         area, associated with each other for administrative purposes
         and to facilitate mail transfer.

         SYSOP:  For the purpose of this document, the single
         individual with primary responsibility for the operation of
         any given node or nodes.

         COORDINATOR:  A sysop at any given level who is designated
         certain technical responsibilities commensurate to the
         administration of the level of which he is a part.  Specific
         responsibilities of coordinators at any given level are
         defined in the section COORDINATOR RESPONSIBILITIES within
         this document.

         NODELIST:  The listing of node information that reflects
         current addressing, routing, capability, compatibility, and
         other technical information pertaining to nodes within the
         network.  The nodelist is essentially the "phone book" that
         nodes use to communicate with each other.

         ZONE MAIL HOUR:  A one hour period of time set aside for and
         dedicated to the processing of mail within a given zone, as
         designated by the coordinator of that zone.  Specifically, a
         node must operate in a "mail only" mode, performing no other
         task other than the sending and receipt of mail during such a
         designated hour.

         LOCAL MAIL SCHEDULE(S):  Additional mail period(s) as may be
         necessary within any given local net for the processing and
         distribution of mail within that net, as designated by the
         coordinator of that net.

     IV. NODE RESPONSIBILITIES

         To obtain and retain a listing in the nodelist, the sysop of
         any NODE shall be responsible for:

      |  A.  Compliance with the minimum FidoNet mail session
      |      standards as defined by the FidoNet Technical Standards
      |      Committee and approved by the IFNA Board of Directors so
      |      as to be able to send and receive mail within the
      |      network.

     FidoNews 6-47                Page 25                  20 Nov 1989


         B.  Adherence to mail hours and schedules, specifically that
             his node must properly observe zone mail hour as defined
             by the coordinator of the zone of which the node is a
             part, and any applicable mandatory local mail schedules
             as defined by any local policy or other supplement to
             this document.

         C.  Utilizing the most current nodelist available for the
             operation of his node.

     V. COORDINATOR RESPONSIBILITIES

         A.  The coordinator of a NET shall be responsible for:

             1.  Gathering, maintaining, and compiling the most
                 current information as reasonably possible concerning
                 the status of nodes within the net of which he is a
                 part, and forwarding such information to the
                 coordinator of the region of which such net is a part
                 in a timely manner to ensure its inclusion in the
                 nodelist.

             2.  The assignment of node addresses to individual nodes
                 within the net of which he is a part.

             3.  Ensuring the distribution of weekly nodelist updates
                 to the members of the net of which he is a part.

             4.  Ensuring the distribution of weekly issues of the
                 network newsletter to the members of the net of which
                 he is a part.

             5.  Forwarding of messages which are addressed to nodes
                 within the net of which he is a part in a timely
                 manner.

             6.  The establishment of Local Mail Schedules for all
                 nodes within the net of which he is a part, should
                 such be required for the efficient operation of the
                 net of which he is a part or the network as a whole.

             7.  Ensuring compliance with the technical provisions of
                 this document on the part of the nodes of the net of
                 which he is a part, including taking such
                 administrative action as may be necessary to correct
                 non-compliance.

         B.  The coordinator of a REGION shall be responsible for:

             1.  Gathering, maintaining, and compiling the most
                 current information as reasonably possible concerning
     FidoNews 6-47                Page 26                  20 Nov 1989


                 the status of nets and nodes that are not part of a
                 net within the region of which he is a part, and
                 forwarding such information to the coordinator of the
                 zone of which such region is a part in a timely
                 manner to ensure its inclusion in the nodelist.

             2.  The assignment of node addresses to nodes that are
                 not part of a net and the assignment of net numbers
                 from a pool provided by the zone coordinator of the
                 zone of which his region is a part to groups of nodes
                 that desire to form a net within the region of which
                 he is a part.

             3.  Ensuring the distribution of weekly nodelist updates
                 to coordinators of nets and nodes that are not part
                 of a net within the region of which he is a part.

             4.  Ensuring the distribution of weekly issues of the
                 network newsletter to the coordinators of nets and
                 nodes that are not part of a net within the region of
                 which he is a part.

             5.  Ensuring compliance with the technical provisions of
                 this document on the part of the net coordinators and
                 nodes that are not part of a net within the region of
                 which he is a part, including taking such
                 administrative action as may be necessary to correct
                 non-compliance.

         C.  The coordinator of a ZONE shall be responsible for:

             1.  Gathering, maintaining, and compiling the most
                 current information as reasonably possible concerning
                 the status of regions and listings for administrative
                 nodes within the zone of which he is a part, and
                 forwarding such information to the international
                 coordinator in a timely manner to ensure its
                 inclusion in the nodelist.

             2.  The assignment of region numbers to regions within
                 the zone of which he is a part.

             3.  Ensuring the distribution of weekly nodelist updates
                 to coordinators of regions within the zone of which
                 he is a part.

             4.  Ensuring the distribution of weekly issues of the
                 network newsletter to the coordinators of regions
                 within the zone of which he is a part.

             5.  Ensuring the establishment and operation of zonegate
     FidoNews 6-47                Page 27                  20 Nov 1989


                 systems within the zone of which he is a part as
                 necessary to facilitate the transfer of mail to and
                 from other zones.

             6.  Designating a Zone Mail Hour for all nodes within the
                 zone of which he is a part.

             7.  Assignment of a pool of net numbers for the use of
                 each regional coordinator within the zone of which he
                 is a part.

             8.  Ensuring compliance with the technical provisions of
                 this document on the part of the regional
                 coordinators within the zone of which he is a part,
                 including taking such administrative action as may be
                 necessary to correct non-compliance.

         D.  The INTERNATIONAL coordinator shall be responsible for:

             1.  Gathering, maintaining, and compiling the most
                 current information as reasonably possible concerning
                 the status of all zones of the network for inclusion
                 in the nodelist.

             2.  The assignment of zone numbers upon direction of the
                 IFNA Board of Directors.

             3.  Ensuring the distribution of weekly nodelist updates
                 to coordinators of all zones.

             4.  Ensuring the distribution of weekly issues of the
                 network newsletter to the coordinators of all zones.

             5.  Ensuring compliance with the technical provisions of
                 this document on the part of the zone coordinators,
                 including taking such administrative action as may be
                 necessary to correct non-compliance.

         [Note:  In the above sections, a coordinator at any level is
                 required to make sure that nodes and/or other
                 coordinators receive the named documents.  This
                 specifically includes the provision that he deliver
                 them directly, should that be necessary for such
                 assurance.]

     VI. RATIFICATION

         This document will be considered to be ratified and in effect
         upon passage in a general or special election by a simple
         majority of votes received from those eligible IFNA members
         voting in such election conducted by the IFNA Nominations and
     FidoNews 6-47                Page 28                  20 Nov 1989


         Elections Committee, in accordance with current standard
         procedures for the conduct of such elections.

      |  This document shall remain in effect as written until
      |  modified or replaced through the procedures designated in the
      |  MODIFICATION section of this document.

     VII. MODIFICATION

         Any proposed modification to this document will be subject to
         the procedures designated in the RATIFICATION section of this
         document before becoming effective.  Any proposed
         modification must be submitted in final form, either written
         or electronically transmitted, to the IFNA Bylaws and Rules
         committee.  Proposals will be considered valid as a result of
         any of the following:

         A.  At the request of at least 25% of the coordinators of the
             network.

         B.  Upon petition from a minimum of 10% of those IFNA members
             who would be eligible to vote in an election to ratify
             such modifications, as designated in the RATIFICATION
             section of this document.

         C.  Upon the recommendation of and sponsorship by a member of
             the IFNA Bylaws and Rules committee.

         D.  Upon the recommendation of and sponsorship by a member of
             the IFNA Board of Directors.

     VIII. EMERGENCY CLAUSE

         Should any portion of this document come into conflict with
         federal, state, or local law or the equivalent thereof, that
         portion shall immediately be considered to have been revoked
         within the geographic area wherein it is in conflict, and the
         coordinator with primary responsibility for that area shall
         immediately bring the situation to the attention of the IFNA
         Bylaws and Rules committee and Board of Directors with
         sufficient detail and documentation to allow work to begin on
         a proposal for permanent modification.

     IX. SUPPLEMENTS

         This document may be supplemented by local policy at the
         Zone, Region, or Net level, such supplement being considered
         to be a legitimate extension of this document at the level
         and for the area to which such supplement pertains, in
         accordance with the following procedures:

     FidoNews 6-47                Page 29                  20 Nov 1989


      |  A.  Any such supplement or any part thereof may not rescind
      |      or relax any responsibility for compliance with any
      |      provision of this document without prior review by the
      |      IFNA Bylaws and Rules committee and approval of the IFNA
      |      Board of Directors.

         B.  Any such supplement or any part thereof may only be
             considered to be ratified and in effect upon passage in a
             general or special election by a simple majority of votes
             received from those eligible IFNA members who are part of
             the area subject to coverage under such supplement voting
             in an election conducted in accordance with current
             standard procedures developed by the IFNA Nominations and
             Elections Committee.  Should ratification fail, the most
             recent supplement previously in effect shall be
             considered to remain in effect.

         C.  Any proposed modification to such supplement or any part
             thereof will be subject to the same ratification
             requirements as the supplement itself before becoming
             effective.

         D.  Proposals for the creation, modification, or removal of
             any such supplement or any part thereof will be
             considered valid as a result of any of the following:

             1.  As a proposal by the coordinator of the level for
                 which such supplement would be applicable.

             2.  Upon petition from a minimum of 25% of those sysops
                 of nodes which are part of the level for which such
                 supplement would be applicable.

     X. APPENDICES

         All current appendices to this document shall be published
         separately, and are included by reference as a legitimate
         part of this document by inclusion in the INDEX OF APPENDICES
         at the end of this section of this document with the
         ratification date shown.  All proposals for appendices shall
         be subject to the same ratification and modification
         procedures as required for this document.

                            INDEX OF APPENDICES
                            ===================

         APPENDIX                 SUBJECT                   DATED
         --------  -------------------------------------  ---------
         --------  -------------------------------------  ---------

             IFNA/FidoNet Policy version 5.0 (Proposed)(Draft)
     FidoNews 6-47                Page 30                  20 Nov 1989


                              Ratified (date)
                                   *end*

     -----------------------------------------------------------------
     FidoNews 6-47                Page 31                  20 Nov 1989


     Pam Murray
     Camelot-BBS  FidoNet 1:340/12
     Victoria, BC   CANADA



     A VISIT FROM MY DAISY MAID

     'Twas four in the morning, when all through the house,
     Not a creature was stirring, not even a mouse.
     The pictures weren't hung in the front hall with care,
     And We knew that our Daisy Maid soon would be there.

     The children weren't nestled all snug in their beds,
     For visions of the vacuum roared loud in their heads.
     And Mamma in her kercheif, and I in my cap,
     Had just been awoken from our short August nap,

     When down in the kitchen, there arose such a clatter,
     I sprang from the bed to see what was the matter.
     Downstairs to the kitchen, I flew like a flash,
     Flung open the door and heard a loud *CRASH!*

     And then, where the worst of the blue molds did grow,
     My flahlight revealed some black gunk below..
     When what to my half-open eyes should appear,
     But a bag full of cleaners and a maid who was queer.

     She cackled and hunched as she scrubbed 'tween the bricks,
     I knew in a moment she MUST be a witch.
     More rapid than eagles, her cleaners they came,
     As she whistled and shouted and called them by name;

     "Now Freedom! Now Tilex! Now, Windex and Lysol!
     On Comet! On Old Dutch! On endust and Pine Sol!
     From the leaves on the porch to the spots on the wall!
     Now scrub away! Scrub away! Clean away all!"

     As dead plants that before the wild leaf-blower fly,
     When they met with an obstacle, mount to the sky.
     So up the the housetop, the cleaners they flew,
     With a vacuum, a mop, and my Daisy Maid too!

     And then in a twinkling, I heard on the roof,
     The washing and scrubbing of my maid - what a goof!
     As I drew in my head, and was turning around,
     Down the chimney my Daisy Maid came with a bound!

     She was dressed all in mauve, from her head to her foot,
     And her clothes (from the 60's) were covered with soot!
     A bundle or rags she had flung on her back..
     She looked like a bag lady opening her sack!

     FidoNews 6-47                Page 32                  20 Nov 1989


     Her eyes did not twinkle, and so I was wary..
     Her arms her like hoses, her legs were all hairy!
     Her small little mouth was drawn up like a bow,
     And the beard on her chin was as white as the snow!

     The stump of a pipe she held tight in her teeth,
     And the smoke! It encircled her head like a wreath!
     She had a fat face, and a six storey belly,
     That shook when she cleaned like a bowl of old jelly!

     She was ugly and fat, a right scary old elf,
     And I screamed when I saw her, inspite of myself!
     A wink of her eye, and a twist of her head,
     Soon gave me to know I had PLENTY to dread.

     She spoke not a word, but went right to her work,
     And scrubbed as if mocking a cleanliness jerk!
     And laying a finger by the wart on her nose,
     And nodding her head, up the vacuum she rose!

     The cleaners, they broke a large hole in my roof,
     And soon they were followed by that crazy maid goof!
     But I heard her exclaim as she flew out of sight...
     "Happy Cleaning to All!!! I'll be back Thursday night!"

     PAM!
     ----

     -----------------------------------------------------------------
     FidoNews 6-47                Page 33                  20 Nov 1989


     =================================================================
                              LATEST VERSIONS
     =================================================================

                          Latest Software Versions

                               MS-DOS Systems
                               --------------

                           Bulletin Board Software
     Name        Version    Name        Version    Name       Version

     Fido            12q+*  Phoenix         1.3    TBBS           2.1
     Lynx           1.30    QuickBBS       2.04    TComm/TCommNet 3.4
     Kitten         2.16*   RBBS          17.2B*   TPBoard        6.0*
     Opus          1.03b+   RBBSmail       17.2*   Wildcat!     2.00P


     Network                Node List              Other
     Mailers     Version    Utilities   Version    Utilities  Version

     BinkleyTerm    2.30    EditNL         4.00    ARC           6.02
     D'Bridge       1.21    MakeNL         2.20    ARCA05        2.01*
     Dutchie       2.90C    ParseList      1.30    ARCmail        2.0
     FrontDoor       2.0    Prune          1.40    ConfMail      4.00
     PRENM          1.47    SysNL          2.65*   EMM           2.02
     SEAdog        4.51b    XlatList       2.90    GROUP         2.16
                            XlaxDiff       2.32    GUS          1.20M*
                            XlaxNode       2.32    LHARC         1.13
                                                   MSG            4.0*
                                                   MSGED         1.99
                                                   PK[UN]ZIP     1.01
                                                   QM             1.0
                                                   QSORT         4.03
                                                   StarLink      1.01*
                                                   TCOMMail       2.2
                                                   TMail         1.12*
                                                   TPBNetEd       3.2
                                                   UFGATE        1.03
                                                   XRS            3.0
                                                   ZmailQ        1.09

                                 Macintosh
                                 ---------

     Bulletin Board Software   Network Mailers     Other Utilities

     Name            Version   Name      Version   Name       Version

     Red Ryder Host   v2.1b3   Macpoint     0.91*  MacArc        0.04
     Mansion            7.12   Tabby         2.1   ArcMac         1.3
     WWIV (Mac)          3.0                       StuffIt       1.51
     FidoNews 6-47                Page 34                  20 Nov 1989


                                                   TImport      1.331
                                                   TExport       1.32
                                                   Timestamp      1.6
                                                   Tset           1.3
                                                   Timestart      1.1
                                                   Tally          1.1
                                                   Mehitabel      1.2
                                                   Archie        1.60
                                                   Jennifer   0.25b2g
                                                   Numberizer    1.5c
                                                   MessageEdit    1.0
                                                   Mantissa       1.0
                                                   PreStamp      2.01
                                                   R.PreStamp    2.01
                                                   Saphire       2.1t
                                                   Epistle II    1.01
                                                   Import        2.52
                                                   Export        2.54
                                                   Sundial        2.1
                                                   AreaFix        1.1
                                                   Probe        0.052
                                                   Terminator     1.1
                                                   TMM           4.0b
                                                   UNZIP         1.01*
                                   Amiga
                                   -----

     Bulletin Board Software   Network Mailers     Other Utilities

     Name            Version   Name      Version   Name       Version

     Paragon            1.00+* BinkleyTerm  1.00   AmigArc       0.23
                               TrapDoor     1.11*  booz          1.01
                               WelMat       0.21*  ConfMail      1.10*
                                                   ChameleonEdit 0.10
                                                   Lharc         0.50
                                                   ParseLst      1.30
                                                   PkAX          1.00
                                                   RMB           1.30
                                                   UNzip         0.86
                                                   Zoo           2.00


                                    Atari ST
                                    --------

     Bulletin Board Software   Network Mailer      Other Utilities

     Name            Version   Name      Version   Name       Version

     FIDO/FoReM Door    1.1*   BinkleyTerm 1.03g   ConfMail      1.00
     Pandora BBS        2.41c* The BOX     1.10*   ParseList     1.30
     QuickBBS/ST        0.40*                      ARC           5.21
     GS Point           0.61                       TurboArc       1.1
     FidoNews 6-47                Page 35                  20 Nov 1989


                                                   LHARC         0.40
                                                   PKUNZIP       1.00
                                                   MSGED        1.96S
                                                   SRENUM         6.2
                                                   OMMM          1.40*
                                                   Timestop      1.00


     + Netmail capable (does not require additional mailer software)
     * Recently changed

     Utility authors:  Please help  keep  this  list  up  to  date  by
     reporting  new  versions  to 1:1/1.  It is not our intent to list
     all utilities here, only those which verge on necessity.

     -----------------------------------------------------------------
     FidoNews 6-47                Page 36                  20 Nov 1989


     =================================================================
                                  NOTICES
     =================================================================

                  Problems With New ChicagoLand Area Code


     Effective November 11, the telephone area code for Chicago
     suburbs changed to 708.  The change was reflected in the nodelist
     update which was distributed November 10.  Although the cutover
     has gone smoothly in the Chicago area, there are certain areas
     outside of Chicago which are unable to use the new 708 code.
     Problems have been reported from California and Texas.

     If you are having problems reaching suburban Chicago numbers, try
     a temporary override to the old 312- number or host routing (the
     NC for net 115 remains in area-code 312).
     -----------------------------------------------------------------

                          The Interrupt Stack


     23 Nov 1989
        26th Anniversary of "Dr. Who" - and still going strong

      1 Dec 1989
        Close of local balloting in IFNA plebiscite

      3 Dec 1989
        The Hague, Holland changes to a seven-digit telephone number.
        You have to put a THREE (3) before the old number.
                     e.g. (0)70-111111 changes to (0)70-3111111

      4 Dec 1989
        Local coordinators post final IFNA vote details

     11 Dec 1989
        Deadline for local IFNA vote tally challenges

     15 Dec 1989
        Network Coordinators report votes in IFNA plebiscite to
        Regional Coordinators

     18 Dec 1989
        Regional Coordinators report votes in IFNA plebiscite
        to Zone Coordinators

     22 Dec 1989
        IFNA plebiscite results posted in NODELIST.356

     30 Dec 1989
     FidoNews 6-47                Page 37                  20 Nov 1989


        Telephone area codes (5, 3 and 0) are abolished in Hong Kong

      1 Feb 1990
        Deadline for IFNA Policy and Bylaws election

      5 Jun 1990
        David Dodell's 33rd Birthday

      5 Oct 1990
        21st Anniversary of "Monty Python's Flying Circus"


     If you have something which you would like to see on this
     calendar, please send a message to FidoNet node 1:1/1.

     -----------------------------------------------------------------

     FidoNews 6-47                Page 38                  20 Nov 1989


             OFFICERS OF THE INTERNATIONAL FIDONET ASSOCIATION

     Thom Henderson 1:107/528  Chairman of the Board
     Les Kooyman    1:204/501  President
     Fabian Gordon  1:107/323  Vice President
     Bill Bolton    3:3/0      Vice President-Technical Coordinator
     Kris Veitch    1:147/30   Secretary
     Kris Veitch    1:147/30   Treasurer


                      IFNA COMMITTEE AND BOARD CHAIRS

     Administration and Finance   *
     By-laws and Rules            John Roberts     1:385/49
     Executive Committee (Pres)   Les Kooyman      1:204/501
     International Affairs        *
     Membership Services          Jim Vaughan      1:226/300
     Nominations and Elections    Steve Bonine     1:1/0
     Public Affairs               David Drexler    1:147/30.20
     Publications                 Irene Henderson  1:107/9
     Technical Standards          Rick Moore       1:115/333
     Ethics                       *
     Security and Privacy         *
     Grievances                   *

         * Position in abeyance pending reorganization


                          IFNA BOARD OF DIRECTORS

        DIVISION                               AT-LARGE
     10 Courtney Harris  1:102/732   Don Daniels      1:107/210
     11 John Rafuse      1:12/700    Phil Buonomo     1:107/583
     12 Bill Bolton      3:711/403   Mark Hawthorne   1:107/238
     13 Fabian Gordon    1:107/323   Tom Jennings     1:125/111
     14 Ken Kaplan       1:100/22    Irene Henderson  1:107/509
     15 Kevin McNeil     1:128/45    Steve Jordan     1:206/2871
     16 Ivan Schaffel    1:141/390   Robert Rudolph   1:261/628
     17 Kathi Crockett   1:134/30    Dave Melnik      1:107/233
     18 Andrew Adler     1:135/47    Jim Hruby        1:107/536
     19 Kris Veitch      1:147/30    Burt Juda        1:107/528
      2 Henk Wevers      2:500/1     Karl Schinke     1:107/516
      3 Matt Whelan      3:54/99     John Roberts     1:147/14

     -----------------------------------------------------------------
     FidoNews 6-47                Page 39                  20 Nov 1989


                                      __
                 The World's First   /  \
                    BBS Network     /|oo \
                    * FidoNet *    (_|  /_)
                                    _`@/_ \    _
                                   |     | \   \\
                                   | (*) |  \   ))
                      ______       |__U__| /  \//
                     / Fido \       _//|| _\   /
                    (________)     (_/(_|(____/ (tm)

            Membership for the International FidoNet Association

     Membership in IFNA is open to any individual or organization that
     pays  a  specified  annual   membership  fee.   IFNA  serves  the
     international  FidoNet-compatible  electronic  mail  community to
     increase worldwide communications.

     Member Name _______________________________  Date _______________
     Address _________________________________________________________
     City ____________________________________________________________
     State ________________________________  Zip _____________________
     Country _________________________________________________________
     Home Phone (Voice) ______________________________________________
     Work Phone (Voice) ______________________________________________

     Zone:Net/Node Number ____________________________________________
     BBS Name ________________________________________________________
     BBS Phone Number ________________________________________________
     Baud Rates Supported ____________________________________________
     Board Restrictions ______________________________________________

     Your Special Interests __________________________________________
     _________________________________________________________________
     _________________________________________________________________
     In what areas would you be willing to help in FidoNet? __________
     _________________________________________________________________
     _________________________________________________________________
     Send this membership form and a check or money order for $25 in
     US Funds to:
                   International FidoNet Association
                   PO Box 41143
                   St Louis, Missouri 63141
                   USA

     Thank you for your membership!  Your participation will help to
     insure the future of FidoNet.

     Please NOTE that IFNA is a general not-for-profit organization
     and Articles of Association and By-Laws were adopted by the
     membership in January 1987.  The second elected Board of Directors
     was filled in August 1988.  The IFNA Echomail Conference has been
     established on FidoNet to assist the Board.  We welcome your
     input to this Conference.

     FidoNews 6-47                Page 40                  20 Nov 1989


     -----------------------------------------------------------------
