   +-------------------------------------------------------------------+
   |    Running Wildcat! Version 4 with Windows for Workgroups 3.11    |
   +-------------------------------------------------------------------+

Written on November 1, 1994 by Bryan C. Laird, Sysop of FCO's BBS.
Version 1.00

Acknowledgment
--------------

I need to first acknowledge that much of the information presented here
is thanks to the hard work of Joe Rhinehart of the Comm * Port BBS.
Any text I used from Joe's documents was used with his permission.
The number for the Comm * Port is 614-870-6544.

Thank you, Joe, for giving all us sysops an alternative to Desqview and
for patiently answering our questions.


The Standard Disclaimer
-----------------------

All responsibility and liability for using these tips rests with the user.
I will not be held accountable for any kind of damages incurred by you
when you use this document.  I have tested all these tips on the BBS I run
in an office environment and they all work perfectly.


Who is Bryan C. Laird?
----------------------

I am the Sysop of FCO's BBS and the Information Systems Manager for
F-O-R-T-U-N-E Consultants of Orlando.  I have been running a Wildcat!
BBS since May 16, 1994.  I started out using Desqview to multitask
the two lines of our BBS.  Desqview worked fairly well by itself.

I ran into problems when I tried to integrate the BBS and Desqview with
our Windows for Workgroups 3.11 network.  Everything was fine until
an event tried to run.  I set up an event to run every hour to send and
receive Internet email.  Everytime this or any other event tried to run,
the BBS computer and the network would lock up.

One of the things Quarterdeck Software wanted me to try was running the
BBS in Windows 3.1 standard mode.  I did that with a single node and
accessing the network - everything ran PERFECTLY.  I decided to use
WFWG 3.11 instead of Desqview.  It multitasks the two nodes just fine
and access speed over the network increased 3-5 times.

Now you know a little about me, but you are wondering what this place
called F-O-R-T-U-N-E is, right?

FCO's BBS is a business owned and operated BBS to satisfy the needs of
F-O-R-T-U-N-E Consultants of Orlando (FCO).  FCO is an executive recruiting
firm specializing in the permanent and contract placement of computer
hardware and software engineers, product managers, etc.


Other Notes
-----------

I will use the default C:\WILDCAT for the Wildcat! home directory.
Please change the drive and/or path to the appropriate settings for you.

Abbreviations I use:

    WFWG   - Windows for Workgroups
    32BFA  - 32-Bit File Access
    VDM    - Virtual DOS Machine - This is just a DOS Window in WFWG
    XMS    - Extended Memory
    EMS    - Expanded Memory


Sort of a Copyright Notice
--------------------------

The original ZIP file that this document came from may be freely
distributed as long as it is not modified in any way.  If you wish to
publish this information in any way, please get my permission before
doing so.

Thank you,

    -Bryan C. Laird


Specifications for FCO's BBS Computer
-------------------------------------

Computer:  386/DX-33, 8megs RAM, 1 Hard disk

DOS:       Microsoft, Version 6.22  (also used 6.20)

Windows:   Microsoft, Windows for Workgroups 3.11

Network:   Microsoft Network using Thin Ethernet

BBS:       Wildcat! Version 4.01 (also used 4.00, 3.91, and 3.90)

Node Info: Nodes 1 and 2 are set up for dial in.
	   Nodes 0, 8, 9, and 10 all accessed via local network logins

Modems:    Two US Robotics Internal Sportster 14.4k FAX with 16550s



Setting up the CONFIG.SYS and AUTOEXEC.BAT files
------------------------------------------------

Here's what mine look like:

CONFIG.SYS:

    DEVICE=C:\DOS\HIMEM.SYS /TESTMEM:OFF
    DEVICE=C:\DOS\EMM386.EXE NOEMS HIGHSCAN /V
    BUFFERS=50,8
    FILES=125
    DOS=HIGH,UMB
    LASTDRIVE=C
    SHELL=C:\DOS\COMMAND.COM C:\DOS\  /P
    STACKS=0,0
    DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS


Notes about the CONFIG.SYS file:

    Pretty much all of these are Joe's recommendations, and I have not done
    much in the way of testing modifications.  I added the TESTMEM:OFF
    switch to the HIMEM line simply to speed up booting the machine.

    The EMM386.EXE line needs a little discussion.  I have Wildcat! set up
    to swap to XMS.  Therefore, no EMS is needed.  If you are using a door
    program that needs EMS, you will need to remove the NOEMS parameter
    from this line.

    I have my FILES set to 125 because of all the nodes.  You should
    start with 25 and add 25 more per node that will be used.  So, a
    single node computer would need the line FILES=50.  Note that this
    computation is a MINIMUM requirement.  You may need more.

    The LASTDRIVE command should set the last available drive letter to
    the last one you need to conserve memory.  The more drive letters
    available, the more memory is needed to store that information.  If
    you have two hard drives (C: and D:) and six CD-ROM drives (E:, F:,
    G:, H:, I:, and J:) then you should set it to J.  If you don't care
    about the memory or don't want to think about it, set LASTDRIVE=Z.

    The IFSHLP.SYS device is needed for some WFWG procedures.
    It should not be removed if you want WFWG to operate properly.


Setting up the CONFIG.SYS and AUTOEXEC.BAT files (continued)
------------------------------------------------------------

AUTOEXEC.BAT:

    PATH C:\WILDCAT;C:\WINDOWS;C:\DOS;
    SET TEMP=C:\TEMP
    WIN /3


Notes about the AUTOEXEC.BAT file:

    Pretty straight-forward, isn't it?  You need to have your Windows, DOS,
    and Wildcat! directories in your path.  Set any environment variables
    needed as well.  The /3 switch tells WFWG to start in 386Enhanced Mode.
    It will do this without the switch if your computer has the necessary
    memory and speed, but it doesn't hurt to put it there.  Notice that I
    don't use SmartDrive or Share.  I'll tell you why later.


Notes about MakeWild
--------------------

I have MakeWild set to hold the overlay buffer in XMS.

I swap Wildcat! to XMS.  Swapping to XMS is faster than swapping to disk.

I have Wildcat! set to NOT terminate on doors and menu hooks.


The CAT.BAT File
----------------

Here's my CAT.BAT:

    @ECHO OFF
    :RELOAD
    C:
    CD \WILDCAT
    SET WCNODEID=1
    WILDCAT
    IF ERRORLEVEL 1 GOTO RELOAD

I would recommend setting the WCNODEID here.  This avoids any Node ID
conflicts with multiple nodes.


If you are running a second node, here's what my CAT2.BAT looks like:

    @ECHO OFF
    :RELOAD
    F:
    CD \WILDCAT
    SET WCNODEID=2
    SET WCPORTID=2
    SET WCIRQID=3
    SET WCBASEID=$2F8
    WILDCAT
    IF ERRORLEVEL 1 GOTO RELOAD

Again, I set the WCNODEID in the batch file.  Also, I am using the same
modem for each node so I only need to tell Wildcat! the proper port
specifications.  All other settings for the modem as defined in MakeWild
are correct for my setup.  There is a WCMDM variable you can use to
override all modem settings.  The WCMDM variable should be used if
the modem's configuration is different than what is defined in MakeWild.


Setting up Windows for Workgroups 3.11
--------------------------------------

I would not recommend using any kind of shell program other than the
Program Manager.  I use Norton Desktop for Windows on my other
computers, but it eats up memory and resources that should not
be wasted on the BBS computer.

NOTE: I have not tested a dial-in node using any kind of third-party
      shell program.


The Control Panel
-----------------

Start WFWG and go to the Control Panel.

-DESKTOP-

In the DESKTOP section, make sure 'Fast "Alt+Tab" Switching' is enabled.
This allows you switch to each node's window easily and quickly.

-386 ENHANCED-

Next is the 386 ENHANCED section.  In the section for Device Contention,
Change the settings for EACH of the COM ports you are using to NEVER WARN.

In the section for Scheduling, Windows in the foreground should be set to
62.  Windows in the Background should be set to something low, like 20.
This means that when you put a Window in the background (with the exception
of DOS windows) the CPU doesn't waste much processor time on it.  More
time will be available to your Wildcat! nodes.  Make sure 'Exclusive in
the Foreground' is NOT checked!  Your Wildcat! nodes will freeze if
you minimize them (or put them in the background) with this set on.

I have my minimum timeslice set to 15, but I have not experimented much
with this setting.

Now, go to the Virtual Memory section.  You should have a PERMANENT swap
file set up.  The size is up to you, but mine is set to 2048K.  If you
are using a dedicated computer for the BBS, 2048K should be enough.
If you intend to run other programs with the BBS in the background then
a higher value, such as 8192 (or even more), would be better for you.

Click on the 'Change' button.  This is where you can set up the swap file.

There are two items at the bottom of this section that you should select.
They are 32-Bit Disk Access and 32-Bit File Access.  32BFA is the
replacement for SmartDrive, and it's better and faster than SmartDrive ever
was.  If you have 8MB of RAM, you should set the Cache Size to 2048KB.
If you have less RAM, you'll may want to try something less.


The Control Panel (continued)
-----------------------------


NOTE:  The most common problem with getting 32BFA to work is that
       WFWG locks up at the title screen.  This can usually be solved
       by changing a setting in your SYSTEM.INI file.  Instructions for
       editing your SYSTEM.INI file are contained in the Virtual Share
       section below.

       Find the line in the [386Enh] section that says NoEMMDriver=.
       This is probably already set to TRUE or ON.  Change it to say 'off'.
       It should look like this:

	   NoEMMDriver=off

       Restart WFWG.  This will usually fix the problem.


That's it for the Control Panel.


The PIF File
------------

The Program Information File(s) for your Wildcat! nodes is critical.
They contain the information about the Virtual DOS Machine that your
node will be running in.  This is how mine are set up:

NODE1.PIF

Get to the MAIN program group in WFWG.  Open the PIF editor.  Make
sure the 386 Enhanced is checked in the MODE pull down menu.  Start
filling in the blanks with the following:

    Program Filename:     C:\WILDCAT\CAT.BAT
    Window Title:         Node 1
    Optional Parameters:
    Startup Directory:    C:\WILDCAT

    Video Memory:         Low Graphics

    Memory Requirements:  -1 Required, -1 Desired
    EMS Memory:           0 Required, 0 Desired
    XMS Memory:           640 Required, 1408 Desired

    Display Usage:        Full Screen

    Execution:            Background: YES
			  Exclusive: NO

    Close Window on exit: YES


ADVANCED SECTION:

    Background Priority:  125
    Foreground Priority:  125
    Detect Idle Time:     NO

    EMS Memory Locked:    NO
    XMS Memory Locked:    YES
    Uses High Memory:     NO
    Lock Application Mem: YES

    MONITOR PORTS:
    Text:                 NO
    Low Graphics:         NO
    High Graphics:        NO
    Emulate Text Mode:    NO
    Retain Video Memory:  NO

    OTHER OPTIONS:
    Allow Fast Paste:     YES
    Allow Close When Active: NO
    Reserve Shortcut keys: Optional


The PIF File (continued)
------------------------

The above settings assume you are holding the overlay buffer in XMS
memory by setting the appropriate field in MakeWild.  This also assumes
nothing you run in this DOS window will need EMS.  That includes any doors
your callers use.  If you are using EMS, you should change the EMS memory
required and desired settings to whatever is appropriate.

The PIF file is what you should run to start each node of your BBS.
If you are running more than one node, all you need to do is change the
program line to the appropriate batch file to start the next node.
Change the Window Title as well to reflect the proper node number.

I would recommend creating a Program Group for Wildcat!.  You can put
MakeWild, MakeMenu, wcPro, wcCode, wcGate, MakeQues, wcModem, wcRepair,
and any other utilities in it.

You can also put the icons for running each node in the Startup Group.
Each node will then automatically start when you run WFWG.


SHARE.EXE and Virtual Share
---------------------------

You might have noticed that I didn't put SHARE.EXE in my AUTOEXEC.BAT file.
This is because WFWG has a Virtual Share Driver.

Virtual Share is a better solution than SHARE.EXE.  You never have
to worry about having enough file locks or space allocated.  Virtual
Share allocates locks and space dynamically when they are needed.

To make sure you are using Virtual Share, you will need to open
your SYSTEM.INI file into a text editor.

WARNING:  DO NOT USE A WORD PROCESSOR!  These programs such as
	  Microsoft Word, Lotus AmiPro, or WordPerfect put
          formatting codes into the file that will cripple your
	  system.  I use the MS-DOS editor.

Once you have opened the SYSTEM.INI file, page down until you get to
section with the heading [386Enh].  Look at each line in this section
until you find one that says:

     device=vshare.386

That is the Virtual Share driver.  You do not need SHARE.EXE if you
use it.

If you cannot find this line, just type it into the [386Enh] section.

NOTE:  I have elected to remove SHARE.EXE from my AUTOEXEC.BAT file.
       You don't have to do this.  If you leave it in, Virtual Share
       will take over when WFWG starts up.  The only price you pay
       is 6K of conventional memory.  This means you will have 6K
       less conventional memory in each VDM Wildcat! is running in.
       If you want to run a single node of Wildcat! after exiting
       WFWG for testing purposes, just type SHARE (and press enter)
       before starting the node.  The default SHARE settings should
       be fine for a single node from DOS.


Other Items of Note in the SYSTEM.INI File
------------------------------------------

One person I was helping reported a problem with running out of
Environment Space.  This is where your environment variables, such as
WCNODEID and your PATH, are stored.

If you run out of this space, Wildcat! or any other program that needs
it will not run properly.

Find the section of your SYSTEM.INI file that starts with the heading
[NonWindowsApp].  You can either modify or add the following line:

    CommandEnvSize=2048

Keep in mind that the memory you reserve here will not be available
to programs running in a DOS window.

2048 is enough in most cases.  If you still run out, you should increase
it to 3072 or even 4096.


The Communications Driver
-------------------------

From what I have learned, there are two factors in communications
speed with Wildcat! and WFWG:  CPU power and the comm driver.

The comm drivers that I know of are TurboComm, Cybercomm, and the
regular WFWG comm driver.  From my testing, none of these are
the answer.  The proper answer is: NO comm driver.

I struggled to get good speed in WFWG with Wildcat! 3.91M.  I finally got
it by using the TurboComm driver.  When I upgraded to Wildcat! 4, my CPS
for downloads and uploads again plummeted to around 700.  Everything
worked fine if I ran a single node from DOS.

I decided to try NOT using a comm driver.  I got a sustained 1600+ CPS
on downloads and 1700 CPS on uploads.  Performance dropped slightly when
another DL/UL was initiated on a second node.  The first node would drop
to around 1500 and the second node wouldn't pass 1400.  As soon as one
of them finished, the remaining one would speed right back up.

WFWG has virtual comm drivers that seem to work better than the
regular one.

Here's what you need to do to use this method:

NOTE: If you are using TurboComm, read the instructions in their manual
      on how to uninstall it.  Then follow the procedure below.

1. Open your SYSTEM.INI file and remark out the line in the boot
   section that specifies a comm driver by putting a semicolon in
   front of it like this:

   [boot]
   ;comm.drv=comm.drv

2. Make sure these three lines appear in your 386Enh section of
   the SYSTEM.INI file and are NOT remarked out:

   [386Enh]
   device=*vcd
   device=serial.386
   device=vcomm.386

   They are the virtual comm drivers and should already be there
   unless you took them out.

NOTE:  Getting the WFWG comm drivers configured properly is the toughest
       part of running a Wildcat! BBS in WFWG.  The above method is not
       your only choice.  Joe and I have tried many different
       configurations in an attempt to find the one that works for
       everyone.  If the above suggestion does not work for you, don't
       give up!  Contact MSI Tech Support, or Joe, or myself.


Running Wildcat! using a Windows for Workgroups 3.11 Network
------------------------------------------------------------

NOTE: This section assumes you have successfully set up a WFWG
      peer-to-peer network.  If you have any problems with that part
      feel free to write me or contact Microsoft Technical Support.


Wildcat! can be successfully run in a WFWG 3.11 Network environment.
A dedicated server is not needed.  You can run nodes on the WFWG
computer doing the serving at the same time it is running one or more
nodes.

The key:  Getting each network node to access the same drive.

All the computers that run either a local node or dial-in node have
to access Wildcat!'s databases.  Also, they all have to refer to the
same location to get to these files.

    +--------+      +--------+      +--------+      +--------+
    | Node 1 |------| Node 2 |------| Node 3 |------| Node 4 |
    +--------+      +--------+      +--------+      +--------+

Picture each of the above nodes as an individual computer connected
by a WFWG local area network.  If your Wildcat! files are on node 1's
hard drive, nodes 2-4 also have to access the Wildcat! files.  All the
nodes have to use the same drive letter and path to get to them.  If
you repartition (divide up) the hard disk on node 1's computer, WFWG
can connect to that drive over the network using the same drive letter
that node 1 will use.  Did I lose you?  :)

You need to have an empty hard drive to repartition it.  Any existing
data on it will be lost.  Make a reliable backup to tape or floppy and
make sure the data will be restored properly if you need to save anything.
This includes DOS!

The MS-DOS program FDISK.EXE is used to repartition the disk.
Here's an example:

    Total disk space:  420 MB
    -------------------------
    Partition for C:    15 MB
    Partition for D:   405 MB

Drive C: contains the DOS directory as well as the AUTOEXEC.BAT and
CONFIG.SYS files.  There should not be a problem with putting WFWG
on this drive as long as you give it the necessary space.


Running Wildcat! using a Windows for Workgroups 3.11 Network (continued)
------------------------------------------------------------------------

Drive D: contains ALL the Wildcat! files, file areas, and door
programs that are needed by every computer.

NOTE:  Just because this is how I chose to partition my hard disk does
       not mean that you have to do it this way.  You could leave drive
       C: with around 10-15 MB and create 1 MB partitions as placeholders
       to get down to drive F: or even W:.

Don't forget to change the LASTDRIVE parameter in your CONFIG.SYS file
to the last drive that will exist on the computer if you need to.

After repartitioning, each drive you created will need to be formatted.

After restoring or installing DOS and WFWG, you should get to the
File Manager and share drive D: with the rest of the workgroup.

NOTE:  Make sure you set the Access Type to FULL!  You will get many lock
       retry errors if you set it to read-only.

Go to each network computer and connect to the shared drive on node 1
AS DRIVE D:!

After doing this, it should be obvious that any computer that accesses
drive D: will be using files on the same hard drive.

It may possible to use the SUBST command to accomplish this, however
this is not recommended by Mustang Software Technical Support.

The CAT.BAT file to start each node should set the appropriate WCNODEID
and comm port settings.

If one or more of these are to be local nodes that do not take calls,
your batch file should look something like this:

    @ECHO OFF
    SET WCNODEID=0
    SET WCPORTID=0
    D:
    CD \WILDCAT
    WILDCAT /B LOCAL

The WCPORTID of zero is critical.  That is what tells Wildcat! that it's
a local node.  You can use any available node number.

The PIF file should be different for local nodes.  They usually don't
need to run in the background, you can turn Detect Idle Time to ON, and
you shouldn't need to lock any of the memory.

One more thing, in MakeWild for Wildcat! Multiline versions, the
network type should be set to 'DOS Share'.


The End
-------

In conclusion, Wildcat! can be run very successfully with Windows for
Workgroups 3.11.  You can run multiple nodes on a single computer,
network the nodes to multiple computers, and even do local logins
over the network.

If you have any comments, questions, or suggestions, please contact
me via one of the following services:

    Internet:  bryan@fco.com
  CompuServe:  73251,2235
  MSI HQ BBS:  BRYAN LAIRD
     US Mail:  P.O. Box 950835, Lake Mary, FL, 32795-0835

I apologize for not being able to give you the number for the board I
operate, FCO's BBS, but it is a business owned board and it would not be
appropriate for me to open it up to this public forum.  I am thinking
of starting my own BBS and will certainly make that number public if
Big Bry's BBS comes into existence.

I will update this file when I learn something new or for a major change
in Windows or Wildcat!.  I am currently investigating running Wildcat! on
a Windows NT 3.5 Server.  I'm sure someday I'll be experimenting with
Windows 95 (Chicago) as well.

Good luck and happy Sysopin'!

    -Bryan C. Laird


