WinUAE weird problem.

[Anubis]

You have minimum and maximum CPU rates, just make sure it is set for both 100% (or very close) when on AC.

When I was testing this, only older computers did not have this issues with JIT.

[Toni Wilen]

Nothing is guaranteed in "power saver" mode but setting low frequency high only makes useless heat..

Find some (overclocking) utility that shows CPU frequency in realtime to see what actually happens.

[Anubis]

The real question would be how JIT settings hits power setting mode on CPU.

[Leandro Jardim]

Originally Posted by Anubis

You have minimum and maximum CPU rates, just make sure it is set for both 100% (or very close) when on AC.

When I was testing this, only older computers did not have this issues with JIT.

This is what I have done before: set AC power minimum/maximum CPU rate to 100/100 and battery power min/max CPU rate to 30/100. It doesnt works. All other applications and emulators I use works accordingly to the advanced power settings configuration that I put there and work well, only WinUAE that not.

Originally Posted by Toni Wilen

Nothing is guaranteed in "power saver" mode but setting low frequency high only makes useless heat..

Find some (overclocking) utility that shows CPU frequency in realtime to see what actually happens.

Yes, it's because of that which I have set battery power minimum CPU rate to 100% and after that to 30%.

Originally Posted by Anubis

The real question would be how JIT settings hits power setting mode on CPU.

Yes good point, this is exactly where I would like to did reached before: why releases after WinUAE 2.9.0b25+ affects the power settings of the CPU, when b24- does not!

[Toni Wilen]

I'd still like to see some real time CPU frequency information because power saving can work (and has been reported previously to work) really strangely when CPU usage is very irregular (lots of CPU usage then short waits etc..) and to confirm CPU isn't throttling.

One possible reason for this change may be compiler update but I don't remember any details. (Perhaps it changed how some newer CPU instructions are used or something like that)

[Anubis]

What would be a good tool to get you CPU data recorded with??

[Leandro Jardim]

A strange but good thing happened, I formatted my notebook and installed Windows 10 from scratch and now WinUAE is working fastly again. I think it should be a graphics driver problem, because all other Windows apps are running at the same speed as usual.

Thanks for the replies and sorry everyone for the time spent on a useless problem, unless of course if my notebook get back with that problem again. Sorry also mainly for jdog, which I interrupted his conversation with Toni.

But I also want to "talk" with Toni, I have an old "problem" with WinUAE that is coming back and I dont know why, is the a2065 emulation which cant connect to nowhere when I enable JIT. I only ask that you, Toni, analyze the logs that WinUAE generated, to see if there is some problem with WinUAE or with my configuration. The logs were generated by WinUAE 3.3.0b14 (official) with the "-a2065log2" parameter. And the problem disappears when I disable JIT.

[Toni Wilen]

Originally Posted by Leandro Jardim

A strange but good thing happened, I formatted my notebook and installed Windows 10 from scratch and now WinUAE is working fastly again. I think it should be a graphics driver problem, because all other Windows apps are running at the same speed as usual.

Thanks for the replies and sorry everyone for the time spent on a useless problem, unless of course if my notebook get back with that problem again. Sorry also mainly for jdog, which I interrupted his conversation with Toni.

Reinstall. Or at least "buy a new PC" always work!

But I also want to "talk" with Toni, I have an old "problem" with WinUAE that is coming back and I dont know why, is the a2065 emulation which cant connect to nowhere when I enable JIT. I only ask that you, Toni, analyze the logs that WinUAE generated, to see if there is some problem with WinUAE or with my configuration. The logs were generated by WinUAE 3.3.0b14 (official) with the "-a2065log2" parameter. And the problem disappears when I disable JIT.

As I said (somewhere), it is "new" JIT problem -> nothing happens until Frode (or someone else who knows how it works) fixes it