If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
LMOUSE boot problem
When I boot my machine, I get the message "While initializing device
LMOUSE:" on an otherwise blank screen and the machine just hangs there. Booting up in safe mode works and everything seems fine. Any hints would be very gratefully received. Here's what I've done so far after searching the discussion groups: 1. I ran msconfig and unchecked anything to do with lmouse. No joy. 2. I ran sysedit and put a ';' in from of the line with lmouse. No joy. 3. I removed the lmouse.vxd and lmouse.drv files from WINDOWS/SYSTEM. Change - it now complains that it can't find the files and I need to reinstall them. I do so from the CABs. No joy. 4. I booted in step by step mode and said no to the step which wanted to handle the lmouse. At the end of the process the computer simply rebooted itself. No error message, just sudden reboot. More information: I have tried a different mouse. No change. I do not have a Logitech mouse. I am using the mouse that came with the computer: Intellimouse 1.1a. I don't think we've had a Logitech mouse. The other mouse we used for a while was an InterAct 2-button mouse. There is no program to remove in the Add/Remove program utility that appears to have anything to do with the Logitech stuff. I have not updated/changed the system in the last few months. Running Windows 98 on a Micron Millennia. Thanks, Steve |
#2
|
|||
|
|||
LMOUSE boot problem
Boot into Safe Mode and in Device Manager, remove ALL 'mice and pointing
devices'. Reboot and let Windows re-detect and install the drivers. Mart wrote in message oups.com... When I boot my machine, I get the message "While initializing device LMOUSE:" on an otherwise blank screen and the machine just hangs there. Booting up in safe mode works and everything seems fine. Any hints would be very gratefully received. Here's what I've done so far after searching the discussion groups: 1. I ran msconfig and unchecked anything to do with lmouse. No joy. 2. I ran sysedit and put a ';' in from of the line with lmouse. No joy. 3. I removed the lmouse.vxd and lmouse.drv files from WINDOWS/SYSTEM. Change - it now complains that it can't find the files and I need to reinstall them. I do so from the CABs. No joy. 4. I booted in step by step mode and said no to the step which wanted to handle the lmouse. At the end of the process the computer simply rebooted itself. No error message, just sudden reboot. More information: I have tried a different mouse. No change. I do not have a Logitech mouse. I am using the mouse that came with the computer: Intellimouse 1.1a. I don't think we've had a Logitech mouse. The other mouse we used for a while was an InterAct 2-button mouse. There is no program to remove in the Add/Remove program utility that appears to have anything to do with the Logitech stuff. I have not updated/changed the system in the last few months. Running Windows 98 on a Micron Millennia. Thanks, Steve |
#3
|
|||
|
|||
LMOUSE boot problem
Exactly what entries pertaining to Logitech mice were in msconfig Startup tab?
Click StartRun, type MSINFO32 and click OK. In the left pane of the System Information window, click the + sign to expand the "Software Environment" category. In the left pane, click to select "Startup Programs"....they will appear in a list on the right. Press Ctrl-A on the keyboard, which will highlight everything in the list on the right. Press Ctrl-C to copy the list to the 'clipboard'. Open a reply to this message, click in the body of the message and press Ctrl-V to paste the list from the clipboard to the message, and post back to this thread. The files involved in loading a Logitech mouse are usually lmouse.drv, lmouse.vxd and lmul.vxd Look in this registry key for sub-keys named lmouse and lmul: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD Export the entire key to a text file for backup (Registry menu Export), then delete the lmouse and lmul sub-keys, if found. This should stop the drivers from being called at boot. -- Glen Ventura, MS MVP Shell/User, A+ http://dts-l.org/goodpost.htm wrote in message oups.com... When I boot my machine, I get the message "While initializing device LMOUSE:" on an otherwise blank screen and the machine just hangs there. Booting up in safe mode works and everything seems fine. Any hints would be very gratefully received. Here's what I've done so far after searching the discussion groups: 1. I ran msconfig and unchecked anything to do with lmouse. No joy. 2. I ran sysedit and put a ';' in from of the line with lmouse. No joy. 3. I removed the lmouse.vxd and lmouse.drv files from WINDOWS/SYSTEM. Change - it now complains that it can't find the files and I need to reinstall them. I do so from the CABs. No joy. 4. I booted in step by step mode and said no to the step which wanted to handle the lmouse. At the end of the process the computer simply rebooted itself. No error message, just sudden reboot. More information: I have tried a different mouse. No change. I do not have a Logitech mouse. I am using the mouse that came with the computer: Intellimouse 1.1a. I don't think we've had a Logitech mouse. The other mouse we used for a while was an InterAct 2-button mouse. There is no program to remove in the Add/Remove program utility that appears to have anything to do with the Logitech stuff. I have not updated/changed the system in the last few months. Running Windows 98 on a Micron Millennia. Thanks, Steve |
#4
|
|||
|
|||
LMOUSE boot problem
Mart:
This was one of the things I had already done. Sorry - I don't think it made it into my original list. Thanks, Steve Mart (NoSpam) wrote: Boot into Safe Mode and in Device Manager, remove ALL 'mice and pointing devices'. Reboot and let Windows re-detect and install the drivers. Mart |
#5
|
|||
|
|||
LMOUSE boot problem
Glen:
I did not realize that lmul was part of the logictech mouse stuff. I'll try this out when I get home tonight and I'll post back. Thanks, Steve |
#6
|
|||
|
|||
LMOUSE boot problem
Glen:
Sorry I took so long to reply - I had to work tonight... Anyway, let me bring you up to date. I did the MSINFO thing and didn't see anything interesting. I've pasted it at the bottom of this post. So then I did the regedit thing and removed two items - lmouse and lmul. And then restarted. Boy things changed! When it rebooted it complained that it couldn't find the files for the mouse and it wanted the Windows98 CD. So I put in the CD but it couldn't find the files it wanted. So I guided it to where the CAB files are (I had to move them as I was out of space on my C drive) and it loaded the mouse drivers and continued booting and then restarted and went back to safe mode. Sad. So I started poking around and it looks like the msmouse driver is now loaded and good to go. So I tried the mode where you boot with confirmation of each step. It seems the last step before going off to never never land and rebooting is SSIACT.386. So, on a whim, I said yes to everything else and then no to this last step and, wonder of wonders, I boot almost normally. I say almost because it's really, really slow. But here I am in my normal environment. So now the question is what is SSIACT.386 and what do I do about this? There is an entry in the System.ini in the [386Enh] that says device=SSIACT.386. I'll try checking for viruses and bots. Otherwise I'm still at a loss. Thanks, Steve EPSON Background Monitor Startup Group "C:\Program Files\Common Files\EPSON\EBAPI\Stms.exe" ScanRegistry Registry (Machine Run) c:\windows\scanregw.exe /autorun TaskMonitor Registry (Machine Run) c:\windows\taskmon.exe SystemTray Registry (Machine Run) SysTray.Exe POINTER Registry (Machine Run) C:\PROGRA~1\MICROS~3\point32.exe TCASUTIEXE Registry (Machine Run) TCAUDIAG.EXE -off LexStart Registry (Machine Run) Lexstart.exe LexmarkPrinTray Registry (Machine Run) PrinTray.exe LoadPowerProfile Registry (Machine Run) Rundll32.exe powrprof.dll,LoadCurrentPwrScheme CriticalUpdate Registry (Machine Run) c:\windows\SYSTEM\wucrtupd.exe -startup Iomega Startup Options Registry (Machine Run) C:\Program Files\Iomega\Common\ImgStart.exe Iomega Drive Icons Registry (Machine Run) C:\Program Files\Iomega\DriveIcons\ImgIcon.exe QuickTime Task Registry (Machine Run) "C:\WINDOWS\SYSTEM\QTTASK.EXE" -atboottime TIPS Registry (Machine Run) C:\PROGRA~1\MICROS~3\tips\mouse\tips.exe Zone Labs Client Registry (Machine Run) D:\Program Files\Zone Labs\ZoneAlarm\zlclient.exe AVG7_CC Registry (Machine Run) C:\PROGRA~1\GRISOFT\AVGFRE~1\AVGCC.EXE /STARTUP AVG7_EMC Registry (Machine Run) C:\PROGRA~1\GRISOFT\AVGFRE~1\AVGEMC.EXE AVG7_AMSVR Registry (Machine Run) C:\PROGRA~1\GRISOFT\AVGFRE~1\AVGAMSVR.EXE EncMonitor Registry (Machine Service) C:\Program Files\Encompass\Monitor.exe dRMON SmartAgent Registry (Machine Service) drmon\SmartAgt\SmartAgt.exe LoadPowerProfile Registry (Machine Service) Rundll32.exe powrprof.dll,LoadCurrentPwrScheme MiniLog Registry (Machine Service) C:\WINDOWS\SYSTEM\ZONELABS\MINILOG.EXE -service SchedulingAgent Registry (Machine Service) mstask.exe CVPND Registry (Machine Service) "C:\Program Files\Cisco Systems\VPN Client\cvpnd.exe" start TrueVector Registry (Machine Service) C:\WINDOWS\SYSTEM\ZONELABS\VSMON.EXE -service KB891711 Registry (Machine Service) c:\windows\SYSTEM\KB891711\KB891711.EXE |
#7
|
|||
|
|||
LMOUSE boot problem
SSIACT.386
Try this link for info. http://www.tradestation2000i.com/sea...DocumentID=608 Hope this helps? " wrote: Glen: Sorry I took so long to reply - I had to work tonight... Anyway, let me bring you up to date. I did the MSINFO thing and didn't see anything interesting. I've pasted it at the bottom of this post. So then I did the regedit thing and removed two items - lmouse and lmul. And then restarted. Boy things changed! When it rebooted it complained that it couldn't find the files for the mouse and it wanted the Windows98 CD. So I put in the CD but it couldn't find the files it wanted. So I guided it to where the CAB files are (I had to move them as I was out of space on my C drive) and it loaded the mouse drivers and continued booting and then restarted and went back to safe mode. Sad. So I started poking around and it looks like the msmouse driver is now loaded and good to go. So I tried the mode where you boot with confirmation of each step. It seems the last step before going off to never never land and rebooting is SSIACT.386. So, on a whim, I said yes to everything else and then no to this last step and, wonder of wonders, I boot almost normally. I say almost because it's really, really slow. But here I am in my normal environment. So now the question is what is SSIACT.386 and what do I do about this? There is an entry in the System.ini in the [386Enh] that says device=SSIACT.386. I'll try checking for viruses and bots. Otherwise I'm still at a loss. Thanks, Steve EPSON Background Monitor Startup Group "C:\Program Files\Common Files\EPSON\EBAPI\Stms.exe" ScanRegistry Registry (Machine Run) c:\windows\scanregw.exe /autorun TaskMonitor Registry (Machine Run) c:\windows\taskmon.exe SystemTray Registry (Machine Run) SysTray.Exe POINTER Registry (Machine Run) C:\PROGRA~1\MICROS~3\point32.exe TCASUTIEXE Registry (Machine Run) TCAUDIAG.EXE -off LexStart Registry (Machine Run) Lexstart.exe LexmarkPrinTray Registry (Machine Run) PrinTray.exe LoadPowerProfile Registry (Machine Run) Rundll32.exe powrprof.dll,LoadCurrentPwrScheme CriticalUpdate Registry (Machine Run) c:\windows\SYSTEM\wucrtupd.exe -startup Iomega Startup Options Registry (Machine Run) C:\Program Files\Iomega\Common\ImgStart.exe Iomega Drive Icons Registry (Machine Run) C:\Program Files\Iomega\DriveIcons\ImgIcon.exe QuickTime Task Registry (Machine Run) "C:\WINDOWS\SYSTEM\QTTASK.EXE" -atboottime TIPS Registry (Machine Run) C:\PROGRA~1\MICROS~3\tips\mouse\tips.exe Zone Labs Client Registry (Machine Run) D:\Program Files\Zone Labs\ZoneAlarm\zlclient.exe AVG7_CC Registry (Machine Run) C:\PROGRA~1\GRISOFT\AVGFRE~1\AVGCC.EXE /STARTUP AVG7_EMC Registry (Machine Run) C:\PROGRA~1\GRISOFT\AVGFRE~1\AVGEMC.EXE AVG7_AMSVR Registry (Machine Run) C:\PROGRA~1\GRISOFT\AVGFRE~1\AVGAMSVR.EXE EncMonitor Registry (Machine Service) C:\Program Files\Encompass\Monitor.exe dRMON SmartAgent Registry (Machine Service) drmon\SmartAgt\SmartAgt.exe LoadPowerProfile Registry (Machine Service) Rundll32.exe powrprof.dll,LoadCurrentPwrScheme MiniLog Registry (Machine Service) C:\WINDOWS\SYSTEM\ZONELABS\MINILOG.EXE -service SchedulingAgent Registry (Machine Service) mstask.exe CVPND Registry (Machine Service) "C:\Program Files\Cisco Systems\VPN Client\cvpnd.exe" start TrueVector Registry (Machine Service) C:\WINDOWS\SYSTEM\ZONELABS\VSMON.EXE -service KB891711 Registry (Machine Service) c:\windows\SYSTEM\KB891711\KB891711.EXE |
#8
|
|||
|
|||
LMOUSE boot problem
No, that didn't help. It mentions this item but not what it is or how
to deal with it. Thanks anyway. Steve poatt wrote: SSIACT.386 Try this link for info. http://www.tradestation2000i.com/sea...DocumentID=608 Hope this helps? |
#9
|
|||
|
|||
LMOUSE boot problem
If you backed up the VXD registry key to a text file as I stated in my original
reply, you cab replace the deleted sub-keys by simply importing the text file back into the Registry: Start Run Regedit, Registry menu Import I'm not sure what you have done since then....you state you allowed Windows to install drivers for the mouse but I don't know what exactly was done. SSIACT.386 appears to be a driver for a copy-protection device, or dongle, apparently installed on the LPT (printer) port. Do you have such a device? -- Glen Ventura, MS MVP Shell/User, A+ http://dts-l.org/goodpost.htm wrote in message oups.com... Glen: Sorry I took so long to reply - I had to work tonight... Anyway, let me bring you up to date. I did the MSINFO thing and didn't see anything interesting. I've pasted it at the bottom of this post. So then I did the regedit thing and removed two items - lmouse and lmul. And then restarted. Boy things changed! When it rebooted it complained that it couldn't find the files for the mouse and it wanted the Windows98 CD. So I put in the CD but it couldn't find the files it wanted. So I guided it to where the CAB files are (I had to move them as I was out of space on my C drive) and it loaded the mouse drivers and continued booting and then restarted and went back to safe mode. Sad. So I started poking around and it looks like the msmouse driver is now loaded and good to go. So I tried the mode where you boot with confirmation of each step. It seems the last step before going off to never never land and rebooting is SSIACT.386. So, on a whim, I said yes to everything else and then no to this last step and, wonder of wonders, I boot almost normally. I say almost because it's really, really slow. But here I am in my normal environment. So now the question is what is SSIACT.386 and what do I do about this? There is an entry in the System.ini in the [386Enh] that says device=SSIACT.386. I'll try checking for viruses and bots. Otherwise I'm still at a loss. Thanks, Steve EPSON Background Monitor Startup Group "C:\Program Files\Common Files\EPSON\EBAPI\Stms.exe" ScanRegistry Registry (Machine Run) c:\windows\scanregw.exe /autorun TaskMonitor Registry (Machine Run) c:\windows\taskmon.exe SystemTray Registry (Machine Run) SysTray.Exe POINTER Registry (Machine Run) C:\PROGRA~1\MICROS~3\point32.exe TCASUTIEXE Registry (Machine Run) TCAUDIAG.EXE -off LexStart Registry (Machine Run) Lexstart.exe LexmarkPrinTray Registry (Machine Run) PrinTray.exe LoadPowerProfile Registry (Machine Run) Rundll32.exe powrprof.dll,LoadCurrentPwrScheme CriticalUpdate Registry (Machine Run) c:\windows\SYSTEM\wucrtupd.exe -startup Iomega Startup Options Registry (Machine Run) C:\Program Files\Iomega\Common\ImgStart.exe Iomega Drive Icons Registry (Machine Run) C:\Program Files\Iomega\DriveIcons\ImgIcon.exe QuickTime Task Registry (Machine Run) "C:\WINDOWS\SYSTEM\QTTASK.EXE" -atboottime TIPS Registry (Machine Run) C:\PROGRA~1\MICROS~3\tips\mouse\tips.exe Zone Labs Client Registry (Machine Run) D:\Program Files\Zone Labs\ZoneAlarm\zlclient.exe AVG7_CC Registry (Machine Run) C:\PROGRA~1\GRISOFT\AVGFRE~1\AVGCC.EXE /STARTUP AVG7_EMC Registry (Machine Run) C:\PROGRA~1\GRISOFT\AVGFRE~1\AVGEMC.EXE AVG7_AMSVR Registry (Machine Run) C:\PROGRA~1\GRISOFT\AVGFRE~1\AVGAMSVR.EXE EncMonitor Registry (Machine Service) C:\Program Files\Encompass\Monitor.exe dRMON SmartAgent Registry (Machine Service) drmon\SmartAgt\SmartAgt.exe LoadPowerProfile Registry (Machine Service) Rundll32.exe powrprof.dll,LoadCurrentPwrScheme MiniLog Registry (Machine Service) C:\WINDOWS\SYSTEM\ZONELABS\MINILOG.EXE -service SchedulingAgent Registry (Machine Service) mstask.exe CVPND Registry (Machine Service) "C:\Program Files\Cisco Systems\VPN Client\cvpnd.exe" start TrueVector Registry (Machine Service) C:\WINDOWS\SYSTEM\ZONELABS\VSMON.EXE -service KB891711 Registry (Machine Service) c:\windows\SYSTEM\KB891711\KB891711.EXE |
#10
|
|||
|
|||
LMOUSE boot problem
Glen:
Yes, I backed up the VXD registry. It appears that Windows installed the driver for the mouse I have: msmouse.drv. We had a program 7 years ago that required a dongle. We no longer have the dongle. Or the program. So, on a whim, I went into msconfig to see if I could find anything. Sure enough, under system.ini there was a selection called [386Enh]. Under that there was a checked box next to "device=SSIACT.386". I unchecked that. I've now booted a bunch of times, all successfully. This seems to have made the difference. An interesting side note: for quite a while (more than a year), the computer usually didn't shut down properly - it would get most of the way and just hang. We'd have to turn off the power and then wait through the disc check when we turned it back on. Since making the change you suggested to remove the Logitech stuff, that problem seems to have gone away. Every time I've shut it down for the last day, it shut down properly. And I've shut it down a lot because of all the changes. (This problem applied to restarts as well as regular shut downs.) Anyway, what are the consequences of getting rid of the SSIACT.386 be? I suppose I can wait and see if something doesn't run. Thank you, Steve |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
boot problem | Dick Minter | General | 1 | May 17th 05 02:23 PM |
Windows 98 Boot up problem due to ndiswan.vxd missing file | Martin Healy | Setup & Installation | 2 | May 4th 05 11:34 PM |
What is going on? | BAP | General | 20 | March 11th 05 01:25 PM |
windows 98se monitor prob | fortwilliam | General | 10 | October 21st 04 08:53 PM |
MBR switch on FDISK | jt3 | General | 30 | June 21st 04 08:56 PM |