My SSE 4.2 emulator (MouSSE), which enables the Mac Pro 3,1 to run the AMD Metal drivers, is finally going public. See this post for details.
@dosdude1, are you going to update the Mojave/High Sierra patchers for this like you did for Catalina?
My SSE 4.2 emulator (MouSSE), which enables the Mac Pro 3,1 to run the AMD Metal drivers, is finally going public. See this post for details.
Yes, I will be.@dosdude1, are you going to update the Mojave/High Sierra patchers for this like you did for Catalina?
For simplicity execute all these commands at once by copying all this code and paste it into the Terminal:
Code:sudo softwareupdate --ignore "macOS Catalina"; defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier; defaults write com.apple.systempreferences AttentionPrefBundleIDs 0; killall Dock; defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier; softwareupdate --list
I'm having issues after the supplemental update. I was on 10.14.4 that @ dosedude1 put on my 8,2 mbp after he did his Gmux fix for thhe dGPU, so using a PNY 16 Gb USB I built a 10.14.4 patcher, and verified it on my 18,3 iMac, and it worked. I put it in the 8,2 hit option at startup and only the HD shows up, then loads half way and gets stuck. So I built another 16 Gb USB with 10.14.4 on it, verified it on my 18,3, put it my 8,2 and same result, then another 16 Gb USB, same result. What am I doing wrong? This is a simple straight forward task it seems. @doseduse1 you have made this process so simple and easy I don't think even I could get this wrong, but maybe I did. Can Someone point to what I've done incorrectly please? I followed the steps to the letter. This happened at the same time the Google Keystone update issue arose, although I don't use Google Chrome, unless it comes with Mojave. Help please?
I absolutely love how no one responds to the stupid people. I'd prefer it though if you'd send over someone to punt my head back into reality, so I don't suffer so long though. This is painful haha! Let'see...Supplemental update...14.4...duh...oh! update to 14.6! Actaully someone said 14.4 was the last version that supported hardware encoding, I believe so I wanted to stay there, thus the stubbornness, ignorange and pain. Oh well, thanks @doseduse1, my 8,2 burns and I simply can't believe it's 9 years old. I'm leaving it on Mojave though for 32 bit app support, unless there is a compelling reason to upgrade. Your patcher and everything you've done with it, and added to it is amazing, and makes our lives incredibly easy. You're our Maccy Jesus, mmm sounds like a song, lol.
Thanks
@alphascorp. Thank you, thank you. As one who, along the way, has made a few smug remarks like RTM at various times, and then finding myself in the uncomfortable position of needing help for something else, I found (to my dismay) that going through 700 pages takes time. Now I have sharpened my search skills and learnt to criticize less (or better still, not at all)... and wait, because sooner or later, someone would have the same problem and ask. Thanks to all who have made this thread - and the other - a delight. I am sticking to Mojave on the MBP4,1 as I have a Catalina-compatible 9,1 for daily use. But I visit the both Unsupported Mac threads everyday.Hi @avz ,
Yes that's right, that's why I notified it in my message #17362
"FIXED MY ISSUE TEMPORARILY!"
"It works as long as I do not run update lookup with the software update system preferences even though I have already run (sudo softwareupdate - ignore "macOS Catalina" and sudo softwareupdate --list) before. "
In this case it is necessary to redo the manipulation with the terminal (which is not a real problem)
Code:sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier defaults write com.apple.systempreferences AttentionPrefBundleIDs 0 killall Dock
That said, we do not launch a search for updates every day...
However, this does not block the search for automatic updates as I read with some solutions on the web
EDIT:
In order to permanently prevent the red badge from coming back after each update search (automatic and/or manual)
Just add the following line to others:
Code:defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier
For simplicity execute all these commands at once by copying all this code and paste it into the Terminal:
Code:sudo softwareupdate --ignore "macOS Catalina"; defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier; defaults write com.apple.systempreferences AttentionPrefBundleIDs 0; killall Dock; defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier; softwareupdate --list
You must reinstall to clear the patched WIFI. You can see your WIFI details clicking the wifi symbol in task bar with the alt/option pressed.Hi guys, I need some help. I have an MBP4,1 15inch that has Mojave on it. It was running well, chugging along on 4 Gb (memory slot 1 is bad), but when the last update came up, I performed the update. Then I ran dosdude1's patcher, but I forgot to clear the update for the WiFi card, because my card is the BCM94322 not the xxx4321. Whether it is that or something else, I don't know, but the Bluetooth part has stopped working. It does not recognise any other bluetooth device. I have rerun the patcher several times (reminds me of a definition of insanity - when you do the same thing over and over, and... but I digress). The wireless works (is there a way to know if it runs at 5Ghz?). I depend a lot on AirDrop and it worked before the update. Does anyone know how to rectify the situation? Thank you all.
Thank you for your quick response. That's what I feared, and didn't want to do because downloading the whole thing is expensive here... Ah well, nothing to do except to get on with it. I had thought there would be a way to unpatch the WiFi, and let Mojave install the right files.You must reinstall to clear the patched WIFI. You can see your WIFI details clicking the wifi symbol in task bar with the alt/option pressed.
Hello,
is there anyone that has a functioning iSight camera on their iMac 9,1 on Mojave? I tried different kexts but none seem to work unfortunately. Maybe anybody in here has working kexts? Any help is appreciated
ProductVersion: 10.14.6
BuildVersion: 18G103
Just checked my 20" iMac9,1 On Mojave 10.14.3 and Facetime is working normally. Patch Updater shows version 2 installed for Legacy iSight patch. Try re-installing from Patch updater by choosing the Legacy iSight patch and Ctrl - click, reinstall update. If that doesn't work, try booting back to your USB patched installer, re-check ONLY the Legacy iSight patch, then make sure you do a force rebuild and reboot.
Maybe you can extract the unpatched kexts from the installer but I don't know how to do it. Maybe ask @dosdude1 or someone else with more knowledge than meThank you for your quick response. That's what I feared, and didn't want to do because downloading the whole thing is expensive here... Ah well, nothing to do except to get on with it. I had thought there would be a way to unpatch the WiFi, and let Mojave install the right files.
Hi, thanks for replying. I already tried both methods but unfortunately in Facetime it keeps showing that the system does not have a camera. Just to try every possible patcher, I also ran 0403979's Patcher but the kexts don't seem to fix my problem. I don't know if it has to do with the system configuration (I have the 24" top model, 3.06 GHz and 512 MB VRAM) or the OS version. Im also pretty sure that it worked on earlier versions of Mojave, just not 10.14.6 unfortunately.
Do you mind sharing the 2 kext files in question? (IOUSBHostFamily.kext and IOUSBFamily.kext) I would try to load them manually (KextBeast) and report back.
Thanks
I think you can convert with about 20 or 15 % free but I'm just guessing. Do a backup of your drive and try to convert, if the free space is not enough the conversion process doesn't begin. DO BACKUP FIRST just in case.I want to share my short experience a one question.
I wanted to update Macbookair3,2 to 10.15 so i needed update it to APFS. I did found that I can convert drive. Somewhere advised that it is possible only when is filled less then 50%. So I deleted number of things and tried.
One important tidbit for others who will try, when you boot from other disk, you have to in disk utility unmount disk first otherwise convert feature is dimmed.
I run convert and it was blazing fast without issues. After restart you have to reapply patches or at least I could not boot without that. So everything is working well.
My question is. Is it really needed to to empty 50% of drive to convert it? I was so quick that it does not seemed to move any big data. I have MBP4,1 with SSD quite filled and want to convert it as well.
And I applied APSF boot patch for unsupported macs but I probably had to use official patch. I have not looked at it. Can I uninstall unsupported patch and reinstall official to get rid of verbal boot sequence?
Thank you
I think you can convert with about 20 or 15 % free but I'm just guessing. Do a backup of your drive and try to convert, if the free space is not enough the conversion process doesn't begin. DO BACKUP FIRST just in case.
Parallels VM performance (I have a Windows 7 VM) is broken in 10.14.4 and later on my MacPro3,1 (I tested 10.14.6 and 10.15 - I guess I'll try a clean install of 10.14.4 and 10.14.5...)Parallels or something that doesn't mess up system drivers ...
The new iMovie update requires metal that are unsupported Macs are not capable of so yes wise choice to stay at the previous version unless a work around is foundI have a late 2009 iMac with Mojave 10.14.6. Recently, I updated iMovie to 10.1.13. The iMovie does not display any video in the video preview window. When play video, it only has the audio. I found the old iMovie 10.1.12 and installed. Now I can use iMovie again. If anyone needs iMovie, don't upgrade to 10.1.13.