Start a Conversation

Unsolved

This post is more than 5 years old

Closed

1 Message

27532

January 8th, 2004 14:00

Inspiron 8500 prevented from going into standby mode..error message blames device driver for 'Standard 101/102-Key or Microsoft Natural PS/2 Keyboard

The Inspiron 8500 will not go into either standby or hibernate mode.  Error message in full is" The device driver for the 'Standard 101/102 -Key or Microsoft PS/2 Keyboard device is preventing the machine from entering standby.  I have checked the driver... I have tried Microsoft Knowledge Base #814149 where I got a blank screen.  Anybody have an idea?

3.1K Posts

January 8th, 2004 14:00

bobmccune,

Thank you for using the Dell Community Forum.

You should remove all peripherals from the system when placing it into suspend or standby mode.

August 17th, 2009 22:00

Q: Hello, I’m running Windows XP on a Gateway laptop and when the computer tries to enter standby mode I get the following error: The device driver for the “Standard 101/102-Key or Microsoft Natural PS/2 Keyboard” device is preventing the machine from entering standby. Please close all applications and try again. If the problem persists, you may need to update this driver.” I’ve tried updating the driver, uninstalling it, and reinstalling it. Nothing works. What I have noticed though is that it started when I added Adobe PhotoDeluxe Home Edition 3.0 to my computer and when I uninstall that software the error doesn’t appear. I’ve tried uninstalling and reinstalling the Adobe software several times and each time the error returns. I have an HP Printer/Scanner/Copier that seems to prefer the Adobe Software for the scanning component as what came with it yet it doesn’t seem to be compatible with my laptop. Do you have any suggestions?? A: A quick search using Google reveals that Microsoft is aware of your issue. See the Microsoft article entitled “Device Driver for the Standard 101/102-Key or Microsoft Natural PS/2 Keyboard” Error Message When You Try to Enter Standby for more information. The basic idea of the article is that the Adobe Type Manager (ATM) sometimes conflicts with the standby function in Windows XP. Microsoft’s solution to the problem is to uninstall the ATM. So it seems reasonable that PhotoDeluxe is indeed the source of your standby problems. According to a post in the notebookreview.com forums called Standby Fails on closing the lid –says keyboard driver problem, the solution to your problem is: 1. Uninstall PhotoDeluxe. 2. (I would suggest restarting your computer) 3. Perform a customized reinstall of PhotoDeluxe without the ATM. 4. (I would restart again.) Your computer should now go into standby mode normally. You might want to look at some of the other posts regarding Adobe PhotoDeluxe here at Ask A Geek. You might also want to consider replacing PhotoDeluxe with its successor, Adobe Photoshop Elements. Many of the features found in PhotoDeluxe still exist in Photoshop Elements.

August 17th, 2009 23:00

Would you believe the problem is NOT the keyboard driver, as the error message suggests?

This is actually a known issue with Windows Operating Systems and it's incompatability with Adobe software.  Usually the offender is Adobe Type Manager.  Microsoft suggests uninstalling it.

See:   http://support.microsoft.com/kb/814149

see  http://support.microsoft.com/kb/314118

pay particlular attention to the part that says:

This behavior can also occur if a program installs a kernel-mode driver that attaches itself to the standard keyboard driver (I8042prt.sys) and does not support Plug and Play I/O request packets (IRPs). Examples of programs that exhibit this behavior include:

  • Pgpdisk version 6.02 and 6.5 (installs Pgpmemlock.sys and Pgpdisk.sys drivers)
  • Adobe Type Manager version 4.0 (installs the Atmhelpr.sys driver)

I solved the problem by finding ATMHLPR.EXE in windows/system32/drivers folder, and renaming it to "a_possibly_faulty_ATMHLPR.EXE" (in order to find the driver again should it reinstall itself, and I need this old mucked up one again).

I then rebooted, and the problem was SOLVED.

No Events found!

Top