WinUAE 4.9.0 beta series (Was 4.5.0)

[falken]

Originally Posted by Toni Wilen

https://download.abime.net/winuae/fi...uae_4500b16.7z
https://download.abime.net/winuae/fi...e64_4500b16.7z

Beta 16:

- Hard reset leaked indirect mode allocated memory banks (outside of JIT compatible address range), for example Z3 RAM outside of partially outside of first ~2G of address space.
- GUI misc list powerled dims option never worked, option was always cleared. (Only manual config file editing worked)
- fi debugger command now accepts assembly syntax (for example "fi trap #0"). Only max first 3 words (if it is longer than 3 words) are used in breakpoint condition.
- CPU% OSD leading zero removed.
- "Blacker than black" display panel option did nothing in non-AGA modes.
- 68060 unimplemented integer instruction mode + unimplemented instruction with -(A7)/(A7)+ addressing mode in user mode: exception stack frame was created first, then -(A7)/(A7)+ modification was incorrectly restored using supervisor stack pointer.
- 68040/060 unimplemented FPU instructions also update FPIAR. Some invalid instructions don't but this seems to be undefined behavior. 6888x only update FPIAR if FPU exception(s) are enabled.
- 68040/060 unimplemented FPU mode arithmetic exception fixes, all 68060 FPSP test package tests now pass. (and when run using 68040 or 6888x: test errors will match real hardware 100%)
- Fixed FMOVEM.L #xxx,<more than one control register> disassembly.
- Windowed mode status bar height is correctly calculated when window is moved to different DPI monitor.
- Removed ROM scan expansion device result list. It is out of date and code was almost unmaintainable.
- Hopefully last blitter update related fix, copper blitter waits should work correcly again. (This is a hack. Copper emulation also needs an update.)

Thank you Toni, i'll try that beta 16

[Zarnal]

Originally Posted by Toni Wilen

https://download.abime.net/winuae/fi...uae_4500b16.7z
https://download.abime.net/winuae/fi...e64_4500b16.7z

Beta 16:

- Hopefully last blitter update related fix, copper blitter waits should work correcly again. (This is a hack. Copper emulation also needs an update.)

The OCS demo "TommyKnockers" freezes again with this new hack (I think this may be normal until the next copper emulation because it is a really complicated case). Am I right ? You had already spoken about it during the first report. Thanks.

[ross]

Hi Toni, with the latest beta I've a black stripe at the bottom, visible in any windowed mode (this is a 'Quickstart' A500 one, but also on my usual configurations).

[Toni Wilen]

Originally Posted by Zarnal

The OCS demo "TommyKnockers" freezes again with this new hack (I think this may be normal until the next copper emulation because it is a really complicated case). Am I right ? You had already spoken about it during the first report. Thanks.

It needs 68000 undefined behavior update. Blitter update simply made old bug visible.

Originally Posted by ross

Hi Toni, with the latest beta I've a black stripe at the bottom, visible in any windowed mode (this is a 'Quickstart' A500 one, but also on my usual configurations).

Which monitor DPI value?

[ross]

Originally Posted by Toni Wilen

Which monitor DPI value?

Do you mean DPI Scaling Level? 125%

[Retroplay]

Same issue here on DPI 125%.

[amilo3438]

Originally Posted by Zarnal

The OCS demo "TommyKnockers" freezes again with this new hack (I think this may be normal until the next copper emulation because it is a really complicated case). Am I right ? You had already spoken about it during the first report. Thanks.

Originally Posted by Toni Wilen

It needs 68000 undefined behavior update. Blitter update simply made old bug visible.

As temporary solution just use 68010 ! (it doesn't freezes the demo)

[Seiya]

i don't know if is beta 4.5, but i saw that i have so many instability and fpu crash using 68040 and 68060 in jit mode, while if set 68030+68882 (always in jit mode) warp3D apps run much better and more stable.

Always on standard Workbench 3.1.

[hexaae]

Originally Posted by Seiya

i don't know if is beta 4.5, but i saw that i have so many instability and fpu crash using 68040 and 68060 in jit mode, while if set 68030+68882 (always in jit mode) warp3D apps run much better and more stable.

Always on standard Workbench 3.1.

(Remember to apply http://m68k.aminet.net/package/util/boot/NoMoreDiv0 if you use JIT for Workbench, for much improved stability against DIVIDE BY ZERO gurus on faaaast emulated systems... Is a benign must-have patch.)

[DamienD]

Originally Posted by Seiya

i don't know if is beta 4.5, but i saw that i have so many instability and fpu crash using 68040 and 68060 in jit mode, while if set 68030+68882 (always in jit mode) warp3D apps run much better and more stable.

Doesn't happen for me; and I've tested all these 68040 / FPU / JIT / RTG games in my collection:

Abuse [RTG]   [MS-DOS conversion].uae
CannonBall - The Enhanced OutRun Engine [RTG]   [Arcade conversion].uae
Cave Story [RTG]   [Windows conversion].uae
Descent - Freespace - The Great War [AmigaCD] [RTG].uae
Doom II - Hell on Earth [RTG]   [ZDoom].uae
Doom [RTG]   [ZDoom].uae
Duke Nukem 3D [RTG]   [AmiDuke].uae
Earth 2140 & Earth 2140 - The Final Conflict - Mission Pack [AmigaCD] [RTG].uae
Fortress of Fear [RTG]   [unreleased] [demo].uae
Heart of Darkness [RTG]   [Windows conversion].uae
Heretic & Hexen [AmigaCD] [RTG]   [MS-DOS conversion].uae
Hydra Castle Labyrinth [RTG]   [3DS conversion].uae
Nightlong - Union City Conspiracy [AmigaCD] [RTG].uae
Spear of Destiny - Mission 2 - Return to Danger [RTG]   [AmiSpear].uae
Spear of Destiny - Mission 3 - Ultimate Challenge [RTG]   [AmiSpear].uae
Spear of Destiny [RTG]   [AmiSpear].uae
The Feeble Files [AmigaCD] [RTG].uae
The Griffon Legend [RTG]   [Windows conversion].uae
Wild Flying [RTG]   [unreleased] [demo].uae
Wolfenstein 3D [RTG]   [AmiWolf].uae

...but I guess you're talking about "Warp3D" mainly; which I've never setup / used.

Mind you, last time I tested them all was v4.5.0 beta 4 or something...

[Seiya]

yes.. i talking about "Warp3D" and with diskmag The Vague that is Warp3D. Now i will try this patch suggested by hexaae

[Toni Wilen]

Originally Posted by Seiya

i don't know if is beta 4.5, but i saw that i have so many instability and fpu crash using 68040 and 68060 in jit mode, while if set 68030+68882 (always in jit mode) warp3D apps run much better and more stable.

Always on standard Workbench 3.1.

You need to "know" if it is beta before posting here..

[Seiya]

i search for testing only, the lastest fix of winuae 4.5 b14 (if yet available)

Originally Posted by Toni Wilen

You need to "know" if it is beta before posting here..

i intended "i don't know if it is a bug of WinUAE".

[AMIGASYSTEM]

"DiskMag The Vague" works with all v45.0 betas, tested with b13, b14, b15 and b16.

Works well with 040/060 FPU with Voodoo 3 and UAE Zorro III video cards, does not work with Picasso IV card.

Test Video: The Vague (OS 3.1 base 040/FPU Voodoo3)

[Zarnal]

This is beta thread, only for new bugs/issues introduced with new beta versions of WinUae...

For others problems, you can post directly in " Support WinUae " for issues unrelated to new betaversions.

[Zarnal]

Originally Posted by Toni Wilen

It needs 68000 undefined behavior update. Blitter update simply made old bug visible.

I understand better now. I didn't realize that this was an old CPU bug causing the problem.

Originally Posted by amilo3438

As temporary solution just use 68010 ! (it doesn't freezes the demo)

Thanks.

[James]

Originally Posted by AMIGASYSTEM

"DiskMag The Vague" works with all v45.0 betas, tested with b13, b14, b15 and b16.

Works well with 040/060 FPU with Voodoo 3 and UAE Zorro III video cards, does not work with Picasso IV card.

Test Video: The Vague (OS 3.1 base 040/FPU Voodoo3)

No, that is broken - the background should change and the menu should appear on the left when the text displays.
Could be correct behaviour for Voodoo3 though, someone with real hardware would need to confirm...

[AMIGASYSTEM]

Yes, I confirm that with the Video Card "UAE Zorro III" The Vague can be seen correctly with the menu on the left, with "UAE Zorro III" it works well even in the window (see screenshot).

With Vooodoo3 32Bit it works only in Full Screen in Window it makes the system crash!

[AMIGASYSTEM]

With a Voodoo 3 Video Card and a 16Bit Screen, The Vague works well even in windowed mode but the graphics are uncovered and the texts are hidden, see screendhot.

[Seiya]

the Vague work good also with CybverVision64/3D emulation, but with beta 15/16 when i run with Virge on, i must reset my computer. Windows totally crash. With beta 14 is all ok. this afternoon i tried Voodoo 3 with the lates fix of beta 14 (unfortunately i delete it) and working good so many GL Apps and with great quality. I was really speechless. This evening i try again with first beta 14 release and newer beta, but nothing.

so again. someone has the latest fixed beta 14 version?. I want check again this thing.

ps:
with the latest beta 16 of 24 January is much better, more stable.

however some days ago with beta 14 fixed + voodoo3 i run GLExcess, Glaxium, Chromium, Tuxracer with excellent quality and speed (60 fps). With beta 16 + Voodoo 3 no more working, but with beta 16 + Cybervision64/3D every of these games and app working good.
Now i start again, to retest with voodoo 3 because is strange this thing.