OnLine Text Reader
v2.7
November 18, 1995
PCBoard 14.x and GAP 4.x
WILDCAT!, Spitfire
QBBS, RBBS, RA
by
Dennis Maidon
PAROLE Software
9411 Buffalo Rd
Clayton, NC 27520
(919) 965-3600 -> Voice
The Parole Board BBS
Fido: 1:151/185 @fidonet
(919) 965-4696 -> US Robotics Dual Standard
(919) 965-9885 -> US Robotics Dual Standard
Copyright 1992-95, PAROLE Software
All rights reserved
I don't believe in CRIPPLEWARE and as such will not support it in
Door programs. If the author doesn't believe that it is good enough
that SysOps will register it unless it is crippled then I don't have
enough faith to even try it.
This ZIP file was created using the -AV function of PKZIP. If
my AV is missing then this file may not be complete of has been
tampered with. Complete and current editions of this program
are always available for D/L on The Parole Board BBS. If the AV
is missing please complain to your sysop to stop the practice of
removing AV's as this is your assurance from the programmer that
the file is complete and virus free.
INSTALLATION
____________
Installation is fairly easy and straight-forward. The following steps and
examples should have you up and running in a very short period of time.
It is assumed that you are familiar with setting up DOORS on your system.
To this end, only examples of the configuration file and Door batch file
are described.
1) Create a directory to hold all OLTR files
2) Unzip OLTR-Vx.ZIP into the the above directory OLTR no longer
requires a BRUN module.
3) Create a configuration file, with a name of your choice, or
modify the OLTR.CFG file that is enclosed.
A description follows:
C:\WILDCAT\CALLINFO.BBS ──┐ <- For Wildcat! 2.xx
C:\WC\WCWORK\NODE1\USERINFO.DAT │ <- For Wildcat! 3.xx
C:\PCB\PCBOARD.SYS │ <- For PCBoard using PCBOARD.SYS only
C:\PCB\USERS │ <- For PCBoard using USERS only
C:\BBS\GTUSER.BBS │ <- For GT Power systems
C:\BBS\DOOR.SYS │ <- For Systems that support DOOR.SYS
C:\BBS\DORINFOx.DEF │ <- For QBBS/RBB/RA. Replace x with Node #.
C:\BBS\SFDOORS.DAT │ <- For Spitfire
C:\BBS\TRIBBS.SYS │ <- For TriBBS
C:\BBS\CHAIN.TXT ───┘ <- For WWIV
The Parole Board BBS <- Your BBS Name
Dennis <- SysOp's First Name
Maidon <- SysOp's Last Name
0^Child's Play ───┐ <- Lines 5 - 10 are used to set
200^Adult Files │ <- the minimum security level to
100^BBS Information │ <- access the door and for the
1000^Sensual Delights │ <- individual directory titles.
500^Public Record │ <- All 6 directories must be
35^Local Gossip ───┘ <- created.
14 <- Default text color
NOTE: There are 2 additional lines necessary when using GTUSER.BBS. Since
this file does not provide the ComPort% and NodeNum% variables, advise
your Door users to add them to this .CFG file on lines 5 and 6
respectively. Both variables will default to 1.
Edit this .CFG file to suit your individual BBS. All 11 lines MUST
be present.
Line 1: This line points to where OLTR.EXE will find the callers
information file. Just include the line that your particular
BBS uses. DO NOT put all of them in the CFG file.
Line 2: Place the name of your BBS on this line.
Line 3: SysOp's first name goes here.
Line 4: SysOp's last name goes here.
Line 5: Registration number (if registered)
Lines 6 - 10 : These lines must be in a special format.
Line 11: Default text color (Codes below)
COLOR # - NAME
---------------
0 - BLACK 9 - LBLUE
1 - BLUE 10 - LGREEN
2 - GREEN 11 - LCYAN
3 - CYAN 12 - LRED
4 - RED 13 - LMAGENTA
5 - MAGENTA 14 - LYELLOW
6 - YELLOW 15 - LWHITE
7 - WHITE
These last 6 lines are where you enter the Text file directory
names. The door will allow 6 individual directories with each
one having it's own minimum security level access. The format
is as follows : 1000^Sensual Delights
│ │ │
┌───────────────────────┘ └"^"divider └Category Title
└Minimum security level to access area
The first part of the line is the minimum security
level that will be able to access that menu. You
will be able to have Adult files mixed in with the
General Files and limit the access to either on.
Just be sure that your Adult Security Access number
is higher than the General. <G> The "^" is the
marker that OLTR looks for to separate the number
from the title. The last part of the line is the
title of that particular Menu. Users will be able to
see all of the menu titles but will only have access
to the ones that you specify. The following screen
is a sample of the Menu that your users will see.
╒═══════════════════════════════╡ MAIN MENU ╞════════════════════════════════╕
│╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬│
│╬╬╬╒══════════════════════════╡ CATEGORIES ╞═══════════════════════════╕╬╬╬╬│
│╬╬╬│ │╬╬╬╬│
│╬╬╬│ 1. Child's Play (0) 4. Sensual Delights (1000) │╬╬╬╬│
│╬╬╬│ 2. Adult Files (200) 5. Public Record (500) │╬╬╬╬│
│╬╬╬│ 3. BBS Information (100) 6. Public Record (25) │╬╬╬╬│
│╬╬╬╘═════════════════════════════════════════════════════════════════════╛╬╬╬╬│
│╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬│
│╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬│
╘══════════════════════════════════════════════════════════════════════════════╛
Security Level : 155
Please select one (1) category [ 1 - 6 <Q>uit <R>edraw ] :
The numbers following the directory titles are the minimum security
levels that are needed to access the particular files in that
directory. Users are also informed of their security level by a
line just below the Menu.
You must use an ASCii editor to modify the CFG file and such. Most word
processors leave imbedded control codes which could cause the door to
fail to operate.
4) Create a batch file or modify the OLTR file supplied. A
description of this file follows:
ECHO off
CD \DOORS\ESP Location of OLTR files
OLTR OLTR.CFG The OLTR Door Program
5) When running in more than one node, be sure to supply a
different configuration name for each node (your choice of name).
OLTR has been tested under LIVECAT! and performs very well.
6) You will need to create 6 directories in the OLTR directory.
They must be named as follows. TEXT1, TEXT2, TEXT3, TEXT4,
TEXT5, and TEXT6. In each directory there must be a file
named "MENU.DAT". This file contains the text file titles as
well as the actual DOS filename. It also has a special format
that must be followed.
EXAMPLE : Mustang buys Tomcat!^msi_tech.txt
The first part of each entry is the title of the text file.
The "^" is once again the separator that the door looks for.
The last part of the entry is the actual DOS filename that will
be displayed when the user selects the file.
Directory Setup:
To set the door up, you will need to put the OLTR.EXE file in a
directory of it's own. You will need to create 7 sub-directories under
the main directory. The main dir may have any name your lil ol' heart
desires BUT, the 7 sub-dirs MUST be named as follows:
\SCREENS This sub-dir must contain the display files.
\TEXT1 ─┐
\TEXT2 │
\TEXT3 ├These sub-dirs contain the text files and MENU.DAT files
\TEXT4 │
\TEXT5 │
\TEXT6 ─┘
\TEXT1 = Line 6 CFG file
\TEXT2 = Line 7
\TEXT3 = Line 8
\TEXT4 = Line 9
\TEXT5 = Line 10
\TEXT6 = Line 11
You may have six (6) directories with 10 text files in each one.
If there is a need for it, I will add more directories and/or allow
more files in each directory.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Now!, comes the exciting part. <G> In the past the text was displayed
as all white. With this release you may change the overall color. You
may take that one step farther. There are special color codes that you
may use to change all or parts of a line. They are as follows:
~ = Blue ' = Green @ = Cyan ^ = Red
| = Magenta { = Yellow } = White
* = Low Intensity
% = Blink
The color codes must be in pairs and on the same line.
^Steve Sambor^ = Will display in Bright Red
Add a % in front of the first ^ and it will blink bright red. Put a *%
and it will blink in low intensity red. You may use several of the
pairs on each line of the file. This feature will allow you to spice up
the display just a bit. Be creative, go "Hog Wild" as we Rebs would
say. <GRIN> BTW, The color codes will also work with the Special
Message on Line #10 of the CFG file.
There is a ZIP file within this archive that contains a WELCOME.ANS & a
WELCOME.ASC screen. If you would like to use them, place them in the
door directory. RREAD.EXE will auto-detect the presence of these files
and adjust the opening screen accordingly. You can use 'em if ya like.
If you prefer to make your own, they MUST contain the same number of
lines that the original ones have.
The user will be given the opportunity to switch his color mode once in
the door. If they have color, they will also be given the opportunity
to set their own text color preference. The special color codes that
you place in the text file will be unchanged.
NOTE: OLTR supports COM 1-4 on the standard IRQ's - COM1/COM3 = IRQ4 and
COM2/COM4 = IRQ3. If you wish to use a non-standard IRQ, add the IRQ
number after the configuration filename. Let's assume your Door is
called FOOBAR and you want to use COM1 and IRQ5. The command line
passed to your Door would be:
FOOBAR FOOBAR.CFG /5
The /5 tells OLTR to use IRQ5 rather than the standard IRQ4 that
is normally used with COM1. No /x parameter is needed for the standard
IRQ's.
Fossil Driver Support
---------------------
DoorFrame supports the use of Fossil drivers. To tell your Door to use the
Fossil driver instead of the standard COM ports, just put /FD on the command
line when running the door. For example:
MYDOOR MYDOOR.CFG /FD
indicates that a Fossil driver is present and should be used. If no Fossil
driver is detected, DoorFrame will print a message to that effect and exit
the door gracefully.
LIVECAT! USERS
If you are using LIVECAT! to control your doors you will need to
make one small change in your door.bat file. LC! changes DOOR.SYS to
DOOR.ORG when it shells out to the door. You will need to add a line in
your script COPY DOOR.ORG DOOR.SYS. If you don't do this, OLTR just
gives up and dies a very unhappy death. I don't go back and delete it
when OLTR finishes and I haven't had any problems with it. If you do,
you might like to delete the DOOR.SYS just as soon as OLTR finishes
running.
If you have upgraded to LC! 3.5, this problem has been fixed and the
copying of DOOR.ORG is no loner necessary.
LEGALITIES
__________
THIS SOFTWARE AND ACCOMPANYING MATERIALS ARE DISTRIBUTED "AS IS"
WITHOUT WARRANTY, EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT
LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL ANYONE INVOLVED WITH
THE CREATION AND PRODUCTION OF THIS PRODUCT BE LIABLE FOR INDIRECT,
SPECIAL, OR CONSEQUENTIAL DAMAGES, ARISING OUT OF ANY USE THEREOF
OR BREACH OF ANY WARRANTY.
DISTRIBUTION
____________
You may make this file available for downloading from your BBS or you may
upload it to any BBS of your choice, provided that you do not make any
changes to the contents of the archive (ZIP file). The archive and its
individual contents may not be used by any service that charges any money
whatsoever, without the written permission of the author.
THANKS
--------------
Special thanks goes out for my wife who is definitely a
"Computer Widow".
Ted Freeman the author of DOORFRAME, a first class BBS Doors
Development Library.
My BBS users who have had to endure constant badgering to help me
test the programs that I have written.
Mustang Software, authors of the most versatile BBS program ever
created.
Liane Benway of Running Wild!!! BBS in Georgia. Her inspiration and
thoughtful guidance helped to make this door possible.
Steve Sambor of Land of the Unicorns!. His assistance helped make
some of these options possible.
OLTR is Copyright 1992-95, PAROLE Software. All rights reserved.