A New 68k Emulator
Posted by Michael on 23 May 2005, 20:34 GMT
For the past few years, the perpetually popular Virtual TI has been declining in usefulness with the release of newer, unsupported calculators such as the TI-89 Titanium and Voyage 200. Now there is a new emulator that aims to emulate the 89, 89 Titanium, 92, 92+, and Voyage 200: TiEmu. The v2.0 release candidate of TiEmu has just been released by Romain Liévin and Kevin Kofler. This emulator will thoroughly emulate any of the 68k calculators with all the fancy features we've come to expect in an emulator, such as saving states, linking, and debugging. But wait, there's more! TiEmu is multiplatform, with Linux and Windows versions as well as a Mac OS X port in progress. The Windows version requires the GTK+ package.
As this is a release candidate, please report any bugs to the authors.
|
|
Reply to this article
|
The comments below are written by ticalc.org visitors. Their views are not necessarily those of ticalc.org, and ticalc.org takes no responsibility for their content.
|
|
Re: A New 68k Emulator
|
Rakka
|
When's the OS X version going to be released?
|
Reply to this comment
|
23 May 2005, 22:03 GMT
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Re: Re: Re: Re: Re: Re: Re: Re: A New 68k Emulator
|
JcN
(Web Page)
|
d00d!
The Mac file structure and organization is significantly different from the structure and organization of Windows files, making portability difficult, not some invisible task! Mac OS uses HFS and HFS+, whereas Windows uses FAT. Mac OS uses 32-bit Creator and Type strings in it's file header to identify parent applications and types of files respectively, whereas Windows uses 3-4 character extentions in the name string in addition to some file header information to do the same. Mac OS splits all of it's files into separate data and resource "forks" for easy storage (although this isn't visible through the GUI), whereas resources and data are crammed into one file in Windows. All of this can't be ignored--you need extra 3rd party software to read Windows files, and even they cannot read ALL Windows files (i.e. Windows executables cannot be converted or read yet because the Windows-based system traps, the references to DLLs, the difference in chip architectures, etc., cannot be effectively emulated). In short, making up for differences in FSs hasn't been reduced to a background task yet.
|
Reply to this comment
|
2 June 2005, 03:36 GMT
|
|
1 2 3 4
You can change the number of comments per page in Account Preferences.
|