I tried the script in Puppy 2.16 using pakt's CUPS install v0.3 and it worked as expected (very good). I did notice that everything was "printing" black and white, but did not take time to investigate.

EDIT: I needed to change a couple of lines at the end of the script to read /etc/rc.d/rc.cups instead of /etc/init.d/cups to work with 2.16 properly.

JBLast edited by JB4x4 on Tue 17 Jul 2007, 05:38; edited 1 time in total

OK.
So I installed in my Grafpup 104 install, which uses the latest CUPS dotpup. I went to print something to pdf, then on a whim pressed cancel when it asked me where to save it. Now when I try to print to pdf the job gets added to the queue, it asks me where I want to save it, and then it pauses the printer (according to CUPS). Telling CUPS to start the printer starts it, then pauses it immediately, and the job stays in the queue. If the printer was paused when I printed the job, it starts the job, asks me where to save it, then pauses the job straight away. My real printer works fine still. I never printed a page, so can't tell if the PDF printer worked to start with and is just broken because I cancelled a job.

So I installed in Puppy 2.16.1 with the same CUPS dotpup, and printed a test page (colour worked). So it definitely worked here to start with. I then printed something, but pressed cancel when it asked me where to save it, like before. Now when I print something it goes through the thing preparing it for printing, adds it to the queue, doesn't ask me where to save it, and pauses the printer. Unlike in Grafpup, if I now tell CUPS to start the printer, it starts and then pauses straight away, but does not ask where to save it. So it is impossible to get to the stage where it asks me where to save it.
More disturbingly, I then installed my real printer in Puppy (an HP PSC1610), using the HPIJS PSC1600 driver, from the same CUPS dotpup that works in Grafpup104 and in Puppy 2.02, and it does not print. Jobs go to the queue, then leave there, but the printer doesn't do anything. I don't know if this is because of the pdf thing or not because I haven't used the printer with 2.16 before, but if it isn't then it is very sad, and indicates that having CUPS in 2.17 may not be quite as wonderful as we think... ---EDIT--- My HP works in a fresh installLast edited by disciple on Wed 18 Jul 2007, 02:26; edited 1 time in total

This package has been tested on successfully Puppy 2.17 alpha, Puppy 2.16 and Grafpup 2.00. Grafpup 1.04 requires that /usr/lib/cups/backend/pdf-writer be modifed as follows to fix the problem reported by disciple (which only occurs in Grafpup 1.04).

Wow - you are fast. That is very kind of you supporting such obsolete software, and presumably the problem would occur in all (or at least most) Puppy 1.xs
But I had the problem in Puppy 2.16.1 as well - do others not have the problem, or have you fixed it?

You are a legend jcoder:) I fixed the script and reran it in Grafpup 104, and now it works great. Thanks!!
Cups seemed to be permanently broken in Puppy 2.16.1, so I started with a fresh save file and installed the .pet and it works great. Thanks. This should definitely be in 2.17

Thoughts/Suggestions:
I have no idea how possible it would be to change, but I think it might be better for a print job to be deleted if you press cancel, than for it to stay in the queue and the printer to go off line. I think the current behaviour would be confusing to most users.
Also, it would be handy to have a printer option to turn off the feature to add a date to prevent overwriting a file - often people want to overwrite a file. I guess we could manually edit the script, but it would be handy to be able to turn it on or off.

This is curious. I have gtklp installed (both my systems), and I don't know if the problems are with CUPS, GTKLP, the PDF printer and/or Seamonkey/Firefox.
To change my paper size I have to change it it the CUPS web interface AND in GTKLP AND I have to restart cups, otherwise it will still print on the old size.
Printing from Firefox or Seamonkey I also have to specify the same size when I go to print it, otherwise it scales to the size specified by the browser, but puts it on the size paper specified by CUPS. How annoying. Why can't the browser dictate the paper size?

In case anybody else wants to print to pdf from CUPS from Puppy 1.x, run this and it should work ---EDIT---I can't quite figure out how to modify the script for version 0.2, so run it and then replace /usr/lib/cups/backend/pdf-writer with the attached file (make sure you unzip it)---

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum