Specifically, i'm trying to run Macintosh ROM's through it.
While it can decode snippets of functions - it dumps a lot of 'data' it thinks - it can't determine what's code and what's not. Also, the references, while they line up, seem to be scattered around, and the visual graph looks like spaghetti. I'm pretty sure the first 4 bytes of the ROM are a checksum, as per https://www.bigmessowires.com/2016/06/10/rom-hacking-tutorial-with-rom-inator-ii/ with the base address being 0x0 - but i'm a bit lost here. I can spend all day expanding 'unknown' chunks into code, but whether that's actually supposed to BE code or if it's just trying to turn something irrelevant INTO code.
While it can decode snippets of functions - it dumps a lot of 'data' it thinks - it can't determine what's code and what's not. Also, the references, while they line up, seem to be scattered around, and the visual graph looks like spaghetti. I'm pretty sure the first 4 bytes of the ROM are a checksum, as per https://www.bigmessowires.com/2016/06/10/rom-hacking-tutorial-with-rom-inator-ii/ with the base address being 0x0 - but i'm a bit lost here. I can spend all day expanding 'unknown' chunks into code, but whether that's actually supposed to BE code or if it's just trying to turn something irrelevant INTO code.