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

Re: [MiNT] 68k binary emulator

Hello Peter

This is a very good solution as I remember,  this was a concept idea of OTOSiS
never finish.

Notice if it's slow its not very important because new CPU are fast enough even
without JIT running correctly 68K application we use it.
I would like to know about portabilility of it? Do you manage something with
system address (like timer). Is it a work from scratch or something related
with other project. I think to the Qemu project that do this sort of CPU
emulation to run on PPC x86 application through wine, and now there is already
an coldfire emulator avaible.

I'm very interesting in your job. I going to look for opengl crash in Kronos
(there is possible bug)

Olivier

> Hi,
>
> Lately I've been working on a rather silly project which I thought I'd
> share with you. Basically it's a 68000 binary emulator, which launches
> an application in an emulated environment, but tunnels OS calls etc.
> to the host OS.
>
> Why on earth would anyone want to do this? Well, today it's fairly
> pointless, but let's say someone ports the kernel to PPC, Arm or
> whatever. An emulator of this kind could then be used to provide some
> basic degree of compatibility with 68k applications.
>
> Feel free to try it: http://hem.passagen.se/shoggoth/misc/emu68k.ttp
>
> Usage:
>
> ./emu68k.ttp <binary.prg>
>
> Compatibility is rather low at the momenty, but I think it can be
> improved a lot.
>
> Successfully tested applications:
>   - AtarICQ
>   - AtarIRC
>   - Atari Works
>   - Truepaint
>   - Kronos (although the image loading takes several minutes, and the
> OpenGL test fail)
>   - SuJi
>   - MyMail
>   - Resource Master 2.11
>   - aFTP
>   - Hexedit
>   - QeD (sluggish response in menues etc.)
>
> Please note that this is more of a toy than a finished concept. Also
> note that running this on anything less on a 060 would be a (major)
> waste of time. My C-language skills are crap at best, so save
> important work etc. before you try it.
>
> -- PeP
>
>
>


--