WinNet NETWORK INFORMATION AND POLICIES ------------ 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 has grown amazingly in offices and homes across the world. We have seen an explosion in the number and quality 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 types of files distributed by Win*Net will be primarily those of general interest to "ordinary" users of the Windows environment. While there are a number of text files and utilities available and of interest to Windows programmers, VAR's, etc., you will see very few of these distributed via Win*Net. There are other services, such as the Programmers' Distribution Network, which circulate such files. Likewise, 32-bit programs intended solely for use with Windows NT will not be found in Win*Net (there is a WINNTNET file-distribution system for this, unaffiliated with Win*Net). -------------- THE BASIC RULES WinNet consists of an open distribution network which a sysop "joins" by locating a convenient "uplink." This is simply another BBS which carries the WinNet file and message areas, and is willing to pass them on to you. In requesting such a link, you should first ascertain that the uplink is willing to take on this task, and then provide him/her with information about your BBS, your voice phone number to work out any problems, suggested sessioni-level and file-distribution-utility passwords, and so forth. If you don't know a likely uplink, there are two places you can look. One is for a nearby "FILEBONE" connection. The Filebone is a sort of file-distribution cooperative within the FidoNet network whose participating sysops undertake (usually at their own expense) to distribute a number of "FDN's" (File Distribution Networks), including WinNet, in a hub-and-spoke distribution system. A list of Filebone "hubs" (regional bbs'es distributing these files) is regularly published and disseminated within Fidonet as FILEBONE.NA. You can file-request this file from any filebone location, or from here at Fidonet 1:130/38; there is node distribution information usually at the end of this file. There is also a "private" distribution system for WinNet, consisting of bbs'es which distribute primarily (or only) WinNet files within certain regions or countries. If you received this file as an archive containing HUB.MAP, you will have an indication of hub feeds close to you; feel free to contact a nearby node to ask about a hookup. Network requirements are as follows: 1) The applicant will run a Fidonet-compatible BBS system capable of using TICK, the "file-echo" utility by Barry Geller, or its functional equivalent. The system must support file requests and should have been a member of their "regular" BBS network for at least six months. The system must also be capable of receiving and sending echo messages in standard, Fido- compatible .MSG format. All networks which are welcome, as well as all systems running whatever software, who can send and receive files and messages in FTSC format. We recommend you set up TICK to use the "replace" function, since updated files are occasionally distributed with file-replace information for your convenience. 2) Access to 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. If you have a "pay board," you may be violating author license agreements - don't identify yourself as a WinNet system! Also, we will be publicizing the fact that we have a network of free-access boards which carry WinNet files, and we don't want to mislead anyone. 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. 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. At least, all regional HUB boards will incur long-distance charges. WinNet requires that uplinks be polled at least weekly. Any node not polling for two weeks, and not making suitable alternate arrangements with its uplink, may be deleted from the network without notice. 5) A list of files in the WinNet area of each board should 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 must 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! --------------- TECHNICAL STUFF To ensure consistency across the system, files are "hatched" from a single central point at 1:130/38, which is a system in the Dallas-Ft. Worth, USA area. These files will be put on "hold" for pickup by direct feeds. Files will be hatched in ".TIC" format. The central distribution point will be sending files using a US Robotics Courier HST/DS. It is requested that applicants for regional HUB status be HST- or V32-compatible. Connections below the regional HUB level will be a matter for the hub boards; Filebone connections are regulated informally by Filebone participants. Session-level and TICK passwords should be used by all participants. An request to participate to a hub should include suggested passwords for both. That way you can be hooked in right away! 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 areas for use by TICK. These are: WIN_UTIL ...for system files, utilities WIN_GRAF ...for graphic/picture files, icons and icon editors, screen utilities/blankers WIN_GAME ...for games and diversions WIN_PROG ...for programs and applications WIN_SYST ...for WinNet-specific stuff, or files mostly of interest to sysops WIN_SOUN ...for 3.1-compliant sound and multimedia files WIN_DRVR ...for Windows driver files WIN_DATA ...for databases, lists, etc. WIN_PRNT ...for font and printer utilities. New Windows-related files for distribution are always welcomed. They should be sent to 1:130/38 in one of the following ways: 1) by direct mail, on disk from the author, addressed to: Larry Mundy WIN*NET 3720 Chittam Lane Bedford, TX 76021 USA 2) by file-attach to 1:130/38, 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 required for distribution by WinNet. The PKZIP -av "security envelope" will be used for all files hatched into WinNet. When you unzip an original WinNet file, it will tell you its authenticity has been verified; if you don't see this announcement, be particularly cautious of the file. -------------------------- USING TICK Upon applying for an assignment, you should set up to receive the WIN_SYS message 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 the mythical 100/100: AREA c:\[directory name] WIN_UTIL 1:100/100 * & AREA c:\[directory name] WIN_GRAF 1:100/100 * & ...and so on, for the files areas listed above. 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. If you need a copy of TICK and have a FidoNet nodelist, file-request "TICK" from 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. There is also a "WinNet library" system that accepts FTSC file requests 24 hours a day at FidoNet 1:124/5003, (214) 448-4082, v.32/v32bis. _______ Thanks for your interest!