H134338 - Mouse Fails Exiting Power Management in Windows 3.x SYMPTOM: IBM PC 300 Series 6576 and 6586 systems preloaded with DOS & Windows 3.x may exhibit a mouse lockup after recovering from APM (Advanced Power Management) mode if either of the following conditions are met: 1) The SYSTEM.INI file in the WINDOWS directory executes the following two mouse drivers that do not re-initialize the mouse after APM has been active for at least 20 minutes: LVMD.386 size=9,688 bytes, date=12/31/93 LMOUSE.DRV size=12,346 bytes, date=12/31/93 2) If Lotus SmartSuite is installed, the following statement may be deleted from the WIN.INI file: "LOAD=C:\WINDOWS\NWAPM.EXE" When the system tries to recover from Suspend mode, the mouse locks up because the APM driver was never loaded in the WIN.INI file. PROBLEM ISOLATION AIDS: This failure only affects the Windows 3.x environment. When this failure occurs, the system continues to function without the mouse. FIX: Mouse Lockup caused by symptom #1: The mouse drivers stated above in the SYMPTOM section are inappropriate for use with the APM feature. The following two drivers will function normally after recovering from APM mode: LVMD.386 size=10,238 bytes, date=7/8/93 LMOUSE.DRV size=32,208 bytes, date=7/8/93 There are 2 sets of the drivers included with the preloaded software on the PC 300 6576/6586 system. They are located in different directories and can be identified by the file size and date. Edit the SYSTEM.INI file and verify that the following two entries are pointing to the directory that contain the appropriate mouse drivers listed above: SYSTEM.INI entries - MOUSE=C:\Mouse Directory\LVMD.386 MOUSE.DRV=C:\Mouse Directory\LMOUSE.DRV Mouse Lockup caused by symptom #2: Edit the WIN.INI file and add the following statement after the "SPOOLER=YES" statement: LOAD=C:\WINDOWS\NWAPM.EXE If mouse lockups persists, continue normal problem determination to isolate the failing application or FRU. Windows is a trademark of the Microsoft Corporation.