WinUAE 4.4.0 beta series

[falken]

Originally Posted by Toni Wilen

"Disappeared" = means nothing. Does old version still work? You sure you don't run it as admin because drag and drop between different security levels is not allowed by Windows.

Ok, I was running WinUAE with administrator rights. Sorry, but I did not know that this caused the drag and drop option to not be functional.

[DamienD]

Toni,

One small issue I've noticed with the beta series is as follows:

If I play a game with say certain KS, then if I go into the GUI, change KS and reset, the old KS is still loaded and not the newly selected one.

[DamienD]

Hi Toni,

I'm going through the games I've configured and testing complex ones with the latest beta3.

A game that crashed about 10 - 20 seconds after starting to play with a software failure is Hexen from Heretic & Hexen.

In 4.3.0 it works perfectly without issues.

I'll send you a PM with a pre-setup .HDF and configuration file.

[Toni Wilen]

Originally Posted by DamienD

Toni,

One small issue I've noticed with the beta series is as follows:

If I play a game with say certain KS, then if I go into the GUI, change KS and reset, the old KS is still loaded and not the newly selected one.

Did it happen with previous beta? Which kind of reset? keyboard or GUI?

Originally Posted by DamienD

Hi Toni,

I'm going through the games I've configured and testing complex ones with the latest beta3.

A game that crashed about 10 - 20 seconds after starting to play with a software failure is Hexen from Heretic & Hexen.

In 4.3.0 it works perfectly without issues.

I'll send you a PM with a pre-setup .HDF and configuration file.

Always those huge non-Amiga originals that are impossible to debug..
I could only duplicate it once..

So..

- does it happen only if JIT is active?
- without MIDI music?
- Even more larger stack?

Originally Posted by falken

Ok, I was running WinUAE with administrator rights. Sorry, but I did not know that this caused the drag and drop option to not be functional.

It is not that commonly known but can be easily duplicated with any Windows application if explorer has different security level than the application.

[DamienD]

Originally Posted by Toni Wilen

Did it happen with previous beta? Which kind of reset? keyboard or GUI?

GUI reset.

Will test with beta 1 & 2 also and get back to you

Originally Posted by Toni Wilen

Always those huge non-Amiga originals that are impossible to debug..
I could only duplicate it once..

So..

- does it happen only if JIT is active?
- without MIDI music?
- Even more larger stack?

I try to avoid using JIT usually, but the problem here is that you need JIT otherwise the game is sooooo slow / unplayable.

Been a while, I can't remember; I think I enabled MIDI music but can try switching that off.

Will also try a different stack size.

[DamienD]

Originally Posted by Toni Wilen

Did it happen with previous beta? Which kind of reset? keyboard or GUI?

Originally Posted by DamienD

GUI reset.

Will test with beta 1 & 2 also and get back to you

Tested now and this occurs with all 4.4.0 betas.

[DamienD]

Originally Posted by Toni Wilen

Always those huge non-Amiga originals that are impossible to debug..
I could only duplicate it once..

So..

- does it happen only if JIT is active?
- without MIDI music?
- Even more larger stack?

Originally Posted by DamienD

I try to avoid using JIT usually, but the problem here is that you need JIT otherwise the game is sooooo slow / unplayable.

Been a while, I can't remember; I think I enabled MIDI music but can try switching that off.

Will also try a different stack size.

If I switch off JIT then it doesn't occur.

If I leave it on the game crashed 3 times out of the 3 times for me when trying to kill the first two enemies:



As mentioned, you need JIT for this game otherwise it's too slow.

When turning off MIDI or setting an even larger Stack size the crashes still occurred.

[Toni Wilen]

This is too strange because nothing in JIT has changed and that guru makes no sense either (It would make sense if last digit would have been 2 or higher) and there is no weird log messages, final reset is done by KS ROM so most likely something called Alert() but finding the culprit in JIT mode can be quite painful, especially when it can't be duplicated easily.

It can be FPU related either because Doom engine based games don't use FPU.

(btw, non-JIT and JIT seems to hit frame limiter because I can't see any speed differences. So one standard solution is to buy a better PC )

--

btw2, Amix crash should be fixed.

[DamienD]

Originally Posted by Toni Wilen

This is too strange because nothing in JIT has changed and that guru makes no sense either (It would make sense if last digit would have been 2 or higher) and there is no weird log messages, final reset is done by KS ROM so most likely something called Alert() but finding the culprit in JIT mode can be quite painful, especially when it can't be duplicated easily.

It can be FPU related either because Doom engine based games don't use FPU.

Yes, very strange indeed given what you've written.

Also in 4.3.0 it's never crashed once.

[DamienD]

Good news Toni

I've played around with settings and now out of 30 tries it only crashed twice.

Previously it would crash 9 out of 10 tries for me...

What I did was change:

... CPU 68040 --> 68030
... FPU --> None
... ticked "More compatible"

Speed of the game is exactly the same as far as I can see.

I'm happy with this result, much better than before

[Toni Wilen]

I starts to sound like there is some check in the code that gets confused by something and causes the crash. It would not be the first time..

Full sources perhaps would help to debug this more.

[Pentad]

Toni,

AMIX had a panic with Beta 3. I have uploaded my log, config, and a screen capture. Also, I responded to your PM.

Thanks for all your hard work!
Mark

[Zarnal]

Originally Posted by Pentad

Toni,

AMIX had a panic with Beta 3. I have uploaded my log, config, and a screen capture. Also, I responded to your PM.

Thanks for all your hard work!
Mark

Hi,


try WinUae.7z.

[DamienD]

Originally Posted by Zarnal

Hi,


try WinUae.7z.

Might help if you told Pentad where these interim releases are located: http://www.winuae.net/files/b/winuae.7z

[Pentad]

Thanks for the help Zarnal and DamienD!

Same panic though.

[DamienD]

Hi Toni,

I'm just checking some settings in a few of my configuration files...

I've just had 2 x crashdumps in the space of 5 minutes.

This is when loading a configuration and then flicking through:

• CPU and FPU
• Chipset
• ROM
• RAM
• Floppy drives
• Display
• Game ports
• Filter
• Disk swapper
• Miscellaneous

Both crashdumps in The Zone! for you.

[Toni Wilen]

Originally Posted by DamienD

I'm just checking some settings in a few of my configuration files...

I've just had 2 x crashdumps in the space of 5 minutes.

This probably is not beta specific. It is in generic GUI code doing invalid access and nothing GUI related has changed. Unfortunately it also does not help to find out what goes wrong..

[DamienD]

Sorry for posting in the beta thread... I've never experienced this crash so much with any stable releases.

I've just finished checking 90 configuration files; WinUAE crashed 17 times whilst flicking through the sections detailed in post #76

I've updated the .ZIP file in The Zone! in case it helps.

[Toni Wilen]

Originally Posted by DamienD

Hi Toni,

I'm just checking some settings in a few of my configuration files...

I've just had 2 x crashdumps in the space of 5 minutes.

This is when loading a configuration and then flicking through:

• CPU and FPU
• Chipset
• ROM
• RAM
• Floppy drives
• Display
• Game ports
• Filter
• Disk swapper
• Miscellaneous

Both crashdumps in The Zone! for you.

Can you narrow it down? (=reduce number of panels that need to be opened to duplicate it)

Especially are panels that are config specific (like ROM) required?

Does it only happen if you first load some config?

EDIT: Already freed windows dialog entry handle is in list which probably is related problem. More debugging later..

[DamienD]

Originally Posted by Toni Wilen

Can you narrow it down? (=reduce number of panels that need to be opened to duplicate it)

Especially are panels that are config specific (like ROM) required?

Does it only happen if you first load some config?

Hi Toni,

I can't really narrow it down as it happens randomly.

I was checking configurations so I'd first load one, then click through each of the sections in the order listed etc. and then load of the next configuration file / repeat going through the sections.

Originally Posted by Toni Wilen

EDIT: Already freed windows dialog entry handle is in list which probably is related problem. More debugging later..

Oh, so you might have found the culprit?