home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ARM Club 3
/
TheARMClub_PDCD3.iso
/
hensa
/
network
/
termhost_1
/
!TermHost
/
!Help
next >
Wrap
Text File
|
1994-04-24
|
6KB
|
169 lines
Term Host © David Brain 1993
****************************
Legal Bit:
This program is freeware, and as such may be distributed freely so long
as no profit is made, the programs remain unaltered, and this file is
included in all copies.
The copyright remains mine (©David Brain 1993) and I accept no
liability for any damage, loss of profits etc. that may arise from use of
this software.
Instructions
************
This program allows a terminal to run a command line via the serial
port. I have found this to be of particular use for debugging programs,
viewing text files, etc all of which can be done from the desktop but
take up valuable screen space (even in mode 31).
This program only supports 3 wire Xon/Xoff communication at speeds
between 300 and 19200 baud. I have only tested this program on my
A5000/CIT-101 Newbury termial and so I have no idea whether this
program will work on any other platforms (not many people have the
hardware - any feedback would be appreciated!). I have particular
doubts as to whether it will work on machines with the old serial
controller chips.
In this file I will assume that you already know how to set up the
terminal, serial cable etc - if you really get stuck contact me at the
address below and I'll try to help (if I can!).
When the program loads it will place an icon on the icon bar (with a
flashing green light - cute eh?).
The menu items are as follows:-
Info:
*****
Gives info about program.
Set Up...
*********
Selecting this menu item opens the settings window. This should be
fairly self explanatory. It allows you to set the baud rate, parity and bits
to be the same as those of the terminal. It is also possible to set what
type of terminal you are using, the wimp slot the terminal task will run
in, and whether control characters are to be allowed by the terminal
task. Clicking on OK will set these options. Some will only take effect
after the terminal task has been re-started (you will be warned of this).
Commands..
**********
Selecting this menu item open the command window. This has two
icons:-
Start up Command :- this is the command that is issued every time the
terminal task is started.
Drag Command :- this is the command that is executed every time a file
is dragged to the iconbar icon, sensible settings for would be 'type' (the
default) or 'cat'. When a file is dragged to the icon <Command>
<Dragged file name> is executed.
Again Clicking on OK sets these options.
Clicking menu over the command window gives you the option to open the
set up window (see above) or save the settings.
Save
****
This saves the current settings (set from the two above menu items) to a
file that is loaded automatically when the program is loaded.
Pause
*****
This temporarily stops the terminal task - useful if you need the
processing time.
Re-Start
********
Re-Start quits the current terminal task (and hence stops whatever it is
doing), and starts a new one. This is of use if the current task becomes
stuck , or to change some settings (see above).
Quit
****
Quits the application.
The Icon
********
The iconbar icon changes depending on the terminal state. A green
'light' flashing ~1Hz indicates normal operation. If the flashing
becomes eratic it indicates that the applications output buffer is full -
the terminal task will be suspended until the buffer becomes empty
(this is of no real concern to the user - but it's nice to know). When the
pause is selected from the menu the icon's 'screen' will go dark, and a
yellow 'light' will flash at ~1Hz, until pause is de-selected. If the
terminal task fails - ie you quit it from the task manager etc, the Icon
will go completely mad with little red 'lights' and a flashing '!' (oh what
a trivially silly bit of coding). With luck 'Re-Start' from the menu will
get things going again.
As mentioned above dragging a file/directory to the icon can be made
to execute a command on that file/directory.
'Undocumented features'
**********************
1.
Setting the system variable Terminal$Task will replace the command
that is used to start the terminal task, this is primarily intended for use
with Brian Brunswick's !Virtual. ie having
'set Terminal$Task virtual' in !Run will use virtual instead of the
taskwindow module.
2.
NB. this one can cause 'strange' effects.
The program can take two (must be two) command line parameters the
first is the size of the applications internal buffer - this is the buffer
where the output from the task window is placed before it is output to
the serial port (to compensate for the fact that the taskwindow module
may stuff data out faster than the serial port can output it). When this
buffer is full the task is halted until it has been emptied. Hence a large
buffer would mean that the task had to be halted less often.
The second parameter is the maximum number of characters that are
written from the above buffer between polls - the lower this figure the
more "multi-tasking friendly" displaying large pieces of text become.
eg. having :-
Run <TermHost$Dir>.!RunImage 1280 10
gives a 1280 byte buffer with 10 characters per poll (this is the default
if no parameters are given).
It won't accept (most) silly values as parameters.
Where I am
**********
If for any reason you wish to get in touch with me I should be at the
email address below for the next couple of years:-
braindl@sun.aston.ac.uk
History
*******
1.00 5/12/93 - First truly working version.
1.01 6/12/93 - Bug fix on 'first truly working version' + nicer menu:
Test release version.
1.02 5/02/94 - Fixed 'flashing light' bug + minor code improvements.
1.10 21/03/94 - Changed windows to be more Style Guide ish.
Menus altered, and more code improvements.
Things To Do
************
Add support for serial block drivers by Hugo Fiennes.
Perhaps (as it would mean a fairly major re-code) add multiple terminal/
session support.