home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Beijing Paradise BBS Backup
/
PARADISE.ISO
/
software
/
BBSDOORW
/
SCHT503R.ZIP
/
INST!TAG.DOC
< prev
next >
Wrap
Text File
|
1993-04-02
|
2KB
|
66 lines
Tag BBS Installation
────────────────────
Installation
────────────
The following instructions explain how to install SabreChat!
onto your system. Note that this installation must be done as so:
1. unzip the SabreChat! package into a \SCHAT directory.
2. you will need to set the environment variable S!NODE to point
to the multi-user data path, and set the variable S!EXE to point
to the directory with all the SCHAT! files in it. If the two
paths are the same you can leave out the S!EXE variable. I would
suggest puting these lines in the AUTOEXEC.BAT.
Here is an example:
SET S!NODE=C:\MULTI
SET S!NODE=C:\SCHAT
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. now you will have to set up a door call. SabreChat! basically
requires only two things.
1) the path to the DOOR.SYS file for this node
2) this node number
You set up the call like this:
C:\SCHAT\SCHAT!.EXE Y<path to DOOR.SYS> N<node number>
5. To configure Schat to work with T.A.G.'s menu system make sure
that the following are specified:
For Tag's Program Key (PKEY): "="
For Tag's Program Data (PDATA): "Schat" (or whatever the name of
the .bat file used to call Schat will be)
6. You will need to reboot the computer so that the changes to
AUTOEXEC.BAT will take place.
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.