Apple Network Server MacOS based ROMs found

joevt

Tinkerer
Mar 5, 2023
335
132
43
I'm going through the code in the extension and I see the string but not where it is checked. What offset in the code fragment did you see that at?
I used Jasik's MacNosy to disassemble the "mace" container from the Apple Enet 2.4.5 extension.
I made a script to dump the string tables from the .asm file.
The property name PLSCCPort is at offset $7C1 in the string list global glob72 in AppleEnet.asm (the .list file disagrees on global numbers - a bug in MacNosy probably).
This string is accessed in proc12.

In the DumpPEF output, the access is at offset 0158C in the first container of the file (the first container "mace" is at offset 0 in the file).
The access is at offset 0150C of the code section in that container (find it in the .dumppef output and the .list output).
 

Attachments

  • Apple Enet.zip
    2.5 MB · Views: 41
  • Like
Reactions: ClassicHasClass

ClassicHasClass

Active Tinkerer
Aug 30, 2022
543
1
316
63
www.floodgap.com
Status update on the 1.1.20.1 extension pack. Besides the already working ndrv for the video (the SCSI controller will be extracted the same way), I now have a working hack of Boot Variables that fixes the console between reboots. This goes in Startup Items and undoes whatever is messing with the input and output devices, and doesn't require me patching the system otherwise.

I also tried changing the nvramrc in the Boot Variables hack to add the necessary property to the MACE Ethernet. I can successfully commit the nvramrc, but it doesn't work, even though I can tell the nvramrc has executed due to debugging messages I put in it.

My second attempt was to use the Name Registry to patch it from inside the Boot Variables hack. I can find it in the device tree and set the property, but the Name Registry is too old and will not let me save a property name of that length to NVRAM. So now I'm working on either an ndrv or an INIT that will run before Apple Enet and set that property, since it does seem to work at runtime. In fact, this approach may be cleaner anyway.

Anyway, getting closer to a universal boot-anything solution. It's hacky but it will run any available OS for Shiner.