As of this release we are around 500kb over our 100MB limit,
If I use 100% the latest ghostscript we will be around another additional 4MB over, Where in the world can we find 4.5MB to remove? I'm only using 2 files from the older version and like 200 from the latest, sure it will register as the previous version, but the rest is updated.Well maybe not the newer way of processing svg files, But to have a full function cups package in puppy working out the box hasn't been done before, Gutenprint was always a repo item I think. So this CUPS package is taking a lot of extra space the way it sits.
ttuuxxx_________________http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games

Intel(R) PRO/Wireless 2915ABG Net is not being recognized on this IBM Thinkpad R52... Pre 4.2 it is recognized. ....

Glad to hear its working for you also
It looks like Canon usb is working great now, Now its just to get the hp working right.
I'll see what I can do, but since I don't have a HP printer and just canon, it makes this task very difficult at most.
Would be easier if people with linux know how, try to get the hp printers working with this package, It would save a lot of time and effort.

So, please, tell the world, and WhoDo,
the truth about which Ghostscript is Really going to be in
Puppy Linux 4.2. Ok?

Thank you,
Eddie Maddox
Inwood IA USA

Well I've stated it like 5 times, at least on here, plus when I made the package I did say that also. I was not 'lying' I just forgot when you asked me, I've been working on this project a min of 15hr a day, since it started, and trying my hardest to get it working and running, and like I said before I don't even print with Linux, I'm doing this solely for everybody else's benefits, I have nothing to gain if CUPS works or not. Its still well over 90% the latest release, whatever really, try to help out the people doing all the work instead of making the work harder and unhappier, I am not a lier . Plus I don't think it even mentions Which ghostscript is being used, only the cups version and thats 100% new and the same with GutenPrint, and Foomatic.
ttuuxxx
ttuuxxx_________________http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games

This is really dismaying, in contrast to CUPS 1.1.23 on Puppy 4.1.1 which works perfectly. But there are several weeks left until Easter. Remedies, anyone?_________________It's stupid to use inferior software for ideological reasons.
--Linus Torvalds

This is really dismaying, in contrast to CUPS 1.1.23 on Puppy 4.1.1 which works perfectly. But there are several weeks left until Easter. Remedies, anyone?

Come on lets not all get disappointed, it works perfect for me and others as stated, bringing up older cups models that didn't work for others doesn't help, finding out why your permissions isn't working when it works out of the box for others would be helpful.
your linux savvy, So lend a hand please. right now Cups is working around 50% of the peoples printers thats up 50% from the last release, I call that a hell of a improvement! is your printer usb??

ttuuxxx"Printing works on Canon pixma 5200"
NathanO "Printing works on USB on HP zv6100. "
Minnesota "Congratulation Canon printer 4300 up and running out of the box!! "

finding out why your permissions isn't working when it works out of the box for others would be helpful.

Something changes the permissions. As I said in the Beta2 thread, the /dev/lp0 connection starts out with "777" (execute) permissions, like /dev/lp1. After I try to print, /dev/lp0 shows "660" (no execute) permissions, unlike /dev/lp1.

And when do the permissions get messed up? Looking at them each step of the way, I find that it's right when the CUPS window opens up, before I've done anything about adding a printer. After that happens, if I change them back to 777, they stay that way.

And so the solution is . . . either (1) find and fix the bug that makes CUPS (sometimes) change the permissions when it opens up, or (2) add in a bit of code to determine whether the permissions on the connected device are OK after that point, and to change them if they're not. Right?

Somebody who knows a lot more about CUPS than I do will have to provide the solution, which presumably isn't to tell every user "If you can't print, just try manually changing the permissions on /dev/lp0, or whatever device file stands for your printer connection." (Huh?) Me, I can now proceed to hunt for comparatively little bugs to report in this RC, because . . . with just a bit of non-obvious manual tweaking . . .

Printing Works !!!

And here's the first comparatively little bug I've found: when I closed the ROX-Filer window in which I was examining the permissions of /dev/lp0, I found that the Pwidgets clock now had a picturesque but incongruous background consisting of hard-disk icons and device names from ROX-Filer!_________________It's stupid to use inferior software for ideological reasons.
--Linus Torvalds

finding out why your permissions isn't working when it works out of the box for others would be helpful.

Something changes the permissions. As I said in the Beta2 thread, the /dev/lp0 connection starts out with "777" (execute) permissions, like /dev/lp1. After I try to print, /dev/lp0 shows "660" (no execute) permissions, unlike /dev/lp1.

And when do the permissions get messed up? Looking at them each step of the way, I find that it's right when the CUPS window opens up, before I've done anything about adding a printer. After that happens, if I change them back to 777, they stay that way.

And so the solution is . . . either (1) find and fix the bug that makes CUPS (sometimes) change the permissions when it opens up, or (2) add in a bit of code to determine whether the permissions on the connected device are OK after that point, and to change them if they're not. Right?

Somebody who knows a lot more about CUPS than I do will have to provide the solution, which presumably isn't to tell every user "If you can't print, just try manually changing the permissions on /dev/lp0, or whatever device file stands for your printer connection." (Huh?) Me, I can now proceed to hunt for comparatively little bugs to report in this RC, because . . . with just a bit of non-obvious manual tweaking . . .

Printing Works !!!

And here's the first comparatively little bug I've found: when I closed the ROX-Filer window in which I was examining the permissions of /dev/lp0, I found that the Pwidgets clock now had a picturesque but incongruous background consisting of hard-disk icons and device names from ROX-Filer!

<snip>… I found that the Pwidgets clock now had a picturesque but incongruous background consisting of hard-disk icons and device names from ROX-Filer!

At least it wasn't the red banjos on a green ..
That may be a new fixwidgets feature .. why I took show_widgets out of the /root/Startup (which likes to make a fixwidgets which if it works as previous pulls a fixPuppyPin which ..)

just spitballin' .. ah, the dialup dl is finally almost finito after a rough start this ayem .. and real pwidgets experts should be 'round shortly to fix that clock .. and its bg

Hi I'm on the ##cups of freenode, I was wondering if you could come on to the chat channel and talk with cups's support, The users name is vimpulse he needs to talk to you about cups, Hes very helpful and could probably work this out for us.
If you can open xchat, then get the room list, click the top of the list where the names are, that will sort the list from a-z, scroll down to ##CUPS and click on that.
Thanks
ttuuxxx_________________http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games

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