10 Replies Latest reply on Apr 22, 2013 3:14 PM by Michael Wineke

    Automatic Popup and Printer Queue Configuration for Mac OS X

    Kevin Maestre Newbie

      Attempting to update Mac Popup client 8.1 to 8.3.2 using TechNote:  Automatic Popup and Printer Queue Configuration for Mac OS X in Uniprint 8.1, which was updated on 29 October 2012. The popup client installs successfully, but it does not create the printers.

       

      For example:

      installFiles.txt = /etc/cups/ppd/RICOHAficioMP2851.PPD

      Postinstall.sh = lpadmin -p  A Hall -v popup://pharos/ald -E -P RICOHAficioMP2851

        • Re: Automatic Popup and Printer Queue Configuration for Mac OS X
          Alex Schumacher Wayfarer

          I just looked through the guide you mentioned, and it's different from what I remember doing a short while ago for an 8.3 custom Popup installer. Here's what I did, hopefully it's helpful / still relevant.

           

          1. Make the Popup.dmg writeable.

           

          2. Right-click on the Popup.pkg file and go to show package contents.

           

          3. in the Popup.pkg>Contencts>Resources folder

           

          - copy the PPD file for the printer.

           

          - Edit the configuration.plist file like the one attached to this post

           

          - Edit the postflight script to include any print driver settings you may want (example attached)

           

          4. Convert the dmg back to compressed

           

          5. Deploy as package installer or dmg for manuall installation!

          • Re: Automatic Popup and Printer Queue Configuration for Mac OS X
            Michael Wineke Wayfarer

            Two possible issues:

             

            It might not like the "A Hall" printer name. Try A_Hall instead.

             

            Otherwise,..

             

            By any chance, did you copy the lpadmin command from the technote and paste it into a text editor?

             

            I did, then couldn't understand why it didn't create printers. lpadmin doesn't complain about anything being wrong with the command, either.

             

            Turns out, the text editor dutifully accepts the ascii characters, but while ascii, they aren't correct. The issue is the dashes, in my case.

             

            Replace the long dashes with regular dashes.