Congratulations on your purchase of IDA pro (lolz)

Anyways, here's a step by step for you. I'm running 5.2, but I assume everything is about the same. I'm also going to assume you want to dissassemble programs (and not the OS):
1. Close out of any windows so you just have the plain IDA screen
2. File>Open your program
3. Change processor type to Z80 Processors: Z80
4. Ram Section: start 0x8000 size 0x8000. Rom Section: start 0x0000 size 0x8000 (this isn't super important)
5. Loading address: 0x9d95
6. File Offset: If you're using a .8xp 0x004c. If you somehow have a raw binary, 0x0000 or maybe 0x0002

That will set IDA up like the calculator. The data starts at 9d95. Most likely you can press C on line 9d95 and you'll be set.

A few notes:

• none of the ram addresses are mapped, so use this
  
• bcalls don't work obviously, if you see rst 28h, go to the line of code after it and press D twice then look up the address in that link
• you can probably not make a rom section if you get really annoyed at how tiny the scroll bar is

Have fun! (IDA is actually a lot of fun (if you're into that kind of thing))

Edit:
    If you're dissassembling an app, it's way harder. Let me know if you are. You can't just set the loading address to 0x4000, you'll have to modify the file first.

I am now fairly sure that this patch has at least one negative side effect. I have reports from two users of this patch that, with it installed, scrolling to errors from Axe results in garbage being displayed, corruption of RAM, and possibly other issues (now that I'm testing it again in Wabbitemu, the OS will not boot after the issue occurs). After a short amount of testing, it appears that the error can be triggered not just by instant error scrolling from Axe, but also from DoorsCS. The OS version may or may not matter; both users who reported the issue use 2.43.

I was pm'ing a guy for a while about stuff like this, and the best thing I can come up with is that this patch exceeds the maximum read/write speed of flash. He tried several different OS's and he always had the same problem. The only thing I could blame at that point was his hardware.

Yepp, this was a pretty nice piece of work. Though, it had to be pretty thorough to fool some of the people that it did.

I made one mistake and critor found it. I didn't add an extra little bit to the OS that TI usually does.

we need zstart for the CSE!

* Sorunome pokes thepenguin

Not a chance. (At least not by me) I hardly have enough time to update zStart let alone make a new one. And besides, I don't have a CSE.

Well, you may have titled the page improperly because you don't actually need to patch the OS. But when the time finally comes and you want to patch the OS, I did in fact make a patcher. (Physically patching the OS sucks. It takes so much code to make such a small change, even if you know exactly what you want to change).

And while we're at it, I might as well link to my guide on hooks since this information is available literally nowhere.

It'd be better for the man himself to answer, but I *think* all of these should work on either model. I don't see a reason why any of theses programs would require the extra ram. There are in fact very few programs that do.

Exactly right. I've actually never made a program that used more ram than what the calculators currently have. I mean, honestly, what are you going to do on the calculator that requires more than like 20kb of ram?

Oops, I'll fix this soon. I should probably add this thread to my watched list.

Ok, I finished it:
#define DWAIT in a, ($10) \ or a \ jp m, $-3

copySetup:
        di
        ld hl, $9900
        ld de, $9901
        ld bc, $100
        ld (hl), $98
        ldir
       
        ld a, $C3
        ld ($9898), a
        ld hl, interrupt
        ld ($9899), hl

        ld a, $99
        ld i, a
        im 2

        xor a
        out (03), a ;don't use halt

        ld a, $A0 ;64 t-state timer
        out ($30), a
        ret

; hl is the buffer to use
interruptCopy:
        nop
        ld a, $C9
        ld (interruptCopy), a ;safeguard against running twice
        ld e, $20
       
nextColumn:
        DWAIT
        ld a, e
        out ($10), a
        cp $2E
        jr nz, notDoneYet
        xor a
        ld (interruptCopy), a
        ex af, af'
        exx
        ret ;returns with interrupts disabled
notDoneYet:
        inc e
        DWAIT
        ld a, $80
        out ($10), a
        ld bc, 64*256+$11
        ld a, 3
        out ($31), a ;this is 3*64 = 192 t-states per write
        out ($32), a ; you can refine this, but 192 is probably good
        ex af, af'
        exx
        ei
        ret

interrupt:                      ;19 + 10
        ex      af, af'         ;4
        exx                     ;4
        out     ($31), a ;11 a = 3
        outi                    ;16
        jr      z, nextColumn   ;7
        exx                     ;4
        ex      af, af'         ;4
        ei                      ;4
        ret                     ;10
                                ;93 total

First of all, this only works in 15 MHz. It is actually worse in 6 MHz mode than the regular methods. To use this, call copySetup once, and then call interruptCopy whenever you need to update the screen. It won't let you run it again if it's still updating the screen (this would be bad) so that's good. The only downside is that you can't use interrupts (including getCSC) and you can't use HALT.

Hey guys: I made a java version of level8, and would like to share it (It requires that you compile the generated z80 source yourself, though, just to be warned.

All of this must be done in one folder: Just compile ("javac IConvert.java"), use "java IConvert" to run, and enter your complete picture filename (including extension). It can be any type, any size, and can have any number of shades. It will generate an all-blue bmp called "saved.bmp" and also create a z80 source file called <pictureNameMinusExtension>.z80 Just compile with SPASM or the like, and you're done!

Well that's pretty cool. Just curious, do you have your own use for this or did you just make it because you could?