I will wait too your APFS booter implementation that has worked perfectly with Mojave since beta 1 until 10.14.5 on Macmini4,1 . @dosdude1 you are a great, thank you again and again! :-D
Thank you for the clarification and all your effort into this
I will wait too your APFS booter implementation that has worked perfectly with Mojave since beta 1 until 10.14.5 on Macmini4,1 . @dosdude1 you are a great, thank you again and again! :-D
they will look identical but they should all be labeled
you probably need to flash the rom on your device so it is able to boot APFSCan´t install catalina on a M M 3.1ater the installation comes a folder with ?
what make i wrong ?
s
Not Yet. You can wait for dosdude1 to create an APFS boot loader.
The patch on 3,1 is not bad. I can't imagine the 5,1 being any worse.
[doublepost=1562858249][/doublepost]I installed Cat B4 last night and it looks like it auto installed the patches. I did not know they are auto applied but just about everything works. My system went to a blank screen. Rebooted, saw the installer media disk, selected it. Install went like a really Mac with black screen, white apple and ETA. When I booted it up to my surprise it always had the patches. I did download the installer disk using 1.0b7 dd1's installer maker.
The only thing missing in the patches is classic Mac OS Standard HFS support (pre Mac OS Extended HFS+ support)
You can use hfs.kext and hfsEncodings.kext from Mojave to get this support added back in. This is helpful for legacy stuff like old data CDs and DVDs that are in the old standard hfs format. To be clear, I'm not talking about Journaled Mac OS Extended HFS+, but the format before it.
Without the kext's from Mojave, you cannot mount old hfs volumes and can't do anything with them.
Amazing work as always @dosdude1Huge Catalina Patcher update: APFS booting implementation is now fully implemented, meaning it is no longer necessary to have APFS support included in your system's BootROM! Please report back any issues you experience, and enjoy!
Awesome thank youHuge Catalina Patcher update: APFS booting implementation is now fully implemented, meaning it is no longer necessary to have APFS support included in your system's BootROM! Please report back any issues you experience, and enjoy!
Hey, I got it running on the 3,1 (Thanks). Are you noticing anything weird about it? Also, I heard from someone that AMD graphics won't run on this? what's up with that? Thanks for yalls help. 1. El cap, 2. throw app on. 3. Catalina patch.I am running on MP3,1 as well.
You are the best!Amazing work as always @dosdude1![]()
Huge Catalina Patcher update: APFS booting implementation is now fully implemented, meaning it is no longer necessary to have APFS support included in your system's BootROM! Please report back any issues you experience, and enjoy!
I like your steps.
Doesn’t dosdude1’s patched installer complain that it’s APFS. What is the difference making a RAID this way vs. Apple’s RAID Assistant? And there are two ways of making Apple RAID’s. one is by whole disks and another is by slices / Volumes. It looks like you are using the whole disk method and I am wondering if gpt destroy is what is allowing the installer to work. As it could be hiding boot points the other disks.
Anyways. I will test your method out as I like command line alternatives.
Thank you for posting this. Lately Disk Utility hangs up a lot. This will work better.
As there's no way for me to check whether or not a machine has had the APFS ROM Patch applied, any machine that did not natively support High Sierra (and official APFS-compatible firmware) will have the APFS patch installed by default. If you do have an APFS ROM patched machine, you can just set the Startup Disk to the APFS volume, and that will bypass the APFS boot implementation. Haven't implemented auto forcing cache rebuild yet.I assume that you defaulted the post patcher to not automatically install the APFS patch, correct? Also, did you ever implement automatic forced cache rebuilding to cope with reinstalling Catalina over itself (where the presence of a stale kernel cache inhibits its automatic rebuilding)?
All those cards work except the Radeon HD 5xxx and 6xxx series video cards. So as long as you don't have one of those, your video card should work fine under Catalina.I am still confused about whether the graphic card support will be improved.
If I am reading the intro post it states
Spoiler
Pre-Metal AMD video cards (Radeon HD 6xxx series and older without acceleration, Radeon HD 4xxx series and older with acceleration.)
Pre-Metal Nvidia video cards (GeForce 5xx series and older, i.e. 8600M(GT)/8800M(GT), 9400M/9600M(GT), 320M/330M)
Pre-Metal Intel video cards (Intel HD Graphics 3000 and Intel HD Graphics Arrandale)
What does this mean. Are those card not supported or is there hope.
As there's no way for me to check whether or not a machine has had the APFS ROM Patch applied, any machine that did not natively support High Sierra (and official APFS-compatible firmware) will have the APFS patch installed by default. If you do have an APFS ROM patched machine, you can just set the Startup Disk to the APFS volume, and that will bypass the APFS boot implementation. Haven't implemented auto forcing cache rebuild yet.
[doublepost=1562943581][/doublepost]
All those cards work except the Radeon HD 5xxx and 6xxx series video cards. So as long as you don't have one of those, your video card should work fine under Catalina.
Do you have Bluetooth 4.x? Bluetooth 2.0 only supports 3Mbit/sec whereas Bluetooth 4.0 supports 24Mbit\sec.
thank i will try tonightHuge Catalina Patcher update: APFS booting implementation is now fully implemented, meaning it is no longer necessary to have APFS support included in your system's BootROM! Please report back any issues you experience, and enjoy!
thank i will try tonight
Yes, it does.I'm assuming this APFS patch will still produce the verbose text boot screen.