macOS 10.14 Mojave on Unsupported Macs Thread

[ASentientBot]

Please try to understand the original problem I described: the app icon bounces in the dock, the dot appears under it, then the app icon stops bouncing and the dot disappears. The app is no longer running at this point. It has crashed. There is nothing to quit, because the app never actually launches.

Try running the app through Terminal, sounds like it's crashing. Maybe you can see why.

Probably going to necessitate a re-install anyways, though. These apps work fine for me on DP6.

 

[visberry]

Th

Hi @Czo - On software update fix ...

I get the following "Package Authoring errors" in my install.log. Some notifications are normal but the Syntax errors indicate (to me at least) that "broken lines" processing in Faker may be a little off. It must be removing lines and leaving open distribution xml sections, hence confusing the parser.

Check the log below. This may account for the inconsistent system update behavior some of us are experiencing. Can you check this out ? (I left you a pm about the tags we are ignoring also)

I matched my install.log with @TimothyR734 who successfully system updates on every shot and no such errors.

Others who've been unable to system update or always get the full install package every time, may want to check their install.log for errors also.

Thanks!

2018-08-07 02:47:57-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return false;
2018-08-07 02:47:58-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 02:47:59-04 Mac-Pro softwareupdated[575]: Package Authoring: error running volume-check script: SyntaxError: Unexpected keyword 'else' at x-distribution:///installer-gui-script%5B1%5D ==> else if (argv[0] == 'HP_Crossbow') { bundlePaths = ["/Library/Printers/hp/Frameworks/Crossbow.framework/Versions/D/Resources/Info.plist",]; }
2018-08-07 02:47:59-04 Mac-Pro softwareupdated[575]: IFJS: Package Authoring Error: error evaluating script visible for choice su: TypeError: null is not an object (evaluating 'my.target.mountpoint') at x-distribution:///installer-gui-script%5B1%5D/choice%5B1%5D/@visible ==> Script9(my.target.mountpoint)
2018-08-07 02:48:02-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 02:48:06-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return false;
2018-08-07 02:48:07-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 02:48:08-04 Mac-Pro softwareupdated[575]: Package Authoring: error running volume-check script: SyntaxError: Unexpected keyword 'else' at x-distribution:///installer-gui-script%5B1%5D ==> else if (argv[0] == 'HP_Crossbow') { bundlePaths = ["/Library/Printers/hp/Frameworks/Crossbow.framework/Versions/D/Resources/Info.plist",]; }
2018-08-07 02:48:11-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 03:02:51-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return false;
2018-08-07 03:02:52-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 03:02:53-04 Mac-Pro softwareupdated[575]: Package Authoring: error running volume-check script: SyntaxError: Unexpected keyword 'else' at x-distribution:///installer-gui-script%5B1%5D ==> else if (argv[0] == 'HP_Crossbow') { bundlePaths = ["/Library/Printers/hp/Frameworks/Crossbow.framework/Versions/D/Resources/Info.plist",]; }
2018-08-07 03:02:53-04 Mac-Pro softwareupdated[575]: IFJS: Package Authoring Error: error evaluating script visible for choice su: TypeError: null is not an object (evaluating 'my.target.mountpoint') at x-distribution:///installer-gui-script%5B1%5D/choice%5B1%5D/@visible ==> Script9(my.target.mountpoint)
2018-08-07 03:02:55-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 03:02:57-04 Mac-Pro softwareupdated[575]: Package Authoring Error: PackageInfo bundle reference found without top-level bundle definition. Bundle will be skipped: <bundle id="*"></bundle>
2018-08-07 03:02:57-04 Mac-Pro system_installd[516]: Package Authoring Error: PackageInfo bundle reference found without top-level bundle definition. Bundle will be skipped: <bundle id="*"></bundle>
2018-08-07 11:18:36-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return false;
2018-08-07 11:18:37-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 11:18:37-04 Mac-Pro softwareupdated[575]: Package Authoring: error running volume-check script: SyntaxError: Unexpected keyword 'else' at x-distribution:///installer-gui-script%5B1%5D ==> else if (argv[0] == 'HP_Crossbow') { bundlePaths = ["/Library/Printers/hp/Frameworks/Crossbow.framework/Versions/D/Resources/Info.plist",]; }
2018-08-07 11:18:40-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 11:22:04-04 Mac-Pro softwareupdated[575]: IFJS: Package Authoring Error: error evaluating script visible for choice su: TypeError: null is not an object (evaluating 'my.target.mountpoint') at x-distribution:///installer-gui-script%5B1%5D/choice%5B1%5D/@visible ==> Or0(my.target.mountpoint)

[doublepost=1533736798][/doublepost]
Hi - I did a little spelunking myself to add to others who are investigating this issue. Here are my (summarized) findings in a nutshell:

• The issue is localized to the Skylight.framework which includes the WindowServer
• A deep inspection of skylight and windowserver binaries revealed that Mojave's version leverages two new libraries compression and the latest metal performance shaders framework (compared to HS Skylight) So Apple has moved some shader processing to their framework, consistent with their bent on "full" metal everywhere and dropping support for OpenGL and OpenCL
• A drop in swap with the HS Skylight will simply not work (and risks hosing things really up)
• I also discovered two missing traditional shaders that are very conspicuously related to transparency/translucency. Why they are gone is up for debate (just a bug by omission or neglect?) but I am almost certain it accounts for our glitches on our older non-metal accelerated cards. For example my "unsupported" macpro 3,1 has a metal capable GTX 680 and does not glitch: so it's simply that Apple really dropped support for non-metal cards like exist on some our older laptops. HS still quasi supported them
• I also believe Dark mode "glitches" on non-metal cards but since it's Dark...you get the drift
• IMHO a solution to this would be extremely difficult since Skylight is ubiquitous (linked everywhere) and a binary patch may introduce unwanted side-effects system wide (skylight handles A LOT of things)
• Transparency/lucency is traditionally handled via shaders since its the best way to accelerate it, so we're definitely on the right track - how to fix this is up for strong debate
• If I had the time, I would debug this issue using Xcode gpu tracers (opengl or metal). But the setup is a little more complex since it's the windowserver: you have to remote debug the offending laptop
• We are at beta 6 and these non-metal card glitches are still not fixed, so I don't think Apple is seriously looking into this. In fact, as stated per their policy, support for non-metal cards is officially deprecated.

Feel free to trash/debunk or add to my theories (I don't take anything personally)

Hope this helps.

thanks for the analysis!

 

[mashersaurus]

Try running the app through Terminal, sounds like it's crashing. Maybe you can see why.

First thing I tried. And as I said in my first post, Terminal is one of the apps that won’t launch.

 

[PBear.SF]

Very confused by the whole 'receiving updates via System Preferences' issue. Installed SWUSwitcher -- thought this was supposed to eliminate necessity of going thru Apple in any way -- but, even though I could set Developer Preview or Public Beta in SWUSwitcher, and these seeds would then show as "enrolled" in Software Update, no updates would appear.

Next step: Went to Apple, enrolled in Public Beta (no choice, since not a paid developer account holder), installed Apple's PublicBetaAccessUtility and, voilà, PB5 download appeared immediately in Software Update -- full version, not update, but that makes sense since I'm updating from DP5, not PB4. Proceeded to download PB5 via Software Update (verified the version number), downloaded macOS Mojave Patcher 1.1.2 from here, and installed the downloaded PB5 on my USB stick (intending to use only for patches, or as a backup install if internal update failed).

Tried to run the new PB5 version of Install macOS Mojave Beta from my Applications folder and, as soon as I tried to choose my destination drive, got hit with the rude message: "This version of macOS cannot be installed on this computer." Drat! Re-installed Software Update Patch from Patch Update, rebooted, and tried again. Same error message from the installer. What gives? I thought the whole idea of the Software Update Patch was to allow the macOS installer app to run on an unsupported machine.

Maybe @dosdude1 can explain how this is all supposed to work.

(Sigh.)

 

[TimothyR734]

First thing I tried. And as I said in my first post, Terminal is one of the apps that won’t launch.

try reinstalling macOS Mojave to see if that fixes your issues
[doublepost=1533758481][/doublepost]

Very confused by the whole 'receiving updates via System Preferences' issue. Installed SWUSwitcher -- thought this was supposed to eliminate necessity of going thru Apple in any way -- but, even though I could set Developer Preview or Public Beta in SWUSwitcher, and these seeds would then show as "enrolled" in Software Update, no updates would appear.

Next step: Went to Apple, enrolled in Public Beta (no choice, since not a paid developer account holder), installed Apple's PublicBetaAccessUtility and, voilà, PB5 download appeared immediately in Software Update -- full version, not update, but that makes sense since I'm updating from DP5, not PB4. Proceeded to download PB5 via Software Update (verified the version number), downloaded macOS Mojave Patcher 1.1.2 from here, and installed the downloaded PB5 on my USB stick (intending to use only for patches, or as a backup install if internal update failed).

Tried to run the new PB5 version of Install macOS Mojave Beta from my Applications folder and, as soon as I tried to choose my destination drive, got hit with the rude message: "This version of macOS cannot be installed on this computer." Drat! Re-installed Software Update Patch from Patch Update, rebooted, and tried again. Same error message from the installer. What gives? I thought the whole idea of the Software Update Patch was to allow the macOS installer app to run on an unsupported machine.

Maybe @dosdude1 can explain how this is all supposed to work.

(Sigh.)

version 1.1.2 version of the of the Mojave patcher downloads macOS DP6 sounds like you downloaded the full installer which is not compatible on a unsupported Mac open your version of 1.1.2 Mojave patcher click on tools then download DP6 then create a usb patcher boot into your usb then you can install over your macOS Mojave without having to do a clean install until the issues with the software update is fixed the best way to tell if you get an update or full installer via the software update the update will be about 3GB full installer 5.87 to 6GB

 

[Luckygreek]

First thing I tried. And as I said in my first post, Terminal is one of the apps that won’t launch.

I had similar issue when installing over HS, did a format, install, Patch & used migration assistant to bring over my files & apps. Safari on 2010 iMac is slow to launch, using Safari Technology significantly faster, aside from that all my apps work as well as can be expected on an unsupported Mac.

Edit; There is a beta version of EtreCheck for Mojave.

 

[visberry]

I had similar issue when installing over HS, did a format, install, Patch & used migration assistant to bring over my files & apps. Safari on 2010 iMac is slow to launch, using Safari Technology significantly faster, aside from that all my apps work as well as can be expected on an unsupported Mac.

Edit; There is a beta version of EtreCheck for Mojave.

I found that the Safari Technology Preview crashes a lot.
[doublepost=1533760691][/doublepost]

Hi @Czo - On software update fix ...

I get the following "Package Authoring errors" in my install.log. Some notifications are normal but the Syntax errors indicate (to me at least) that "broken lines" processing in Faker may be a little off. It must be removing lines and leaving open distribution xml sections, hence confusing the parser.

Check the log below. This may account for the inconsistent system update behavior some of us are experiencing. Can you check this out ? (I left you a pm about the tags we are ignoring also)

I matched my install.log with @TimothyR734 who successfully system updates on every shot and no such errors.

Others who've been unable to system update or always get the full install package every time, may want to check their install.log for errors also.

Thanks!

2018-08-07 02:47:57-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return false;
2018-08-07 02:47:58-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 02:47:59-04 Mac-Pro softwareupdated[575]: Package Authoring: error running volume-check script: SyntaxError: Unexpected keyword 'else' at x-distribution:///installer-gui-script%5B1%5D ==> else if (argv[0] == 'HP_Crossbow') { bundlePaths = ["/Library/Printers/hp/Frameworks/Crossbow.framework/Versions/D/Resources/Info.plist",]; }
2018-08-07 02:47:59-04 Mac-Pro softwareupdated[575]: IFJS: Package Authoring Error: error evaluating script visible for choice su: TypeError: null is not an object (evaluating 'my.target.mountpoint') at x-distribution:///installer-gui-script%5B1%5D/choice%5B1%5D/@visible ==> Script9(my.target.mountpoint)
2018-08-07 02:48:02-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 02:48:06-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return false;
2018-08-07 02:48:07-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 02:48:08-04 Mac-Pro softwareupdated[575]: Package Authoring: error running volume-check script: SyntaxError: Unexpected keyword 'else' at x-distribution:///installer-gui-script%5B1%5D ==> else if (argv[0] == 'HP_Crossbow') { bundlePaths = ["/Library/Printers/hp/Frameworks/Crossbow.framework/Versions/D/Resources/Info.plist",]; }
2018-08-07 02:48:11-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 03:02:51-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return false;
2018-08-07 03:02:52-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 03:02:53-04 Mac-Pro softwareupdated[575]: Package Authoring: error running volume-check script: SyntaxError: Unexpected keyword 'else' at x-distribution:///installer-gui-script%5B1%5D ==> else if (argv[0] == 'HP_Crossbow') { bundlePaths = ["/Library/Printers/hp/Frameworks/Crossbow.framework/Versions/D/Resources/Info.plist",]; }
2018-08-07 03:02:53-04 Mac-Pro softwareupdated[575]: IFJS: Package Authoring Error: error evaluating script visible for choice su: TypeError: null is not an object (evaluating 'my.target.mountpoint') at x-distribution:///installer-gui-script%5B1%5D/choice%5B1%5D/@visible ==> Script9(my.target.mountpoint)
2018-08-07 03:02:55-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 03:02:57-04 Mac-Pro softwareupdated[575]: Package Authoring Error: PackageInfo bundle reference found without top-level bundle definition. Bundle will be skipped: <bundle id="*"></bundle>
2018-08-07 03:02:57-04 Mac-Pro system_installd[516]: Package Authoring Error: PackageInfo bundle reference found without top-level bundle definition. Bundle will be skipped: <bundle id="*"></bundle>
2018-08-07 11:18:36-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return false;
2018-08-07 11:18:37-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 11:18:37-04 Mac-Pro softwareupdated[575]: Package Authoring: error running volume-check script: SyntaxError: Unexpected keyword 'else' at x-distribution:///installer-gui-script%5B1%5D ==> else if (argv[0] == 'HP_Crossbow') { bundlePaths = ["/Library/Printers/hp/Frameworks/Crossbow.framework/Versions/D/Resources/Info.plist",]; }
2018-08-07 11:18:40-04 Mac-Pro softwareupdated[575]: Package Authoring: error running installation-check script: SyntaxError: Return statements are only valid inside functions. at x-distribution:///installer-gui-script%5B1%5D ==> return (needsEFIUpdate(actualEFI, intendedEFI, actualSMC, minSMCforEFI));
2018-08-07 11:22:04-04 Mac-Pro softwareupdated[575]: IFJS: Package Authoring Error: error evaluating script visible for choice su: TypeError: null is not an object (evaluating 'my.target.mountpoint') at x-distribution:///installer-gui-script%5B1%5D/choice%5B1%5D/@visible ==> Or0(my.target.mountpoint)

[doublepost=1533736798][/doublepost]
Hi - I did a little spelunking myself to add to others who are investigating this issue. Here are my (summarized) findings in a nutshell:

• The issue is localized to the Skylight.framework which includes the WindowServer
• A deep inspection of skylight and windowserver binaries revealed that Mojave's version leverages two new libraries compression and the latest metal performance shaders framework (compared to HS Skylight) So Apple has moved some shader processing to their framework, consistent with their bent on "full" metal everywhere and dropping support for OpenGL and OpenCL
• A drop in swap with the HS Skylight will simply not work (and risks hosing things really up)
• I also discovered two missing traditional shaders that are very conspicuously related to transparency/translucency. Why they are gone is up for debate (just a bug by omission or neglect?) but I am almost certain it accounts for our glitches on our older non-metal accelerated cards. For example my "unsupported" macpro 3,1 has a metal capable GTX 680 and does not glitch: so it's simply that Apple really dropped support for non-metal cards like exist on some our older laptops. HS still quasi supported them
• I also believe Dark mode "glitches" on non-metal cards but since it's Dark...you get the drift
• IMHO a solution to this would be extremely difficult since Skylight is ubiquitous (linked everywhere) and a binary patch may introduce unwanted side-effects system wide (skylight handles A LOT of things)
• Transparency/lucency is traditionally handled via shaders since its the best way to accelerate it, so we're definitely on the right track - how to fix this is up for strong debate
• If I had the time, I would debug this issue using Xcode gpu tracers (opengl or metal). But the setup is a little more complex since it's the windowserver: you have to remote debug the offending laptop
• We are at beta 6 and these non-metal card glitches are still not fixed, so I don't think Apple is seriously looking into this. In fact, as stated per their policy, support for non-metal cards is officially deprecated.

Feel free to trash/debunk or add to my theories (I don't take anything personally)

Hope this helps.

Idea: If Dark Mode's code can be adapted to be integrated into the Light Mode code, would we get this to a) work as expected or b) be less noticeable.

 

[TimothyR734]

I found that the Safari Technology Preview crashes a lot.
[doublepost=1533760691][/doublepost]

Idea: If Dark Mode's code can be adapted to be integrated into the Light Mode code, would we get this to a) work as expected or b) be less noticeable.

do you have version 62 of Safari Technology installed

 

[Luckygreek]

I found that the Safari Technology Preview crashes a lot.
[doublepost=1533760691][/doublepost]

Sounds like something else is obviously wrong, I've yet to have it crash. Have you tried re patch, SUM & or Disk Utility? If Terminal won't open in OS have you tried to run it in Recovery Mode?

 

[PBear.SF]

try reinstalling macOS Mojave to see if that fixes your issues
[doublepost=1533758481][/doublepost]
version 1.1.2 version of the of the Mojave patcher downloads macOS DP6 sounds like you downloaded the full installer which is not compatible on a unsupported Mac open your version of 1.1.2 Mojave patcher click on tools then download DP6 then create a usb patcher boot into your usb then you can install over your macOS Mojave without having to do a clean install until the issues with the software update is fixed the best way to tell if you get an update or full installer via the software update the update will be about 3GB full installer 5.87 to 6GB

Doesn't the Mojave Patcher download the full versions of the Developer Previews? (Every version I've downloaded with the patcher before this has been over 5 GB.)

But, in the end, are you saying that the full version I downloaded via Software Update will not work even if I run it from the USB stick that I created with it last night using the patcher -- and, furthermore, if I do get the smaller update of a future beta release from Software Update, that I will be able to install that directly from within Mojave? If that's true, will I also be able to use that smaller, update file with the patcher to create a new USB stick installer? This is where I get so confused.

 

[TimothyR734]

Doesn't the Mojave Patcher download the full versions of the Developer Previews? (Every version I've downloaded with the patcher before this has been over 5 GB.)

But, in the end, are you saying that the full version I downloaded via Software Update will not work even if I run it from the USB stick that I created with it last night using the patcher -- and, furthermore, if I do get the smaller update of a future beta release from Software Update, that I will be able to install that directly from within Mojave? If that's true, will I also be able to use that smaller, update file with the patcher to create a new USB stick installer? This is where I get so confused.

you might be able to make a patcher from the full installer I tried a few times but got a lot of error messages when trying so I stuck with just downloading it from the Mojave patcher. I am one of the lucky ones who got to update from DP5 to DP6 from the software update and a copy didn't not appear in my download or applications it just download then asked to install to finish the update this was on my iMac 9,1 When the update works properly you should have to make a new patcher but it is wise just in case something goes wrong

 

[thewebgal]

Tried again earlier today, Kingston 16GB USB3 stick. Latest Patcher and fresh OSX dload MacPro flashed to 5.1 last year ... (BootRom MP51.00087.800)
Its been happily running Sierra 10.12.6 for quite a while, but I could never get HS to install -
so today I tried a direct upgrade to Mojave -
Crashed and burned - reloaded Sierra w/Time Machine ... ah well!

 

[ASentientBot]

First thing I tried. And as I said in my first post, Terminal is one of the apps that won’t launch.

I'm a dumbass.

 

[visberry]

I'm a dumbass.

Oh.

 

[TimothyR734]

I'm a dumbass.

no you are not we are all have the same goal get macOs Mojave working on unsupported and help people along the way

 

[ASentientBot]

Is anybody else having trouble with this? In DP6, if I make an AppleScript that controls another application and export it as an app, it fails to run because it's "not authorized to send Apple events". But it doesn't show up in the Security & Privacy prefpane. Any ideas?

 

[PBear.SF]

Is anybody else having trouble with this? In DP6, if I make an AppleScript that controls another application and export it as an app, it fails to run because it's "not authorized to send Apple events". But it doesn't show up in the Security & Privacy prefpane. Any ideas?

Known bug since Mojave betas started (I thought it was fixed in DP5 'cause I have a scripted app that exhibited the same behaviour then seemed to work after updating to DP5 but maybe that was just a quirk -- or it's broken again in DP6). Anyway, it's definitely on Apple's bug list; just Google the error message and you'll find plenty of info.

Also, if you click on the "Edit" button in the error dialog, it will open the script editor where you can run the script with no problem -- just can't run it as an app.

 

[shaocaholica]

So how does the patcher get older non metal supported GPUs working? Is it a driver hack to get metal support or OpenGL fallback?

 

[TimothyR734]

Tried again earlier today, Kingston 16GB USB3 stick. Latest Patcher and fresh OSX dload MacPro flashed to 5.1 last year ... (BootRom MP51.00087.800)
Its been happily running Sierra 10.12.6 for quite a while, but I could never get HS to install -
so today I tried a direct upgrade to Mojave -
Crashed and burned - reloaded Sierra w/Time Machine ... ah well!

when you tried installing High Sierra did you make a High Sierra patcher usb , did you make sure your SIP is disabled, and run the post install patches after from the same usb? Check the OP on the first page of this thread to see if your MBP 5,1 is compatible to use the Mojave patcher if it is your will have to make a Mojave Patcher usb as well

 

[mashersaurus]

Those you indicate are all core main system apps, they deal with many macOS frameworks, to me there is not so much to investigate, I would suggest to reinstall Mojave.

1. Boot to RecoveryHD: Disk Utility, run First Aid of ur Mojave partition.
2. Open Terminal to disable SIP: $ csrutil disable
3. Reboot to ur Mojave MainSystem, run this:

Spoiler

sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / && sudo update_dyld_shared_cache -force

4. Reboot again && test. Good luck.

Thank you both again for your responses. Reinstalling Mojave over the top seems to have done the trick - I can now open all apps, and the system seems to be functioning normally. If I have problems again I'll try @Badruzeus's suggestions, and failing that I'll do a format and reinstall. Thanks again everyone
[doublepost=1533799776][/doublepost]

Is anybody else having trouble with this? In DP6, if I make an AppleScript that controls another application and export it as an app, it fails to run because it's "not authorized to send Apple events". But it doesn't show up in the Security & Privacy prefpane. Any ideas?


View attachment 775114 View attachment 775115

I'm having this problem in an app I have in development. It uses NSAppleScript to send keystrokes to another application, but since installing Mojave I get this error. This is really frustrating, as complying with Dark Mode was the only reason I installed Mpjave, and now I can't release the app anyway until Apple fixes this bug.

 

[jackluke]

Tried again earlier today, Kingston 16GB USB3 stick. Latest Patcher and fresh OSX dload MacPro flashed to 5.1 last year ... (BootRom MP51.00087.800)
Its been happily running Sierra 10.12.6 for quite a while, but I could never get HS to install -
so today I tried a direct upgrade to Mojave -
Crashed and burned - reloaded Sierra w/Time Machine ... ah well!

It seems you have Nvidia GeForce GTX 680 that is a Metal supported card, so you should need only few patches, not sure about yours cpus/mcp, but I guess your Kernelpanic is due only to the 5 IOUSB*** kexts and telemetry.plugin.

Anyway since you have a timemachine from which you can use even Migration Assistant in Mojave later, try reinstalling Mojave over your Sierra (or maybe if you have a Sierra timemachine, do a clean Mojave install on your disk), then without applying any patches try to boot directly Mojave.

If it fails, hold "option" key at power-on, booting again from the USB Mojave Installer, open Post Install, select as your Mac model: MacPro 4,1 and manually de-select this patch: "Legacy video card", while keeping all the others, select "Force cache rebuild".
After done, reboot, wait and check if Mojave finally works.

If you can boot Mojave without GPU acceleration then download and install in Mojave this driver:

http://www.nvidia.com/Download/driverResults.aspx/136062/en-us

[doublepost=1533802128][/doublepost]

So how does the patcher get older non metal supported GPUs working? Is it a driver hack to get metal support or OpenGL fallback?

I guess they enhanced GPUs APIs calling them Metal, Vulkan, Directx 12, but substantially in the core they are all next-gen OpenGL/CL 3D/2D evolution.

 

[thewebgal]

when you tried installing High Sierra did you make a High Sierra patcher usb , did you make sure your SIP is disabled, and run the post install patches after from the same usb? Check the OP on the first page of this thread to see if your MBP 5,1 is compatible to use the Mojave patcher if it is your will have to make a Mojave Patcher usb as well

Well, its not a MBP (Mac Book Pro 5.1) Its a Mac Pro 5.1 - Aluminum cheese grater tower machine.
Yes, I have always done this with a USB stick. As I said, I built a Mojave Patcher yesterday and tried to skip High Sierra this time.
Everyone says this re-Flashed machine is Native supported for High Sierra -
It is fine in Sierra, but not High Sierra, and is not in MoJave either.
I suspect something got corrupted somewhere and I can't figure it out.

 

[Larsvonhier]

Well, its not a MBP (Mac Book Pro 5.1) Its a Mac Pro 5.1 - Aluminum cheese grater tower machine.
Yes, I have always done this with a USB stick. As I said, I built a Mojave Patcher yesterday and tried to skip High Sierra this time.
Everyone says this re-Flashed machine is Native supported for High Sierra -
It is fine in Sierra, but not High Sierra, and is not in MoJave either.
I suspect something got corrupted somewhere and I can't figure it out.

Are you sure you have the latest SMC firmware and boot ROM versions? You can check and compare to what Apple lists at
https://support.apple.com/de-de/HT201518
And also check that your processors are up to the task (I once had a 2nd hand cMP where the previous owner downgraded the XEONs ... ;-// )

 

[jackluke]

Are you sure you have the latest SMC firmware and boot ROM versions? You can check and compare to what Apple lists at
https://support.apple.com/de-de/HT201518
And also check that your processors are up to the task (I once had a 2nd hand cMP where the previous owner downgraded the XEONs ... ;-// )

Probably you're right, needed to upgrade instead from the BootRom MP51.00087.800 to BootRom MP51.007F.B03 (EFI 1.5)

edit:
No, wait, MacPro5,1 supported natively until El Capitan, I think a downgrade BootRom isn't feasible.
Maybe has to install Mojave only in HFS+ on that machine.

Well, its not a MBP (Mac Book Pro 5.1) Its a Mac Pro 5.1 - Aluminum cheese grater tower machine.
Yes, I have always done this with a USB stick. As I said, I built a Mojave Patcher yesterday and tried to skip High Sierra this time.
Everyone says this re-Flashed machine is Native supported for High Sierra -
It is fine in Sierra, but not High Sierra, and is not in MoJave either.
I suspect something got corrupted somewhere and I can't figure it out.

Anyway try to follow my previous advice, I told during Post-Install to select "MacPro4,1" since MacPro5,1 seems not yet available on the Mojave Patcher, they are very similar, the only relevant difference is that you have a Metal supported video card.

 

[Loyd-01a]

I'm a dumbass.

Absolutely not !

I'm this thread from practically the beginning and every time I see the green disk I think there must be something new interesting for our unsupported mac (especially for my MB7,1 ;-)) !
Keep up the good work !

And thank you for you efforts and time