MS WheelMouse stuck with any "low-key" config. when plugged into a PS2 port
 

I noticed that my MS WheelMouse was stuck with any "low-key" config. (among which A500 Quickstart)
if plugged into the PS2 socket of my PC (via an converter).

I just plugged in to an USB port and it's working again. This doesn't happen with v1.4.6.

What?

I didn't notice that problem with the mouse freezes earlier since I haven't been using the A500 Quickstart in weeks .

There are two cases :

• When I load a preconfigured WB and emulate an A1200 or 4000 -typically AmigaSYS, in this case the mouse behaves normally
• When I boot from a floppy, using a config with low specs (typically the A500 Quickconfig), in this case, the mouse pointer would halt in its initial position, the buttons would not respond in clicks at all

("Installing" the virtual driver doesn't help)

So what I did was simply plug my mouse (which is a MS USB WheelMouse) to a USB port.

The mouse, only when plugged on the green port just beside the purple one (they're called PS2 ports, right ?) would have this erratic behavior, on such occasions I try to describe : Loading a game or a demo directly from df0:, with an A500 config..

NOTE : since it's a USB model, I need to use a USB/PS2 converter to plug it on these ports


-Fixed-

The mouse goes in the green port, not the purple one.

Keyboard is purple.

I mixed them, sorry. The keyboard, also a USB model, is indeed on an adapter connected to the first port,
the mouse was plugged on the green port.

I tried with "enable legacy USB devices" in the BIOS, it didn't help either.

I still have no idea what this thread is about.

In simple terms, my mouse is stuck when I load a demo or a game with the A500 Quickconfig, provided it is plugged on the PS2 port.

Just thought of telling Toni about the problems it would cause in such circumstances.

I don't have any "true" PS2 mouse to experiment further, it's an optical WheelMouse, which, to save a USB port, I used to leave on that port. I don't use as many USB devices as before, so now it's all right for me to plug in on a USB port (still I wonder why that problem didn't occur with stable releases).

There we go!

That makes sense now. Well done.

I have the same mouse, the same WinUAE version and I don't have your problems. Mine works like a charm :D

...but it's not plugged in the same way.
Do you have a USB2PS2 converter or a "true" PS2 mouse at your disposal ?
Only then could you possibly see what I mean (if the problem is reproducible, chances are it is since my other computer does the same).

As I stated earlier, the mouse works fine with latest beta when plugged on a USB port (Also, problem is noticeable only when loading any ADF from df0: with the A500 QuickConfig or a custom A500 config).

Sorry Deli, I had the same mouse until it suddenly stopped working, you must of cursed it, so I'm now using another mouse but just the PS2 Logitech thing I first had.

I'm gonna take it to bits later and see if there's anything I can do with it, if I can't get it working by 21:00 it's getting the lump hammer treatment.

Blinking sods law this, perfectly good mouse, disabled my one of our favourite members "Deleauvive" :D

@Toni
Here are the log files :
winuaebootlog, winuaelog, and my config, although the quick config. would not differ concerning this issue.

@DH
Good, if you still have one of these old PS/2 mouse.
Could you try to boot an ADF and take notice of what's happening (or not happening for the matter) when you want to move the pointer or left-click, then ?

That would be nice if you could attach your log files too, in case yours is stuck too (that is, before you go on hammering it :lol).

@Deli
Too late, the mouse is totally bust, it doesn't work in windblows, nor on 3 other computers, it has died, it has ceased to exist, it has expired and is now in wheely bin heaven :laughing

Sorry mate! Can't help you now, I'll have to get a new mouse :( I don't like this old Logitech thing, it's horrible :(

Test all mouse types in ports panel first.

@Toni
You're right to suspect a wrong mouse selection.

"MS PS2 Port Mouse (IntelliPoint)" is a more suited
option than "Windows Mouse"

But in either case, the mouse is stuck, no improvement.
Same with other selections (Souris*, Souris sans fil CDTV...)

I can donate a PS2 converter :lol if you're the only person willing to reproduce it.

@DH
In OT, there is a rather lively suggestions thread for choosing a new keyboard.
May be it could be interesting to have one for choosing a new mouse.

How useless reply as usual. Test ALL mouse options.

@Deli, like I said earlier, mine worked no problems until it broke :mad

Anyhow, I know what mouse I'm after, so I don't need to create an OT thread requesting a new mouse.

Like Toni said, try all mouse options, one should work, it did with mine ;) obviously ;) until it broke :mad

In port 0, tried :

• Souris*
• Windows Mouse
• MS PS2 Port Mouse (IntelliPoint)

With any combinaison of

• Défaut
• Souris
• Souris Sans fil CDTV

Tried with Virtual Drivers installed also :sad

You have no 'RAW mouse' entry? That's strange...
Oh and maybe it would be helpful if you would disable your french translation dll for these tests.

@Deli
Your mouse will break soon, like mine :mad and become another casualty in a wheely bin, go and buy yourself a PS2 mouse and your problem will be solved :D