[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[MiNT] XaAES and CTPCI (was: trunk 0908)



Lars Schmidbauer wrote:

> Hi,
>
> > 1. The system freezes reproducable (needs reset then) with the errormessage
> >    attempt to restart XaSYS pid 102 (XaSYS) Bus Error: User PC 112582C, Address 711C0504 (basepage: 10F00B0 text: 10F01B0 dat
> >    when i open the window context menu (rightclick on CLOSER) and move the mousepointer over the menu-options.
> >    Perhaps when a sub-menu is opened??
>
> Sometimes XaAES crashes without errormessage when i click on About XaAES or Process. It seems that
> this mostly happens when the mousecursor is moved a little bit while clicking, but i'm not sure.
>
> > 2. Exactly the same error occures (reproducable) when i use the horizontal slider in XaAES Taskmanager.
> >    Strange: Moving the slider to the right works normal, but when i move it back to the left the error occures.
> >    The vertical slider works correct. The same happens in XaAES menu/Process/System (Log) window.
>
> To be more precise: If i use the hor. slider (grab with mouse and move it), the error occures when
> moving it back to the left. Using the arrowbuttons is the same. But when i click on the scrollbar
> (background of slider area) everything works ok, window scrolls correct to right/left side, no error.
> This must be a problem with XaAES because scrolling works correct with TeraDesk and every other app
> i tested. It's still present with trunk-23082010.
> I know that there's no problem on Aranym (tested myself), but i hope this can be fixed.
> Is there anybody who could reproduce it yet?
>
> One more: With CTPCI/Radeon, XaAES themes (ext. textures) don't work. In xaboot.log there's an
> errormessage for every image which was found in /xaaes/img/hc/:
>
> xaaes_sysfile: check if '\d\MINT\1-17-0\XAAES\img\hc\wtitle.img' exists - return =3D 0
> load_img: '\d\MINT\1-17-0\XAAES\img\hc\wtitle.img'
> load_img: file \d\MINT\1-17-0\XAAES\img\hc\wtitle.img
>   depacking...OK!, no palette
> pixel format:screen:planes=3D32 pixel-format=3D-1 src:8
>
>  unknown pixel format:screen:planes=3D32 pixel-format=3D-1 src:8- cannot transform from=3DFFFFFFFF to=3DFFFFFFFF

Hm - so it seems you have a new pixel-format or the odd-stack-issue reappeared.

I compiled a version that logs vrocpyfm and displays the stack:

http://mitglied.multimania.de/zabruder/files/system/xaaes040.zip

Run it, let it crash and send me the complete bootlog. Thanks.


-Helmut