From mint-bounce@lists.fishpool.fi Thu Aug 12 12:04:45 2010 X-Authenticated: #3273601 X-Provags-ID: V01U2FsdGVkX19pzJBkiutpzCGtH1EkvZTNWy/QHm6xtO26d4TvRg lOoudJH0wM11AM To: From: Lars Schmidbauer Subject: Re: [MiNT] Daily builds Trunk 0908 X-Mailer: MyMAIL Rev:1.94.13761 (Atari/(STiK/STinG/GlueSTiK)) X-Hardware: Atari Falcon/CT60 MIME-Version: 1.0 Date: Thu, 12 Aug 2010 17:58:28 +0200 (MET) Content-Type: text/plain; charset="UTF-8" X-Priority: 3 X-MSMail-Priority: Normal Message-Id: <000863d8.019db262fcc4@mail.gmx.net> X-Y-GMX-Trusted: 0 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: latzmaster@gmx.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o7CG4iQS021700 Hello, >> i disabled everything in AUTO folder and every program and desktop started from xaaes.cnf; the error still >> occures reproducable but the errormessage has slightly changed (only Address is the same as before): >> >> attempt to restart XaSYS pid 102 (XaSYS) Bus Error: User PC 10699D0, Address 711C0504 (basepage: 1034254 text: 1034354 data: 10 >> >> There's more: In XaAES menu/Launch.../Fileselector, the masks menu option is not displayed (but selectable) >> and if i open any of the 3 pulldown menus the system freezes with exactly the same error(s). >> But when the fileselector is called from TeraDesk or any other program, everything works correct. > I guess you use similar HW as this: > falcon 030, ct60(66mhz), 14mb st ram, 256mb tt ram,ctpci Yep, Falcon030/CT60(80 MHz), 14 STRAM, 128 TTRAM, CTPCI/Radeon 9250. > This is from Pawel Goralski who also gets mysterious issues. There may > be lots of reasons for this, but I never heard similar by anyone with > other hardware. I read this. So can anybody else with a similar hardware confirm this? Perhaps it's a problem with XaAES running without NVDI (and perhaps fvdi handles something different than NVDI). >You may also try without desktop but I doubt it will tell us much. Sure i tried this, too. No difference. Lars