                            ,=-=-=-=-=-,
                            "  RaWKoS  "
                            '=-=-=-=-=-'
                            -=PUB CHAT=-
 There are 2 example startup batch files in the archive STARTBAT.ZIP
 1 for bbs's that can pass the node number to the batch file 
 and one for spitfire type bbs's

 Specifically, RemoteAccess, and PCBoard, although this door works
 on almost _all_ BBS types

 for further help, read on...
 
 INSTALLATION  
 ------------                                             
  Create a Directory for the Rawkos Files and
  Copy all the files into that Directory


  there are 3 different versions of rawkos.exe
  raw3ra.exe, rawpcb.exe, and raw3bare.exe

  Although it was possible to incorporate all the routines for these
  3 types into 1 exe, I thought memory would be more beneficial than
  a little Hard Drive space...


  by default, RAWKOS.EXE is actually RAW3RA.EXE
  this is the version for remoteaccess.


  If you are using PCBoard, then type :-
  COPY RAW3PCB.EXE RAWKOS.EXE

  If you are using a different type of BBS Software, then type :-
  COPY RAW3BARE.EXE RAWKOS.EXE

  Edit the RAWKOS.CFG File

  CREATE Copies of RAWKOS.CTL and name them RAWKOS1.CTL, RAWKOS2.CTL
  1 for each node you use, and edit each of these

  Edit one of the startup batch files in StartBat.ZIP 
   or create your own that better suits your bbs requirements,
   and place it where your BBS can call it -
   call this file with RAWKOS.BAT <node> if possible, otherwise
   it may be necessary to create a batch file for all nodes.
   such as the SFSTART.BAT file in STARTBAT.ZIP


OR  If you prefer, there is a RAWKOS environment variable you can set
--  to avoid using a batch file.


set the environment variable as follows

SET RAWKOS=C:\RAWKOS

then you can simply call rawkos from anywhere without
changing to the rawkos directory by typing

C:\RAWKOS\RAWKOS.exe <node>.....etc...etc


If the door exits when more than 1 node are on, try changing the
two numbers 20 and 400 in lines 4 & 5 of RAWKOS.CFG to a higher number
eg, 300 400. Otherwise read b4uask.doc
