JDW
Well-known member
Please forgive me, but I am a bit more confused now and I would like to clarify my understanding as follows...Currently the last two of your bullet points are mutually exclusive (ROM disk with your favorite apps, and Daystar Turbo 040 compatibility), so what you seek doesn't exist. It's not a question of having sufficient room to include a ROM disk, but a question of integrating the code that implements the ROM disk into the Turbo 040 code. Theoretically that should be possible, but it's semi-unknown territory and would require some substantial reverse engineering work from someone.
The way I have understood the ROM-inator II SIMM is that you at the very least need a ROM file (e.g., an exact copy of an SE/30 ROM, IIsi ROM, IIfx ROM, or IIci ROM that is filename formatted as "*.rom") to burn into the ROM-inator II SIM in order to allow the SE/30 to boot. So if, for example, I had an exact copy of the SE/30 stock ROM named "se30.rom" and burned that to the ROM-inator II MEGA via SIMM Programmer and then installed that SIMM into the ROM slot on my SE/30, it would boot just fine and exactly as usual. BUT, if the ROM file burned into he ROM-inator II MEGA SIMM is a IIsi or IIfx or IIci (IIci is mere heresy because I myself have never owned one to verify it even works on the SE/30), you will get a 32-bit clean ROM that can boot into System 7.6.1 or OS 8.1, assuming you patch the System file first. AND, to kill RAM checking on cold boot (which takes an eternity if you have 128MB of RAM) would require some kind of hack to one of those ROMs prior to burning (a hack which I don't even know exists). AND, if you want a 32-bit clean ROM (again, IIsi or IIfx or IIci) that ALSO works fine with an attached Daystar Turbo 040 accelerator PDS card, you would also need to hack the said IIsi or IIfx or IIci base ROM in order to achieve that; which thus far, despite all the back-and-forth dialog about that ROM and past discussion threads, no one has been able to accomplish because... well... I don't know... The Turbo 040 chip is encrypted and nobody can read out the code...? Lack of ASM knowledge on the code that was read out...? I don't know.
Supplementing that...
We then have the separate but related talk of adding your own DISK IMAGE (*.dsk), within which you can save some vintage Mac apps (space allowing), which would become accessible via ROM when you boot (and you seem to have the ability to choose those apps to be made accessible from either ROM or a RAM DISK, assuming you have sufficient RAM. AND, to achieve that (i.e., to put your DISK IMAGE into your *.ROM file), you must concatenate the base ROM file (e.g., IIsi ROM file, or hacked IIsi ROM file, or stock SE/30 ROM file, etc.) with your compressed disk image file (*.fc8), as per the instructions given here, to get the needed *.rom file to burn to the ROM-inator II SIMM:
https://www.bigmessowires.com/2016/07/22/rom-disk-creation-with-rom-inator-ii/
So are you saying that some of my assumptions written above are incorrect?