Re: [hpoj-devel] HPOJ 4110 disappears!

[Cory M. <cor...@hp...>]

Which port did you choose when configuring via the CUPS web interface?
Can you send me the errors_log?

Cory

On Fri, 2004-07-23 at 02:42, Tom Walsh wrote:
> Cory Meisch wrote:
> 
> >I need some more info. and there are a couple things you can do. 
> >
> >in /etc/cups/cupsd.conf change the loglevel to debug2
> >check the /var/log/cupsd/error_log for any errors
> >
> >upgrade hpoj to 0.91
> >
> >What versions of ghostscript and CUPS are you running?
> >
> >Can you try creating the print queue outside of Printerdrake but using
> >http://localhost:631 instead?
> >  
> >
> Ok, downloaded a PPD driver and get that working.  Configured the 
> printer via CUPS, still nothing, plays dead.
> 
> TomW
> 
> >Run any other system updates... What kernel version are you running?
> >
> >Cory
> >hp linux printing team
> >
> >
> >On Thu, 2004-07-22 at 12:13, Tom Walsh wrote: 
> >  
> >
> >>Hello,
> >>
> >>This is frustrating!
> >>
> >>I am using Mandrake 9.2 with HPOJ v0.90 and CUPS v1.1.9, these were 
> >>installed from the stock Mandrake distro.  I installed the system with 
> >>the HPOJ 4110 connected, via usb cable, and was very pleased to find 
> >>that Mandrake found the HPOJ.  All functions appeared to work correctly: 
> >>scanning and printing.  After a few days of configuring the system, I 
> >>deployed it to the customer location.  This is when the problem showed 
> >>up, in actual use the printer will print for a while and then 
> >>myteriously die!  'lpq' reports that 'Printer is not ready'.
> >>
> >>Ok, a little research into the HPOJ docs and it says  that the 
> >>ptal-printd should not be used with cups and to disable it in 
> >>/etc/ptal/mlc:usb:officejet_4100_series by setting init.printd.start=0.  
> >>This seemed to have worked, for a few more days before it died again.
> >>
> >>I am at a loss, the only way it seems to get this printer to work is to 
> >>run the Mandrake "Configure your computer | Hardware | Printers", delete 
> >>the printer, then add it again.  Once I do that, it works fine, for a 
> >>few hours or a few days.
> >>
> >>How can I diagnose the problem, or fix this?  The customer and end-users 
> >>are getting very annoyed, so am I!
> >>
> >>Regards,
> >>
> >>TomW
> >>
> >>    
> >>
>