![]() Yeah, it mean that your binary will still be 68k, but at least you can imrpove broken parts and made it be more os4 friendly (like by replacing all custom or chips graphics stuff on system friendly one). It's not mean you need to wrote all fixes in assembler, you can use C of course too= like i do in Foundation : i just set a call from assembler to my C function where need it, and made necessary C based fucntions as different object, which a link together when compile reassembled assembly code back to 68k binary. ![]() then work start : you then found parts you need to fix, and fix them. And always recompile it back to check that binary still works.ģ). then by hands imrove it for better readability (shift chunks, call names, replace library calls on proper lvo names for better readability, etc). disasembly binary by IRA to 68k assembler codeĢ). In brief that what i do when want to patch some 68k game sources of which i do not have:ġ). Of course it is not native os4 binary, but it can be fixed to be more os4 system friendly. ![]() I doing so when made patches for Foundation and Exodus. you use IRA to disassemble 68k binary to produce 68k assembly code (of course, not as original, but working one), which you can then compile back to the new 68k "exe" by vasm or phass, or devpac, etc. The only for real working 68k reassembler is : IRA (on os4depot).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |