search

MiSTer-devel / ao486_MiSTer

ao486 port for MiSTer
Other
260 stars 68 forks source link

Mouse driver says "Mouse reset returned <hex> (should be ack)" #8

Open thejpster opened 4 years ago

thejpster commented 4 years ago

On both MS-DOS 6.22, with some random mouse.com driver, and when installing Windows 95 (original release), I've seen the following error:

Mouse reset returned { hex } (should be ack)

It doesn't happen on every boot - maybe about one in four. Rebooting the core from the F12 menu seems to fix it. { hex } is a random hex byte - it seems to vary.

robindegen commented 4 years ago

Same issue here. I've seen 0 and 18 so far. Doing a warm reset with the key0 menu seemed to help

NightshadowPT commented 4 years ago

I had the same problem.

Only had this issue when using EMM386.

As a workaround you can change the order of loading the Mouse driver and it should work.

I guess it just fell on a different position in memory and worked fine.

Cheers

mabalmer commented 4 years ago

I was getting this too, but the hex byte returned was pretty consistent. I was trying to install Windows 3.1 in custom mode and it would say this:

FATAL: Mouse reset returned 28 (should be ack)

Every time I tried using it, it would do this.

Using DOS 6.22. I am not using EMM386, but I was loading HIMEM at boot time along with SB 2.0 drivers.

sorgelig commented 4 years ago

try other mouse driver. I use mouse too, but have no such problem.

thejpster commented 4 years ago

Can you give any details about which mouse driver you are using? I can then locate a copy and test.

sorgelig commented 4 years ago

CuteMouse v1.9.1 [DOS]

mabalmer commented 4 years ago

I was not using a mouse driver at all — perhaps that's why the error was coming up. Once I installed the CuteMouse driver, it stopped. I've also noticed a similar (possibly unrelated) error popping up with Windows 95 - if the mouse is moved before Windows fully starts, it throws a protection error that requires the machine be rebooted.

sorgelig commented 4 years ago

It's known unrelated issue. Either mouse moved or key is pressed in some booting stage leads to exception.