WinUAE 3.2.0 beta series

[waldiamiga]

Originally Posted by AMIGASYSTEM

I too have the same problem with Win7 32 Bit:

JIT is off, Z3 mapping mode is Real, set picasso_iv_flash.rom in RTG Boards (before I had Rom disablet)

EDIT

Now everything is back to normal, to activate the graphics card Picasso IV, i replaced "Picasso IV Zorro III" with "Picasso IV Zorro II" in "RTG Graphics Card"
With "Picasso IV Zorro II" the graphics card Picasso IV remains active, also with the Rom in RTG Boards disabled

Yes, it works in Picasso IV Zorro II. Why doesn't work Zorro III option?

[Toni Wilen]

Originally Posted by waldiamiga

Yes, it works in Picasso IV Zorro II. Why doesn't work Zorro III option?

See above, config file is needed.

I use wazp3d. If i switch to winuae 64 bit the soft3d.dll works also with it?

[waldiamiga]

Originally Posted by Toni Wilen

See above, config file is needed.

My config file.

[AMIGASYSTEM]

On OS 3.9, i noticed that now even the "RTG Graphics UAE Zorro III" me no more the Resolutions Graphics "UAE" in screenmode.

[Toni Wilen]

Originally Posted by AMIGASYSTEM

On OS 3.9, i noticed that now even the "RTG Graphics UAE Zorro III" me no more the Resolutions Graphics "UAE" in screenmode.

You wanted "Real" Z3 memory mode but you don't have enough virtual address space. Switch to to UAE or automatic. (or switch to 64-bit Windows)

Available memory depends on too many things, there is no guarantee it stays the same.

[Toni Wilen]

Originally Posted by amadama

- Added support for 68020+ CPU floating bus data when clock chip is not connected (Not yet correctly emulated, need accurate CPU cycle sequence and more)

Nothing interesting, CPU accesses to unused clock region gets correctly routed to unmapped memory handler (that returns correct data when 68020 CPU cycle sequence is correct enough)

Originally Posted by waldiamiga

It does not work Picasso IV in AmigaOS 4.1 FE. Cards can not be seen in ScreenMode and Picasso96Mode. Beta 16 32bit. On the previous beta it was OK.

Manually edit your config file and delete line "picassoiv_rom_file=:NOROM". I have no idea where it has come from (at least recent WinUAE versions won't modify it) but it forced WinUAE to not load P4 ROM.

Next beta has automatic workaround for this.

[AMIGASYSTEM]

Originally Posted by Toni Wilen

You wanted "Real" Z3 memory mode but you don't have enough virtual address space. Switch to to UAE or automatic. (or switch to 64-bit Windows)

OK thanks now goes well with " UAE or Automatic", you have switch on "Real" as suggested in the past, because I have a Windows system to 32Bit

Toni, a few days, I had asked for a clarification here, when you have a little time, if you can get an answer, thank you.

[Toni Wilen]

Originally Posted by AMIGASYSTEM

OK thanks now goes well with " UAE or Automatic", you have switch on "Real" as suggested in the past, because I have a Windows system to 32Bit

"Real" is only needed if you want to run OS4 and have working Z3 boards.

[AMIGASYSTEM]

Originally Posted by Toni Wilen

"Real" is only needed if you want to run OS4 and have working Z3 boards.

Ok thanks Toni, about the problem "Picasso IV Zorro III" cited before, attaching my Fileconfig

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Ok thanks Toni, about the problem "Picasso IV Zorro III" cited before, attaching my Fileconfig

I can't duplicate this. Does it still happen if you disable all Z3 RAM?

[AMIGASYSTEM]

Originally Posted by Toni Wilen

I can't duplicate this. Does it still happen if you disable all Z3 RAM?

If you reset the values of Z3 Fast RAM (values 0) -> OS4.1 does not start (black screen)


The problem is only on Windows 7 32Bit

Same configuration on Windows 7 64Bit Picasso IV Zorro III Cards it works perfectly

[AnnaWu]

Originally Posted by Toni Wilen

I can't duplicate this. Does it still happen if you disable all Z3 RAM?

Picasso IV Zorro III
I have the same problem (WinXP Pro 32-bit) with the new WinUAE + qemu-uae.dll version.
Beta 15 vs. Beta 16 (check the attachment)

PS. It seems, the loading time of the hard drive image on the newer version is slower for me.

[Leandro Jardim]

Originally Posted by AnnaWu

PS. It seems, the loading time of the hard drive image on the newer version is slower for me.

For me, too (Windows 10 64 bit).

I would say more, in overall, the 68k emulation seems slower and the new JIT seems not so fast like the old JIT, for me anyway.

My bugreport is for the 64 bit version, everytime I open a file dialog from WinUAE x64, WinUAE crashes without however generating a dump file.

[Toni Wilen]

No feelings allowed. Only hard numbers, comparisons between versions.

[Leandro Jardim]

I am booting AmigaOS 4.1 FE with a very similar config to that attached in this post, but whenever I enable Legacy VSync for native screens before starting the emulation, AmigaOS boot process stops with a black screen, shortly after the AmigaOS logo.

Without Legacy VSync or with Low Latency VSync the boot process is very fast.

I have Legacy VSync for native screens and and Legacy VSync for RTG screens, both enabled.

WinUAE 3.1.0 have the same problems on my machine, and all logs and configs are attached in this post.

[Toni Wilen]

Originally Posted by Leandro Jardim

WinUAE 3.1.0 have the same problems on my machine, and all logs and configs are attached in this post.

So this has nothing to do with 3.2 betas? In other words, nothing is wrong. (You probably should read first post of this thread)

Don't even think that you can use vsync reliably in OS4..

EDIT: and anything OS4 performance related = will be quite likely to be ignored unless it also happens under m68k AOS.

[AnnaWu]

Originally Posted by Toni Wilen

So this has nothing to do with 3.2 betas? In other words, nothing is wrong. (You probably should read first post of this thread)

Don't even think that you can use vsync reliably in OS4..

EDIT: and anything OS4 performance related = will be quite likely to be ignored unless it also happens under m68k AOS.

You found the reason why Picasso IV Zorro III + OS4x support problems exist on the 32-bit OS?

[Leandro Jardim]

Originally Posted by Toni Wilen

So this has nothing to do with 3.2 betas? In other words, nothing is wrong. (You probably should read first post of this thread)

No I meant it happen with WinUAE 3.2.0 of course, and 3.1.0 too.

Originally Posted by Toni Wilen

Don't even think that you can use vsync reliably in OS4..

So I cant enable RTG VSync.. Worse yet when I enable it together with Native VSync.. And what both options have in common with WinUAE, for it stopping to work in the boot process? And why it works on a real Amiga, that have *real* VSync enabled everytime?

Originally Posted by Toni Wilen

EDIT: and anything OS4 performance related = will be quite likely to be ignored unless it also happens under m68k AOS.

Yes, I know you would say that . But like already said, AmigaOS 4.1 FE runs quite happily on my machine, and thats not the problem here.

I dont need answer, I only want that do you think...

[Toni Wilen]

Originally Posted by AnnaWu

You found the reason why Picasso IV Zorro III + OS4x support problems exist on the 32-bit OS?

Not yet.

Originally Posted by Leandro Jardim

No I meant it happen with WinUAE 3.2.0 of course, and 3.1.0 too.

Which makes it NOT 3.2 SPECIFIC problem -> offtopic here.

Only if problem is NEW/CHANGED/INTRODUCED in 3.2 -> this thread!