Don't know if this has been reported yet.
I used a certain setup in work (A4000T died, so have a perfect copy of HDD and hardware in WinUAE). Been using same setup for over a year without issue.
However after updating to any of the PPC beta's, Im unable to use UAE.gfx anymore on non-PPC setup. As soon as it starts RTG it locks up completely with no way to get out of it. Have to tell pc to restart.

If I revert to version before beta's its fine. I originally though this issue was me. However its definitely not.

When I get chance I will try and get some logs sorted. I did try yesterday, but it wasn't even giving me logs.

Sorry but total lockup is always OS/hardware/driver problem. You really sure about that? (and don't use fullscreen!)

Tony if I leave my B15 install (running OS 4.1 Classic) in a minimized window then come back to it it hangs the entire emulation, the windows mouse pointer goes to the circle and I have no choice to close the program (it says it has stopped responding). Have you noticed that?

Tony if I leave my B15 install (running OS 4.1 Classic) in a minimized window then come back to it it hangs the entire emulation, the windows mouse pointer goes to the circle and I have no choice to close the program (it says it has stopped responding). Have you noticed that?

Probably same problem which causes pause/F12/etc hang. Nothing to do with PC hanging

I also suffered the hang. In my limited testing something happens (great bug report I know) then if you reset using f12 it will freeze, however if you restart instead It quits properly and you can reload the config and keep going.

I will run creating logs in the hope it happens again to give you something meaningful Toni

Sorry but total lockup is always OS/hardware/driver problem. You really sure about that? (and don't use fullscreen!)

Its because Im in full screen (I ment the emu locks completely and is stopping anything else from being displayed), so we cant use fullscreen anymore, not even on non PPC configs?
I did try it on my other PC, that was windowed and that locks up once RTG starts.

I have found that logging out of windows then back in, forces it to close.
Saves rebooting completely.

On a side note;
Just spent the last 3 hours trying to get it to boot OS4.1. For some reason thats not working anymore, even with my working config.
Tried reinstalling, replacing all files, still not booting, . Get blank screen, stuck on pink, cpu crash and hang or reset loops.

I was using some crazy cycle exact speed though when emulating 68040, if it's all related then great. Will wait for the next beta.

Then it probably is related to 68040/060 ce mode changes. Probably can't be fixed without easy test case.

Quote:

Originally Posted by FOL

Its because Im in full screen (I ment the emu locks completely and is stopping anything else from being displayed), so we cant use fullscreen anymore, not even on non PPC configs?
I did try it on my other PC, that was windowed and that locks up once RTG starts.

No. I meant the very first step when there is any kind of problem is to switch off fullscreen and try again.

If ctrl+alt+del or alt-tab does not work, check that you don't have too high winuae active priority setting. Recent betas can get stuck in situation where 2 CPU cores runs at 100% all the time. This shouldn't happen in next beta anymore.

No. I meant the very first step when there is any kind of problem is to switch off fullscreen and try again.

If ctrl+alt+del or alt-tab does not work, check that you don't have too high winuae active priority setting. Recent betas can get stuck in situation where 2 CPU cores runs at 100% all the time. This shouldn't happen in next beta anymore.

I have to disable RTG card completely to get it to boot.
Switching to window doesn't help.

So active profile to Normal should stop it hanging so I can exit if crashes?
As I have it as Above normal at the moment.

I can't see any difference between double vs triple buffering (and it shouldn't cause any difference).

Just reporting the behavior on my machine (and apparently, Retrofan's too). With triple buffering enabled, 4.0 & 4.1 fail to boot -- with it disabled (no buffering at all -- NOT double buffering), it loads and works fine. It exhibits the same behavior with b16.

Just reporting the behavior on my machine (and apparently, Retrofan's too). With triple buffering enabled, 4.0 & 4.1 fail to boot -- with it disabled (no buffering at all -- NOT double buffering), it loads and works fine. It exhibits the same behavior with b16.

Include winuaelog.txt with and without triple buffering. (EDIT: and config file too, please)