![]() ![]() Introducing heuristics to try to find the hidden ones can find some, but also find fake ones.Īnd there are tables, that are difficult to figure out for the same reason (plus disassembling data confuses the disassembler One recognizes an address inside the ROM, but it could be a value too. Actually I was able to find most of the reloc offsets, but still miss some.įor instance, this one is obvious, LAB_0186 must be relocated (it also could have been made originally PC-relative but that's another story: LAB_0181: I tried to re-create those myself and failed. My question is: how exactly are created those relocation table files ? A table exists for almost every official ROM file (see here). ![]() That's where the relocation table files (aka. It contains a lot of hardcoded addresses between $F80000/$FC0000 and $1000000 Problem is: the ROM files isn't position-independent code. Since the ROM is by definition not writable, those soft-kick programs have to load the replacement Kickstart somewhere else in memory. install another ROM than the original one, without changing the chips physically, either to upgrade to a newer ROM to run more recent programs, or on the contrary to boot older programs that aren't compatible with new ROMs. Several programs are able to "soft-kick" Amigas, i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |