1111
Hardware / Re: USB drivers 10.213 released
« on: December 25, 2016, 02:04:54 pm »
Sorry but all of what you describe has nothing or very little to do with the USB drivers.
1) first you screwed up your system by removing MULTIPT.EXE where you don't know what that file is good for. Suffice it to say that it is loaded by some WPS class, very likely WPMouse, and therefore it's certainly a very bad idea to just kill it or remove it because you don't know what the affected WPS class will do if that daemon executable is not running.
2) then you fumbled around with your WIFI and think it has some repercussion on the system even though you didn't even install a driver for that device. The only thing that could go wrong is that your WIFI HW is issuing spurious interrupts and if no driver handles that (of course no driver will do as there is no WIFI driver to specifically handle that interrupt) OS/2 will eventually shut down the interrupt for good and any device using the same (shared) interrupt would cease working. Then the only advice can be to turn off WIFI for good. And you know that you have crappy HW.
3) you say that all of a sudden you can select the XView menu entry. However, USBMOUSE.SYS only knows about mouse clicks and mouse pointer position info. It does not give a bit or care on what you click on.
From all those weird issues you have I would think that your OS2.INI and OS2SYS.INI are completely screwed up and need a cleanup. You will never solve this problem by mucking around with drivers, no matter what drivers you use.
Another likely culprit is your legacy mouse driver which is either AMOUSE.SYS or MOUSE.SYS. I suggest you (re)install the latest AMOUSE (if you have an ArcaNoae subscription). That's because USBMOUSE.SYS needs a legacy mouse driver to interact with. In the end, it's the legacy mouse driver that reports mouse clicks and pointer position to the operating system.
Lars
1) first you screwed up your system by removing MULTIPT.EXE where you don't know what that file is good for. Suffice it to say that it is loaded by some WPS class, very likely WPMouse, and therefore it's certainly a very bad idea to just kill it or remove it because you don't know what the affected WPS class will do if that daemon executable is not running.
2) then you fumbled around with your WIFI and think it has some repercussion on the system even though you didn't even install a driver for that device. The only thing that could go wrong is that your WIFI HW is issuing spurious interrupts and if no driver handles that (of course no driver will do as there is no WIFI driver to specifically handle that interrupt) OS/2 will eventually shut down the interrupt for good and any device using the same (shared) interrupt would cease working. Then the only advice can be to turn off WIFI for good. And you know that you have crappy HW.
3) you say that all of a sudden you can select the XView menu entry. However, USBMOUSE.SYS only knows about mouse clicks and mouse pointer position info. It does not give a bit or care on what you click on.
From all those weird issues you have I would think that your OS2.INI and OS2SYS.INI are completely screwed up and need a cleanup. You will never solve this problem by mucking around with drivers, no matter what drivers you use.
Another likely culprit is your legacy mouse driver which is either AMOUSE.SYS or MOUSE.SYS. I suggest you (re)install the latest AMOUSE (if you have an ArcaNoae subscription). That's because USBMOUSE.SYS needs a legacy mouse driver to interact with. In the end, it's the legacy mouse driver that reports mouse clicks and pointer position to the operating system.
Lars