Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!uunet!microsoft!kentsu
From: kentsu@microsoft.UUCP (Kent Sullivan)
Newsgroups: comp.sys.cbm
Subject: Re: C128-D
Message-ID: <9147@microsoft.UUCP>
Date: 24 Nov 89 01:05:24 GMT
References: <1989Nov20.194237.5236@ug.cs.dal.ca>
Reply-To: kentsu@microsoft.UUCP (Kent Sullivan)
Distribution: na
Organization: Microsoft Corp., Redmond WA
Lines: 32

In article <1989Nov20.194237.5236@ug.cs.dal.ca> lee@ug.cs.dal.ca (Michael l) writes:
>
>
>    Has anyone else with a C128-D noticed that while using Kermit
>with the screen driver set in the 128-80 columns mode that certain
>keys will not respond in the terminal mode.  For example the keys 
>a,d,g do not respond , instead ^A,^D,^G is sometimes printed
>( the keys respond correctly if I am using the C64 80-columns 
>mode).  I'd like to use C128-80 columns since the characters look 
>better.
>
>    Could it be a problem with my specific computer (I don't
>know anyone else with a 128D)?  Or could it be a bug with Kermit
>using the 128D environment?

As far as Ray and I have been able to determine, this is *not* a bug in
Kermit.  Kermit has been tested on a wide variety of C-128s and C-128Ds
(I have a C-128D myself).

Rather, the behavior you describe seems to occur only when a 1351 mouse
is plugged in.  Solution: unplug the mouse.  It seems that the micro-
processor inside the mouse is continually spewing out data, and this
confuses the custom keyboard scan routine in Kermit.

Please contact either Ray (ray@maxwell.physics.purdue.edu) or me if
this does not solve the problems you are having.

Kent Sullivan (author of the Kermit v2.1/2.2 manual)
Microsoft Corporation

The opinions expressed in this article are my own and do not necessarily
reflect those of my employer.