HYTELNET for WINDOWS

This program provides a Windows interface for the Hytelnet system
of Internet sources. THE HYTELNET FILES THEMSELVES ARE NOT
PROVIDED WITH THIS INTERFACE.  They must be downloaded separately
and installed in their own directory. 

This interface uses a button bar to move through the files, or
you can double-click on a Hytelnet "link", such as <US001>, to
bring up the next screen.  Other features include:

   .  Direct connection to sources by double-clicking on the word
"telnet".

   .  Ability to edit and save text of any file and create new
files while in Hytelnet.


INSTALLING HYTELNET FOR WINDOWS

After unzipping these files, run the program called SETUP.EXE
from Windows (double-click on SETUP.EXE from Windows File
Manager).  This installs Hytelnet for Windows; when it prompts
you for the directory, specify the directory that contains your
Hytelnet files (not included).  The setup program will create a
new program item within Windows.  In order to run the setup and
use this program, you MUST have the file VBRUN300.DLL already in
your Windows System directory.  VBRUN300.DLL is commonly
available in forums and on bulletin boards; since it is a large
program (some 300K) I did not include it so as to save the
download time for people who already had it. All Visual Basic
programs use this file.


USING HYTELNET FOR WINDOWS

     1. Start your Windows communication program.

     2. Connect to your Internet provider and go to where it
expects to receive Telnet commands.

     3. Start Hytelnet for Windows.


CONNECTING TO TELNET ADDRESSES

Once you reach a screen that has an Internet address on it, you
connect to it by double-clicking on the word "telnet" (or
"tn3270").  The program then will switch to your terminal program
(which must be running at the same time) and issue the
appropriate command.  If there is a login: value specified, you
can (optionally) retrieve the login from the clipboard with paste
(Alt-E, P in Windows Terminal).



OTHER FILES

Hytelnet for Windows uses a file called HELP.TX1 that it expects
to be in the same directory as your initial start.txt files; it
is a help file that you can access with the Help menu item or
with the F1 key and explains the operation of the program and all
the various options.

The program also checks for a file called SETTINGS.DAT in your
start-up directory.  This file contains all the settings you have
chosen and is created whenever you exit Hytelnet for Windows. 
You don't need a settings file.

The only really critical setting is specifying the name of a
terminal program, which you will be asked to provide when you
first try to connect; you can also set it under the Options menu.
You must use the EXACT application name as it appears in the
Windows task list (Alt-TAB), e.g. "Terminal - DELPHI.TRM", not
just "Terminal" (if that is the way it appears).  Otherwise,
Hytelnet for Windows will not be able to switch to the terminal
program and issue the connect command. While case is not
important, spacing and punctuation are critical; beware
hard-to-see spaces surrounding hyphens, as in "SMARTCOMM -
DELPHI.SCM". I could not find a foolproof way for the program to
automatically detect what terminal program you are using, so this
manual entry is necessary. I have tested the program with Windows
Terminal, ProComm, COMIT, and with the terminal component of
pfs:WindowWorks.   

Your terminal program must be up and running; otherwise you
cannot connect.  If you try to connect without your terminal
program running, you will be given an opportunity to exit to
Program Manager so you can start it.  Hytelnet for Windows will
remain active.

Some communications programs, notably ProComm, rename themselves
when they are minimized (shrunk to an icon).  This poses a
problem if you try to switch to the program while it is
minimized: Hytelnet for Windows will try to switch to it under
its original name.  Other communication software can be minimized
and then restarted because they keep the same name.


CHANGING THE PROGRAM ITEM

You can edit the program item with the Properties option under
the Program Manager File menu. On the command line, you can give
the program the name of a start-up file other than the one
installed (which is called NEWSTART.TXT).  If no start-up file
appears on the command line, the program looks for a file called
START.TXT.  The working directory should be where your Hytelnet
files are and where the HELP.TX1 and SETTINGS.DAT files are
located. If the program can't find a start-up file, it will
prompt you to open one; however, the help and settings
information may not be loaded if you start up with an incorrect
directory.


SYSTEM-SPECIFIC PROBLEMS

The screen colors that are available will be limited by the type
of graphics card and Windows drivers you have installed.  Also,
printing the screen using fonts will generate an error if your
printer cannot print the screen font.  Using a True-type screen
font should solve this, or you can print without using the screen
fonts (Options menu).

If the program cannot find a file, it issues an error message. 
It first looks for the file in the current directory. If it is
not found it looks in a subdirectory specified by the first three
characters of the file name (this is the Hytelnet subdirectory
structure).  Then if it still can't find it, it issues the error
message.


ABOUT THIS PROGRAM

This program was written in Visual Basic by Bruce Clouette
(clouette@delphi.com or 71053.1652@compuserve.com).  Please send
your comments and suggestions for revisions and enhancements.  

There is no charge for this Windows Hytelnet reader (nor is there
any warranty, stated or implied).  However, please support the
ongoing development of Hytelnet.  The author, Peter Scott, asks
$20 to cover his costs and time. Contact him by E-Mail at

    aa375@freenet.carleton.ca

or by regular mail at:

    Peter Scott
    324 8th Street East, 
    Saskatoon, Sask, Canada, S7H0P5
