Hello Community, my machine is Powerbook G4 A1138 with SSD. Previously I've used a registered MOS 3.18 but wanted to have a multiboot System with MOS 3.19 and MacOS10.4. I've followed (https://dreamolers.binaryriot.org/dualboot.pdf) and installed first MacOS10.4 and then MOS 3.19. Now if I try to boot MOS 3.19 I am getting a grey screen. I've done the instalation of MOS twice but with the same result, somehow I can't find the problem, maybe you guys have a hint for me how to diagnose my problem.
I've installed just MOS 3.19 with automatic partiotioning, and checked for differences in HDConfig, I can see that the automatically generated partitions have the flag enabled 'In Use (A/UX)', might this be the problem? what does the flag do?
So Boot partition is in HFS and initializes boot from OF, how does the Boot partition know, where MorphOS is located, to be able to select to proper partition?
The Multiboot-Guide says: "Note: do NOT remove the 128MB padding partitions. Mac OSX expects them to be there!" So: I removed the 128MB padding parition between DH0 (Boot) and DH1 (System) :D
The Boot partition is set a 1st to Boot (in OF) - default one Now I can: - Boot into MorphOS w/o using Bootmenu (alt pressed) - default one - Boot into MacOSX using Bootmenu - If there is MorphOS-CD inserted MorphOS will boot from CD automatically.
Now I can't: - Boot into MorphOS using Bootmenu. The screen is going gray and stays there.
> how does the Boot partition know, where MorphOS is located, > to be able to select to proper partition?
"Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. Note that this only applies to partitions that contain a MorphOS compatible bootable filesystem. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities […]." https://library.morph.zone/Open_Firmware#Boot_Arguments
DH1 has boot priority set to 0, and is the only SFS partition. Does my system now behaves normally, or why did I had to remove the 128MB padding partition? I mean I am happy, that it works, I am just wondering, if this is a normal thing?