X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=3.1 required=5.0	tests=BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,FREEMAIL_REPLYTO,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Reply-To: leonius AT inbox DOT ru
Date: Thu, 11 Nov 2010 21:04:37 +0300
Message-ID: <AANLkTikBaKhEQfE4GB6kLUUTNwXxrgHrwS70LfaHrcdR@mail.gmail.com>
Subject: Re: Typing trouble?
From: Leonid Sadikov <leoniusleonius AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> At 10:24 AM 12/13/2000, Richard Dixon wrote:
>
> >Dear All,
> >
> >A novice's question here - just got Cygwin running using an older version
> >(a 10MB-or-so executable containing all the relevant files).
> >
> >It seems to be OK in terms of running but when typing in the bash shell,
> >there are lots of beeps and any letters I type often delete the previous
> >letter or shift the last letter written along one - e.g. typing abcdef
> >might come up as abcdfe (and no I've typed this in very slowly so it's not
> >me!) - and it's very infuriating.
> >
> >Just wondered if anyone else has had this peculiar trouble and whether
> >there was any sort of patch released that might cure it.
> >
> >Many thanks in advance,
> >Richard (rdixon AT met DOT rdg DOT ac DOT uk)
> >
> >
>
>
> If the package you got contains a cygwin1.dll, try removing it in favor of
> the current one (which you can download from www.cygwin.com if you don't
> have it already).  If it contains a cygwinb19.dll, remove it and try copying
> the latest cygwin1.dll to cygwinb19.dll.  As I recall, the current DLL is
> binary compatible with B20 and B19, so these procedures should "upgrade"
> you directly.  If you have some release before B19, your only option is
> to rebuild with the latest and greatest.  Of course, this is an option even
> if you have something working with B19 or later!;-)

Have encountered same behaviour with todays version of Cygwin on OS Windows 7.
( Firstly i was disappointed and wanted to throw Cygwin away. )
Solved by Windows reboot.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple