http://www.winuae.net/files/b/winuae.zip should fix all above bugs. (Except if theme changes and emulation is paused, it is "feature" if window stays black)


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

Beta 1:

- Internal mouse counter under/overflow fixed, while moving mouse far enough, mouse jumped in opposite direction. (old bug)
- Directory filesystem file modification date resolution support is now 1 microsecond (was 1 second). AmigaDOS file time 1/50s "tick" resolution is now fully supported (if NTFS, FAT only has 2 second resolution)
- 1G RTG RAM was detected as "too large". (early 250 beta)
- ClipCursor() was not always called, it was possible for hidden Windows mouse to move outside of WinUAE window in some situations. (250b24)
- RTG aspect ratio still affected filter panel aspect ratio setting. (b26 update was not complete)
- _UAEFSDB.___ meta data files (stores illegal names, protection flags and comments if non-stream capable filesystem like FAT) haven´t worked correctly for a long time.
- _UAEFSDB.___ wasn´t always deleted when it become empty.
- Unminimizing unpaused emulation when "pause when mouse is uncaptured" was enabled.
- If win32.guikey config entry is set, normal GUI key (F12) events won´t open the GUI anymore.
- Always reset special monitor active flag (A2024/Graffiti) when display mode changes, fixes A2024 mode position when window needs to reopen but resolution didn´t change.
- Improved windowed mode bottom statusbar height calculation, fixes two pixel gap in Windows Vista classic mode.
- Fixed Amiga-side illegal memory access when booting directory harddrive(s) under KS 1.3.
- Reset GUI/emulation display when Windows desktop state changes (Theme change etc..)
- Removed remains of unused AROS CDFS support code.
- Compiled using MSVC 2012 with update 1 installed.





2.5.1 beta series.

This is usual quick 2.5.0 bug fix version. Estimated release date: before Christmas.
I try not to do any GUI changes this time, 2.5.0 translation DLLs should still work with 2.5.1.

Rules:

Allowed posts in this thread:

- bug reports but make sure bug is NOT in previous offical version. (Old bug -> separate thread)
- comments and suggestion about new features in betas or changed feature in beta. (missing feature or old feature which has not been changed in latest beta series -> separate thread)

Everything else will be deleted, no questions asked. (includes offtopic posts, discussion about pros and cons of public beta testing etc..)

Misc notes:

- "not working" is not a bug report -> instadelete
- always include name of the program. "Everything" or "most games" fail is not a bug report!
- always use quickstart settings. Non-QS setting reports will be ignored unless there is reason why quickstart isn´t good idea but still test using quickstart just to confirm! (unless it needs some HD highend config)
- always check logs (both winuaebootlog.txt and winuaelog.txt, don´t forget to enable logging in misc-panel) for possible error or warning messages.
- remember to include PC specs + Windows version (if asked)
- graphics error -> include screenshot.
- disk based program -> include CRC32 (mouse over disk history arrow down button will show CRC32) of the image(s) (or SPS ID or full tosec name if from latest set). Plain name of the game is NOT generally enough! (usually there are different cracks, trainers etc..)

As usual, betas may destroy your PC and your sanity

This thread is for general discussion (bad/good/stupid idea/whatever, no trolling or flaming) about public beta testing.

Beta test related PMs or emails will be generally ignored.