Fatdog64-511

Message

Roy · #106 Post by **Roy** » Mon 28 Feb 2011, 18:56

Thank you, guys!

Jamesbond, yes... it is my sole local printer, connected via USB. Found the permissions stuff Menu > Cups manage printing > Administration tab > Manage Printers > left click on desired printer > under 'Administration' drop down menu, select 'Set Allowed Users' > enter 'root spot' (without ''). Now the default printing capability is -- at least functionally -- restored.

rcrsn51, that's the ticket! I had already gone to the link you provided, but was getting a geek CLI message that indicated a 32-bit library was not being accepted by the 64-bit system when trying the pixma-backend-qrky-1.0.21.pet. Might have just been a problem on my end, but installing your pixma-backend-fd64-1.0.21.pet solved my scanning issue with my Canon PIXMA MP460. Thank you!

-Roy

rcrsn51 · #107 Post by **rcrsn51** » Mon 28 Feb 2011, 19:01

Excellent.

Because this package also installs libusb1.0, it slightly modifies how other USB devices work. However, I have never had a problem with this in 32-bit systems like Quirky.

rcrsn51 · #108 Post by **rcrsn51** » Mon 28 Feb 2011, 19:45

Here is Peasyscan for FD64.

Please provide feedback.

rcrsn51 · #109 Post by **rcrsn51** » Mon 28 Feb 2011, 21:54

Here is the HP printer package for CUPS. These are just basic printer drivers - no scanners, firmware plugins or toolkits.

Please provide feedback.

rcrsn51 · #110 Post by **rcrsn51** » Mon 28 Feb 2011, 23:11

Here is the HP scanner driver package. It has been tested with a Deskjet F4280 in both Xsane and Peasyscan.

Please provide feedback.

Jim1911 · #111 Post by **Jim1911** » Mon 28 Feb 2011, 23:25

rcrsn51 wrote:Here is the HP scanner driver package. It has been tested with a Deskjet F4280 in both Xsane and Peasyscan.

Please provide feedback.

Thanks, works fine using Xsane with my HP C5280.

@jamesbond
I have prepared an sfs of the 64bit final version of LibreOffice-3.1.1_en-US that works fine,including printing, with Fatdog. If you like, PM me temporary upload info, and I'll upload it to your site. I've already uploaded the 32bit version to playdayz and it should be available for download with Quickpet in the new Lucid-5.2.

Cheers,
Jim

jamesbond · #112 Post by **jamesbond** » Tue 01 Mar 2011, 11:15

Thank you everyone!

Please give feedback to rcrsn51's pets - if they're ok, I'll put them to the repo.

Jim, I tried LibreOffice 3.1.1 before (when you announced to me), when it opened for the first time there was a window re-painting problem on its welcome screen. It doesn't affect functionality but it does give the impression that the application is "broken". Has this been fixed (=ie, doesn't happen in your system)? You can use the mydrive.ch account in page 7 of this thread, and upload it to "upload" folder. Let's hear some feedback on it and if it's ok, I'll publish that to the repo. Thanks for packaging

cheers!

rcrsn51 · #113 Post by **rcrsn51** » Tue 01 Mar 2011, 14:43

Here is the alternate Epson scanner driver required by some models. It has been tested with a WorkForce 320 in both Xsane and Peasyscan.

Please provide feedback.

rcrsn51 · #114 Post by **rcrsn51** » Tue 01 Mar 2011, 20:21

Here is the "official" Epson printer driver package. It supports a variety of models not handled by Gutenprint.

Please provide feedback.

Roy · #115 Post by **Roy** » Wed 02 Mar 2011, 02:30

Curiously, even though the extra library allowed Xsane to start and (preview) scan in FD64, I discovered that Xsane would not actually scan and save the image -- even with the new library added. Xsane merely reported that the operation was canceled.

HOWEVER, adding the peasyscan dot pet solves the issue by both scanning and successfully saving the image. Wish peasyscan would create .pdf's, but .jpgs will certainly do (and might be smaller).

Wondering if I can professionally manipulate and image to insert a hand-written signature and then use something like sam2p to convert from a jpg into a pdf..... But then, I wouldn't need to print or scan (as much) if I could do that.

-Roy

rcrsn51 · #116 Post by **rcrsn51** » Wed 02 Mar 2011, 03:04

Roy wrote: Wish peasyscan would create .pdf's

Peasyscan lets you save the image as a Postscript (PS) file. You can then convert it to a PDF with

Code: Select all

ps2pdf xxx.ps

jim3630 · #117 Post by **jim3630** » Wed 02 Mar 2011, 03:47

thanks rcrsn51 and others for the fd64 511 hp printer pets and others pets, my fd is obese by puppy standards. I've only "fixed" it once enough to break but was a good learning opportunity. Almost everything is working now...

Just can't quite figure out how to get my sound back in fd HDD install on new HP dual intel which do have sound on the other distros, have triple boot Snow Puppy and Knoppix on the HDD. I'm in the wrong section for the question but hoping it's a simple fix a seasoned fd user will have off the top. thanks again jim

rcrsn51 · #118 Post by **rcrsn51** » Wed 02 Mar 2011, 04:04

the fd64 511 hp printer pets

Could you be more specific? What printer model(s) did you test? Did you use both the printer and scanner drivers?

jim3630 · #119 Post by **jim3630** » Wed 02 Mar 2011, 04:44

rcrsn51 wrote:
the fd64 511 hp printer pets
Could you be more specific? What printer model(s) did you test? Did you use both the printer and scanner drivers?

My wife got both hpijs_print_fd64-3.11.1.pet and hplip_scan_fd64-3.11.1.pet for a hp6400. May have used both it's over my skill level.

Roy · #120 Post by **Roy** » Wed 02 Mar 2011, 05:41

jamesbond wrote:

Good report on Frisbee ... if we have good feedback, kirk will probably include that as the default

Frisbee works very well for me, although in some of the earlier versions a few testers were asking for a rollback to the traditional network manager... Haven't seen ANY complaints on the later versions, and I am content with a .pet -- as long as you ensure a valid .pet version is available! As for the broadcom wireless, that's what I have to use on my netbook, with the wl.ko driver and no ssb module loaded. Jemimah's done good work there, too.

rcrsn51 wrote:

save the image as a Postscript (PS) file. You can then convert it to a PDF

Thank you, rcrsn51. I really should remember things like that.... it's either the years or the miles under my belt that cause me to forget.

-Roy

Roy · #121 Post by **Roy** » Wed 02 Mar 2011, 06:29

Created a FRESH save file and loaded ONLY the skype.sfs... Still won't run from menu. Shows 'Segmentation fault' when attempted via CLI.

Downloaded fresh skype.sfs and replaced original. (Original worked with FD64-500) Still nothing from menu. 'Segmentation fault' from CLI.

rcrsn51 · #122 Post by **rcrsn51** » Wed 02 Mar 2011, 16:06

Here is the printer driver package for the foo2xxx collection. I have incorporated the firmware-hotplug components from Patriot's 32-bit version. To reduce the size of the package, I have removed all of the ICM colour files.

I don't own any of these printers, so if you test this package, PLEASE provide feedback.

[Edit] Attachment deleted. No feedback provided after 20 downloads.

gcmartin · #123 Post by **gcmartin** » Thu 03 Mar 2011, 07:06

rcrsn51 wrote:... To reduce the size of the package, I have removed all of the ICM colour files.

I don't own any of these printers, so if you test this package, PLEASE provide feedback.

@Rcrsn51. Please don't take this the wrong way as I mean no malice. But would you explain to me why you would remove the ICMs in a system which does NOT have memory issues? I know you mean well, but all 64bit PCs running FATDOG even on LiveDVDs do not suffer from the memory issues that you may be referring to

.
Which are you trying to address....FS storage on, say, LiveDVD or RAM used when printing?
Would including the ICMs have been a less risky assistance provided?

Thanks for helping understand.

rcrsn51 · #124 Post by **rcrsn51** » Thu 03 Mar 2011, 11:35

If I include the ICM's, the PET is too large to be attached here, so it must be hosted externally. If the package is not downloaded regularly, it will eventually disappear.

If and when someone provides some feedback on this driver and actually requests the ICM data, I will deal with the issue.

Would including the ICMs have been a less risky assistance provided?

I don't know what you mean.

gcmartin · #125 Post by **gcmartin** » Thu 03 Mar 2011, 17:53

rcrsn51 wrote:If I include the ICM's, the PET is too large to be attached here, so it must be hosted externally. If the package is not downloaded regularly, it will eventually disappear.

If and when someone provides some feedback on this driver and actually requests the ICM data, I will deal with the issue.
Would including the ICMs have been a less risky assistance provided?
I don't know what you mean.

Thanks for your help. I am just beginning to embark on a PET production journey and your explanation allows me to pay attention as I begin moving forward.

That question was to get your insight on the support risks.

That question you highlight put another way is asking this. If you are aware that you are producing something that MAY reduce/impact functionality for the sake of file size, is it worth the down-the-road user impact/support that must be expended for the sake of size? (Size is a relative thing and I realized that it means one thing in Puppy and a completely different thing in FATDOG where manufacturers ship a completely different machine than many Puppy users might have.).

Lastly, different topic
I understand that Printer/Copier manufacturers do NOT always make drivers (PPDs) available for their products in the LInux community, Another question: If I want to provide a PPD from a Manufacture like Lexmark or Canon who make PPDs, how should we present these to this FATDOG community so that instead of my benefiting, others can too?

Thanks in advance

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fatdog64-511

Why remove the ICMs?

Thanks: Helping me understand your approach. I wasn't aware