djo7613@hardy.u.washington.edu (Dick O'Connor) (08/27/90)
I recently sent a note to Christine Gianone at Columbia University concerning
some things I've noticed in my early dealings with Z100 Kermit Version 3 that
some of you may be interested in. If anyone has any further reports along
this line, please post them!! And join me in a rousing chorus of
VT-100 for Z-100 Now!
VT-100 for Z-100 Now! :)
"Moby" Dick O'Connor djo7613@u.washington.edu
Washington Department of Fisheries *I brake for salmonids*
-----note follows------------
Christine:
I've worked with Kermit version 3.0 for the Z-100 for a few days, and I
have some initial comments that you may to archive or pass on to the person
who worked on it.
First, I hope the tireless individual who put out this version, to whom
great thanks are owed, can contact Drew Derbyshire, who did a lot of work
on the Z100 version up to 2.32A (which may not have been an official release)
to compare notes. Drew was looking into VT100 support, which is really all
that this version is missing, and perhaps the two of them can put it together
with a little brainstorming. I think I have his latest email address, if
you or Joe Doupnik don't have it handy.
1) It appears that this version reports different key scan codes for the Z100
keyboard, which breaks all initialization files with SET KEY commands.
ZKerm 3.0 reports F0 as \406, and I believe the correct code is \150.
2) I use Kermit over a serial line to a multiplexor which needs a triple-
BREAK sequence to disconnect from whichever target machine I've been
working on. Once kermit is placed in connect mode, a <RETURN> is all the
mux needs to begin querying me for "Destination:". This version seems to
require sending a BREAK down the line each time I want response from the
mux, as if the serial port needed to be "cleared" for some reason.
3) I've noticed some odd delays and sporadic lost characters on
transmission of full screens of data. This doesn't happen with Drew's
version 2.32A, which I currently use, and I'm not sure if there's
something I do that causes this. I do set CTTY ANSI so I can use ANSI
color sequences in my DOS prompt and in other programs, but I'm using
the ANSI driver that comes with Z-100 MS-DOS version 3.1 (the "standard"
one). I can experiment with this some more if necessary.
Anyway, I'm glad to see a new version of Z100 Kermit for all of us
fanatics who just can't give up these beasts! I hope the comments are
helpful.
"Moby" Dick O'Connor djo7613@u.washington.edu
Washington Department of Fisheries *I brake for salmonids*
"Moby" Dick O'Connor djo7613@u.washington.edu
Washington Department of Fisheries *I brake for salmonids*