WinUAE 2.1.0 beta series (was 2.0.2)

Have somebody test winuae with a JIT configuaration and 68040 ?I have a single core CPU AMD64 3000+ a winuae 2020b11 and later have very slow fileaccess and so boot is unusable slow.I notice that file system is problem because when i switch JIT off for test it boot lots faster.when i later switch JIT on i notice the benchmarks for CPU and openconsole in sysspeed give same speed values as before but solid window move is unsmooth.When i do the drive bench there come very very low values in both hardfile and directory file system.

[Mclane]

Bernd, I suspect you may be about to get a Toni roast, he's not overjoyed about non realistic configurations based upon JIT settings.

If you have a favourite plot or want cremation it may be a time to say now

[Toni Wilen]

Only problem is lack of configuration and logs (and I already asked for those privately few days ago )

Probably something to do with priorities, smp/dual+ core machines work very differently when one thread uses all CPU time compared to single cores.

[CFou!]

i am just testing: WinUAE v2.0.2 beta 12

here curiously it is very slow as if JIT option was disabled

file accesses are very very slow.....


config:
INTEL Core 2 Duo E8400 3Ghz
+4go+xp pro sp 3

[thomas]

Originally Posted by CFOU!

i am just testing: WinUAE v2.0.2 beta 12

here curiously it is very slow as if JIT option was disabled

file accesses are very very slow.....

Same here, already since beta 10.

Contrary to

Originally Posted by Toni Wilen

EDIT: b10 can run (possibly very) slowly when there are lots of interrupts happening (ce-modes only), winuae.zip in same directory should fix that problem.

for me beta 10 is the last version which runs at full speed. The msvs2010 version as well as winuae.zip and beta 11 and 12 all run very very slowly.

[Toni Wilen]

http://www.winuae.net/files/b/winuae.zip is now 2008 compiled. Still slow?

[Cosmos]

Yes, Toni, and slower than with msvs2010 here...

[thomas]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae.zip is now 2008 compiled. Still slow?

Unfortunately yes. But it seems related to (hard) disk access only. Onscreen LEDs say that FPS is at 50 through 51, CPU usage is at 60%, sound is in the white range. But when Workbench comes up, I can see each icon appear seperately and the AISS script in WBStartup which only makes a few assigns runs longer than five seconds (comes up with the well-known requester "AISS is still running, should I wait a little longer ?").

[Toni Wilen]

Fix attempt #2. (same date, check that file time is newer)

[CFou!]

Originally Posted by Cosmos

Yes, Toni, and slower than with msvs2010 here...

idem

[Toni Wilen]

Hmm... Did you even test because above version is again 2010 compiled..

[thomas]

Originally Posted by Toni Wilen

Fix attempt #2. (same date, check that file time is newer)

CPU% is now always above 80% and performance is even slower than before. AmiDock needs ages to load.

[Maren]

Here's a mask problem. Pay attention to the bottom of the screenshot, looks like the white lines in scanlines.png are being turned into gray lines or something.

Doesn't seem to happen with all the resolutions, but 320x512 and 640x512 are definitely affected.

Get both logs and config here

Regards.

[Toni Wilen]

Originally Posted by thomas

CPU% is now always above 80% and performance is even slower than before. AmiDock needs ages to load.

Any numbers? (1s? 10s?) "Slower" does not really tell much.

[thomas]

I'd say 20% slower, similar to the increment of CPU load.

[Toni Wilen]

http://www.winuae.net/files/b/winuae.zip updated again (25.02.2010) This really should fix it..

[ceztko]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae.zip updated again (25.02.2010) This really should fix it..

Ehi, git-bisect could have helped here

[Photon]

Just installed DX9 Aug. 'D3D9 initalization failed.' when I change to DirectX in Misc. panel.

Log and config attached.

Thinkpad T40, Pentium M 1.3 GHz, ATi Radeon Mobility 7500 with latest supported drivers from Lenovo.

Maybe it simply uses some features not supported by the laptop?

[Toni Wilen]

Originally Posted by Photon

Maybe it simply uses some features not supported by the laptop?

Yes, no pixel shader support. (ATI 8000 series is probably oldest that works)

32-589: D3D9:POW2 NPOTCONDITIONAL ALPHA DYNAMIC
32-589: D3D9: PS=0.0 VS=1.1 2048*2048*0 FS 16-bit

(something is not correct because there should have been better error message..)

[thomas]

Originally Posted by Toni Wilen

This really should fix it..

Yep, back to normal.