Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Introducing a new way to run OS 9 on supported non-G4 and G5 macs, 100% compatible!
- Thread starter Rikintosh
- Start date
- Sort by reaction score
You're just a spoiled brat who got bitter because he thinks the world revolves around him.when you can’t deliver, you shut up.. basically it what means.
If you don't like it, go ahead and order it without a refund, oops! Oh, that's right, it was free, and yet you want to act like a Karen who bought something that didn't work lol
Perhaps this may be a bit off-topic, but since we are talking about improving OS 9 compatibility on OS X in this thread, I'm wondering if anyone has done work on getting MacIPX to work (or know why it doesn't work on a low-level technical level)? If not, would anyone be interested in teaming up to see if we can come up with a patch or fix?
From what I've read and tried, MacIPX seems to not load properly in Classic Environment on OS X 10.3 nor 10.4. But when I boot into OS9 on the same machine, it works perfectly. So, it's not just my installation, there's something that's not loading properly.
Examining the problem: The code for MacIPX seems to be entirely in 68000, but relatively short (~64k excluding Token Ring and AppleTalk drivers) and with a straightforward entry point (at least for INIT and cdev in the MacIPX resource fork). So, it should be relatively easy to debug and come up with a patch once we know what the problem is, if altering MacIPX is the way to go. However, it isn't clear at this point whether the problem is with how Classic Environment loads the MacIPX Ethernet driver or how the MacIPX Ethernet driver interacts with Classic Environment (e.g. Open Transport 2.8.3), nor whether it may be simpler to instead code a simple Ethernet IPX shim from scratch.
From what I've read and tried, MacIPX seems to not load properly in Classic Environment on OS X 10.3 nor 10.4. But when I boot into OS9 on the same machine, it works perfectly. So, it's not just my installation, there's something that's not loading properly.
Examining the problem: The code for MacIPX seems to be entirely in 68000, but relatively short (~64k excluding Token Ring and AppleTalk drivers) and with a straightforward entry point (at least for INIT and cdev in the MacIPX resource fork). So, it should be relatively easy to debug and come up with a patch once we know what the problem is, if altering MacIPX is the way to go. However, it isn't clear at this point whether the problem is with how Classic Environment loads the MacIPX Ethernet driver or how the MacIPX Ethernet driver interacts with Classic Environment (e.g. Open Transport 2.8.3), nor whether it may be simpler to instead code a simple Ethernet IPX shim from scratch.