WinUAE v5.1.0 Beta 7 is released. WinUAE is the commodore amiga emulator for Windows. WinUAE is a mostly complete software emulation of the hardware of the Commodore Amiga 500/1000/2000. A Commodore Amiga, for those who don’t know, is a 16/32 bit computer system based on the Motorola 680×0 CPU and a few specially designed custom chips that provide very good graphics and sound capabilities. Its first incarnation, the A1000, appeared in 1985, followed by the highly successful A500 and A2000 models. WinUAE is a port of the originally written for Unixish systems UAE; but over time, it seems the Windows port, WinUAE has become the best version available on any platform. WinUAE is free software: you are welcome to distribute copies of it and/or modify it, under certain conditions. There is no warranty of any kind for UAE. For more details concerning these issues, please read the GNU General Public License, which describes the terms under which WinUAE is distributed.

WinUAE v5.1.0 Beta 7 Changelog:
- Fixed on screen keyboard transparency in D3D9/11 modes. It previously only worked in D3D11 HDR mode.
- Ignore "Main window always on top" misc setting in D3D11 mode. D3D10+ windowed mode is not possible if always on top window flag is set. Previously this caused fallback to D3D9 mode. This does not make sense in my opinion and it does not seem to be mentioned in documentation but CreateSwapChainForHwnd() fails if it is set. Debug D3D11 DLLs also report that it failed due to unsupported window flag.
- Do not do unnecessary graphics setup reset if RTG mode changed but only parameter that changed was color depth and mode is not fullscreen with match depth if possible enabled. (b1)
- If D3D11 screen init decided that new requested mode has same parameters as old mode, skip also other unnecessary graphics reinitializations.
- Do not enable temporary frameskip in warp mode if debug overscan mode is enabled, it can cause random glitches. Warp mode normally enables frameskip in non-ce modes.
- Ignore backwards or same line vertical VPOSW writes if it was CPU write and CPU emulation is not in accurate mode. This basically reverts VPOSW updates to pre-5.0 behavior when CPU is not at least in memory cycle exact mode, supporting only usual "fake NTSC" modes. At least AR3 does stupid things with VPOSW that can't work if CPU is not slow enough.
- Added generic support for emulation of IDE controllers that have in-circuit programmable flash/EEPROM chip.
- Flash/EEPROM emulation updates (support write protection enable/disable commands, parallel EEPROM partial writes supported)

Download: WinUAE v5.1.0 Beta 7 x86
Download: WinUAE v5.1.0 Beta 7 x64
Source: Here