MacInTouch Amazon link...

Apple compatibility issues

Channels
Apple
I did some testing this week with LibreOffice on dozens of his AppleWorks files, and was shocked (and delighted) to discover that LibreOffice opens AppleWorks database files!
For those of us who spent time in DOS / Windows before moving to Mac, LibreOffice will also open and convert Microsoft Works Database files (file type .wdb) to speadsheets.
 




Note: LibreOffice basically opens the AppleWorks database files as a spreadsheet; but Dad's databases were pretty simple, and he views them in tabular format anyway. It provides him with some way to view his data, and that's the important part.
As far as I remember, AppleWorks databases were not relational - a single table per file - so migrating to a spreadsheet isn't a bad solution. You lose the layouts, but you should end up with all the data.

Unfortunately, there's still no way (unless it was recently added) to import an AppleWorks drawing file. Every importer I've tried over the years has failed on these. They usually end up just importing the text boxes, but with none of the vector graphics.
 


Ric Ford

MacInTouch
Unfortunately, there's still no way (unless it was recently added) to import an AppleWorks drawing file. Every importer I've tried over the years has failed on these. They usually end up just importing the text boxes, but with none of the vector graphics.
I haven't tried this, but MacWorld said (back in 2012) that Intaglio could do it.
Macworld said:
Opening (very) old AppleWorks and Word documents
One place where I found this did not succeed was with documents created using AppleWorks Draw module. I assume this is because no iWork app directly corresponds to the Draw module. Fortunately, third-party apps come to the rescue here. To find out if I owned one of these apps, I selected Open With from the contextual menu of a reluctant AppleWorks file. A likely compatible app showed up in the list: Intaglio. I selected the app and, just as I had hoped, the file opened.
Or EasyDraw might work:
EazyDraw said:
AppleWorks Import
EazyDraw Retro, version 9.0.2, is provided as a full solution for AppleWorks and the other classic drawing formats. EazyDraw Retro runs fine on Mojave and all older versions of OS X back to 10.4.11 . Use it to open AppleWorks (MacDraw, MacDrawII, MacDrawPro, ClarisDraw) drawings directly on macOS 10.14. Save the drawings to EazyDraw graphic format for use by all other versions of EazyDraw. EazyDraw Support has a download link and more information. EazyDraw Retro runs on OS X 10.4.x and newer, including Mountain Lion.
 



I have definitely used Intaglio to convert MacDraw II files - several versions up to 10.12. Not sure beyond that as not sure I have systems that will go higher. I am converting single line drawings, some with thousands of objects in the drawing.
 


Ric Ford

MacInTouch
I can confirm that EasyDraw Retro (on Mac OS X 10.6 to OS X 10.10 and earlier systems) does open MacDraw and ClarisDraw files. The demo version of Intaglio (3.4.4) also opens MacDraw and ClarisDraw files on Mac OS X 10.6 and OS X 10.10 systems.
I have definitely used Intaglio to convert MacDraw II files - several versions up to 10.12. Not sure beyond that as not sure I have systems that will go higher.
I just took a look at the Intaglio website:
  • The most recent version was an update for macOS 10.13
  • Purchasers are directed to Kagi... which collapsed and no longer exists....
 


I just took a look at the Intaglio website. Unfortunately:
  • The most recent version was an update for macOS 10.13
  • Purchasers are directed to Kagi... which collapsed and no longer exists....
macOS 10.13 High Sierra isn't that old. Perhaps nothing needed to be changed since then.

Purchasing Intaglio says...
Purgatory Design said:
Unfortunately the company we've been using to operate our online store since 2003, called Kagi, abruptly stopped doing business recently. Until we can get a replacement working we're handling all orders via email at sales@purgatorydesign.com. Please contact us directly for purchasing options.
I agree that the fact they haven't updated the Kagi links reflects poorly.
 


I just took a look at the Intaglio website. Unfortunately:
  • The most recent version was an update for macOS 10.13
  • Purchasers are directed to Kagi... which collapsed and no longer exists....
Here is correspondence I had with them last week.
On Oct 17, 2019, at 8:34 AM, Fred Kinder ... wrote:

I tried to purchase Intaglio from your web site, but the following link is dead.

++++++++++ Response +++++++++

I’m sorry for the inconvenience, we’re working on a replacement for our old provider Kagi. FWIW, there’s some info here: Purchasing Intaglio

For now, we are processing sales manually. If you send $89 USD to sales@PurgatoryDesign.com via PayPal, I’ll make sure to get a serial number back ASAP. If you don’t have a PayPal account, we can send you a PayPal invoice that you can pay with a credit card, without the need for an account.

Regards,
Nick Nallick
 


(Also, will it run Linux, unlike new MacBook Pros?)
So, after looking into this, the problem with T2 MacBook Pros is that so many functions are being crammed through the T2 chip that require new drivers and/or kernel patches. This (non-exhaustively) includes SSD controller, Secure Boot, audio input/output, keyboard and trackpad input, camera image processing, SMC controller. And WiFi, which is not related to the T2 chip, but seems to require separate kernel modification to get going.

The nice thing about the Mac Pro is that a lot of these issues specific to the MacBook Pro will not apply. It does not have an integrated keyboard and trackpad, and no camera. Audio output via T2 has been resolved. I believe there is a kernel patch that allows addressing the T2 controller and the built-in SSD. If not, a standard NVMe SSD should be able to be used in the NMVe slot (with External booting enabled, and Secure Boot disabled for Linux). WiFi is unknown, but if it's a problem, you can always use Ethernet or a supported WiFi USB dongle. And, of course, it does not have a camera built-in.

The Mac Pro's Linux challenges should be similar to the iMac Pro, with the differences being that it does not have a camera like the iMac Pro, and it has the additional NVMe slots that should be able to be used as alternative boot media. I did not find people with many issues running Linux on the iMac Pro.
 


Don’t they run [Linux] if you disable T2 Secure Boot?
Nope. I tried again yesterday with Mint 19.1 and the 2018 MacBook Pro, which kernel-panic'd.
After way too much looking into this issue (after all, I've never even owned a MacBook Pro), I found that it appears the most work on getting Linux running on T2 MacBook Pros is happening here on Github. At the moment, you're not going to get Linux running without a lot of manual work, patching kernels and adding drivers. Some of these modifications will make their way upstream to Linux distributions eventually, but some might never.
It seems like a lot of these things may have been compiled here, but there's not much in the way of documentation or instructions there.
 


Ric Ford

MacInTouch
So, after looking into this, the problem with T2 MacBook Pros is that so many functions are being crammed through the T2 chip that require new drivers and/or kernel patches. This (non-exhaustively) includes SSD controller, Secure Boot, audio input/output, keyboard and trackpad input, camera image processing, SMC controller. And WiFi, which is not related to the T2 chip, but seems to require separate kernel modification to get going.
The problem is that Apple doesn’t permit booting Linux: post-19247
 



Ric Ford

MacInTouch
Sure it does. In the article you linked, just follow the instructions to change the Secure Boot setting to “No Security”. There are plenty of people booting Linux on T2 Macs today.
It doesn’t work for a 2018 MacBook Pro, as I’ve shown. If you can find someone successfully booting Linux on that computer, please provide the details.

It may work on other T2 Macs, but Apple omits any mention of Linux in a support document, citing only Macs and Windows: About Secure Boot - while there’s this Linux signing issue:
Phoronix said:
Apple's New Hardware With The T2 Security Chip Will Currently Block Linux From Booting

... Apple's T2 documentation makes it clear and explicitly mentions Linux:
NOTE: There is currently no trust provided for the the Microsoft Corporation UEFI CA 2011, which would allow verification of code signed by Microsoft partners. This UEFI CA is commonly used to verify the authenticity of bootloaders for other operating systems such as Linux variants.
In other words, until Apple decides to add this certificate or the T2 chip otherwise is cracked so it could be fully disabled or allowed to load arbitrary keys, good luck even being able to boot Linux distributions on the new Apple hardware.
But maybe Apple has subsequently added a “UEFE CA” for Linux in a firmware update, as I could at least start to boot Linux before it kernel-panic’d.
 


It doesn’t work for a 2018 MacBook Pro, as I’ve shown. If you can find someone successfully booting Linux on that computer, please provide the details.
You're not being prevented booting Linux by Secure Boot (if you set it to "No Security"). You can't boot it because you're running an unpatched distribution. That's simply a hardware compatibility issue, not a security policy enforcement. All the details are in my earlier post. I tried to distill the essentials as much as I could, but unfortunately, you may need to spend hours reading, as I did, in order to understand it all. The bulk of the discussion is in this monster thread, where people are troubleshooting issues and booting their T2 MacBook Pros in Linux.
That article is wrong, basically. It was written based on inaccurate and incomplete information. They get it correct at the end where they say disabling Secure Boot will allow Linux to boot. Then they get it wrong again in Update 2, where they cite another issue, the T2 SSD Controller, which is unrelated to Secure Boot, which is what the entirety of the rest of the article is about. It is true that at the time, the T2 SSD controller was not addressable, which made the internal SSD drive inaccessible. That, however, did not prevent booting Linux from external media. Since then, the kernel patch published in July 2019 that I mentioned in my other post makes the internal drive accessible to Linux, so even that is not an issue.
But maybe Apple has subsequently added a “UEFE CA” for Linux in a firmware update, as I could at least start to boot Linux before it kernel-panic’d.
They haven't. But code signing would only come into play if you had Secure Boot enabled ("Full Security" or "Medium Security"). In order for you to have gotten as far as you did, you must have Secure Boot currently set to "No Security", right?
 


After way too much looking into this issue (after all, I've never even owned a MacBook Pro), I found that it appears the most work on getting Linux running on T2 MacBook Pros is happening here on Github. At the moment, you're not going to get Linux running without a lot of manual work, patching kernels and adding drivers.
I just skimmed through the hundreds of entries on the Github referenced by Todd.

Yes, with a kernel patch, some have booted Linux on T2 Macs. To find flaky fans, no sound, screens going black, USB-C connection problems, and more issues.

One interesting factoid I picked up about how things work on the T2 is SMC, known to we Mac users a long time, is built into the T2. Seems that results in Windows installs (authorized by Apple) not being able to directly access the audio processing system; the Apple workaround for Windows installs is to process audio through the GPU.

If Apple had wanted to permit Linux installs on Macs with the T2 chip, none of this would be necessary. Out in the real world, unless the well-intentioned hobbyist/hackers on Github can somehow assemble all the software components, which are then integrated into a mainstream Linux distribution, don't expect Linux to run on a T2 Mac. Even if it gets to the point of running successfully, if the Mac is connected to Apple for updates, don't expect it to keep booting Linux....
 


It doesn’t work for a 2018 MacBook Pro, as I’ve shown. If you can find someone successfully booting Linux on that computer, please provide the details.
I found that someone has spun a custom Fedora 30 ISO with all the available patches and drivers pre-installed. If you've got some time, maybe you'd like to test it out and see how well it works by following the directions here?
 



I'm late to the party of HEIC. I was sending an email to my sister (I gave her a rehab 2015 MacBook Pro 13"), and she couldn't view the images. I changed the setting on my iPhone 8 Plus (with iOS 13.3) under Settings > Formats > Most Compatible. (Thanks, Apple, for making High Efficiency file the default.)

Odd, since her MacBook Pro is on the last version of High Sierra....
 




About two weeks ago, I updated my iPhone 7 Plus from iOS 12.x to iOS 13.3.1. With no problems resulting from this, yesterday I updated my spouse's iPhone 7 Plus from iOS 12.x to iOS 13.3.1. The update went smoothly.

Unfortunately, today, upon connecting her phone via USB/Lightnning cable and opening up Photos, her 2015 MacBook Pro running Mojave now throws an error message saying she has to update her Mac to Catalina to connect to her phone.

I did not get this message, but I'm using a 2009 Mac Pro running Mojave.

I would prefer to not update her MacBook Pro to Catalina as a) I can't do it on my Mac Pro and it will make support more difficult and b) she doesn't need it.

So, short of installing the unwanted Catalina, how can I get out of this box?
 


About two weeks ago, I updated my iPhone 7 Plus from iOS 12.x to iOS 13.3.1. With no problems resulting from this, yesterday I updated my spouse's iPhone 7 Plus from iOS 12.x to iOS 13.3.1. The update went smoothly.

Unfortunately, today, upon connecting her phone via USB/Lightnning cable and opening up Photos, her 2015 MacBook Pro running Mojave now throws an error message saying she has to update her Mac to Catalina to connect to her phone.

I did not get this message, but I'm using a 2009 Mac Pro running Mojave.

I would prefer to not update her MacBook Pro to Catalina as a) I can't do it on my Mac Pro and it will make support more difficult and b) she doesn't need it.

So, short of installing the unwanted Catalina, how can I get out of this box?
Could this be related to the "MobileDeviceOnDemand" package update issues from message #21670?
 


I updated my spouse's iPhone 7 Plus from iOS 12.x to iOS 13.3.1. The update went smoothly.

Unfortunately, today, upon connecting her phone via USB/Lightnning cable and opening up Photos, her 2015 MacBook Pro running Mojave now throws an error message saying she has to update her Mac to Catalina to connect to her phone.
I wish I could help, but I updated my 7 Plus today, disconnected and later reconnected my iPhone, under Mojave 10.14.6 on a 2017 5K Retina iMac, and it reconnected to iTunes and Photos (at least the first time I've tried).
 


Unfortunately, today, upon connecting her phone via USB/Lightnning cable and opening up Photos, her 2015 MacBook Pro running Mojave now throws an error message saying she has to update her Mac to Catalina to connect to her phone.
So, short of installing the unwanted Catalina, how can I get out of this box?
Try simple first: (1) close all apps on both her phone and Mac, then shut down both for at least 30 seconds. Restart, and apply any updates the machines ask for. Then check to see if the problem still exists. If so, then (2) look (with a strong light) into the lightning connector to see if lint has built up. If needed, gently use a nonmetallic object, e.g., toothpick, to clean out. (3) Make sure the iPhone is awake: app buttons are visible when Photos on the Mac is open.
 


About two weeks ago, I updated my iPhone 7 Plus from iOS 12.x to iOS 13.3.1. With no problems resulting from this, yesterday I updated my spouse's iPhone 7 Plus from iOS 12.x to iOS 13.3.1. The update went smoothly.

Unfortunately, today, upon connecting her phone via USB/Lightnning cable and opening up Photos, her 2015 MacBook Pro running Mojave now throws an error message saying she has to update her Mac to Catalina to connect to her phone.

I did not get this message, but I'm using a 2009 Mac Pro running Mojave. ...
My Mac Mini is on Mojave. My iPhone7 and my wife’s 6s Plus are now on iOS 13.3. I get that message when I connect my phone to the Mac. However, I only connect it when I want to offload photos or make a backup.

The Image Capture app included on Mojave works fine to capture photos and videos without requiring a macOS upgrade. And I use iMazing for backups. iMazing complains when it wants to access the old iTunes backups, but I don’t care about that and tell it to proceed.
 


Try simple first: (1) close all apps on both her phone and Mac, then shut down both for at least 30 seconds. Restart, and apply any updates the machines ask for. Then check to see if the problem still exists. If so, then (2) look (with a strong light) into the lightning connector to see if lint has built up. If needed, gently use a nonmetallic object, e.g., toothpick, to clean out. (3) Make sure the iPhone is awake: app buttons are visible when Photos on the Mac is open.
I shut off and restarted the iPhone 7 Plus; checked Settings > General > Software Update and was told that the software was up to date.

I shut off and restarted the 2015 MacBook Pro running Mojave. Checked "Software Update", and the only update available was the update to Catalina, which was canceled.

Connected the phone to the computer via USB/Lightning cable, and the phone shows that it is charging, so the connection appears good.

Opened Photos. The "must do a software update to connect to iPhone" notification popped up. Clicking "not now". We were able to see that the iPhone had connected to the Mac and the iPhone icon was visible in Photos.app. Photos were downloaded to Photos.app just fine, so it would appear that the cable/socket works OK. We can live with the annoying "upgrade to Catalina" pop-up if we have to

Then opened up iTunes, and the iPhone icon did not appear there, so the iPhone backups to the computer and iCloud could not be done. This is a more serious obstacle.

Cleaned the lightning port with a toothpick and canned air. Tried a different USB/Lightning cable. No change.

Any ideas as to what I can try next?
 



Opened Photos. The "must do a software update to connect to iPhone" notification popped up. Clicking "not now".
That software update is most likely not Catalina. It will also not be mentioned with other available updates, because it is specifically needed for connecting an iOS 13 device. I allowed the update while I was still in Mojave. It did not upgrade to Catalina.
Did you check into the issue mentioned in post-21670 and referenced above in post-26559?
 


That software update is most likely not Catalina. It will also not be mentioned with other available updates, because it is specifically needed for connecting an iOS 13 device. I allowed the update while I was still in Mojave. It did not upgrade to Catalina.
So, you are saying that the MacBook Pro needs an update that will not be listed by Software Update as being available?

The Silent Knight app says the Mac is fully up to date, so no clue there.

The previous post talking about the "MobileDeviceOnDemand" must have come in while I was reading another one, as I missed it completely.

FWIW: I didn't get this message when updating my iPhone from 12.x to 13.3.1 while connected to a Mac Pro running Mohave. Must be something different for her MacBook Pro.

Looks like I'll have to accept the mystery software update and see what happens. I really hope it's not Catalina!
 


So, you are saying that the MacBook Pro needs an update that will not be listed by Software Update as being available?
The Silent Knight app says the Mac is fully up to date, so no clue there.
That is correct. For whatever reason, these mobile updates are not discoverable using the normal System Update commands, so neither Software Update nor Silent Knight detect them.

The special treatment of these updates by Apple certainly is very confusing. From a user interface perspective, the way Apple informs a user of these updates frankly has more in common with malware methods than with Apple's normal way of notifying users about a necessary update. The dialog box is very vague and uninformative, the wording is different from other Apple update notifications, and it appears in a context that is different from every other Apple update.
 


That is correct. For whatever reason, these mobile updates are not discoverable using the normal System Update commands, so neither Software Update nor Silent Knight detect them.
The special treatment of these updates by Apple certainly is very confusing. From a user interface perspective, the way Apple informs a user of these updates frankly has more in common with malware methods than with Apple's normal way of notifying users about a necessary update. The dialog box is very vague and uninformative, the wording is different from other Apple update notifications, and it appears in a context that is different from every other Apple update.
Clicking on the ‘More info...’ link in the update dialogue will reveal other pending updates and permit selection of the ones to process.
 


About two weeks ago, I updated my iPhone 7 Plus from iOS 12.x to iOS 13.3.1. With no problems resulting from this, yesterday I updated my spouse's iPhone 7 Plus from iOS 12.x to iOS 13.3.1. The update went smoothly. Unfortunately, today, upon connecting her phone via USB/Lightnning cable and opening up Photos, her 2015 MacBook Pro running Mojave now throws an error message saying she has to update her Mac to Catalina to connect to her phone.
I did not get this message, but I'm using a 2009 Mac Pro running Mojave....
I'm running a 2015 iMac with Mojave 10.14.6 and iOS 13.3.1 and have not had the problem. I suggest you google the issue, as there are tips to help that are available.
 


That is correct. For whatever reason, these mobile updates are not discoverable using the normal System Update commands, so neither Software Update nor Silent Knight detect them.
The special treatment of these updates by Apple certainly is very confusing. From a user interface perspective, the way Apple informs a user of these updates frankly has more in common with malware methods than with Apple's normal way of notifying users about a necessary update. The dialog box is very vague and uninformative, the wording is different from other Apple update notifications, and it appears in a context that is different from every other Apple update.
Clicking on the ‘More info...’ link in the update dialogue will reveal other pending updates and permit selection of the ones to process.
Yes, but this specific update is not listed there. It is only mentioned as a necessary update in a dialog that appears when the iOS device is connected, with no indication at all about what will be updated. That is what makes people hesitant to proceed and allow the update.
 


Clicking on the ‘More info...’ link in the update dialogue will reveal other pending updates and permit selection of the ones to process.
Clicking on the "More Info" link opens up an Apple web page discussing Catalina. Hence my concern...
 


My household has an iMac and a MacBook Pro, both running Mojave, with each machine hosting its own iPhone 6s on iOS 13.3.1 . Both iTunes and Apple Configurator 2 are used to manage the phones and a variety of iPads.

I haven't faced any forced upgrades to Catalina during iOS backups or syncs. I have seen, once on each Mac, the MobileDeviceOnDemand update dialog popup. I think – and I don't have a precise memory of this because it was a couple of years ago now – clicking More Info on the dialog just led to the generic System Updates screen. And since I always lag macOS versions by a year, my System Updates always contains a nag about upgrading to the most recent OS.

In any case, I use both Time Machine and Carbon Copy Cloner for backups so taking an update that Apple claims is required is relatively low risk for me.
 


Thank you to all the folks who helped me realize that the "you need to update your Mac's software to connect to your phone updated to i0S 13.x" message was not a forced update from Mojave to Catalina.

The update went smoothly, and all is now well.

Definite points deducted from Apple for not making this clear.
 


Ric Ford

MacInTouch
Apple software updates break FaceTime compatibility between its own devices?!
MacRumors said:
iOS 13.4 and macOS 10.15.4 Prevent FaceTime Calls From Working With Some Older iPhones and iPads Amid Pandemic
Newer devices running Apple's recently released iOS 13.4 and macOS 10.15.4 software updates are currently unable to make FaceTime audio and video calls with older devices running iOS 9.3.5 or iOS 9.3.6, according to numerous users across the Apple Support Communities, MacRumors Forums, Reddit, and Twitter.
 


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

Latest posts