home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
ra
/
scht503r.zip
/
INST!WC.DOC
< prev
next >
Wrap
Text File
|
1993-04-02
|
3KB
|
72 lines
Wildcat 3.x Installation Instructions
─────────────────────────────────────
Installation
────────────
The following instructions explain how to install SabreChat!
onto your system. Note that this installation assumes the
following directory structure:
C:\
┐
├─\WC30
│ │
. ├─\DATA
. │
└─\WCWORK
│
├─\NODE1
│
├─\NODE2
│
.
.
If you have installed Wildcat using different pathnames then
you will have to modify the instructions accordingly.
1. unzip the SabreChat! package into a C:\SCHAT directory or any
door directory you might wish. The rest of this installation
will assume that you are using C:\SCHAT, if you use something
different just replace C:\SCHAT with the path given here.
2. add the line 'SET S!NODE=C:\WC30\DATA' to your AUTOEXEC.BAT.
add the line 'SET S!EXE=C:\SCHAT' or the directory you
unzipped SabreChat! into in #1.
3. add the line 'C:\SCHAT\SMIXER! N2' to your AUTOEXEC.BAT.
note that the parameter N needs to be set to the highest
node number on the whole system. (example: for nodes 1,2,5
you would use N5 instead of N3). For additional
information please see the SMIXER!.DOC that was included in the
archive.
4. set up your MAIN1.RUN or MAIN2.RUN file as follows:
C:\SCHAT\SCHAT!.EXE YC:\WC30\WCWORK\NODE%wcnodeid%
5. In MakeWild, under the setup menu, raise the level of
access on Wildcat's internal Chat function so users no
longer have access to it. Next, enable one of your DOS
hooks on the main menu (either 1 or 2 depending on the name
of your MAINx.RUN file) and assign it the letter T (or
anything you wish). Under the DOOR setup options menu in
MakeWild, be sure to make this hook multi-user.
If everything is in order then you should have a working
version of SabreChat!. I would check everything now and make
sure that all is working. Afterwards, you may customize
SabreChat! to better fit your specific online needs...
TroubleShooting
───────────────
Here's a few tips that may help with problems that arise
after a while. If you start getting 'ghost' users or
conferences, try deleting all the *.SWD files.