Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!cica!iuvax!rutgers!cbmvax!fred
From: fred@cbmvax.commodore.com (Fred Bowen)
Newsgroups: comp.sys.cbm
Subject: Re: Kermit 2.2 UppErCAsE PrOLblEM
Message-ID: <10377@cbmvax.commodore.com>
Date: 27 Mar 90 15:54:21 GMT
References: <6683@ucdavis.ucdavis.edu> <51015@microsoft.UUCP> <3313@trantor.harris-atd.com> <53659@microsoft.UUCP>
Reply-To: fred@cbmvax (Fred Bowen)
Distribution: na
Organization: Commodore, West Chester, PA
Lines: 28

In article <53659@microsoft.UUCP> kentsu@microsoft.UUCP (Kent SULLIVAN) writes:
>Regarding the uppercase problems a few people have been having with
>Kermit v2.2, our best guess is that it is related to the keyboard scanner
>routine problems that were discussed here previously.  In sum, Kermit is more
>sensitive to the chips that handle keyboard input than most programs.

The only times I have seen this happen is when you setup your terminal for
an 8-bit word length and the host is 7-bit, or parity is incorrectly set.

An rs232 byte is transmitted as follows:

	start bit,  B0, B1, ... Bn,  parity bit, stop bit(s)

If your setup is incorrect, the parity or stop bit might be misinterpreted
by the system as the most significant data bit, which would cause the rather
screwy upper/lowercase problem.

While I did report a problem with Kermit's C128 keyscanner, it would not
cause a problem like this (it caused "dead" keys in one particular row
containing the A,D,G, etc. keys).
--

-- 
Fred Bowen			uucp:	{uunet|rutgers|pyramid}!cbmvax!fred
				domain:	fred@cbmvax.commodore.com
				tele:	215 431-9100

Commodore Electronics, Ltd.,  1200 Wilson Drive,  West Chester,  PA,  19380