Xref: utzoo comp.sys.mac.hardware:4170 comp.sys.mac.misc:934 Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!umich!terminator!um.cc.umich.edu!Gavin_Eadie From: Gavin_Eadie@um.cc.umich.edu (Gavin Eadie) Newsgroups: comp.sys.mac.hardware,comp.sys.mac.misc Subject: Re: Anyone seen these keyboard problems ? Message-ID: <1990Jun30.183958.12053@terminator.cc.umich.edu> Date: 30 Jun 90 18:39:58 GMT Sender: usenet@terminator.cc.umich.edu (usenet news) Organization: U of Michigan Information Systems Lines: 25 References:<1990Jun26.193915.18901@calgary.uucp> In article aland@chaos.cs.brandeis.edu (Alan D Danziger) writes: > Well, I've run into about the same problem, duplicated on 2 SE/30's > with extended keyboards... In more than one program, if I'm typing > quickly and type 'o' and another key at more or less the same time, I missed the start of this thread but caught this reply. I too, and two of my colleagues, have been having trouble with keyboard stoppage as we type certain sequences fast. The sequence in particular is "stop" (which is typed a lot into VersaTerm for our mainframe software) and the final "p" sometimes doesn't appear. If you notice, and type "p" again it still doesn't work - you need to type something else to 'unjam' the keyboard. I reported this to Mac Technical Support in April and they suggested VersaTerm might be dicking with the keyboard map, but I doubt it (and so does Synergy - the publishers of VersaTerm). I also have had this happen once in Think C as I was typing "top" (though it's possible VersaTerm was in the Multifinder background at the time - I don't remember). It's easy to type the "op" sequence very fast - the two keys are right next to each other - but I can't get this to happen more than about once a day or two. It's totally real, but elusive. I'd love to find the problem and get a fix ... Gavin Eadie, U of Michigan Information Systems