WinUAE v4.10.2 Beta 2 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 changelog:
- There is no undocumented HAM behavior, it was bug in emulation, in certain situations HAM decoding incorrectly started before border and fix only accidentally worked in test case. (b1)
- Hardware info panel now shows complete memory map when emulation has been started. Before starting emulation it works like previously (adjustable, lists expansion devices only). Added address space end column. (TODO: more info, perhaps also include PCI devices)
- Added backslash/F11 swap key option to Input panel. This is global option (registry/ini) and swap is done after input mapping. Reverts b1 key swap.
- Enabling Copper DMA didn't wake up Copper immediately but when next line started. (4.9.something probably)
- Added inverted lightpen/gun input events. (ALG Fast Draw Showdown)
- If any debugger memory search command (s, fa, etc) have start address parameter that points to any ROM address, search runs normally until last ROM address. Previously searching from ROM addresses was not possible.
- If keyboard reset warning was enabled, releasing reset keys caused second reset if they were kept pressed until reset warning had internally generated reset. (4.10.0)
- If keyboard reset warning is enabled, keyboard reset does not start (and reset warning key code is not sent) until at least one key is released and if keys are kept more than 5 seconds, hard reset is forced. Previously if keyboard reset warning was enabled, reset always started immediately and forced hard reset was not possible.

Download: WinUAE v4.10.2 Beta 2 x86
Download: WinUAE v4.10.2 Beta 2 x64
Source: Here