Preparation and Installation of Windows 95

Before Windows 95 is installed a complete system backup should be done to insure easy recovery in the event of a system problem.  If you are planning to add the BBS system to an existing network you may want to setup the network card before installation.  This will allow the setup to detect it so you won't have to run the hardware wizard later.  When installing Windows 95 perform a custom installation and select only those files you will need.  If your BBS system does not have a sound card do not select any multimedia options.  If it will be connected to a network or already is be sure and install the net watcher and other network utilities.

Setting Up Windows 95

After Windows 95 is up and running you will need to do a few things before you set up Wildcat to run under it.  If you will be printing to a networked printer install the printer driver by right clicking on the printer in network neighborhood and clicking install.  When setting up the printer opt to capture the printer port.  If you do not you will be unable to print Wildcat utility program screens (printable only via shift+print screen).  Use the hardware wizard to setup your modem or modems so you can dial out through hyper terminal for testing as needed.  If you have a network set the network log on type to Windows instead of Microsoft Client to avoid being prompted for a name and password at startup.  If you do not a power failure will leave your BBS down until you return!!!

Configuring Wildcat, Modifying the Boot Files and Creating the Batch Files

To setup Wildcat for use under Windows 95 change the network type in makewild to reflect your line status.  If you will be running with one node leave the network type set to No Net.  If you will be running with more than one node or with one dial in node and a local node set the network type to DOS Share.  After that you are ready to modify you startup files and create the needed batch files.  Please note that these directions assume a Wildcat home directory of c:\wildcat.  Your startup files should read as follows.  Your old path should follow the = in the line reading path=. The drive letter in the line lastdrive=f should be the one higher than your last drive letter.

If you currently load any programs at startup include them in your autoexec.bat file.  Also include any other set statements you may need such as one to set the defaults for dir.  Please note that when we tried to use the fossil driver BNU distributed with the setup notes for Windows 95 on the Mustang HQ we had problems.  The setup seemed to imply that we would have to use it, but it caused everyone to connect at 2400 baud when loaded via config.sys. Using no fossil driver caused Wildcat to display the right baud rate for everyone, but use a one lower baud rate (i.e. 14400 baud callers connected at 14400 baud and received data at 9600 baud while 9600 baud callers connected at 9600 baud and received data at 2400 baud).  Installing Win Fossil resulted in everything working fine.  For fossil drivers to work properly you need to set each modem to determine ringing using Ring Detect and determine baud rate using Result Code 2

Autoexec.bat

@Echo off
PATH =
set comspec=c:\windows\command.com
set wcnodeid=0
set wchome=c:\wildcat

Config.sys

files=200
lastdrive=f
shell=c:\command.com c:\ /P /E:2048
device=c:\windows\command\ansi.sys

Your batch files should read as follows.

node0.bat (sets environment for local node 0)

@Echo off
SET WCNODEID=0
SET  WCPORTID=0
c:
cd\wildcat
startbbs.bat

node#.bat (sets environment for dial in nodes)
(substitute # with a node #)

@Echo off
SET WCNODEID=1
rem set wcportid=1
rem set wcirqid=3
rem set wcbaseid=$2F8
set nodepath=c:\wildcat\wcwork\node#
set wcmdm=ussr288.mdb
cd\wildcat
startbbs.bat

startbbs.bat (loads Wildcat)

@echo off
echo Running STARTBBS.BAT for Node %wcnodeid% on Com:%wcportid%
:reload
wildcat
if errorlevel 1 goto reload

Change the values of the set statements in the node#.bat files to reflect the appropriate values files each node.  If you use a mailer change the last line of the node#.bat file to reflect the name of your mailer batch file for nodes running the mailer.  Lines 3-5 of node#.bat are needed for BBSs running multiple dial in nodes. When we used them on our single line BBS running Wildcat 4.20 SL node 1 would not operate properly forcing us to rem them.

Setting Up the Wildcat Node Picks

Create a folder on your start menu called BBS Nodes.  In it create a pick for each Wildcat node using the node#.bat files as the command lines. Modify the picks to include the following settings for each tab.

General

Nothing gets changed here.

Shortcut

     Cmd Line: NODE#.BAT
       Working: C:\WILDCAT
   Batch  File:
Shortcut Key: None

Font

Change the settings here to match your preferences.

Memory

Set the Conventional, EMS, XMS, and MS-DOS protected mode settings to Auto.  Place a check in the Uses HMA box.  Do not place a check in the Protected box.

Screen

Set the Usage pick to your preference and the Initial size to Default. Place a check in the Display toolbar, restore settings on startup, fast ROM emulation, and dynamic memory allocation boxes.

Misc

Set Idle Sensitivity to low by moving the slider as fart to the left as you can.  Place a check in the Fast pasting box.  Place a check in each of the Windows Shortcut key boxes.  Do not place a check in the Allow screen saver, QuickEdit, Exclusive Mode, Always Suspend, and Warn if still active boxes.  When the picks are modified copy those for nodes that are to be active all of the time to your startup folder.

Modifying Your Wildcat Event and Door Batch Files Configurations

If your BBS was running with only one node previously you will need to modify your event and door batch files to work with any new multi line setup.  Only one event batch file, the one that runs wcPACK needs to be modified.  It must be setup to run wcPACK with all nodes except the one it is run from down or in maintenance mode as it cannot pack conference 0 otherwise.  To do this modify your wcpack batch file to read some thing like this:

cd \wildcat
wcnode /r 1
wcwait/S:25
wcpack 0
wcnode /w  1
wcpack 1-73

Line 2 places all nodes except the one running the event in maintenance mode.  Line 3 waits 25 seconds to give the nodes time to get into maintenance mode.  Line 4 packs conference 0.  Line 5 wakes up all of the nodes not running the event.  Line 6 packs all conferences other than conference 0.

Your door batch files must be modified for multi line use.  Before you modify them find out which doors are multi user and set the multi user flags for these doors in makewild to yes.  For doors which do not require separate configuration files change the path for door.sys in the configuration file to
C:\WILDCAT\WCWORK\NODE%WCNODEID%\DOOR.SYS.
For doors which require separate configuration files create configuration files for each node and modify the batch files to be similar to the one below that we have for "In the Year 2151".  Once this is done your doors should work on all nodes even node 0.  The only exception I have found is Immortal Combat which won't let you specify a node number of 0 when prompted for one in the configuration editor.

Sample Batch File for Door Which Requires Separate Configuration Files

rem this batch file runs the 2151 Door program set up as door 2
ECHO OFF
CLS
CD\DOORS\2151
2151 2151%WCNODEID%.CFG

Lila Godel's Web Site
Brought To You By Hamilton Services, Inc.