Postby Neurotoxic » Tue Sep 12, 2017 6:43 am
Kroll wrote:I noticed another abnormality, for example on Yopla I press the right mouse button to close or kill some process this menu appears only after a while, with a slight delay?
I've also got this short delay on my Milan040. I thought that was due to the missing power of the 68040 cpu.

So I didn't care about this. Perhaps it's also about the implementation or support of graphic drivers in MyAES. I'm using a ATI Radeon in my Milan040 and realtime resizing of windows just works very well with XaAES. Even realtime moving of a window works without any problems in XaAES and it's also much faster on my Milan than on the Firebee. All the realtime stuff is working with MyAES, too. But it's significantly slower on my Milan than XaAES. I'm not sure why. Perhaps it's because XaAES is a kernel module and MyAES isn't? Or it's due to the support of the VDI and/or graphic drivers that are used by the AES? I'm no programmer so I don't really know. But MyAES is just working very fine and with a suitable speed on the Milan when turning of all realtime stuff. I hope I can test the coldfire version of MyAES very soon. I think that's going to happen at the end of the year. If it's working very well on the firebee I will use MyAES as my default AES on the Firebee in combination with EasyMiNT.

520 ST(M) (TOS 1.02), Falcon030 (16 MHz, 16 MB RAM, CF-Card, MiNT & MyAES), Milan040 (25 MHz, 48 MB RAM, EasyMiNT 1.90), Firebee, PowerMac G5 Late 2005 (2 x 2,3 GHz, Mac OS 10.5), iMac 4K Late 2015 (intel Core i7 4 x 3,3 GHz, Mac OS 10.11.6), IBM XT SFD (640 KB RAM, DR DOS 6.0), Compaq LTE 5300 (Pentium/133 MHz, DR-DOS 7.03), AT-PC (Cyrix 6x86L/200 MHz, Windows 98 SE/MS-DOS 6.22 & Windows 3.11)