Columbia Kermit/kermit.zip/archives/win100.zip/winaaahlp.txt

Text File | 1991-10-20 | 6KB | 142 lines

               WINKER READ ME FILE


     Please read this before trying the program or reading any
other documentation.  Some of the items may not be meaningful
now, but it is important for you to have some idea of the file
contents and of any special difficulties you may encounter.


             CONTENTS OF THE RELEASE

Necessary files:

    1.  WINAAA.HLP - This file.

    2.  WINKER.BOO - A Windows terminal emulator for the
Heath/Zenith H/Z19 terminal containing the Kermit file transfer
protocol.  You must convert it to executable format using the
program MSBPCT.EXE or some other equivalent program which can
read a Kermit .BOO file.

    3.  WINKER.DOC - ASCII version of the documentation.

Optional Files:

    1.  WINWRI.BOO - Documentation for the Windows H19 terminal
emulator for use by the Windows WRITE program.  After recovering
the file with MSBPCT.EXE or an equivalent program, load it into
WRITE for reading and/or printing.  The text was formatted
originally for a PCL (Laserjet) printer.  If you have some other
kind of printer, then you may have to reformat and repaginate the
text.

    2.  WINFON.BOO - An optional ASCII font also containing the
original H19 graphics characters which can be loaded with the
Windows control panel and used with the H19 Windows terminal
emulator.  Recover it from its .BOO format using MSBPCT.EXE or an
equivalent program.  Install the font with the Windows control
panel.

    3.  WINH19.TCP - a suggested UNIX TERMCAP file for the
Windows H19 emulator.  Both 24 and 30 line versions are
illustrated for ANSI and HEATH modes.

    4.  WINCAS.BOO, WINPRZ.BOO, WINPRZ.BOO, WINMZE.BOO,
WINESH.BOO - These files draw pretty pictures on your Winh19
screen.  To use them you must: (1) Install the font Winh19.fon;
(2) Recover the files using MSBPCT.EXE or an equivalent program;
(3) Move the resulting .HGR files to your host using Kermit; (4)
Set the emulation to Heath mode; (4) Type the files.

    5.  WINCOM.BOO.  An updated Windows communications driver for
Windows 2.10.  The current driver fails to function correctly
when XON-XOFF flow control is being used.  To install the new
driver: (1) recover the driver from its .BOO format using
MSBPCT.EXE; (2) Locate the Windows distribution disk containing
the comm driver; (3) Using diskcopy, duplicate the disk; (4)
Replace the old driver with the new one; (5) Run Setup and
reinstall Windows in another directory.
     When you are satisfied with the new installation, you can
make it your regular Windows work area.  Or, you can do the
following: In the old directory, backup WIN200.BIN, WIN200.OVL,
and WINOLDAP.GRB.  Copy the new version of these files over the
old ones.  You can then try your old Windows directory with the
new files.  If you are satisfied with the results, you can delete
the old versions of WIN200.* and WINOLDAP.GRB.

Source Files:

    You must have the Windows Software Development Kit as well as
the Version 5.1 C compiler, both from Microsoft, to make the
executable file.  In addition, you must have a copy of WART.EXE
from the C-Kermit distribution or the source files listed in item
7 below.  The make file assumes the existence of the WART
sources.

    1.  Make File - WINKER.MAK

    1.  C Sources - WIN19F.C, WIN19T.C, WINH19.C, WIN19M.C,
WIN19N.C WINKPD.C, WINKPX.C, WINKPN.C

    2.  Header Files - WINASC.H, WINH19.H, WIN19D.H, WINKPF.H,
WINKPR.H.

    3.  Resource Files - WINKER.RC, WINKPM.RC, WIN19B.RC,
WIN19M.RC, WINKPR.RC.

    4.  Linker file - WINKER.LNK.

    5.  Protocol (Wart) file  - WINKPR.W.

    6.  Definition files - WINH19.DEF, WINKPR.DEF.

    7.  Wart preprocessor source files - WINCKW.C, WINCKC.H


                  NOTES

    1.  The Window program contained here REQUIRE Windows version
2.0 or greater, Windows/286, or Windows/386.  Windows 1.0 is
OBSOLETE.  Use your upgrade offer from Microsoft to get the
latest version.

    2.  If you are using the Kermit feature and find that you
cannot even exchange the first packet, then check for a mismatch
between host and emulator parity and word-size settings.  If you
can, use 8-bits and no parity.  Also note that this program has
not been tested in the IBM environment.  Please contact us if you
need help in this area.

    3.  The emulator screen can appear to lock up for two
reasons. The first is when the emulator program receives an XOFF
and no subsequent XON signal.  If you think this is the problem,
go off line and type CTRL-Q and then go back on line.  The second
situation causing the screen to seem to freeze is when you are in
Heath mode and you receive the sequence ESC [.  This can happen
accidentally if you are in HEATH mode and the host thinks that
you are an ANSI or VT100 type terminal.  In this case, the screen
goes into hold screen mode.  Try typing Scroll Lock or Shift
Scroll Lock.  You should see the next line or the next several
lines from the host.  You can free the terminal by going off line
and typing ESC \ from Heath mode or ESC [ > 3 l if in ANSI mode.
(Spaces are shown between characters only for clarity.  Do not
type them.)  Alternatively, try using the 'Reset' menu item.
Correct the emulation mode, if necessary. Then go back on line
and again try typing Scroll Lock once or twice.

    4.  Some keys have no corresponding menu items.  Please read
the program documentation to learn how to use the Scroll Lock,
function key F6, CTRL-BACKSPACE, and CTRL-BREAK.

    5.  Be aware that you can run two instances of the program,
one for each of COM1 and COM2.  This can lead to problems during
file transfers if both are trying to deal with the SAME file at
the same time.  Try to watch out for possible conflicts of this
type.  DOS does not always seem to do the right thing with files
in these situations.

    6.  If you are performing a file transfer to or from a floppy
disk, do NOT change the disk during the transaction.