Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
That's a lot of testing for one person, especially considering you're developing the software as well! I wonder if the community could help out with your efforts (myself included).
What you're saying completely makes sense. I've been holding on to an 11 year old Mac Pro 1,1 for as long as humanly possible. It uses two very old but powerful Xeon processors. It's become more and more clear to me that's it's coming time to build that hackintosh.
I will try out the Sab 2.3.0 when I'm by the computer and let you know how it goes. Thank you for your informative reply.
Cpuroast wrote: ↑November 24th, 2017, 7:33 pm
The mac version is being built on the oldest travis build environment possible using xcode 6.4 on 10.10, it contains the sdk for 10.9 and 10.10.
So the version of Sab currently shipping is essentially as un-optimized as possible to support the highest number of OSes as possible.
Starting with 2.3.0, I have been personally testing Sab on 10.9, 10.10, 10.11, 10.13 in VMs and on 10.12 on the host running those VMs which is a mid-2012 MacBook Pro running 10.12, to make sure builds run on all OSes and so far they have been working flawlessly at least on this 2012 CPU.
It really looks like the travis build environment which is building Sab or python 2.7.14 is using more recent CPU instructions not present on legacy CPUs, most likely of the Core 2 Duo era which are now over 10 years old.
Sab 2.3.0 uses Python 2.7.13 while Sab 2.3.1 and newer uses Python 2.7.14, so this could be something.
Maybe there's way to make the build environment even more restrictive in terms of CPU instructions used.
But realistically, at the end of the day, it's very simple, at some point old stuff needs to be recycled.
10+ year old computers while still supported by Apple under 10.11, at least until Fall 2018, when 10.11 goes out of support, need to be replaced.
This was built using a diff build environment, I've tested this build on 10.9 through 10.13 on a 2012 mac without any issues and we've had 1 confirmation that it runs on an old 2007 24" iMac on 10.11.6.
We'll try out best to support 10.9 and up on all supported hardware for as long as possible.
There may come a time when 10.9 and 10.10 get dropped, but all computers that run 10.9 and 10.10, can also run 10.11.
This was built using a diff build environment, I've tested this build on 10.9 through 10.13 on a 2012 mac without any issues and we've had 1 confirmation that it runs on an old 2007 24" iMac on 10.11.6.
We'll try out best to support 10.9 and up on all supported hardware for as long as possible.
There may come a time when 10.9 and 10.10 get dropped, but all computers that run 10.9 and 10.10, can also run 10.11.
This was built using a diff build environment, I've tested this build on 10.9 through 10.13 on a 2012 mac without any issues and we've had 1 confirmation that it runs on an old 2007 24" iMac on 10.11.6.
We'll try out best to support 10.9 and up on all supported hardware for as long as possible.
There may come a time when 10.9 and 10.10 get dropped, but all computers that run 10.9 and 10.10, can also run 10.11.
Thanks!
Good to hear, means the current build environment is good for now and covers all macs on 10.9 and up.
