home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
GEMini Atari
/
GEMini_Atari_CD-ROM_Walnut_Creek_December_1993.iso
/
files
/
telecomm
/
fzt_d220
/
fzdsterm.doc
< prev
next >
Wrap
Text File
|
1992-07-07
|
86KB
|
1,809 lines
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
FreeZe Dried Software Presents:
________ _____ ____
/ / | \
/___ ____ ____ ____ / ____ | \ ____ ___ ____ ___
/ / //__ /__ / /__ | > | ' | |__ | \
/ / / / / / | / | | | | >
/ / /___ /___ /____ /___ |___/ | _|_ |___ |__/
/
_____________ /oftware
' | ____'____ _ _ ___ _ _ _ _
| | | ' |\ /| | |\ | / \ |
| |-- | | \/ | | | \ | /---\ |
| |___ | | | _|_ | \| / \ |____
v2.20
Programs and All Documentation Copyright ©1991-1992 Aaron Hopkins
This program is Shareware. The Demo may be distributed freely.
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
DISCLAIMER: This is a very powerful and complex program, and being such,
there is a greater potential for misuse. The developer has made every
possible effort to ensure that the included software is error-free, but it is
given out solely on an "as is" basis. No warranties, either express or
implied, are made by the developer with the respect to the software or its
fitness for a particular purpose. The developer accepts no responsibility
for any loss that may result from the use or inability to use this software.
The entire risk as to the quality and performance is with the user of this
software.
YOU USE THIS PROGRAM AT YOUR OWN RISK!
TABLE OF CONTENTS:
----- -- --------
I. Introduction ............................................... [INT]
A. List of Features ........................................ [FEA]
B. About FreeZe Dried Software ............................. [FZD]
C. What exactly is Shareware? Why should I register? ...... [SHR]
D. Why don't we use GEM? ................................... [GEM]
E. Why you need a good term program ........................ [TRM]
II. A. Basic Setup ............................................. [SET]
B. General Use ............................................. [USE]
C. The Terminal Mode ....................................... [TTM]
III. Autodialer .................................................
A. Introduction ............................................ [DLI]
B. Dialing ................................................. [DIL]
C. Auto-Logs/Auto-Macros ................................... [ALM]
IV. File Transfers .............................................
A. Introduction ............................................ [XFR]
B. Using your protocols .................................... [XFU]
C. Installing new protocols ................................ [XFI]
D. Batch Queue List editor ................................. [BQL]
V. Macros .....................................................
A. Introduction ............................................ [MAC]
B. Editing your macros ..................................... [MCE]
C. Explaination of macro functions ......................... [MCF]
VI. Disk commands .............................................. [DSK]
A. General use ............................................. [DKU]
B. Using the LZH/ARC/ZIP archiver shell .................... [ARC]
C. Setting up the archiver shell ........................... [ARS]
VII. RS-232 Configuration ....................................... [RS2]
VIII. System Setup menu .......................................... [SYS]
A. Changing your colors .................................... [COL]
B. System parameters ....................................... [PAR]
C. Terminal Event Chimes ................................... [CHM]
D. The daily .LOG .......................................... [LOG]
E. AES Background Events ................................... [AES]
F. BBS Timeout Logoff Pause ................................ [LOF]
IIX. Font Installation .......................................... [FNT]
IX. The Capture Buffer ......................................... [CAP]
A. The Scrollback .......................................... [SCL]
B. Capture Buffer Configuration ............................ [CPC]
X. The Text Editor ............................................ [TED]
XI. Script Files (".DO") ....................................... [.DO]
XII. A. How to Reach the Author ................................. [RCH]
B. Reporting Bugs .......................................... [BUG]
C. Future Features ......................................... [FUT]
XIII. Troubleshooting ............................................ [TBL]
A. General ................................................. [TBG]
B. Transfers ............................................... [TBT]
C. Autodialer .............................................. [TBA]
XIV. Final Acknowledgements ..................................... [FIN]
NOTE: To use the table of contents, you may look at the index characters and
use them in a text editor or file viewer capable of searching. You
would enter the index characters as the search pattern to quickly take
you to a portion of the documentation. For instance, you would search
for "[XFR]" to read an introduction to File Transfers.
I. Introduction - [INT]
============
FreeZe Dried Terminal was written by a BBS (Bulletin Board System)
addict. It was written because the "best" of all available Terminal Programs
just wasn't good enough for my use. The original purpose was to write a more
usable terminal program just for my personal use, but as it grew and
developed, I gave it to a few friends and they enjoyed it so much that my
goal became developing it enough to the point of perfection, at which time I
would release it. But as I worked on it, I discovered that it never could be
quite perfect, and at some point I would have to stop and say "This is it,
I'm going to release this if it kills me." You see, I am a bit of a
perfectionist. FZT can never be perfect, and never will. There will always
be things to change, new features to add. I started FzDSTerm in mid-August,
1990 and it has taken me almost two years to get this far. I hope you enjoy
using it as much as I and my Beta-testers do.
I. A. Here are a few features that FzDSTerm has to offer: - [FEA]
==================================================
o Colorful, Intuitive non-GEM user interface with full mouse control and
keyboard commands for most selections.
o True 19200 baud input handling. Use your high-speed modem as it was meant
to be used.
o VT-52, ANSI, UBT-Graphics, Instant Graphics, and more.
o Any external protocol can be installed under easy-to-use shell:
Currently installed protocols include Z-Modem Batch, Y-Modem Batch,
Y-Modem G Batch, F-Modem Batch, X-Modem 1k, X-Modem CRC, X-Modem Checksum.
o Any protocol with a unique start sequence may be set up to Auto-Start
receiving or sending. (Z-Modem send and receive are currently set up to
do so.)
o Full Featured Auto-Dialer With 45 slots, redial, chain dialing, and
background dialing.
o Auto-Logon Sequences for each BBS to get you on with few keystrokes.
o Auto-Learn Logon feature to create Auto-logs automatically.
o Auto-Macros for each BBS to perform repetitive tasks for you.
o 40 Macros with the ability to perform any script command or keyboard
command, chaining macros, and much more.
o 5 extra Macros for each BBS to hold your personal information, such as
Handle, Password, etc.o Full Featured Capture Buffer (maximum of 32000
lines), including block commands to save, ASCII send, etc. a block of
text.
o Full Featured Text Editor including word wrap, block commands, reformat,
search & replace, and more.
o Flash!(tm) Compatible .DO Script Files.
o Full Featured Disk Commands, including Format Floppy and an LZH/ARC/ZIP
archiver shell.
o 1000 Character Type Ahead Buffer with 10 memories.
o Several built-in fonts and the ability to load standard .FED 8x8 or 8x16
Font Files.
o Cheap Registration Price ($25)
o Fully usable Demo, with only non-essential commands disabled and no time
limit.
o Complete In-Depth Documentation.
REQUIREMENTS:
- At least one Megabyte of RAM.
- ST Medium (color), ST High resolution (monochrome), or TT Medium (color)
are recommended, but any resolution 640x200 or above should work.
(FZT was developed on a color monitor; using it in color is preferable.)
- Modem (preferably using the Hayes "AT" command set). It must be able to
set Carrier Detect properly.
- Serial RTS/CTS Patch if using a high-speed (above 2400 baud) modem and an
version of TOS not supporting RTS/CTS flow control.
I. B. About FzDS Software - [FZD]
===================
Let me start out with the correct way to pronounce FzDS, the acronym for
FreeZe Dried Software. Whenever saying the name it is pronouced FizzDizz and
FizzDizz Software. The software group is dedicated to bringing you the
finest available programs with a reasonable price. It was started by the
authors of UBBS, Brian Hauer and Sean Price. It was originally FDS Software,
but when we were told that FDS is a brand of feminine hygiene products we
promptly changed the name.
We at FzDS as a whole have produced quite a few small utilites, and
several larger applications, mostly BBS and modem related. If you enjoy
using this software, you might check out other FzDS products! If you are
interested, ask me about them.
I. C. What is Shareware? Why Should I Register? - [SHR]
================= =====================
The principle of Shareware is simple. The program is distributed by the
Public Domain libraries, by uploading onto BBSes, and giving copies away.
Users can get a copy of the program just for the price of the media, and then
take it home and use it. If the user likes the program, he sends the author
a Shareware fee. Usually, the author will send back a few goodies (as an
incentive to register) or if the program was Crippleware (Shareware with a
few functions disabled.) they get a fully-working version of the program. If
enough people send in the cash to make it worthwhile, he may do more
Shareware stuff.
Naturally you don't have to pay anything if you don't like the program.
Of course a lot of people might like the program and decide not to pay, but
if too many people do that then nobody will ever bother writing any decent
Shareware at all, and it's back to buying stuff off the shelf. So, it's down
to the users - if they're honest, then programmers will be more inclined to
work hard on Shareware releases. The idea of Shareware is very idealistic,
perhaps impracticably so, but the advantages over the conventional market are
so enormous that it seems to be worth the effort to try it.
Advantages of Shareware:
=======================
1 - It is a totally honest way of selling. Everybody gets to try the program
out, and only those who use it are morally obliged to pay the fee. Nobody is
disappointed or feels ripped-off.
2 - There are no constraints on creativity. No-one says 'we cannot publish
this because it ain't mainstream'. Programmers do what the hell they like
and the users vote with their Shareware fees.
3 - Anyone can use it. The mechanism of distribution is already in place in
the form of Public Domain libraries. All the originator has to provide is a
disk to each of the PD libraries with program and documentation. If it's
good, it'll get passed around the PD scene; if it's bad nobody will bother
with it. Forget spending thousands on advertisements trying to convince
people to spend lots of money on something they haven't even used yet...
4 - The concept of piracy becomes null. All that business of hacking and
cracking doesn't apply to software which is both unprotected and easily
copied. Shareware authors WANT their software to be spread and copied. If it
gets onto a BBS in England and spreads all over the UK, well and groovy! Good
Shareware exports itself!
5 - Prices can be very low. Since the authors have no overheads in terms of
production and advertising, they don't need to ask as much in payment. And
the users pay the programmers directly - nobody else takes a cut. 100% of
twenty dollars is better than 5% of fifty dollars.
The advantages of Shareware as a democratic, honest way of publishing
software are pretty obvious, but it does have to go both ways. If a
programmer puts a lot of time and effort into his code and releases it as
Shareware, he's trusting you, the users, to be honest and pay him if you like
his program. If you all just take the stuff for free, he won't bother to do
anymore Shareware stuff. If you support the author, he'll be inclined to do
much better next time - and you'll be the ones to benefit.
NOTE: By sending money to the author of this program, you are paying for the
use of FzDSTerm and associated utilities for FzDSTerm (such as CONV2FZT and
FZDSXFER) which have been written for FzDSTerm. Software not written by
FreeZe Dried Software that is included in the archive must be registered
seperately. XYZ transfer protocols are Copyright Alan Hamilton of Starfall
and the registration for XYZ is not included in the shareware fee for
FzDSTerm.
I. D. Why don't we use GEM? - [GEM]
====================
Atari ST GEM was created in 1985 when the Atari ST first came out. The
first Atari 520 ST had limited memory so TOS was written around that fact.
Now with Atari STs capable of having 4 megs of RAM, FzDS has rewritten the
user interface routines around this fact. Our buttons are faster, colorful
and do not need a resource file.
GEM uses basically two colors. Menus and other dialog boxes may have
some background colors, but the original 520 ST was mainly sold with the
monochrome monitor, so the buttons are limited to black and white. The new
FzDS routines allow any color within the 4 color palette in alert boxes,
dialog boxes and menus.
By using built in Line-A assembly calls to draw all graphics,
FzDS buttons' speed equals and usually exceeds the speed of GEM calls.
There are some disadvantages to using this method though. Resolution
independant graphics are lost by not using the VDI. This means that new
graphics boards, the Moniterm Viking, and TT High resolutions are not
currently compatible with FzDSTerm. Stay tuned for a future version of FZT
utilizing a new user interface using pure VDI. So far it looks VERY good,
and has little or no loss of speed, and is resolution independant! It will
probably reduce program size along with the amount of RAM that FZT takes to
run.
I. E. Why Do I Need a Good Terminal Program? - [TRM]
=====================================
Modems (short for MOdulator/DEModulator) are devices which allow one
computer to communicate with another through standard telephone lines. To
use a modem, you will need a few things. First, you need something capable
of connecting to the modem to allow the user to interact with whats going on
with the modem. Also, you need a modem and appropriate connectors (RS-232
cable, etc.) Lastly, and the most importantly, is the software to allow the
modem to communicate with the computer and the user. This is referred to as
a Terminal program. You can have the most expensive computer and the fastest
modem, but if you don't have a good terminal program you are nowhere.
Many people have had a terminal program that they've been using for a
long time, and that they're happy with. They're happy, thats all that
matters. I was happy with my 8-bit for a long time, I was sure that it could
handle all that I needed to do. But then I saw an ST over at a friends
house, and it could do all that I NEEDed to do, plus much more. It was
faster with a better user interface, and had the extras that made computing
easier and more interesting. This same idea applies to Term programs,
something else may work for your NEEDs, but does it do all that you WANT?
There have of course are a lot of other programs out there and many have
things about them that nothing else can touch. But most, if not all, trade
one feature for another. If you want true 19200 baud communications, you
might have had to sacrifice something else. If you wanted IGS graphics, you
would have had to put up with a completely featureless terminal. If you
wanted a feature packed program, you would have had to sacrifice ease of use
or speed. Its a trade-off. But FzDSTerm has everything I or any of my beta
testers have ever needed, wanted, or thought of, all in a very fast, easy to
setup and use package.
II. A. Basic Setup - [SET]
===========
If you wish to just preview FzDSTerm you will not need to do any of
the following except run it. Most of this program should set itself up.
Your archive (or disk) should contain:
FZDSTERM.PRG The FzDSTerm Main Program (Demo versions are named
"FZT_Dxxx.PRG", where xxx is the version without the
decimal point.)
FZDSTERM.DOC This documentation
REGISTER.DOC Registration information
PRINT.ME Registration Form
READ.ME Changes in FzDSTerm and useful information
RECOMEND.DOC Recommended PD/Shareware utilities for use with FZT
CONV2FZT.PRG Converter for Interlink, Flash, Stealth, Qterm,
Dterm, and Vanterm autodialer and macro files to FZT
format
CONV2FZT.DOC Docs for Converter
FZDSXFER.TTP Beta Test Version of the FreeZe Dried Protocols
FZDSXFER.DOC Documentation for the FzDS Transfer Protocols
XYZ201.TTP X-Modem, Y-Modem and Z-Modem protocals v2.01
XYZ201.DOC Documentation file to go with XYZ201.TTP
NOTE: Other, unlisted programs or documentation may be included for your
convenience.
It will also (eventually) create the following files, which will be
loaded at the startup of each session with FZT:
FZDSTERM.CFG The configuration file
FZDSTERM.NUM The default autodialer directory
FZDSTERM.MAC The default macro set
Follow these steps to quickly configure FzDSTerm to your system. It comes
with most options set to a preset configuration.
1. If you do not have a Hard Drive, you may wish to use a RAM Disk as a fast
drive which FzDSTerm will use to keep the protocols and other temporary
files for increased productivity. If you want to use this feature,
install a RAM Disk now. (HRAMDISK.PRG is recommended for this.)
2. Run FZDSTERM.PRG
3. It will pop up a fileselector asking you to locate the config file.
Since you currently don't have one, click on Cancel.
4. An alert box will appear telling you that it couldn't find the config
file and that it will be using defaults. Hit return.
5. Another alert box will ask you what type of modem to set up for. If you
have a 300, 1200, or 2400 baud modem click on "Generic 2400". If you have
a USR HST or similar high-speed modem click on "USRobotics HST".
6. A Quick Setup menu will appear next. This is where you can set all of
your defaults before you begin using FzT:
7. It will default to 2400 baud, 8 bits, No Parity, 1 stop bit, No CTS/RTS,
No XON/XOFF, Full Duplex, No Echo, No Linefeeds, Capture Open, VT-52
Emulation. If you need to change any of these, click on RS-232 config
and do so. Click on EXIT when you are done.
8. a) Click on Default Paths. You may specify specific paths for most
different types of files. Click on a path to change it. I prefer to
make seperate paths for everything, I like to be organized, but you may
leave them all to the default.
b) If you are without a Hard Drive and have decided to use a RAM Disk as
a fast drive, you will need to install it. Click on "Ramdisk" and when
the fileselector appears, move to the path for the RAM Disk in the
fileselector, and click on "OK".
c) Hit UNDO or the right mouse button when you are done.
9. a) Click on Initialization strings.
b) If you are in the US or Canada, and your phone number is in the format
of (xxx) yyy-zzzz, where (xxx) is your Area Code, you may wish to use the
locked format dialing system in FzT. This is best for people who don't
dial internationally, and don't need to change modem settings for
different BBSes. FzT will default to locked format, if you don't feel
this is suited for your needs, click on "Free Format Phone", and hit
Return twice to skip through the conversion dialogs.
c) Next, use the arrow keys to move to the Current Area Code. Backspace
over 310. If you are in the US or Canada, enter your current area code.
If you are not, LEAVE THIS BLANK! THIS IS IMPORTANT.
d) If you want to change any of the preset Init strings, do so. When you
are done, click on EXIT.
10. Click on Save Config to write your configuration to the current path, and
then EXIT to go on.
11. You will be presented with the Main Menu. Enjoy!
II. B. General Use - [USE]
===========
Once you get the hang of how FzDSTerm's functions are layed out, it gets
to be very easy to use. Here are a few things to keep in mind while you are
using FzDSTerm:
o A function is on when it's button is selected (right and bottom sides of
the button filled in.)
o UNDO and the right mouse button exit from every menu.
o There are usually keys in every menu that select all or at least the most
commonly used functions. I stuck mostly to cursor keys, SPACE, RETURN, and
the Function and Arrow keys for this. Its sometimes a lot quicker to hit a
key than move the mouse and click, and its nice to get away from using the
mouse every once in a while. Press HELP in a particular menu to find these.
NOTE: Help screens will be improved in future versions.
o In Alert Boxes, RETURN and the right mouse button click on the default
(highlighted) button. You may also press 1, 2, or 3 to select buttons, in
order from left to right.
o In an editor such as the macro editor: BACKSPACE will delete the character
in front of the cursor, DELETE will clear the line, CLR HOME will jump to the
front or back of the line, INSERT will toggle between pages or sides, and the
cursor keys will move around.
II. C. The Terminal Mode - [TTM]
=================
The most important feature of ANY terminal program is the terminal mode
or online screen, where the input from the modem is processed and the main
user interaction takes place. When you are here, you are "online" or in
some form communicating with the modem or BBS. Whatever other features a
terminal may offer, if this area is not top-notch, you can dump the terminal
program.
FzDSTerm possesses the unique ability to process input much faster than
many other terminal programs, while still adding many more features.
Autologs, Automacros, Script commands, echo, linefeeds, destructive
backspacing, emulations, etc are all processed in the terminal mode
simultaneously.
A list of available keyboard commands is available by pressing Help.
These will allow you to hang-up by pressing Alternate-H, for example, or
change the current emulation by Alt-E.
FzDSTerm can process several different types of "emulations", which are
statements by a remote system telling your system to display something
graphically, whether changing colors or repositioning the cursor. Vt-52 is
the ST standard and allows limited text graphics. ANSI is for use with
MS-DOS BBSes, and also includes a different character set which allow
somewhat better graphics capabilities than Vt-52. IGS is like these yet much
different. Vt-52 and ANSI use text graphics (80x25), where as IGS allows
true bitmapped graphics (640x200) along with many extended commands.
UBBS-Term graphics are much like IGS, but have a much more rigid structure
and are more compact, allowing UBT to be sent over the modem faster. UBT
also includes quite a few unusual instructions which IGS lacks. It's
basically FreeZe Dried Software's expanded, improved version of IGS.
Unfortunately at the moment of this writing, UBT is only available on UBBS
BBSes.
FzDSTerm's terminal mode contains at the bottom of the screen, a status
bar (usually), along with various other gadgets which may improve your modem
life. The first is a "Type Ahead Buffer", which allows you to type up to
1000 characters, look them over, check them for correctness, and move to
correct any errors, all before anything is ever sent to the modem. When you
finish with your sentence or command and see that it is satisfactory, you may
hit return to send it the modem. Previous lines are available by using upand
down arrow, and you may edit a line by using left and right arrow. This is
especially useful for "chat" boards, where multiple users are communicating
at once and any typing pauses the conversation for you until you hit return.
Also available at the bottom of the screen is the text editor, invoked
by pressing Insert. This will allow you to view and edit your text files
while still participating in a conversation on a chat board, for example.
You may toggle where your keystrokes are sent by hitting Insert again. They
will either be sent to the modem or processed by the text editor. I also
find that this feature replaced all the little yellow slips of paper around
my desk by acting as a notepad. This may be removed by pressing Undo.
Depending on which features of FzT you have active, more status lines
may appear at the bottom of the screen. Script files, and some commands in
UBT may create extra status lines. (A semi-outdated, yet helpful list of
UBBS-Term commands may be obtained from the author. Source code for
processing UBT may be made available upon request, to help spread usage of
UBT.)
III. A. The Autodialer - An Introduction - [DLI]
============== -- ------------
The purpose of an autodialer is to simplify the process of dialing and
logging on to your most commonly called BBSes. FzDSTerm's Autodialer may be
reached by the right mouse button or F2 from the Online screen, or from the
main menu. There are 45 slots to fill in info about different BBSes. This
info includes the name of the BBS, the telephone number, 2 lines of comments,
the baud rate and serial port settings, the emulation to use, the autologon
sequence, the script file to execute upon connection, 5 individual macros,
and the whether or not the autologs or automacros are on. You may leave any
or all of this blank except for the phone number.
To select a particular slot, you may use the either click on the slot, or
use the UP, DOWN, RIGHT, and LEFT arrow keys. (If the EDIT button is on,
you will have to hold down CONTROL while pressing the keys.)
To edit the Name, Numberm and comments of a slot, you may use the UP, DOWN,
RIGHT, and LEFT arrow keys, if the EDIT button is on. (If its off, either
toggle it on, or hold down CONTROL.) Also, RETURN will go to the next line.
To edit the baud or serial port settings, .DO script file to execute, the
emulation to use, or the status of the autologs and automacros, click on the
appropriate buttons.
To edit the BBS specific macros, autologon sequence, or automacros, click on
"Autolog/Automacro Editor".
Insert will toggle the group dialing status of the current slot. Clr/Home
will clear all slots from group dialing status.
To load a new autodialer directory or save the current one, click on "DISK"
and then the appropriate button.
You may copy a whole slot or just the autologs/automacros/BBS Specific macros
by clicking on Copy under the DISK menu. You can move one slot to another
location by selecting the slot, going to the DISK menu and either clicking on
MOVE or simply dragging the slot then releasing it. You may clear some or
all slots by selecting CLEAR from the DISK menu.
III. B. Dialing: - [DIL]
=======
There several different ways of dialing. The simplest is to double
click onthe name of BBS to dial. You may also may highlight the name of the
BBS using the arrow keys and hit F4 to dial.
To group dial more than one number at a time, click on "MULTI" and
highlight the names of the BBSes to call by clicking on them or moving to
its name and pressing INSERT. Once you have selected the BBSes to dial,
click on "DIAL" or hit F4.
If you wish to do other things while dialing several BBSes, you have
the option of selecting the "BACKGND" button in the dialer. This will not
pop up the dial status window, allowing you to continue to use FzDSTerm as
normal while waiting for a connection. (In fact I am chain dialing several
BBSes as I write this now.) This background dialing runs off of the user
interface interrupts, so if you run an external program or go to a
fileselector, the dialing process will be interrupted until you return. To
halt background dialing, simply click on the "DIAL" button again, or hit F4
in the Autodialer.
NOTE: You may use your Accessories as long as they open windows instead of
dialog boxes or alert boxes for input.
Available commands while dialing: (Not available during background dialing.)
SPACE or the left mouse button will abort the current dial and cycle to the
next number in the sequence.
RETURN will cycle to the next BBS in the sequence and re-Initialize the
modem.
UNDO or the right mouse button will abort the dialing sequence.
LEFT and RIGHT will change the maximum redial tries allowed.
UP and DOWN will change the dial timeout for the current BBS.
DELETE will remove the current BBS from the Group dialing list.
III. C. Auto-Logon Sequences / Auto-Macros - [ALM]
==================== ===========
If you call a BBS often, it gets tiresome typing in all of the info
normally required for your account (Handle, Password, phone number), not to
mention aborting the pages of news that you've already read a thousand times.
Well, FzDSTerm makes this process much simpler. Once you have filled in the
autolog sequence for a BBS, every time you log on after that, it will wait
for each prompt in the list and then send your reply. The autologon editor
may be reached from the Autodialer by clicking on "Autolog/Automacro Editor"
or from the Online screen by pressing F3 (for the current BBS.)
At the top of the editor, there are 5 macros that are different for each
BBS. These are used for such info as Handle, Name, Password, Phone Number,
etc. They may be used by holding ALTERNATE and pressing 1, 2, 3, 4 or 5
while connected to that BBS. They may also may be used in your Macros,
Autologs, Automacros, etc by putting in a carat (^) followed by a 1, 2, 3, 4,
or 5.
Then there are a series of blanks under the title "AutoLogs". On the
left (the short lines) is where you tell FzDSTerm what to look for coming
from the modem. When it receives these characters, it will send what is on
the right (the longer lines), and go on to the next down the list. (You may
switch from the left to right side or vice versa by pressing INSERT.) To be
able to use these, you must highlight the "Autolog" button in the autodialer
for the BBS that you have written them for.
There is a button labelled "Auto Learn Logon" in the Autolog/Automacro
editor. This can be used to generate the Prompts/Replys necessary for a
successful automatic logon to a BBS. When you want to generate the autolog
sequence for a particular BBS, do the following: Go to the autodialer and
click on the BBS which you wat to generate autologs for. Click on
"Autolog/Automac Editor". You will go into the autolog editor. Click on
"Auto Learn Logon". Click on "Exit", and then "Dial". When you connect to
the BBS, enter all required information. When you are done logging onto the
BBS, hit UNDO. All the Autologs should be filled in properly.
NOTE: Auto Learn Logon is a feature to HELP you write autologs for a BBS,
it may or may not fill in everything exactly as it should. If it
picks as a prompt sequence a character string that is repeated often,
it may end up seeing the prompt sequence earlier than you want it to
and send the reply then. (For instance, if it picks a period (".")
as a prompt, then how is it supposed to know the next time around
which exact period its supposed to send the reply on. Or if it
chooses an ANSI color code as a prompt, it may see that same color
code somewhere else, and send the reply then, which would mess up
your autologon to the BBS.) Its YOUR job to make sure it has a
unique sequence of characters. (Pick something unique out of the
line you want it to reply on, such as "Password:" instead of
"<Esc>[0;34;4;2" (an ANSI color code, which it might find elsewhere.)
Toggling screens brings you to the "Automacros". These are a bit
like extended autologs. Instead of going in a particular order, automacros
are active seperately the whole time you have them turned on. Auto-Macros
are used to perform repetitive, commonly done tasks.
In their most primitive use, they could be used to send a RETURN every
time FoReM asks you to "Hit Return". Or if you wanted to read all of the
messages on a Bulletin Board System, you could have it wait for the prompt,
and then have it send a Return until it was done reading all of your
messages, which you could read later in the capture. On a multi-line chat
board, you could have it say "Hey, Bob!", everytime it sees that your friend
Bob enters the chat. There are many uses for these, especially considering
you can use all Macro commands and Script commands from your macros.
IV. A. File Transfers - An Introduction - [XFR]
============== -- ------------
Out in the world of BBSing, there are so many programs available for
use by anyone who can download them that you really don't ever need to go
into a computer store or send away for mail order software. Its all there
for the taking, all you have to do is transfer it from the BBS that you are
calling to your computer. This is done by way of a file transfer protocol,
which ensures that the program gets from the BBS to you without any errors
due to line noise, etc. Most terminal programs have a bunch of these built
in, which usually cover all of the commonly used protocols. But what
happens if you find an interesting new protocol that your terminal program
doesnt have listed? You are out of luck.
Until now. FzDSTerm has 16 slots available to install new protocols.
All you have to do is download the protocol, find out what kind of
parameters (instructions) that it needs to be given, and type in these
parameters into FzDSTerm. It will then be able to use the new protocol as
its own. This allows you to use the latest up-to-date versions of the
protocols just by downloading them, without having to wait for the author to
update the terminal.
NOTE: Work is being done on adding either better external protocols or
internal protocols. FreeZe Dried Software has completed very fast
code for X-Modem, X-Modem 1k, Y-Modem Batch, and Y-Modem-G, send and
receive. We have not found complete documentation to Z-Modem yet, and
are searching for it desperately. If you have complete docs for any
protocols, please send them to me.
IV. B. Using your protocols - [XFU]
====================
Protocols are divided into two groups, receive and send. They may be
accessed by either clicking on Receive or Send at the main menu, hitting F4,
ALT-R or ALT-S from the Online Screen. This will bring up a menu asking
which protocol to use. Click on it or use the arrow keys to select it and
either hit SPACE, double click, or click on "Begin Receive" or "Begin Send".
If filenames need to be passed to the protocol, a fileselector will appear
foreach file. If the protocol uses the Batch Queue Lists, it will jump to
the BQL editor to input filenames to send.
Once you start the protocol, it will load the needed external program
from either the path in Default Paths or the Ramdisk, and run it.
IV. C. Installing new protocols - [XFI]
========================
Protocols may be installed by going to the protocol selection menu and
clicking on "Edit Current Slot". This will bring up an editor which allows
you to change the name, filename, command line, and autostart sequence. Hit
HELP for more information on the above information. Just about any external
program which will allow command line parameters for starting protocols may
be used. (Or you may wish to simply have FzT execute another program when
you run a protocol, and from there select options.)
Filename: The program FZT should run.
Status: What to display on the screen when running the program.
Full: Show the command line at the bottom, and show the terminal
mode in the middle.
Bottom: Show just the command line at the bottom.
None: Leave a black screen when running.
Command line: What parameters to pass. The following commands may be
inserted on the command line to pass information:
#x (x=1-9) Insert x filenames (including paths) on the command line.
#L Save a Batch Queue List to the path specified for transfer
protocols, and insert its name.
#C Copy all files in the Batch Queue to the temporary path specified
in the Default Paths editor and insert "*.*" on the command line.
(This is for programs which cannot accept Batch Queue Lists, but
can accept wildcards.) If there is only one file in the BQ, it
will just insert its name instead of copying it.
IV. D. Batch Queue List editor - [BQL]
=======================
The Batch Queue List editor is used for protocols that can be used to
send multiple files at one time (called a "Batch Upload".) This Queue is
used to input, modify, load, and save the list of files to be sent. The load
and save features are useful when you may wish to send the same list of files
to several BBSes. (Such as related text files or documentation.)
The Batch Queue List editor may only be used with protocols which accept
batch send lists (a text file containing the full path of each file,
seperated by CR/LF) or wildcards ("*.*"). Some protocols may only accept
multiple files on the command line, in which case you will not be able to use
this feature.
The following commands are available:
Add files to Queue <F1>: Will prompt you for files to add to the Queue until
you either click on Cancel in the Fileselector or the Queue is full.
Delete file from Queue <F2>: Will allow you to remove a single file from the
Queue by clicking on it.
Clear Queue <F3>: Will clear the entire Batch Queue List.
Load BQL <F4>: Will allow you to load a previously saved Batch Queue List.
Save BQL <F5>: Will allow you to save the current list of files. Load BQL
will recall this list.
V. A. Macros - An Introduction - [MAC]
====== -- ------------
Macros are key-combinations that you may set up to perform a variety of
functions. The usual use of macros is to store commonly typed words or
phrases and to insert these words when you type a certain key-combination,
such as Shift-F1. But in FzDSTerm, macros can do much more. By putting a
particular sequence of characters, you can do much more with macros; such as
chaining (execute another macro, then return), activating an alternate key
combination (Like Alternate-H to Hangup could be put in a macro as "^H".) See
"V. C. Explaination of Macro Functions" for a complete list.
In FzDSTerm, there can be a total of 45 macros active at a time. (40
macros per set, plus 5 extra for each BBS in the autodialer.) They may be
used by pressing the following key combinations:
Regular Macros: 01 to 10 -- SHIFT and F1 thru F10
11 to 20 -- CONTROL and F1 thru F10
21 to 30 -- ALTERNATE and F1 thru F10
31 to 40 -- SHIFT and ALTERNATE and F1 thru F10
BBS Macros: 1 to 5 -- ALTERNATE and 1 thru 5 (not on numeric keypad)
V. B. Editing Your Macros - [MCE]
===================
You may edit your macros by either clicking on "Macro Editor" from the
main menu or pressing F5 from the online screen or main menu. The
combinations of SHIFT, CONTROL, ALTERNATE and F1 thru F10 to use to activate
each macro are shown down the left side. Just move the cursor with the arrow
keys and type! Clicking on "Next (Previous) Page" or hitting Insert will
toggle which page to edit (F01-F20 or F21-F40). BBS Specific macros may be
edited from the AutoLog/AutoMacro editor for the appropriate BBS. To load,
save, clear, or print macros, click on the the appropriate button or press
F1-F5 to select the function.
V. C. Explaination of Macro Functions - [MCF]
===============================
Not only can macros automate your typing, but they can also do many
other things for you. You may also mix the two, as most macro functions may
be placed anywhere in a macro and may even be used repeatedly in each macro.
Macro functions:
----- ---------
* - Available in Macros, BBS Specific Macros, Autologs, and Automacros
** - Available in Initialization Strings
Execute another macro and return when done
Format: ^nn
* nn being the >2< digit macro number from 01 to 40.
Execute BBS Specific macro and return
Format: ^n
* n being the single digit macro number from 1 to 5
Execute Keyboard Function
Format: ^n
* n being a letter from A to Z
Normally, you would hold down ALT and type the letter,
such as ALT-H for hangup or ALT-M for toggle automacros
would be ^H or ^M in a macro.
Half Second Pause
Format: ~
*, ** Each ~ in the macro will cause it to wait a half second before
sending the rest of the macro.
Perform File Function:
Format: %<path><filename>.<ext>%
* <path> is optional
If <ext> is: MAC - Load macro set
NUM - Load autodialer directory
PRG, TOS, or TTP - Execute Program (no parameters)
RND - Pick random line from 1 to 50 out of text file
(useful for throwing in a random quote, etc.)
Anything else - ASCII Send Text file
Send String Directly To Screen
Format: `<Message>
* <Message> being what you want to send to the screen. (You may
wish FzDSTerm to display a short memo to you when you use a
particular macro, this will do so.)
Execute Script File Command
Format: ><Command>|
<Command> being the script file command. This allows you to use
any of the script file features in your macros.
Examples:
>DL Z D:\| - Download Z-Modem To D:\
>UL E:\| - Select protocol to upload with, then select files from E:\
NOTE: This has to be the first thing in a macro. The ">" must be the
first character in the macro. Other things may follow the "|".
Wait For String To Come From Modem:
Format: {<string>}
** <string> is String to wait for
In an Init String, you may wish to have FZT wait for the modem
wait for something to come back from the modem before continuing
to send the line. (Such as sending the modem an AT command and
have FzDSTerm wait for an "OK" to come back. This works in many
cases instead of a long pause.)
VI. A. Disk Commands - [DSK]
=============
While online, you may find it necessary to perform some disk function,
such as viewing or copying a file, or formatting a disk. Also contained in
Disk Commands is a limited shell for manipulating LZH, ARC, and ZIP archives.
Using this shell you may view, extract, or add files to an archive.
Copy File(s) <F1>: Prompts for file to copy from and path to copy it to. You
may specify a new name for the file to copy to, and it will change the
name of the file when it copies. You may a filename containing wildcards
(such as "*.*") for the file to copy and it will copy all files which
match the wildcard.
Rename File/Move File(s) <F2>: If you wish to rename a file, click on it in
the first fileselector, and then input the new name in the second. If
you wish to move files (copy, then delete), for the first fileselector
input the filename (wildcards accepted), and specify the path to move
them to in the second.
Delete Files / Remove Folder <F3>: To delete a file, input the filename
(wildcards accepted), and it will delete all matching files. To remove a
folder, go to the folder to remove and leave the filename field blank.
If there are no files in the folder, it will remove it.
Create Folder <F4>: Prompts for the path and the name of the new folder to
create.
Format Floppy <F5>: A simple floppy disk formatter, it can do 9 or 10 sectors
and between 80 and 82 tracks on either drive A or B. If you want to
format MS-DOS compatible disks, set it to format using 9 sectors, 80
tracks. The MS-DOS bootsector will be placed on the disk.
Free Disk Space: Will prompt you for a drive, and show the remaining space on
that drive.
Free RAM: Shows the amount of memory available.
Directory <F6>: Jump to the fileselector
Show Text File <F7>: Display a text file.
Print Text File <F8>: Print a text file.
ASCII Send Text File <F9>: Send a text file as ASCII text to the modem.
Execute Program <F10>: Run another program from inside FzDSTerm.
VI. B. Using The LZH/ARC/ZIP Archiver Shell - [ARC]
====================================
The archiver shell may be used in place of ARCShell or other
point-and-click interfaces for archive utilities. Normally to use many
archivers, such as LZH, ARC, or ZIP, you would need to supply a complex
command line every time you wished to view, extract, etc an archive. There
are a total of 9 different setups for external archivers; each of the formats
(LZH, ARC, ZIP) has a setup for each type of function (View, Extract, Add).
Once you configure these (see Setting up, below), these functions are quite
easy to use.
To select an archive to manipulate, click on "Archive: ...". You will
then be prompted with a fileselector for the filename of the archive. (For
the "Add To Archive" function, the file need not exist yet.) Then select the
archive format to use (LZH, ARC, ZIP). Then select the function (View,
Extract, Add). If you are doing an Extract, you may wish to change the path
to extract to by clicking on "Extract To: ...". (Some archive programs will
allow you to specify a template to extract, such as "*.TXT" or "READ.ME". You
may enter the template in the filename portion of the fileselector.) Then
click on "Begin Operation" to start whatever process you have selected. If
for any reason it does not appear to work correctly, check over the setup by
clicking on "Install Utility".
VI. C. Setting up the archiver shell - [ARS]
=============================
Archivers need to be passed parameters much like protocols. You may
edit an archiver's parameters by chosing the right combination of
View/Extract/Add and LZH/ARC/ZIP and clicking on "Install Utility". You will
need to know what parameters each program needs to be passed for each
function. There are also several parameters that FzDSTerm will insert for
you, such filenames and extract paths. These parameters are shown in the
installation window.
NOTE: Some users have had problems using the archiver shell. If when you
click on Begin Operation, the drive spins and returns an Out Of Memory error,
or the program loads up and produces Bombs, you may not have enough memory to
use this feature.
To install an archiver, you will need to specify its filename, whether you
want FzT to pause for a keypress after execution, and a parameter command
line. The following options may be placed on the command line:
%1 Insert the name of the LZH, ZIP, or ARC file to be Viewed,
Extracted from or Added to.
%2 Insert the path in "Extract To: ..."
%L Ask for a list of files and save them as in the format of a batch
queue list.
%C Ask for a list of files, and copy them to the temp path specified
in "Default Paths". Insert "*.*" on the command line.
%I Ask for files, and insert them all on the command line (including
paths.)
%D Ask for files, and insert them, leading directory style:
The files: E:\TEMP\FILE.LZH, E:\TEMP\FILE2.LZH, D:\GAME\DEMO.PRG,
D:\GAME\DATA.001, and F:\ARC\LHA.TTP would produce:
D:\GAME\ DATA.001 DEMO.PRG E:\TEMP\ FILE.LZH FILE2.LZH F:\ARC\ LHA.TTP
%Q Ask for a list of files and insert them in the format for
Quester's Lharc (v2.01x). This is a less compressed method than %D,
but it works. With the same files, this format would produce:
D:\GAME\ DATA.001 DEMO.PRG E:\TEMP\FILE.LZH E:\TEMP\FILE2.LZH F:\ARC\LHA.TTP
VII. RS-232 Configuration - [RS2]
====================
Many serial port settings may be changed here, including baud, echo,
linefeed, duplex, parity, stop bits, word length, etc. Get to it by F8 from
the Online screen or "Rs-232 Config" in the main menu.
VIII. System Setup Menu - [SYS]
=================
This is where you can configure your system and FzDSTerm to your
personal preferences. Its kind of like a control panel, but for parameters
inside FzDSTerm. This menu may be reached from the term screen or main menu
by F8, or by clicking on "System Setup" from the main menu.
This menu may auto-redraw itself if you change any functions pertaining
to the user interface in FzT. It will attempt to show you an accurate
representation of what the menus will look like by redrawing itself when
necessary.
VIII. A. Changing your colors - [COL]
====================
If you do not like the default black background, off-white foreground,
and blue and red alternate colors, you may change them with these sliders.
There are two different sets of colors, one set for the online screen, and
another for the menus, etc. To toggle between sets, click on "Edit Colors:
...". Then select which color to edit by clicking on the color (below the
sliders). Then you can change the levels of red, green, and blue in each
color by click on the sliders. (In monochrome, the sliders will be replaced
by one large button labeled "Monochrome Inverse". This will allow you to
select whether the text will be white on a black background or vice-versa.)
NOTE: In non-ST resolutions, these color settings will have no effect.
Please set them with a control panel or other program.
VIII. B. System Parameters - [PAR]
=================
If you want to change the status (on/off) of keyclick, the Control-G
system bell, or whether or not FzDSTerm ejects the last page of a printout or
not, you may do so here.
Text shadows may also be toggled here. I hear that the shadow effect on
much of the text makes it unreadable in monochrome. As I have no way of
testing this, I have included the option of turning this on or off.
VIII. C. Terminal Event Chimes - [CHM]
=====================
This allows you to turn on or off the chimes for certain events that
happen throughout FZT, such as connect, error, warning, etc. I enjoy these,
as I can be in a different room and leave FzDSTerm doing something, and I
know exactly what happened by which chime it produces. Some people may find
these annoying, so they can turn them off with this.
VIII. D. The Daily .LOG - [LOG]
========= ===
If for some reason, you need to keep a record of what you have done in
FzDSTerm, turn this option on. It will store your actions in a file with the
format "FTyymmdd.LOG" (FT<Year><Month><Day>.LOG), which changes each day.
"Keep for __ Days" tells FZT how many days to keep the log files before
deleting them (to conserve space). Usually 2-3 days is plenty.
NOTE: This option shouldn't be used if your system clock will not always be
set to the right date.
VIII. E. AES Background Events - [AES]
=====================
If you have an alarm clock accessory, background transfer accessory, or
anything that counts on GEM/AES calls to run in the background, you will need
to turn this option on. "Every: ... ms" is the amount of time, in
milliseconds, to allow between AES event_multi() calls. If it doesn't need
to hog processor time, and only checks something every once in a while, such
as an alarm clock, set the time to a fairly high number. If it needs to
continously be called, set it to a low number.
NOTE: Having this option on will cause your mouse cursor to be constantly on,
for some unknown reason. (GEM bug of some sort?)
VIII. F. BBS Timeout Logoff Pause - [LOF]
========================
Have you ever been on a BBS, and gone to check something somewhere else
in a terminal, and come back, only to find that the BBS has hung up on you
because you took too long doing whatever it was that you were doing. Now
with FzDSTerm, you can have it send a few characters every so often just to
make sure that this won't happen. "BBS Timeout Logoff Pause" will turn this
option on/off. "Send: ..." is what it should send. Usually a space and a
backspace (Control-H) works best here. "Every: ..." is how often, in
seconds, to send it. And lastly, the "Modem Inp Only" will wait until there
is input from the modem before sending it. BBSes usually give a warning
before they hang up, this will wait for the warning before sending anything.
NOTE: FzDSTerm will only perform this function while it has control of the
computer. This will not work while in a fileselector or while running
an external protocol, archiver, or other program.
Also, if you need to walk away from the computer while on a BBS, you may
either press Alternate-Z while at the online screen, or put a carat ("^")
followed by a "Z" in a macro. This will temporarily activate BBS Pause, and
to continue, press any key.
IIX. Font Installation - [FNT]
=================
FzDSTerm supports the changing of the system character set. The
standard ST VT-52 system font cannot be used with ANSI or UBBS-Term
emulations, as they require different character sets for proper use. Also,
you may get tired of looking at the same font day after day, and may wish to
see something new. Therefore, FzDSTerm has multiple options for installing
new fonts. Several fonts are provided, including the standard system font,
an ANSI font, a font for use with UBBS-Term (this will be added to in the
near future), and a couple others which I found, including Macintosh and
Future style fonts. You may also load standard .FED (Font-EDitor) 8x8
or 8x16 fonts by double clicking on "Install New Font".
In editors: Font? - Use the selected font in menus and editors using the
BIOS text font font, or use the standard system font?
UBT: Keep UBT Font - Always use UBBS-Term Font while in UBT Emulation
regardless of the selected font?
ANSI: Keep ANSI Font - Always use ANSI Font while in ANSI emulation
regardless of the selected font?
ANSI Font Attributes - The ANSI emulation standard allows the remote system
to change the font style to Bold, Underline, Italics, Shaded, or any
combination of the above. If you would like to see these attributes
displayed, turn this feature on. (This requires that FZT be able to
change the font (see below), and it also eats up an extra 8k-16k if
selected.)
NOTE:
It has been reported that GDOS, an accessory known as "Font-Tricks", and
Warp9 (with a new font installed) will not allow FzDSTerm to change the
font. Also, Quick ST has been known to scramble the new font. Also,
Turbo ST will not allow FZT to change the font if the "ANSI Attributes"
feature is on. If you cannot get FZT to change the font or the fonts look
scrambled, please remove any extra AUTO or Accessory programs and/or disable
any screen accelerators you may have installed.
IX. The Capture Buffer - [CAP]
==================
The Capture Buffer collects all input from the modem and stores it for
your future use. If you need to look back at something that scrolled off the
top of the screen too quickly, or need to look back at something that went by
quite a while ago, you would use the capture.
The capture sorts the input from the modem by lines, seperated by
Returns. You may specify the maximum amount of these lines in the capture
configuration. There is no set size limit; each line may be 32k in length,
but each normally is under 80 bytes. You will need to play with this setting
a little to avoid using too much memory. I find that 5000 lines is fine if
you have more than a meg, but with only a meg you might want to keep it at
around 1000 lines.
If the capture is on, you will see the capture filling up available
lines by watching the "nn%" in the lower right corner of the online screen.
When it gets full, one of several things will happen depending on how you
have it setup:
Wrap: It will drop the top line to create space and then put the new line on
the bottom of the stack. The capture always remains full of lines.
Clear: It will clear the whole capture.
Flush: It will append the whole capture to a file, and then clear it.
Save dropped: Like "Wrap" except each line as it is dropped will be appended
to a file.
Ask: It will ask you if you want to Wrap, Clear, or Flush the capture.
IX. A. The Scrollback - [SCL]
==============
The scrollback allows you to view and cut out parts of the capture
buffer. Get to the scrollback by hitting F6 from the online screen or main
menu, or click on Scrollback in the main menu. To move around, you may use
the arrow keys or click on arrows indicating the direction you wish to move
the cursor up at the top.
Mouse controlled scrolling is also available. You can move the mouse cursor
down below the drop down menu, and use the mouse buttons to page up and
down. (Holding down both mouse buttons will exit.)
There are various block and search commands available under the menu bar,
along with keyboard commands for them.
IX. B. Capture Buffer Configuration - [CPC]
============================
This allows you to set up your capture. You may get here by Alt-C frm
the online screen, "Capture Setup" from the main menu, or "Setup" from the
scrollback. The left and right arrows allow you to set the number of lines
allowed in the scrollback. The "Full Buffer: ..." button has the functions
described under "The Capture Buffer". To be able to use "Save Dropped Lines"
or flush, you need to define a filename to save to. Do this with the "Save
as: ..." button. You may also save the capture when you exit FzDSTerm by
turning on "Save Upon Exit".
X. The Text Editor - [TED]
===============
The Text Editor is basically a mini word processor that allows you to
alter any standard ASCII text file. You may Load or Insert text from a file
on disk or Import a block of text from the Scrollback (define the block in
the scrollback first.) With the block commands, you can copy, move, delete,
print, ascii send, send using a protocol, or save/append to a file. You can
clear, print, or save/append all of the text. All commands and appropriate
keypresses can be found under the pulldown menus. (Keypresses are indicated
by the two leftmost characters next to the corresponding command. The
highlighted X next to a letter means hold down ALTERNATE while pressing that
key.)
Mouse controlled scrolling is available in the text editor. To use it,
hold down control or activate "Caps Lock". When the mouse cursor is
positioned below the menu bar, you can use the mouse buttons to page up and
down. Hold down both buttons to exit.
There is a special feature of the text editor which you may or may not
use. It allows you to edit the document in the text editor while at the
online screen and receiving input from the modem. I use it instead of a
paper and pencil for taking notes, but other uses might be to write a report
while sitting on a chat board, etc. This feature may be turned on by hitting
INSERT at the online screen. UNDO will remove it, and INSERT will toggle
whether your typing is sent to the modem or the text editor. (NOTE: To use
most of the extra features of the text editor, you will need to go to the
main text editor. <F7>)
XI. Script Files - [.DO]
============
Script files allow for the automation of many of the functions in
FzDSTerm. At the moment, only commands available in both FzDSTerm and Flash
have been implemented, in the future there will be many more added.
A script file is simply an ASCII text file composed of a list of
commands, in order of execution. I don't use .DO files that often, so I
can't say how well they will hold up (especially some of the unusual
variations of the commands.) This will be greatly expanded in the
future, and this list is provided as a quick reference, not an
in-depth guide. An in-depth description will be provided when the
Script language is better implemented. Here's a description of FzT's .DO
commands:
o Commands must start with the '>' symbol. (Without the '>', it is sent
directly to the serial port.)
o Variable names must be entered in uppercase, commands can be either upper
or lower case.
o Only one command is allowed per line.
o A '|' in a string simulates a Carriage Return character.
o Commands may usually be abbreviated by taking the first 2 characters.
o 26 variables (places to store data) preceded by '$' and followed by a
letter.
NOTE: Commands marked with a * are known not to be implemented properly.)
Cmd: Description:
--- -----------
AL Get user input through a GEM alert box. The button number selected
(1-3) is stored in the variable.
>AL ("[0-3][TXT1|TXT2|TXT3][BUT1|BUT2|BUT3]") ($A-$Z)|
AL Set status of Autologs
>AL ($A-$Z ON OF /)|
AM Set status of Automacros
>AM ($A-$Z ON OF /)|
AP BL *Append marked block to a text file
>AP BL ($A-$Z D:\FILENAME.EXT)|
AS * Set ASCII parameters
>AS ($A-$Z 0-9 D S M P \x)|
AU Set .DO file to auto-execute upon bootup
>AU ($A-$Z "TXT")|
BA Select Baud Rate
>BA ($A-$Z 11 30 60 12 24 48 96 19)|
B1 Ring the system bell (Control-G)
>B1|
B2 Keep ringing the bell every second until a key is pressed.
>B2|
CA Set capture buffer status
>CA ($A-$Z ON OF / CL)|
CL Display the system clock as opposed to the online timer
>CL|
CO Copy file(s) from one path to another or one name to another
>CO ($A-$Z D:FILENAME.EXT) ($A-$Z D:FILENAME.EXT)|
DD * Display contents of path. (Now it opens a fileselector)
>DD ($A-$Z D:FILENAME.EXT) (A$-$Z D:FILENAME.EXT AUX:)|
DE Delete file(s).
>DE ($A-$Z D:FILENAME.EXT)|
DF * Display current free space on drive
>DF ($A-$Z A:-P:)|
DI Dial phone number. (If a matching name or number is found in the
autodialer, it will dial that. Otherwise, it will dial the number.)
>DI (NUMBER NAME)|
DL Download file
>DL (<Search Pattern for Proto name>) (A$-$Z D:FILENAME.EXT)|
DO * Execute .DO file. (Will not currently return from it.)
>DO ($A-$Z D:FILENAME.EXT)|
DP Set default path
>DP ($A-$Z A:-P:)|
DU Set duplex
>DU ($A-$Z FU HA /)|
EC Set echo
>EC ($A-$Z ON OF /)|
ED Open an edit window
>ED (AS DI FK RS BQ)|
EN End a .DO files
>EN|
EX Execute another program
>EX ($A-$Z D:\FILENAME.EXT) (PARAMETERS)|
FF Send the printer a form feed and clear the screen
>FF|
FK Set a function key equal to another string
>FK ((I1-I5/01-40) ($A-$Z "TXT")|
GEM Execute a program
>GEM ($A-$Z D:FILENAME.EXT) (PARAMETERS)|
GET Get input from the serial port - RETURN=Stop BS=Back up 1 char
>GET ($A-$Z) (1-9999)| - 2 Minute default
GO Gosub function key and return
>GO (1-20)|
HE Open the help window
>HE|
HG Hang up the phone
>HG|
IN * Get input from the "OP"en device.
>IN ($A-$Z)|
JM Jump to a label
>JM (LABEL)|
KI Kill a file
>KI ($A-$Z D:FILENAME.EXT)|
LF Set Input LineFeeds
>LF ($A-$Z ON OF /)|
LO Load a File
>LO (CA DI FK BQ) ($A-$Z D:FILENAME.EXT)|
LOG Insert text into the capture buffer
>LOG ($A-$Z "TXT")|
L: Define a line as a label
>L: (LABEL)|
ME Go To the Main Menu
>ME|
MK Mark a block in the capture
>MK (TO BO CL)|
MO Set Emulation Mode
>MO ($A-$Z VT AN IG UB ST)|
NA Rename a file
>CO ($A-$Z D:FILENAME.EXT) ($A-$Z D:FILENAME.EXT)|
OP * Open a device for Input
>OP ($A-$Z D:\FILENAME.EXT AUX: BLK: BUF:)|
PA Pause for a certain number of seconds, or until a key is pressed
>PA (1-9999)|
PR Set Modem Input->Printer
>PR ($A-$Z ON OF /)|
PY Set Parity
>PY ($A-$Z NO OD EV)|
QU Query the user for input
>QU ("TXT1|TXT2|TXT3") ($A-$Z)|
RE Set Max number of redials
>RE (0-990)|
RU Set Destructive Backspace (RUbout)
>RU (ON OF /)|
RT Reset Time to 0 seconds online
>RT|
SA Save File
>SA (BL CA CO DI FK BQ) ($A-$Z D:FILENAME.EXT)|
SB Set Stop Bits
>SB ($A-$Z 1 2)|
SC Set system clock (in 24-hour format)
>SC ($A-$Z "HH:MM:SS")|
SE Send text to the Serial port (and screen if in Half Duplex)
>SE ($A-$Z "TXT")| WITH OR WITHOUT CR/LF
ST Set strip bit
>ST ($A-$Z ON OF /)|
TA Set type ahead mode
>TA ($A ON OF /)|
TI Display the Onliner Timer as opposed to the System Clock
>TI|
TY Send text directly to screen
>TY ($A-$Z "TXT")| WITH OR WITHOUT CR/LF
UL Upload a file
>UL (<Proto Search String>) ($A-$Z D:FILENAME.EXT)|
UL BL *Upload a marked block
>UP BL (Protocol Search Pattern)|
UL CA *Upload the capture buffer
>UP CA (Protocol Search Pattern)|
VI View a text file
>VI ($A-$Z D:FILENAME.EXT)|
WA * Wait for a certain string to come through the serial port before
executing next command.
>WA ($A-&Z "TEXT") [(1-9999) (LABEL)]|
WL Set Rs232 word length
>WL ($A-$Z 7 8)|
WT * Wait for a certain time (24 hour format)
>WT ($A-$Z "HH:MM:SS")|
** Remark or comment - Not executed
>** (TXT)|
System Devices:
BLK: Currently marked block
BUF: Capture Buffer
* AUX: Serial Port
System Variables:
CA TRUE if a carrier is currently detected
* DI TRUE if the last dial command succeeded
DL TRUE if the last download succeeded
* EO TRUE if the end of a file is reached
OP TRUE if a file is currently open for variable input
UL TRUE if the last upload succeeded
* WA TRUE if the last WA command succeeded
* A-Z TRUE if the length of $A-$Z is greater than 0
$A-$Z String variables (used to store text strings.)
Set a string:
>($A-$Z) "TXT"|
>($A-$Z) ($A-$Z)|
Invert a condition (TRUE->FALSE, FALSE->TRUE):
>IF ~CA COMMAND|
>TFI ~($A-$Z) "TXT" COMMAND|
Test a system variable:
>IF CA COMMAND|
>IF (A-Z) COMMAND|
Compare strings:
>IFI ($A-$Z) ($A-$Z) COMMAND|
>IFI ($A-$Z) "TXT" COMMAND|
XII. A. How to Reach the author - [RCH]
=======================
There is now a GEnie topic for The FreeZe Dried Terminal:
It's Category 8, Topic 6, "FreeZe Dried Terminal".
All posts will reach me one way or another.
Or, send E-Mail on GEnie to S.PRICE19. I do not have an
account on GEnie as of yet, but all mail will reach me
via Sean Price, and I should be able to reply.
Or, I may be reached by sending me a letter to this address:
Aaron Hopkins
RE: FzDSTerm Comments
1213 Walnut Avenue
Manhattan Beach, CA 90266
USA
Or, send me Email or Netmail on one of the following BBSes:
- The Official FreeZe Dried Software support board: -
Sanctuary From the Law |RatSoft|Dual | (619) 377-3611 | #29 Lazlar Lyricon
NOTE: There is a guest account for FzDSTerm to give you instant
access to download the latest FzT Demo version, and send
feedback to the author. Type "FzDSTerm" where it asks for
your handle. Please use this if you only plan on calling
0 once, as our user list is already getting a bit full.
- Lead Node of the US Xnet FzDSTerm Support Conference -
MasaTek (Fnet #429) |//Trbo| Dual | (310) 518-9524 | Lazlar Lyricon
NOTE: There is also an account on Masatek to get the latest
version. Log on as "FzDSTerm", password "FzDSTerm".
MasaTek is the lead node of a new Crossnet conference
supporting FzDSTerm. Its conference 21429, contact your
local ///Turbo Board or FoReM sysop and ask him to add it,
if you are interested. (The latest versions of FzT will be
sent out through the Crossnet, so you can get it even
faster.)
- Other BBSes Where I May Be Reached: -
The Travellin' BBS | UBBS | HST | (310) 543-5483 | #3 Lazlar Lyricon
Target Range |Expres| HST | (310) 643-8993 | Lazlar Lyricon
CodeHead Quarters |Mchtrn| 2400 | (213) 461-2095 | Aaron Hopkins
Club Playhouse | DLX | 2400 | (818) 781-PLAY | #2013 FreeZeDriedHell
There is also a support BBS for European users of The FreeZe Dried
Terminal: (Along with ///Turbo Board, Maximiser, and IGS.)
<<<InterNet>>> Tel: +44-296-395-935
HST/V32 V32bis/V42bis 24Hrs Fnet node 1031
A support conference is available on Fnet which is also gated to
Fidonet via <<<InterNet>>> to Sounds Digital BBS (2:256/45)
If you can't call, Ben Van Bokkem (the sysop) is handling
the European support. He may be contacted at:
Ben Van Bokkem
100, Broughton Avenue
Aylesbury,
Bucks, HP20 1QB
England
Thank you Ben, for all of your help.
XII. B. How to report Bugs - [BUG]
==================
If you have come across a bug in the program, I would like to find out about
it. We would like the following information:
o What exactly the problem is. (Details, details!)
o Which version(s) have you found it in?
o What type of ST are you running it on (ST/STe/TT).
o Which version of TOS you are using.
o What resolution you are running it in.
o Amount of RAM your ST has.
o How many drives you have, specify types. (Type of driver software if using
Hard Drive.)
o Which memory resident programs you have installed. (Accessories and AUTO
folder programs.)
o What color is the status bar (if you are in the terminal mode when this
happens.)
Please when reporting bugs we need to know this information to make it
compatible with your system.
XII. C. Future Features - [FUT]
===============
These are some features that we hope to have in coming versions:
Better Documentation
Internal Transfer protocols
Improved Script Files
More emulations (VT-100/102/2xx/3xx)
Better IGS Emulation
Graphics Boards/TT resolution compatibility
XIII. Troubleshooting [TBL]
===============
This is a summary of the most commonly asked questions, along with
answers or suggestions. FzDSTerm has many powerful features, some of which
may confuse you, or may not work correctly with your system. Before sending
me e-mail or asking around for help, READ THIS! If you are having a
non-specific problem, please look through all of these tips and see if there
is anything resembling your problem.
If you have gone through FzDSTerm and played with any settings, you may
have unintentionally altered some important setting which is causing your
problem. If all else fails, you may wish to delete your config file
(FZDSTERM.CFG) and start over.
XIII. A. General [TBG]
=======
Problem: FzDSTerm bombs out, the user interface does very strange things, or
I get out of memory errors a lot. (Or the screen flashes red a
lot, along with a warning tone.)
-or- When I click on something in a menu, and then come back, the screen
is blank except for the button I clicked on.
Suggestions:
a) If your ST has one meg of RAM or less, you cannot install every AUTO
program and Accessory under the sun and expect FzT to be able to have enough
RAM to run correctly. Take out some of the useless stuff. Rename .PRGs to
.PRX in your auto folder and .ACCs to .ACX and try again.
b) The current capture buffer system does not support the ability to define
an amount of memory to use as the capture. You must tell it the number of
lines to use. If you are running low on memory, try making the capture
buffer a bit smaller. (Go to "Capture Config".)
c) You may be having TSR/ACC conflicts with FzT. One or more of your AUTO
programs or accessories might be doing something weird which FzT doesn't
expect. Try de-installing all AUTO and .ACC programs and reinstalling them
one by one until you find the culprit. (See the procedure for this, above.)
---
Problem: I call GEnie/Compuserve/Delphi/Tymnet/Telenet/etc and with other
terminal programs, everythings fine, but for some reason FzT just
produces garbage.
Suggestion:
Go to the autodialer, and select the service you are trying to connect to.
Change the emulation to "Strip 7th Bit". This should do the trick. (How
this is done will probably be changed in the future, as this would put in
hastily.)
---
Problem: When I am online, FzT loses some characters that are coming in
through the modem. Letters are missing in random words.
Suggestions:
a) If you are on an STe or other machine with a Blitter, try turning it off.
This usually helps.
b) If you are using a screen accelerator (Quick ST, Turbo ST), they speed up
the screen display at the expense of slowing the system down a bit. The
system may not be able to catch all of the characters coming in through the
modem. Try turning this off.
---
Problem: Why won't FzT recognise my printer? It keeps saying "Printer Not
Available".
Suggestions:
a) Check your printer and make sure its really "Online" and hooked up to
your ST properly.
b) Try another printer. If it works, try substituting the cable from the
working one to the other. Possibly, one of the signals is not reaching your
ST, and the cable may be at fault.
c) Try removing any printer drivers you may have installed. They could
possibly be interfering.
d) Remove any printer buffers or printer spoolers that you have installed.
These may be doing weird things to your system.
---
Problem: The fonts look garbled, ANSI attributes don't work, or the Font
menu doesn't do anything.
Suggestions:
It has been reported that GDOS, an accessory known as "Font-Tricks", and
Warp9 (with a new font installed) will not allow FzDSTerm to change the
font. Also, Quick ST has been known to scramble the new font. Also,
Turbo ST will not allow FZT to change the font if the "ANSI Attributes"
feature is on. If you cannot get FZT to change the font or the fonts look
scrambled, please remove any extra AUTO or Accessory programs and/or disable
any screen accelerators you may have installed.
XIII. B. Transfers [TBT]
=========
Problem: I have an HST/MNP/compression-something-er-other modem and for some
reason I can't upload using Z-Modem or Ymodem-G. It continuously
gets errors every few KB or it aborts irregularly.
Suggestions:
a) Get a CTS patch. (TurboCTS, HS_Fix, etc.) High speed modems use the RTS
and CTS lines of the RS-232 interface to regulate the flow of data through
the serial port. Unfortunately, TOS versions 1.0, 1.4, 1.6x, 2.xx, and 3.xx
cannot properly interpret these signals without a patch.
b) Go to RS-232 config and turn off the button marked "1k (Serial) Output
Buffer". This will disable the output buffer that FzT normally installs,
which normally helps the situation.
c) Make sure you have RTS/CTS flow control on your modem set correctly.
(On HSTs its "AT&H1&R0".)
---
Problem: I have only floppy drives and I can't get the protocols to work
correctly. If I put any disk in but the one FzDSTerm is on, it
refuses to download or upload, or I simply can't transfer anything.
Suggestions:
a) You need to have the .TTP or .PRG for the protocols available to FzDSTerm
every time they are executed. This means they must be on a disk which is
always in the drive. If you have another drive, you will have to download
to that.
b) You may also use the Ramdisk feature for your external protocols and
archivers. (Such as HRAMDISK.PRG) Install it, run FzT, and go to "Default
Paths". Click on Ramdisk, and select the path of it. (ie "L:\") (See the
main documentation under "Setting Up" for more details.)
---
Problem: Whenever I try and use the Batch Queue List editor to send files
using XYZ.TTP, XYZ justs displays the info screen and returns
without doing anything.
Suggestion:
Make SURE you are using XYZ.TTP v2.01. Versions 2.0, 2.1, etc do NOT
support the full command set that is set up as the defaults for FzT. You
make use it, but you will need to re-enter the command lines for everything
using XYZ.
XIII. C. Autodialer [TBA]
==========
Problem: FzT always seems to think that my modem is online (carrier detect)
even though it is not. What do I do?
-or- FzT won't dial with my modem turned on, but when I turn it off, I
can click on dial. What's up?
Suggestions:
a) Many modems come factory preset with their DIP switches or NVRAM settings
("AT...") set up in wierd configurations. FzT need to be able to detect
CD to properly function. Go to the online mode and type "AT&C1" and hit
RETURN. If FzT now recognises that the modem is not online, then go to
the terminal mode and type the following:
ATZ<Return>
AT&C1<Return>
AT&W<Return>
If that doesn't work, consult your modem's manual on Carrier Detect and/or
DIP switch settings. (You might try adding "&C1" to your Init String.)
b) If you are on a TT, there may be hope for you yet. Some TTs have their
carrier detect line reversed. (Online is really Offline, and vice-versa.)
FzT should have asked you the current status of the carrier detect of your
modem when you first ran it (without a config file). If it didn't, or you
answered incorrectly, please delete your current config file and try again.
c) If you are running Maccel v2 (Atari's Mouse Accelerator), remove it from
your AUTO folder. It is rumored to cause the CD line to always be high
(online.)
---
Problem: I bought a cheap modem and it won't recognise anything that
FzDSTerm sends it (like dial commands, etc.)
Suggestions:
a) Try setting "Char Delay" to a number higher than 0. (In
"Autodialer Setup".) This will slow down the sending of dial commands/init
strings, to hopefully make your modem recognise commands.
b) Make sure the init string/dial strings are set correctly for your modem.
Consult your modem manual for details. (The defaults should work, but your
modem make misinterpret some commands.) If necessary, completely delete the
Init String, and turn your modem off and back on.
---
Problem: My phone system is weird and I can't get FzDSTerm to dial numbers
correctly.
Suggestions:
a) If you are in the US or Canada, make sure your phone number Area Code is
set correctly (Autodialer Setup). If you are not in the US or Canada,
leave the Area Code BLANK!
b) Go to "Init Strings/Autodialer Setup". Click on the button labeled "Free
Format" so it is selected. You will be prompted for a pattern to convert
your current number entries to exactly what it needs to dial. (Make sure
your area code is set correctly before doing this.)
---
Problem: I need to put a lot of info in the number of each BBS I want to
call, such as settings for my modem or long distance dialing codes
and have no room to do so.
Suggestions:
a) If your autodialer is in "Free Format", you have the two different dial
strings to use (Dial #1/#2 in Init Strings.) You can select which one to
dial with for each BBS by using the "DS1"/"DS2" button next to the number of
the BBS.
b) You can insert macros and BBS Specific macros into your dial command.
(Macros: "^xx" where xx is between 01 and 40 - BBS Specific macros: "^x"
where x is between 1 and 5.) Examples:
To insert a modem command into your dial command:
- Change the Dial String in Init Strings to "AT^5DT<Insert><Return".
- For each BBS that you need to change a modem setting, select the BBS in
the autodialer and go to the Autolog/Automacro editor. The first five
lines are the BBS Specific macros (different for each BBS.) Go down to
macro number 5 and put the command (ie "&H0") that you want inserted in
the dial command. When it dials, it will insert it.
To add a long distance dial code:
- Do the same as for adding a dial command, but change the dial string to
"ATDT^5<Insert><Return>.
XIV. Final Acknowledgements - [FIN]
======================
For general ideas and help with writing this documentation, I wish to thank
Jason Sylvester.
For general ideas, programming tips, and the use of his TT for testing this
thing, I wish to thank Sean Price.
For programming tips and ideas, thanks go out to John Eidsvoog.
For beta testing FzDSTerm, I wish to thank the following people:
Jason Sylvester
Sean Price
Ben Van Bokkem
Norm Weinress
Mike O'Shea
Scott Book
Mark Cox
To all the users who have made the continual updating of FzT possible
through their patience, understanding, helpful suggestions, and MONEY, I
give a sincere THANK YOU!
To my friends who I see less of than I'd like to because of this thing:
"Batcave!" (inside joke)
For their outstanding product, the "Nectar of the Gods", I wish to thank
Coca-Cola.
I'd like to wish that damned gremlin that keeps my ST alive and running most
of the time a LONG LIFE! (and to plead with it to be merciful with me.)
To everyone at Atari around the world who have brought us the greatest
platform available: "Don't BLOW IT this time around, guys."