<!-- HTML document saved from Computer Concepts' Impression -->
<!-- using ben's HTML saver (c) Ben Summers 1995 -->
<!-- for more info, email ben@cconcepts.co.uk -->
<!-- Exported from document 'Streamer' -->
<title>Streamer User Guide - Introduction</title>
</head>
<body>
<h2><a name = "intro">Introduction</a></h2>
<ul>
<li><a href = "#intro">What is Streamer?</a>
<li><a href = "#features">Features</a>
<li><a href = "#startup">Start up</a>
<li><a href = "#strwind">Streamer windows</a>
<ul>
<li><a href = "#tncwind">tnc stream windows</a>
<li><a href = "#nvwind">new view windows</a>
<li><a href = "#duwind">dump stream window</a>
<li><a href = "#logwind">logger window</a>
<li><a href = "#sfiwind">Streamer file views</a>
</ul>
<h2><a name = "intro">What is Streamer?</a></h2>
Streamer is a packet radio tnc (terminal node controller) terminal program. The task of the program is to
control the flow of data between the computer and the tnc. User input is taken from the keyboard, and text generated by the tnc is displayed on the VDU. This is a description of a simple terminal emulation. Such a
program is not able to make convenient use of the more sophisticated facilities offered by most tnc's. The
foremost of these is the ability to connect to more than one station at a time, on different streams. It is
possible to use more than one stream with a simple terminal program, but the display soon becomes
cluttered. Streamer uses the stream switching facilities of the tnc to direct input and output from and to
separate stream windows, greatly enhancing the interface between user and tnc.<p>
<h2><a name = "features">Features</a></h2>
<ul>
<li>Fully multitasking
<li>Multiple streams, each with its own window
<li>More than one view of each window possible
<li>Scroll-back limited only by memory
<li>User control of colours
<li>Automatic highlighting of words
<li>TX and RX text distinguished by colour
<li>Up to 32 upload buffers with queued uploading
<li>Automatic log keeping
<li>Monitored text sent to a separate window whilst connected
<li>Special file format which can be viewed from Streamer, with TX and RX portions still distinct
<li>Stream text can be saved to a file, spooled as data arrives (intelligent buffering system) or a selection
can be saved
<li>Streams are tnc mode-aware – no need to manually switch between command and converse modes
<li>Cooperates with other users of the serial port
<li>Uses block drivers</ul>
<h2><a name = "startup">Start up</a></h2>
Run Streamer by double-clicking the !Streamer icon. The Streamer icon should now appear on the iconbar.
If the icon is greyed-out it means that another task is using the serial port, and will not relinquish it.
Streamer will attempt to claim the port if its icon is clicked with adjust.<p>
Depending on the stored configuration one or more stream windows might have appeared at this stage. Any
active windows may be opened from the iconbar menu. Click the middle mouse button over the iconbar
icon and click on the entry for the stream you want in the Open submenu.<p>
<h2><a name = "strwind">Streamer windows</a></h2>
<h3><a name = "tncwind">tnc stream windows</a></h3>
<a href = "sprites/big.gif">Click here for a sprite of a Streamer stream window and logger window</a><p>
There are several types of Streamer window. The tnc stream windows are your means of communicating
with the tnc. Depending upon the terminal setup, there might be just one available stream (single stream
operation) or several (multiple stream operation). Clicking with select on the iconbar icon will display the
next stream out of those not already shown, or you can select one from the iconbar menu.<p>
Tnc stream windows have two parts – an input (TX) and an output (RX) area. Text entered in the input area
is sent to the tnc when the return key is pressed. Text from the tnc is displayed in the output area.<p>
<h3><a name = "nvwind">new view windows</a></h3>
New views of any window can be created from the new view option on the stream window menu. These
have no input area. All user input must be provided in the input area of the parent window.<p>
<h3><a name = "duwind">dump stream window</a></h3>
Depending upon the terminal switching mode in use there can be a separate stream window for dumped
data. In RXBlock mode, data other than received text are sent to the dump stream rather than a connected
stream in converse or transparent mode. Thus you can set your tnc to monitor the channel even whilst
connected (<code>mcon on</code>). Monitored packets will be displayed in the dump window.<p>
<h3><a name = "logwind">logger window</a></h3>
Streamer provides a log keeping facility. When operational (see logger setup) log entries are displayed in the
log window. This has no input area. All input is provided by Streamer itself.<p>
<h3><a name = "sfiwind">Streamer file views</a></h3>
Data received/sent by Streamer may be saved as Streamer files. These contain extra information, such as
whether text is received or sent, and will not display correctly in a normal editor. However, Streamer files
can be viewed with Streamer. Simply drag the file's icon onto Streamer or double click on it. The file's
contents are displayed in a Streamer window with no input area – you cannot change the text in a Streamer
file view window.<p>
<a href = "../Manl_html">Back to contents page</a>
