[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: XaAES
- To: mint@atari.archive.umich.edu
- Subject: Re: XaAES
- From: Johan Klockars <rand@cd.chalmers.se>
- Date: Tue, 23 Jun 1998 02:57:52 +0200 (MET DST)
- In-reply-to: <Pine.MNT.3.96-MiNT.980622222232.215F-100000@bluto> from "Jo Even Skarstein" at Jun 22, 98 10:36:32 pm
> > I've uploaded a small test archive (/pub/XaAES/xa7tst2.lzh), where the
...
> > If someone out here wants to help out again (I sure hope so), this mailing
> > list is still running...
>
> I'm tempted to give it a try, but I'm also tempted by oAESis... Is
;-)
> there any chance that the XaAES-looks will be moderated a bit? I would
> like to have a spiced-up AES, but I think XaAES stretches it a bit too
What was the latest XaAES version you saw?
The looks changed rather significantly for beta6 or beta7.
If it's just the widget images you dislike, those are very simple to change.
I've now squashed another bug, by the way. PROGDEFs were assumed to follow
the Lattice C calling conventions (d0-d1/a0-a1 destroyed), but for example
GEMBench modified register a2, which caused the system stack to be
relocated to a place right in the middle of the program code...
Before I upload another version, I'll do something about rsrc_gaddr, though.
If anyone tests XaAES, please let me know what programs have problems
with it. Many things seem to run just fine, but when something goes wrong
it's usually serious enough to bring down MiNT as well for me (no memory
protection on '040s yet)...
It's possible to launch XaAES under MonST if you run it from the desktop,
as I always do. I've kept all the symbol information in the test versions,
so it's easy to interrupt the execution at any time and set a break point
at a specific place.
IME, most problems result in bus errors and if you run into one of those
inside the XaAES code itself, I'd very much like to know where. Just move
up a couple of pages in MonST to find the nearest function label.
If you have written an program yourself that uses the AES, it shouldn't
be very hard to figure out what (if anything) goes wrong under XaAES.
--
Chalmers University | Why are these | e-mail: rand@cd.chalmers.se
of Technology | .signatures | johan@rand.thn.htu.se
| so hard to do | WWW/ftp: rand.thn.htu.se
Gothenburg, Sweden | well? | (MGIFv5, QLem, BAD MOOD)
- Follow-Ups:
- Re: XaAES
- From: Jo Even Skarstein <joska@nuts.edu>