MacInTouch Amazon link...

macOS 10.15 Catalina

Channels
Apple, News
... If VueScan uses the ICA driver, then that would also be an option. The web page doesn't say which driver it uses, only that Apple should auto-install it, which implies, but doesn't state that it is the ICA driver...
The current VueScan release notes:
If your scanner isn't on this list, VueScan may still work with your scanner if you can find a WIA driver (Windows) or an Image Capture driver (Mac OS X) on the scanner manufacturer's web site.
I should have some time to run some experiments on some "clean" OS instances in the next couple of days, but I suspect what happens in this mode is that VueScan is limited to the same set of abilities that Image Capture is. You are just getting the VueScan GUI.

I suspect the problem here is that Apple's Image Capture app, and the ImageKit (and Quartz) framework it is layered on top of, is too "lowest common denominator" and that non-mainstream stuff, like infrared lights/camera, multi-lens, etc. just aren't covered by the framework. Cameras and scanners were not covered by Apple's IOKit for drivers but by a different mechanism. Another contributing factor here is probably a "falling between the cracks" in the IOKit to DriverKit transition and this class of peripherals (and the scanner vendors wanting proprietary scanner apps as a product differentiation tool).

Brother and some other scanner makers are pointing folks at Apple's Image Capture app for 64-bit macOS 10.15 support. So, many scanners are getting up-to-date ICA drivers, but that is mainly to enable Image Capture, not the legacy apps. It would be smart for VueScan to ride that same wave, if they can tap into ImageKit foundations, too. (They'd pick up all the coverage that the standard bundled app got, too.)
 


Well, Catalina keeps sounding worse and worse, the more I read. I know that I’ll have to move to it eventually but am in no hurry. It occurs to me that I might have fewer problems if I did a clean installation and then restored my software and documents from Time Machine. How has this worked for those who have tried it?
For many years (since System 1.0) my occupation has included testing the viability of using a new macOS on various work computers. For Catalina, I started with a clean system install, as well as clean installs of all applications. Microsoft Office and Adobe Creative Cloud, plus a diverse group of utilities. We use Apple Mail, and my previously archived messages were all imported manually, as were all documents. It's a tedious process, but when a major OS upgrade is involved, this often saves a lot of trouble over time.

I'm only one week in, but so far, Catalina has been both stable and fast. Most of the exceptions, like audio components, have been mentioned here.
 


I'm running Catalina in VMware. I used the default disk size of 40 GB, assuming that would be enough for a system with no App Store or 3rd-party software installed. Wrong. The 10.15.1 update said it needed 18 GB. Only 14GB was free. I assume there's at least 10 GB of space occupied by installers I downloaded and deleted. APFS...

I shut down Catalina and expanded the drive to 60 GB in VMware's settings. After booting Catalina, the drive did not expand to include the new 20 GB. I used Terminal to manually expand the drive. First, use this command to identify the container on the startup drive:
Code:
diskutil list
...
/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                        40.0 GB   disk3
                                 Physical Store disk0s2
   1:                APFS Volume Catalina                 40.0 GB   disk3s1
...
Look for "(synthesized)", then "Physical Store" with the name of your boot drive immediately below (mine is "Catalina"). The Physical Store is what's needed; mine is disk0s2. Then use this command (with the container's disk from above) to expand the container (0 says use all available free space):
Code:
sudo diskutil apfs resizeContainer /dev/disk0s2 0
That's it, now Catalina is using the full size of the VMware drive.
 


I have an Epson V330, and when I look that up on VueScan’s extensive list of scanners supported, the support page says... which appears to mean that for Catalina it just doesn't work until suitable 64-bit drivers are developed.
I have a V500 with VueScan. Works fine in Catalina (upgraded via migration).
 





I'm getting more and more fed up with Apple. Their products are good and their support is top notch, but the gap is narrowing between them and Windows. Pretty soon these two will be equally bad. In the last few years it seems as though Windows usability has gone up while Apple's has gone down.
I, like you and many others on this forum, am fed up with Apple for a variety of reasons. However, in my opinion, their products are not as good and their support is not what it used to be.
 


Ric Ford

MacInTouch
I'm running Catalina in VMware. I used the default disk size of 40 GB, assuming that would be enough for a system with no App Store or 3rd-party software installed. Wrong. The 10.15.1 update said it needed 18 GB.
This gigantic update space demand is absolutely bizarre. I can't imagine what's going on there. Here's more confirmation of the issue:
Mr. Macintosh said:
What’s New in the macOS Catalina 10.15.1 Update (19B88)?
... First thing to note is the SIZE of the update! The Point Update clocks in at 4.49gb!!! That’s over 50% the size of the main installer app! (The full installer is 8.63gb).

... When you have an update that is almost 5gb in size, you also have to take in to account how much extra free space you will need. For this update you may need up to 20gb of free space to even install the update.
 


Worth a try. Epson's product page for the V500 and maxOS 10.15 links to ICA driver v5.8.7 (released a few weeks ago on October 7th), which says it supports macOS 10.5 through 10.15. But the driver description also has this cryptic footnote...
... So, to anyone with a V500 that has already upgraded to Catalina, go download and install (if necessary) the Epson ICA driver and see if you can scan via ImageCapture. If you can, then download and try VueScan. And please let us know the results of your tests.
Much to my surprise, and delight, when I just checked Epson's product page for my aging V330 and pretended to have macOS 10.15, I found that Epson has uploaded a new version of the scanner software, Epson Scan 2, which is 64-bit and can run on Mojave, as well as on Catalina.

So, Epson is upgrading its scan software for older models as well as recent ones. Note that you won't find the new version unless you look for software for macOS 10.15.
 


Apple has been deprecating the Internet Radio section of iTunes Music for a while. Sometime ago, it stopped updating the directory. Nevertheless, you can still play URL streams in iTunes and even create playlists (although they will not be synced through iCloud nor play on mobile devices).

Catalina Music apparently drops the Internet Radio section, but streams will still play (at least that is what I have heard, as I have not upgraded yet). Glenn Fleishman has provided a guide to preserving access to your streams here. Note that it involves exporting playlists from Mojave iTunes and then importing them to Catalina Music.
 


Ric Ford

MacInTouch
A couple of cautionary tales from Reddit for what they're worth:
Reddit /r/mac said:
PSA: Don’t upgrade to Catalina 10.15.1 if you have a mac Mini
My Mac mini 2018 version bricked when I tried upgrading from Mojave to Catalina this morning. Genius Bar guy says they received a number of such cases. Have to replace the whole motherboard.
Reddit /r/mac said:
A bit of frustration...
I just downgraded back to Mojave from Catalina after a few weeks. My Mid-2015 MacBook Pro had 600+ console entries relating to intel graphics and GPURestart tailspin’s. Had a few kernel panics as well whenever using MS word or Logic Pro X, There were so many system hangs in logic that my workflow was toast.
When I spoke with Apple support after signing in and picking my MacBook Pro/serial number from the list, I ran through the hardware diagnostics and several other information gathering steps with nothing out of the ordinary discovered. I was told the error messages were “beyond the scope of what Apple can support”. I asked for clarification as to why the components soldered on to the logic board and interacting with their software ( I asked to focus on the messages being generated by logic) was beyond the scope of troubleshooting and support and it was just repeated back to me. No offer of a genius bar visit or other potential next steps (I told them the money was not important if there would be a cost associated, I just need to get my computer working again)
After saying I was tapping out and wanted to go back to Mojave, Apple support was unable to send me a link to download the installer as it was no longer accessible on the App Store and kept sending me different links to various patches and updates but never the actual installer. I eventually closed the chat and had to use DosDudes patching tool to get the installer from their servers in order to make a bootable drive.
After getting Mojave installed the console entries are no longer appearing and everything is working as expected.
I’ll keep my eye out for any updates versions and GPU fixes but this launch has been disastrous for many. I was super disappointed in my experience with Apple support this time, I usually have been accommodated and experience great customer care.
 


But it seems a little disingenuous to imply, as the developer did, that just out of the blue Apple shipped an OS that doesn't support Carbon or 64-bit apps. If they couldn't figure out which way the wind was blowing after more than ten years, it makes me wonder how on-the-ball they really are.
For context, this particular developer has a very large number of relatively low-cost plug-ins. I own a couple of them. They tend to be very flexible, at the expense of usability and elegance. These issues extend to the plain-but-configurable user interface shared by all of their plug-ins, which they advertise as "the most advanced GUI engine on the market." I corresponded with their developer about a serious usability issue related to nonstandard rhythmic nomenclature (what the rest of the world recognizes as a dotted eighth note, they call a dotted quarter note instead, reflecting internal values rather than user norms); they were friendly, but not interested in fixing the problem. In sum, they are somewhat idiosyncratic.

That said, other plug-in developer friends have long expressed frustration with Apple's constantly-changing audio standards, which have indeed required a lot of reworking of previously functional code - in contrast to Windows' focus on backwards compatibility. That particular issue seems to be a bit calmer recently, but reworking to satisfy security requirements is taking its place. (The elimination of 32-bit support is less of an issue for audio plug-ins, since most audio host applications forced plug-ins to move to 64-bit some time ago.)
 


Have been dealing with family matters and other business recently but now am back on track with testing Apple's latest shenanigans (Catalina, installers, etc) and updating MacStrategy. First up: Catalina and FireWire booting…
... I can therefore confirm, with my limited/basic testing, FireWire is not supported for booting macOS 10.15 Catalina!
I did this testing weeks ago and reported it to MacInTouch. My findings were confirmed by Bombich Software, makers of Carbon Copy Cloner....
 


Apple has been deprecating the Internet Radio section of iTunes Music for a while. {snip} ...Glenn Fleishman has provided a guide to preserving access to your streams here. Note that it involves exporting playlists from Mojave iTunes and then importing them to Catalina Music.
Thanks for sharing that important tip, as it is far superior to trying to add favorite Internet Radio feeds to Catalina's Music.app manually, especially since the default name of a manually added Internet Radio feed in Catalina is the feed's URL!
 


Waited until yesterday to install Catalina. Many restarts, bluetooth failing (luckily, I have an old USB mouse and keyboard), Spotlight going mad, as usual, until I essentially emasculated it and used EasyFind, which still works, Safari mistakes, opening many apps causes them to open last window instead of blank input screen.

Poor QA and obvious poor management of QA function. One would expect several heads should roll because of this mess. An announcement of regret from Apple and answer as to what they are going to do about it and the tremendous waste of time its customers have had to endure.
 


I did this testing weeks ago and reported it to MacInTouch. My findings were confirmed by Bombich Software, makers of Carbon Copy Cloner....
I wonder if a FireWire disk could be used for startup if connected via a FireWire-Thunderbolt adapter? Or even via a FireWire-Thunderbolt adapter connected to a Thunderbolt-Thunderbolt 3 adapter?
 




I wonder if a FireWire disk could be used for startup if connected via a FireWire-Thunderbolt adapter? Or even via a FireWire-Thunderbolt adapter connected to a Thunderbolt-Thunderbolt 3 adapter?
My testing was conducted with a Mac Mini 2014 Thunderbolt 2 port <-> Thunderbolt 2-FireWire 800 adaptor <-> FireWire 800 cable <-> 2.5" hard disk in a FireWire 800/USB2 enclosure. Catalina can't be installed on it and can't boot from it (when cloned).

However, the same drive shows up fine over USB2 and can be seen by the Catalina installer as an "allowable" installation location.
 


Your comment about the 2012 Mac Pro quad-core no longer booting after an update is why I have held off on updating my 2010 Mac Pro quad-core, with a Metal-capable GPU, to Mojave. Having a bricked machine scares me. I'm curious about what you might have been able to do to fix it.
Oh, [the Mac Pro] wasn't bricked, just something wrong with that particular OS install. Another drive in the computer still booted fine, and I could have likely fixed it, but it wasn't worth the time for me vs. getting the newer Mac Mini setup (and I'll likely use it for 6 years or so, may add an eGPU at some point).
 


My testing was conducted with a Mac Mini 2014 Thunderbolt 2 port <-> Thunderbolt 2-FireWire 800 adaptor <-> FireWire 800 cable <-> 2.5" hard disk in a FireWire 800/USB2 enclosure. Catalina can't be installed on it and can't boot from it (when cloned). However, the same drive shows up fine over USB2 and can be seen by the Catalina installer as an "allowable" installation location.
Thank you to all who've turned a digital wrench to answer the whether question about Catalina FireWire booting.

Can any of us speculate and/or venture an educated guess as to why Apple has shut down FireWire startup? I didn't renew my Apple Developer account this year ($$ and TFA), so I can't search whatever documentation there might be. Security? APFS? Both? Neither?

I'm going try booting from the Catalina installer block-copied to a partition on a FireWire-attached storage device in the hope that, because it'll be an HFS+ volume, it'll boot. I certainly hope it does, if for no other reason than to feel justified in shaking my fist toward Cupertino, but...
 



Ric Ford

MacInTouch
Can any of us speculate and/or venture an educated guess as to why Apple has shut down FireWire startup?
Since FireWire does still work, just not at startup, there's presumably a problem with the FireWire boot driver, but I'm not sure what it is, exactly. What has changed in Catalina's version of boot code (which is, of course, a radically different and special environment)?

This must be a change in firmware and part of Catalina's prerequisite firmware update(s). Hmmm, does FireWire Target Disk Mode work or not after a Catalina firmware update? And can you still boot macOS Mojave from FireWire after a Catalina firmware update?
 



... This must be a change in firmware and part of Catalina's prerequisite firmware update(s). Hmmm, does FireWire Target Disk Mode work or not after a Catalina firmware update? And can you still boot macOS Mojave from FireWire after a Catalina firmware update?
Ohhhh, I sure hope so... (I'll find out, and get back to y'all.)
 


This must be a change in firmware and part of Catalina's prerequisite firmware update(s). Hmmm, does FireWire Target Disk Mode work or not after a Catalina firmware update? And can you still boot macOS Mojave from FireWire after a Catalina firmware update?
Ohhhh, I sure hope so... (I'll find out, and get back to y'all.)
With the caveat that I haven't tried (no time right now) to perform an installation in either configuration, here's some good news:

The 2013 Mac Pro 6,1 boots from an "Install macOS Mojave" (10.14.6) partition on a Seagate GoFlex FireWire 800-attached 2.5" Hitachi hard drive.

The 2010 Mac Pro 5,1 boots from an "Install macOS Mojave" (10.14.6) partition on the internal SSD in the Mac Pro 6,1 running in FireWire Target Disk Mode and attached with a FireWire 800 cable to the Mac Pro 5,1. (I know the installation wouldn't currently work, because I don't have a Metal-capable graphics card.)
 



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

Latest posts