

    WinNet NETWORK INFORMATION AND POLICIES........July 28, 1990
                        ------------

                        WHAT IS IT?

WinNet is a network of participating Fido-compatible BBS'es set
up to distribute shareware and public domain files written for
use with Microsoft's WINDOWS operating environment.  It was
started in July, 1990 to serve the same purpose for Windows users
that SDS, SDNet/Works!, DVNET and similar "file echo" networks
serve for their respective audiences.  With the release of
Windows 3.0 in mid-1990, Microsoft created a DOS-based graphical
environment that can be taken very seriously, and whose use is
certain to grow in offices and homes across the country.  We
anticipate a steady increase in the number of PD and shareware
authors writing utilities and applications for Windows, and
believe that a quick and organized method of distribution for
Windows-related files will help both users and authors.  WinNet
is not affiliated in any way with Microsoft Corporation.

                       --------------
                       THE BASIC RULES

WinNet will consist of a controlled distribution network which a
sysop "joins" by making application and being added to the
distribution list.  Initially, such applications will be made to
Larry Mundy at Fidonet address 1:130/38.

As the network has grown, we have acquired regional hubs who will 
distribute network files in their region.  If you received this file
as an archive containing WINNET.MAP, you will have an indication of
possible feeds closer to you; feel free to contact a nearby node to
ask about a hookup, but please still copy your info to 130/38.

If you are interested in being a hub, file-request HUBINFO.TXT 
from 130/38.

Membership requirements will be honed as we progress, but will
initially include:

     1) The applicant will run a Fidonet-compatible BBS system
capable of using TICK.  The system must support file
requests and must have been a member of their "regular" BBS
network for at least one year.  The system must also be capable
of receiving and sending echo messages in standard, Fido-
compatible .MSG format.

     2) Membership in WinNet is not open to BBS'es which charge
users a "subscription fee" for access to the WinNet files.  It is
acceptable that a BBS require answering a questionnaire, accepting 
a return call from a "callback verifier," or similar user check for 
access, so long as a user who complies with the BBS membership 
requirements is not thereafter charged for continuing access to the 
WinNet files section.  The idea is to provide fast and free access to Windows-related software for users in the calling area.

     3) Member boards will carry and participate in a message
echo called WIN_SYS, which is a sysop-only echo for the
discussion of network- and software-related problems and
suggestions.  No user-level access will be allowed to this echo
area.  No "public" message echo will be associated with WinNet;
the WINDOWS echo in Fidonet (and similar forums in UseNet, on
CIS, etc.) are adequate for this purpose.  It is required,
however, that a WinNet member BBS carry at least one such public-
access echo accessible to all users who can access the WinNet
files area.

     4) Member boards should be aware that long-distance calls
may be necessary to access the files, if they are not available
from a local hub.  All applicants for regional HUB status will
incur long-distance charges.  WinNet will require that uplinks be
polled at least weekly, with a recommendation of at least twice a
week.  Any node not polling for two weeks, and not making
suitable alternate arrangements with its uplink, will be deleted
from the network.

     5) A list of files in the WinNet area of each board must be
updated at least weekly (we suggest nightly as part of the BBS
batch file maintenance) and downloadable by users from within the
WinNet files area.  This list must also be file-requestable by
any other system using the magic filename "WINFILES."

     6) Each system carrying WinNet files will place the
following disclaimer in a display or "dumpfile" so that it is
displayed to a user accessing the WinNet files area (this may be
done by adding it to the start of FILES.BBS or its equivalent,
placing it in a "Welcome" file or using "dumpfile" capabilities
if your BBS software has them):

          This BBS supports the WinNet files distribution 
          system for Microsoft Windows-specific files.  There
          is no warranty, express or implied, that any such
          file has been tested for safety or functionality.
          You use or run these files at your own risk!

Pretty simple, huh?  We are not trying to replace any other file-
echo network or established message echo; we are simply trying to
provide a dedicated files network for Windows-related files.  We
anticipate no restriction on "auto-Tic'ing" or other means of
further local-level distribution of the files, since the object
is to get wide distribution of files to Windows users.  However,
only nodes which have been granted member status in WinNet will
be identified as "WinNet Member" boards.  A list of member boards
will be distributed periodically, and must also be made available
for download in the WinNet files area.

We anticipate assigning a limited number of nodes, with the aim
of having few duplications within a given local calling area. 
In assigning nodes, consideration will be given to the size of
the potential user base in an area (i.e., population), modem
speeds, and so forth.  As the distribution is "fleshed out," we
will refine membership guidelines.

                        --------------- 
                        TECHNICAL STUFF

To ensure consistency across the system, files will initially be 
"hatched" from a single central point at 1:130/38, which is a 
system in the Dallas-Ft. Worth area.  These files will be put on 
"hold" for pickup by direct feeds.  Files will be hatched in ".TIC" 
format.

As regional hubs area added to the system, files may be hatched 
from them to 130/38 for automatic distribution, so if you volunteer
to become a hub and want to supply files, you will be expected
to do at least some rudimentary testing.  Freq HUBINFO.TXT from 130/38
for further details.

The central distribution point will be sending files using a US
Robotics Courier HST.  It is requested that applicants for
regional HUB status be HST-compatible.  Connections below the
regional HUB level will be a matter for the hub boards.

Session-level and TICK passwords will be required of all
participants.  An application to participate, netmailed to
1:130/38 (or to a probable local uplink and copied to 130/38 by 
netmail) should include suggested passwords for both.

The WIN_SYS echo will be distribued along with the files, and
will not be placed on the "backbone" no matter how large it may
get.  Upon applying for membership, a system operator should
configure his system to receive this echo (with appropriate
safeguards against regular user access) and should set up the
files area WINNET for use by TICK.  Confirmation of a
node assignment will be made in the WIN_SYS message echo, 
and if a system is not set up to receive it, it will be missed.

New Windows-related files for distribution are always welcomed,
but should NEVER be "hatched" to 130/38 except by HUBS.  They should 
arrive at 1:130/38 from other sources in one of the following ways:

     1) by direct mail, on disk from the author, addressed to:
          Larry Mundy
          3720 Chittam Lane
          Bedford, TX 76021 USA

     2) by file-attach, accompanied by a net message stating:
          a) a short description of the file
          b) a summary of how it was obtained by the person
             sending it (i.e., directly from the author, from 
             CIS, etc.); and
          c) a statement that the person sending it has tested it
             at least preliminarily and has found it to be
             functional/virus-free/etc.

Files compatible with Windows 3.0 and above will be preferred 
for distribution by WinNet.  There are a large number of PD and
Shareware files written for use with Windows 2.X; as these are 
rewritten for 3.0 compliance, the rewritten files will be preferred
for distribution, since the message 3.0 gives you when running an
"oldapp" is so darn irritating!

The PKZIP -av "security envelope" will be used for all files 
hatched into WinNet.  
                    --------------------------
                  APPLYING FOR A NODE ASSIGNMENT

As stated above, applications should initially be made to Larry
Mundy at 1:130/38 or a local uplink in WINNET.MAP, with a copy to 
130/38 in that instance, and must include the following information:

NAME:
MAILING ADDRESS:
HOME PHONE:
WORK PHONE:
BOARD NAME:
BOARD LOCATION (CITY, STATE, COUNTRY):
BOARD PHONE NUMBER:
FIDONET REGION:
NETWORK:
NETWORK ADDRESS:
MAILER SOFTWARE/VERSION:
BBS SOFTWARE/VERSION:
MODEM SPEED/BRAND/MODEL:
SESSION-LEVEL PASSWORD:
TICK/FLEA PASSWORD:
SUGGESTED LOCAL UPLINK, IF ANY:
WOULD YOU VOLUNTEER TO BE A HUB IN YOUR REGION?

This information will be used only in connection with the
legitimate purposes of WinNet, including divulging such
information to any uplinks in the distribution chain.

After applying for an assignment, you should set up to receive both
the WIN_SYS echo, however this is done using your software, and the 
WinNet files by creating a directory and appropriate configuration
and support files.  For example, using TICK, you would add the following
lines to the TIC.CFG file for a direct link to 130/38:

          AREA c:\[directory name] WINNET
               1:130/38 * &

For connection to some other system, just substitute the appropriate
sending node.  Hubs of course will not use the "*" and "&" flags, but
will list subnodes with the appropriate (C or H) tag.

We hope this is a successful enterprise, and we are willing to
invest a considerable amount of time and effort to make it
succeed.  We welcome questions or suggestions about the
administration of the network, file sourcing, and so forth either
in the WIN_SYS echo from member boards, or by netmail to:

Larry Mundy, Spare Parts, 817-540-3527 (1:130/38).
                               _____

                            CATCHING UP

As new nodes join, most of you will want to "catch up" on files already hatched into the network.  You can do this by file-request from your feed, but there is a considerable volume of files and the cost could be prohibitive.  We will be glad to mail you volumes of the earlier files.  Send two 1.2 or 1.44-meg floppy disks, pre-formatted and labeled, to the address above, and include a stamped, self-addressed return mailer.  We will duplicate disks full of older files as long as you make the return mailing as easy as dropping the disk in the mailer and putting it in the mailbox.

                               _______
