home *** CD-ROM | disk | FTP | other *** search
- TriAutoPost v1.2
- (c) 1993 By Hugues Scarlata
- For TriBBS v5.x
- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=-
-
- DISCLAIMER:
- I relinquish any and all responsability for anything that may
- occur due to the use of this program, correctly or incorrectly.
- I am in no way libel for any damage that is attributed to the
- use of this program by any and all persons.
-
- WHAT IT IS:
- TriAutoPost is a simple Door for TriBBS boards, that will allow
- your users to send Auto Messages that will be read by all the
- callers, when they log on, until the Auto Message is changed.
-
- INSTALLING TRIAUTOPOST:
- Installation of TriAutoPost is very easy, make a new directory
- that will contain all the files contained in this archive. The
- next step is to create a configuration file, you can call it
- whatever you want. The configuration file is a plain ASCII text
- file and should follow the following format:
-
- Line 1: Door data file type.
- Line 2: Path to the door data file(s).
- Line 3: BBS Name.
- Line 4: Sysop's name.
- Line 5: Locked baud rate.
- Line 6: Path and name for the @-Codes screen.
- Line 7: Tells TriAutoPost if it should use aliases.
- Line 8: Tells TriAutoPost if it should create a log.
-
- As illustrated above, the door data file type is specified in
- Line 1 and can be PCB for PCBoard, GAP for GAP (DOOR.SYS), SF
- for SpitFire, RBBS for RBBS, WC for WildCat!, TRIBBS for TriBBS
- or WWIV for WWIV. The locked baud rate is specified on line 5.
- If you don't lock your serial port, you must specify 0 for the
- locked baud rate. NOTE: Although many door formats do pass the
- locked baud rate in the door data files, some older formats
- such as RBBS do not. For conformity, TriAutoPost requires that
- you specify the locked baud rate in line 5 and ignores any
- value passed in the door data files.
- Line 6 is the path and name of the screen that TriAutoPost will
- create. @-Color Codes will be used in the screen, so you only
- need to specify the path of the .BBS screen.
- Line 7 should be Y if you want TriAutoPost to use the caller's
- alias, or N to use the caller's real name.
- Line 8 should be Y if you want TriAutoPost to create a log of
- all the messages that have been sent, this file will be called
- AUTOPOST.LOG. If you don't want to use this feature, put a N
- instead.
-
- The following is a sample door configuration file:
-
- TRIBBS
- C:\TRIBBS
- Player One
- Hugues Scarlata
- 38400
- C:\TRIBBS\DISPLAY\LOGON3.BBS
- N
- Y
-
- RUNNING TRIAUTOPOST:
- To run TriAutoPost you must create a batch file that will
- change to the directory where TriAutoPost is installed,
- run the door, and load back the board.
-
- This is an example batch file:
-
- @ECHO OFF
- CD\AUTOPOST
- AUTOPOST AUTOPOST.CFG
- CD\TRIBBS
- BOARD
-
- TriAutoPost can be run locally without a door data file, by
- specifying LOCAL after the configuration file parameter in the
- DOS command line.
-
- Example:
-
- AUTOPOST AUTOPOST.CFG LOCAL
-
- SUPPORT:
- The fastest way to contact me is by leaving a message
- on my board:
-
- Player One - (301) 299-1196 - 14400 v.32bis
-
- I can also be reached on:
-
- * The 3rd Party Support Conference on the WME Network.
-
- * CompuServe: 75720,1411
-
- * America OnLine: DJ Snoop
-
- * Prodigy: RPGC44A
-
- -----------------------------------------------------------------------------
- Files included in TAPST12.ZIP (Or ARJ, LZH...)
-
- AUTOPOST.EXE : The TriAutoPost Program.
- AUTOPOST.CFG : Sample Configuration File.
- TAPST12.DOC : TriAutoPost 1.2 Documentation (this file)
- FILE_ID.DIZ : Description File.
- DESC.SDI : Description File.
- P1AD.EXE : Ad for Player One BBS (Run It!!! <G> )
- README.1ST : As the name says, read it first! :)
- HISTORY.DOC : TriAutoPost Versions History.
- -----------------------------------------------------------------------------
-
- TriAutoPost was compiled with Turbo C++ 3.0 and TriDoor 1.22 (By Mark Goodwin)
-
-
- Thanks For Using TriAutoPost!!!
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-