I'm still new to the SE/30 game and haven't played with updating to a Clean ROM SIMM yet, so a couple of quick questions:
Does the Gestalt ID change with the ROM installed?
Has anyone hacked the SE/30 to give a IIfx, IIci, IIsi or other Gestalt ID to the OS?
I haven't had an adapter in order to play PowerCache head games with the SE/30 . . . yet. [}
] ]'>
I've been wondering just how far I can confuse an unsuspecting MoBo into doing things it's not supposed to do by convincing the PowerCache do things it can do in the ci and si because it does them differently on those boards with the ROM SIMMs native to those machines.
Project 30 hit a roadblock I'm not equipped to address (unlike other insane hacking projects ) the Bus Mastering issues of Slot Manager Ops in the SE/30 as compared to the way things are done under the Gestalt IDs of Macs with SE/30 compatible ROM SIMMs.
Postulate WAGs:
PowerCache's 68030/internal MMU: to be compatible across a broad range of Macs, runs the show with amazing flexibility.
---- eliciting whatever behavior it wants from any given Mac's hardware
--------would handle the memory controller of any of those Macs to its best advantage
WAG/theory:
Hack the Gestalt ID of the SE/30 to match that of the compatible ROM SIMM donor and the above processes will be altered.
Point of the exercise:
Get PowerCache to handle operations in the SE/30 with greater flexibility than possible with its own ROM/Gestalt ID.
Sidestep my obvious software/firmware/digital logic design levels of incompetence to place the problem firmly into the building block diagrams of my toy set in order to do an end run around Bus Mastering roadblock in the SE/30 Gestalt ID/ROM/Hardware/Firmware
Hoodwink the PowerCache, getting the IIsi NuBus Adapter or any other NuBus chipset solution to play nicely on its own processor bus in an alterated SE/30 playpen.
h34r:
Does the Gestalt ID change with the ROM installed?
Has anyone hacked the SE/30 to give a IIfx, IIci, IIsi or other Gestalt ID to the OS?
I haven't had an adapter in order to play PowerCache head games with the SE/30 . . . yet. [}
] ]'>I've been wondering just how far I can confuse an unsuspecting MoBo into doing things it's not supposed to do by convincing the PowerCache do things it can do in the ci and si because it does them differently on those boards with the ROM SIMMs native to those machines.
Project 30 hit a roadblock I'm not equipped to address (unlike other insane hacking projects
) the Bus Mastering issues of Slot Manager Ops in the SE/30 as compared to the way things are done under the Gestalt IDs of Macs with SE/30 compatible ROM SIMMs.Postulate WAGs:
PowerCache's 68030/internal MMU: to be compatible across a broad range of Macs, runs the show with amazing flexibility.
---- eliciting whatever behavior it wants from any given Mac's hardware
--------would handle the memory controller of any of those Macs to its best advantage
WAG/theory:
Hack the Gestalt ID of the SE/30 to match that of the compatible ROM SIMM donor and the above processes will be altered.
Point of the exercise:
Get PowerCache to handle operations in the SE/30 with greater flexibility than possible with its own ROM/Gestalt ID.
Sidestep my obvious software/firmware/digital logic design levels of incompetence to place the problem firmly into the building block diagrams of my toy set in order to do an end run around Bus Mastering roadblock in the SE/30 Gestalt ID/ROM/Hardware/Firmware
Hoodwink the PowerCache, getting the IIsi NuBus Adapter or any other NuBus chipset solution to play nicely on its own processor bus in an alterated SE/30 playpen.
h34r:
Last edited by a moderator:
