                   *********************************
                      * * *  W E B - N E T  * * *
                   *********************************

------------------------------------------------------------------------------
[ 1 ]  Instructions for importing WN_CONFS.SUB into Synchronet BBS
------------------------------------------------------------------------------

NOTE: These instructions are for Synchronet v2.20a or later.  Older
      versions of Synchronet do not offer the ability to import message
      group definitions into SCFG.  If you are using an older version, you
      must skip to the next section and begin there.

1.	Perform steps 1 - 6 from the next section.  Starting with step 7,
	return here and continue.

7.      Select "Import Areas..." and hit ENTER.

8.	Select the SUBS.TXT format file and hit ENTER.

9.	Enter the complete path to where your WN_CONFS.SUB file resides
	and hit ENTER.  The Web-Net sub-group definitions will be imported.
	Hit ENTER again at the "OK" prompt.

10.	Hit ESC twice and answer "Yes" to the "Save Changes" menu.

11.	Continue in the next section, starting with step 25.

	==> GO TO STEP 25 NOW.


------------------------------------------------------------------------------
[ 2 ]  Instructions for manually adding Web-Net to Synchronet BBS's
------------------------------------------------------------------------------

NOTE: These instructions are for Synchronet v2.00 or later.  With older
      versions of Synchronet, these instructions may differ slightly.

1.      Run SCFG (type SCFG from a NODE directory or hit 'C' at the
        "Waiting For Call" screen).
        
2.      Select "Message Areas" and hit ENTER.
        
3.      Hit the END key to move the lightbar to the end of your group list.
        
4.      Hit the INS key to add a new message group.
        
5.      Enter "Web-Net" for both the long and short group names.
        
6.      Hit ENTER on the new "Web-Net" message group.
        
7.      Hit the END key to move the lightbar to the last option ("Message
        Sub-boards...") and hit ENTER.
        
8.      Hit the INS key to add a sub-board.
        
9a.     Enter "Sysops / Net Admin" for the long name.

9b.     Enter "Net Admin" for the short name.
        
10.     Enter "WN-ADMIN" for the QWK name.
        
11.     Enter "WN-ADMIN" for the internal code.
        
12.     Hit the END key to move the lightbar to the bottom of the sub-board
        listing.
        
13.     Repeat steps 8 through 12 for the remaining sub-boards:
        
    Long Name                                Short Name     QWK Name Int. Code
    ---------------------------------------- -------------- -------- ---------
    Web Browsers                             Browsers       WN-ADMIN WN-ADMIN
    Hot Web Sites                            Hot Sites      WN-HOT   WN-HOT
    Home Page Design and Layout              Design         WN-DES   WN-DES
    Ask the Experts                          Experts        WN-ASK   WN-ASK
    Hyper Text Markup Language (HTML)        HTML           WN-HTML  WN-HTML
    Virtual Reality Modeling Language (VRML) VRML           WN-VRML  WN-VRML 
    Java / JavaScript                        Java           WN-JAVA  WN-JAVA
    Miscellaneous Executable Content         Misc. Content  WN-MEC   WN-MEC
    Web Site Administration                  Site Admin     WN-SITE  WN-SITE
    Common Gateway Interface (CGI) Scripting CGI            WN-CGI   WN-CGI
    Web Magic                                Magic          WN-MAGIC WN-MAGIC
        
14.     Hit HOME then ENTER to edit the first sub-board in the list.
        
15.     Hit END, UP-ARROW then ENTER to edit the sub-boards "Network Options".
        
15a.    Hit 'E' then ENTER to modify the "Export ASCII Only" option.

15b.    Hit 'Y' then ENTER to change this option to "Yes".

16.     Hit 'Q' then ENTER to modify the "QWK Networked" option.
        
17.     Hit 'Y' then ENTER to change this option to "Yes".

18.     Hit ESC to move back to the sub-board config option menu.

19.     Hit the UP ARROW key then ENTER to modify the "Toggle Options".
        
20.     Make sure that "Allow Private Posts", "Allow Anonymous Posts"
        and "Post Using Real Names" are all set to "No".

21.     Make sure that "Allow Message Quoting" and "Public 'To' User"
        are both set to "Yes".  If either step 20 or 21 are not as
        indicated, change them to comply with these settings.

22.     Hit ESC three times until you're back at the "Web-Net Group" menu.
        
23.     Move up to the "Clone Options" choice, then hit ENTER, 'Y', ENTER to
        clone the options of the first sub-board into the rest of the group.
        
23a.    Go back in to the "Message Sub-boards..." menu and select the
        "Sysops/Admin/Nodelists" conference.  Hit ENTER to modify it.

23b.    Select the "Toggle Options" again and hit ENTER.

23c.    Change "Post Using Real Names" to "Yes".  This conference is the
        only conference that will use Real Names.

23d.    Hit ESC once and select "Access Requirements" and hit ENTER.

23e.    Hit ENTER again to add a "Requirements" string.

23f.    Enter "LEVEL 90" and hit ENTER.  If you are using a different ARS
        to specify WHO is a Sysop, enter that ARS instead.

24.     Hit ESC five times and answer "Yes" to the "Save Changes" menu.
        
25.     Hit UP ARROW four times to select "Networks" and hit ENTER.
        
26.     Hit ENTER to select "QWK Packet Networks".
        
27.     Hit DOWN ARROW, then ENTER to edit your "Default Tagline".  If you
        have already specified a Tagline, ignore this step and the next step.
        If you haven't created a Tagline yet, follow the next step.
        
28.     Enter the name and phone number of your BBS.  Include any other
        information you think appropriate.  Remember this all must fit on
        one line (generally about 60 characters long).
        
29.     Hit UP ARROW, then ENTER to edit your "Network Hubs...".
        
30.     Hit INS to create a new hub entry.
        
31.     Enter the QWK System ID of your feed's BBS.  If you are using the
        Network Master Node (Fat City BBS) for your hub, enter "FATCITY".
        
32.     Now hit ENTER to edit the new hub. The window should look like this:
        
        Hub System ID           FATCITY (or whoever your hub is)
        Pack Command Line       %!pkzip %f %s
        Unpack Command Line     %!pkunzip -o %f %g %s
        Call-out Command Line   %!qnet
        Call-out Node           1
        Call-out Days           Sun Mon Tue Wed Thu Fri Sat
        Call-out Time           00:00
        Networked Sub-boards...

32a.    If the "Pack" and "Unpack" command lines are blank, edit them
        to contain the information specified above.

32b.    Set the "Call-out" fields appropriately for your system.  You
        should know what node will call out to pick up QWK packets, what
        time and days you should call out and what the command line will be.
        You may leave these alone and come back to them later, after you
        have been given appropriate instructions from your feed, if you wish.
        
33.     Hit END, then ENTER to edit the configured "Networked Sub-boards".
        
34.     Hit INS to add sub-board.
        
35.     Hit END, then ENTER to select the "Web-Net" group.
        
36.     Hit ENTER with the "Sysops / Net Admin" sub-board highlighted.
        
37.     Enter "10001" for the Conference Number on Hub.
        
38.     Select "Strip-Out" for the "Ctrl-A" menu.
        
39.     Hit END to move the lightbar to the bottom of the sub-board list.

40.     Repeat steps 34 through 39 for the following sub-boards:
        
        Conference Name                           Conference Number
        ----------------------------------------- -----------------
        Web Browsers                                   10002
        Hot Web Sites                                  10003
        Home Page Design and Layout                    10004
        Ask the Experts                                10005
        Hyper Text Markup Language (HTML)              10006
        Virtual Reality Modeling Language (VRML)       10007
        Java / JavaScript                              10008
        Miscellaneous Executable Content               10009
        Web Site Administration                        10010
        Common Gateway Interface (CGI) Scripting       10011
        Web Magic                                      10012

        NOTE: The conference numbers specified above are examples.  You
              will need to obtain the CORRECT conference numbers from your
              feed.  The conferences will be numbered xxx01 - xxx12, where xxx
              is the base numbering scheme of your feed's Web-Net conferences.
        
41.     Hit ESC five times and answer "Yes" to the "Save Changes" menu.
        
    (steps 42 - 43 have been removed and are no longer needed)

44.     Move the lightbar down to "Message Options" and hit ENTER.
        
45.     Set your "BBS ID for QWK Packets" to an abbreviation of your BBS name
        (must start with an alphabetic character). Remember your QWK BBS ID;
        you'll need it later.  If you have already set your QWK Name, then
        skip to step # 47.
        
46.     Hit ESC and answer "Yes" to the "Save Changes" menu.
        
47.     Now hit ESC to exit SCFG.
        
 ******************************************************************************
 * AT THIS POINT, if you do not intend to use Telix to transfer QWK packets,  *
 * you can skip to step 62.  There are several ways in which to transfer QWK  *
 * packets, including directly with Synchronet Baja.  Consult the Synchronet  *
 * System Operators Manual for more information.  The following steps are for *
 * a configuration using Telix to transfer QWK packets.                       *
 ******************************************************************************

48.     If you're not already at a DOS prompt, get to one (i.e C:\SBBS\NODE1>).
        
49.     If you haven't already installed TELIX, do so now. Be sure to configure
        Telix for the *SAME* COM port, DTE rate, and flow-control settings as
        the node you are using for the call-out (call-out node is specified in
        step 32).
        
50.     Copy the files QNET.SLT and SBBSQNET.SLC from your EXEC directory into
        your TELIX directory.
        
        Example:
                 copy \sbbs\exec\qnet.slt \telix
                 copy \sbbs\exec\sbbsqnet.slc \telix
        
51.     Change into your TELIX directory.
        
        Example:
                 cd \telix
        
52.     Edit the QNET.SLT file.
        
        Example:
                 edit qnet.slt

53.     Move down to the lines that start with "copystr". If you installed
        Synchronet into your C:\SBBS directory, leave these lines alone.
        Otherwise, change "C:\SBBS\DATA" into the drive and directory where
        you installed Synchronet with "\DATA" on the end (for both lines).
        If you have changed the SCFG->System->Advanced Options->Data Directory,
        these lines must point to THAT drive and directory.
        
54.     Move down to the line that starts with "call".
        
55.     Change "VERT" and the phone number to match the BBS ID and phone
        number of the hub you are calling.  If your hub is the Network Master
        Node, enter "FATCITY".  If you are in the same area code as your hub,
        remove the area code prefix ("1-xxx") from the phone number.  The
        name you enter here should be the same name you entered in step 31.
        
56.     Change "QWKID" into your system's QWK BBS ID (as entered in step 45).
        
57.     Change "Password" to the password you wish to use on your hub BBS.
        
58.     Save the file and exit the editor.
        
59.     Compile the SALT script.
        
        Example:
                 CS QNET
        
        If you do not get the message "CS done..." then you did something wrong
        when editing QNET.SLT. Copy it from the EXEC directory and start over
        at step 51.
        
60.     Call your hub system. Logon as NEW and enter your BBS QWK ID as your
        user name and let your hub's sysop know that the account is for a
        Web-Net node (usually in new user validation feedback). Make sure you
        use the SAME password for the hub BBS that you entered into your
        QNET.SLT file. Do not perform a QWK net call-out to this hub until
        you are sure the sysop has made the necessary modifications to your
        QWK node account or the script will not work correctly. DO NOT download
        a QWK packet without the proper settings on your QWK node account. If
        you don't immediately get a QWK: prompt when logging on to the hub,
        your QWK node account has not yet been setup and you must wait until
        it is properly configured on the hub BBS before sending or receiving
        packets.
        
61.     If you installed TELIX in a directory other than "\TELIX" or on a
        different drive than Synchronet, you will need to edit the QNET.BAT
        file in your EXEC directory to have it change drive and directory to
        the correct location of TELIX.
        
62.     You will need to post a "start-up" message in each Web-Net sub-board
        to assure that it is added to your new message scan on your Web-Net
        host BBS. Any message will work, but if you don't have anything
        important to say, it is best if you just post a message to user name
        "SBBS" with a title of "ADD" in each of the sub-boards.  If you wish to
        later remove a sub-board from your new scan, simply enter a message to
        user name "SBBS" with a title of "DROP".  These "ADD" and "DROP"
        messages are called control commands and are explained in detail in
        "Message Base: Offline posting via QWK" in the Synchronet Sysops Manual.

63.     Take a deep breath -- you've just finished...  :-)
        

------------------------------------------------------------------------------
[ 3 ]  Disclaimers, Caveats and Warnings
------------------------------------------------------------------------------

If you have more than one QWK network currently in place, you may need to
modify these instructions slightly to avoid overwriting the existing QNET.SLT
file in your Telix directory.  If you DO have more than one QWK network active,
you probably know what is involved in this, so we won't repeat it here.  Just
keep in mind that you are basically duplicating what you have already done for
other QWK networks such as DOVE-Net.

To configure your call-outs using a terminal program other than Telix, you
may need to write your own scripts.  Scripts for Telix, Qmodem, and Baja
are provided in the \SBBS\EXEC directory.  Other communication programs have
similar scripts of their own.  Consult your users manual for assistance.
        
WARNING!!  WARNING!!  WARNING!!  WARNING!!  WARNING!!  WARNING!!  WARNING!!
WARNING!!  WARNING!!  WARNING!!  WARNING!!  WARNING!!  WARNING!!  WARNING!!
WARNING!!  WARNING!!  WARNING!!  WARNING!!  WARNING!!  WARNING!!  WARNING!!

It is MANDATORY that you *DO NOT* call more than one Web-Net hub unless
you and the hub sysop are very experienced with QWK networking.  It is also
important that if you SWITCH hubs in the future, that you delete all the
messages in the Web-Net sub-boards before your first call-out to the new
hub BBS.  Otherwise, you will flood the network with duplicate messages.

THIS IS VERY IMPORTANT!  Duplicate messages flooding the network are the
easiest way to get a group of Sysops mad at you.  Keep in mind that if YOU
send out 500 duplicate messages, EVERY NODE in the network will have to
absorb the cost of picking up (and possibly redistributing it, in the case
of the area hubs) those 500 messages.  Do YOU want to reimburse them?

------------------------------------------------------------------------------
[End of Document]    [Last updated: 28-Mar-96 by Fat City BBS]    [Rev 1]
