Dear CNET members,
Happy Friday the 13th! Before I get into Michael's laptop keyboard that has gone rogue on him ever since he dropped it, I have a couple of quick announcements. First up is the launch of CNET's Toolbar. Right now if you go to any CNET Web pages and look at the bottom of your screen (sorry, this feature is not available to Internet Explorer 6 users) you will see a subtle black bar going across the screen. From this toolbar you can access all the wish, research, and recommendation lists you've created--from using the CNET My List feature, your Download.com Watch lists, and if you are using CNET TechTracker, it will even list all your software updates. Everything from logging in and out to accessing your profile is also incorporated into this too bar--so everything is right at your fingertips. I hope you enjoy using this, and if you have any feedback, you know how to reach me. The second item on my list is the about the Deals and Bargains forum. The holidays are in full swing already. And with budgets being especially tight these days, every dollar we can save helps. So if you run across a great deal online or in your in-box, share it with all of us by posting it in the Deals and Bargains forum. This way all of us can benefit from it. The forum is only as good as the people who participate in it, so start sharing! Thanks all! Now let's see if we can home in on Michael's rogue keyboard issue. Well, Michael, sorry to see you had dropped your laptop. Before we get any further, I hope you have all your important data backed up, just in case something really goes rogue like your hard drive. Reading through all our members' answers to you, I would have to say many suggested that your problem stems from a hardware issue since your keyboard started to act up after the drop--ranging from a keyboard, hard drive, RAM module that has a loose connection to more serious issues as a damaged motherboard. However, we also can't rule out the possibility of other factors such as coincidental malware infection around the same or simply because of intense system resources being used up--best explained by member clap_clap here. I will admit these types of issues are difficult to troubleshoot and narrowing it down can be time consuming and takes some patience. And the only real way is the process of elimination--starting with simple stuff and knocking out the eliminating the possibility one at a time. For instance to see if the physical keyboard is the culprit, a simple yet effect solution was suggested from member wilswong on how to test to see if the physical keyboard is either loose or damaged. There are plenty of other great ideas and suggestions that you can try, and if some of the suggestions are beyond your technical ability, Michael, I would suggest leave it to a professional. I have selected a few suggestions from our members in the Q&A to start from, but there are plenty more member recommendations to read through. Good luck and please come back and follow up to tell us what you discovered and exactly what worked--we are all very curious. Thanks to everyone for your efforts. Have an awesome weekend and take care! Cheers! - Lee
Got suggestions? Send me an e-mail: messageboards@cnet.com |
No comments:
Post a Comment