WinUAE 2.3.0 beta series (was 2.2.1)

[PaulyQ]

I like, sort of a second chance to enter "none"

[Toni Wilen]

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

Beta 17:

- removed duplicate "none" in filter list
- RTD also missed address error check
- MMU emulation bus error handler uses C++ exceptions again (like in original Aranym version), removed some not so useful forced inlining, smaller executable.
- decided to disable some MMU table caching and suddenly NetBSD crash disappeared, MMU emulation is probably much slower now but at least it seems to work until proper fix is found, (hopefully Aranym developers have some ideas) Debian 68k Sarge Linux confirmed working now
- right border color "glitch" when waiting for hpos<7 in copper list broke in b3
- only disable Direct3D9Ex if pixel shader support is < 2.0
- do not open files smaller than blocksize (512 bytes) as a hardfile
- hardfile dialog accepts dragged and dropped files

[Toni Wilen]

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

Beta 18 (RC1, official release next week):

- F13/F14/F15 rawinput keycodes fixed (at least available on some apple usb keyboards)
- removed default volume and mute keyboard mappings because in rawinput mode they are always handled by Windows (which is annoying, I haven't found any simple way to disable them, "disable hotkeys" flag only seems to disable Windows keys)
- fall back to directinput if rawinput enumeration worked but RegisterRawInputDevices() returns error
- Paula disk fifo statefile support

[Toni Wilen]

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

Beta 19 (RC2):

- rar archives crashed if file was already open (stupid design flaw, it was possible to open archives even if requested mode was read-write)
- added "fullscreen (max)" and "fullscreen (tv)" (approximate only) to "autoscale" select menu, basically replaces old "FS" filter multiplier

[Asle]

Hi,

With version 2300b19 (never tested any beta before), I can't access anymore a DMS with "standard" Amiga file system. Meaning booting on a HD, whatever config, then adding the disk image and typing df0: . It worked OK with 2.2.0.
You can try with this example file :
ftp://ftp.amigascne.org/pub/amiga/Pa...heSaurizo2.dms

DMS write is OK and accessing the ADF goes back to normal afterwards.

Not sure it's a correct report. Please, tell me what more would be needed

All the best
Sylvain

[TCD]

Works with beta 18. Beta 19 displays 'DFx:DMS!' instead of the disk name.

[Toni Wilen]

Archive support design flaw is worse than I originally thought..

When disk image is inserted, first it attempts to open in read-write mode and if it fails, it tries to open in read-only mode.

Archive support ignores this flag and returns "ok" when attempting read-write, this breaks read-write checkbox, saveimages and others.

Previously it worked accidentally but now it causes issues..

[Toni Wilen]

http://www.winuae.net/files/b/winuae.zip should fix it properly, make sure to test all kinds of archives

[TCD]

Following tested and working :
7Zip
DMS
RAR (using unrar.dll)
Zip

[Asle]

Hey,

DMS with AFFS are read OK now. A question however. Again, I mounted a DMS with AFFS, then removed the write-protect and deleted a file. It was OK ! And rebooting WinUAE with said disk image gave me a complain because a file was missing. Now, closing WinUAE and renaming the DMS then booting it is OK (no file missing). What's happening then ?
I made the test because you talked about that feature earlier.

cheers,
Sylvain

[Toni Wilen]

Originally Posted by Asle

Hey,

DMS with AFFS are read OK now. A question however. Again, I mounted a DMS with AFFS, then removed the write-protect and deleted a file. It was OK ! And rebooting WinUAE with said disk image gave me a complain because a file was missing. Now, closing WinUAE and renaming the DMS then booting it is OK (no file missing). What's happening then ?
I made the test because you talked about that feature earlier.

It works as designed, when non-writable image (dms, ipf, archives etc..) is write-enabled, separate "saveimage" is created in saveimages directory that contains modified tracks. Original file is never modified.

This may not have worked properly with some image types previously because of above design flaw that confused write-enable check.

[Xorlac]

On Beta19 (and other betas in the series), if you load a configuration, make some changes , highlight a custom configuration, andthen click "save", the configuration tree is collapsed. If you flip to Hardware and then back to Configuration the tree state is restored.

Shouldn't the state after save be the same view prior to clicking it?

[hrmes]

I just discovered a display issue with all betas. I tested b2 to the latest.

When Graphics API is DirectDraw and any filter (other than "none") is used, sometimes the screen goes black in some games.
I used Space Harrier (WHDLoad registered) for testing in both A500 and A1200 configurations.
From b2 to b9 the screen goes black after the title screen when in-game and the sound continues to play normally.
From b10 to the latest beta the screen goes black in the title screen and stays black in-game also.

During this if you switch the API to Direct3D or the filter to "none" then the screen returns to normal.

I also tested a floppy version of Space Harrier and it also has this issue, but it seems to be affected by other parameters like vert. position in the filter settings, and it is a bit unpredictable as to when it appears.

In the latest beta the screen returns to normal also if you selected "Fullscreen TV" in the filter settings.

Using latest Catalyst driver and latest DirectX update in Windows 7 x64.

[Toni Wilen]

Sorry but this is totally useless without logs. Also does it go black if you use direct3d when starrting emulation?

[Toni Wilen]

Originally Posted by Xorlac

On Beta19 (and other betas in the series), if you load a configuration, make some changes , highlight a custom configuration, andthen click "save", the configuration tree is collapsed. If you flip to Hardware and then back to Configuration the tree state is restored.

Shouldn't the state after save be the same view prior to clicking it?

Perhaps but 2.2 does the same too.. (EDIT: fixed)

[hrmes]

Originally Posted by Toni Wilen

Sorry but this is totally useless without logs. Also does it go black if you use direct3d when starrting emulation?

Sorry, here is the log. When Direct3D is selected this doesn't happen at all.

[Toni Wilen]

winuaelog.txt is missing (remember misc panel checkbox)

[hrmes]

Doh. Here we go again.

[Toni Wilen]

Thanks. http://www.winuae.net/files/b/winuae.zip should fix both reported issues.

"Final" RC tomorrow, official after few days. At least thats the plan..

[hrmes]

That was fast, but it didn't fix it... Now it's black screen all the time, from the moment the emulation starts.
Tried several WHDLoad games with the same results. Again switching to Direct3D fixes it.

EDIT:
I think it must be a problem with the screen vertical offset. I started the A4000 configuration and native screens like SysInfo are centered too high, that is only the bottom half is visible.