[hpoj-devel] (no subject)

[<jj...@ya...>]

Hi,  
  
I'm new in Linux - just a month or so of experience. I've just  
ended installing the hpoj software, and I want to share with you  
some problems I've found during the installation and how I've  
overcome them.  
  
First of all, I use SUSE Linux 9.0 with the following kernel: Linux  
linux 2.4.21-215-default #1 Tue Apr 27 01:00:43 UTC 2004 i686  
i686 i386 GNU/Linux  
My printer is a HP PSC 1110 all-in-one.  
I downloaded the package to compile it from source, since the  
ones available for Suse 9.0 were not compiled for libusb support.  
I succeeded in compiling - the standard compilation - the hpoj  
software but I found the following bug: at the end of the proccess -  
don't remember now whether it was in the 'make install' or before,  
the compilation succeeded in creating the appropiate scripts for  
'ptal-init' in all runlevels except in runlevel2 (/etc/init.d/rc2.d). I did  
this manually following the instructions you provide in the  
documentation pages. Since the compilation had created init  
scripts with the form 'S01ptal-init' in the other runlevels (3 and 5), I  
assigned the same S and K numbers to the scripts that I created in  
runlevel2 (S01ptal-init).  
Then I rebooted the system, and checked whether HP-OfficeJet got  
started before CUPS. With this, there was no problem. But at the  
end of the proccess, ptal-mlcd produced the following error:   
May 24 20:57:18 linux ptal-mlcd: ERROR at ExMgr.cpp:4063,  
dev=3D<mlc:usb:psc_1100_series@/dev/usb/lp0>, pid=3D743, e=3D20,  
t=3D1085425038         libusbFindDevice: Couldn't find device!  
  
As  expected, when I try to communicate with the printer, using the  
'ptal-print </dev/null' command, the program gave back "failed"  
message. But, the somehow stunning thing was that if I 'ptal-init  
setup' again, the comunication with the printer was made, and I  
could use all the printer facilities.  
  
After some thinking and trying various changes that didn't do  
anything I found out what was the problem: compilation had  
charged the scripts files too early, so the libusb modules weren't  
still charged. I corrected this for all the runlevels (2,3 and 5) and  
restarted the system. And everything is working!!!  
  
The rest of the process was very easy: I used cups to setup the  
print queue, and followed your instructions for sane. No problems  
there.  
  
I've post you this message because I don't know why the  
compilation process assigned a '01' start script to ptal-init.  
(S01ptal-init). I use the standard compilation, that is, no special  
characteristics. If this is done automatically, I understand that is  
done this way intentionally to get 'ptal-init' started before CUPS.  
But, it would be useful to correct this numbers, so that 'ptal-init'  
started just before CUPS.  
  
I hope this would be useful to other users.  
Thanks a lot.  
Jos=E9 Juan Gonz=E1lez  
jj...@ya...  
  
P.D: sorry for my english. I am spanish: if I can help translating  
your page or documentation, just tell...