Turbo/warp mode under WINE on Linux

[Yesideez]

It's permanently enabled and I can't switch it off.

When I reset the emulator and hold down both mouse buttons to get into the early startup control it boots up before I can press both mouse buttons.

Pressing END+BREAK does nothing - is there anyway I can switch it off without using the keyboard please?

(I've also noticed that the lcommand and rcommand (the Amiga keys) and a combo in Workbench doesn't respond either. I've set ToolsDaemon up to open a new CLI window on rcommand+w and nothing happens. Tried rcommand+N for New Drawer and Linux opens another browser window)

I'm using the latest version of WinUAE (4.1.0) x64.

[Toni Wilen]

Originally Posted by Yesideez

It's permanently enabled and I can't switch it off.

When I reset the emulator and hold down both mouse buttons to get into the early startup control it boots up before I can press both mouse buttons.

Pressing END+BREAK does nothing - is there anyway I can switch it off without using the keyboard please?

(I've also noticed that the lcommand and rcommand (the Amiga keys) and a combo in Workbench doesn't respond either. I've set ToolsDaemon up to open a new CLI window on rcommand+w and nothing happens. Tried rcommand+N for New Drawer and Linux opens another browser window)

I'm using the latest version of WinUAE (4.1.0) x64.

Check that your config file does not have warp mode force activation. (warp=true)

Misc panel has "1 second reboot pause" option designed for above situation (without warp mode it still can be too fast, especially if JIT is enabled)

Keyboard problem may be wine issue but I have heard there should not be any wine specific issues with winuae.

Use -log -inputlog 1 -inputdevicelog 1 command line parameters and test if both host side and Amiga side keyboard event gets logged.

[Falcon]

Using WinUAE 4.9.1 64-bit with Wine 7.21 (same with many recent versions), I have found that the PAUSE and NUMLOCK keys are swapped in WinUAE's input handling. No clues about any solutions so far, but as a workaround, I have mapped the NUMLOCK source to "Pause emulation".

Not sure if Warp mode can be remapped, so I just have to toggle it with END+NUMLOCK instead.

Hope this helps someone.

[Falcon]

Not sure if this is the best thread for it, but since it's already been mentioned and it's sort-of related, here goes:

Running under Windows:

- PAUSE first sends scancode 0x1D (CTRL) with RI_KEY_E1 flag set, which gets ignored by WinUAE (had a look at the source code), followed by scancode 0x45 and VKey 0xFF; the 0xFF causes WinUAE to set bit 7, making the final scancode 0xC5

- NUMLOCK sends scancode 0x45 with no extended flags -> final scancode is 0x45


Running under Linux and Wine:

- PAUSE sends only one RawInput event with scancode 0x45 and VKey 0x13 -> final scancode is 0x45 (interpreted as NUMLOCK)

- NUMLOCK sends scancode 0x45 with RI_KEY_E0 flag, causing WinUAE to set bit 7, making the final scancode 0xC5 (interpreted as PAUSE)


This explains the swapping of the two keys. If a workaround is implemented for this, I would recommend having it enabled via an option like "-winekeyboard".

Detecting Wine and automatically activating the workaround would be risky, since the Wine behaviour might be changed in some future release.

I might have a go at it myself sometime, if I manage to build WinUAE from source.

[xc8]

guys the Amiberry works like a charm on linux - can even r/w on raw amiga HDDs/CFs, don't waste your time with 'wine'

[SpaceAce]

Originally Posted by xc8

guys the Amiberry works like a charm on linux - can even r/w on raw amiga HDDs/CFs, don't waste your time with 'wine'

Amiberry doesn't support Kickstarts after 3.1 (e.g. 3.1.4, 3.2)


That's why we use "Wine" under linux.

[xc8]

weird, I just booted it with 3.2.1 and 3.1.4 and is working, at least on early startup screen as I have no installation of the later workbench (system asks for libs)

amiberry v5.1 on debian (LMDE) , if you need any tests there let me know.

edit:
those kickstarts are booting even with e-UAE 0.8.29 (bit ancient version I think)

-I just used the roms for A500/600 .

[SpaceAce]

Originally Posted by xc8

amiberry v5.1 on debian (LMDE) , if you need any tests there let me know.

Now that's interesting. I tried 3.1.4 and 3.2 on Amiberry 5.1 on a Raspberry Pi 4 and it won't boot, I only get a black screen. Early startup doesn't work.

Is the feature set different between X64 and ARM?

[Saghalie]

Originally Posted by SpaceAce

Is the feature set different between X64 and ARM?

x64 is the 64bit architecture for computers running Windows/MAC/Linux
ARM architecture is for computers running RaspberryPI (PI400 for me).
There are other computer OSes that use ARM as well.

Currently AmiBerry v5.4 works with all 3.xx models. You can visit
https://www.amikit.amiga.sk/ and get the best damned configuration ever
made (IMHO anyway). I just checked, it will not run v4.xxFE - but that's
why we have IBM clones running Windows - correct?

Anyways, have fun!