From mint-bounce@lists.fishpool.fi Sat Oct 16 22:57:11 2004 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Date: Sat, 16 Oct 2004 22:55:13 +0200 (CEST) From: Frank Naumann X-X-Sender: fnaumann@muecke.local To: mint@fishpool.com Subject: Re: [MiNT] FreeMiNT 1.16.1 beta release In-Reply-To: Message-ID: <20041016224933.N72899@muecke.local> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scan-Signature: 358e2e207984a4790e33c6cf28180fcd X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: fnaumann@cs.uni-magdeburg.de 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.0 tagged_above=-50.5 required=3.8 tests=BAYES_00 X-Spam-Level: Hello! >> So it's already known since the 1.16.0 beta release. Would be nice if you >> can submit a bugreport into the bugtracker so we developer are informed >> about the bugs too :-) > > Well, not everyone uses betas. :o) But he said it stopped working since XaAES is a kernel module. So he tried before the 1.16.1 beta release and don't reported it. So I or Ozk didn't had a chance to fix it as we both don't own a Calamus license. >> Beside from that this Calamus violates the GEM convention as it do a >> wind_update AES call without calling appl_init() first. > > Meaning it's not a bug in XaAES? Yes, it's a bug in Calamus and need either a workaround in XaAES or a correction in Calamus. I think the workaround in XaAES is the faster solution (XaAES already have lot of workarounds for buggy AES applications). Regards, Frank -- ATARI FALCON 060 // MILAN 060 ----------------------------------------- http://www.cs.uni-magdeburg.de/~fnaumann/ e-Mail: fnaumann@freemint.de