┌──────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
└┐ ┌───┐ │ │ ┌───┐ │ └┐ ┌───┐ └┐ │ ┌───┐ │
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │
│ └───┘ │ │ │ │ │ │ └───┘ │ │ │ │ │
│ ┌┐ ┌──┘ │ │ │ │ │ ┌───┐ │ │ │ │ │
│ │└┐ └┐ │ │ │ │ │ │ │ │ │ │ │ │
┌┘ └┐└┐ └─┐ │ └───┘ │ ┌┘ └───┘ ┌┘ │ └───┘ │
└────┘ └───┘ └─────────┘ └─────────┘ └─────────┘
┌──────────┐ ┌─────────┐ ┌──────────┐ ┌────────────┐
│ ┌─┐ ┌─┐ │ └┐ ┌───┐ │ └┐ ┌───┐ │ │ ┌─┐ ┌─┐ │
└─┘ │ │ └─┘ │ │ └─┘ │ │ │ │ │ │ │ │ │ │
│ │ │ └──┐ │ └───┘ │ │ │ │ │ │ │
│ │ │ ┌──┘ │ ┌┐ ┌──┘ │ │ │ │ │ │
│ │ │ │ ┌─┐ │ │└┐ └┐ │ │ └──┘ │ │
┌┘ └┐ ┌┘ └───┘ │ ┌┘ └┐└┐ └─┐ ┌┘ └┐ ┌┘ └┐
└────┘ └─────────┘ └────┘ └───┘ └────┘ └────┘
VERSION 2.70
Concept and Program By Seth Hamilton.
Compiled August 8th, 1992.
LIABILITY AND RIGHTS
─────────────────────────────────────────────────────────────
Please read and understand this section before using Robo-
Robo-Term.
1) Robo-Board's creator does not assume any liability for the
use or misuse of this software.
In no event will Robo-Board's creator be liable to you for
any additional damages, including any lost profits, lost
savings, lost programming, or other incidental or
consequential damages arising from the use of, or
inability to use, this software and it's accompanying
documentation, even if ROBO-TERM's creator has been
advised of the possibility of such damages.
2) Robo-Term is the property of Seth Hamilton. Seth Hamilton
retains the right to stop supporting Robo-Term at any
time he see's fit.
3) You may not reverse engineer or modify in any way
Robo-Term in memory or on disk, or distribute it for such
purposes.
4) Robo-Term may be distributed free of charge with any soft-
ware using the RBO100 Graphical telecommunications protocol
as long as no cost is levied for the use of Robo-Term.
5) Robo-Term is FREEWARE and may only be distributed as such.
Under no conditions is it to be sold or charged for.
WHAT IS IT?
─────────────────────────────────────────────────────────────
Robo-Term is a FreeWare terminal required to call Bulletin
Board System's (BBS's) utilizing online graphics via the
RBO100 graphical protocol.
Robo-Term is simple while in text mode. Yet it offers ANSI
and ASCII emulation without an ANSI driver, a dial list with
mark, unmark, edit and autodial capabilities, a DOS shell,
Auto Zmodem, Ymodem, Ymodem-G, Xmodem, Xmodem CRC, Xmodem 1K,
and Xmodem-G 1K for fast transfers.
In graphics mode the environment is a little different.
First off, the status bar at the top of the screen disappears.
Secondly, if you have a Microsoft compatible mouse installed a
graphical mouse pointer is placed in the middle of the screen.
Lastly, the default Zmodem protocol has been replaced with
Rmodem (a fast, error correcting, sliding protocol with speeds
averaging from 238cps to 240cps on a 2400 baud modem, on files
over 100k that works out to 100% effiency). But most of all
you will notice the graphics, they are fast and detailed.
Robo-Term, like Robo-Board will directly read and write to
your UART chip. Support for 16550s with FIFOs is automatic.
Note: Robo-Term Requires a 100% EGA or VGA video adaptor. If
use a fossil driver, Robo-Board will ignore it.
UP AND RUNNING
─────────────────────────────────────────────────────────────
Robo-Term is very easy to set up. Upon loading Robo-Term
you will notice a bar on the top of screen. This is the
status bar. The status bar only exists and is needed while in
text mode. Now press the F1 key, this is the help key and is
also only available while in text mode. From this menu you can
learn Robo-Terms HOT KEYS and functions. Use the arrow keys
select SETUP or press ALT-S (the help menu does not have to
be up to use HOT KEYS). Now use the Arrow keys to select the
BAUD RATE option and press enter. Select the maximum baud
rate your modem operates at and press enter. Now do the same
for the COM PORT option. The default dial and init strings
should work fine with your modem, if any changes are needed
make them now. The download path is defined to tell Robo-Term
where to place the files you download. If you leave this
field blank then Robo-Term will place files in it's operating
directory. If you do specify a path, be sure it exists.
First, before calling a BBS with Robo-Term you should be
sure that around 500k free disk is left. This space is
used when Robo-Term is in graphics mode. At times a swap file
might be needed for the temporary storage of screen bitmaps,
but only if all memory is consumed. If you do run out of disk
while Robo-Term is swapping don't worry, the result will
cause windows and screens not to pop down or to be stored
(creating a visual mess).
Now your ready to use Robo-Term. Simply press F1 or press
the hotkey ALT-D to bring up the dial window. Enter any BBS
names and numbers into the dial list and your ready to go.
With Robo-Term you may dial more than 1 number at a time by
tagging numbers with the space bar. Robo-Term will then do
a redial of all the tagged numbers until a connect is made.
THE MOUSE
─────────────────────────────────────────────────────────────
Here are some special notes about mice. First, Robo-Board
will use one. Robo-Board access and initializes the mouse in
the simplest way. That is it, does nothing fancy AT ALL and
calls only those MOUSE interupts set aside for the mouse. The
mouse interfacing information I found came directly from
MICROSOFT. Seeing as they pretty well invented the IBM mouse,
if your mouse doesn't work with ROBO-TERM then it isn't 100%
compatible MICROSOFT specs. Don't worry there still is hope!
These mice are known to work:
LOGITECH SERIAL: using Logitechs MOUSE600.com driver.
ATI BUS MOUSE : using ATI's bus driver
DEXXA MOUSE : using a dexxa .COM style mouse driver.
TANDY MOUSE : Didn't come with a driver so we tried the
Logitech MOUSE600.COM and it worked!
GENIOUS MICE : This one caused QEMM to give exception 13s,
caused the mouse to be invisible, or froze
the system. The driver that did this was the
GMOUSE (.COM and .SYS) driver. I am not sure
what version (7.01 I think) written early in
1991. This driver just wasn't 100% MICROSOFT
compatible. So, we found Logitechs MOUSE600
driver on a local bbs and installed it, and
PRESTO! it worked!
NOTE: I think Logitech just knows how to write a great mouse
driver thats 100% microsoft compatible! So if your mouse does
not work when you call or causes bad problems, then turn it off
on the ROBO-TERM settings menu (hit F1 for help), or call a few
boards, or talk to your friend with a logitech and get a new
mouse driver. I have MOUSE600.ZIP on my bbs if you want.
QUESTIONS
─────────────────────────────────────────────────────────────
Questions about Robo-Term or the RBO100 protocol can be
sent to Seth Hamilton along with a self addressed and stamped
envelope at the address below:
SETH HAMILTON
PO BOX 633.
AYLMER QUEBEC,
CANADA.
J8X-3L0.
Or
The ROBO-BOARD {HQ}
1200-14400 (HST)
24hrs
1(819)685-0957