Does anyone know if there is a version of High Sierra compatible with macbook air late 2018 (8.1) ?
That's still supported by Apple, so you can even go to the most current version (Mojave 10.14).
Does anyone know if there is a version of High Sierra compatible with macbook air late 2018 (8.1) ?
So, a laptop that’s less than a year old can support the previous OS? I would hope that’s a dead certainty. Am I missing something?That's still supported by Apple, so you can even go to the most current version (Mojave 10.14).
So, a laptop that’s less than a year old can support the previous OS? I would hope that’s a dead certainty. Am I missing something?
Sure. But why would you install High Sierra on a laptop that's capable of running Mojave and possibly came with it pre-installed?Just answering his question. Maybe he doesn't understand how the OS's work.
OK, after trying several scenarios with the 2019-001 security update, here's what works for me.
High Sierra security updates also update the Recovery HD, unlike Sierra and earlier. That recovery update process is buggy and often fails, but there's a workaround.
If you want the Recovery update:
Download and expand the security update package as in post 1. Then copy four files (AppleDiagnostics.chunklist, AppleDiagnostics.dmg, BaseSystem.chunklist, BaseSystem.dmg) from RecoveryHDMeta.dmg in EmbeddedOSFirmware.pkg in the update package, to the root of a dosdude 10.13.6 installer (replacing what's there), then boot and run the dosdude installer as usual. That resets the system to pure 10.13.6, but the Recovery HD will be the latest. (Remember that Mac OS installs do not affect installed applications or user data.) Once that's done, install the editted security update as in post 1, or simply use "softwareupdate -i -a" to install direct from Apple. Once all that's done, both your system and recovery will be up-to-date.
If you don't want the Recovery update:
Download and expand the security update package as in post 1. In addition to the edits in post 1, locate the RecoveryHDUpdate.pkg/Scripts/ directory and edit the replaceRecovery file. Edit the two lines starting "/usr/bin/hdiutil" to start "echo /usr/bin/hdiutil". Edit the two lines starting "./Tools/dm" to start "echo ./Tools/dm". (In all cases you simply add "echo " to the beginning.) Then flatten and install the update package as described in post 1. This updates your system but leaves the recovery unaffected.
(In my case I don't even have a Recovery partition. Who needs one when you have an installer stick? The second option suits me fine.)
I hope these workarounds work for other people. Please let us know if they do not.
[doublepost=1548207165][/doublepost]
Among my many, MANY jobs over the past few decades, I've been a software release manager. I know how they think.![]()
Each posting in a thread has a number (your post is #4432). Post 1 is the very first post in this thread, back on page 1 (we are now adding to page 178). I'm not sure that there is an "easy way" yet; there are just some reported solutions, and they don't seem to work for everyone.
I can normally close everything and shut down, but when I restart it goes back to a state WAY before I shut down i.e. it reopens apps that I'd quit before shutting down - like as if it's gone back to a snapshot of the system from hours ago.
I've now started looking at logs before I shut down - and here's another strange thing. This morning I started having a problem at about 11:00am. The last entry in the system.log was about 9:00am.
Any suggestions as to what this may indicate, or any steps I could take to find out what's going on, would be greatly appreciated.
Interesting. I'll try turning it off for a while. Unfortunately, I can't force this to happen, so won't really know whether it's the culprit. I don't see others complaining so maybe it's not a "system" issue per se. In all honesty, I don't use Dropbox much.Not an expert, but it sounds like something like DropBox, or some other cacheing/buffering system, is "overlaying" the system disk, sort of masking it for some period. I don't use Dropbox, so I can't suggest anything other than stopping using it for a while, and see what happens.
Happened again with Dropbox off, so it's not that. It's very weird. My /var/log/system.log had stopped adding entries at 14:30 (which is when I presume the problem started) but it was now 17:30. When I looked in the Console app, there were loads of errors being generated some of them disk I/O errors. I could still browse the internet although Gmail seemed to be having a problem until I logged out of it and back in. Again ReportCrash was running but at the top of the list for CPU usage was photoanalysisd - I have no idea what that is or why it was running. Back to normal after a restart - although it wouldn't shutdown until I relaunched the Finder (Application Not Responding).Interesting. I'll try turning it off for a while. Unfortunately, I can't force this to happen, so won't really know whether it's the culprit. I don't see others complaining so maybe it's not a "system" issue per se. In all honesty, I don't use Dropbox much.
Ah, alright. I'll make a new version for 10.13.6 with the latest security updates.@dosdude1,
Do you have an update for the amdgpupatch uninstaller script? The latest version for 10.13.4 does not work with 10.13.6 (with security update 2019-001). Any help would be much appreciated.
Happened again with Dropbox off, so it's not that.
at the top of the list for CPU usage was photoanalysisd - I have no idea what that is or why it was running.
Ah, alright. I'll make a new version for 10.13.6 with the latest security updates.
I'm on HFS+. I've run Disk Utilities' First Aid and no problems.Are you on APFS or HFS+? I tend to be conservative so I'm still on HFS+. Can you run a disk hardware test, maybe something SMART related?
Googling "photoanalysisd" shows many complaints, and requests to disable. Mine shows 0.33 s CPU in 15 days uptime.
I'm getting a strange error while trying to make an installer. I've done this a thousand times, the drive is properly formatted. I am doing this on a Mac thats running mojave, so I'll try this again on my iMac that still has High Sierra on it, idk why the host OS would matter but I don't know what else to try.
Great work, thanks a lot! I did this to my MacBook Pro 4,1 (early 2008), very happy with it![]()
Also have some ExpressCard/34 cards on the way from eBay, eSATA II, dual USB 3.0 and eGPU adapter for the fun of it. It also has an SSD installed.![]()
Yeah, it's your GPU that's the issue. The AMD drivers for newer cards in High Sierra (and Mojave) require the SSE4.2 instruction set, which the CPUs in the Mac Pro 3,1 do not support. Unfortunately, the only solution is to replace the card with an nVidia one.@dosdude1,
Firstly, thank you for all your effort in making old Macs more useful for longer. I successfully used your tool on my MacBook Pro 2009, and it's been working great.
Unfortunately on my MacPro 2008 (3,1) I am experiencing an issue after install. I get the following output over and over during boot, and the computer never completes the boot to the lock screen.
IOConsoleUsers: time(0) 0->0, lln 0, llk 1,
IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0
Doing some searching leads me to believe that this is graphics related. I have a flashed AMD Radeon R9 280X in this system. I tried using the option in post install for the newer AMD GPUs, but that made no difference. Any insight would be great. Thanks so much for your help!
Great, thanks!Ah, alright. I'll make a new version for 10.13.6 with the latest security updates.