1. VNET
2. How to Join VirtualNET
3. VNET.EXE Command Line Usage
4. VCONFIG Set-Up for VNET
5. Clients
6. BBSLISTs and AREALISTs
7. Setting Up Email
8. Setting Up VirtualNET Message Bases
9. Advanced Options

                VNET.EXE is the VirtualNET-type network software provided
         with Virtual Advanced software.  It supports VirtualNET, and the
         many alternative networks based on this format.  VNET is complete
         -- there is no other mailer or software needed, and set-up couldn't
         be easier.

               Virtual Advanced features an extremely sophisticated
         version of VNET.EXE which can easily gate email and message bases
         between itself (VirtualNET-type networks) and any other network
         type also supported by Virtual Advanced.  With VNET, it is easy
         to gate email and messages:

         VirtualNET-type <--> FIDOnet
         VirtualNET-type <--> Internet
         VirtualNET-type <--> QWK type                (messages only)

               Complete instructions and guidelines, plus the NODE.APP
         are available in file NETGUIDE.ZIP, available at the Virtual
         ComTech BBS and many others, and at the web site.

               Note that <ch> refers to Virtual Advanced Channel Number,
         and that <x> refers to the NETWORKID #, as defined by file
         DATA\NETWORKS.LST. The NETWORKID=<x> parameter may be omitted
         if NETWORKID=1.

         VNET <ch> /U NETWORKID=<x>

           Update and packup any outgoing mail.  Automatically called
           by VME as needed.

         VNET <ch> /IMPORT=<path and filename of packet> NETWORKID=<x>

           Pull in data received by remote.
           (Automatically run when data is received after a net call, however
           you might use this function for special purposes.)

         VNET <ch> /D<full system address> NETWORKID=<x>

           Dial into the specified system.

         VNET  <ch> /A NETWORKID=<x>

           Compile the BBSLIST.

                When setting a VirtualNET-type network using VCONFIG, you
         will be given the following choices:

         1. Node Number:

         This is where you enter your node number.  If you don't have one
         yet, then set this to 0.

         2. Network Directory:

         The "storage directory" for use by this VirtualNET-type network.
         Note: Every VirtualNET-type network you set-up must reside in
         its own, unique storage directory not used for any other purpose.
         (Example: C:\NET1)

         You will need to create this directory manually.  The BBSLISTs
         and AREALISTs for this particular VirtualNET-type network must
         be copied to this directory.

         3. Protocols Allowed:

         The choices are Ymodem, Zmodem, HSLink, or all three.
         (Note: HSLINK not available for VADV-OS2 systems.)
         This field lets you configure what protocols that others
         calling into you can use.

         4. Protocol Preferred:

         The choices are Ymodem, Zmodem, or HSLink.
         (Note: HSLINK not supported for VADV-OS2 systems.)
         This field lets you specify your favorite to use
         when you are calling out.

         5. Server:

         This field is where you put the node number of your server,
         as designated usually by the hierarchy of the network you are
         joining. (Unless you are starting a new network, then you *are*
         the hierarchy.)

         6. Server Phone Number:

         The phone number for the modem to dial when "netting" into your
         server.  This should be entered exactly as it needs to be dialed.

         7. Server Call:

         This is the first of two fields that affect how VNET behaves with
         regards to "polling" (automatic dialouts) to your server.

         Whether this is a local call, or long distance.
         If long distance, then evening calling hours apply, and only
         one call per day wil be allowed. If local, then there are no
         restrictions on time of day or number of times to call.

         8. Server Threshold:

         This is the second of two fields that affect how VNET behaves with
         regards to "polling" (automatic dialouts) to your server.

         If 0, then polling is totally disabled, and you will have to
         force callouts manually or through some other mechanism.
         If non-zero, then this indicates the number of kilobytes that
         must be present minimum in order for a dialout to be attempted.

         9. Server Macro:

         Specifies a macro file to use to complete the login process,
         where Virtual Advanced is running under a matrix, shuttle-login,
         or another BBS.  Usually NOT needed.

         A. Server Password:

         This field specifies the password to use to ensure authentic
         network mail transfers from one authorized member to another.
         This field can be left blank (no password), but setting a
         password at least 5 characters long is strongly encouraged.

         B. ZIP Trigger Level:

         This specifies the level at which pre-ZIPPING (compression)
         of network packets occurs.  Normally this can be left at default,
         UNLESS YOU ARE A MAJOR SERVER TO OTHER SYSTEMS, IN WHICH CASE
         A VALUE OF AT LEAST 200000 IS RECOMMENDED.

                If you are serving (refeeding the mail to) other systems,
         then you will have one or more "clients" beneath your system
         on the overall network tree.  The set-up for a client system
         is similar to the inputs needed for your server; you will need
         the client's node number, phone number, and desired password,
         and you can set the call and threshold polling options as desired.

                Once set-up, a client than then "net into" your system and
         get their network feed from you.

                As general rule, especially when you are just starting out,
         you will get your BBSLISTs and AREALISTs from the "authorities"
         of the network you are subscribing to.  Initially you will download
         a set of files to start you out, and from there on out, you will
         get updates automatically through the network.

         NOTE: For VirtualNET (NETWORKID=1), you can always download the
         latest BBSLISTs and/or AREALISTs from the Virtual ComTech BBS
         at 616-399-4818, or from the website at http://virtualc.com.

         BBSLISTs filename VNETDATA.ZIP
         AREALISTs filename AREALIST.ZIP

                There is nothing extra you need to do, beyond the initial
         VNET set-up described above, to be able to send and receive
         VirtualNET Email.  There is nothing further you must do to be
         able to GATE email to other networks, either.

                VirtualNET Message Bases can be quickly and easily set-up
         using the included VMB utility program.  Make sure you have
         AREALISTs for the network you wish to manipulate in the that
         network's directory.

                An alternative method to message base set-up is to use
         VCONFIG to manually set-up/edit each database entry.  In this
         case, you would use the DATABASE CONFIGURATION portion of
         VCONFIG to display/edit a MESSAGE AREA DATABASE CONFIGURATION ENTRY.

         At this point, selecting the field "(G) Networks Configuration"
         would let you manually do what VMB does automatically.
         A typical message base number looks like:

               100000
               -or-
               77777

                To GATE a Message Base, you merely set-up its
         DATABASE COFIGURATION ENTRY to show that the field
         "(G) Networks Configuration" shows multiple networks --
         FIDOnet, and the other network(s) you want to GATE to/from.
         For example, you might see:

              VirtualNET=100000
              FIDOnet=MY_GATED_SUB

                The features described hereafter are optional, and unneeded
         in most cases.