MaxCoderz

blueskies wrote:cool background and icons demon. what's your distro?

Judging by the presence of Iceweasel it must be Debian.

Timendus wrote:You can't express the success of a project in how many lines of code it contains

I have to disagree with that. The less the better! It’s a pity there’s no practical C compiler for the Z80, progress could be a lot faster.

King Harold wrote:But, what I would really like to know: can you run code from $C000 - $FFFF if you swap in an executable rampage?

Yes, as it’s the page protection that counts, not the address it is mapped to.

Nice topic, I feel like contributing too.

Dwedit wrote:I like how that code writes repeatedly to the same destination address.

It’s a memory mapped register.

A much nicer example of abusing switch and C macros is implementing coroutines. I think Contiki uses something similar for its protothreads.

You forgot to zero d when adding the horizontal byte offset. A fix that doesn’t cost a single byte would be simply to move the addition of gbuf to the end of the address calculation.

Without the research done for PindurTI, we wouldn't have been able to make Wabbitemu. I think the same. Before PTI, there were no real alternatives to VTI, as TilEm was little more than a GTK port of it that didn’t really improve emulation. PTI ended up as a dead end mainly because we knew too litt...

agreed, it was much better than VTI by far! Fortunately there are better options to compare it to. :) Is there anything we can do to change your mind about quiting (money, women, threats, etc.)? Oh, I’d love to keep the project alive, but I’m lacking the resources to do so. Time, that is. As you ca...

Wabbitemu expands on a lot of PindurTI's features, it wouldn't be a bad idea to incorporate your source with it. You'd also get support for SE and 84+. I don’t think the current core would be easy to use for these newer models, and I had problems adding debugging facilities too. It would require a ...

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 proje...

I'd really like to do a total rewrite of the front-end so it can interact with the assembler a bit better. And it really needs your name on it. :| I’m not standing in your way. ;) That said, not being able to change the state of the calculator via the non-interactive mode (edit registers and memory...

The "PindurTI debugger" has been mercilessly hacked out of Latenite, so the code very bad (reliance on public static members in Program, to give you a sample). CoBB is not properly credited, though, and it does use a pretty old build of PindurTI, so this'll have to be fixed. The newest bu...

Okay, PTI does the following for each bank: 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 advantage of the latter is that you can keep the list in the form of a shell script that does "apt-get install" on each of them, so you just have to do a fresh install, let the script run, and when you come back you're good to go. Is there any point in doing that? If I’m working with ...

The first one is the winner without doubt.