From mint-bounce@lists.fishpool.fi Sun Apr 10 21:01:47 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] TosWin2 problem with latest XaAES From: Odd Skancke Reply-To: ozk@atari.org To: mint@fishpool.com In-Reply-To: References: Content-Type: text/plain; charset=UTF-8 Date: Sun, 10 Apr 2005 20:56:44 +0200 Message-Id: <1113159404.8897.2.camel@fedora> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) X-MIME-Autoconverted: from 8bit to quoted-printable by smtp220.tiscali.dk id j3AIw4gg061750 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: ozk@atari.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=1.1 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, RCVD_IN_SORBS X-Spam-Level: * Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j3AJ1hqf012090 Hi, søn, 10,.04.2005 kl. 19.53 +0200, skrev Martin Tarenskeen: > Hi, > > After several crashes I finally have the latest XaAES version from CVS > running. (Nice fileselector !). Thanks ;-) > > The problem I had at first appeared to be my homemade English translation > of Toswin2's (version 2.6) toswin2.rsc file. But with the new XaAES my > system crashes with a message like this: > > pid 98 (toswin2): XaAES: ../trnfm.c, 867, fix_rsc_palette(): kfree o 0x2E28104: invalid S?_MAGIC! > FATAL ERROR. You must reboot your system. > > But after reinstalling the original German rsc file, everything is fine > again. But I want my English version back. I think the standard language > for all FreeMiNT projects should be English anyhow. > > I'm not sure where the problem is: XaAES, TosWin2, or maybe Intrface (that > I used to translate toswin2.rsc) produces incompatible rsc files ?? > This is a bug I'm trying to figure out now. There is a serious bug which causes HighWire to crash on certain pages too, and I think that is linked to what you report here. Hopefully I will be able to figure it out soon.... regards Odd Skancke