Page 90 of 91
Posted: Thu 05 Jul, 2007 12:02 am
by Spencer
Hey Tim, I just wanted to give you a heads up.
Much of Wabbitemu's code runs natively under Linux and a couple guys have started working on a GTK port.
Since our care-level intercalc linking is rather low, you'll be missing out on all that fun, but if you just wanted a good emulator to run natively under Linux you might think about contributing to ours.
If not, feel free to take whatever code you like for your PindurTI port.
http://svn.revsoft.org/wabbitemu/
Posted: Thu 05 Jul, 2007 12:22 am
by Timendus
Thank you very much for the offer, and I'll certainly take a look at it. I am, however, very much a PTI fanboy who loves his emulated HUB and delayed pixels
I see your GTK code is in C though; that would make porting my code to your emulator or visa versa slightly less simple. Anyway, I'll see what I can do with it. I'll release my source soon enough anyway, so if you'd like to use any of that, you'd be welcome.
Signed/unsigned int bug has been fixed by the way; the screen looks lovely now
Posted: Sun 08 Jul, 2007 9:33 pm
by GuillaumeH
Nice work Timendus
I'll be watching which emulator will be the first to enable animated screenshots under Linux (natively).
Posted: Mon 09 Jul, 2007 12:43 am
by __Guest_
This emulator just rules. Saves me time for capturing the screen and making animations.
Posted: Tue 10 Jul, 2007 3:23 pm
by Timendus
I've polished the screen a bit, finished the keyboard and added a few options to the menu. Release details here:
http://kvince83.tengun.net/maxboard/vie ... hp?p=60229
Posted: Sun 25 Nov, 2007 6:55 pm
by driesguldolf
I guess I should post it here, something goes wrong...
If you set a breakpoint, make the break happen and then try to continue running the program the emulator won't let you (neither can you step over). You have to single step it first (I think I've read about this somewhere...).
But it gets weirder, if you quit the debugger several times (it keep popping up because of the breakpoint) then you cannot delete or create any breakpoints which forces you to restart PTI.
And that is annoying because it doesn't save the setup of the debugger window (I mean the size of the embedded windows) and your lcd momentum...
Posted: Mon 26 Nov, 2007 3:52 pm
by CoBB
The whole breakpoint business is a terrible hack on top of the emulator code, to be honest...
Posted: Thu 13 Dec, 2007 9:05 am
by Timendus
CoBB, PindurTI is losing in popularity against WabbitEmu...
I'll hack it as a second backend into my new Linux frontend for WabbitEmu, so I don't give either project an advantage, but if PTI wants to survive you really need a nice GUI soon
(And preferably a Linux binary with working LCD too
though I know I also failed miserably in finding the bug...)
Posted: Thu 13 Dec, 2007 9:56 am
by CoBB
Timendus wrote:CoBB, PindurTI is losing in popularity against WabbitEmu...
Why is that a problem? Wabbit is superior in practically every respect.
Timendus wrote:I'll hack it as a second backend into my new Linux frontend for WabbitEmu, so I don't give either project an advantage, but if PTI wants to survive you really need a nice GUI soon
Heh, it’s been ‘coming along’ for ages... And for a reason.
Posted: Fri 01 Feb, 2008 10:03 pm
by tari
Greetings, everyone! (blahblah, yes I just joined the board, no I'm not new; I hang out in #tcpa)
I've mentioned this on UTI, but I've found a bit of an inaccuracy in how it handles paging. In the interest of brevity, I'll just
link to it.
Posted: Sat 02 Feb, 2008 2:03 pm
by King Harold
If you do not explicitly set a page for bank b, then there is nothing in it, is this supposed to happen?
Posted: Sat 02 Feb, 2008 5:23 pm
by CoBB
Okay, PTI does the following for each bank:
Code: Select all
if bit 6 is set (RAM is mapped), then
if (bank & 0x1f) > 1 (invalid RAM page), then
emptiness is mapped (i.e. a read-only page full of 0xff’s)
else
the approriate RAM page is mapped
else
the approriate ROM page is mapped
Bits 7 and 5 have no effect on the mapping, but they are stored in case you read back the page number.
I guess you see the invalid RAM page mechanism in action, Harold.
Jim e wrote:Besides PTI emulates all hardware and hardware quirks that should be emulated. Not every little detail that exists. Theres a lot of quirks which have no benefit to developing.
I’d still try to emulate as many as possible, but I have no 83+ myself, which puts a limit to this kind of activity...
Posted: Sat 02 Feb, 2008 7:13 pm
by Jim e
CoBB wrote:Jim e wrote:Besides PTI emulates all hardware and hardware quirks that should be emulated. Not every little detail that exists. Theres a lot of quirks which have no benefit to developing.
I’d still try to emulate as many as possible, but I have no 83+ myself, which puts a limit to this kind of activity...
I was more referring to stuff like the vector for the interrupt table or the blue lines. We know the vector table isn't random but for all practicality it may as well be consider so. And the blue lines pretty much have very little benefit to anything in the universe.
Posted: Thu 07 Feb, 2008 7:00 pm
by CoBB
So that was it, I’ll have to acknowledge the harsh reality and pronounce the PTI project dead for real.
As I said in the Brass section, I’m giving away the source, and everyone is welcome to rummage through it and take whatever seems to be of any value. You can download it from the good old project page from now on. Go Wabbit!
Posted: Fri 08 Feb, 2008 5:04 pm
by JoostinOnline
