EUAE automatisch auf der Workbench zentrieren ?

[FlynnTheAvatar]

Hi smarkusg,

Thanks for the info regarding e-uae.

About the IMP3 crashes, it also crashes without CPUInfo_docky. Or without AmiDock. AmiDock just makes the bug show itself much faster. But I got a decent stacktrace today, maybe I can figure out where in PtReplay the issue is.

[smarkusg]

We're straying a bit from the UAE thread but the IMP3 problem may be a bit more complicated than the ptplay ptreplay libraries themselves.
I spent a while today testing a few things.
I have a copy of the sam460ex Amiga OS4.1FE update 1 emulation - no problems with IMP3. I don't even have problems with CPUInfo_docky/AmiDock if IMP3 is running.
Something seems to be messing up the OS4.1FE update 2 kernel and topic related to (m64k)?
If you have the possibility to run the system with Amiga OS4.1FE update 1 or some developer it might be worth checking.
Emulation is not always a good way to debug and in my case I only have that possibility.

[Joerg]

I had cpuinfo_docky added to AmiDock. In this case it is obvious that a CPUInfo.CPUTask system process is created with a priority of -127.
From the logs it seems to be the same for you, but I'm guessing you are using a different version. (CPUDock_idleTask (pri -127)
After running IMP3 and a while, the same problems as you start to appear. Programs hang, the system crashes.
After checking through the ‘top’ you can see that the CPUInfo.CPUTask process starts to consume system resources terribly. You don't see this right away only after a certain period of time.
In my case CPUInfo.CPUTask consumes up to 80-100% of the CPU.

I don't know those "CPUDock" or "CPUInfo" tools specifically, but nearly all CPU monitor tools, dockies, etc., on AmigaOS install a priority -127, which is the lowest possible priority on AmigaOS, busy loop task and use the CPU time consumed by it for the CPU usage display: 100% - time used by the busy loop task.
Only exceptions may be my CPUTemp.docky, my "top" and Capehill's "Tequila" shell tools, which work differently.
If you use 2 of them at the same time, with one of them being my "top" or Capehill's "Tequila", they will display nearly 100% CPU usage for the other, busy loop pri -127 based, tool. 100% for the busy loop task if the rest of the system is completely idle.

[smarkusg]

I checked again. Yes, you are right as usual. I am using your ‘top’.
The CPUInfo_docky I use incorrectly shows/draws my CPU usage when I use IMP3 on Qemu Pegasos 2 and AmigaOne.
On sam460ex it shows the correct values. ‘top’ on all QEMU machines shows cpu load with CPUInfo_docky running 80-100%.

[smarkusg]

@FlynnTheAvatar
If you can, check out the native 68k PT-Player application

https://github.com/apolkosnik/ptreplay_ ... /PT-Player

If there is no problem with PT-Player and Amidock then ptplay and ptreplay are correct.

[Maijestro]

@FlynnTheAvatar

Ja wir sind etwas von eigentlichen Thema abgekommen, da ich aber imp3 öfters verwende habe ich gestern ein paar tests durchgeführt. smarkusg gab mit den Tip das die Addons von AmiDock schuld sein könnten. Hab dann mal alle Addons für AmiDock deaktiviert Netzwerk/CPU/GFX/RAM und siehe da AmiDock friert beim starten bzw. verwenden nich mehr ein.

@smarkusg

PT-Player arbeitet ohne Probleme unter AmigaOs4.1, hab das gerade getestet.