I'm sure it will have no problem with external DVD drives. The issue is that the AppleIntelPIIXATA.kext plugin in IOATAFamily.kext has been dropped in Catalina.
Got a tip for us?
Let us know
macOS 10.15 Catalina on Unsupported Macs
- Thread starter julianfairfax
- Start date
- Status
My Home app just bounces in the dock and doesn't open so it must have got the metal treatment to
i am running Catalina Beta 3 on a MacPro 5.1 with a Metal GPU.
Everything seems to run fine except Mail.
During opening mail, i see my content. But as soon as i click on an e-mail, Mail crashes.
Any tips?
Thanks
Everything seems to run fine except Mail.
During opening mail, i see my content. But as soon as i click on an e-mail, Mail crashes.
Any tips?
Thanks
Thanks for looking into this. My preference would be to add the missing kext to the plugins but that would be beyond my skills. I always try to have the minimum changes to the OS but it is still early days with Catalina. Should have noticed this before but only just noticed the DVD was absent!
I assume that is on a non-metal graphics card? All of those are behaving normally against a GTX680.Stocks and Voice Memo's also crashing no wave with Siri its gone again
FYI, Collin will be adding this in the next patcher release. I also confirmed his solution of just copying over the missing Mojave AppleIntelPIIXATA.kext into the Plugins directory of the Catalina IOATAFamily.kext works fine.
Stocks, Home, and Voice Memos don't crash on my system (can't really test Home properly though). Can you upload the crash reports?Stocks and Voice Memo's also crashing no wave with Siri its gone again
You're right about Siri, I assume that it's trying to draw something with Metal. I'll see if a binary patch is possible.
Edit: got Siri mostly working.
Last edited:
Do you hav any idea why Microsoft word is acting strange when highlighting text ? That doesn't use metal right ..
I'm not sure about Word, I'll download a copy and give it a try sometime soon-ish.
As for Siri, I got it working with a three byte patch to the following file:
Code:
/System/Library/PrivateFrameworks/SiriUI.framework/Versions/A/SiriUIIf anyone wants to try it, the replacement is attached. Make a backup copy first.
All I did was change one line of assembler:
Code:
0x5512: jmp 0x5607
Not sure if that will work in this case. Apple has Application Swift libraries that link to the System's Swift libraries. They started doing this with Swift 4.2 and Swift 5 and it will always use the System Swift Libraries. And the System Swift Libraries link to the actual System frameworks and the paths in those libraries are hard encoded. I ran into this with the Quartz framework that a System Swift library was looking for and the path had to be exact on the system.
I could try added the libraries its looking for and make them static and see if it will override. However I think they way the Swift libraries are setup and when they link to other libraries, on its second hop it will still look for the System Libraries from the System Swift library.
I'll fool around with it some more once I get a few other things with the App in place.
For libraries that I write myself, this would be much easier to control. It's clear the Base System was never meant to run Swift and the fact that I was able to get it work is a miracle. It look a good block of time running my app in the command line seeing what was missing and the trickiest part was the Quartz library because the full blown Catalina lib's structure as different than the thinned down Base System one. It took a couple of tries to get just what it needs without blowing up the display. So yeah, if I can get it to use a Quartz lib. that local the app, that would be best.
The conflict with NSDataAsset was already there in the Base System. I did not create it. Apple has two libraries that calling the same class. One is probably a newer framework and may guess the UI labeled one is for SwiftUI. I'm not using SwiftUI, so it's strange to have a new library fire up. This overlap happens quite frequently on macOS and most of time it's hidden in the console.
[doublepost=1562276024][/doublepost]
My DVD is partially working and I haven't put in the Kext yet. I think it only working the way it is because I booted my system with a DOS CD inserted. Many of my own CDs are not reading upon insert. Going to get the one from Mojave as suggested.
I don't see any crash logs for them Home, stocks and voice memo's just bounce in the dock then stops no crash message appears but have to force quit them
my screenshot is not uploading with Safari 13
[doublepost=1562279453][/doublepost]Thank goodness for my MacBook I tried Cat on my 5,2 but its like waiting for paint to dry getting to the desktop with 4gb ram it takes about 9 mins to get to the desktop on my iMac 9,1 with 8gb but this what Home, Stocks and voice memo's do on my iMac
[doublepost=1562279453][/doublepost]Thank goodness for my MacBook I tried Cat on my 5,2 but its like waiting for paint to dry getting to the desktop with 4gb ram it takes about 9 mins to get to the desktop on my iMac 9,1 with 8gb but this what Home, Stocks and voice memo's do on my iMac
Attachments
This is actually good timing, I'll be testing CloneToolX burned to a CD.
------
Looks like Catalina dropped support for "Mac OS Standard" CDs aka HFS too. As they are seen in diskutil and DiskUtility but do not mount.
Catalina does have HFS kexts, and those are loading. Going to try Mojave's unless I can find something else. Mojave had no issues reading in my HFS CDs.
Catalina B2 had IOATA Kext with PATA stuff inside, I'll Mojave's to see if HFS volumes loaded (not yet).
Guess PATA was dropped in B3. I haven't installed B3 yet.
---
Update: I see that AppleATAPIStorage.kext is not loading on B2. (Doesn't seem to be it.)
---
Not sure what's up with my HFS CDs not reading on Cat B2. Gonna start fresh with B3.
Update: I got plain HFS to work, look farther down this thread.
Last edited:
I know you uploaded a copy of the updated file but how do you edit it ? through a hex editor or something else ?
This ridiculous overly-complex "libs linking to libs" thing is one of the main reasons why Swift is so bad. At this point, the only thing Swift is good for are extremely high-level programs, that do nothing more than interface with a REST API (which is EXACTLY what this whole "SwiftUI" stuff is geared towards). I really think using Objective-C would have been a MUCH better route to go for writing a program like this. All Swift is is an overly complex link down to Objective-C/Foundation libs, while trying to "hide" the Objective-C part from the developer. On top of that, it also utilizes a very confusing and honestly extremely counter intuitive syntax. It's almost as bad as Rust syntax.
Last edited:
I truly understand your frustration. I know that its good to have some changes to keep macOS revenant but I truly believe if something isn't broke don't fix it
Drift screensaver seems to be not working on MP3,1 with GTX680 metal card running Cat3b installed by latest dosdude1 patch. All other screensavers are working and Drift works on supported macs.
How do I replace it? I am looking at the file, I have your patched one downloaded, I can't for the life of me figure out how to replace the file.
I have good news for ATAPI / PATA internal CD player users on MP3,1.
I have MacOS Standard HFS discs mounting properly on Catalina Beta 3.
Here's what you need and don't need.
Catalina Beta 2 has the missing PATA kext inside the IOATAFamily.kext, so you don't need Mojave's and the other Kext's in this set are the same version as Beta 3. You can use the entire IOATAFamily.next from B2.
Next, The HFS and HFSEncodings seem to be foobarred in Beta 3, they will see the Mac OS Standard HFS CD volume, but they will not mount, burn, copy to a dmg or anything. You will get nothing but errors. You may even get kernel panics or Finder relaunches when trying to burn something.
So, from Mojave using the HFS and HFSEncodings.kext's and you'll be back in business with legacy HFS CDs. I do not know what the changes are in the newer HFS Kexts, but my assumption is Apple dropped support for HFS and kept HFS+ in. If they did that shame on them because Apple has kept support for Windows, MBR, NTFS, ExFat, Fat32, DOS, etc. So why on Earth drop one of your native disc formats even if it's old and keep all the PC ones?
I will be updating my CatWoman patch shortly that includes ATAPI/PATA/ATA/HFS Support. If you get operation not permitted, you can ignore the errors, the kexts copy over fine. Could be the system trying to set itself back to read only while in flight, even though the disk is set to read write before the operation starts.
Update: I wrote over my B3 install by mistake when I thought ASR was just replacing the Data volume and it the whole disk and did not honor the slice. Apple remove file copy from ASR. In the future, I'll use rsync or ditto to copy - Data volumes. I'll update the CatWoman patch tomorrow.
I have MacOS Standard HFS discs mounting properly on Catalina Beta 3.
Here's what you need and don't need.
Catalina Beta 2 has the missing PATA kext inside the IOATAFamily.kext, so you don't need Mojave's and the other Kext's in this set are the same version as Beta 3. You can use the entire IOATAFamily.next from B2.
Next, The HFS and HFSEncodings seem to be foobarred in Beta 3, they will see the Mac OS Standard HFS CD volume, but they will not mount, burn, copy to a dmg or anything. You will get nothing but errors. You may even get kernel panics or Finder relaunches when trying to burn something.
So, from Mojave using the HFS and HFSEncodings.kext's and you'll be back in business with legacy HFS CDs. I do not know what the changes are in the newer HFS Kexts, but my assumption is Apple dropped support for HFS and kept HFS+ in. If they did that shame on them because Apple has kept support for Windows, MBR, NTFS, ExFat, Fat32, DOS, etc. So why on Earth drop one of your native disc formats even if it's old and keep all the PC ones?
I will be updating my CatWoman patch shortly that includes ATAPI/PATA/ATA/HFS Support. If you get operation not permitted, you can ignore the errors, the kexts copy over fine. Could be the system trying to set itself back to read only while in flight, even though the disk is set to read write before the operation starts.
Update: I wrote over my B3 install by mistake when I thought ASR was just replacing the Data volume and it the whole disk and did not honor the slice. Apple remove file copy from ASR. In the future, I'll use rsync or ditto to copy - Data volumes. I'll update the CatWoman patch tomorrow.
Last edited:
Code:
sudo mount -uw /
# the above command will make an error about "AppleInternal", ignore it
sudo mv /System/Library/PrivateFrameworks/SiriUI.framework/Versions/A/SiriUI /System/Library/PrivateFrameworks/SiriUI.framework/Versions/A/SiriUI.old
sudo cp SiriUI /System/Library/PrivateFrameworks/SiriUI.framework/Versions/A/
Code:
sudo mount -uw /
killall Finder[doublepost=1562290379][/doublepost]
I use Hopper Disassembler trial (the full version costs something north of $100) to understand the code and make modifications, and then open its hex view and mimic the changes in a hex editor. It's a pain, but it works.
Like this just drop the one you downloaded and click replace then authenticate enter your password but you could also drop the original in your documents folder just in case
Attachments
I followed this steps. My MBP 8,1 restart during installation (using usb installer) , made the OS not properly installed. Did I miss some important things to do?
Make sure your system has the latest, APFS-comaptible firmware installed. You can do this by installing this package. Your system must be plugged in in order for the firmware to be flashed.
- Status
