Jump to content
IGNORED

BBS dial out Catch-All thread


Opry99er

Recommended Posts

First up... anyone have text docs for Mass Transfer (the XB2.7 Suite version)?

 

I think they were DV80 files on the disk itself, but I do not have a copy, not am I currently at a terminal to extract docs.

 

 

I HAVE extracted the Term80 docs and will post them to this thread either tonight or tomorrow.

  • Like 1
Link to comment
Share on other sites

Okay. These are the documents for Mass Transfer 4.1--

 

Sorta tough to find, buried in the pc99 utility folder in whtech.com.

 

 

I have also attached the .DSK image for Mass Transfer 4.1 for anyone who needs it.

 

 

 

 

 

 

 

"MASS-TRANSFER" Modem Utility.
Version 4.1.
Copyright 1985,1986 Stuart Olson.
If you are using this program, and have not yet paid for it,
please send $10 check or money order to the author for his work.
I'm allowing you to try this software before you decide to buy
it. As such, I am trusting you to pay for it if you should
decide to keep it. If you do not like it, please pass it along
to other users, as they may find a need for this program. Good
response from you will encourage programmers like myself to
provide you with software at a reasonable price and without copy
proctection. Like they say, you can start paying us now or pay
a software dealer 3 times the price for their programs..
STUART OLSON SYSOP: TI-85033 (602) 848-6200.
6625 W. COOLIDGE ST..
PHOENIX, AZ. 85033.
MASS-TRANSFER is a terminal emulator program written in 9900
assembly language. Through its menu driven screens, it supplies
the user with a variety of options with which to enhance the
telecommunications of the TI computer..
..
SYSTEM REQUIREMENTS.
The minimum system necessary for operation is the TI-99/4A
console, 32k Memory Expansion, RS232 card, disk drive, and a
modem. Either the Editor Assembler or Extended Basic cartridge
may be used. .
GENERAL INFORMATION.
This software employs a unique feature provided by the
TI-99/4A computer. The RS232 card contains its own programming
inside a special Device Service Routine (DSR) rom. This rom
normally handles the computers file management. It also allows
for the use of Circular Interrupt Buffer (CIB) operation. This
routine interrupts the running program each time a character is
received and places that character into a special buffer in
memory. This program periodically checks the CIB and upon
finding new characters, processes them as either control
characters or data. The CIB overwrites itself if more than 255
characters are received and not processed. This type of
programming results in an interrupt driven input for the
computer, allowing the user to leave the terminal mode and
return to the main menu for short periods of time without any
data loss..
MASS-TRANSFER maintains its own user managed telephone
directory. The accompanying extended basic program (PHONEMAKE)
allows the user to load a phone directory with up to 20 of the
most frequently called numbers. The directory can be easily
updated with the program's editing feature. The desired phone
number can be accessed via the auto-dial feature. This
auto-dialing can only be accessed if a smart-modem with autodial
capacity is being used. Each of the 20 listings allow the user
to send up to 50 characters to the modem. This allows the user
to send special modem control codes prior to the actual dialing
of the desired phone number..
NOTE: In order to use the auto-dial phone directory
option, the extended basic program that creates the directory
should first be used. To do this, load and run the following
program OLD DSK1.PHONEMAKE. If this program is being ran for
the very first time, then select option 1 from the menu, which
will create a blank directory on the disk you have in drive #1.
To provide for proper modem operation, you must answer all the
prompts in the "change modem commands" section. This program is
also menu driven. Follow the screen prompts to load the
directory with your phone numbers and modem commands..
..
INTRODUCING "MXT" (Multiple Xmodem Transfer).
The MXT file transfer option is an ALL NEW concept for the TI
and its growing xmodem file transfer capabilities. The MXT
supervisor routine allows the user to select any number of files
from a disk, and send them without the boring task of typing in
numerous filenames and other associated key combinations as used
by other xmodem transfer programs. If used with a smartmodem,
the program will even disconnect itself from the phone line
after the transfer is complete or should more than 10 retries be
encountered on any one record..
If the MXT system is used on both sending and receiving
computers, the modified xmodem transfer is automatic, allowing
both users to walk away from the computer, returning later to
turn off the equipment..
MXT is capable of SENDING your selected disk files to OTHER
xmodem terminal emulators also. The receiving system will still
have to type in filenames, however the MXT supervisor sends the
other computer a message containing the proper filename of the
file to be transfered. This allows MXT to work with such
programs as Fast-Term and 4A/Talk..
MXT uses a modified file header to convey the necessary info for
the receiving MXT system, including the proper filename and
status as to any more files to be sent after the present one is
finished. Although the file header is modified, it still works
with those other programs previously mentioned. Since the other
xmodem emulator programs do not send the modified file header,
MXT can NOT be used for receiving files from these other
programs..
ERRORS.
Mass-Transfer uses on screen I/O error messages if problems are
encountered while accessing a peripheral. For your convenience,
the standard TI error codes are listed below..
Code Meaning.
---- -------.
00 Bad device name.
01 Device is write protected.
02 Bad open attribute such as incorrect file type
03 Illegal operation; ie., an operation not supported on
the peripheral or a conflict with the open attributes.
04 Out of table or buffer space on the device.
05 Attempt to read past end of file.
06 Device error. Covers all hard device errors.
07 File error such as program/data file mismatch or file
not found..
..
SYSTEM DEFAULTS.
Upon entering the program, the following are in affect: .
RS232 card #1, port #1.
300 baud rate.
8 bit character length (terminal mode masked to 7).
1 stop bit.
No parity check.
Auto Hangup Off.
Local echo Off.
Remote echo Off.
Buffer capture On.
Log file Off.
Linefeed Off.
Print spooler off, set for PIO.
CONTROL and FUNCTION KEYS.
The following control and function keys are active along with
auto repeating of all keys:
Control G Bell - Produces a beep.
H BS - Move cursor one space left, deleting
the previous character.
J LF - Scrolls the display screen one line.
R - Changes some RS232 parameters when at main
menu.
L FF - Clears the screen and homes cursor.
/ - Causes the program to generate a break
character and also CANCELS the AUTO-DIAL
routine once it has been started.
= - Changes screen color.
Function S BS - Left arrow, provides same function as
Control H.
X LF - Down arrow, provides same function as
Control J.
1 - Changes text color..
4 - FCTN CLEAR allows the user to abort most
functions.
7 - FCTN AID exits the Terminal mode and
returns to the main menu screen.
= - Prompts you for exiting the program.
Toggles print spooler on/off in terminal
mode.
D - Right arrow, provides same functin as the
space bar..
9 - When in terminal mode, allows a screen
dump to be done..
Enter CR - Positions cursor at the beginning of the
line..
..
LOADING THE PROGRAM.
Editor Assembler using option 5.
Enter the filename as: DSK1.MASS.
Extended Basic module.
Enter the filename as: DSK1.LOAD.
CUSTOMIZING THE PROGRAM.
.
NOTE: It is assumed the user of this info has an understanding
of how a sector editor works, especially the one that will be
used to alter the MASS file. You should make a copy of the MASS
file first, and attempt your changes on that copy. If a mistake
is made, you will not destroy your only "working" version of the
program. If you do not know how to use a sector editor, I would
recommend that you contact a local user group or an individual
who is knowlegable in the use of sector modifications..
.
.
Directions:.
.
1. Using a sector editor, locate the first sector of the MASS
file. This is the sector in which all modifications will
be made..
.
2. Locate the byte(s) within the sector to change. The
following tables gives the location and function of the
bytes and defaults that are available..
.
3. After you have changed the desired bytes, write the edited
sector back to disk..
.
NOTE: I count bytes assembly style. In other words, the
first byte in a sector is 0 and the last byte is 255.
I am using decimal numbers for the byte #'s and hex
numbers ">" for the default and optional numbers..
.
.
NOTE: Most RS232 cards have 1 PIO port and 2 serial ports. Most
users only have 1 RS232 card. If so, the serial ports are
refered to as RS232/1 and RS232/2. If two RS232 cards are
installed in your system, the second card then becomes RS232/3
and RS232/4, and the second PIO port becomes PIO/2. Since each
card has two serial ports, the computer addresses these by using
two seperate notations; the card address and the port address.
The following tables show you which hex codes to edit into the
program for setting up both the card and port addresses,
depending on your system configuration. .
..
Byte # Default Function and Optional values.
------ ------- ----------------------------.
.
10-11 >1300 Selects first or second RS232 CARD..
.
13 >F4 Selects character and screen colors..
The first digit is character color..
Second digit is screen color..
15 >40 Selects the RS232 port within the card..
.
16-17 >04D0 Selects the modem baud rate..
.
42-43 >03E8 Delay time before auto-repeat for
keyboard (>03E8=1000).
.
44-45 >003C Delay between characters once keyboard
has started auto-repeating. (>003C=60).
.
48-49 >0000 Print spooler type..
>0000=TI card PIO.
>0002=TI, Corcomp, Myarc card serial.
.
50-51 >1300 Select first or second RS232 card for
print spooler..
.
52-53 >0040 Selects the RS232 serial print spooler
port within the card..
.
54-55 >0034 Selects the baud rate for serial print
spooler..
.
56-57 >8300 Selects number of data bits, parity, and
stop bits for serial print spooler.
Color codes (in hex) Baud rate codes (in hex).
0 - transparent >0638 = 110 baud.
1 - black >04D0 = 300 baud.
2 - medium green >0341 = 600 baud.
3 - light green >01A0 = 1200 baud.
4 - dark blue >00D0 = 2400 baud.
5 - light blue >0068 = 4800 baud.
6 - dark red >0034 = 9600 baud.
7 - cyan.
8 - medium red RS232 card and port codes (in hex).
9 - light red >1300 = RS232 card #1.
A - dark yellow >1500 = RS232 card #2.
B - light yellow >40 = RS232/1 or /3.
C - dark green >80 = RS232 /2 or /4.
D - magenta.
E - gray Data bits, parity, stop bits.
F - white >8200 = 7N1 >8300 = 8N1.
>A200 = 7E1 >A300 = 8E1.
>B200 = 7O1 >B300 = 8O1.
..
.
SCREEN DUMP OPERATION.
.
While in the terminal mode, a screen dump can be done without
having to go to the view buffer mode. To dump a screen, the
FCTN and 9 keys are used. It is advised to dump a screen when
the sending computer, BBS, etc. has stopped sending data. If
this is not handy, and the other computer responds to Xon/Xoff
control keys (control S and Q), send a control S to stop the
other computer's data flow. Then, dump your screen to any
device you wish to enter (disk, printer, etc.). After the dump
is finished, enter a control Q to tell the other computer to
continue the data transmission..
.
PRINT SPOOLER OPERATION.
.
The print spooler in M/T shares the same memory space as the
buffer. As such, a few things should be noted while using the
print spooler. First, you must make sure the 1st sector of MASS
contains the proper code to match the program with your type of
printer. If you have not already done so, refer to the previous
steps on sector editing and make the necessary changes..
.
NOTE: I HAVE NOT BEEN ABLE TO OBTAIN THE NECESSARY INFO NEEDED
TO ALLOW M/T TO WORK WITH THE MYARC AND CORCOMP PIO PORTS. THEY
ARE ACCESSED DIFFERENTLY THAN THE TI PIO PORT. UNTIL SOMEONE IS
KIND ENOUGH TO PROVIDE ME WITH THE CRU ADDRESSING INFO, I'M
AFRAID I CAN NOT IMPLEMENT PRINT SPOOLING FOR USE WITH CORCOMP
AND MYARC PARALLEL USE..
.
The print spooler is toggled on and off by simply press the FCTN
and = keys while in the terminal mode..
.
Your printer can fall behind the currently received modem data
if your modem is running at speeds faster than 300 baud. The
print spooler is designed to allow the printer to lag the
incoming data by up to 12.5K bytes. If this amount is exceeded,
the program will initiate certain steps to prevent data loss.
The buffer will close, preventing any more incoming data from
being stored. The print spooler will continue to dump the
remaining 12.5K of data to your printer. After the print
spooler is empty, you can once again turn on your spooler and
resume normal use..
.
Since the print spooler and buffer share the same memory space,
M/T will automatically turn on your buffer if you turn on the
printer spooler. If the buffer is already on, it will make no
difference to the program's operation..
..
If you should have both the buffer and print spooler on, and
decide to turn off the buffer, the print spooler will turn off
also. Your printer will continue to print any data still left
in the spooler. If you should then turn on both the buffer and
the print spooler, you will re-initialize the print spooler.
Any remaining unprinted data will be lost unless you wait for
the spooler to empty. Turning the print spooler on and off will
cause no problems..
.
Since many BBSs often pause while accessing the message base,
your printer should be able to keep up with the incoming data
without falling too far behind. You usually have the option of
pausing somewhat, before reading the next message. This will
give your printer a chance to catch up somewhat..
.
.
PHONEMAKE AND NEW PHONE FILES.
.
The PHONEMAKE program for version 4.1 is the same as the one
used in version 4.0. Nothing in it has been changed, except the
version number itself..
.
You now have the option of using up to EIGHT PHONE files with
M/T. M/T now provides you with a seperate menu screen from
which to make your selection. You have the option of selecting
the "not using phone files". If this is selected, no data is
loaded and any part of M/T that uses this data is made
non-useable, to prevent any program crash..
.
You can load the PHONE file from almost any storage device;
Myarc ramdisk, New Horizon ramdisk, or floppy disk drive. Just
select the appropriate option from the menu and M/T will do the
rest. If you receive an error while doing this, you most likely
do not have the PHONE file available on that device, or the
PHONE file was from a version eariler than 4.0..
.
NOTE: M/T EXPECTS THE PHONE FILES TO BE NAMED EITHER:.
.
PHONE1, PHONE2, PHONE3, ........ or PHONE8.
.
Use your disk manager to rename your old PHONE file to and one
of the above filenames..
.
.
NEW HORIZON RAMDISK SUPPORT.
.
Although I do not have an HRD, I've been told that they can
emulate DSK5. I have included in all parts of the program that
require you to input a drive # the ability to enter a 5. This
should allow full use of your HRD with this program..
.
......................
MAIN MENU INSTRUCTIONS.
.
.
<R> Reconfigure I/O port.
This option allows the user to change the RS232 port and also the
baud rate for that port. To reconfigure your system for a
different setup, select R from the menu. The program will take
you to the Configuration Setup screen. You will then be able to
enter the desired communication parameters..
Although the RS232 port can be changed along with baud rate,
several users requested an easier way to change data bits,
parity, and stop bits. M-T is pre-programmed with the 3
standard protocols; those being 8,N,1; 7,O,1; 7,E,1. These
refer to number of data bits (7 or 8), type of parity (none,
odd, or even), and number of stop bits, respectively. To access
this feature, just press CONTROL R (CTRL R) on the main menu.
You will notice the 8N1 that was underneath the buffer size
counter has now changed. Pressing CTRL R again will again bring
up the next option, and one more time will bring you back to
where you started. Once the selection is made, the RS232 port
is automatically reset to your new specifications..
.
.
<M> Multiple Xmodem Transfer (MXT).
This option allows the user to send and receive an unlimited
number of disk files without having to attend to the computer
during the transfers..
When you select the send option, the program will catalog the
disk and display the directory on the monitor, 10 files at a
time. To select a file for transfer, position the cursor next
to the desired filename and press the <ENTER> key. You may use
the up and down arrow keys to move the cursor. To delete a
previously selected file, position the cursor in front of the
filename, and press the FCTN and 1 keys (FCTN DELETE). To
proceed on to the next screen of directory entries, press the
FCTN and 6 keys (FCTN PROCEED). When finished with the last
directory screen, press FCTN PROCEED one more time and the MXT
transfer will begin..
To abort during a transfer, press the FCTN and 4 (FCTN CLEAR)
keys. The abort will cancel the current file being transfered
and any other files still remaining in the supervisor list. .
When using MXT to send files, the sending computer will pause
for 5 seconds between files. This is so that the receiving
system (if non-MXT capable) can type in the next filename as it
appears on his monitor. If you wish to bypass the 5 second
pause, just press the <ENTER> key..
NOTE: IF USING MXT IN THE RECEIVE MODE, USE A CLEAN DISK. THE
MXT SUPERVISOR ROUTINE WILL CREATE THE FILENAMES ON YOUR DISK
JUST AS THEY WERE LABELED ON THE SENDING DISK. IF YOU HAVE
FILES ON YOUR DISK, THEY COULD BE ERASED AND OVERWRITTEN WITH
THE NEWLY RECEIVED FILE IF THE FILENAMES ARE THE SAME..
..
<H> Hangup after MXT status = OFF.
This option allows the user to pre-select the auto hangup
feature upon completion of an MXT transfer.
The auto hangup will be executed when the transfer is either
successfully completed OR aborted. This feature allows the user
to leave the computer unattended for a period of time, and
return later to see the status of the disk transfer. This
option toggles ON and OFF by pressing the H key..
NOTE: THE DATA NEEDED BY M/T TO HANGUP YOUR MODEM IS CONTAINED
IN THE PHONE FILE. FURTHER, A MODEM CAPABLE OF HANGING ITSELF
UP THROUGH EITHER PROGRAM OR KEYBOARD CONTROL IS REQUIRED. IF
YOUR MODEM IS NOT ABLE TO HANG ITSELF UP, THEN M/T WILL NOT BE
ABLE TO PERFORM THIS FUNCTION. BE SURE TO RUN THE PHONEMAKE
PROGRAM AND ENTER YOUR MODEM HANGUP COMMANDS IN THE APPROPRIATE
SECTION..
.
.
<C> Clear download buffer.
This option clears the buffer. Any previously received data
will be lost. After the buffer has cleared, the program returns
to the main menu..
..
<E> Echo remote status = OFF.
monitor status = OFF.
This option allows the user to select the necessary echo as
needed. The user has control over both the remote and monitor
echo. Varied use of this option will permit the user to
interface with almost any other computer, regardless of what the
remote computer provides/requires in the area of character
echo..
To change either the remote or monitor echo status, press the E
key. A four choice menu appears, allowing the user to turn
on/off each echo. A beep will be heard, when a valid choice is
selected from the menu. When all choices have been made, press
ENTER. The program will return to the main menu, with the new
echo status displayed..
<1> Remote echo - ON.
Echo all received data back to the sending computer..
<2> Remote echo - OFF.
Normally used when communicating with BBS's.
<3> Monitor echo - ON.
This mode shows what you are typing but does not echo the
received characters back to the remote computer.
<4> Monitor echo - OFF.
Suppresses the echo of your typed characters to your monitor..
NOTE: The above combinations of echoes gives the user an
excellent choice to use under various situations. However, one
should keep in mind the following idea. If both computers are
using an echo ON mode, the program usually starts typing a
string of feedback characters since both computers are
re-sending the same character over and over. If this should
occur, it can be stopped by returning to the menu and changing
the remote echo to off. Auto-dialing should not be done with
the remote echo on. This echoing of modem responses usually
causes the modem to misdial or lock up..
..
<U> Upload DIS/VAR 80 file.
This option allows the user to send a display variable 80 file
that is loaded in from disk and stored in the buffer. It will
erase the contents of the buffer. Be sure to save anything of
importance in the buffer before you select this option..
NO ERROR CHECKING is provided in the program as to the SIZE of
the file being loaded. Since the file is placed in the buffer,
care should be taken not to exceed the size of the buffer. A
DV-80 file of about 40 to 50 sectors in length will easily fit
into the available buffer space. Since thie text sending
feature is normally used to send a pre-composed message to a
BBS, this size limitation should be of no real problem..
.
After the file is loaded, you must determine who will control
the sending of the text. You can let the computer manage it, or
you can take control and send it one line at a time. It is
suggested that if you are uploading to a BBS, the line by line
option may be the best choice. Experimentation on your part may
be necessary. Follow the instructions on the screen which will
tell you how to send the data. As the data is sent, a carriage
return is added to the end of each line automatically..
While sending, any prompts or text that are sent or echoed by
the BBS will also appear on your monitor. When the last line
has been sent, you will be placed back into terminal mode. .
..
<A> Auto-Dial from directory.
.
After selecting the "[A]" option from the main menu, you will
see your phone file on screen with three options available for
use..
.
[D]ial is used to dial any phone number you have included in
your phone list. It will dial that number only once, and return
you to the terminal mode. To dial a number, simply select the
desired letter (A-T). Your smart modem will now dial the number
for you..
.
[R]edial is used when you wish M/T to dial a possibly busy phone
number. It will continue to redial the busy number until the
line is no longer busy or you cancel the dialing process
manually. To redial any number, simply select the desired
letter (A/T). After you select the first number to dial, M/T
prompts you for an alternate number. Yes, M/T is able to redial
two different numbers until it gets through to one of them. To
use this feature, just enter your second choice. If you do not
wish to dial an alternate number, just press the enter key, and
M/T will skip the alternate redial feature..
.
While M/T is redialing numbers, it will display the current
number being dialed, along with the status (busy or dial) and
the number of redialing attempts for that number..
[P]c-Pursuit is the last option available in the auto-dialer.
It allows you to let the computer REDIAL any PCP area code you
desire. On my system, I have found that M/T will redial a busy
area code listing 10 times per minute. At that rate, it is
quite easy to get an access line..
.
In order to make use of the PCP feature, you'll need a special
file(s) on disk that contain the necessary info required by PCP.
(ie, password, ID, area code, and baud rate). You can use a
standard DV80 file editor to create these files, or make use of
the editor provided in PHONEMAKE (option 6). If you use an
editor such as TI-Writer, be sure to use the "PF" option to save
your file to disk, as M/T will not work properly with the margin
info normally found at the end of a TI-Writer file..
.
If you use the PHONEMAKE editor to create your file, all the
info needed by PCP is display on your monitor. Just enter
your specific data. After that, your PCP file will be saved to
disk, under whatever filename you wish. Personally, I use
filenames such as 312/12 which indicates area code 312 and 1200
baud..
..
Assuming you have made up the necessary PCP files, you can
auto-dial an area code by first connecting with your local PCP
access line. After you arrive at the PCP prompt where you would
type in the usuall C DIAL 312/12.....etc, just select the
autodialer function from the main menu, followed by the
[P]c-Pursuit option. You will be prompted for the file name
(remember the ones you made using one of the DV80 editors).
Enter the name, and M/T will now faithfully redial that "always
busy" area code for you. When it connects, you are signaled
with a beep from the program (just like before)..
.
At this point, you could use the auto-dialer to dial the BBS
number you are trying to logon to. To do so, return to the main
menu, select the autodial option again, and this time use the
redial feature to dial the BBS you desire..
.
NOTE: If you have PC-Pursuit but do not have a smart-modem, you
can still make use of the auto-dialer features once you are
connected to a PC-Pursuit access line!.
.
CANCELLING THE AUTO-DIALER.
.
To cancel the auto-dialer, press the break key (CTRL /). This
signals M/T to stop auto-dialing and searching for any modem
repsonses..
.
One last comment on using the auto-dialer. The two responses
you supply in the PHONEMAKE program are what is used by M/T for
modem response comparison. My Hayes modem gives a NO CARRIER
for a busy response while my use of PCP shows that BUSY is
returned for a busy number. Keep these modem responses in mind
as you enter them in the PHONEMAKE program. Without the proper
responses and commands, M/T will not be able to control your
smart-modem..
..
<D> Dump download buffer.
This option copies the buffer to a storage device. This device
can be any legal device name that supports a maximum file length
of 80 characters, except cassette. Upon selection of this
option, enter the appropriate filename, such as PIO,
DSK1.SAVEFILE, RS232/2.BA=4800.DA=8, etc. You can also abort
the dump by following the screen prompts. In order to allow the
same buffer contents to be saved to several devices, the buffer
is NOT CLEARED after the dump routine..
NOTE: This buffer is shared with the LOG file. However, even if
you have the LOG file on, you may still dump the buffer contents
to any device you desire. .
.
.
<S> Set up Log File status = OFF.
This option allows you to assign a peripheral device to accept
the contents of the buffer when the buffer fills. You will be
asked for a filename. Most users would use either the printer
or a disk in order to keep a copy of the buffer contents for
later review..
Once the log file has been toggled on, you may turn it off by
simply pressing the "S" key from the main menu. If there is
data in the buffer, it will be sent to the device you had named
as the log file before it closes the file. If you do not desire
to have the buffer contents sent to the log file, then clear the
buffer before closing the log file. Likewise, if you should
happen to quit the program while the log file is open, you will
be asked if you wish to save the buffer contents..
The log file uses an append format which allows the computer to
add on to the previous file contents, if any. This means that a
file on disk will have new contents added to it each time the
buffer fills and dumps to the disk. THE LOG FILE WILL NOT
OVERWRITE AN EXISTING FILE ON DISK..
Since the file append mode can create a file too large to be
loaded by TI-Writer, another way exists in which you can print
the file. The E/A module allows you to print a file directly
from the disk drive. To use this feature, select the EDIT
option from the E/A main menu. Next select the Print feature.
At this point, you will be asked to type in the filename, and
then the printer' filename. Upon entering your printer's
filename, the file will be read off of the disk and sent to your
printer..
.
NOTE: M/T sends an XOFF (control S) to the other computer when
logging the buffer contents to the assigned peripheral. After
the buffer is emptied, the program sends an XON (control Q) to
allow the sending computer to continue. This is commonly
refered to as Xon/Xoff protocol. A BBS that supports this
protocol (most of them do) allows M/T to dump the buffer and not
miss any incoming data since the BBS will not be sending any
during this time..
..
<V> View buffer contents.
This option allows the user to view the contents of the buffer
without destroying it. As an added feature, any portion of the
buffer can be saved to any peripheral via the screen dump
option. This allows the user to read or save a message without
having to dump the entire buffer. Scrolling of the displayed
text is controlled by the space bar. Press the space bar once
to stop the scrolling and again to start it. Pressing FCTN 4
(CLEAR) will abort the viewing option and return to the main
menu. To use the screen dump option, allow the screen to scroll
to the desired text. Stop the scroll and press the "P" key to
start the screen dump. You will be prompted for the output
device name. After the screen dump is completed, you will be
returned to the viewed screen. You may continue the viewing,
printing more screens if necessary, or abort back to the main
menu with the FCTN 4 keys..
<B> Buffer capture status = ON.
This option allows the user to control the flow of data into the
buffer. When the status indicates ON, all data is stored in the
buffer. By pressing "B", the buffer will toggle between ON and
OFF..
.
.
<L> Line feed toggle status = OFF.
.
This option allows the program to provide a linefeed after each
received carriage return. Pressing the L key will toggle the
option between ON and OFF. These linefeeds are not stored in
the buffer, since they are not received data, but rather
generated locally by the program. This option is very handy
when accessing a BBS that does not supply linefeeds after
carriage returns or when receiving an uploaded file from another
computer. When toggled ON, it also causes double spacing of the
buffer contents when using the view option..
..
<X> Xmodem File Transfer.
This option allows the user to transfer a file to another
computer using the xmodem protocol. As with the other xmodem
file transfer programs available for the TI computer, this
routine provides the user with compatiability with these other
programs. It supports both CRC and checksum error detection.
The filename for the transfer is assigned after entering this
routine. Retry, record, and sector (current and total)
indicators are updated constantly (files other than DIS/FIX 128)
on the monitor, along with disk access errors. Transfer status
is indicated upon completion or aborting of the file transfer.
You may use the FCTN 4 keys to abort the transfer..
NOTE: TO SEND A DISPLAY FIXED 128 (DF-128) FILE IN LARGE BLOCKS
RATHER THAN THE USUAL 1 SECTOR AT A TIME, USE THE MXT FUNCTION.
THIS WILL ALLOW THE RECEVING TI COMPUTER TO PROCESS THE FILE AS
THOUGH IT WERE A "REGULAR" TI DISK FILE. (SEE COMMENTS ON MXT
SENDING AND RECEIVING).
.
<F> Files (catalog disk) Selection this option from the main
menu allows the user to catalog a disk. M/T will prompt you for
the drive you wish to display. I use this catalog feature on my
Myarc ramdisk. I can not guarantee it will work on other
versions of Myarc ramdisks, or any other brand of ramdisk
either..
.
.
..
*****************************************************************
NOTE: MASS-TRANSFER was originally designed for use with the
smartmodems. Although it will work with other modems, one item
must be remembered. Some modems (specifically the TI) will not
allow the RS232 card to send it data when it is not linked with
another modem. During this time, if the program attempts to
send the modem data, the computer will appear to lock up.
Actually, the program is attempting to send the modem a
character, but the modem refuses to accept it. The easiest fix
for this problem is to try turning the modem on or off. This
will usually prevent/cure this "lock-up" condition..
Your modem may differ in other ways.
****************************************************************
I'd like to thank the many users of my old TI-North BBS
(312-395-4618) who provided me with many ideas on how to improve
my program..
You can call my new BBS at (602) 848-6200.
I'd also like to thank my wife, who I've made a computer widow
during the countless hours spent working on this program..
.
......................

 

MassXferDocs.txt

masstr41.zip

  • Like 2
Link to comment
Share on other sites

These are the documents for Term80

 

I have also attached the .DSK image for Term80 for anyone who needs it.

 

 

***edit***

 

These docs are truncated to 60k, but you can get the full versions inside the disk image. The docs are there. :)

 

 

 

 

 

 


 

.CO Please Print Using the TI Writer Formatter
.CO Written by Jeffrey Brown for v3.1.4
.CO Updated October 27th, '95 from v2.7.8
.LM0;RM80;IN0
.CE3
Term^80^Documentation
v2.7.6
Main^Documents
Term80 is CopyRight 1994-1995 by author Jeffrey Brown. Any illegal use
of this program is punishable by law.
.HETerm^80^Docs^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^@Index^^^
.BP
I. Opening Remarks
A. Purpose of Term 80
B. Meet the author!
C. CrippleWare/Commercial versions
D. The LAW
II. How to set up Term 80
A. System Requirements
B. Fuzzy screen?
C. RS232 cable/modem info
D. Setting up the main program
E. Setting up the loader
F. Setting up the autodialer module
G. Setting up the external program loader
III. Using the main program
A. Using menus
B. How to startup Term 80
C. The status screens
i. The MAIN status screen
ii. The ANSI status screen
D. The external modules
i. The help menu module
ii. The autodialer module
iii. The download module
iv. The upload module
v. The ascii transfer module
vi. The macro module
vii. The external program loader
viii. Unfinished modules
E. The keyboard commands
F. ANSI? What's that?
VI. Advanced features/functions
VII. Appendices
A. Ordering the full version of Term 80
B. Known bugs
C. ANSI v3.64 protocol
D. Quick reference list of keyboard functions
E. Possible problems & solutions (errors)
F. Filenaming scheme
G. Glossary
H. The future (v4.0+)
VIII. Ending notes
.PA1
.HETerm^80^Docs^^^^^^^^^^^^^^^^^^^@Opening Remarks^^^^^^^^^^^^^^^^^
.BP
Well, these are just a few opening notes before you start using Term 80.
PLEASE read the manual FULLY before you attempt to do anything, and if you have
ANY questions, please contact me, or another knowledgeable person before
proceeding. (It is better to be safe than sorry!)
A. What's the purpose of Term 80?
Term 80 is a full terminal emulation program designed for the TI-99/4A
computer. (if you have a Geneve, you CANNOT use this program! Don't even TRY!)
It is the ONLY 80 column terminal program (that I know of) which does NOT need
an expansion video card or the like to provide full-screen 80 columns without
page flipping or scrolling. It also supports many other screen widths but in
each and EVERY mode, the display is in full 8 colour ANSI.
Note: All menus are fixed to 80 columns, if enough of you complain, I MAY
make that optionnal...
B. Who wrote this fabulous program?
Term 80 was programmed by myself (duh!), Jeff Brown, in Ottawa, Ontario
(Canada) on my TI computer. I'm only 15 at this moment, but I started it
11 months ago (at the end of August, '94). I'm going to be starting 10th
grade this September (god knows how boring that will be. <sigh>), but I
have receive special permission to enter the 12th grade computer couse ©.
Currently I program in:
- TMS9900 Assembly
- TI Basic/XB & hybrid XB/Assembly
- TI Logo
- Some C
- GFA Basic v2.0 (not too often though... a little boring, not too powerful)
- Amiga E (my FAVORITE!)
- Watcom Basic (it this basic? really? it's WAYYY out of the standard!)
- A logo we had at school (in french, quite different from TI-Logo!!)
- bunch of other ones
C. Pirating my program?? Wait a sec.... it's commercial!
Well, to those who think they can pirate my program and get away with it,
think again! There's a law preventing that (see next page). At the time of
this writing, there are two versions of Term 80:
1) Crippled (free) version:
This version may be distributed free of charge although it lacks many useful
features, such as the upload/download and macro functions. At ALL times it
must be distributed WITH ALL THE ACCOMPANYING DOCUMENTATION AND FILES!!!!
2) Commercial (pay) version:
This version is commercial, meaning you must pay for it. It has all the
features of Term 80, and perhaps, some other goodies. This version entitles
you to cheaper updates of the program (like a couple $$ plus shipping).
D. Still want to pirate my program? Think again!
So you think you can still get away with passing out copied of my program?
NO WAY! All commercial copies are serialised and therefore come update time
if I get two people claming the same serial number, or even just not on my
list, I'll get the law down on your back QUICK! Other important things which
are kept are addresses and phone numbers :) So forget about pirating my
program. If you want to pass out copies to your friends, give them the
crippled version.
I don't want to sound mean, but I don't like being robbed... would you?
--------------------------------------------------------------------------------
.HETerm^80^Docs^^^^^^^^^^^^^^^^@How^To^Set^Up^Term^80^^^^^^^^^^^^^^^
.BP
A. What do I need to run this thing?
All you need to run this is a TI (not a Geneve) with 32k RAM and 1 DSSD
disk drive (an SSSD would be too cumbersome). You will also need an RS232
card (or side-cart "daisychain" style) and a modem (any speed >=300bps).
You can theoretically run this on TI Emulators, however I recommend against
it. I do not want to endorse a product or anything, but so far the only
emulators I have seen that would be capable of handling Term 80 are PC99
and V9T9. It would seem strange to run Term 80 if you have a PC, anyhow!
B. Heh, what do I do about this screen?
Term 80 uses standard bitmap mode to provide a colour 80 column simulation.
The letters are only 3 pixels wide, and stuck together (in 80 col mode) so
you should run this program on a monitor. Although Term 80 does not use any
80 column video cards, RGB video device replacements and the like will
dramatically improve the image. You should try playing with the brightness
and contrast of your monitor. You may have to play with the focus a bit.
Even after trying this, it may still be a bit hard to read, but after a
while you get quite used to it. What is confusing sometimes, however, is
the colour emulation. Because of the 9918A's video limitations (2 colours
per 8 pixel wide block) the colours may bleed into segments of the next
letter even if it is supposed to have a different colour. Normally this is
not a problem, but if you call typically colourful bulletin boards, you can
always switch the colour emulation off. There is also a keyboard function
which allows you to reset the screen's colours to white/black (see keyboard
commands). Another thing to note about colour is the fact that I chose the
best looking combinations of each of the 8 ANSI colours' TI "equivalents"
and made a lookup table for the program. This means that say, white on blue
might have a darkey "blue" than black on blue. This was done to make things
more legible. You may notice in colourful screens that in fact there are
different shades of colours depending on the fg/bg.
There is also a hardware modification which can be done to enhance the
sharpness of the display. I have not tested it myself yet, but the author
apparently claims a good 40% improvement of picture clarity! Anything you
do is at YOUR OWN RISK!!!
From the OK-99 User's Group Newsletter of May '89:
"There are quite a few hardware modifications that can be done on the
TI99/4A. I have not triem tem but will pass on the information to you
so the brave at heart can give it a try. This and all modification to
the TI you do at your own risk. The proper kind of soldering iron and
equipement is necessary.
For some reason the load resistor that TI called for in the VDP LOAD
RESISTOR was replaced with one of higher value which causes ghosting.
The resistor in your computer is 560ohms and the recommended value should
be 330ohms 1/4 watt. This change will improve the picture by 40% and
you'll wonder where the WHITE SHADOWS WENT. All that is required for you
to do is unsolder the old resistor and soler the new one in its place."
Anyhow... he included a little graphic... to hepl you find the resistor, it
has the stripes coloured Green/Blue/Brown/Gold, and in most consoles it is
located (looking "up" with the keyboard connector towards you) just one
resistor below two transistors in the top-left corner of your console. If
you can't find it, try following pin #6 of the TMS9918A through two inductors
(they're big red things that kinda look like resistors) until you get to a
resistor (striped as noted above). Oh, another little hit is that the other
end of the resistor is grounded... (other, meaning the one not connected to
the inductors).
C. What do I do about the cable?
You can use the same cable as you would with any other terminal program.
This cable is quite simple. Basically all lines are straight-through from
the modem to the computer, with the exception of pins 2 & 3 which must be
swapped. If your cable works well on other terminal progs. it should work
fine with Term 80.
Because of the older modems most TI's seem to use, Term 80 does not use
RTS/CTS handshaking. Instead it uses an XON/XOFF method of making sure the
buffer doesn't overrun. You can disable this mode, if you so desire. If
people tell me the kind of cable required and give me hardware information
on RTS/CTS implementation on the TI, I will update the program for it.
D. Down to business, how do I set up Term 80's main program?
Using any standard EA #5 (TI-W #3) loader program, run the program called
C_MAINCFG. When it asks for the drive where Term 80 is located, insert the
disk containing the main program, and type the number. (or <enter> if it
guessed correctly). Note: you CANNOT use names beginning with anything other
than DSK. See the Appendix for more info on these limitations.
You are now presented with a menu (if it error'd out, the program wasn't
found!!). I will go section by section:
(like most menus, use the letters to enter/chage items, and enter to exit the
menu, or to terminate manual entry, hitting enter on the main menu, saves and
quits.)
a. Modem Config
A. Modem Init String
The current initialization string. It is a string input region which is
terminated by an <enter>. The "!" is interpreted as a carriage return in
the string, and "~" is a 1 second pause. My string is: ATZ1!~~~~AT&K0!
B. Modem Port Number
This is a toggle for what modem port is being used! 1, 2, 3 or 4.
C. Default modem baud (bps) rate
This shouldn't be too high, although Term 80 does support up to 19200,
the resulting slowdown is due to the frequency of port scans required to
catch the chars. (remember, no RTS/CTS so I can't pause it fast enough
to prevent data loss, meaning I have to check when there's data!) I use
4800 for normal communication, and only use 9600 or 19200 for HS data
transfers. (you can change it within the program)
D. The modem parity
Available are: 8N1, 7E1 and 7O1. These translate down to: x data bits,
even, or or no parity, and 1 stop bit. Check your RS232 manual.
E. XON/XOFF flow control, on/off
F. RS232 port scan rate
If you have an accelerated system, you can slow down the scan rate to
improve performance somewhat. Normally just leave it at normal. If you
have lots of data loss, or transfer errors, speed it up.
b. Printer Config
Note: none of these configs can be changed from the main program, except
the default printing status.
A. Printer port number
Just the printer port. Note Term 80 does direct accessing of the port!!
B. Printer baud rate
Not required if PIO, but like the modem, this is the printer's baud rate.
C. Data bits
Again, not required for PIO, but this is the printer's data bits.
(typically 8)
D. Parity
The printer's parity, normally none. (unnecessary for PIO)
E. Printer stop bits
Again, not required for PIO. Normally 1.
F. Default print status
On bootup, printer enabled or disabled?
G. Printer wait status
If the printer cannot be accessed, you can choose to have it pause until
the printer is clear (wait) UNINTERRUPTABLE! Skip past it, (no wait),
timeout after a certain wait time (timeout) or wait until it can be
accessed but interruptable (w/intrp.).
c. Buffer config
This defines the amount of buffer space available to Term 80.
A. Main buffer
The main RS232 input buffer space allocation. Maximum is 65535. This
should be at least 8192 (bytes). The program tries to allocate as much
RAM as possible for the buffer (but not exceed the limit you establish)
after which it will spill over into the temporary storage.
B. Temporary storage
At the moment, the temporary storage is allocated but UNUSED. You should
set this to 65535 nonetheless. When implemented, it will store frequently
used modules to speed things up. It may even be used as a sort of RAMdisk.
d. Emulation config
All these can be changed within the main program, and even by autodialer
entries. They define what Term 80 is supposed to do!
A. ANSI/VT52 interpreter
Default interpreter setting, ANSI only, VT52 only, BOTH, or disabled.
B. ANSI colour
Hate colours? Disable it then... If you disable the interpreter, you also
disable ANSI colour.
C. ANSI tabs
Tabs should be left on at ALL times! Like ANSI colour, if the interpreter
is off, these are too.
D. Cursor control method of preference.
Defines what is to be sent when various cursor keys are pressed.
Note: At ALL times, Fctn-1 is a forward delete (DEL, ASCII 127) and
Fctn-9 is a true backspace. (ASCII 8)
TI: The cursor keys (FCTN-E, S, D & X) send codes like they would in TI
Basic. This isn't really very useful, as most BBS's interpret the
codes with other meanings.
TABS are DISABLED in this mode because the TI Basic interpretation
of that code is a forward move (?).
VT/AN-BS: Send ANSI or VT52 key codes (see appendix) for all but the
FCTN-S, which is send as an ASCII 8 (standard backspace) instead
of a cursor movement command. If you are running VT52 only, VT52
cursor controls are sent... in all others, ANSI codes. TABS are
enabled in this mode.
VT52/ANSI: Send ANSI or VT52 key codes at all times (see appendix).
Backspaces must be accomplished using Fctn-9. (my preference for
visual editors) The actual codes sent depend on the interpreter mode
(see VT/AN-BS). TABS are enabled in this mode.
E. Initial TAB setting
The default is 8, which is what most systems use (maybe all). It means
that tabs are space every 8 chars.
F. Echo/Duplex toggle
Full or half duplex. If you see double, the you should set this to Full,
if you see nothing, then use half. Most modern BBSs require full duplex.
G. CR translation IN
How carriage returns are interpreted when received. As CRs, LFs, or both.
Normally use CR.
H. CR translation OUT
How carriage returns are sent out. Normally use CR.
e. Screen Config
A. Screen size (width)
The default screen width. 80, 64, 54, 40, 36 or 32. (colour is available
in all modes.) You should use 80.
B. Default foreground colour
Most bulletin boards expect the default foreground to be white.
C. Default background colour
Most bulletin boards like a black background.
D. Default backdrop (border) colour
A TI colour to be placed in the screen border. This can be anything you
like...
f. Other Configs
A. The keyboard scan rate
How fast to scan the keyboard. Like the RS232 scan, if you have a fast
system, you can slow this down. If you find the keyboard sluggish, or
misses chars, speed it up! Default, normal. (duh!)
E. Setting up the loader (pathname)
Run the program C_PATHCFG using an EA#5 loader.
This one's easy. It just configs the loader to help find Term 80. Enter
where the loader program is (RS232/RS233), then it will show the current
drive #, then enter the new drive number. Using "*" is an autodetect mode.
If you are likely to put Term 80 in different drives, this is for you. It
may not work on some devices (esp. RAMdisks) so if possible, enter the drive.
After entering the drive, it saves and quits.
F. How do I config the autodialer?
If you have the demo version of this program, you don't have the autodialer
so you can skip this part. (it is a very flexible dialer, which is the best
I've seen so far on a TI)
Like the other two config programs, run C_DIALCFG using an EA#5 loader, then
enter the drive where Term 80 is. (specifically where R_DIALER is... it should
be on the same drive as Term 80....)
After a few seconds, it should load the dialer entries, which it will
display. Like the main program config, enter the number, or letter of what
you want to change to select it. Hitting enter will end the current entry
field, or exit from a menu. If it's the main menu, it saves & quits.
1. Retry delay
This is the amount of time allocated to connect to a certain system before
it times out. It will move on to the next number it detects certain strings
too. Typically this should be 60secs or so, but if you have a pulse line,
you might want to play with it a bit.
2. Delay between numbers
How long it waits before it tries the next number. This is here so the modem
properly hangs up and is ready to receive the next dialing command if the
last timed out. Typically, 2 secs is good.
A-Z. Dialer entries
Hit the letter to enter the dialer entry configuration menu:
a. System name
A text entry field for the system name
b. System number
Another text entry field for the number of the system. This MUST have
the dialing command included in it. (like ATDT) The reason for this is
that I use different modem configs for a bunch of boards, so one of my
entries might be: AT&Q6S37=006N0D and then the number....
c-i. ANSI defaults, like in the main program. It will reconfigure to these
automatically on connection. (See main program init)
j. Screen width, as in the main program. Like the ANSI defaults it configs
to this...
k-o. RS232 defaults, see the main program init (RS232 section) for more
info.
p. Login macro
If there is a login macro for this entry, enable it, else, disable it.
It is ok, to leave this enabled even if there is no logon script, however
it will slow down the system because it must load the macro routine.
These macros follow the same rules as the normal macros, however they are
named differently. Normal macros start with: M_MACRO/, these begin with
L_MACRO/. The login macro for dialer entry A would be named: L_MACRO/A,
for B: L_MACRO/B etc... All internal macro functions are identical.
Note that during the macro sending, all ANSI input interpretation is
delayed until the end of the macro. (actually, all displaying is delayed)
G. How do I set up the external program loader?
The external loader can be any EA#5 program, however included with Term 80
is John Johnson's BOOT program. To install another program, just rename it
to R_LD on the Term 80 disk. I may come around to designing my own loader,
but for now, unless John objects, I included his marvelous program.
Note: I have not tried any other progs as the external loader for Term 80, so
I am not quite certain if they will run correctly from Term 80. I made
a very simple loader program, possibly too simple, to load external
stuff. (it was VERY tight fit because of having to load BOOT into low
memory) If you know assembly, you could build a secondary loader if
mine fails, quite simply. Just compile your loader program so it will
load into load memory, and name the memory image result R_LD.
--------------------------------------------------------------------------------
.HETerm^80^Docs^^^^^^^^^^^^^^^^@Using the Main Program^^^^^^^^^^^^^^^
.BP
A. What are all these windows??
Windows and menus make up most of the Term 80 user interface. Most commands
are controlled from these displays. Among them are status menus and program
requesters (for filenames...). As in the configuration programs, items are
selected by pressing the key corresponding to the desired function/option.
Most items are toggles, but a few are string input gadgets. Menus are
typically exited using the <enter> key, however some use other keys (because
exiting the window would mean interrupting a task).
B. How do I start up Term 80 now?
Using any EA#5 loader, run the program RS232 on the Term 80 disk. This
program (RS232/RS233) should display the program's startup image. Hit any key
to load the main program. DO NOT run RS234 directly!!!! The Term80 loader sets
up pathname information, and of course displays information which MUST be
seen. To skip it isn't permitted! (besides, I doubt any other loaders could
load Term 80 properly directly!)
When Term 80 starts up, it will open up a little window on the screen
which displays bootup info. I admit, this used to be just a little debugging
display while I was working on the device drivers, but I like it, and it
is nifty to look at. Just be patient and watch. (yes, the display is slowed
down.... it goes through a big loop so it doesn't just blip by!)
If all goes well, you should see the main program's message ("Welcome to
Term 80!"). There are many errors which can occur however. If any error
messages come up, READ them, and refer to the list of bootup errors in the
appendix for help!!! Such errors can include devices which weren't found,
or even fatal memory errors! Watch out!
If you see a flashing cursor and the window disappears, all went well.
Oh yeah, one last thing, make sure your modem is on when you start Term 80,
if it's off, the program may lock until it is available, or skip past it,
not initializing it. (this also goes for direct computer-computer transfers,
make sure the other program is on, and the cable strung.) Nothing really bad
can happen if the modem isn't ready though.
Final note: ALL string gadgets backspace using Fctn-9, and end in ENTER!
C. Ok, what are the status menus available?
The terminal emulation and various important setup options are divided into
two menus. The first is the ANSI status menu, and the second, the RS232
status menu, described in the following sections:
i. ANSI Status Menu
The ANSI status is currently entered using Fctn-4 (See appendix for key
list). It controls then ANSI interpreter, and the ANSI current status.
The list is divided in two, items A-E are all the interpreter controls,
and F-M control the current ANSI colours, text attributes, cursor, and
insert mode.
a-e. These are identical to the main program setup controls, and permit
changing of ANSI status "on the fly". (see main program config)
f-g. These two toggles change the current ANSI colour (NOT the colours on
the screen already, however!!).
h-k. These 4 toggles are self-explanatory. They modify the current text
attributes (NOT those onscreen already!).
Note: Bold & Blink text are ignored for now.
l. Toggles the cursor on/off. If the cursor disappears on you, you can
bring it back with this.
m. Insert/overwrite mode toggle. Normally this should be overwrite. It
toggles what happens when new data is received and there are chars
further along in the same line. Insert mode is RARELY used, and it
is rather slow. Most visual editors use the character insert ANSI
command (which insert uses). If when you type things it displaces
characters further along the line when it's not supposed to, check
this item! (ie. don't scream at me!)
ii. RS232 status menu
The RS232 status menu is currently accessed using Fctn-5. It provides all
the main functions to control the RS232 emulation, as well as displaying
a few other pieces of information. REMEMBER THIS KEYPRESS!
All the functions are identical to their Main Program Config counterparts.
Note: Buffer overrun prevention means XON/XOFF.
On the last 4 lines of the menu, you should see buffer information. The
free RS232 buffer space updates as data is received, so you can see it
get smaller and smaller! The module buffer is not used at the moment,
but you can still see how it configured the buffers.
Note: If the Free RS232 buffer space scrolled down "past 0" the buffer
overran. You will have data loss, and strange results. This isn't
supposed to happen, but sometimes XON/XOFF isn't enough to stop it.
Recently I've had trouble with XON/XOFF... for no reason at all. If
you have any problems, tell me! I will check it out. (It's worked
perfectly for almost 8months now though...)
D. Ok, what are the available external modules?
Term 80 is made up of a lot of modules. These include the transfer utils and
autodialer functions. The main reason for modules is that an unexpanded (32k)
TI cannot fit all these routines into RAM. Therefore, I put them all out on
disk, to try and maximize the amount of buffering space without slowing down
the system too much. Term 80 should be run off a RAMdisk for this reason.
Note: System key commands CANNOT be executed from within modules.
i. The help menu
The help menu module is loaded using Fctn-7 (Aid). It displays all the
key commands to date, even the unimplemented ones. Use the spacebar
to flip pages, and enter to exit. You CANNOT execute any of the keyboard
commands from within the module! You must exit first!
ii. The autodialer
The autodialer is only available to people who purchased the full copy
of Term 80. It is called using Fctn-2. When loaded, it should display
the list of names/numbers you entered using the Dialer Config program.
On the last line of the menu, you can enter a list of what numbers you
want to dial. You can enter them in ANY order, and even repeat numbers
multiple times if you like. An example might be "ABAC". Number A will
be dialed, if it does not connect, then B is called, then A, and
finally C. It will then repeat back to A. It is quite simple to use...
just enter the corresponding letters, and end with enter. If you don't
want to dial anymore, just enter an empty list.
After hitting enter, the dialer status will be displayed. Shown are
the current name, number of retries, and last modem status (the last
string received from the modem). The functions provided are also listed.
If the autodialer receives "CONNECT" it assumes you connected, sets up
the main program according to the setup you provided in the dialer
status. If "NO CARRIER", "ERROR" or "VOICE" is received, it assumes
it didn't connect, and goes on to the next number. If no recognized
strings are receive within the time you allocated before timeout in the
setup, it moves on.
Note: The baud rate and parity are set up before dialing each number
according to the configuration you provided forthat particular
number.
Hitting the spacebar skips to the next number, Fctn-4 deletes the
current number from the dial list. If the list is now empty, it exits.
If you press Fctn-9, it just exits. That was easy!
iii. Downloading stuff
Like the autodialer, this is only provided if you pay! <nasty grin>
The download module is started up by Fctn-6. It provides 4 transfer
protocols: TIBBS Xmodem, Xmodem-CRC, Xmodem-1k, and Ymodem Batch. The
other 2 protocols on the displayed menu (Ymodem G and Zmodem) and NOT
currently supported because of the fact that the RS232 on the TI does
not have an internal buffer for true asynchronous transfers like Y-G
and Zmodem.
For the Xmodem protocols, you must enter the filename you are receiving.
"DSK ." is provided for you. Just enter the drive number, then the file
name. When you hit enter, it will attempt to start the transfer.
Note: Xmodem 1k block means that each block is 1k long. This is more
efficient, than the normal 128byte blocks.
Ymodem transfers are easier, just enter the drive number and hit enter.
It should start a batch transfer. All filenames will be displayed and
the size shown too. Theoretically, this protocol can receive an infinite
number of files.
Note: The TIFILES header is received and used if possible.
The transfers can be terminated by Ctrl-X. You must HOLD this key
because for better efficiency, it only checks for aborts at the
beginning of each block. Even though Term80 supports 19200bps, the
download routine is not fast enough to handle it. However, it does
handle 9600bps quite nicely, with my best CPS record being at about 800.
(measured by the Amiga I was transferring from)
iv. Uploading things
You want to upload? Use Fctn-Shift-6
Well, this is very similar to the download routine. The same 4 protocols
are supported. Uploads are as easy to use as downloads. The main thing
to remember is that TIBBS-Xmodem sends the TIFILES header ALL the time,
the other protocols don't send it if the file is DF128 unprotected.
The Ymodem protocol is a smart Ymodem which sends 1k blocks whenever
possible, and finishes off the transfer with 128byte blocks if there's
not enough left for a 1k block. You can send at 19200bps without a
hitch, with my best transfer rate at 1340cps!!! AMAZING!
Again, abort using Ctrl-X.
v. Sending/Receiving ascii files
I apologize for the cumbersome Fctn-Ctrl-Shift-6 keycode you need to
call this routine. I didn't think about it at the time <sigh>.
Although the safest and most efficient transfers are binary transfers,
ASCII isn't so bad for text files and capturing information. Because
of the lack of a capture routine (except to printer), you must use
an ASCII receive to get things. It uses XON/XOFF at all times, as per
the ASCII transfer protocol.
To use it, just enter A or B, depending on if you want to upload, or
download the file (C to abort), then enter the filename. It should
transfer the file. Use Ctrl-x to quit.
Note: The transfer will NOT be stopped unless either you press Ctrl-X,
or one is received.
vi. The powerful macro/scripting function
Well... for those who didn't pay (wish you did yet?). The macro routine
is called automatically by the autodialer if you enabled autologon, but
for other mcaro purposes, you can call it with Fctn-8.
If called manually, it just pops up a little requester for the macro
number (case sensitive!!). You MUST enter a number, I haven't built an
abort feature into the requester. If you enter a nonexistant one, it
exits. While sending, pressing Fctn-9 will abort the macro send.
Macro name patterns are simple to use and remember. They follow the same
kind of naming scheme that the rest of Term80 uses (See appendix).
"Manual" macros use the pattern M_MACRO/x, and "AutoLogin" macros use
L_MACRO/x. In the preceeding, "x" represents a number, letter, or other
valid character in filenames. The name is CASE SENSITIVE!!!
Note: AutoLogin macros numbers are the letter of its corresponding
dialer entry. (uppercase!)
Note: Macros are limited to about 3k each, but you can chain many
together to make HUGE macros!
Macro Functions:
Macros will send plain text normally, but there are also a bunch of
scripting/timing functions available. One MAJOR thing to note is
that no linefeeds or carriage returns are appended to the end of
macro lines. To add them, use {M}{J} which (as shown below) is CRLF.
To send a control code (ASCII codes 0-31, see appendix), encase the
caracter corresponding to the code required + 64 in {}. ex. {@} is
a NULL (ascii 0), {M} is a Carriage Return (13), {L} is ASCII 12, and
{`} is ASCII 31.
Half-second pauses can be acheived using {,}x, where x is the length
is half-seconds. (it MUST be ONE digit)
Two-second pauses are available usgin {.}x, again, x being the length
is two-seconds. (again, MUST be ONE digit)
To enter an arbitrary ASCII character, use {#}xxx, where x is a 3
digit number representing the ASCII code.
You can also chain macros with {&}x, x being the macro's name. (one
char)
As for scripting, this very powerful function is EXTREMELY useful...
{?}xxxxxxxxx| waits for string "xxxxxxxxxx" (case sensitive). The
string can be as long as you like (but should be shorter than 1 line)
and is terminated with a pipe ("|").
Because theoretically the buffer could overrun in the middle of the
macro (your RS232 buffer), you can purge the buffer with {^}. This can
also be used so that you don't have to look at all the data that came
in during the macro, so if you have an autologin macro that leave you
at the menu prompt, you could just purge the buffer, and skip to it
immediately.
Note: Macro chaining is NOT immediate, it is deferred until the end
of the macro is reached. So... you could put the chaining
command at the very beginning of the macro, but it will only
chain when this macro's done.
Future possible enhancements:
In the future, I am planning to add a "command oriented macro"
where you could do things like "GOSUB" to another macro, then
"RETURN" back, and allow the creation of requesters with
cases depending on what you select. Maybe you could make a
requester to ask who you are logging in as (in a login macro),
Branch to a routine to send the name/password, then come back
and finish off the macro. Anyhow, to be seen... suggestions?
vii. The external loader
To load the loader which loads R_LD (yes, Term 80 loads the module,
which loads a 40column charset, then loads R_LD), hit Fctn-Shift-8.
(see the external loader config for more info on this)
It is very easy to use, but remember, when you exit Term 80, you can't
come back unless you reload it, so make sure you really want to leave
before entering Yes at the requester.
viii. Other modules
At the time of this writing, there are two other modules not in the
above descriptions. The first is the character set. Because of the very
memory-expensive size of the charsets (2), I cannot afford to have both
in RAM at the same time. Whenever there is a charset change, it loads
the module into RAM, and copies the new charset into the charset buffer.
Because of the charset out on disk, you should avoid running Term 80 in
40 column mode because every menu you load (80 cols) will require the
loading and swapping of charsets. You should also run Term 80 off of a
RAMdisk.
The other module is a screen saver. It is a very simple, yet slow
routine (slowed down because it still does key and RS232 scans). It
is quite nice, however, and can be called manually by Fctn-Shift-9, or
it is called automatically if no data is received, or keys pressed
within about 10minutes. The first keypress or data, will exit the screen
saver. (BTW, a full version of this simple program is included with
Term 80.)
ix. Well, I've not had time to finish these...
If you check the help menu, you'll notice some modules which don't
actually exist in this version, these include:
- Review Buffer
- File Editor
- Disk Cataloging
- UUencode/UUdecode routines (I lost my docs! ARGH!!!)
The review buffer is not done yet because of the complexity of skipping
ANSI control code, or interpreting them. It'd be very easy to do if you
started off the buffer from the beginning, but that would be quite
inconvenient. Anyhow, it should be done for the new version.
E. Term 80's keycodes!
Term 80's interface is mainly by keyboard, so a good description of the key
mapping and commands available, would be in order.
I built Term 80 with multi-liguistic caracterstics in mind to some degree.
By using certain key combinations, you can send accented characters and the
like. Hitting Fctn-Shift and a letter simultaneously will display the letter
with an "Accent Aigu" on it if possible. Ctrl-Shift-letter puts an "Accent
Grave" on the pressed letter. Fctn-Ctrl-letter sends a "Circumflexed" letter,
and Fctn-Shift-Ctrl sends a special accent for some letters.
Note: Not all letters can be accented. Only those in the ANSI character
mapping can.
The available letters for accenting are:
Accent Aigu - A E I O U "'"
Accent Grave - A E I O U "`"
Accent Circumflex - A E I O U "^"
Accent Special - A C E I N O U Y Diaresis (two dots on the letter)
for A, E, I, O, U & Y,
Cedilla (thingy under Cs)
for C,
"~" on N.
Note: In the extended keypresses, you will notice strange things if you say
press Fctn-Shift-D... instead of seeing a D (because it's unsupported
for accents) you see an accented A! The reason for this is the way the
TI maps the keycodes. I had to "fake" out the machine to get it to work
well.
The keyboard can also be used for quick toggling of some modes, such as the
ANSI interpreter. You can see these keys in the help menu, as well as listed
at the end of this manual, in an appendix.
F. What the heck is ANSI?
ANSI is the American National Standards Institution, and one of the things
they designed and standardized was the ANSI terminal emulation protocol.
The protocol provides for all the commands to be used by systems for doing
such things as formatting text, and controlling all the necessary functions
to make communication of text/graphics/sound viable. ANSI is almost 100%
compatible with VT100 (which is a subset of ANSI in most ways), but quite
incompatible with VT52. Basically, you can use Term 80 with VT100 and up.
My ANSI compliance is near perfect. I support all the main functions that
ANSI has, and ignored those which are never, or rarely used. (protected text
block, etc...) I implement 8 Colour ANSI, which as the name implies, has only
8 colours. One thing I don't support, which I should (but the TI is too
limited to handle properly) is Bold Text. Blink Text is rarely used, or
supported, so I ignored that too. (not to mention it's next to impossible to
do properly on a TI!) Italics are also completely ignored... on a lowres TI
italics are impossible to get looking good anyhow.
The ANSI implementation I have made has all the standard cursor movement,
text/line inserts/deletes, screen segment deletes, etc... To see a comparison
of supported commands with other terminals (like Telco), and the list of
actual command codes, see the appendix on ANSI control.
--------------------------------------------------------------------------------
.HETerm^80^Docs^^^^^^^^^^^^^@Advanced^Features/Functions^^^^^^^^^^^^^
.BP
Well, to date, I must admit, there are no really "advanced" functions... so I
suppose this is a waste of a page! <sigh> There are a few things you can do to
make your life easier... so I guess they could be called "advanced".
You can, for example reset the configuration of the program using the dialer!
Basically, just create a dialer entry (with or without login macro) with the
number "CONNECT". If you are using a modem which echos chars back, then the
string will be received and interpreted as a carrier connect, therefore
resetting the baud/parity and all the other things the autodialer configs
when it connects. Some modems judge the baud rate by the rate of the last "AT"
command, so you might want to use "ATCONNECT" which acheives the same results.
On top of reconfiguring the program, you could put an "ATZ" command or the like
in an autologin macro...
Also to note is that you can put ANSI commands and stuff in macros. And since
macro lines do NOT append carriage returns or linefeeds to the end of macro
lines, you have a LOT of liberty as to what you want to do!
--------------------------------------------------------------------------------
.HETerm^80^Docs^^^^^^^^^^^^^^^^^^^^^^@Appendices^^^^^^^^^^^^^^^^^^^^
.BP
A. How do I order Term 80?
Well, ok, you've read the main part of the docs, and likely seen what kind
of FEATURES NOT INCLUDED in the demo version of Term 80... and being you like
the program so much, and just LOVE to support programmers... and you feel
like opening up your pocketbook, and mailing a letter to me... :-) Just
kidding!! Term 80 is not too expensive. As in the text file "Crippleware.TXT"
(hmm... nope, on the TI it's just CRIPPLE), Term 80 is $20 Canadian ($15 or
so US). Just mail a cheque or cash to me (preferred), as well as money for
shipping+disk (about $2.50 total, but it may be best to send $3 or so just in
case). Heck, why repeat the same information here as in CRIPPLE... just look
it up there! :-)
When ordering Term 80, you will be assured a full release version of Term
80's current version (whatever that is when you order it), and "free" new
copies of Term 80 future releases for the price of disk+shipping. (You will
be notified of major new releases through the mail, if possible, but all
releases (however minor) will be mentionned through comp.sys.ti (UseNet
newsgroup) and if people echo it from there, then it may even wind up at
your TI User Group!)
B. Did Jeff do his job well, or are there problems with this program?
Well, I don't actually KNOW of any bugs, but I am almost certain there are
at least a few minor ones. Term 80 runs smoothly %99.5 of the time, but every
so often it crashes for no apparent reason. I have narrowed it down to one
likely possibility, being the AMS/SuperAMS support routine. Because of the way
the AMS/SuperAMS pages in and out memory, when bytes are read and written to
the device, part of the program gets paged out of RAM temporarily. Term 80
was written without the AMS device in mind, in the goal of making it as
compatible as possible with all 32k TI systems. (actually, that's a bit of a
lie, the original required a SuperCart, but that was changed at v1.3.5! At
least 10 months ago!!!) If there's enough demand, I may modify Term 80 to take
advantage of the SuperAMS paging (the AMS cannot properly page low memory).
Oh... BTW, Term 80 v4.0 with support for all memory cards (a complete
rewrite with MANY MANY MANY enhancements) is scheduled for late Spring '96.
C. Comparative analysis of ANSI support
ANSI is the protocol used for all terminal emulation in this program being
it is the most used of all protocols and is (to my knowledge) completely
downward-compatible with VT100 (and the like) protocols.
ANSI support in Term 80 is near perfect (compared to Telco's HORRIBLE
support! I don't mean to "bash" it, but it is by far out of date!).
ANSI codes normally begin with ESC[, but some just start with ESC, and there
is also a "quick CSI" (control sequence introducer) which uses ASCII $9B (a
cent sign) which represents ESC[ (ASCII $1B, followed by a "[").
What follows is a list of all supported ANSI functions as well as a mark
which represents whether that code is supported by Telco (As listed in Telco's
documents). To my knowledge, no other TI programs (Port on the Geneve
excepted) support ANSI, however, I may be wrong!!!
Note: When I said v3.64 of ANSI, I use that lightly. It is actually a bit more
recent than that, but I could only find documentation for v3.64 of ANSI.
If I can find more recent information (such as info explaining ANSI
sound), I will implement it without hesitation!
Note: "x" is a decimal value of any length, typically optionnal (defaulted to
1, or 0 depending on the command). Most "uncertain" commands are due
to the fact that I have never seen them used. I tested them manually to
what I *think* they should do, but as I said, no guarantees! In all the
"ESC [" codes, the "ESC [" can be replaced with ASCII $9B.
Note: ALL commands which cannot be understood are IGNORED!! The only downside
to this is that if the command started with a $9B (cent sign) and it
really WASN'T a command at all, just plain text, you lose the "cent".
Sorry...
Note: As of v2.7.6, some VT52 is supported (mentionned in command list). Due
to the VT52 support I added, you may have some problems if ANSI commands
which are unsupported are interpreted at VT52. Unfortunately, there is
no real way to avoid this because the command sets are incompatible,
even if some command codes exist only in one, not in the other, but in
many cases, the command set incompatibility does not allow for proper
implementation of both sets. In designing this, I gave priority to the
ANSI command set, so it has the best support, and is guaranteed to
function.
Note: Due to the fact that I couldn't find a VT52 bulletin board (!!) I could
not test the VT52 functions. I ASSUME that they SHOULD work since all
but the "ESC Y" branch off to the ANSI routines. I do not even have
proper documentation for them either... <sigh>
Code | Description | Telco
----------+-------------------------------------------------------+-------
ESC A | Cursor Up (VT52) | Yes (VT52)
ESC B | Cursor Down (VT52) | Yes (VT52)
ESC C | Cursor Right (VT52) | Yes (VT52)
ESC D | Cursor Left (VT52) | Yes (VT52)
ESC E | Next Line (bug here... does not scroll, RARELY used) | No
ESC H | Horizontal Tab Set (or Home if VT52 only) | No/Yes
ESC I | Horizontal Tab Set w/Justification | No
ESC J | Erase from cursor to end of screen (VT52) | Yes (VT52)
ESC K | Erase from cursor to end of line (VT52) | Yes (VT52)
ESC Y yx | Move cursor... x/y is char offset from SPACE | Yes (VT52)
ESC [x@ | Insert 'x' characters | No
ESC [xA | Cursor Up | Yes
ESC [xB | Cursor Down | Yes
ESC [xC | Cursor Right | Yes
ESC [xD | Cursor Left | Yes
ESC [xE | Down Line (little bug here... see appendix for bugs) | No
ESC [xF | Up Line (same kind of bug as Down Line) | No
ESC [xG | Move Cursor to an absolute horz. position | No
ESC [x;xH | Move Cursor to an absolute position (Home if no pos.) | Yes
ESC [xI | Tab 'x' tab positions (horizontal) | No
ESC [xJ | Erase in Display (1) | Some (1)
ESC [xK | Erase in Line (1) | Some (1)
ESC [xL | Insert 'x' lines | No
ESC [xM | Delete 'x' lines | No
ESC [xP | Delete 'x' characters | No
ESC [xX | Erase 'x' chars without shrinking line (unsure...) | No
ESC [xZ | Go back 'x' Tabs | No
ESC [x' | Horizontal position absolute | No
ESC [xd | Vertical position absolute | No
ESC [x;xf | Move cursor to abs. position (Home if no position) | No
ESC [xg | Tab clear (resets to default) | No
ESC [xh | Select mode (VT100 modes) Some (2) | No
ESC [xl | Reset Mode (VT100 modes) Some (2) | No
ESC [xm | Set text attributes (3) | No
ESC [xn | Device Status Report... Some (4) | Some (4)
ESC [s | Save current cursor position | Yes
ESC [u | Set current cursor position back to saved one | Yes
Notes:
1. Telco supports only "Clear Display" and "Clear Line". The parameter selects
what to do...
in ESC[xJ:
0 - Clear to End Of Line
1 - Clear from Start of Line to Current Position
2 - Clear Entire Line (Telco only supports this one)
in ESC[xK:
0 - Clear to End Of Screen
1 - Clear from Start of Screen to Current Position
2 - Clear Entire Screen (Telco only supports this one)
2. Select mode, only mode 4 (if set, the Insert, otherwise, OverWrite) is
supported.
3. The text attributes control bold/blink/underline etc... and colours:
00 - Reset attributes
01 - Select Bold
02 - Italics (ignored)
04 - Select UnderLine
05 - Select Blink
07 - Select ReverseText
21 - Deselect Bold
22 - Deselect Italics (ignored)
24 - Deselect UnderLine
25 - Deselect Blink
27 - Deselect ReserseText
30-37 - Select Foreground Colour
40-47 - Select Background Colour
Colours:
0 - Black 1 - Red 2 - Green 3 - Yellow
4 - Blue 5 - Purple 6 - Cyan 7 - White
4. Device Status Report
Both Telco and Term 80 only support one mode of this command. Mode 6 of
this command prompts both programs to send an ESC[x;xR command with the
current cursor position. Some bulletin boards use this to see if your
terminal program supports ANSI/VT100.
D. You wanted of list of keyboard functions?
Term 80 is highly keyboard-operated, so a list of the keyboard functions
would be useful, wouldn't it? In a future release, I may create a "Main Menu"
to help you guys out, but until then, learn the ones you'll use the most!!!
:-) (just look up the help menu if you forget! yes, the key is FCTN-7...)
Cursor and editing:
Fctn-1: DELete Fctn-9: BACKspace
Fctn-E: Cursor Up Fctn-S: BACKspace (Cursor LEFT if ANSI)
Fctn-D: Cursor Right Fctn-X: Cursor Down
Ctrl-G: Bell (ASCII 7) Ctrl-H: BACKspace
Ctrl-J: LineFeed Ctrl-L: FormFeed (clearscreen)
Ctrl-M: CarriageReturn
Other keys you should remember:
Ctrl-[ or Ctrl-.: Escape
Ctrl-]: NoName but sometimes asked for
Terminal codes: (locally used... NOT transmitted!!!!)
Ctrl-1: Reset to B/W Ctrl-2: Inc. & reset FG colour
Ctrl-3: Inc. & reset BG colour Ctrl-4: Inc. & reset BD colour
Ctrl-5: Toggle arrow key config Ctrl-6: Toggle ANSI Colour mode
Ctrl-7: Toggle ANSI Parser mode Ctrl-8: Toggle printer dump on/off
Ctrl-9: Clear RS232 buffer Ctrl-0: Clear screen
Fctn-0: Toggle duplex FctSft-0: Redetermine clock (See glossary)
Calls to system utils:
Fctn-2: Call Autodialer Fctn-4: ANSI Status Menu
Fctn-5: RS232 Status Menu Fctn-6: Download Binary files
Fctn-7: Call Help Menu Fctn-8: Call Macro Send
FctSft-6: Upload Binary files FctSft-8: Call External Loader
FctSft-9: Call Screen Saver FcCtSf-6: Transfer Ascii files
Other things:
FcCtSf-=: Quit!! Multi-Lingual: See main program key explan.
E. TroubleShooting!
Well, if any problems occur, you can always call me, but if I start getting
dozens of annoying calls from people who didn't read the documents, I may
set up a voice-mail message so I can be left in peace! :-) Just read these
things, and if that doesn't help... leave Email, if you can't, call me, but
PLEASE! check the time zone map in your phone book!! I am in Ottawa, Ontario,
and if I get calls at 3am, I will not definitely get annoyed.
Well, with that said, let us move on. <sly grin>
1. Loading errors
"The darned thing just won't load!" Yes, did you set the pathname right? Did
you READ the setup information? Try removing device drivers (see next
chapter) and carefully read any messages you may see (if the main program
loads). If it all fails (if you can't even read the disk!) CALL ME!
There are various error codes provided on bootup... such things as:
"I/O Error..."
Well... something happened, it couldn't read/write a file!
"Error - Cannot install device!"
Well... something wrong loading the device driver, or internal to the
device. This is NOT caused by not having that kind of device on your
system. It can occur if it runs out of RAM to stick the drivers in
though.
"Error - Driver list corrupt!"
The device driver list is unreadable or something!
"Error - Device list read error!"
Did you pull out the disk in the middle of the read? Anyhow, can't read
the driver list!!!
"Error - Cannot find driver file!"
Could not find the device drive on the disk!!!
"Error - Memory FULL!"
Just what it says... not more RAM left for drivers. BTW, the drivers
share a small 2k block of RAM with the RS232 input buffer...
"Warning - Memory list full!"
Too many device & memory block entries in the memory list!!!
"Warning - Too much memory!"
Term 80 is unable to allocate all the RAM you gave it... so it truncated
the blocks. This will only ever happen if you go nuts on RAM!
"Fatal Error - Hit Fctn-="
Ok, some errors are fatal, and if they are, you see this... hit Fctn-=
to reboot.
2. Crashing in mid-program
"It crashed and killed my conversation on me!!" Hmm... dunno what to say
here. You might try removing device drives (ESPECIALLY the AMS driver, which
becuase of the constant paging is somewhat unreliable, one missed repage and
the system will crash almost for sure!). IF the program reboots, then maybe
there was a power-surge! Who knows? If you've owned a TI for a number of
years, then you should be able to recognize the problem and fix it (let's
hope!). Make sure you have a backup copy before you attempt anything.
3. Other troubles
"It didn't save!", "It crashed for no reason!", Help!!!! Use your judgement,
The main problem that can occur is if the program is unable to load/save a
file. The TI's filesystem is very vulnerable so weird things DO happen. My
suggestion, reboot, and retry... or just GUESS!
There are only a few known bugs... they lie in the ANSI parser. In the
Index, Reverse Index, Up Line, Down Line routines, it does NOT scroll as it
should according to ANSIx3.64. I could fix this, but it is so rarely
encountered that I won't bother. To note: v4.0 will have this 100% ok.
Those are the ONLY known bugs!
F. Ok, what are all these "D_" and "R_"s?
Well, the filenames are all under a code... or a pattern... whatever! Here
it is. File beginning with... are:
"C_": Configuration programs
"D_": Device Drivers, and list
"L_": Login Macros
"M_": Normal Macros
"R_": Term 80 modules
Here is a description of the main files:
"LOAD": A loader (by default from DSK1., can be overridden by keypress)
"MD": It's a loader so I can load Term 80 by holding "M" on bootup on my
Horizon 248k Rdisk w/EPROM.
"RS232"-"RS233": Term 80 main loader/image/path config
"RS234"-"RS237": Term 80 main program
"D_DEVLST": Device list, list of devices to be used by Term 80. Lines starting
with ";" are comments. Just stick here the device name (without
the "D_"). I provided a bunch of lines to help describe things,
so just comment out the devices you don't have (or uncomment those
which you do!). It trys to identify if you have those devices and
adds them to the deivce list on bootup if you do.
Note: DO NOT! use the SuperCart & Minimem atthe same time!!!
Note: Use the AMS driver closest to, but not larger than the size
of the AMS you have. Only ONE must be used!!!
Note: Macros, the device list, and files produced by ASCII downloads are in
DV80 (text) format.
Little bit of history behind the program executable filename... I used to call
it RS232 since it was just a silly little test program... I never bothered to
change filenames! Maybe at v4.0?
G. Need a dictionary?
For those who can't understand the terms in Term 80, well... I wanted to
provide a glossary. It's late, and I'm tired, so why not look in a good
dictionary, or ask a friend. (I've tried to explain everything along the way
anyhow... :-) Still in need of help? Contact me...
H. The FUTURE!!!!
If you have a time machine, and travelled ohh... to late Spring '95, you
would probably be able to catch me finishing off the first demo edition of
Term 80 v4.0. V4.0 is MORE than a terminal program, it will be an entire OS
+ have TONS of applications. I am planning a TRUE GUI interface, FULL support
for expanded memory cards, mice, etc... IT will have picture viewers/converts
a text editor, file utils, and PROGRAMMER SUPPORT. Yes, I will release tools
for designing your own Term 80 modules to make use of it's functions +
libraries, and devices. Term 80 v4.0 *should* have support for expanded video
cards/devices (TMS9938) and the ability to run off of the Geneve.
Anyhow, I just want to finish this all off... so no more dreaming for now.
Let me just say this, if Term 80 v4.0 is as successful as I hope it will be,
the TI community will DROOL over it!
VIII. Ending notes ................................................ 23
--------------------------------------------------------------------------------
.HETerm^80^Docs^^^^^^^^^^^^^^^^^^^^^@Ending notes^^^^^^^^^^^^^^^^^^^^
.BP
Phew!! I'm FINALLY here!!!! Well... I must say I am GLAD to finish off t
(truncated to 60Kb)

 

Term80Docs.txt

term80.zip

Edited by Opry99er
  • Like 1
Link to comment
Share on other sites

I bought this modem... Looks like an EXCELLENT choice. In speaking with arcadeshopper, it appears that this one is handshake-ready with the TI... straight-thru cable will have the TI talking to this modem brilliantly. (At least that's the plan) ;)

 

 

I have attached the manual for this modem here so you can see the pinouts and determine if it is something for you!

 

002806-00.jpg

USRManual.pdf

  • Like 2
Link to comment
Share on other sites

There are some very inexpensive straight thru cables on Amazon. Here is one:

 

https://www.amazon.com/SF-Cable-DB25-Straight-Molded/dp/B006WB3Q70/ref=sr_1_8?ie=UTF8&qid=1490070513&sr=8-8&keywords=db25+serial+straight+thru

 

 

$2.95 a piece for a 3 foot cable.

 

 

41uyC9waxFL._SX425_.jpg

 

 

 

A short cable from the rs232 to the modem is all you need to dial out. I have purchased a splitter box (Belkin Data Switch) so that I can remain hooked up to both my modem and my PC, and switch between them with the flick of a knob.

 

20170319_193203_zps2wuaegxj.jpg

 

20170319_193214_zpsq5t9wldj.jpg

  • Like 1
Link to comment
Share on other sites

Not directly BBS related, but this is my favorite file transfer program for the TI. This is a serial interfacing thread, too... so. It counts. :)

 

MagicFileManipulator, or MFM for short.

 

 

Excellent program. Ernie Pergrem sent me my first copy many years ago in the mail so that I could start transferring files. I did ALL the Opry99er serial transfer videos using this program.

MFM.zip

  • Like 1
Link to comment
Share on other sites

Alright, I have connected my system... I now have the US Robotics modem hooked up to my A/B box, as well as the serial cable out to my PC for transfers. I have all the cables hooked up, ready to go for BBSing via dialup.

 

 

20170324_035102_zpsidbn8ydh.jpg

 

 

The ad for the modem said "Adapter Included"..... apparently we had differing opinions of what 'adapter' meant.

 

 

 

20170324_035052_zpsus4qbfqg.jpg

 

 

 

So... it had an ETHERNET adapter, but no power adapter.... UGH!

 

Luckily I found a Universal Adapter at WalMart and picked it up... It cost more than the modem plus shipping. :D

 

 

 

548beae7-a6fd-446b-aaed-adea280f1280_1.7

 

 

 

 

The phone company jerked me around this week and I still do not have a phone jack installed in my basement next to my system where I need it. Fortunately, I have a 100ft phone cord upstairs... I don't think it will reach going down the two flights of stairs (plus it is hazardous) but I might be able to slip the cord out the window, down to the main level of the house, through the deck boards, and into the window of my basement, with just enough cord left to plug into my modem....

 

It's a long shot, but I am really eager to get up and running.

 

I had planned on trying to run the phone cord down tonight, but I spent the time after work getting all the gear set up just the way I wanted it, clearing up my desk a bit, vacuuming the floors, dusting, etc... Now I can look at this set up and be proud of it. :)

 

 

 

20170325_030425-01_zpsjq52ux7z.jpeg

 

 

 

20170325_030628-01_zpsdew53qtj.jpeg

 

 

 

 

Tomorrow, I will try to string the phone cord through the deck boards and dial in to the Hidden Reef. :)

 

 

This hobby is insane........

  • Like 1
Link to comment
Share on other sites

 

 

The ad for the modem said "Adapter Included"..... apparently we had differing opinions of what 'adapter' meant.

 

 

 

20170324_035052_zpsus4qbfqg.jpg

 

 

 

So... it had an ETHERNET adapter, but no power adapter.... UGH!

 

 

 

This is not an ethernet adapter, it's a rs232 adapter to use an ethernet or other rj45 cable as the cable.. I used these on my BBS when I had 12 lines so that I could do wire management easier. Also good for making interchangeable adapters.

 

like dis one https://smile.amazon.com/StarTech-com-Serial-adapter-DB-9-RJ-45/dp/B00006IRQA/ref=sr_1_10?ie=UTF8&qid=1490463526&sr=8-10&keywords=rs232+to+rj45

Link to comment
Share on other sites

So the straight through cable did not work... The docs on the modem were a bit confusing, so it was all wonky.

 

I had a straight through cable that I cut in half and used a meter to identify the necessary cables.

 

20170326_145739_zpsrt6k0prv.jpg

 

 

I didn't have any electrical tape, so it was suggested that I just do the ol' twisty McScotch tape dealy-o. Which I did.

 

:D

 

And I plugged it all up... and got an immediate response from the modem!!!

 

Yay!!!

 

I'll be attempting my first dial out later today.

 

 

The cable setup:

 

1 -- 1

2 -- 3

3 -- 2

6 -- 20

7 -- 7

20 -- 6

  • Like 1
Link to comment
Share on other sites

Note: I did have to reset the modem to factory presets because it was not allowing my TI screen to see the data.

 

Greg McGill diagnosed that one pretty quickly. :)

 

BTW, I realized how badly I need 80 columns when I dialed in to thekeep.net. :) The awesome 80 col graphics don't look all that hot in 40 columns. :D

Link to comment
Share on other sites

Note: I did have to reset the modem to factory presets because it was not allowing my TI screen to see the data.

 

Greg McGill diagnosed that one pretty quickly. :)

 

BTW, I realized how badly I need 80 columns when I dialed in to thekeep.net. :) The awesome 80 col graphics don't look all that hot in 40 columns. :D

 

Sounds like it's time for an F18A!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...