home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
MISC
/
QCHT100.ZIP
/
QCHAT.DOC
< prev
next >
Wrap
Text File
|
1998-03-04
|
73KB
|
1,658 lines
┌──────┐┌─────┐┌───┐┌──┐┌───────┐┌───────┐
│░▒┌┐░▒││░▒▓┌─┘│░▒▓││░▒││░▒▓┌┐░▒│└─┐░▒▓┌─┘
│▒▓││▒▓││▒▓█│ │▒▓█└┘▒▓││▒▓█││▒▓│ │▒▓█│
│▓█││▓█││▓██│ │▓██┌┐▓█││▓██└┘▓█│ │▓██│
│██└┘██││███└─┐│███││██││███┌┐██│ │███│
└──────\└─────┘└───┘└──┘└───┘└──┘ └───┘
Deluxe Splitscreen ANSI/ASCII Chat Utility
For QuickBBS, RemoteAccess, ProBoard v2.xx
and any Dorinfo1.Def & Door.Sys Compatibles
v1.00 Release Date: 03/02/98
─────────────────────────────────────────────────────────────────────────────
QChat v1.00 Copyright Matrix Technologies, 1993-98 QChat v1.00
─────────────────────────────────────────────────────────────────────────────
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Some Of QChat's Features ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
{+} Indicates registered only.
* QChat is a split screen chat utility for QuickBBS, RemoteAccess,
ProBoard and many other BBS types as long as they support Dorinfo1.Def
and Door.Sys type Doors.
* QChat support 10, that's TEN different TOTALLY configurable chat
screens!
* QChat has a special chatmode for ASCII users.
* QChat has file transfer support!
{+} QChat allows the users to post a comment in the area of the SysOps
Choice. It requires an external message editor for this purpose. This
function requires the Hudson or Jambase message Base type to work.
* If the SysOp doesn't answer the page, and you are using RA/PB
QChat will update the [Wants Chat] flag causing it to be activated
on the SysOps status line, and the users total number of pages for
the call will be incremented. This is ONLY possible when using RA,
generic Dorinfo1.Def systems are not supported by this feature.
* Configurable Emergency page option, password protected. This is
activated when a user has paged outside of paging hours. If they
chose to emergency page, they must enter a password. This can be
disabled by leaving password blank when configuring QChat. It can
also be configured so that only users ABOVE a set security level
will be asked for the emergency page password.
* QChat v1.00 will seek out Remoteaccess 2.xx and read in crucial
information from the BBS configuration to make QChat v1.00 even
easier to install than it already is.
* A configurable page tune for those users that are in your VIP.CTL
Textfile
* QChat is Easily configured, unlike many programs SysOp's have to deal
with.
* Online User Editor : QChat has an Online User Editor Built in so that
the SysOp can edit the users Profile without having to exit back to the
BBS. (RA/PB Compatible)
* Can play random page tunes
* Defined Macro Listing in Chat
* And MUCH MORE!!
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Setting Up QChat Using ChatCfg.Exe ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
To Setup QChat, please read this section thoroughly! Then also read the
section of these documents that apply to the Installation of QChat into
the particular type of BBS system you are running (i.e. QuickBBS, RA, TG
etc)
Note:
Menu items that are followed by '{+}' are REGISTERED ONLY features, and
will not be active until you have registered QChat and obtained a valid
key.
When you run CHATCFG.EXE, you will be presented with a series of pulldown
menus. In this section we will step through each menu in turn and explain
in some detail what you need to enter in order that QChat will be
configured correctly. The cursor keys are used to move around the
configuration program, left and right will move between the various
pulldown menus, and the up and down keys will step through the items on
each menu or submenu.
────────
SYSTEM
────────
· Save & Exit - Selecting this option will save any changes you have made
and exit to Dos.
· Exit Without Save - Exit ChatCfg, but DO NOT save any changes made.
· Operator Names -
· BBS Name - Enter the name of your BBS system.
· SysOp Real Name - The name of the System operator. If you are a
registered user of QChat, this name MUST be exactly the same as the
name that appears in the registration key.
· SysOp Alias - System operators Alias (if used). If this is enabled,
QChat will use the Users alias aswell.
· CoSysOp 1-3 Names - Enter up to 3 Co-SysOps in these fields. To select
a CoSysop for Chat, run QChat with a parameter ranging from A-C, or
you may select the CoSysOp for chat from within QChat while the
pagetune is playing.
i.e. QChat.Exe /A - would cause QChat to use the #1 Co-Sysops
name instead of the SysOp's name.
OR You may press 1,2 or 3 while the page is playing to select a CoSysOp
for chat.
· External Filenames -
· MsgBase Path {+} - Path to your message base, i.e. C:\QuickBBS\MSGBASE
NOTE TO RA SYSOPS:
QChat DOES support the JAM message base at this time. The area
selected for QChat to post messages into MUST be specifically
configured to be either a HUDSON base OR a JAM Base.
· Chat Log Path - The path and filename of the chat conversation log, if
enabled.
· Logfile Path - The path and filename of the logfile QChat should use.
This can either be a seperate logfile, or QChat can append to your BBS
logfile if you so choose.
· External Editor {+} - The full path and command line of the external
message editor you want to use such as QuikEdit. This will be called
whenever a user leaves a message to the SysOp when a page has not been
answered. Please refer to the documentation for the message editor of
your choice for details of the required command line.
· External DOS Util - When shelling to DOS using the Alt-J function within
QChat, you have the ability to call up a program automatically by
enabling this option.
If you enter the path and filename of a DOS utility, when you shell
to DOS QChat will ask if you want to invoke your Dos program - You
can then select 'Y' to run it, or 'N' to go straight to Dos.
If you leave this field blank QChat will just shell to Dos as
normal, you will NOT be asked to press Y/N.
· Regular Pagetune - The path and filename the 'Normal' pagetune to be
used by QChat (i.e. C:\QuickBBS\QChat\Page.Ice).
· VIP Pagetune - The path and filename of the 'VIP' pagetune to be used
by QChat (i.e. C:\QuickBBS\QChat\Vip.Ice).
This tune is used for VIP users who's names are stored in an ASCII
control file called VIP.CTL. See the section of these docs about
the Files Used and Created by QChat for more info on this file.
· Transfer Protocols -
· Protocol - Enter the name of the external protocol you are using.
· Send - Enter the path and filename of batchfile or external program
which will be used to send user files.
· Receive - Enter the path and filename of batchfile or external program
which will be used to recieve incoming files.
· Trigger - Enter the code or string that QChat should interpret as
a remote protocol attempt to transfer files.
· Auto Upload YES/NO - Should QChat automatically activate the inbound
commandline when trigger is detected.
· Confirm YES/NO - If Auto upload is activated, should QChat quickly
prompt SysOp for confirmation.
· ANSI bulletins
· Page Header - File displayed to user when QChat is first activated.
· Not Available - File displayed to user when SysOp doesn't answer the
page.
· Out Of Hours - File displayed to user when they have paged outside of
scheduled paging hours.
· Page Exceeded - File displayed to user when they have paged too many
times.
· Page Warning - File displayed to user when they are about to exceed
maximum number of pages.
· Page Hangup - File displayed to user when they are going to be hung up
on for paging excessively.
· Finished Chat - File displayed to user when they have completed a chat
session.
· Language Editor
NOTE: QChat now has the ability to use a number of macro characters that
will be translated when it is run. These can be used in the various
'Strings' that can be displayed to the user. See the seperate section
of these docs for more info on the macros and their usage.
· Greetings String - String displayed to users when the SysOp first enters
chat. This string will only be shown once per program execution. Leave
blank to disable.
· User Editor String - String displayed to users when the user record is
being altered, by using the built in user editor in QChat (RA/PB only).
· ASCII Dump String - String displayed to users when SysOp is preparing
to view an ASCII file.
· Drop To Dos String - String to be displayed to users when the SysOp
Drops To DOS.
· SysOp Help String - String displayed to users when SysOp is viewing
local help window by pressing F1 (Function key F1) when in Chat.
· Page SysOp String - Enter the string displayed to users when paging the
sysop.
· Page Reason Header - Reason for page header. i.e. "Why do you want to
chat with Benjamin?"
· Message String - The string to be displayed when QChat asks if the
user wants to enter a message to the SysOp if the chat request is
unanswered. If you are unregistered, make this a statement such as
"Why Not Leave The SysOp A Message?". If you are registered, make this
a question such as "Would You Like To Leave The SysOp A Message? ".
· "Not Here" String - The String to be displayed when either 1) The page
expires when the SysOp doesn't answer it. 2) The SysOp has defined the
user as a "quiet user".
· "Page Time" String - The string to be displayed when the user pages
outside of scheduled hours, before a time slot later in the day.
· "Tomorrow" String - The string to be displayed when there are no more
page slots left in the day.
· Template Manager - With QChat, it is possible to define up to 10
COMPLETELY CONFIGURABLE chat screens. Use the template manager to
define window dimensions and clock locations. When in QChat, you can
call up each of these screens with the ALT-Fx keys. The corresponding
Template ANSi will be displayed.
This chart is the Template Manager. Use it to configure all of the above
fields.
Screen File - Full path and filename to the ANSI template file.
Clock Type - Choose between DISABLED, 12 HOUR, and 24 HOUR clocks.
- Position - Choose clock X,Y co-ordinates
- Colors - Choose clock foreground,background colors
Date Type - Choose between DISABLED, and 4 different date formats.
- Position - Choose date X,Y co-ordinates
- Colors - Choose date foreground,background colors
Timer - Choose either DISABLED, or ENABLED toggles.
- Position - Choose timer X,Y co-ordinates
- Colors - Choose timer foreground,background colors
Window 1 + 2 Setup -
- Boundaries - Select top-right corner of window, and then
bottom left corner of window. Leave a minimum
of 4 LINES in window.
- Name Position - Where should the sysop/user name be displayed?
Leave as 0,0 to have the name centred on the
top border of the window.
- Max. Name Length - Enter maximum name length. Any names which
exceed this value will be truncated.
- Colors - Configure name and window background color.
Additionally, it is possible to alter a template record WITHOUT using
the template manager. In order to create a screen layout, it is usually
necessary to either create the screen, and record the necessary location
values to be later entered into the manager, OR create the screen in the
manager FIRST, and then design your custom ANSI after.
It is now possible to combine the two steps. If you create an ANSI with
special SCREEN LOCATION CODES, QChat will automatically import the
cursor locations into the template manager, leaving only simple
preferences such as color configuration for you to deal with.
The following are screen location codes which QChat will import, if
configured to do so.
^R1 Sysop Window X1,Y1 location (top left)
^R2 Sysop Window X2,Y2 location (bottom right)
^R3 Sysop name location (X,Y)
^R4 User Window X1,Y1 location (top left)
^R5 User Window X2,Y2 location (bottom right)
^R6 User name location (X,Y)
^R7 Clock location (X,Y)
^R8 Date location (X,Y)
^R9 Timer location (X,Y)
· Program Info - Gives detail of the current version of QChat including
release date and any crucial fixes.
─────────
TOGGLES
─────────
· Alias Usage - Should QChat use the SysOp's & User's alias as defined
above? Yes/No
· Force Greeting - Should QChat use the 'Greeting' string when a 'Forced'
chat is initiated by the SysOp.
· Suspend Time - Should QChat freeze the users time whilst in chat.
· Allow Remote Exit - Are users allowed to terminate a chat? If set to NO,
only the Sysop will be able to stop the chat by pressing [Esc] or Alt-X.
· Allow CTRL-G beep - Should users be allowed to beep with CTRL-G.
· Chat Logging Enabled - Should the conversational log be activated when
chat is initiated.
· Use 24 Hour Clock - Should QChat use the 24h clock in it's string
translations?
────────
COLORS
────────
Here you can define what colors QChat should use for various
types of text. You can select the color you prefer for any of the
following :
· .SYS represents the SYSOP window text color configuration
.USR represents the USER window text color configuration
· Punctuation · Numbers · Capital Letters · High Bit ASCII
· Reason Bar · SysOp Name · User Name · Time Clock
· Chat Timer · Status Line
· Default Settings - Selecting this option will restore QChat's 'Default'
colors.
Select the color you prefer by entering the number indicated in
ChatCfg.Exe. QChat will then use these colors when in chat.
────────────
PAGE SETUP
────────────
· Page Hours -
The page hour setup in QChat has been greatly improved since v3.60. In
previous versions, you could only have one time slot per day ranging from
an earlier hour to a later hour. Hours couldn't extend past midnight. This
was very inconvenient to those SysOps who are 'Nighthawks'. So, as of v1.00
a new system is in place. If you refer to the chart above, you can see that
the days of the week are listed at the left, and each hour of the day across
the top. Every square on the grid represents an hour of the day. The two
blocks within each square represents an half-hour slot. For Example:
╔══╤══╤
║00│01│ <-- Hour of the Day, Starting at midnight
╔══╬══╪══╪
Day Of Week --> ║Su║■■│■■
╚══╩══╧ ^----- Represents 1:30a to 2:00a.
^----- Represents 1:00a to 1:29a.
By toggling these little blocks on or off, you can configure as many half-
hour paging slots a day as you want, at whatever time is convenient for
you.
· Page Duration - How long (in seconds) QChat should page the sysop.
· Maximum Pages - How many times a user may page in one session. This
feature can only be used if RA is the BBS package.
· Page Reason Length - The minimum number of characters a user MUST enter
as a page reason. If the user enters LESS than this amount QChat will
exit and inform him/her that the reason is too short.
· Password required to page the sysop outside normal paging times. The
user will need to enter this password BEFORE QChat will call the SysOp,
in this way regular or trusted users can page you at any time. They MUST
also have a security level ABOVE the level set in 'Emergency Security'
for this feature to be used.
· Emergency Security - The MINIMUM security needed by a user before they
will be given the option to FORCE an 'Emergency Page' outside normal
paging hours. Users with a security BELOW this level will NOT be given
the option to page outside the normal hours. See also 'Emergency
Password', the two emergency options (Password and Security) work in
combination with each other.
· Configure Display -
· Reason Bar Color - Color of the page reason brackets
· Elapsed Character - The character which fills in time already elapsed
in the countdown bar.
· Elapsed Color - The color of the elapsed character.
· Remaining Character - The character which fill in the time which is
left in the countdown bar.
· Remaining Color - The color of the remaining character.
· Configure Toggles -
· User Page Warning - Should QChat warning user when they are paging
excessively.
· Exceeded; Hangup - Should QChat hangup on user when they have paged
excessively.
· Exceeded; Twitlist - Should QChat add user to the twitlist when they
have paged excessively.
· Beep Remotely - Should QChat beep remotely while paging.
· Use Countdown Bar - Should QChat use the countdown bar while paging.
· Fake Page - Should QChat fake the page when twit users run
QChat.
─────────────
MACRO SETUP
─────────────
· Macro Editor - This menu option will bring up a submenu that will ask
for a 'Keyword' and a 'Macro' that will be used in place of the 'Keyword'
as explained below. You can also configure the color that will be used
when these macros are displayed.
There are five pages available for you to enter macros. They are
explained below. Pages #2-#5 are ONLY available to registered users
of QChat, unregistered users are limited to one page.
- User Keyword - The word to be translated by QChat, i.e. QB
- Macro - The replacement to be used by QChat, i.e. QuickBBS
QChat has the ability to translate Macros when in Chat mode,
here you can enter the macro and what QChat should convert it
to. i.e. QB = QuickBBS. You will be asked for the original
word and then for the replacement, enter "QB" (as the original) and
QuickBBS (as the replacement) then whenever you type "QB" when
in chat mode, QChat will convert it to "QuickBBS" (without
Quotes). You have two pages in which you can enter any macros you
wish. It is useful to also place common mistyped words here too, i.e
TAHT (User Keyword) - THAT (Macro) then every time you accidentally
type 'Taht', QChat will convert it to 'That'.
Control strings may also be used in macros. For Example, if your
key word is "HT!" and the Macro is "Hi There @F!", when "HT!" is
typed in chat, it will be replaced with "Hi There Benjamin!" For
example. Available control strings are listed in a seperate section
of these documents.
With QChat, it is possible to use color codes into your macros.
This is very easily done. Wherever you would like to have a color
change in your message, type one of the following codes:
|00 - Black
|01 - Blue
|02 - Green
|03 - Cyan
|04 - Red
|05 - Magenta
|06 - Brown
|07 - LightGray
|08 - DarkGray
|09 - LightBlue
|10 - LightGreen
|11 - LightCyan
|12 - LightRed
|13 - LightMagenta
|14 - Yellow
|15 - White
- Color
Once you have entered a "User Keyword" and it's accompanying
"Macro" QChat will ask for a color. This is the color that the
Macro will be displayed in when in chat. An Asterisk (*) will show
the color you have selected.
· MacroFile Sorter - Allows you to sort macrofile in alphabetical order by
User Keyword, and will close any gaps in the macrofile.
· Macro Triggers - Configure punctuation which will trigger macros.
· Macro Toggles -
· View Macros YES/NO - Should users be able to list macros which are
available?
· Create Macros YES/NO - Should users be able to create their own macros?
· SysOp Window YES/NO - Should macro translation be active in the Sysop
window?
· User Window YES/NO - Should macro translation be active in the user
window?
──────────
MESSAGES
──────────
· Board Number {+} - The number of the message board as defined in your
BBS config. This only applies if you are using the HUDSON style message
base. If you are using JAMBASE, make sure you specify the full path and
filename of the JAMbase in the files setup.
· Message Flags {+} - Message Type - Private, Public, Or Both - Select the
message attribute. If set to 'Private/Public' QChat will ask if the
message is Public or Private before it is saved.
· Area Name {+} - Name of the message area used to post messages into if
the sysop does not respond to a chat request (or if he/she manually
aborts the request)
· Memo Comment - The string to be appended to messages left for the
sysop.
· Conditions -
· Out Of Hours YES/NO - Should users be allowed to leave comments when
they page out of hours.
· No Answer YES/NO - Should users be allowed to leave comments if the
sysop doesn't answer.
· Excessive Page YES/NO - Should users be allowed to leave comments if
they have paged excessively.
· Failed Password YES/NO- Should users be allowed to leave comments if
they've failed the emergency page password?
· Twit Page YES/NO - Should twits be allowed to leave comments?
· SysOp Abort YES/NO - Should users be allowed to leave comments if the
SysOp aborts the page?
· User Abort YES/NO - Should users be allowed to leave comments if they
abort the page?
───────
OTHER
───────
· Chat Border Type - Choose one out of a selection of three different
types of chat windows borders that you would like to use while chatting
with the user.
· BBS Type - Select the BBS software you are using. This is essential for
the correct operation of QChat.
- RA v2.xx/PB v2.xx
If you are using either RemoteAccess or ProBoard, this option should
be selected to give the most that QChat has to offer.
- Dorinfo1.Def Compatible
If you are not using RA, QChat can still use the generic
Dorinfo1.Def file which is generated by *most* BBS packages. Check
your BBS documentation to see if it can generate a Dorinfo1.Def
file.
- Door.Sys Compatible
If you are not using RA, QChat can still use the generic
Door.Sys file which is generated by *most* BBS packages. Check
your BBS documentation to see if it can generate a Door.Sys
file.
· Name Brackets - Select the brackets ( {([ ) that will be used when
displaying the SysOp's or Users name in QChat.
Please note that the configuration file is not a text file, so you
MUST use CHATCFG.EXE to configure the program, and the configuration file
Must be named QCHAT.CFG.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Upgrading From IceChat v4.40 to QChat v1.00 ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
This couldn't be easier!
Simply copy the files from the v1.00 distribution archive into the
directory you have QChat installed and run CHATCFG.EXE. This will
upgrade all of the previous version's configuration to the format needed
by v1.00.
Please Note!
Failure to upgrade your previous configuration files will result in an
error message being displayed if you attempt to run ChatCfg.Exe or
QChat.Exe.
You should also step through each of the pulldown menus in CHATCFG to
ensure your setup is correct.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Installing QChat Into RA v2.xx Systems ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
Please read the section of this document entitled 'Setting Up QChat Using
ChatCfg.Exe' BEFORE attempting to install QChat into RA. Failure to setup
QChat correctly before installing it into your bbs program will probably
result in QChat failing to run or not running as expected.
If you are using RemoteAccess or ProBoard, and you wish to take advantage
of the added features for these BBS Packages, you MUST be running
RemoteAccess v2.xx, ProBoard v2.xx or above. QChat's added features will
not work properly with older versions of these software packages.
In order to run QChat.Exe, you must have a fossil driver active. A fossil
driver such as BNU should work fine with QChat. If you don't have a
fossil driver installed, a simple error message will be displayed, and the
program will stop. A fossil is not required when running in local mode.
We will now run through EVERYTHING you need to do in order to get QChat
to run in your RemoteAccess setup.
1. Extract all the files in the distribution archive to a directory of
your choice. C:\RA\QCHAT is recommended and is assumed to be
the directory you are using from now on.
2. To help QChat find it's configuration files, you need to define an
environment variable for it in this manner in your AutoExec.Bat :
SET QCHAT={PATH TO QCHAT DIRECTORY}
The environment variable is used by QChat to find its system files
and configuration. Failure to setup the environment variable can result
in QChat failing to run correctly - YOU HAVE BEEN WARNED!
Please see your DOS manual for more information on environment variables.
NOTE:
You will need to reboot your machine after entering the environment
variable for it to take effect.
3. Run ChatCfg.Exe and configure all of QChat's options as explained
earlier in this document. You MUST configure QChat for it to work
correctly! Refer to the section of this document for setting up QChat.
4. You will now need to edit your .MNU files to include QChat so that
when a user pages you it will execute QChat instead of the internal
chat routine built into RemoteAccess.
QChat can be run using either a type 7 or a type 15 menu command. A type
15 menu will require a batch file that is called to execute QChat, a type
7 menu only needs to have the command line to execute QChat on the
Optional data line of the menu. See your BBS manual for more information
on type 7 and type 15 menus... Decide which type of menu command (Type 7
or type 15) you wish to use and then do ONE of the following depending on
which menu type you have chosen to use:
Type 7 Menu Command:
Optional Data:
<command line> [control codes]
Description:
This function will run an external program, or door in a
shell while the user is on-line.
Example command lines for Type 7 usage:
Calling QChat in either a single line or multiline system you would use:
Single Line: C:\RA\QCHAT\QChat.Exe -d:C:\ra *! *M
Multi Line : C:\RA\QCHAT\QChat.Exe -d:C:\ra\line*N *! *M
In a single line system, calling CoSysOp #1 (NOT the sysop) you may use...
C:\RA\QCHAT\QChat.Exe -A *! *M
The following RA parameters are used in the above examples:
*M
Activate the MemorySwap feature. RemoteAccess attempts to
swap itself and all the memory it occupies to XMS and EMS
memory (if available) or to disk, leaving only 3KB resident.
This is ideal when running memory-hungry programs but takes
a few seconds longer in order to perform the swap. If the
swap cannot be accomplished, RemoteAccess will attempt to
load the program in a normal shell.
*N
The current node number, as specified by the -N command line
parameter when RemoteAccess was loaded.
*!
Freeze the system timer for the duration of the shell.
Type 15 Menu Command:
Exit to DOS with errorlevel
Optional data:
<errorlevel>
Description:
This function causes RemoteAccess to exit to DOS completely,
returning an errorlevel to your BBS batch file. The
optional data field should contain the errorlevel that you
wish to pass to the batch file. The batch file should trap
the errorlevel and act accordingly.
If you use this exit while the user is still on- line, the
user may be logged back into RemoteAccess using the command
line parameter -R. This forces RemoteAccess to read the
EXITINFO.BBS file that was written at the time of the exit
so that it can restore system and user information,
presenting the user with the TOP menu.
NOTE: Errorlevels 0 through 5 are reserved for internal use
by RemoteAccess. For a complete description of these
internal errorlevels and how they are used, see the
Errorlevels section of the Reference chapter.
If you decide to use a Type 15 menu to call QChat you will need to add
QChat into your BBS batchfile and call QChat with the errorlevel you
have chosen.
:START
IF ERRORLEVEL 10 GOTO QCHAT
IF ERRORLEVEL 5 GOTO NET&ECHO
IF ERRORLEVEL 4 GOTO ECHOMAIL
IF ERRORLEVEL 3 GOTO NETMAIL
IF ERRORLEVEL 0 GOTO START_UP
GOTO START_UP
:QCHAT
CD\RA\QCHAT
QCHAT.EXE <Don't forget QChat's Parameters!>
RA -R
GOTO AFTER_BBS
In this example, a TYPE 15 menu command with an Errorlevel of
10 will make the batch file execute the command following the
:QCHAT label. Include the line "RA -R" to return to
the board after the external programs have been executed.
NOTE:
DO NOT FORGET to include the correct command line switches for QChat in
your batchfile. Failure to do so will result in QChat not functioning as
it is intended. See the section of this doc file for more info on QChats
parameters.
5. Make sure you have changed ALL of the menus you wish to call QChat
from and that you have saved the changes.
6. QChat also needs to be setup in RACONFIG.EXE so that when you break in
to chat with a user it calls up QChat and NOT the internal RemoteAccess
chat. Change to your RemoteAccess directory and run RACONFIG.EXE
7. What you do next depends on wether you have registered RA....
If you HAVE registered, Goto OPTIONS, PAGING and then to 'External'.
Enter the following command line:
C:\RA\QCHAT\QChat.Exe -F *E *M *!
If you are NOT running a registered version of RA you will need to setup
QChat so that it is called from a Function key, as the above example will
ONLY work if you have a registered copy of RA. Instead you will need to do
the following.
Goto MANAGER, AltFn Key, and choose a blank entry to install QChat into.
We will assume entry 1. Enter the following command line:
C:\RA\QCHAT\QChat.Exe -F *E *M *!
If you are running an UNREGISTERED copy of RA, and have chosen this second
example, you will need to call QChat by pressing Alt-F1 instead of the
Alt-C command which would be used when it is installed in a REGISTERED
version.
These are only an example to get you going... Please refer to the section
of these docs about 'parameters' to ensure you have the correct command
line to execute QChat.
8. Please make sure that there is a Page.Ice in your BBS System Directory,
or in your QChat Directory. QChat requires this as your page tune. A
selection of sample page tunes has been included, just rename the tune
of your choice to Page.Ice.
9. When you run QChat, be sure that the QChat.Cfg file has been created.
If it has not, then you MUST run ChatCfg.Exe. If you don't, and attempt
to run QChat.Exe directly, QChat will display an error message that
QChat.Cfg doesn't exist.
That's all there is to it....
Please make sure that there is a Page.Ice in your BBS System Directory,
or in your QChat Directory. QChat requires this as your page tune. A
selection of sample page tunes has been included, just rename the tune of
your choice to Page.Ice. If you have enabled a seperate tune for VIP users
the tune you wish to use should be named Vip.Ice and this should also be
placed in either your system or QChat directory. BOTH tunes must exist
for this feature to work, if the Vip.Ice tune does not exist, or cannot be
located by QChat the default Page.Ice file will be used instead.
When you run QChat, be sure that the QChat.Cfg file has been created.
If it has not, then you MUST run ChatCfg.Exe. If you don't, and attempt
to run QChat.Exe directly, QChat will display an error message that
QChat.Cfg doesn't exist.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Installing QChat Into Dorinfo1.Def/Door.Sys Systems ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
Please read the section of this document entitled 'Setting Up QChat Using
ChatCfg.Exe' BEFORE attempting to install QChat into your Dorinfo1.Def/
Door.Sys compatible system.
Your BBS MUST be capable of producing a Dorinfo1.Def/Door.Sys drop file
for QChat to run correctly. If QChat fails to find this file it will abort
with an error message!
Because of the number of slight differences between various BBS systems it
is impossible to give a detailed explanation of EXACTLY how to install
QChat into any Non RemoteAccess system. However, if you follow the basic
ideas outlined in the sections of this document about installing QChat
into RemoteAccess it should give you the general layout of what is
necessary. Please refer also to the documents for your particular BBS
system for any differences in layout or command line parameters.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Sysop and User Function Keys ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
Easy To Use SysOp function keys :
F1 : Display Help Status Pop Up Menu
PGUP : Initiate file transfer to remote user
ALT-Fx : Toggle Chat Template (1..10)
ALT-B : Blacklist User (Security Lockout) [RA/PB Compatible]
ALT-E : User Editor [RA/PB Compatible]
ALT-H : Hang Up
ALT-J : Drop To DOS
ALT-L : Line Noise Key
ALT-T : ASCII TextFile Dump to modem & screen
ALT-X : Force Program Exit
Easy To Use User Keys :
CTRL-L : List/Add to available Macros (if enabled)
CTRL-W : Clear Window
CTRL-R : Redraw Screen
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Substitution Strings In Commandlines ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
The following codes can be used in any external filename that QChat calls
upon. These codes are based on the same ones that are used by RemoteAccess.
*C - replaced with COMSPEC environment variable.
*M - swap to external program. Not necessary in QChat as QChat auto
attempts to swap to memory or disk.
*N - node number that QChat is being executed under.
*B - User's current connection rate.
*P - Current port that is being used by QChat.
*T - User's Timeleft.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Control Codes Used In TextFiles ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
QChat now has the ability to interpret and convert control codes which
are imbedded in textfiles that QChat displays to the user. The following
are valid codes that QChat can use. This information (referring to
available ^F and ^K codes) can also be found in your RemoteAccess
documentation.
Control
Code Information Displayed
────────────────────────────────────────────────────────────
^K1 Number of the current template message
area.
^KA Total system calls.
^KB Name of last caller (any node).
^KF Number of times user has paged the Sysop
during this session.
^KI Time in 24-hour format.
^KJ Today's date.
^KL Seconds connected (always returns zero).
^KM Minutes used today.
^KN Seconds used today (always returns
zero).
^KO Minutes remaining today.
^KP Seconds remaining today (always returns
zero).
^KQ Daily time limit.
^KR Connect speed.
^KT Daily download limit (in Kb).
^KW Node number (as set on command line).
^KX Terminates the current call.
^K/ Clear to end of the current line.
Control
Code Information Displayed
────────────────────────────────────────────────────────────
^F! User's default protocol setting.
^F# User's current file group.
^F$ User's address line 1.
^F% User's address line 2.
^F& User's address line 3.
^F' User's sex (Male/Female).
^F* Current file group number.
^F+ Current message group number.
^F[ User's download limit.
^F3 User's handle.
^F4 Date of user's first call to the system.
^F5 User's date of birth.
^F6 Subscription expiration date.
^FA User's full name.
^FB User's location.
^FD Business/Data telephone number.
^FE Voice/Home telephone number.
^FF Date of last call.
^FG Time of last call.
^FH A Flags setting.
^FI B Flags setting.
^FJ C Flags setting.
^FK D Flags setting.
^FL Credits remaining (cents).
^FM Total messages posted.
^FN Last message read.
^FO Security level.
^FP Total calls to the BBS.
^FQ Number of files uploaded.
^FR Kilobytes uploaded.
^FS Number of files downloaded.
^FT Kilobytes downloaded.
^FU Minutes used today.
^FV Current screen length setting.
^FW User's first name only.
Control
Code Information Displayed
────────────────────────────────────────────────────────────
^RA Sysopname as defined in ChatCfg.
^RB BBSName as defined in ChatCfg.
^RC Co-SysOp name #1.
^RD Co-SysOp name #2.
^RE Co-SysOp name #3.
^RF Full name of user.
^RG Area name in which comments to SysOp are posted.
^RH Beginning time of next page slot.
^RI Ending time of next page slot.
^RJ Time elapsed within chat.
^RK Time of day.
^RL Today's date.
^RM User's security level.
^RN User's location.
^RO User's first name.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Macros In QChat Configuration ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
** NOTE : All MACROS and the following strings and headers (UserEditor,
ASCII, Drop To DOS, SysOp Help, Page Reason String, and Paging Header) can
all make use of built in control strings:
@1 = CoSysOp name #1
@2 = CoSysOp name #2
@3 = CoSysOp name #3
@A = SysOp alias
@B = BBS name
@C = Chat duration
@D = Date
@F = User's first name or alias
@S = SysOp name (Read From QChat Configuration)
@T = Time of day
@V = Program version number
@Y = Next pageslot begin time
@Z = Next pageslot end time
The control strings can be used in the following manner. For Example, if
you were configuring your Page Reason String to ask the user why they are
paging, you could put:
@F, Why Would You Like To Chat With The SysOp?
And then when QChat is run, and asks the user who is "John Smith" in this
example to enter a page reason, the @F will be replaced, and the string
will appear to the user as:
John, Why Would You Like To Chat With The SysOp?
All the control strings can be used in a similar manner in all the other
Strings & Headers, as well as macros.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Errorlevels used by QChat ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
QChat will terminate on different errorlevels depending on what conditions
QChat encounters during runtime. Here is a list of hardcoded errorlevels
which QChat uses.
Errorlevel Definition
─────────────────────────────────────────────────────────────────────────
0 No error has occured, normal exit.
1 Error initializing fossil driver.
2 Configuration file can not be found.
3 Version conflict has occured, try upgrade util.
4 Configuration error has occured, make sure settings are correct.
5 Dropfiles (Exitinfo.bbs, Dorinfo1.Def or Door.Sys) Can't be found
6 User posted a comment to the SysOp.
7 Carrier was lost!
8 A file is corrupted.
9 User daily time limit has expired.
10 User paged, but not answered. Did not post a comment.
11 User exceeded pages per session limit.
12 The users page reason was not long enough.
13 The user paged the SysOp out of defined hours.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ BBS System Files Used By QChat ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
See also the section on 'Files Created & Used By QChat' later in these
docs.
When executed, QChat calls upon the following Files from your BBS System:
ExitInfo.Bbs - Read/Write To Exitinfo.BBS, to adjust time limit,
read in the User's Name, Location, baudrate etc..
and to indicate the [Wants Chat] at the bottom of the
SysOp's screen after exiting QChat. Also accessed
by QChat's User Editor.
Dorinfo1.Def - Read in user Information
When using RemoteAccess, QChat also calls upon the following files as well
as those above :
Ra.Log - QChat writes out to this file to indicate the User's
Paging reason (If you set your Logname to your Ra.Log)
PageStat.Ra - QChat uses this to determine whether or not The
SysOp has disabled the paging by using ALT-O in
RemoteAccess. If Paging is set to [OFF] Then no page
tune will be heard on the Sysops end when the user pages
This file is only used if it can be found in the System
directory defined in ChatCfg.
If you have registered your copy of QChat, it will also read and/or write
to the various BBS message base files if you have allowed the user to post
a message to the SysOp if the chat request is not answered.
If you are not using RemoteAccess, the only file that is read from is the
Dorinfo1.Def or Door.Sys BBS drop file.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Parameters Used When Executing QChat ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
There are many parameters that can be used for QChat. They are :
-D:[PATH] This will cause QChat to use the specified [PATH] to locate
the dropfiles that QChat will read in. This is a change since
the previous versions, which had a limit of ten paths in the
configuration program. This new change will allow for more
than 10 paths.
-F This will cause QChat to abort the page reason prompt and
jump directly into chat mode. This would normally be used when
the SysOp instigates a chat with a user, OR if you do not want
QChat to ask for a reason when paging.
-L This will cause QChat to run in local/testing mode so that
the SysOp is able to test it out.
-N:[NODE] This will cause QChat to acknowledge what node of
the BBS that it is being executed on.
-RANDOM[#] This will cause QChat to load a chat template randomly within
the range of 1 to [#].
-TP:[#] This will cause QChat to load up the template
which corresponds to [NUMBER] when chat mode is entered.
-A/B/C This will cause QChat to change the SysOp name to
either CoSysOp #1,#2, or #3. Co-SysOps names are
defined in ChatCfg.
QChat.Exe This will cause QChat To wait for the user to enter a page
reason. If they are outside of paging hours, a message to that
effect will be displayed, and they will return to the BBS.
These parameters may be used in almost any combination when executing
QChat, It is IMPORTANT that you select the right parameters for QChat
to run correctly, so please read this section carefully and refer to
the various examples given for setting up your particular BBS in the
relevant section of these documents.
There is one more parameter that was added in during the v4.20 betas.
I had planned on removing it, however I've left it in for those who
really need to finetune QChat to their system. This parameter controls
how much timeslicing will occur in multitasking environments. The LARGER
the value, the LESS slicing that occurs. QChat defaults to 20, which
is the optimum value on all test systems. Following is a symptom/solution
chart:
Symptom: | Solution:
─────────────────────────────────────────────────────────────────────────
QChat, when run in a | QChat is giving up TOO many timeslices
multitasking environment is | in your multitasking environment. You
really slow, although the | should INCREASE the value, so that QChat
other windows run fine. | gives LESS timeslices.
─────────────────────────────────────────────────────────────────────────
QChat runs absolutely | QChat is "hogging the CPU" (it's not
great in my environment, | giving up enough timeslices). Correct for
with no lag or delays. | this by DECREASING the value, so that
However, while QChat is | QChat gives up time slices more
running, my other windows | frequently.
slow to a crawl. |
─────────────────────────────────────────────────────────────────────────
The parameter to use to adjust QChat's slicing is:
/S:[value] - [value] represents the slice value, as outlined above.
We recommend you play with this only if *** YOU REALLY
KNOW WHAT YOU'RE DOING! ***
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Files Created & Used by QChat ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
QChat creates a number of files for it's own use, these include it's main
configuration file and macro file etc. There are also a number of ANSI
files that you can create yourself using an ansi editor (such as TheDraw).
These ANSI files will be used by QChat during its operation. See the
following list for a full rundown on the files that are created and/or
used by QChat.
!! ALL of these files MUST reside in the same directory as QChat.Exe !!
───────────
QCHAT.CFG
───────────
This files stores QChat's main configuration. It is created by
ChatCfg.Exe and MUST be present for QChat to run.
───────────
MACRO.CFG
───────────
Macro.Ice file is an encoded file that you MUST use ChatCfg to edit. Do
NOT use a standard text editor. It contains words that will be replaced
in chat with new words. For Example, if you type "BBS" in chat, it will
replace it with "Bulletin Board System". These are all SysOp Defined.
────────────
NOPAGE.CTL
────────────
NoPage.Ice file is an textfile that you can use any text editor To edit.
It contains any names of users that you feel shouldn't be allowed to
page. When the user enters the page reason, it will appear that the music
is playing from the remote end, but no page music will be heard on the
Sysop's end. You do not HAVE to use a NoPage.Cfg, but it is always handy
to prevent yourself from being annoyed by the constantly paging user
that every BBS has.
────────────
RANDOM.CFG
────────────
Random.Cfg file is a text file that you can create. It contains any page
tunes that you would like to have randomly selected and played everytime
a user pages. When the user pages, QChat will read in all of the page
tunes listed in this file, and will randomly select one to be played.
Please note, if this file exists, the VIP page tune will not be played
for VIP users. The Format is simple :
Page.Ice
Dallas.Ice
Dance.Ice
Axel_F.Ice
That is a simple example. You do not have to use these particular tunes,
just replace these names with the page tunes you prefer. These tunes must
be in your QChat directory. If it can't find the random pagetune that it
selects, it will default to page.Ice. A file containing various page tunes
is included in the release archive.
────────────────────
PAGE.ICE & VIP.ICE
────────────────────
These are standard RemoteAccess page tunes that QChat will play while
paging. Page.Ice is used for normal users, and Vip.Ice is used for VIP
users. These files must be located in either the QChat directory or the
main BBS System directory. These files will not be used if the Random page
tune function is active.
───────────
VIP.CTL
───────────
Very Important Person TEXTFILE - use a different tune for these Users.
This file is a simple ascii text file which contains a list of user names
that will use the Vip.Ice pagetune when they page the SysOp. It's format
is simple, just enter each user that you wish to use the Vip.Ice pagetune,
ONE name per line as follows:
Benjamin Schollnick
Scott Drake
──────────────
NOTAVAIL.A**
──────────────
This is an ANSI/ASCII file that can be displayed if the SysOp is unable to
(or chooses to abort) the users page. You can create this file using any
standard ANSI/ASCII editor.
──────────────
OUTHOURS.A**
──────────────
This is an ANSI/ASCII file that can be displayed if the user pages
outside of the SysOp's paging hours. You can create this file using any
standard ANSI/ASCII editor. This file is ONLY Displayed when user pages
out of hours and there is NOT a defined emergency password.
──────────────
TEMPLATE.x
──────────────
Any TEMPLATE.x file that you use MUST be in 24x79 format, and they MUST be
saved in ANIMATED mode in TheDraw. If you dont save them like this, it is
possible for them to scroll off the bottom of the screen by one line, and
thus mess up the display. YOU MUST SAVE THEM IN THIS FORMAT TO WORK !!!
The "x" represents the template number. 1 & 2 are hardcoded, but 3 - 10
can be defined using ChatCfg.
If you create this file, it will be used by QChat to replace the default
chat modes (Horiz/Vert). This file is NOT necessary, but is included
so that you can make QChat look like the rest of your BBS setup should
you wish to. Simply create an ANSI screen using an ansi editor (TheDraw)
And name it TEMPLATE.x. This file MUST be in the same directory as
QChat.Exe.
──────────────
MACROHDR.ANS
──────────────
Included in the release archive is an ANSI screen named SAMPLE3.ANS,
It is used to replace the header at the top of the macro listing feature.
the screen has to be renamed to MACROHDR.ANS to become active. If this
screen is not available in your chat directory QChat will use its built
in screens. {+}
─────────────
PAGEHDR.ANS
─────────────
It is used to replace the header at the top of the main paging screen.
The screen must be renamed to PAGEHDR.ANS to become active. If this
screen is not available in your chat directory QChat will use its built
in screen. This file can only be 7x79 characters in size. {+}
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Frequently Asked Questions ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
Q: Is it possible to run QChat from RA's external chat feature? I have the
path and filename set correctly, but RA's default chat mode always comes
up.
A: This is most likely because your copy of RA is Unregistered. This RA
feature is only available in the registered version. Change from using
RA's external chat routine and use a Function key instead. This is
explained in the section of these docs about installing QChat into RA.
--
Q: QChat is ignoring the necessary configuration files that it requires at
startup. What is wrong?
A: There are two possible solutions. 1st: Make sure that none of the QChat
files are WRITE-PROTECTED. If they are, QChat will simply ignore them.
2nd : Make sure that you have set up an QChat environment variable.
ie.
SET QCHAT=C:\QuickBBS\doors\chat
This will allow QChat to find its configuration files no matter where
QChat is run on the System. Otherwise, it will be necessary to run
QChat from a batchfile that will CD into QChats home directory. EG:
@Echo OFF
Cd \QuickBBS\DOORS\CHAT
QCHAT.EXE
Cd \QuickBBS\Node1
--
Q: When I try to run QChat, it gives me a conversion error similar to
"Invalid QChat.Cfg : Please run v4.35 -> v1.00 converter". What is
wrong?
A: This is most likely because you have just recently upgraded to a newer
version of QChat and not run the conversion utility. The solution
would be to run the Conversion program (CHATCFG), or to delete your
QChat.Cfg file and start the installation from scratch.
--
Q: When I try to run GEdit with the registered copy of QChat, GEdit
always runs thinking that it is in LOCAL mode.
A: When you install GEdit into QChat, make sure that you use the
following commandline:
[Path]\Gedit.Exe *P *B *T <kbt>
<kbt> represents the keyboard timeout value in seconds.
--
Q: I am running a registered copy of QChat, and have configured my
external editor correctly in ChatCfg. However when the page is not
answered and a user attempts to leave a comment QChat says
"Swapping Out For External Editor.." and then freezes. What is wrong?
A: This is a known bug, which only affects some systems. If you are
encountering this bug, it is most likely because you have a *M on your
external editor commandline. Remove this *M, because QChat will
automatically attempt to swap out when loading the editor.
--
Q: When a user pages, it ALWAYS pages no matter what the hour is, or it
does the exact opposite and either A) never emits any sound or, B) tells
the user that I'm unavailable even during page hours. What is wrong?
A: There are two possibilities here. The first possibility is that you have
your RemoteAccess override engaged. When you are logged onto
RemoteAccess, try hitting ALT-O. If it is set for always ON or always
OFF, QChat will respect this setting and abide by it, regardless of
page hours setup.
The other possibility is that you have your scroll lock key engaged. If
scroll lock is ON, QChat paging is OFF.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Registration ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
The Development of QChat v1.00 took many long hours, and a lot of time
and effort not to mention money. This program is NOT FREEWARE. If this
program satisfies your expections of a chat utility, if not MORE, then you
are expected to register it after an evaluation period of 30 days or
sooner. By doing this you can be sure of continued development of the
software. Thanks for your support.
This Program may be freely distributed but DO NOT under any circumstances
change any of the executables or alter any files that come in the original
distribution archive.
I urge you to register as soon as you can! The more registrations that
I have will show the interest of people in the program, and I will release
a newer version with many more features. If you register, the QChat built
in message editor will be available and the extra Macro editing screens.
Also, all "Unregistered" messages and almost inaudible beeps within the
program will be removed.
Please note that the status of features (whether they are available or not
to unregistered users) may be changed without further warning in later
versions of the software; but this does not mean that they will be
changed.
To register, fill out the REGISTER.DOC form and submit it to any of the
sites in REGSITE.LST. Thank you for your support.
Any Registration forms that have invalid or missing information may be
considered void and not be processed, depending on the extent of the
errors.
Due to recent events, I have changed my policy on personal cheques that
are sent in to pay for registration. I will continue to honor them,
however as of this release, there will be a 2 week hold placed on the
cheque to ENSURE that it does NOT go N.S.F. Although most people are
honest about this, lately too many people have sent in N.S.F. cheques, and
when contacted about them, show little or no concern about them or the
financial difficulties they may have caused.
Additionally, a service of $25 will be levied against any N.S.F. cheques.
Until both the full payment, and the service charge is recieved in the form
of a MONEY ORDER, the registration will not be processed.
In conclusion to the above information, to ensure a speedy turnaround time
it is recommended you send your registration in the form of a money order
If you do choose to send in a personal cheque, it means that you have read
and understood these conditions.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Archive Contents ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
QChat v1.00 has been compressed using ZIP, This archive should have an
authenticity verification seal by Benjamin Schollnick. If this archive
is not in ZIP format, or if the seal has been broken, it is may be
advisable to get a new archive from one of the support sites listed at
the end of the documentation.
The QChat archive should contain the following files :
QCHAT .EXE - The Main Program
CHATCFG .EXE - Use to configure the program
QPLAY .EXE - PageTune Player
PAGES .ZIP - Archive containing sample pagetunes
QCHAT .DOC - Program Documentation
HISTORY .DOC - Feature addition history
WHATSNEW.100 - Changes (Additions/Deletions) in QChat v1.00
REGISTER.DOC - Generic Registration Form
REGSITE .LST - Quik Utilities Registration Sites
PAGE .ICE - Page Tune
FILE_ID .DIZ - General Program Description
TEMPLATE.1 - Chat Screen Template #1
TEMPLATE.2 - Chat Screen Template #2
TEMPLATE.3 - Chat Screen Template #3
SAMPLE .ZIP - Sample Template files (Included files are listed below)
SAMPLE1 .ANS - Sample Horizontal ANSI screen (rename to Template.1
to use it). See Template.X in the section of these
docs on 'Files Used & Created by QChat' for more
info.
SAMPLE2 .ANS - Sample Vertical ANSI screen (rename to template.2 to
use it). See Template.X in the section of these docs
on 'Files Used & Created by QChat for more info.
SAMPLE3 .ANS - Sample Macro Header ANSI screen (must be renamed to
MacroHdr.Ans to be used). See MacroHdr.Ans in the
'Files Used & Created by QChat' section for more
info.
XFER-S .BAT - Batchfile used for file transfers to user
XFER-R .BAT - Batchfile used for file transfer from user
If one or any combination of these files are missing, or files have been
ADDED, then you are using a possibly modified or altered copy of QCHAT.
It would be advised that you delete this copy, and get a clean copy of
QCHAT from one of the BBS's listed at the end of the documentation.
Newest Version of QChat can be F'REQed from Matrix Technologies BBS under
the magic name 'QCHAT' (without the quotes)
Files QChat will create are :
QCHAT.CFG - The configuration file
MACRO.CFG - Encrypted Macro File
NOPAGE.CTL - List of TWIT users who may not page
QCHAT.LOG - Usage Log (Can be configured to be appended to your
BBS system log)
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Copyright Notices & Program Disclaimer ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
The door QChat, along with all its support files and documents,
are Copyright (C) 1993-98, Matrix Technologies & Benjamin Schollnick.
Distributing a version AFTER it has been registered is prohibited;
distribution of the original, unaltered evaluation version is permitted,
indeed encouraged, as long as all support-files and documentation
accompany the program are included WITHOUT ALTERATION OF ANY SORT. None
of the files included in the QChat archive may be modified in any way or
distributed in any package without the expressed permission of Matrix
Technologies. Any type of cracking of either evaluation or registered
versions of QChat including (but not limited to) hex-editing, reverse
engineering, decompiling are strictly prohibited.
The author can be quickly reached for information through the QUICKBBS,
QUICKPRO, QUIKUTILS, ICEUTILS, PROBOARD or the RA_UTIL international
FidoNET Conferences, or at InterNET e-mail address:
QuickBBS@QuickBBS.Com or bscholl@eznet.net
Or, If you wish to trust comments/complaints/suggestions to the Post
Office, you can send them to:
Benjamin Schollnick
c/o Matrix Technologies
33 Valiant Drive
Rochester, New York 14623
The following programs mentioned in this documentation are Copyright of
their respective authors. They are listed in no particular order:
QChat - Copyright Matrix Technologies & Benjamin Schollnick
QuickBBS - Copyright Matrix Technologies & Benjamin Schollnick
FKFossil - Copyright Tim Strike and Forbidden Knights Systems
RemoteAccess - Copyright Wantree Development & Andrew Milner
Telegard - Copyright Tim Strike
Concord - Copyright Pasi Talliniemi
ProBoard - Copyright Philippe Leybaert
Synchronet - Copyright Digital Dymantics
TriBBS - Copyright Freejack's Software & TriSoft
AdeptXBBS - Copyright AdeptSoft
X00 - Copyright Raymond L. Gwinn
BNU - Copyright David Nugent and Unique Computing Pty Limited
Turbo Pascal - Copyright Borland International
THE USUAL LEGALITIES
I (Benjamin Schollnick) make no warranty of any kind, expressed or
implied, including without limitation any warranties of merchantability
and/or fitness for a particular purpose. I shall not be held liable for
any damages, whether direct, indirect, special or consequential arising
from the failure of this program to operate in the manner desired by the
user.
I shall not be held liable for any damage to data or property which may
be caused directly or indirectly by the use of this program.
In no event will I be held liable for any damages, including (but not
limited to) any lost profits, lost savings, or other incidental or
consequential damages arising out of the use -- or the inability to use --
this program, or for any claim by any other party.
The only thing that this package is guaranteed to do is to take up space
on your hard drive.
Making use of this software is acknowledgement that you have read,
understand, and fully agree to the license and disclaimer agreement.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Credits ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
We would like to thank all of the Beta sites, and users that have
assisted us in the development of QChat.
Special thanks to Scott Drake of ISO InterNet & LAN Services for creating
and maintaining our homepage on the internet!
(http://www.isonline.com/Matrix/)
Also, portions of the Fossil Routines used in QChat v1.00 are Copyright
1993-94 By Tim Strike and Forbidden Knights Systems.
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Other Matrix Technologies Utilities ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
Here is a list of all the Matrix Technologies utilities that were
available at the time of release of this archive. If you enjoy using
this Quik utility, you may want to check some of these out! :)
· QChat -
QChat is a split screen chat utility for QuickBBS, RemoteAccess and
ProBoard BBS packages. It can be used with many other BBS types as long
as they support Dorinfo1.Def/Door.Sys type Doors.
· QuikEdit -
QuikEdit is a fullscreen ANSI message editor that was originally designed
for use with RemoteAccess. Although it has been tested with QuickBBS v2.xx
Telegard v3.00, RemoteAccess v2.xx, ProBoard v2.xx, Synchronet v2.xx,
TriBBS, AdeptXBBS v2.xx Watcom / v1.xx VAC and Concord v0.001 it should be
compatible with any other BBS that uses the QuickBBS style dropfiles that
contain the message writing information.
· QuikBank -
QuikBank is the fourth utility to become available. It is a fully
functional, fully configurable timebank system for QuickBBS v2.xx,
RemoteAccess v2.xx and ProBoard v2.xx.
It has many cool features, including InterBBS transactions.
· QuikCBV -
The very newest Matrix Technologies door available! Took awhile to
finally get it released, but you won't be disappointed. Full featured
callback verification system for QuickBBS, RemoteAccess and ProBoard.
Many unique features! Look forward to even more features in the next
version!
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Program Support - Internet Email Addresses ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Following is a list of support/distribution/registration sites which
currently have Internet email addresses. Please contact any of the
sites listed in SUPPORT.DOC via email for assistance with any Matrix
Technologies product.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Program Support - BBS Locations ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
All Matrix Technologies utilities are available from our homepage at:
http://www.isonline.com/Matrix
QChat can be File Requested from any of the BBS's listed in SUPPORT.DOC,
which is included in this archive.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ End Of QChat Documentation ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
