English Amiga Board - View Single Post

Toni Wilen · 23 October 2022, 20:00

https://download.abime.net/winuae/fi...nuae_4920b3.7z
https://download.abime.net/winuae/fi...ae64_4920b3.7z

Beta 3:

- 68000 IPL check position is now almost fully accurate (Still some special cases to check and test). Very big thanks to fx68k author!
- W debugger command hang fixed.
- Full drive/RDB mode is now normal checbox. Hopefully it is now less confusing than button that didn't really look like a button. If selected HDF already has RDSK identifer, checkbox is ticked and disabled. Checkbox can be only ticked/unticked if selected HDF does not have RDSK identifier.
- GDI mode didn't force 32-bit screen depth mode.
- FloppyBridge uae-configuration change now really updates all internal variables.
- Screenshots didn't work if 256 color checkbox was not ticked (tried to create 24-bit palette indexed image)
- DMACONR blitter status 1 cycle delay was broken (Circle scroller / UFO)
- Enabling DMA debugger and then returning to emulator continuously reported conflicts until next frame had finished. DMA debugger init was changed but tables were not fully initialized.
- Keyboard reset now behaves more like real hardware. Press keys, hardware gets reset (if keyboard reset warning is not active), reset continues only when at least 1 key is released. If all keys are kept pressed more than 5 seconds: do hard reset.
- DMA debugger CIA access line includes also E-clock state (0, 2, <data access info>, 6, 8) and any "wasted" cycles needed to sync with E-clock are marked with "-".
- DMA debugger is wider. More space for future features.
- New cputester tests done, for example all SR modification instructions (including STOP) tested with both trace + pending interrupt. No errors found.
- If STOP was executed without trace active and STOP enabled trace, STOP still stops normally and only interrupt can wake it up. (b1)
- Blitter busy bit read incorrectly as blit not busy if blitter was in non-nasty mode and not line mode and CPU stole second to last D channel slot.
- Removed all remaining Windows 7/Vista checks (from days when XP and Vista was still supported).
- "Remove interlace artifacts" is broken. Will be fixed later.

btw, this thread is only about beta related bugs or problems. Don't post unrelated new feature or improvement requests here.

23 October 2022, 20:00	#94
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,507	https://download.abime.net/winuae/fi...nuae_4920b3.7z https://download.abime.net/winuae/fi...ae64_4920b3.7z Beta 3: - 68000 IPL check position is now almost fully accurate (Still some special cases to check and test). Very big thanks to fx68k author! - W debugger command hang fixed. - Full drive/RDB mode is now normal checbox. Hopefully it is now less confusing than button that didn't really look like a button. If selected HDF already has RDSK identifer, checkbox is ticked and disabled. Checkbox can be only ticked/unticked if selected HDF does not have RDSK identifier. - GDI mode didn't force 32-bit screen depth mode. - FloppyBridge uae-configuration change now really updates all internal variables. - Screenshots didn't work if 256 color checkbox was not ticked (tried to create 24-bit palette indexed image) - DMACONR blitter status 1 cycle delay was broken (Circle scroller / UFO) - Enabling DMA debugger and then returning to emulator continuously reported conflicts until next frame had finished. DMA debugger init was changed but tables were not fully initialized. - Keyboard reset now behaves more like real hardware. Press keys, hardware gets reset (if keyboard reset warning is not active), reset continues only when at least 1 key is released. If all keys are kept pressed more than 5 seconds: do hard reset. - DMA debugger CIA access line includes also E-clock state (0, 2, <data access info>, 6, 8) and any "wasted" cycles needed to sync with E-clock are marked with "-". - DMA debugger is wider. More space for future features. - New cputester tests done, for example all SR modification instructions (including STOP) tested with both trace + pending interrupt. No errors found. - If STOP was executed without trace active and STOP enabled trace, STOP still stops normally and only interrupt can wake it up. (b1) - Blitter busy bit read incorrectly as blit not busy if blitter was in non-nasty mode and not line mode and CPU stole second to last D channel slot. - Removed all remaining Windows 7/Vista checks (from days when XP and Vista was still supported). - "Remove interlace artifacts" is broken. Will be fixed later. btw, this thread is only about beta related bugs or problems. Don't post unrelated new feature or improvement requests here.