Thread: 10.5.2
View Single Post
  #18  
Old February 12th, 2008, 09:24 AM
bbloke's Avatar
bbloke bbloke is online now
Registered User
 
Join Date: Jun 2002
Location: UK
Posts: 1,407
Thanks: 0
Thanked 15 Times in 13 Posts
bbloke has a spectacular aura aboutbbloke has a spectacular aura about
Quote:
Originally Posted by CaribbeanOS-X View Post
bbloke: i think i had a similar issue. as i rapidly flip from program to program and arrive at a input field... i quickly enter, say my email... and when i look up the first letter is missing.

...

Is that what your MB PRO is doing? I have a MacBook, 10.4.11, 2 gig RAM etc... the thing preforms like a thoroughbred 99% of the time. However, I built a clean install a few weeks ago and the issue is gone!
Hi CaribbeanOS-X,

Your experience sounds similar to what I have encountered. I bought a MacBook Pro over the summer (running Tiger) and noticed that the first letter would be missing occasionally, right after I started typing. This might be particularly the case when typing in a field when browsing the web, and that sort of thing. I put it down to not having adjusted to a laptop keyboard yet!

I upgraded to Leopard some weeks after it was released and, by that time, I was more convinced it was not the case that I was unfamiliar with the keyboard. The same phenomenon occurred under Leopard. I started looking around on forums, particularly Apple's own discussion pages, and found this is a widespread issue that has been driving people crazy!

The first letter tends to only not appear if they keyboard has been inactive for some time. It doesn't seem to miss random letters or freeze up, and the trackpad is fine. Once I've started typing and don't stop for long periods, the letters seem to show up appropriately. I started to think it is almost as if the keyboard goes to sleep when not used for a bit, and the first key press wakes it! Someone else made a similar comment concerning the USB bus going to sleep, and how it could be overly-aggressive power management. While some had said the problem occurs when using Windows via Boot Camp, more had said that it didn't occur within Windows, so that gave me more hope that it is software-related.

Fingers crossed...
Reply With Quote