home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 8
/
CDASC08.ISO
/
VRAC
/
GRAFD220.ZIP
/
GRAF-D.DOC
< prev
next >
Wrap
Text File
|
1993-09-10
|
13KB
|
251 lines
Program: GRAF-D v2.20 Copyright (C) 1993 Clark Development Co., Inc.
Author: Steve Catmull
Date: 09/10/93
DESCRIPTION
========================================================================
PPE (PCBoard Programming Executable) that you can replace
PCBTEXT record #149 with.
What this PPE offers that PCBoard does not is to do some
checking for graphics capability before asking the caller
if they want graphics or not.
By testing for graphics before the prompt is ever issued,
the appropriate default value can be set for the user. If
they have ANSI capabilities (as per the <esc>[6n test)
then the default for the prompt will be "Yes". A test
will also be made if they have RIPscrip capabilities (as
per the <esc>[! test). If neither of these are detected
in the default wait period then the default will remain
as no.
INSTALLATION
========================================================================
Installing this PPE is very simple. Use MKPCBTXT to load
your PCBTEXT file. Press F3 and enter 149. You will now
see the "Do you want graphics" record. Simply change it
to an ! followed by the full path and filename to the
GRAF-D.PPE file.
In addition, make sure that you have not told PCBoard
that you want to default to graphics at login. If you
do, GRAF-D will warn you that your system is improperly
configured.
That's all there is to it.
COMMAND LINE PARAMETERS
========================================================================
You can control the wait time for ANSI and RIP detection
from the command line. You may also choose to run this
program in "compatible" mode via command line switches.
You can specify as many command line parameters as you
wish. If you specify more than one, make sure each
parameter is separated with a space. The following
details the command line options that are available.
/WAIT:[clock ticks]
Gives you the ability to over-ride the default wait
time for graphics detection. The default wait is
for 55 clock ticks which is equal to about 3
seconds (There are roughly 18.2 clock ticks per
second). For example, if you wish to make the new
wait time about 4 seconds, then you would enter the
following in PCBTEXT:
C:\PCB\PPE\GRAF-D.PPE /WAIT:73
/COMPATIBLE
Because this PPE will change the "Do you want"
graphics prompt based on the graphics capability
detected then there is a good chance that login
scripts might fail.
In other words, a user could login and receive
"Do you want graphics (Enter)=no?"
but the next time they login it may say
"Do you want graphics (Enter)=yes?"
Obviously, if the user has a script which checks
for "(Enter)=no" then their second login attempt
will fail.
This command line switch will tell GRAF-D to report
the graphics mode detected above the "Do you want
graphics" prompt and explain that it will be the
default response. The prompt will then be modified
to always display:
"Do you want graphics (Enter)=default?"
It may break a few scripts initially, but once the
user has modified their end they can be assured
that they will always receive that prompt. The
following is an example of how to specify this
parameter on the command line:
C:\PCB\PPE\GRAF-D.PPE /COMPATIBLE
/AUTO
Some sysops may not want to give the user a choice
as to what graphics mode is selected. If you are
one of these folks, then this switch is for you.
This switch will make the user use ANSI or RIP if
detected by the PPE. If neither ANSI or RIP is
detected, then the user will be asked what graphics
mode they would like to use.
The reason that the PPE does not simply go with
non-graphics mode is because the user's
communication package may not properly handle the
ANSI auto-detection. Example:
C:\PCB\PPE\GRAF-D.PPE /AUTO
/NORIP
Not all systems have RIPscrip screens designed. If
you do not want GRAF-D to automatically detect RIPscrip,
use this command line parameter. When this command line
parameter is used, the auto-detection code for RIPscrip
is not sent out. Example:
C:\PCB\PPE\GRAF-D.PPE /NORIP
/NOQUICK
Some SysOps put a hefty amount of time into producing
welcome screens for their users. Users who are familiar
with PCBoard may use the Q subcommand at the "Do you want
graphics" prompt to skip the welcome screen. When this
option is used, you will disable the ability for users
to skip the welcome screen by using the Q subcommand.
Example usage:
C:\PCB\PPE\GRAF-D.PPE /NOQUICK
/DELAY:[clock ticks]
When checking for an ANSI response, this PPE will wait
for a default of 2 clock ticks if no response is received
(after the first character). In certain circumstances
like excessive line noise, you may need to bump up
the delay time. The delay time is expressed in clock
ticks (18.2 per second). Unless you need to, I suggest
you do not use this parameter.
Example usage:
C:\PCB\PPE\GRAF-D.PPE /DELAY:10
/DEBUG
This command line switch will write some debug information
to a file called DEBUG.GRF. The debug information simply
shows the contents of some variables and below that is
a history of what is received after the ANSI request is
sent out.
Looking at this information you will be able to determine
if you need to increase the /WAIT time (because an
incomplete response was received) or if the response
from the remote terminal program is flawed in some
manner.
ERROR RATES
========================================================================
Not every user will have their graphics capabilities
properly detected upon login. If an invalid (or no
response) at all is detected during the wait time then
it must be assumed that the user does not have graphics
capabilities.
Some terminal programs are just plain slow in responding
to ANSI or RIPscrip requests. I have tested with the
following communications software and all respond
swiftly and accurately:
Telemate v4.x
Telix v4.x
Robocomm v4.x
ProComm Plus v2.x
Qmodem v4.31
Even if you are using one of these programs it would
still be likely for a response to not be detected. This
may happen if you are using error-correcting modems and
the modem happens to be experiencing line noise. In a
case such as this, there is nothing that can be done.
In my testing (about 1800 calls to Salt Air) I have seen
that about 17% of all connections will fail to even get a
response from the remote user. Another 4% of all
connections will fail due to incorrect responses from the
remote terminal. This may happen if you start typing
while graphics are being attempted to be detected.
Of course, you could bump up the wait time to catch some
of these connections. The problem with this thinking
though, is that users who truly do not have graphics
capabilities will *have* to wait for the wait period (a
default of about 3 seconds). Extending that time any
longer may really cause you to have some upset callers.
For your reference, the following report shows the statistics
for the 1800 or so calls that I talked about previously:
+-- Number of
| calls where
| no response + Incomplete
| was recorded | responses
| |
*************************************************************************
Report ran: 05-07-93 08:24:53
<= 2400 : Calls: 69 Average ticks: 17 Exc: 8 Inv: 7 Inc: 2
2400-9600 : Calls: 153 Average ticks: 12 Exc: 43 Inv: 12 Inc: 1
9601-14400 : Calls: 1101 Average ticks: 13 Exc: 245 Inv: 68 Inc: 13
14400+ : Calls: 150 Average ticks: 15 Exc: 13 Inv: 1 Inc: 5
*************************************************************************
| | | |
Baud---+ +-- Number +-- Average |
of clock ticks +- Invalid
calls elapsed responses
before a
response
MODIFYING SOURCE
========================================================================
Feel free to modify the PPS (source) file as your needs
dictate. That is why the source is included. :-)
If you do modify the source, please do not redistribute
your version.
Last, but certainly not least. HAVE FUN!