Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!archimedes.math.uwm.edu!jgreco
From: jgreco@archimedes.math.uwm.edu (Joe Greco)
Newsgroups: comp.sys.cbm
Subject: Re: Kermit 2.2 UppErCAsE PrOLblEM
Message-ID: <3164@uwm.edu>
Date: 30 Mar 90 00:41:35 GMT
References: <6683@ucdavis.ucdavis.edu> <51015@microsoft.UUCP> <3313@trantor.harris-atd.com> <53659@microsoft.UUCP> <3063@uwm.edu> <10378@cbmvax.commodore.com> <3113@uwm.edu> <10407@cbmvax.commodore.com>
Sender: news@uwm.edu
Distribution: na
Lines: 30

In comp.sys.cbm article <10407@cbmvax.commodore.com>, fred@cbmvax (Fred Bowen) wrote:
>>I might point out that the problem in question happens all the time 
>>while in Kermit, and not just while in connect mode.  It merrily uppercases
>>commands on the command line, and magically goes away when I leave 
>>Kermit.  The uppercasing only seems to affect certain letters.  This
>>suggests foul play keyboard scanning in Kermit.
>
>Sorry, I think if you examine which letters are incorrectly cased you will
>find a correspondence with the parity bit.  The shift keys do not occupy
>positions in the key matrix that would cause this sort of problem, even with
>the worst keyscan code AND the longest, noisiest cable imaginable.  You may
>not be connected to a host, but are you still connected to your modem?

Fred, would you please re-read my statement?  If you are in Kermit, type
"^Y c" to break out to the Kermit command line, and type, the problem STILL
occurs.  I am _POSITIVE_ that my keystrokes are not going to the modem;
my Courier has status lights.  It also happens with nothing at all connected
to the User Port, I just booted a machine and tried it.

Now, I'm not interested in explaining this all day.  I can't seem to find a
set-up where this doesn't happen.  So it is very likely that if you pop your
hood, pull your 6581, and boot Kermit that you can try it for yourself.

It's probably a stupid program "bug."


... Joe

P.S. I just checked maxwell.physics.purdue.edu for the source code, I don't
see it.