
- #Epson scanning software mac drivers#
- #Epson scanning software mac driver#
- #Epson scanning software mac upgrade#
- #Epson scanning software mac code#
#Epson scanning software mac driver#
According to the descriptions, the "Epson Event Manager" must be installed after the "Scanner Driver and Epson Scan Utility 2".
#Epson scanning software mac drivers#
Three appear to be for different scanner drivers and utilities. What are they are for? Epson does a poor job of presenting this info.Ĭlick on the "+" signs next to the names for more info.
#Epson scanning software mac upgrade#
Whatever, we'll wait and see-but not upgrade quickly.įive different download options. Just getting by seems to be the attitude maybe because hardware is their main product. Epson has the resources but this is an area that seems to lack support. Assuming they have the resources to do so, of course. That said, combining this "push" with the mandatory 64-bit requirement may be enough for hardware companies to just write new everything for Catalina (user app and device driver). The last gossip I saw was that this wasn't going to be mandatory with Catalina.
#Epson scanning software mac code#
I think those may have a mandatory requirement of being code signed.Īdditionally, with Catalina I believe Apple is pushing driver developers to move from using kernel extensions (KEXTs) to writing their drivers with DriverKit to run in user space. For example, while you can manually bypass OS warnings to launch unsigned apps, I'm not sure if the same is true for loading of device drivers. It's my understanding that device drivers have some requirements which are similar (or identical) to apps and some that are specific to just drivers.

Second, you have the device driver that the OS interacts with. First, you have the application that you, the human user, interacts with. Overall, just remember that when you're speaking about hardware such as scanners there are potentially two "layers" of concern. I use several open source programs and if notarization requires a developers license, that seems like a problem. Notarization which one of the responders mentioned: Although the releases have been fairly problem free. For the last several years there hasn't been features that are that important. I'll wait for 10.15.1 or several weeks particularly with this issue. Would be surprising if Epson abandons all the scanners that use their 32-bit software. And given the major changes Catalina's unleashing on us, it might be a good idea to wait a while before updating to Catalina. It can be very hard I know, but this is a good time to be patient.

But I've got enough software and would prefer to have Epson do it. From my perspective, unless you really need something in Catalina (that's "need", not "want" or "looks interesting"), waiting could save a lot of hassle. This doesn't bother me yet, as Catalina betas are still evolving and vendors may want to wait until the final release to start final testing of any versions supporting Catalina that they plan to release. However, Catalina hasn't shipped yet and Epson isn't the only vendor who hasn't yet released Catalina compatible versions. The component that concerns me the most is Epson Printer Utility, as I haven't found a printer monitoring replacement yet. I've also found that the current version of Swift Pubisher can replace PrintCD. VueScan is an excellent alternative to Epson Scan.

According to Go64 and other 32-bit detection software I've run, all Epson software is 32-bit and thus won't run in Catalina.
