OS/2, eCS & ArcaOS - Technical > Hardware

Mouse weirdness

(1/2) > >>

Mentore:
Hello all, long time no see :-) I've been lurking a lot but without having too much to add. Recently, though, I came across a strange problem.

I've a rather old machine built by myself. Nothing too fancy, it's just an old Intel dual core with 2 GiB RAM, working only with eCS 2.1 GA. When I say "rather old" I mean "It has a PS/2 keyboard port and mouse port".

I used to work on it with an USB mouse connected to the PS/2 port via an adaptor and it worked fairly well (it's still smoother than my last laptop with an i5 CPU and Windows 10, mind you).

In the last few days, though, strange things have happened:

1 - my old mouse stopped working its left button, so I tried to use an USB mouse. It worked the first time and then no more.

2 - I tried another old PS/2 mouse (but this could be not working) and no success.

3 - I bought a new (wired, not wireless) USB mouse and tried to connect it to all the USB ports, other than the PS/2 port with its adaptor, and nothing - no mouse movements.

4 - everytime I connect the mouse to the USB port, eCS beeps (it's the same beep that occurs when I connect an USB pendrive or other MSD).

5 - Amouse is installed and Amouse USB driver too. Amouse control panel seems to detect the mouse, but the pointer does not move and pushing any of the mouse buttons doesn't do anything.

Now I want to take some time to try and see if the eCS installer actually sees the mouse. The same I'll do with some other OS installer (say, some linux).

Maybe this is the right time to think about migrating to ArcaOS...

Some ideas, anyone?
Mentore

Lars:
As to USB mouse: have you tried an updated USB driver stack ? I consider the eCS 2.1 supplied USB drivers to be hopelessly outdated. Either use the driver stack from AN or try mine (on Hobbes).

For PS/2 mouse and keyboard: the usual advice applies, always plug in PS/2 mouse or keyboard before you power on the PC. Everything else can damage the electronics (I cannot remember if it would work at all if connected to an already powered system).

I remember that USBD.SYS will issue a beep on an overcurrent situation (if a device draws too much current).
Bad, bad bad.
On the other hand: if you have a UHCI controller (which I strongly assume you do) then the problem is that the "overcurrent bit" was not properly defined between the Intel UHCI and the VIA UHCI controller. VIA has defined it logically negated to Intel. But then I remember (in the USBUHCD.SYS driver) I am flipping the bit on VIA to match that on Intel (same holds true for the AN stack) ...

I assume you can also neither see nor use your USB pendrive, correct ?

Finally: AMouse (at least older versions) comes with their own USBMOUSE.SYS driver. Don't use it. Make sure you use the one in the AN stack (or my stack). These will be located in the \OS2\BOOT directory.

Pete:
Hi

Are all usb drivers that are required installed?

You can use usbcfg to view and change usb settings - usbcfg is available as zip or wpi package http://hobbes.nmsu.edu/h-search.php?key=usbcfg082&pushbutton=Search


Regards

Pete

Mentore:

--- Quote from: Lars on December 04, 2017, 01:03:06 pm ---As to USB mouse: have you tried an updated USB driver stack ? I consider the eCS 2.1 supplied USB drivers to be hopelessly outdated. Either use the driver stack from AN or try mine (on Hobbes).

For PS/2 mouse and keyboard: the usual advice applies, always plug in PS/2 mouse or keyboard before you power on the PC. Everything else can damage the electronics (I cannot remember if it would work at all if connected to an already powered system).

--- End quote ---

Well this worries me a little (or a lot). I don't use the eCS supplied stack but one of your latest one, which by the way I found to be really useful. (thanks for that.)


--- Quote from: Lars on December 04, 2017, 01:03:06 pm ---I remember that USBD.SYS will issue a beep on an overcurrent situation (if a device draws too much current).
Bad, bad bad.
On the other hand: if you have a UHCI controller (which I strongly assume you do) then the problem is that the "overcurrent bit" was not properly defined between the Intel UHCI and the VIA UHCI controller. VIA has defined it logically negated to Intel. But then I remember (in the USBUHCD.SYS driver) I am flipping the bit on VIA to match that on Intel (same holds true for the AN stack) ...

--- End quote ---

IIRC (I built that beast loooooong ago) it has indeed an UHCI controller, and the beep is issued everytime I connect something to the USB ports. I was indeed assuming this was a "reassuring" signal, not a warning. Stupid me.


--- Quote from: Lars on December 04, 2017, 01:03:06 pm ---I assume you can also neither see nor use your USB pendrive, correct ?

--- End quote ---

This is a good "no": I indeed can see almost any of my USB gadgets, including a multicard reader. Actually I should try that again, but I surely remember I copied some files from a 16 GB pendrive to my machine using Larsen Commander and selecting the files via keyboard. No problems at all IIRC.


--- Quote from: Lars on December 04, 2017, 01:03:06 pm ---Finally: AMouse (at least older versions) comes with their own USBMOUSE.SYS driver. Don't use it. Make sure you use the one in the AN stack (or my stack). These will be located in the \OS2\BOOT directory.

--- End quote ---

This is something I shall try.
What I really can't possibly understand is why the mouse stopped working without having changed anything.
The next things I'll do will be surely taken from your list: updating USB stack and using your stack instead of USBMOUSE from AMouse. And keep fingers crossed.

Thanks a lot in the meantime.

Mentore

Mentore:

--- Quote from: Pete on December 04, 2017, 08:52:08 pm ---Hi

Are all usb drivers that are required installed?

You can use usbcfg to view and change usb settings - usbcfg is available as zip or wpi package http://hobbes.nmsu.edu/h-search.php?key=usbcfg082&pushbutton=Search


Regards

Pete

--- End quote ---

Hi Pete,

no problems in USB stack - everything is installed fine. As I just wrote to Lars, I'll surely try and update the drivers and modify something in CONFIG.SYS to use the right stack.
Then I'll go to eBay and buy new PS/2 keyboard and mouse, since there are still many  8)

Mentore

Navigation

[0] Message Index

[#] Next page

Go to full version