Is there any updated version of Ghostscript, required for ImageWriter and many other Printers?
Mojave reports the standard version is 32-bit only.
Is there any updated version of Ghostscript, required for ImageWriter and many other Printers?
Mojave reports the standard version is 32-bit only.
Posted on Oct 7, 2019 12:54 PM
Oct 8, 2019 11:44 AM
<<Am I going to have to do all this work myself 😀>>
Someone cited mathematician from U of Oregon as having an already built and installable Ghostscript 8.7.1 sitting on his web site, ready to install. He has it there to support his colleagues typesetting with TEX variants.
He has moved up to 9.1.7, already packaged into an Installer:
https://pages.uoregon.edu/koch/
So I suggest someone will need to see if that works, for those overwhelmed by the complexity of the big build of gs.
Oct 9, 2019 9:02 AM
In my opinion, Matt Broughton's script to modify those PPD files is rather a hack, compared to the elegant parameterizations throughout CUPS. The entire CUPS system uses parameter from CUPS.conf to specify the directories where the CUPS component parts can be found. His script makes a quick and dirty patch, directly to the PPD file, referencing a specific directory structure. It is unlike anything else in any PPD or elsewhere in CUPS.
I would like to find a way to preserve the elegance of CUPS.Conf file references, rather than having to revert to an inelegant specific directory reference in the PPD files.
--------
I mentioned elsewhere that his suggestion (and I believe his script) deletes one line from the PPD. But deleting that line makes Sharing these Printers across a Network collapse. (I think this may be because the Sharing file-format between most Shared Printers is now PDF, so you cannot just delete that line without substituting another PDF converter).
The reason to delete was that the foomatic converter to PDF files was not as good as the one built onto CUPS.
I think I may have found a solution, sitting in the middle of Generic Printer PPD. These lines:
*% The generic Printer is a PDF cap 00004000 able Printer
*cupsFilter: "application/vnd.cups-pdf 0 -"
DO Indeed work if substituted for the line from the ImageWriter PPD:
*cupsFilter: application/vnd.cups-pdf 0 foomatic-rip
That substitution appears to invoke the CUPS version of PDF conversion, rather than the foomatic version. Once there is an explicit conversion to PDF, Networked CUPS works again.
Oct 16, 2019 12:49 PM
Besides a re-complied 8.71, I think the other top candidate is the 9.20 Ghostscript for PPC and MacOS with installer for MacOS as prepared by Richard Koch U of Oregon. Right after 9.20 Artifex seems to have set about ripping out the PPC support, which is how ImageWriter driver appears to have been tossed aside.
(This link to his page, because the link to that version is the download link.)
https://pages.uoregon.edu/koch/
.
Oct 20, 2019 7:48 PM
Under Mojave:
I tried printing with the 9.20 version (last one before gdevadmp was removed) installed by Dr. Richard Koch's Installer.
https://pages.uoregon.edu/koch/
(it installs both an X11 and a non-X11 version with an Alias defaulting to the non-X11 version). My result: "filter failed" on the Sending Mac, nothing was forwarded to the rasterizing Mac.
I had previously followed other advice to move all of ghostscript and all of foomatic-rip to another folder: /usr/libexec/cups/filters
It appears that move was NOT necessary if you changed to 'Sandboxing relaxed'. in cups.files
So foomatic-rip was no longer in the same folder as the new ghostscript. I thought that might be THE issue.
Rather than dig out the many files, I simply re-installed Foomatic 4.0.6.230, (same version proffered on Linux Foundation site) whose installer still works in Mojave as an Unidentified Developer Install. It placed Foomatic-rip and associated files in:
/usr/local/bin
Did not even have to restart Mac or CUPS, the next print attempt worked just fine, and no warning that gs "was not optimized for your MacOS" (i.e., still 32-bit)
So the 9.20 version probably works. Notarized for Mojave may be an outstanding issue.
I overlooked that this version, while it does include gdevadmp with its IWhi driver, is Intel only, while the 9.19 version (also available through Dr. Koch) includes PPC as well.
Oct 8, 2019 6:53 PM
Grant Bennet-Alder wrote:
If you can move around Terminal and type a few terminal commands, or as you suggested, use HomeBrew, the whole process is not overwhelming.
I agree it's not that bad.
I'm at a roadblock trying to add those three devices to the gs build: iwhi iwlo and iwlq. If you compile gs from source code, it includes a lot of drivers, but those are missing.
Try it for yourself: from wherever it resides on your Mac, run gs -h
It also states "Initialization files are compiled into the executable" which appears to imply you have to add those devices to the build when compiling it. I don't know how to do that, so I'm investigating its documentation.
As far as those devices themselves: The old Linux Printing Imagewriter.pkg won't install in recent macOS versions, perhaps due to SIP, or perhaps other reasons. It doesn't tell you the reason it fails. However, you can manually open the package, and within it find and extract three ImageWriter PPDs. They are readable ASCII text. If you follow my User Tip, that appears to be the package that makes those drivers available to CUPS as well as Printers & Scanners so you can choose its driver, and then everything works.
There is probably more to it than that, but I never knew what it was and no one was talking any more. Anyone who worked on that package seems to be long gone. I know nothing about packaging, but all the other files in that .pkg don't appear to be specific to the ImageWriter. If there are other files required strictly for the IW, I don't know what they are, but it's clear to me you have to include them when building gs from its source. Somehow.
Oct 14, 2019 10:49 AM
John Galt wrote:
Try it for yourself: from wherever it resides on your Mac, run gs -h
My older gs 8.71 (the 32-bit one that worked until Cat) returns a total of 323 "available devices" including iwhi, iwlo, and• iwlq
• The new gs 9.27 returns 335 "available devices" but the three we need are absent. That's an obvious show-stopper.
I have an old VM with 10.7 and Xcode 5.1 installed. I downloaded and built the old gs 8.71. I had to make a small hack to get it to compile. I don’t know what they were doing with that (comment out lines 45 and 46). But it now it builds and is 64-bit. It seems to run on Mojave when I just copy over the gs executable. It seems to have the Imagewriter drivers. It would be better to build on the VM and then do a full “make install” on Catalina. I have no way to test any of this. Contact me and I’ll send you the installable directory.
Oct 16, 2019 11:22 AM
etresoft wrote:
I have an old VM with 10.7 and Xcode 5.1 installed. I downloaded and built the old gs 8.71. I had to make a small hack to get it to compile. I don’t know what they were doing with that (comment out lines 45 and 46). But it now it builds and is 64-bit. It seems to run on Mojave when I just copy over the gs executable. It seems to have the Imagewriter drivers.
Quick update: I installed your gs 8.71 build on both High Sierra and Mojave systems, and I'm happy to report it works! Which is to say the ImageWriter drivers are included, I can print the way I always have on those various systems, and nothing appears to have been broken. My only other (non-Ghostscript related) /usr/local/bin/ files that might have been affected don't appear to have been affected.
I don't know of any better way to inspect its architecture other than the file command, results below:
Prior to installing it (the "old" gs)
iMac4:~ john$ file /usr/local/bin/gs
/usr/local/bin/gs: Mach-O universal binary with 2 architectures: [i386:Mach-O executable i386] [ppc]
/usr/local/bin/gs (for architecture i386): Mach-O executable i386
/usr/local/bin/gs (for architecture ppc): Mach-O executable ppc
iMac4:~ john$
After installing it (the "new" gs):
iMac4:~ john$ file /usr/local/bin/gs
/usr/local/bin/gs: Mach-O 64-bit executable x86_64
iMac4:~ john$
As I wrote I don't know any other way to determine its 64-bit compliance, except for System Information. It does show the "old" gs, but its entry indicates its "last used" date was a few days ago, so that's not a surprise.
It's still version 8.71 which I'm sure you're aware of, but I want that to be clear in the highly unlikely event anyone else is interested.
When making changes like this I try to use my systems for a while in the usual manner before drawing any conclusions, but for now am I correct in assuming that "Mach-O 64-bit" architecture means Catalina ought to load it? Of course it's easy enough for me to try it myself, which I'll get around to doing over the next few days. I just wanted to give you this quick update and say thanks!
Oct 16, 2019 1:52 PM
I have a new installer if anyone else wants to try it: https://etresoft.org/download/ghostscript64.pkg
It is notarized and should install on Catalina without any complaints. It is very similar to the version that John tested above and found to work.
Disclaimer: This is my own web site. This is free software downloaded from (https://sourceforge.net/projects/ghostscript/files/GPL%20Ghostscript/8.71/) with some custom patches and procedures applied. it’s GPL, so contact me if you want full build procedures. Downloading this software or using it could give me some form of compensation, financial or otherwise.
Nov 20, 2019 7:10 PM
Grant Bennet-Alder wrote:
If nothing else, seeing that 9.20 seems to work adds credibility that the main developed versions of Ghostscript going forward may still do the job for Mac users. They don't seem to have changed it so much that it is falling apart for Mac users.
Just to keep you updated, a week or two ago Chris at Artifex told me via email:
"The Apple devices were updated and reinstated as contrib devices."
I don't believe they have quite yet made it into a public gs release, but I expect that it will occur soon.
This is the best possible outcome, much better than I would have imagined. Apple's 35 year old ImageWriter printers are alive and well in Catalina, with full 64-bit Ghostscript support, thanks to you, Etresoft, and perhaps one or two others in the known universe.
I'll update my User Tips at an appropriate time. I have some other equipment on order (a modern, wireless serial device server, as well as a commercially available cable) which I'll also be evaluating presently.
Thank you all! Without your interest this outcome would never have gotten off the ground.
😄
Oct 7, 2019 4:22 PM
<<ImageWriter to remain operational, provided it remained so under Mojave.>>
It works under Mojave, provided you have been keeping up and have already moved gs and all the filters from:
/usr/local/sbin
to
/usr/libexec/cups/filters
Mine still spools to an AppleTalk ImageWriter with an iPrint adapter via AppleTalk-over-Ethernet provided by a 10.4 computer on my network.
I was watching it print and saw the momentary warning that gs was not updated or something. Then it dawned on me what "gs" was, and why it was in trouble. gs=ghostscript 8.7.1
Oct 7, 2019 9:19 PM
Grant, the gs I've been using resides at /usr/local/bin/gs on all my Macs.
It's obviously been working there, so your installation is different. I never moved gs or anything else to /usr/libexec/cups/filter although that folder contains an alias of foomatic-rip that points to /usr/local/bin/
I was under the impression that's where it should be so I don't know why yours is different. Give me some time and I'll post screenshots of my corresponding folders so you can compare them to yours.
etresoft wrote:
I just compiled Ghostscript. Only took about 3 minutes. I don’t know if there are any associated files requires. The basic gs command seems to work.
Same here, so I now have gs version 9.27.
That's about all I've done so far though. I think moving it to /usr/local/bin/ at least ought not to break anything.
Yes there are a lot of associated files, and if any of those existing files poses a problem I'll have a lot more work on my hands. Those files are the product of package installers that don't function any more.
Packaging is something I've wanted to do for a long time. If I ever figure that out, I'll update the Linux Foundation's webpage. I didn't think there was anyone interested in those printers any more.
Oct 8, 2019 11:38 AM
RE: location of gs and filters
You may (or may not) recall that at 10.7 cupsomatic broke, and YOU moved on to Foomatic-rip. But mine is not exactly like yours, so mine kept on working for years after that.
I print to another computer across my home network. That means that only the first part, making a PDF out of the Print stream, is processed locally. Then that pdf is sent across the network to a computer running 10.4 CUPS and Foomatic for rasterization and eventual printing.
My cupsomatic did not break until MUCH later. When I went looking for the reasons, I found a whole lot of information from people whose Foomatic printers had stopped working, mostly due to increased sandboxing. Solutions proffered included:
1) Matt Broughton's script and advice in your old thread discussing this issue. His recommendation to "remove one line" completely broke networked CUPS. I was not pleased.
2) addition of "Sandboxing relaxed" in a CUPS configuration file.
3) suggestion from completely different sources to move gs and filters to a less-restricted location (also to get around sandboxing). THAT is what I mistakenly thought I got from you, but it turns out to be from another source. and your are now saying it was never even necessary.
I seem to have implemented both 2 and 3, and also had to fix the .ppd file because its margins were wrong. But I had also lost a preference file from an App I use, and that caused additional printing grief.
Oct 9, 2019 6:34 PM
I started at Linux Foundation web site and tried to find source for Ghostscript 8.71. I found an old source code repository. Source for Ghostscript 9.04, and gdevadmp.c is present in the base folder -- (circa August 2011).
base/gdevadmp.c n 00004000 ot present in 9.05: it looks like at that point Artisoft is moving more strongly toward GhostPDL, built on top of Ghostscript. That may be the motivation for "streamlining".
A search shows notes about changes for 64-bit versions occurring in early 2011, so this may be the version that still supports ImageWriter (and older gdev's) AND 64-bit versions.
Oct 7, 2019 1:01 PM
Tried building (only) x86_64?
https://www.ghostscript.com/doc/9.27/Make.htm
Homebrew lists Catalina, too:
Oct 7, 2019 2:18 PM
Have you already checked the supported printer list in Gutenprint 5.3.3?
Originally posted at discussions.apple.com/thread/250711255