1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Keyboard numbers shifted?

Discussion in 'PC Hardware' started by CaptEMRG, 2006/08/27.

  1. 2006/08/27
    CaptEMRG

    CaptEMRG Inactive Thread Starter

    Joined:
    2006/08/27
    Messages:
    1
    Likes Received:
    0
    My keyboard numbers have suddenly shifted to the upper values (!@#$%^&*()? Have rebooted, checked keyboard driver? Only on programs on my computer. They are working corectly here (1234567890)
    Weird! Anythoughts.
     
  2. 2006/08/27
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,317
    Likes Received:
    252
    Need to try a different keyboard.
    Also make sure your current one is plugged in all the way.
     

  3. to hide this advert.

  4. 2006/08/27
    BOBBO

    BOBBO Geek Member

    Joined:
    2002/01/07
    Messages:
    1,892
    Likes Received:
    19
    CaptEMRG: Welcome to the BBS!

    If those keys behave themselves here, I'd think that shows the problem isn't with the keyboard itself. What program(s) in your computer does it misbehave with? Just one program? Several?
     
  5. 2006/09/04
    semperdoodle

    semperdoodle Inactive

    Joined:
    2006/09/04
    Messages:
    1
    Likes Received:
    0
    Don't know what it is, but it's contageous!

    Hey Capt. (don't mind if I call you capt. do ya?)

    I'm a self employed PC/Network Technician (Yeah! aren't we all?) Anyway, I'm going to present a case for the idea that it's not a hardware problem, then you tell me if I'm crazy or not. OK? My clientele base within my area of coverage runs just under a hundred (not including one timers). Within the last week I have been contacted by a total of fourteen of those clients all with the identical issue, (basically the keyboard acts as if you have the fn key pressed continuousely while typing) there are an additional six of whom I have not confirmed however from the descripyion they gave me it seems likely. I was just fortunate enough to be presesnt with one of those clients who requested that I reinstall his Windows XP Pro from scratch. After performing a LLF on the drive (more for his peace of mind than anything else) I began his "Clean Install" After the install and configuration I hooked up his DSL in order to download and install an anti-virus program. Within just one or two seconds of being connected I saw a brief flash of what seemed at first a Windows Update screen. Then it all hit the fan. His system appeared to freeze up but his mouse pointer was shaking like it was having a siezure and his HDD LED was blinking at warp speed. I tried Cntrl+Alt+Del to access the Windows Task Manager which finally came up about a minute later. To my amazement there was an unidentified (There is never a pen handy when you need one) process running at a whoping 89% to 100% of CPU usage (No it wasn't System Idle Processes) A second later it blinked out and I suddenly began experiencing the same keyboard issue all over again. Those of you who deal with such things will know that the keyboard has a tendency to act quirky when a remote user logs on to a system where the profile is currently in use. (Can I get an Amen! Moderator?) Anyway, what I believe actually happened was that a remote bot programed to search for available open ports, tcp or udp most likely dropped what is commonly refered to as a payload in a concentrated bust for about ten seconds onto my clients system (this is a bad thing!) If I'm right, the keyboard issue is only a symptom left over from his dastardly deed. The real problem will eventually reveal itself later through a serious drop in your systems performance, followed by application error messages (the "sorry for the inconvenience" type), and eventually resulting in a dreaded BSOD (Blue Screen Of Death). If all of you who are experiencing this issue have any doubts as to whats going on in your system, I suggest you go to Start > Run > cmd> and at the command prompt type sfc /scanonce. Then exit the command window and restart your system. Don't worry, I'm not in to I told you so's. But I'll tell you this much. I've been working as a Tech since 1985, and I promise you this. This is no simple keyboard malfunction.

    email address removed for your security against spam by Moderator
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.