On my settup, jpg's in /usr/share/background corrupt right away, and don't load.prehistoric wrote:Getting backgrounds to work is not the problem, as you can see in that screen shot.jpeps wrote:No biggee...just convert the jpg's in /usr/share/background_original to png's in /usr/share/background. Bottom line...use png format for background. (although I think they worked in 005)
Puppy Stardust 006
Re: backgrounds
Has there been a change in the CUPS program. It is working perfectly on 005 but when I made a seperate installation of 006 (both hard disk installs on separate partitions) it goes through the motions including identifying the printer involved (HP5550 Deskjet) but will not print a test page. I rebooted to 005 and it works perfectly. Any thoughts?
Other than that I have been using 005 as my primary OS and am very satisfied with it ,staying true to Barrys original with useful mods seems to be the answer.
Regards Dennis .
Other than that I have been using 005 as my primary OS and am very satisfied with it ,staying true to Barrys original with useful mods seems to be the answer.
Regards Dennis .
I will remove /usr/sbin/background_reshape to avoid image cropping when changing wallpaper. This is a tool Barry introduced to keep format of wallpapers when stretching. It does only work for jpgs and for pictures in 4:3 format, and relies on some apps from the netpbm package which I of course want to get rid of .......... to be honest, I don't see the value of such a program on Stardust. The wallpapers in the iso are all stretchable, and when user chooses his/her own, it will be chosen because it fits screen.
dalderton mentioned that printing testpage works in 005. Good news. That means it is not a font, but a netpbm tool. probably some of them......I will find out.
Sigmund
dalderton mentioned that printing testpage works in 005. Good news. That means it is not a font, but a netpbm tool. probably some of them......I will find out.
Sigmund
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
Prints on Samsung ML-1710
Zigbert,
I almost reported an error when my Samsung ML-1710 did not print after I added a ppd file for it, then I remembered the bug. When I tried printing from Abiword, it worked fine. Curiously, the error message does mention a missing font. (See attached screen shot.)
I've attached the ppd file, so you can add it to your definitions. I think there are enough of these printers out there to make it worthwhile.
I almost reported an error when my Samsung ML-1710 did not print after I added a ppd file for it, then I remembered the bug. When I tried printing from Abiword, it worked fine. Curiously, the error message does mention a missing font. (See attached screen shot.)
I've attached the ppd file, so you can add it to your definitions. I think there are enough of these printers out there to make it worthwhile.
- Attachments
-
- Samsung-ML-1710-gdi.ppd.gz
- gzipped printer definition file for Samsung ML-1710
- (5.72 KiB) Downloaded 403 times
-
- printer_error.jpg
- Printer error shown by CUPS after attempting to print test page on ML-1710.
- (72.93 KiB) Downloaded 381 times
Sorry Guys, I forgot to mention, - The print-testpage-bug was also fixed yesterday.
I'm not sure about the ppd-files (because the lack of knowledge). How many of these files should we include to really improve the printer-driver situation? Then, how big would this pack be? And why hasn't this been done earlier?
Sigmund
I'm not sure about the ppd-files (because the lack of knowledge). How many of these files should we include to really improve the printer-driver situation? Then, how big would this pack be? And why hasn't this been done earlier?
Sigmund
Thanks but they say the same.
Concurrent download limit exceeded.
I failed to find your files there but tested pupitup iso and got same message as on Asia host
Hahahh Ttuxx told me to jsut hit F5 a few times and that worked. 5 minutes left to download now.
Concurrent download limit exceeded.
I failed to find your files there but tested pupitup iso and got same message as on Asia host
Hahahh Ttuxx told me to jsut hit F5 a few times and that worked. 5 minutes left to download now.
Last edited by nooby on Fri 29 Jan 2010, 09:02, edited 1 time in total.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
success, I write from a frugal install of Stardust now so success on my HP/Compaq Desktop computer. But Stardust could not get my Acer wired connection to work but it did wireless out of the box which is rather unique. Thanks for the pupradio thing. Very contagious.
Stardust maybe will be my preferred puppy from now on?
now that I have Stardust save file named stardust will it find that one or let me chose among many save files or does it load the first it find?
I did not write puppy pfix=ram but only pfix=ram so could the extra word there be a typo?
And if one do it from a USB maybe one should change from cd to usb?
Just me trying to get it right. No nitpicking.
Not to prehistoric
another work around that is much more easy is to just do F5 and that solve it.
Stardust maybe will be my preferred puppy from now on?
now that I have Stardust save file named stardust will it find that one or let me chose among many save files or does it load the first it find?
I did not write puppy pfix=ram but only pfix=ram so could the extra word there be a typo?
Should it really be puppy pfix=ram because IIRC usually it is just pfix=ram and not puppy in front of it?
BE AWARE!!!!
If you have Puppy installed, you MUST run this with the prefix 'puppy pfix=ram'. Else, the Stardust desktop will not install.
And if one do it from a USB maybe one should change from cd to usb?
Just me trying to get it right. No nitpicking.
Not to prehistoric
another work around that is much more easy is to just do F5 and that solve it.
Last edited by nooby on Fri 29 Jan 2010, 18:18, edited 1 time in total.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
Stardust 005 => Stardust 006 xdelta available
Hi nooby,
If you read the post by 01micko following Zigbert's original post, you will find there is an xdelta to convert Stardust 005 to Stardust 006. If you have 005, this may get around the "concurrent download limit exceeded" problem, and cut download time as well. All the 431 puplets should have xdelta.
Zigbert,
If we were talking about the megabytes used by Windoze drivers, there would be an issue in including printer ppd files. The file above is only 28k unzipped. If you don't feel like putting all these definitions in the distribution, I'd recommend a separate pet of printer definitions. People with specific printers could install the pet, check out the printers they need, copy those ppd files to a safe place, then uninstall the pet. After that, they would only have to copy the ppd files from the safe place to /usr/share/cups/model. This would result in zero wasted space for unused printer definitions, and it would cut the frustration of finding, downloading and trying things that, for some unknown reason, don't work in Puppy.
Above, I was reporting a successful test under Stardust 006, so we know the Samsung ML-1710, like the Brother HL-2040, is supported. If you give me any encouragement, I'll check on a few other systems around, and see what printers other people are actually using. After I've tested that these work under Stardust, I'll post the ppd file I used.
Regards,
prehistoric
If you read the post by 01micko following Zigbert's original post, you will find there is an xdelta to convert Stardust 005 to Stardust 006. If you have 005, this may get around the "concurrent download limit exceeded" problem, and cut download time as well. All the 431 puplets should have xdelta.
Zigbert,
If we were talking about the megabytes used by Windoze drivers, there would be an issue in including printer ppd files. The file above is only 28k unzipped. If you don't feel like putting all these definitions in the distribution, I'd recommend a separate pet of printer definitions. People with specific printers could install the pet, check out the printers they need, copy those ppd files to a safe place, then uninstall the pet. After that, they would only have to copy the ppd files from the safe place to /usr/share/cups/model. This would result in zero wasted space for unused printer definitions, and it would cut the frustration of finding, downloading and trying things that, for some unknown reason, don't work in Puppy.
Above, I was reporting a successful test under Stardust 006, so we know the Samsung ML-1710, like the Brother HL-2040, is supported. If you give me any encouragement, I'll check on a few other systems around, and see what printers other people are actually using. After I've tested that these work under Stardust, I'll post the ppd file I used.
Regards,
prehistoric
prehistoric
I think it is a great idea to collect external ppd-files into a pet. It could either be included into the iso, or we could provide a download link in the the html-page (/usr/sbin/cups_shell). - Depending on size and usage.
I don't know much about printing (except I want it to work ). Please help me and other puppians.
Sigmund
I think it is a great idea to collect external ppd-files into a pet. It could either be included into the iso, or we could provide a download link in the the html-page (/usr/sbin/cups_shell). - Depending on size and usage.
I don't know much about printing (except I want it to work ). Please help me and other puppians.
Sigmund
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
printer pet
Zigbert,
I'll start a thread for the pet tomorrow, after I've tried out 006 on a few more machines, (so I'll know what problems people are likely to encounter before I write the instructions.) My idea is to collect ppd files, or equivalents, for every printer someone reports working with a specific unmodified pupplet, starting with Stardust. When someone reports a problem, that goes into a different thread on printing.
Naturally, I can think of something for you to do. This is simple, (I hope.) When a printer is added to a system, the description file should be copied from /usr/share/cups/model to a location where it will not be removed when the pet is uninstalled. After the pet is uninstalled, there should be an option to restore the descriptions of working printers on the system to /usr/share/cups/model. This will give people working printing with minimum overhead.
This same technique could be used for font packages. As you know, these can take a lot of space. Once you have things set up as you like, you can uninstall the pet, and only keep the additional ones you have actually used, plus a number required for system functions.
For people with more space than they know what to do with, there is no particular reason to uninstall. For machines where space is tight, this makes it easy to get things working and down to minimum requirements.
What do you think?
prehistoric
I'll start a thread for the pet tomorrow, after I've tried out 006 on a few more machines, (so I'll know what problems people are likely to encounter before I write the instructions.) My idea is to collect ppd files, or equivalents, for every printer someone reports working with a specific unmodified pupplet, starting with Stardust. When someone reports a problem, that goes into a different thread on printing.
Naturally, I can think of something for you to do. This is simple, (I hope.) When a printer is added to a system, the description file should be copied from /usr/share/cups/model to a location where it will not be removed when the pet is uninstalled. After the pet is uninstalled, there should be an option to restore the descriptions of working printers on the system to /usr/share/cups/model. This will give people working printing with minimum overhead.
This same technique could be used for font packages. As you know, these can take a lot of space. Once you have things set up as you like, you can uninstall the pet, and only keep the additional ones you have actually used, plus a number required for system functions.
For people with more space than they know what to do with, there is no particular reason to uninstall. For machines where space is tight, this makes it easy to get things working and down to minimum requirements.
What do you think?
prehistoric
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
ppd files
That's 5 KB gzipped, when unpacked in /usr/share/cups/model it takes 28 KB of RAM. Losing 2-3 MB of RAM would be significant, if all the definitions stay there all the time. The ppd files aren't the biggest problem. There are some printers that just don't follow that model, and require larger drivers of their own.zigbert wrote:prehistoric
What model to be used for installation depends on the result you get. Your ppd is 5kb, which gives us 100 printerdrivers in 0.5 megabytes. - Sounds not bad.
Sigmund
I've done a few more tests. An HP Laserjet 1320 worked "out of the box" with the definition already available, (once I found the correct entry.) An HP Photosmart 8250 I encountered probably matches requirements for the 8200, which is said to work perfectly with the HPLIP package from HP. I don't have experience with this, but will check. Several manufacturers have similar "universal" Linux driver packages available which take megabytes.
We have decisions to make about where to cut-off built-in support and provide a separate custom pet. Even if much better drivers exist, I would like to include working ppd files in the basic printer support package. There are probably only half a dozen manufacturers furnishing distinct large "unified" driver packages worth having. One problem is that the resulting printers are sold under different labels, so consumers are not aware of who actually built the device.
As jpeps' link shows, most printers usable under Linux are in the Open Printing database. Yesterday, I found a ppd file there for a Samsung ML-1740 about which we had a question. This looked very similar to the file for my ML-1710. I'm hoping to hear back about a success.
I also dug out an ancient Canon BJC-210 I have, and found a ppd file for it. (Unfortunately, while the device appeared ready to work, the ink had fossilized.)
I'll try several other printers today, at friends' houses. At present, I'm testing all of these under Stardust 006, using the test page in Abiword instead of the CUPS test page. When 007 comes out, I won't have to warn people about this, will I?
Added: Just so people will not think I'm trying to take credit for someone else's work, here's the link to Patriot's CUPS topic I've been using. What I'm trying to do is merely to confirm that things now work under Stardust.
I can now confirm that the splix-2.00 pet works with my Samsung ML-1710 and another ML-1740. Splix is 58 KB., versus 5 KB for the ppd file for the ML-1710, but after I count the number of ppd files it can replace, with full functionality, I've decided splix-2.00 makes more sense. I have the HPLIP lite pet, and will test that on that HP Photosmart 8250 when I next have access to the printer.
One problem is that even the lite version of HPLIP is 3.8 MB, and some printers require additional plug-ins. HPLIP makes more sense as a separate package than as built-in support.