MacInTouch Amazon link...

Apple compatibility issues

Channels
Apple
I am guessing AutoDesk did not want to get into a place where customers buy software that is only good for one or two years — trapping them in place.

in my opinion, the ideal would be having an OpenGL-to-Metal translation. I know it would be difficult, and I know the long-time Apple belief is that if you let people use sub-optimal methods, they will never switch to the Latest&Greatest, but it’s still annoying when you’re the one who can’t use Alias/VRED/Eudora/Word 2011/Word 5/PageMaker/Adobe CS3.
 


... My gut feeling is that an open source OpenGL library (over Metal) will eventually be developed in one form or another in order to provide OpenGL capabilities for XQuartz, since that is the only real 3D standard for the X11 environment, but I wouldn't begin to guess at a timetable, nor would I want to make any predictions about the possibility of using it as a replacement library for native macOS apps that use OpenGL.
My gut feel is that has some problems. If you look at the Github for XQuartz, there isn't much activity. It is creeping up on two years since the last new release. As Apple has merged more Metal focus into macOS, this project has slowed down, not sped up.

At one point, parts of Quartz were tied to OpenGL. There was a hiccup at Mountain Lion that XQuartz worked around, but when Apple yanks out the rest of OpenGL completely, I suspect there will be some components of XQuartz that will have problems.

There are several apps that run in XWindows that will probably need some OpenGL access, but XQuartz itself may need help. If that is the case and development activity is close to zero, then that would be a problem.

Couple that with the Xorg X11 vs. Wayland vs. " X12 " churn on the Linux side of the source tree, and that can complicate XQuartz momentum issues all the more.
 


Ric Ford

MacInTouch
I just found out about a surprising compatibility problem apparently introduced by Apple in macOS 10.13.4 High Sierra:
Plugable said:
Plugable USB-C Triple Display Docking Station
NOT macOS COMPATIBLE (10.13.4 version and later) ... only macOS 10.13.3 and earlier are supported.
Plugable said:
macOS 10.13.4: DisplayLink, Duet Display, and other Virtual Graphics Products Not Working
Some secondary display products no longer work on macOS 10.13.4, including all products using DisplayLink technology like USB docks and graphics adapters, and all apps which enable using a tablet as a second monitor. It’s unclear if Apple will be providing fixes. The only available solution currently is to disable updates and stay on macOS 10.13.3.
DisplayLlink said:
macOS High Sierra 10.13.4+ and Mojave 10.14 Early Previews
The driver (DisplayLink Installer 4.1.11) doesn't work anymore with macOS High Sierra beta 10.13.4 (17E139) and newer.

... DisplayLink has worked for many months to maintain support for its users during the transition from macOS High Sierra to Mojave. While functionality such as Ethernet and audio or charging, where implemented, is unaffected on all releases, display connectivity has been limited on macOS releases from 10.13.4 through 10.13.6.

Developers/users with access to Apple’s fifth developer preview of 10.14 Mojave, released on 30th July, will see full support has now been restored for multiple extended DisplayLink displays where DisplayLink driver v4.3 beta 5 (http://www.displaylink.com/downloads/file?d=175) is installed. We are doing wide scale testing of v4.3 beta against this preview and will release a new driver upon general availability of 10.14.

Users of 10.13.4-10.13.6 should also use v4.3 beta 5 as it contains a workaround to enable one extended USB display (720p or 1080p). An FAQ details how to enable Apple AirPlay with DisplayLink display for extend or mirror mode: https://support.displaylink.com/knowledgebase/articles/1854724

Users on macOS 10.13.3 and earlier should remain for the time being with DisplayLink driver 4.1 to maintain full extended display functionality.
 


MacOS 10.13 (High Sierra) is available via the App Store. Since you're running 10.7, you should be able to just open the App Store. Go to the "Updates" tab and you should find an "Update Now" button.
Click "Update Now". This will download the installer and run it when it downloads. When the installer starts to run, do not continue but quit from the installer. The installer will remain on your hard drive in your Applications folder. You can copy it to a flash drive for safekeeping.
Amusingly, App Store "Update" does not offer "macOS 10.13." However, "macOS High Sierra" is listed in the Quick Links. Clicking "Get" from that page returns the error, "We could not complete your purchase. This update requires MacOS version 10.8 or later."

Apparently, the solution is to upgrade to El Capitan first, then upgrade to High Sierra as per the Apple Support note here:

Guess I'll try Graham Needham's suggestion to use the High Sierra Patcher next. That appears to download and run. Just need to run out to Wallyworld for a blank SSD.
 


Amusingly, App Store "Update" does not offer "macOS 10.13." However, "macOS High Sierra" is listed in the Quick Links. Clicking "Get" from that page returns the error, "We could not complete your purchase. This update requires MacOS version 10.8 or later."
Apparently, the solution is to upgrade to El Capitan first, then upgrade to High Sierra as per the Apple Support note here:
Guess I'll try Graham Needham's suggestion to use the High Sierra Patcher next. That appears to download and run. Just need to run out to Wallyworld for a blank SSD.
Indeed, even if you can download the full High Sierra installer via the Patcher app, the installer will not run on OS X 10.7. As you've already discovered, you need to install an intermediate version of OS X first, before you can install High Sierra.
 


Indeed, even if you can download the full High Sierra installer via the Patcher app, the installer will not run on OS X 10.7. As you've already discovered, you need to install an intermediate version of OS X first, before you can install High Sierra.
Or (I would assume) make a bootable installer (which may also require a Mac with a more recent version of macOS) with 10.13 and boot it.

But if the upgrade-installer won't run directly, it may not be able to upgrade macOS either - that route may force you to perform a clean installation (after which, you would have to restore your apps and documents from a backup).
 


Or (I would assume) make a bootable installer (which may also require a Mac with a more recent version of macOS) with 10.13 and boot it.
I was able to download the full High Sierra installer via the Patcher app. I then directed the Patcher to create a bootable flash drive while running on OS X 10.7 and came back later to find it had completed, seemingly without a problem. Regardless, I now have the software, so I am (somewhat) immune to making High Sierra unavailable due to its replacement with Mojave.

Thanks to all!
 


*As Brian Lawson points out, even if the primary app is 64-bit, some of its resources may still be 32-bit. There's no way, until the 10.15 beta comes out (~June 2019), to know which apps will/won't work. The recommendation, at this point, is that if you still want to run any form of Adobe Creative Suite/InDesign CS with macOS 10.15 or later is to virtualise an older version of macOS - see recommendations below.
I didn't see anyone mention this but just wanted to add that if any of you are curious how your Adobe (or any other software for that matter) will behave in the next version of macOS, you can enable 64-bit only mode via boot parameters right now and test it (High Sierra and Mojave only):
Jeff Gamet said:
Here's How to Force Your Mac to Run Only in 64-bit Mode
  1. Restart your Mac and hold down Command-R to boot into Recovery Mode
  2. Launch Terminal
  3. Enter this command: nvram boot-args=”-no32exec”
  4. Restart your Mac
The instructions on how to set things back to mixed 32/64-bit mode are included on that page. Hope that helps.
 


I didn't see anyone mention this but just wanted to add that if any of you are curious how your Adobe (or any other software for that matter) will behave in the next version of macOS, you can enable 64-bit only mode via boot parameters right now and test it (High Sierra and Mojave only):

The instructions on how to set things back to mixed 32/64-bit mode are included on that page. Hope that helps.
I had completely forgotten about that option in Mojave - thanks for reminding me. Time to dig out a spare Mac, find some time, and do some testing :-)
 


I had completely forgotten about that option in Mojave - thanks for reminding me. Time to dig out a spare Mac, find some time, and do some testing :-)
(Someone just donated over on MacStrategy - thank you very much.)

Anyway, keen to try a few things in 64-bit only mode on macOS 10.14 Mojave and with some time available this afternoon, I got a test Mac Mini (2014 model) set up with macOS 10.14, updated to 10.14.3, set up the fake Java 6 folders, and then switched on 64-bit-only mode.

An immediate killer gotcha for Creative Suite is that the installers simply don't work - nothing I did could get them to work in 64-bit-only mode. So, I switched back to 32-bit support mode and got the basic Adobe CS5 and CS5.5 installed. I didn't try CS6 at this point, because it requires a login and registration with Adobe.

Checked that the following apps launched okay, which they did:
  • Illustrator 5.0
  • Illustrator 5.1
  • InDesign 5.0
  • InDesign 5.5
  • Photoshop 5.0*
  • Photoshop 5.1
* Under Mojave, Photoshop 5.0 required security access to control the computer (this is common with a lot of older software, but I had to allow it - otherwise, it wouldn't launch).

Switched back to 64-bit-only mode and tried launching the apps again:
  • Illustrator 5.0 - failed (expected)
  • Illustrator 5.1 - failed (not expected, 5.1 is supposed to be 64-bit)
  • InDesign 5.0 - failed (expected)
  • InDesign 5.5 - failed (expected)
  • Photoshop 5.0 - launched
  • Photoshop 5.1 - launched
Thinking that maybe Illustrator 5.1 requires the 5.1.1 update to be installed to work as 64-bit I opened Photoshop, and going to Help menu > Updates did nothing. Here's killer gotcha number two: the Adobe Application Manager and Adobe Updater apps do not work in 64-bit-only mode. Manual installation of the updates fails, too. That means no updates, but more importantly, no licensing capability (activation/deactivation).

Switched back to 32-bit support and installed the Illustrator 5.1.1 update manually (you can't use the helpful Adobe Updater app, because, although it launches, most updates won't install on later versions of macOS, because of that g****mn proprietary installer software - grrrr!).

Switched back to 64-bit-only, and Illustrator 5.1.1 still doesn't launch. The error reported is that it requires 32-bit support - so much for it being 64-bit.

I have not done any extensive testing in Photoshop in 64-bit mode and haven't tried CS6, but the fact that you can't install/update any CS apps/suites and the Adobe Application Manager (licensing) does not work in 64-bit mode means there's not any urgency for me to test at this point.

Conclusion: If you want to run any CS apps/suites on macOS 10.15 or later you're almost definitely going to want to go the virtualisation route.

Next up for me is exactly that. Running macOS 10.14 in 64-bit mode, getting virtualisation software installed and seeing if I can run an older macOS with Adobe CS. Watch this space…
 


Okay, I've had some time over the last few days to do some virtualisation testing. The test Mac:
  • Mac Mini (2014 model 3Ghz i7 with 16GB RAM + 500GB Apple SSD)
  • macOS 10.14.3
  • 64-bit only mode enabled
  • Parallels Desktop 14.1.2
  • VMware Fusion 11.0.2
  • VirtualBox 6.0.4
I've installed OS X 10.8 into each virtualisation application and test-installed the following:
  • Parallels Desktop 14.1.2 with fake Java 6 + Adobe CS3, CS4, CS5, CS5.5
  • VMware Fusion 11.0.2 with fake Java 6 + Adobe CS5.5
  • VirtualBox 6.0.4 with fake Java 6 + Adobe CS5.5
OS X 10.8 + Adobe CS all installed okay. All Adobe CS applications launched fine in 30-day trial mode (except Extension Manager, which I believe is a known issue until updated).

I've documented the steps for virtualising OS X 10.8 in my Virtualising OS X 10.8 Mountain Lion MacStrategy article. As usual, VirtualBox (the free one) is a lot more complicated than the paid-for products, but I got it installed and going.

I've documented notes on virtualising Adobe Creative Suite in my Virtualising Adobe Creative Suite with Mac OS X / OS X / macOS MacStrategy article.

I hope this information is useful for people as we move towards a world without 32-bit software and ubiquitous/onerous software subscriptions. :-(

At this point I've not done any extensive "work" testing in Creative Suite (and I'm away for a few days now), but if anyone has any specific question,s feel free to ask (here or on MacStrategy), and I will try to answer them if a) I have the facilities/software/versions, b) I can, and c) I have the time (donations to MacInTouch and myself - top of any primary MacInTouch page / bottom left of any MacStrategy page - are very welcome).

More (extensive) testing to come and more versions of macOS / OS X as guest OSes to be installed and documented…
 


Every time I charge my Apple Watch, it nags me to update from 5.1.2 to 5.1.3. I have not done so because my iPhone 6 Plus is running iOS 12.1.2 (I have been scared to update beyond that, based on reports here and elsewhere of connectivity issues.) All my connectivity currently works, and I don't want to break it.

My question for now is, is it necessary to keep Watch/iPhone updates "in sync", or can I update my Watch and still keep my iPhone at 12.1.2?
 


... My question for now is, is it necessary to keep Watch/iPhone updates "in sync", or can I update my Watch and still keep my iPhone at 12.1.2?
I can't answer your question directly, but FWIW I have no problems with an iPhone 6 Plus running iOS 12.1.4 and an Apple Watch running 5.1.3
 


I've had some more time over the last couple of days to do more virtualisation testing. The test Mac:
  • Mac Mini (2014 model 3Ghz i7 with 16GB RAM + 500GB Apple SSD)
  • macOS 10.14.3
  • 64-bit only mode enabled
  • Parallels Desktop 14.1.2
  • VMware Fusion 11.0.2
  • VirtualBox 6.0.4
I've now tried installing OS X 10.11 and macOS 10.12 guest OSes into each virtualisation application and also test installed Adobe CS3, CS4, CS5, CS5.5 in each of those plus CS6 on all three OSes (10.8/10.11/10.12).

The good news is that CS6 installs and updates fine on all those OSes. I haven't done any extensive usage testing, as that will have to come later and I need to do that quite in-depth for my own purposes, too.

I've documented the steps for virtualising OS X 10.11 in my Virtualising OS X 10.11 El Capitan MacStrategy article. I could not get OS X 10.11 installed in VirtualBox. I tried many things and followed various instructions posted on the internet - none of them worked.

I've documented the steps for virtualising macOS 10.12 in my Virtualising macOS 10.12 Sierra article. I could not get macOS 10.12 installed in VirtualBox. I tried many things and followed various instructions posted on the internet - none of them worked.

If anyone has any tips on getting OS X 10.11 and/or macOS 10.12 installed in VirtualBox 6, especially on a modern Mac/Mac Mini (2014 model), please do chime in here (or contact me via MacStrategy).

I've updated my documented notes on virtualising Adobe Creative Suite in my Virtualising Adobe Creative Suite with Mac OS X / OS X / macOS article. Although there is a small cost if you don't already have it, I can highly recommend virtualising OS X 10.8 - it's so much faster than 10.11 or 10.12, especially with CS6 :-)
 



I can't answer your question directly, but FWIW I have no problems with an iPhone 6 Plus running iOS 12.1.4 and an Apple Watch running 5.1.3
Thank you for that very useful data point. Perhaps I will consider an update. I wouldn't be so worried if updates weren't a one-way trip.
 


Do you have to start from scratch on these, or can you take an existing system and shove it in as an image?
I don't personally have to start from scratch - so that's a good idea - thank you, and I will try that. But my original plan was to create help documents (to post on MacStrategy) for people who are starting from scratch with an exact step-by-step guide to get going.

VirtualBox is free but it is a total nightmare to get working with intricate settings, arcane configuration and, it appears, terminal requirements for later macOSes as a guest environment.

On the other hand, both Parallels and Fusion just worked, with simple click-and-play options and the software doing all the heavy lifting at awkward steps, such as creating the required bootable disk image and using that for virtual environment setup. I can't fault either of those products in my testing. Personally, I recommend just spending the money on either Parallels or Fusion - the time wasted on VirtualBox is just not worth it.
 


Ric Ford

MacInTouch
Do you have to start from scratch on these, or can you take an existing system and shove it in as an image?
I don't personally have to start from scratch - so that's a good idea - thank you, and I will try that. But my original plan was to create help documents (to post on MacStrategy) for people who are starting from scratch with an exact step-by-step guide to get going.
I have exactly the same question. It seems really awkward and wasteful to have to go through a whole system installation procedure, when I already have multiple systems installed on multiple drives, and it would be far better to simply "clone" one of those to a virtual disk image, like I clone them to another drive. But I don't know if this is possible or how to do it.
 


My question for now is, is it necessary to keep Watch/iPhone updates "in sync", or can I update my Watch and still keep my iPhone at 12.1.2?
Looks like I've stumbled across the answer. This article clearly states that only iOS 11 is required, so it would seem that I'll be able to do the update. I'm hoping it will solve one problem I've been having for about a week now: useless appendage that it already is, the Apple News app on my watch has stopped updating entirely. Whereas it used to show the top five stories on Apple News (and, frustratingly, nothing else) now it's all out of date. I've tried quitting the app, but nothing changes.
 


...the Apple News app on my watch has stopped updating entirely. Whereas it used to show the top five stories on Apple News (and, frustratingly, nothing else) now it's all out of date. I've tried quitting the app, but nothing changes.
Well, the upgrade installed successfully, but the Apple News problem still exists, even after rebooting the watch fully. I'd do a reset, but I don't want to lose my heart data. Looks like I stop using the News app. Its iPhone counterpart is working without any problem.
 



It seems really awkward and wasteful to have to go through a whole system installation procedure, when I already have multiple systems installed on multiple drives, and it would be far better to simply "clone" one of those to a virtual disk image, like I clone them to another drive. But I don't know if this is possible or how to do it.
Most of the virtualization platforms (including the Mac versions) have supported direct migration of physical Windows machines to virtual machines for quite some time, but as far as I know, none ever have supported doing the same for migrating macOS systems. The usual advice has been to do a clean macOS install on a VM and then to use Apple's Migration Assistant to bring over the contents of the original Mac drive. I don't recall seeing a definitive explanation for this limitation.
 


Most of the virtualization platforms (including the Mac versions) have supported direct migration of physical Windows machines to virtual machines for quite some time, but as far as I know, none ever have supported doing the same for migrating macOS systems. The usual advice has been to do a clean macOS install on a VM and then to use Apple's Migration Assistant to bring over the contents of the original Mac drive. I don't recall seeing a definitive explanation for this limitation.
With my (very) preliminary investigation into this, it appears VMWare Fusion can do it. I've set aside some time tomorrow to investigate/test it properly.
 


Anyone know how long Apple supports its latest generation of iPads? I got burned with the 1st Gen iPad when Apple stopped supporting it after two years. It was (and is) a great little tablet, but I use it mostly as an ebook reader now, because the version of Safari on the device doesn't work well with most new websites that use the latest gewgaws and gimcracks in place of sensible interface design principals - just one of the reasons I don't own an iPhone or a newer iPad, which Apple seems to turn into landfill fodder relatively quickly. I won't touch one with a bargepole unless I can get at least four generations of iOS on it and six years of serviceable life.
 


Ric Ford

MacInTouch
Anyone know how long Apple supports its latest generation of iPads?
Wikipedia has a page that tracks that:
Wikipedia said:
iOS version history
iOS is a mobile operating system, developed by Apple Inc. for iPhone, iPad, and iPod Touch. Updates for iOS are released through the iTunes software and, since iOS 5, via over-the-air software updates. With the announcement of iOS 5 on June 6, 2011, a USB connection to iTunes was no longer needed to activate iOS devices; data synchronization can happen automatically and wirelessly through Apple's iCloud service. Major new iOS releases are announced yearly during the Apple Worldwide Developers Conference (WWDC), and are usually released in September of the same year, usually coinciding with the release of new iPhone models.
 


Anyone know how long Apple supports its latest generation of iPads? I got burned with the 1st Gen iPad when Apple stopped supporting it after two years. It was (and is) a great little tablet, but I use it mostly as an ebook reader now, because the version of Safari on the device doesn't work well with most new websites that use the latest gewgaws and gimcracks in place of sensible interface design principals - just one of the reasons I don't own an iPhone or a newer iPad, which Apple seems to turn into landfill fodder relatively quickly. I won't touch one with a bargepole unless I can get at least four generations of iOS on it and six years of serviceable life.
The iPad Air, released in 2013, can run iOS 12 and run it well. I still have an iPad 2 from 2011 that struggles with iOS 9, but, since its Music app is able to access iCloud music, works as a lightweight music server.
 


Anyone know how long Apple supports its latest generation of iPads?
I have iPads that are 4 years old that use the current iOS. Unfortunately, the 1st-gen iPad had a shortish life. (I also have an iPhone 6, and it runs great with the latest iOS.)

The biggest hurdle for older iOS devices was the move from 32-bit to 64-bit only software. Apple has done a great job of supporting their devices vs. the Android world, where the cheap phones might come with old versions of Android and you can't count on OS upgrades after 2 years. (I hope the Google-made phones do better.)
 


With my (very) preliminary investigation into this, it appears VMWare Fusion can do it. I've set aside some time tomorrow to investigate/test it properly.
Bad news, everyone - I couldn't get this to work. There are many old references on the Internet to converting a .dmg to .vmdk using VMWare Fusion's rawdiskCreator and vdiskmanager utilities (e.g. this one). There are also many references to "p2v" (physical-to-virtual), all of which are great for Windows but ultimately no good for macOS.

I created my .dmg's from working OS X 10.8 and macOS 10.12 hard disk partitions then tried to use the above instructions (or the myriad of similar ones on the internet). None of them would work. The second, vdiskmanager, command would generally fail with a "Received signal 11" error message. Googling this turned up this bug in Fusion 11. I can only assume the bug is still there in v12.

After what many viewed as, Apple's deliberate requirement of crippling VM software to not be able to use the client version of Mac OS X 10.6, I wouldn't put it past Apple that this bug has been deliberately required/introduced to stop users converting a .dmg to .vmdk.

In our use case, this feature would be really useful, but, of course, its primary use would end up being for Windows/Linux users to easily take a pre-installed .dmg of an OS X/macOS installation and convert and run it on non-Apple hardware, which would totally bypass the need for Apple hardware and the requirement to download and use the OS X/macOS installer to set up a virtual environment in the first place. Apple will no doubt take all action necessary to cripple a "feature" that allowed this to happen… (YDVOAMV - Your Dystopian View Of Apple May Vary).

On the good news side, what I could get to work is to create a clean OS X/macOS virtual environment (but not in VirtualBox) and then use Apple's Migration Assistant on first boot to access and use a .dmg clone to copy across the original setup/installation, users, applications and files. Of course, this requires setting up the basic/clean VM in the first place, on Apple hardware with Apple's official OS X/macOS installer, but at least this is possible.
 


Amazon disclaimer:
As an Amazon Associate I earn from qualifying purchases.

Latest posts