.TOPIC:
Running VBBS under MicroSoft Windows
                                        VBBS 6.12 Documentation --11-A-1
         ͻ
          CHAPTER 11 ANNEX A  RUNNING VBBS UNDER MICROSOFT WINDOWS 3.x  
         ͼ

         Running VBBS under Microsoft Windows <tm> 3.0 or 3.1 can
         sometimes seem to be a little mystical, but with a little twea-
         king, it can not only be done, but done well enough to run two
         high-speed remote nodes as well as a local login. This is of
         course dependant on the hardware that you may be currently using
         for your bbs. Windows is very much RAM dependant, like all other
         GUI's that are currently available. So, no matter what settings
         you use with 4 MEGS of RAM, you are NEVER going to get the
         performance that 8 will get you. Not even these WISE words, will
         change that <G>.

         Also, the newest release of Windows For Workgroups (As of this
         writing 3.11 was the latest), has some added features that made
         running multiple sessions of VBBS, much more palletable, to even
         the most uninitiated Windows sysop. I highly advise this as the
         preferred system, to the Standard Windows 3.1.

         Minimum Requirements
         

         For a single remote-plus-local system, you'll need a
         386DX/25 (or higher) CPU and an absolute minimum of 4 megs of
         RAM.  Performance improves dramatically with additional RAM (8
         megs is recommended) and higher CPU speeds. For a two remote-
         plus-local, your machine should be a 386/33 with eight megs of
         RAM (again, a minimum baseline).


         Setting Up Your .PIF
         

         The most critical single element is your .PIF (Program
         Information File).  The more carefully you design the .PIF, the
         better your system will run.

         There is a strategy that you should use when determining
         your PIF's. You need to decide what you want to do in the
         background, and what priority that should have in comparison to
         your bbs. This just simply means; if your bbs is running, and you
         are printing out a report, if something has to slow down, which
         will it be. If you want the bbs to run, and not slow down EVER,
         then these settings should be helpful.

                                       VBBS 6.12 Documentation--11-A-2

         Below are suggested "starter" settings:

         In Basic .PIF Setup
         

         Program Filename:       C:\VBBS\BBS.EXE
         Window Title:           VBBS Online
         Optional Parameters:    1  (Commandline parameters go here)
         Start-up Directory:     (Leave Blank)

         Video Memory:           Text
         Memory Requirements:    KB Required:   520      KB Desired:   640
         EMS Memory:             KB Required:    0       KB Desired:  1024
         XMS Memory:             KB Required:    0       KB Desired:  1024


         -----> NOTE:   The 520 "SHOULD" handle all situations. I have
                        NEVER run out of memory, with that setting.  I
                        also have never had a problem with NOT enough
                        EMS or XMS with the 1024 settings.


         Display Usage:          Full Screen
         Execution:              Background (selected)
         Close Window on Exit:   Yes (selected)

	 
         In Advanced Options
         
	 
         1) Multitasking Options:
                Background Priority:    500 (400 for high-speed modems)
                Foreground Priority:    400 (350 for high-speed modems)
                Detect Idle Time:       NO (unchecked)

         [ REVERSED for applications you intend to run parallel to VBBS ]


         2) Memory Options:
                Lock Application Memory (Only item selected)

         3) Display Options:
            (none)

         4) Other Options:
            (none)

                                       VBBS 6.12 Documentation--11-A-3

         In Windows Control Panel -- 386 Enhanced
         

         1) Device Contention:
            See discussion on COMports, below

         2) Scheduling:
                   Windows in Foreground:   400
                   Windows in Background:   500 (see Note 1)
                   Exclusive in Foreground: OFF (unchecked)

      	 	Note 1: This setting can be higher if you really need 
                        more activity in the background.

         3) Minimum Timeslice:
                   10-12 (for 25 MHz CPUs)
                    8-10 (for 33 MHz CPUs)
                    6-8 (for 40+ MHz CPUs)

         4) Virtual Memory:
            This option controls Windows' "swap file" where it can
            move inactive applications out of RAM and onto the hard
            drive temporarily. It is imperative that you create a per-
            permanent Swap File of 2-6 meg to speed any swapping ac-
            tivity.
                        
         --> IMPORTANT NOTE:  If you are creating a Permanent Swap File
                              for the first time, be sure to optimize
                              your selected partition BEFORE you create
                              the Swap File! Also, Double-Spaced Drives
                              will NOT allow a Permenent Swap file.
                              Therefore a NON DS'ed drive should be used.

             Select 32-Bit Disk Access to maximize data transfer to and
             from the hard drive. (Not Possible with Some I/O cards)
             Also, in WFWG 3.11 turn on 32-Bit FILE access as well.

        5) COMports:
           If you are running a 9600 baud or faster modem, be sure
           to lock that port in Control Panel, Ports.  Windows 3.1
           will allow locking up to 19200 baud; if you are running a
           FOSSIL driver (such as BNU or X00), you can safely lock
           the FOSSIL at a higher rate without threatening your Win-
           dows environment. Also, the 19200 limit that is percieved
           by most people, is adjustable to 38400 *BY TYPING* it in
           instead of selecting.
                        
           Also, make sure you set Flow Control to "Hardware" for
           high-speed modems. This setting MUST match your COMPORT
           setting in VCONFIG.

                                       VBBS 6.12 Documentation--11-A-4


        6) Conflicts:
           Often, computers ship with bizarre hardware configura-
           tions, some with COMports 1 and 4 occupied by a modem
           and a mouse.  Make sure you do not introduce problems by
           introducing a second modem on an already-occupied port
           address or IRQ.  Just because you have four COMports on
           an ISA-bus computer doesn't mean you can use all
           four without conflicts.  There are only two IRQs avail-
           able for them.

           In Control Panel, 386 Enhanced, select "Never Warn" for
           your active COMport.  This will prevent Windows from
           opening a "COMport Contention" dialog box when an online
           user selects a game that does its own COM writes (thus
           locking the port until you intervene).

           Just make sure that you do not inadvertantly attempt to
           seize the BBS COMport for your own use from another win-
           dow!


        In SYSTEM.INI
        

		Under the heading [386Enh], add or modify the following 
        lines as necessary for your system:

                COMxBuffer=1024  (where x is your modem port)
                COMBoostTime=8
                COMxFIFO=1  (where x is a port controlled by a
                             NS16550AFN buffered UART) 
                COMxAutoAssign=0  (where x is a "no conflict" COMport)


        Additional Hints
        

          The use of a FOSSIL driver for the BBS can many times resolve
           nagging problems with BBS-external programs, such as games.
           Two widely used FOSSIL drivers in the BBS community are BNU
           and X00.  As discussion of FOSSIL drivers and setup is beyond
           the scope of this document, please refer to the documentation
           accompanying the drivers, and, if using one, make sure to set
           "Use FOSSIL Driver" to "Yes" in VCONFIG.

          Replace your DSZ protocol driver with the newer GSZ, which is
           much better suited to sharing resources in a Windows environ-
           ment.  With a 14400 data transfer in background, DSZ effec-
           tively locks the local user's window; with GSZ, the transfer
	    

                                       VBBS 6.12 Documentation--11-A-5


          is barely noticeable.

          Make sure all .PIFs for DOS applications have a Background
           Priority of 1 and have the Exclusive Execution box UNCHECKED.

          If at all possible, put your mouse on COM1 and your modem on
           COM2. Avoid the COM1/4 or COM2/3 setups (and certainly do NOT
           use COM1/3 or 2/4 together on an ISA-bus machine).  Remember,
           COM2 is serviced before COM1.

          Avoid running the BBS in a windowed display, especially if
           there are other windows open on the desktop.  Video conflicts
           can wreak havoc with the BBS! Also, a Windowed Screen actually
           uses MORE memory than a Full Screen session does.

          Consider replacing Windows' COMM.DRV with one of several
           after-market COM drivers, such as TurboCom (Bio-Engineering
           Research Labs, Berkeley, CA) or, for multi-port COM cards
           (such as the VBBS-supported DigiBoard), W3COM9 (Cherry Hill
            Software, Marlton, NJ). Also, Delrina (WINFAX), has made their
            COM Drivers Freeware. These have been founf by many to be as
            effective as the expensive TurboCom.

          Never be afraid to experiment with .PIF and Control Panel
           settings.  Your results are dependent on your machine, setup
           and use of the computer. To avoid the Apps that you are running
           on the desktop from slowing your BBS down. Make sure that the
           Foreground Priority of the App is NOT HIGHER than the Background
           Priority of the BBS.PIF.


         ͻ    Running VBBS under Windows can sometimes overwhelm you.
         ͼ	It CAN be done (and is being done by many sysops).  Feel
                free to ask questions in any of the VirtualNET support
                subs; you may also want to consider carrying "Windows
                Workshop" (VirtualNET autorequest sub #6090).

            More Windows reading:   Windows 3.1 Secrets, by Brian
            Livingston (IDG Books Worldwide, San Mateo, CA)

