But in the general case, determining what is a label and what is a constant is not something any automated disassembler can do.  (For one thing, determining all the possible code paths reduces to the halting problem.  For another thing, when you start getting into seriously optimized code, like some that I've written, the distinction between "constant" and "label" becomes somewhat fuzzy, as optimizations can imply constraints on your labels that can't even be expressed in standard assembly language.)  But for even a moderately complex assembly program, I wouldn't trust any automated disassembler to understand everything - it requires human eyes to figure out exactly what the program is doing.

That said, if you know the code is produced by a compiler that doesn't use any outlandish optimizations (and more to the point, if you know beforehand exactly what programming techniques that compiler uses) - then some heuristics able to recognize those techniques might be sufficient.  (Note that I'm assuming the programmer has used "pure" Axe, or Axe with a well-defined set of simple assembly libraries - in other words, that the programmer has not made any assumptions that depend on the implementation of the Axe compiler or the target machine.)  I don't know enough about Axe to say how hard it would really be, but I would be somewhat surprised if there were any existing disassembler able to do that in general.

OK, this is getting a bit off-topic; sorry.  In conclusion: disassembly is hard.

That's true, I really have a disassembler recognizing labels, datas and texts. Unfortunately, it's unnamed, but you can download it here : http://mattias.refeyton.fr/espace-ti/z80disassembler.zip

Also, I have my code here : http://mattias.refeyton.fr/espace-ti/jetpack82/JETPACK.z80 , but remind that it's 51K large.

There aren't any error at the compilation, but here is a screenshot of it working with the installer on a 83 :


EDIT : in fact, there isn't any _DelVarArc in the file ...

Yeah sure, I join the *.8xp I compiled from the source I posted.

Oops, I forgot to join the installer, you need to launch it before prgmJETPACK

The setup creates a program named prgmJTPKSTUP, stores three 768 bytes images in it and then quits.

What the main program does is accessing to this program and read the three images with a 768 or 1536 offset.

Now that I think of it, I remind that there is a bcall named _DelVarArc on the 83+ that doesn't exist anymore on the 83, I'll try to replace it with _DelVar and see if it works better.

Ah yeah, I'll send you something to test it.

Is it only me or is the gs the same on the real 83? Since uh, then you can better remove the gs part