On Feb 3, 2016, at 3:58 PM, Alyssa Milburn wrote:
On Wed, Feb 03, 2016 at 03:36:52PM -0500, Programmingkid wrote:
Is it possible the invalid/unsupported opcode errors are PowerPC instructions that are not implemented? Or do you think the processor is executing memory it should not be executing? The message "qemu: fatal: Trying to execute code outside RAM or ROM at 0xfdfdfdfc", was it shown when you used your patch? If it was then there is some kind of address calculation error possibly taking place.
There's some kind of weird memory corruption going on during the Mac OS 9 boot for me, and making small changes (even changing the available RAM) makes things behave differently. A jump to some arbitrary address (often NULL) is a pretty common result, and annoyingly at that point no amount of hunting around with MacsBug seems to let me work out what's going on. Maybe the crash here is/was another instance of this?
Usually I manage to get through the whole boot process and then it crashes after the menu bar has appeared inside something like the Control Strip code. Sometimes it even boots. It makes it pretty frustrating to debug though, since you can't just randomly remove resources (e.g. patches) and check whether that fixed it or not. Maybe I'm doing something really stupid though, so I'll post this in this thread and see if anyone has suggestions..!
There has to be an easier way. Things would be a lot easier if Apple released the source code to Mac OS 9. What I have been doing is improving how Mac OS X behaves in QEMU and hoping my patches also help Mac OS 9. It looks like a lot of programs rely on The OTUtilityLib to operate. When it is gone a lot of good programs go with it. So I currently can't test out if the RTL8139 NIC actually works in Mac OS 9 yet.