Email or attach your configuration if this is still happening. Does this only happen if you use input panel configuration?

Never mind, I found the problem.. (stupid me)

Buttons #4 and #5 are mapped to LALT+CursorLeft / LALT+CursorRight ("back" and "forward") by default (if more than 3 buttons) Unfortunately newish "Wheel [+]" and "Wheel [-]" are also considered buttons..

(I couldn't duplicate because I have mouse with extra buttons..)

http://www.winuae.net/files/b/winuae_1450b17.zip

Beta 17: (getting there..)

- rom scan detected roms inside archive directory failed to load
- mouse buttons #4 and #5 default Left ALT + Cursor Left/Right mapping fixed, was mapped to "Wheel +/-" if less than 5 buttons

Toni - 1450b17 :great

http://www.winuae.net/files/b/winuae_1450b18.zip

Beta 18: (RC)

- moved Picasso96 resolution list from special reserved display RAM area to regular Amiga RAM (allocated with AllocMem) This should be 100% fix to display resolution list corruption in display prefs utility. (if previous fix in b16 didn't fix it)
- following "fake" display resolutions added to Picasso96 resolution list (if no native support): 320x200, 320x240, 640x400, 640x480. In fullscreen selects next bigger supported resolution automatically. Note: fullscreen display is not centered
- keyboard led emulation should not cause random key presses anymore (but it still is quite unreliable)

default translation dll also included.

I still get the problem with the mousewheel and screwing up the keyboard!

What do you suggest I do so you can fix this?

Most obvious: check your input configuration and reset it..

Compatibility is selected as default

Nothing has been changed. I even remade the config file from scratch and still same problem!

This is getting nowhere without having any details, like do you still see something mapped to mouse wheel or "Wheel -/+"? (when using compatibility mode) Does it happen in non-compatibility mode? Does it happen if you use other mouse options in compatibility mode? (Mouse* or Windows mouse) What input events gets sent when you use mouse wheel? (debugger, "dj 1")

In compatibility mouse wheel 1 is mapped to the wheel

wheel + is left alt as is wheel -

Maybe it is that!

This is something that shouldn't happen anymore.. hmm... I guess I need to find 3 button mouse :)

Toni - If this helps I'm not having any problems with the mouse wheel with b18. I did debug and all I see is what I'm supposed to see. I have a Microsoft mouse with a left and right button and a wheel/button in the middle. I'm also having no problems with the Z3/RTG memory.

Are you 100% sure you have correct winuae.exe version? This can't happen anymore.. (famous last words, I know..)

I'm at my girlfriends right now (for a couple days at least) I'll get the latest beta and test when I get home, but i'm pretty sure it's the correct exe!

I have always the problem when no focus with winuae pausing (F12) : pause stop and winuae want focus!

please read
http://eab.abime.net/showthread.php?t=26715 before posting.
Without more details it will be difficult for toni to form a reply and handle your problem.
Anyways F12 is not used for pausing but rather to bring up the configuration screen. Paused emulation is a side effect of this function, albeit a welcome one.
Enough with the chit chat as i'm pretty sure this isn't beta related.

1.4.5 has been officially released. This thread closed.