hpoj-devel — HPOJ development/support list

Re: [hpoj-devel] A hack For those of you with external zip drives

[<pa...@rc...>]

Sammy Redshaw wrote:
> For those of you linuxers with zip drive if you are running linux
> mandrake or red hat and only have one parallel port to share your zip
> drive and printer with use this quick hack to run both devices on the
> same port
Hi, Sammy.  Thanks for providing this tip.  Are you plugging the printer into
the pass-through port on the Zip drive or plugging one device into your PC at
a time?  I have often heard that one could have problems when connecting a
printer to a switchbox, Zip drive, or other pass-through device, particularly
when using advanced protocols such as ECP, because the signals or timing might
not always get passed through correctly, confusing the PC and/or the printer.
Perhaps newer Zip drives are better about this.  If it works for you, then
all the more power to you, but if you ever have problems, then it would be a
good idea to try it with the printer connected directly to the PC in case
that was what was causing the problem.

> goto /etc/rc.d/rc.sysinit and write the following lines in
> after it loads the sound modules or it won't work
> 
> #load parallel port
> /sbin/modprobe parport
> /sbin/modprobe parport_pc
> /sbin/modprobe parport_probe
> 
> #load zip drive
> /sbin/modprobe imm (this for zip250 use the one applicable to zip 100)
> 
> #load printer
> insmod  /usr/local/bin/ieee12844.o
> insmod /usr/local/bin/ieee12844pp.o
I would also be concerned about having two drivers loaded at the same time
that try to use the parallel port, particularly if you're scanning an image
and saving it to your Zip drive.  But again, if this works for you, then
great.

Another thing to note here is that if you're loading parport_probe and
ieee12844pp.o at boot time, then you need to make sure your printer is
connected and powered on at boot time, or you will have to unload and
reload these drivers later so they will properly detect the printer.

David

Re: [hpoj-devel] wrapfilter

[<pa...@rc...>]

re...@ca... said:
> Can you lot have another look at the wrap filter this is the what did
> i opened up the  filter script wrote what was in the print how to
> readme then deleted all the other bits of script in the file then
> saved it as wrapfilter but it still doesn't want to work
Hi, Sammy.  Your new wrapfilter script looks fine.  I double-checked the path
you specified for QUEUEDIR to make sure it was consistent with the "sd="
(spool directory) specified in /etc/printcap, and it is.  The only other
thing I can think of offhand is to make sure the wrapfilter script has
execute permission, because I made that mistake when I was setting up my
print queues the other day.  Say "ls -l /var/spool/lpd/lp", and you should
see something like the following:
-rwxr-xr-x    1 root     root         9479 Nov 29 21:29 filter
-rwxr-xr-x    1 root     root          190 Nov 29 21:29 general.cfg
-rw-r--r--    1 root     root            4 Dec  2 12:54 lock
-rwxr-xr-x    1 root     root          360 Nov 29 21:29 postscript.cfg
-rw-rw-r--    1 root     root           32 Nov 29 21:32 status
-rwxr-xr-x    1 root     root          148 Nov 29 21:29 textonly.cfg
-rwxrwxr-x    1 root     root          132 Nov 29 01:21 wrapfilter

The important thing is that you should see "x"s for filter and wrapfilter.
If not, then issue the command "chmod +x /var/spool/lpd/lp/wrapfilter".

> when i go to
> where the file resides /usr/local/bin and run ieee12844_print from the
> command line nothing happens or in a winblows term it locks. I
> wondering if it the actual ieee12844_print file that stopping the wrap
> filter from working? so i sending both of them to you lot to have a
> look at 
This isn't a bug.  ieee12844_print takes the print job data from standard
input, which is the keyboard when invoked at the command line without any
I/O redirection.  Try typing a line or two of text, then press control-D
(which indicates end of file).  It should exit, and the text should print,
although it may be stair-stepped.

> Just informing you lot that i have now got the the scanner working on
> my hp 1150c using the patch in the CVS repository
I'm glad it works for you now.

> it a bit slow bit it earlys days.
> i am wondering when scanning in colour should it stop
> start and then move one step forward just wondering?
What resolution (i.e. dots per inch) are you scanning at?  The higher the
resolution, the more data that needs to be transferred.  Also, color scans
have 24 times as much data as lineart, and 3 times as much data as greyscale.
When there's a lot of data to be transferred, sometimes the I/O becomes the
bottleneck, and the scanner has to stop and wait for buffered data (which it
has already scanned) to be transferred before it can scan any more.  If it's
too slow for you, then try scanning at a lower resolution.  Definitely don't
scan at the maximum resolution (I forget what that is for the 1150).

> Umm in previsour
> which you havent answered yet i still have problem getting it to print
> with ieee12844_print could some one send me a copy of their wrap
> filter for the 1150c please? 
Sorry about the delay in getting back to you.  As I said above, it looks OK.
In addition to double-checking that wrapfilter has execute permission, it
also might be a good idea to change the "Printer Device" (i.e. port) from
/dev/lp0 to /dev/null, and to make sure the "lp" kernel module isn't loaded.
Type "lsmod" to find out, and type "rmmod lp" if it is loaded.  These two
steps will eliminate the possibility that lp (the Linux standard parallel
port driver) is interfering with the hpoj parallel port driver.

I hope this helps.  If it's still not working even after trying these things,
it would help me help you if you could give more details about exactly what
is going wrong.  For example, exactly what happens when you print something,
either via "lpr" or by sending an ASCII or PostScript test page from
printtool?  Do you see any error messages at all?  Does lpd send you an
error message warning you that the document failed to print (which is what
happened to me when I had forgotten about execute permission for wrapfilter)?
When you run "lpq", does it show any pending jobs?  Are there any spool files
sitting around in /var/spool/lpd/lp (the filenames would probably start with
"df" or "cf")?

David

Re: [hpoj-devel] hpoj documentation offered - Comments Please

[<pa...@rc...>]

joe...@sn... said:
> Now is your chance to help. David has asked for an update to one of my
>  previous posts, which he says he would like to put in the next
> release, which  will probably occur soon. I've attached the article
> below. Please read and  post any comments or corrections you may have.
> Thanks in advance. 

Hi, Joe.  Thanks for sending this out.  It looks good, and I added some
additional information based on some previous advice I gave out on the list
(such as use with JetDirect), and based on my own experiences.  (For some
reason, I didn't actually get around to trying this out for myself until
a few days ago!)  I haven't yet tried to play around with gamma adjustment,
though, but it seems fairly straightforward.

Let me know if you or anybody else has comments about this document and/or
my attached changes.  If nobody raises any objections then I will replace
PRINT-HOWTO with this document in CVS in the near future.

David

Re: [hpoj-devel] xojpanel

[Joe P. <joe...@sn...>]

On Saturday 02 December 2000 04:40, David Paschal wrote:

> > Hi, Joe.
>
> joe...@sn... said:
> > There is another problem with either xojpanel or the low-level code.
> > Sometimes xojpanel fails to start on the first try. This message is
> > displayed  at the command line:
> >
> > "Error 0 (system error 100) in file mlccon.c, line 280: Unexpected
> > error,  please post a bug report to hpo...@bs..."
>
> I will fix that e-mail address.
>
> > If I try to start it a second time, xojpanel usually starts and runs
> > with no  problems that I can see.
>
> I'm not sure what the problem here is, but the problem must be in the
> low-level driver code.  Do you see any error messages in syslog
> (/var/log/messages)?  You could also try using the "debug=1" parameter when
> loading ieee12844pp.o, and maybe from that I can tell where it's going
> wrong. Could you elaborate on the circumstances in which this happens?  For
> example, does it only happen the first time after you load the drivers, or
> does it happen after you power-cycle the peripheral, etc.?

Lately the line number reported in the error message has been 263, but that 
doesn't matter very much now. I'm reasonably certain I found what was causing 
the problem. In /var/log/messages the OfficeJet is reported as being on an 
EPP port rather than an ECP, which I thought it was. After I removed the 
ieee12844pp module and reinserted it with the usenibble=1 option, xojpanel 
starts every time. I wrote a shell script that would repeatedly start and 
then kill xojpanel 6 seconds later. It's been through 1000 startups so far 
without any failures. Previously, one try in 15 starts would fail (rough 
average).

I'll see what happens after I change the port type to ECP on the IO card the 
OfficeJet is connected to. 
 

> Attached is a patch containing some changes I made.  The second change adds
> an explanation if xojpanel dies because the peripheral doesn't support LCD
> readback.  The first change changes the poll rate from once to four times
> per second, which greatly improved the response when I was scrolling
> through menus really fast.  However, it's probably not worth actually
> putting in, because I expect most people wouldn't need this level of
> responsiveness given the extra overhead it introduces, and IIRC you
> previously indicated some reason (debugging?) why you didn't want it to
> poll more than once per second anyway.
>

The patch installed ok, but it gave two error messages:
patch unexpectedly ends in middle of line
patch unexpectedly ends in middle of line

xojpanel compiles runs fine with the patch.

Early in development, the printer poll timer controlled scroll speed as well, 
so to cut down on unnecessary console output during testing, I set it as high 
as 3000ms (if I remember correctly). Now that the timers are separate, that 
reason is gone. The poll timer can be set lower than 1000ms. Are there any 
network delay issues to consider in setting the timer? For instance, if an 
lcd message is changing in the printer, but it's being polled too often, the 
wrong message might get to xojpanel first. Could this happen?

Overhead doesn't seem to be a big problem with xojpanel. It seems to use a 
lot of memory, but little processor time. top -p says that most of the time 
its CPU usage is 0.0%. The timer is set at 500ms for now, though.


> I'm glad you added the license statement at the top of the files, but you
> might want to add a copyright message, similar to what I did in the ptal
> and ieee12844 directories.  If you do this then it would be proper to also
> include a copyright for the original author, which I think was Andreas
> Fester.  (Is this correct, Andreas?  And what copyright year should be
> given for you?)

I'll put a copyright notice in, with credit for anyone who contributed to the 
remaining parts of the original xojpanel, if the contributors can be 
identified. If not, I'll give generic credit. It might be important to know 
the origin of the name 'xojpanel'. Andreas' response should be helpful. 

>
> When should I start putting this into CVS?  Once I do, then it would be
> preferable for additional changes to be made available as patches to
> hpoj-devel, even if you continue to provide a downloadable package on your
> website.
>
> Am I correct in assuming that the only file I should remove from CVS is
> lcd.bmp?  For the new files you provide, should I include
> CHANGES-xojpanel_jsp (possibly renamed to just "CHANGES")?  It might be
> easier to let the CVS checkin comments serve as the changelog.  What about
> xojpanel.kdelnk (maybe?) and .directory (probably not)?
>
> David

Hopefully, the copyright issue will be solved soon, so waiting a day or so 
before committing the new xojpanel code to CVS will probably make one patch 
unnecessary. 

Handle the changelog whichever way you think is best.

You won't need .directory for anything. I probably should have deleted that. 
lcd.bmp is no longer used or even very usable, due to a size difference. You 
can leave both of them out.

A KDE user could copy xojpanel.kdelnk to his/her desktop for a quick way to 
start the app. Many users may prefer to create their own launchers, but some 
don't know how, or don't want to go to the trouble. The addition of a GNOME 
launcher might be nice later on. I have only an older version of GNOME and 
haven't used it in a while, so I wasn't that interested in making one right 
away.


-- 
Joe

Re: [hpoj-devel] xojpanel

[<pa...@rc...>]

Hi, Joe.

joe...@sn... said:
> There is another problem with either xojpanel or the low-level code.
> Sometimes xojpanel fails to start on the first try. This message is
> displayed  at the command line:
>
> "Error 0 (system error 100) in file mlccon.c, line 280: Unexpected
> error,  please post a bug report to hpo...@bs..."
I will fix that e-mail address.

> If I try to start it a second time, xojpanel usually starts and runs
> with no  problems that I can see.
I'm not sure what the problem here is, but the problem must be in the
low-level driver code.  Do you see any error messages in syslog
(/var/log/messages)?  You could also try using the "debug=1" parameter when
loading ieee12844pp.o, and maybe from that I can tell where it's going wrong.
Could you elaborate on the circumstances in which this happens?  For example,
does it only happen the first time after you load the drivers, or does it
happen after you power-cycle the peripheral, etc.?

> I also made it possible to load the pixmaps from a user-specified
> directory  chosen at build-time. I took most of your advice on
> creating a single pixmap  loading function.  It will be necessary for
> the pixmap path and its enclosing  quotes to be inserted in place of
>
> XOJPANEL_DEFAULT_PIXMAP_PATH 
>
> I hope what I did works correctly. It will correctly handle whatever
> path is  #defined in ojstatus.cpp, but I haven't tested it when
> controlling from  ./configure.
Super.  It looked fine to me.  I will hack this into the configure/build
sequence when I commit it to CVS.

> I removed most of the references to unicode and replaced #define
> UNICODE_SUPPORT with #define USE_QCHAR. 
OK.

> Do my recent changes to the pixmap loading code work correctly? Does
> it still segfault? 
I played with it a lot last night, and I'm no longer seeing the various
segfaults I previously reported.  Thanks for fixing that.

Attached is a patch containing some changes I made.  The second change adds
an explanation if xojpanel dies because the peripheral doesn't support LCD
readback.  The first change changes the poll rate from once to four times
per second, which greatly improved the response when I was scrolling through
menus really fast.  However, it's probably not worth actually putting in,
because I expect most people wouldn't need this level of responsiveness
given the extra overhead it introduces, and IIRC you previously indicated
some reason (debugging?) why you didn't want it to poll more than once per
second anyway.

I'm glad you added the license statement at the top of the files, but you
might want to add a copyright message, similar to what I did in the ptal
and ieee12844 directories.  If you do this then it would be proper to also
include a copyright for the original author, which I think was Andreas
Fester.  (Is this correct, Andreas?  And what copyright year should be
given for you?)

When should I start putting this into CVS?  Once I do, then it would be
preferable for additional changes to be made available as patches to
hpoj-devel, even if you continue to provide a downloadable package on your
website.

Am I correct in assuming that the only file I should remove from CVS is
lcd.bmp?  For the new files you provide, should I include
CHANGES-xojpanel_jsp (possibly renamed to just "CHANGES")?  It might be
easier to let the CVS checkin comments serve as the changelog.  What about
xojpanel.kdelnk (maybe?) and .directory (probably not)?

David

RE: [hpoj-devel] SMP patches?

[Robert G. B. <rg...@ph...>]

On Wed, 29 Nov 2000, PASCHAL,DAVID (HP-Roseville,ex1) wrote:

> > I have a bit of kernel module and smp expertise myself (at
> > least enough
> > to know what a "bottom half handler" is:-) and can possibly even help
> > intelligently in the event that the patch doesn't fix my problem(s).
> All input is welcome.  :-)  If nothing else perhaps you can review the
> changes to ieee12844pp.c and ieee12844.c (particularly the functions
> mlc_sendmsg and mlc_recvmsg in the latter file) and let us know if you see
> any problems.

When I looked I realized that I had actually downloaded and installed
the SMP patch when I first grabbed the software; I just didn't recognize
it from the description.  So it was installed all along.

So I was (and still am) getting the following message from the
mlcpp_transmit() routine even with the patched driver:

Dec  1 18:23:30 lucifer kernel: mlcpp0: mlcpp_transmit while TX busy

This invariably causes the image I'm printing to scramble at that point
and the printer starts trying to print the incoming message as if it is
a binary/ascii data stream (that is, it rips through paper putting all
those funny little ascii block characters).

I still suspect an SMP problem but I'm not certain.  It could either be
that having two processors allows a second transmit interrupt to occur
before the line is fully clean from the first -- not necessarily a
proper spinlock failure but a mix of spinlock failure and handshaking
failure.  Or something.  It could also just be some sort of flow control
failure all by itself -- with megabyte sized images, the printer may be
trying to say "enough" while it processes what it's got but the flow
stop may not be getting through.

Over the weekend I'll try a couple of things:

  a) To make sure that the problem is really likely the SMP box, I'll
run the printer from an almost identical (but UP) box next door.  If
this works I could, of course, just leave things that way but I'd rather
help debug the SMP problem.

  b) If the problem occurs on the SMP box but not the UP box, I'll try
to run the modules with a higher debug mode.  I assume that this traces
the operation fairly tightly.  I have lots of cheap paper and although
the cartridges aren't cheap, I'm willing to burn at least one set
getting the thing to work.

Any helpful suggestions beyond that would be appreciated, especially
from folks who already know why the transmit while TX busy message might
be occurring.  I did already note the new requirement that the printer
port be configured EPC (mine was SPP in the bios) and reset it but it
made no difference.  I'm guessing that was more for scanner function
anyway.  This seems like an overrun failure of the plain old printer
device.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rg...@ph...

[hpoj-devel] hpoj documentation offered - Comments Please

[Joe P. <joe...@sn...>]

To all hpoj-devel list members:

Now is your chance to help. David has asked for an update to one of my 
previous posts, which he says he would like to put in the next release, which 
will probably occur soon. I've attached the article below. Please read and 
post any comments or corrections you may have. Thanks in advance.


David: 

I made a few more changes to xojpanel/ojstatus.cpp. Nothing really important, 
just  changes to comments and "pixmap not found" error messages. The new code 
is up on my site.

Do my recent changes to the pixmap loading code work correctly?
Does it still segfault?

-- 
Joe Piolunek

RE: [hpoj-devel] SMP patches?

[PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...>]

Robert G. Brown wrote:
> Searching the hpoj-devel list archives, I learned that there 
> has been a
> patch proposed for smp systems because of deadlock issues 
> resulting from
> a non-smp-safe bottom half handler.  I looked for the patch as best I
> could on the website, but found nothing.
Hi, Robert.  Please see http://hpoj.sourceforge.net/todo.shtml.  You can use
the patch against 0.6, unless you want to deal with downloading from CVS and
then patching that.

> I have a bit of kernel module and smp expertise myself (at 
> least enough
> to know what a "bottom half handler" is:-) and can possibly even help
> intelligently in the event that the patch doesn't fix my problem(s).
All input is welcome.  :-)  If nothing else perhaps you can review the
changes to ieee12844pp.c and ieee12844.c (particularly the functions
mlc_sendmsg and mlc_recvmsg in the latter file) and let us know if you see
any problems.

> Now regarding "perfectly".  I'm using the cdj550 filter, but 
> results on
> photographs leave a great deal to be desired.  I feel like I'm getting
> at most a tiny fraction of the printer's potential 
> resolution.
Yes, unfortunately this is the case at the moment, but there is work being
done within HP to develop an open-source driver to take advantage of the
newer inkjets (http://www.linux.hp.com/open_letter.html).

If you don't mind patching and rebuilding ghostscript, then you might
benefit some from this DeskJet 970C driver, which should also work on the
OfficeJet G and K series:

http://www.linuxprinting.org/show_driver.cgi?driver=cdj970
http://www.harsch.net/Ghostscript/ghostscript.html

The second site is in German.  Babelfish
(http://www.babelfish.altavista.com)
gives a fairly decent translation.  If you try this out I would be
interested to hear about your impression/experience with it.

> Again diligently searching the web I see that there is an 
> "hpdj" driver
> for postscript that is being developed that speaks pcl3+ and 
> that might
> produce superior results on the G55 or other OfficeJets.
The hpdj driver is for the original DeskJet and DeskJet Plus.  Supposedly it
produces better text than cdj550, but it appears to be black and white only,
not color.

David

[hpoj-devel] [hpoj-devl] A hack For those of you with external zip drives

[Sammy R. <re...@ca...>]

For those of you linuxers with zip drive if you are running linux
mandrake or red hat and only have one parallel port to share your zip
drive and printer with use this quick hack to run both devices on the
same port goto /etc/rc.d/rc.sysinit and write the following lines in
after it loads the sound modules or it won't work

#load parallel port
/sbin/modprobe parport
/sbin/modprobe parport_pc
/sbin/modprobe parport_probe

#load zip drive
/sbin/modprobe imm (this for zip250 use the one applicable to zip 100)

#load printer
insmod  /usr/local/bin/ieee12844.o
insmod /usr/local/bin/ieee12844pp.o

i must be done in this order or it won't work and don't have your zip
drive compiled into the kernal either or it won't work
/sbin/modprobe bit are assuming you have the module installed in the
kernal i think not entirely sure other wise insmod them from where ever
they are.
i hope this helps

my regards sammy

[hpoj-devel] SMP patches?

[Robert G. B. <rg...@ph...>]

Dear List Persons:

I greet you!  I just got a OJ G55 for the home to print photos and so
forth on.  It hangs on a dual Celeron (Abit BP6 motherboard) running RH
linux 6.2 with the 2.2.16-3smp kernel.  I diligently searched and found
the hpoj site and 0.6 drivers, compiled them, and they work -- sort of.

The most common problem I have produces the following message:

Nov 29 08:51:37 lucifer kernel: mlcpp0: mlcpp_transmit while TX busy
Nov 29 08:59:19 lucifer kernel: mlcpp0: mlcpp_transmit while TX busy

This seems to trash a tiny but critical part of the stream, and kicks
the printer off of printing e.g. a full color picture into printing all
the associated ASCII, whereupon I scrabble for the cancel button.  To
recover I minimally have to restart the printer daemon and sometimes
have to unload and reload the ieee12844 modules as well.

Searching the hpoj-devel list archives, I learned that there has been a
patch proposed for smp systems because of deadlock issues resulting from
a non-smp-safe bottom half handler.  I looked for the patch as best I
could on the website, but found nothing.

Could someone provide me directions to the patch?

I have a bit of kernel module and smp expertise myself (at least enough
to know what a "bottom half handler" is:-) and can possibly even help
intelligently in the event that the patch doesn't fix my problem(s).

Note that it does seem like a deadlock issue because it doesn't always
happen -- I can print as many as a couple of pictures "perfectly" (see
below) and then lose it in the third.  Before I saw the possibility of
an SMP problem I was suspecting a handshaking problem or an overrun
problem -- it is that kind of thing.

Now regarding "perfectly".  I'm using the cdj550 filter, but results on
photographs leave a great deal to be desired.  I feel like I'm getting
at most a tiny fraction of the printer's potential resolution.  This is
especially visible comparing the results of copying a photograph using
the printer's copy function and the results of scanning it into sane at
full resolution and trying to print that.  It also, however, shows up in
e.g. TIFF's and hi-res jpegs printed from images from our 3.3. Mpixel
camera.

Again diligently searching the web I see that there is an "hpdj" driver
for postscript that is being developed that speaks pcl3+ and that might
produce superior results on the G55 or other OfficeJets.

Are there any remarks on this?  Am I doing things correctly/incorrectly?
I'm using the printcap "formula" suggested for Red Hat in the hpoj
documents and it "works" (except for the aforementioned smp problem) but
never at anything close to even 600x600 dpi, let alone the 2400x1200 the
printer is nominally capable of.

Thanks,

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rg...@ph...

RE: [hpoj-devel] 1150C scanning locks up

[Graham V. <gr...@gp...>]

Hello David.

> Hi, Graham.  The fixes for this particular problem are actually in
> ieee12844pp.c, not ieee12844.c.  For now, if you don't want to mess with
> CVS, then your best option would be to apply the "patch against 0.6"
> available at http://hpoj.sourceforge.net/todo.shtml.  0.7 will have this fix
> when it comes out.

Patch applied & rebuilt. Scanning now up and running :-)

Many thanks,

Graham
.
Graham Vincent, Engineering Director, GPV Enterprises Ltd.
PO Box 5001, New Plymouth, New Zealand. Phone 025-814-655
email gr...@gp...   URL http://www.gpv.co.nz

Re: [hpoj-devel] Scanned images "too blue"

[<pa...@rc...>]

James Fidell wrote:
> I have printing and scanning working with my OfficeJet 1175c (though I've
> only done fairly limited testing so far), but the scanned images are
> very blue compared with the originals.
> 
> Is there any simple way to fix this problem?

Hi, James.  If you're using xsane, then you can click off the "RGB Default"
button (the first of six buttons just above the "Start" button.  That allows
you to individually adjust the gamma, brightness, and contrast for each
color component.  Alternatively, if you have already scanned your pictures,
then I'm sure you can make adjustments in Gimp.

David

[hpoj-devel] Scanned images "too blue"

[James F. <ja...@cl...>]

I have printing and scanning working with my OfficeJet 1175c (though I've
only done fairly limited testing so far), but the scanned images are
very blue compared with the originals.

Is there any simple way to fix this problem?

Thanks,
James
-- 
 "Yield to temptation --             | Consultancy: ja...@cl... 
  it may not pass your way again"    | http://www.cloud9.co.uk/james
                                     |
        - Lazarus Long               |              James Fidell

[hpoj-devel] got scanner working

[Sammy R. <re...@ca...>]

Just informing you lot that i have now got the the scanner working on my
hp 1150c using the patch in the CVS repository it a bit slow bit it
earlys days.
i am wondering when scanning in colour should it stop start and then
move one step forward just wondering?
Umm in previsour which you havent answered yet i still have problem
getting it to print with ieee12844_print could some one send me a copy
of their wrap filter for the 1150c please?

sammy

RE: [hpoj-devel] more install problems

[PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...>]

Hi, Mike.

Mike Schauer wrote:
> Hi all.  I sent a message in a while back having problems 
> installing hpoj 
> 0.6.  I wanted to upgrade from Redhat 6.2 to 7.0, but after 
> having problems 
> with that, decided to reinstall 6.2, and must also therefore, 
> reinstall hpoj. 
>  Now, I run the '. configure' and it works fine.  I run the 
> 'make' and it 
> outputs a ton of 'gcc .......' lines, but none of those say 
> 'Error'.  then I 
> run 'make install' and it tells me that install is up to 
> date'.
Make sure there isn't a file called "install" in the hpoj-0.6 directory.
(There is a file called "install-sh", which is correct.)

> what am I 
> forgetting?  I would include all the output from the make 
> script, but there 
> wouyld be pages and pages of it.  You would not be able to 
> find my email 
> message for all that.  thanks much.
There are a lot of warnings in the "ptal" directory to the effect that
control reaches the end of non-void functions.  These are OK because they
are due to stub functions I laid out but haven't actually implemented yet,
and there may be warnings in other directories as well.  However, you have
gotten my curiosity up about these "pages and pages" of warnings, so if you
want to e-mail them to me (pa...@rc..., dav...@hp...) directly
as an attachment (so as not to bother everyone on the list with it), then
I'll take a look at it and see if there are any problems.

David

RE: [hpoj-devel] 1150C scanning locks up

[PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...>]

Graham Vincent wrote:
> I have successfully built the hpoj-0.6 modules and compiled sane 
> with the 1.0.3 patch applied. RH 6.2 with 2.2.17 kernel on a single 
> intel processor, via apollo chipset, board.
> 
> When I try an "xscanimage" there is a short period of activity 
> followed by nothing but a flashing light on the 1150C with the 
> message "Scanning". I haven't worked out how to unjam things 
> without rebooting which is rather embarrassing for a Linux user!
> 
> Can anyone help me sort this out please?
> 
> I have also tried changing the ieee12844.c to the version available 
> from the CVS tree but it generated a stack of errors during the 
> compile - I have no idea how to use the CVS resource properly - 
> can someone point me to a tutorial or advise me on its use?

Hi, Graham.  The fixes for this particular problem are actually in
ieee12844pp.c, not ieee12844.c.  For now, if you don't want to mess with
CVS, then your best option would be to apply the "patch against 0.6"
available at http://hpoj.sourceforge.net/todo.shtml.  0.7 will have this fix
when it comes out.

David

[hpoj-devel] [hpoj-devel]

[Sammy R. <re...@ca...>]

Can you lot have another look at the wrap filter this is the what did
i opened up the  filter script wrote what was in the print how to readme then deleted
all the other bits of script in the file
then saved it as wrapfilter but it still doesn't want to work when i go to where the
file resides /usr/local/bin
and run ieee12844_print from the command line nothing happens or in a winblows term
it locks.
I wondering if it the actual ieee12844_print file that stopping the wrap filter from
working?
so i sending both of them to you lot to have a look at

 I would be greatful for any help thx sammy

Re: [hpoj-devel] installation problems

[Sammy R. <re...@ca...>]

Marco Bruschi wrote:

> Hi David,
> yes, following your suggestion, I installed g++.
> Now I'll try to make the modification you suggest.
> I'll let you know.
> Thanks a lot,
> Marco
>
> On Sun, 26 Nov 2000, David Paschal wrote:
>
> > Hi, Marco.  First of all, I'll say that this is a very strange problem.
> > What did you do to make ./configure work?  Do you have "g++" installed
> > now?
> >
> > Somewhere in "apps/xojpanel/Makefile", there's a line that says "CC = gcc".
> > Try changing that to "CC = g++" and see if that helps.
> >
> > David
> >
> > Marco Bruschi wrote:
> > >
> > > Hi, now the ./configure is works fine.
> > > I get problems on "make" with the following output
> > >
> > > gcc: ojstatus.cpp: linker input file unused since linking not done
> > > gcc: ojmanager.cpp: linker input file unused since linking not done
> > > gcc: moc_oj.cpp: linker input file unused since linking not done
> > > gcc: ojstatus.o: No such file or directory
> > > gcc: ojmanager.o: No such file or directory
> > > gcc: moc_oj.o: No such file or directory
> > > make[2]: *** [xojpanel] Error 1
> > > make[1]: *** [release] Error 2
> > > make: *** [release] Error 2
> > > bruschi-rem:/usr/lib/hpoj-0.6 # less error.txt
> > > bruschi-rem:/usr/lib/hpoj-0.6 # make > error.txt
> > > gcc: ojstatus.cpp: linker input file unused since linking not done
> > > gcc: ojmanager.cpp: linker input file unused since linking not done
> > > gcc: moc_oj.cpp: linker input file unused since linking not done
> > > gcc: ojstatus.o: No such file or directory
> > > gcc: ojmanager.o: No such file or directory
> > > gcc: moc_oj.o: No such file or directory
> > > make[2]: *** [xojpanel] Error 1
> > > make[1]: *** [release] Error 2
> > > make: *** [release] Error 2
> These  seem to be occuring from the fact that your gcc header files are not installed
> it happend to me as well

sammy

>

>
> > > Any idea about how to proceed ?
> > > Thanks a lot again
> > > Marco
> > >
> > >
> > >
> > > On Mon, 20 Nov 2000, David Paschal wrote:
> > >
> > > > Marco Bruschi wrote:
> > > > ...
> > > > > checking for c++... no
> > > > > checking for g++... no
> > > > > checking for gcc... gcc
> > > > > checking whether the C++ compiler (gcc  ) works... no
> > > > > configure: error: installation or configuration problem: C++ compiler
> > > > > cannot create executables.
> > > > ...
> > > >
> > > > Hi, Marco.  Make sure you have the C++ compiler installed.  I don't know
> > > > what the package name is for SuSE, but on RedHat 6.2 it's "egcs-c++-1.1.2-30".
> > > >
> > > > David
> >
> > _______________________________________________
> > hpoj-devel mailing list
> > hpo...@li...
> > http://lists.sourceforge.net/mailman/listinfo/hpoj-devel
> >
>
> _______________________________________________
> hpoj-devel mailing list
> hpo...@li...
> http://lists.sourceforge.net/mailman/listinfo/hpoj-devel

[hpoj-devel] 1150C scanning locks up

[Graham V. <gr...@gp...>]

Hello.

I have successfully built the hpoj-0.6 modules and compiled sane 
with the 1.0.3 patch applied. RH 6.2 with 2.2.17 kernel on a single 
intel processor, via apollo chipset, board.

The insmod list executes OK - see section of /var/log/messages 
below. A "hpo devid" responds OK with the 1150C info. The sane 
dll.conf and hp.conf files are setup as detailed.

When I try an "xscanimage" there is a short period of activity 
followed by nothing but a flashing light on the 1150C with the 
message "Scanning". I haven't worked out how to unjam things 
without rebooting which is rather embarrassing for a Linux user!

from /var/log/messages

Nov 25 15:40:59 hal kernel: parport0: PC-style at 0x378 (0x778) 
[SPP,EPP,ECP,ECPEPP,ECPPS2] 
Nov 25 15:40:59 hal kernel: parport0: detected irq 7; use procfs to 
enable interrupt-driven operation. 
Nov 25 15:41:07 hal kernel: parport0: Printer, HEWLETT-
PACKARD OFFICEJET PRO 1150C 
Nov 25 15:41:34 hal kernel: IEEE1284.4 protocol layer for Linux 
installed 
Nov 25 15:41:42 hal kernel: ieee12844pp: IEEE1284.4 device found 
on parport0: 
Nov 25 15:41:42 hal kernel:    HEWLETT-PACKARD OFFICEJET 
PRO 1150C; 
Nov 25 15:41:42 hal kernel:    device registered to IEEE1284.4 
protocol layer as link mlcpp0 
Nov 25 15:44:37 hal kernel: 
PAR_WAIT_SET_CLEAR(l=c882c160,set=0x0000,clear=0x0040): 
timed out waiting for event=9! 
Nov 25 15:44:37 hal kernel: mlcpp0: mlcpp_intr ERROR -110 
Nov 25 15:44:37 hal kernel:   state=5 event=9 reset=7 recv=3 rcv=0 
send=2 
Nov 25 15:44:37 hal kernel: mlc: mlcpp0: link error -110 
Nov 25 15:50:52 hal kernel: 
PAR_WAIT_SET_CLEAR(l=c882c160,set=0x0098,clear=0x0040): 
timed out waiting for event=23! 
Nov 25 15:50:52 hal kernel: mlcpp0: mlcpp_intr ERROR -110 
Nov 25 15:50:52 hal kernel:   state=7 event=23 reset=7 recv=3 
rcv=0 send=2 
Nov 25 15:50:52 hal kernel: mlc: mlcpp0: link error -110 

Can anyone help me sort this out please?

I have also tried changing the ieee12844.c to the version available 
from the CVS tree but it generated a stack of errors during the 
compile - I have no idea how to use the CVS resource properly - 
can someone point me to a tutorial or advise me on its use?

Thanks,

Graham

.
Graham Vincent, Engineering Director, GPV Enterprises Ltd.
PO Box 5001, New Plymouth, New Zealand. Phone 025-814-655
email gr...@gp...   URL http://www.gpv.co.nz

[hpoj-devel] more install problems

[<Hur...@ao...>]

Hi all.  I sent a message in a while back having problems installing hpoj 
0.6.  I wanted to upgrade from Redhat 6.2 to 7.0, but after having problems 
with that, decided to reinstall 6.2, and must also therefore, reinstall hpoj. 
 Now, I run the '. configure' and it works fine.  I run the 'make' and it 
outputs a ton of 'gcc .......' lines, but none of those say 'Error'.  then I 
run 'make install' and it tells me that install is up to date'.  what am I 
forgetting?  I would include all the output from the make script, but there 
wouyld be pages and pages of it.  You would not be able to find my email 
message for all that.  thanks much.

Mike Schauer

Re: [hpoj-devel] Re: installation

[<pa...@rc...>]

Joe Piolunek wrote:
> According to complaints coming from Linux spokespeople, HP is holding back on 
> information or releasing it too slowly. Is there any comment you can make on 
> this, David?
Hi, Joe.  The DeskJet driver is coming from a different division from the one
I work in, but I have been in contact with the project manager for that and
they are working on it, as the aforementioned Open Letter response suggests.
Sometimes information that is being "held back" isn't released because it
belongs to third parties who don't want it released, so there isn't much
that can be done, as is the case for a certain pair of unsupportable
LaserJet all-in-ones.  That's about all I can say on the matter (and I speak
for myself, not for HP).

> > (Dean Hoover)
> > > I could not get the wrapfilter change to do anything,
> > > so I left it out for now. I am attaching copies of my
> > > /etc/printcap, gamma.ps, filter, and wrapfilter files.
> 
> Try setting up the hpoj driver only after you have your system printing in an 
> acceptable fashon. It isn't necessary for printing, and won't improve the 
> quality.
Although it's not necessary to print through ieee12844_print, it is helpful
to be able to print and scan using the same kernel drivers.  Also,
ieee12844_print wraps the job in some PJL commands that tell the printer
where the job begins and ends.  This should fix the "blinking light syndrome"
at the end of the print job.  I didn't think of this the other day.  The
"addpjl" command in the "scripts" directory does the same thing.

> > wrapfilter:
> > > #!/bin/sh
> > > QUEUEDIR=/var/spool/lpd/HPofficejet
> > > IEEE12844DIR=/usr/local/bin
> > > ${QUEUEDIR}/filter "$@" | ${IEEE12844DIR}/ieee12844_print
> > >
> > > --------------26DB7C4A1E222CA8AFA30D40--
> 
> I don't understand what the line immediately above is for.
Sorry.  I missed that when I was removing the junk added by MIME.

David

Re: [hpoj-devel] test of cvs + smp patch, xojpanel

[<pa...@rc...>]

Joe Piolunek wrote:
> Have you or has anyone else been able to test the more recent xojpanel code 
> on an officejet that uses a two-line LCD? Do whitespace stripping, line-2 
> scrolling and scroll-delays work the way you expect?
It's better, in that text on the second line scrolls properly (and only when
necessary), but now it segfaults when the second line is blank and the
peripheral returns a string of spaces (which is the case on the K80 and G85).
It works OK on the 570 (which only has one line anyway) because it doesn't
return the superfluous spaces when asked for the second line.

> Is it definite that no OfficeJets output unicode to their LCD? If they don't, 
> it might make more sense to #define something like "USE_QCHAR"  in place of 
> "UNICODE_SUPPORT" for whitespace stripping. Should It be changed?
I'm pretty sure that there is currently no Unicode support.  If there were
you would know it by what symbol set was specified in the PML GET reply.
For now I don't think you need to worry about that.  If it ever became
necessary, then you could check the symbol set at runtime and respond
appropriately.  Of course, this runtime switch should only be enabled for
appropriate versions of QT.  From this standpoint it might make sense to
call it "USE_QCHAR" instead.

Here are a couple of other suggestions:

- Create a single function (possibly an overridden QPixmap::load) which
takes a simple filename parameter and does the magic of trying to load it
from the various possible locations and printing an error message if
unsuccessful.  It's easier to maintain this code in once place.  Of course,
when adding a path you'll have to use a temporary buffer, which should
probably be dynamically allocated (and freed) to be able to fit the default
path, simple filename, slash in between (if necessary), and final null byte.

- Instead of hard-coding the default path, use something like this:
#ifndef XOJPANEL_DEFAULT_PATH
#define XOJPANEL_DEFAULT_PATH "/usr/local/share/pixmaps/hpoj/"
#endif
That way, I can modify the configure/build process to pass the right path
if the user specifies the "--prefix=<DIR>" switch to the configure script
to change the install directory.

David

Re: [hpoj-devel] installation problems

[Marco B. <br...@ma...>]

Hi David,
yes, following your suggestion, I installed g++.
Now I'll try to make the modification you suggest.
I'll let you know.
Thanks a lot,
Marco


On Sun, 26 Nov 2000, David Paschal wrote:

> Hi, Marco.  First of all, I'll say that this is a very strange problem.
> What did you do to make ./configure work?  Do you have "g++" installed
> now?
> 
> Somewhere in "apps/xojpanel/Makefile", there's a line that says "CC = gcc".
> Try changing that to "CC = g++" and see if that helps.
> 
> David
> 
> Marco Bruschi wrote:
> > 
> > Hi, now the ./configure is works fine.
> > I get problems on "make" with the following output
> > 
> > gcc: ojstatus.cpp: linker input file unused since linking not done
> > gcc: ojmanager.cpp: linker input file unused since linking not done
> > gcc: moc_oj.cpp: linker input file unused since linking not done
> > gcc: ojstatus.o: No such file or directory
> > gcc: ojmanager.o: No such file or directory
> > gcc: moc_oj.o: No such file or directory
> > make[2]: *** [xojpanel] Error 1
> > make[1]: *** [release] Error 2
> > make: *** [release] Error 2
> > bruschi-rem:/usr/lib/hpoj-0.6 # less error.txt 
> > bruschi-rem:/usr/lib/hpoj-0.6 # make > error.txt
> > gcc: ojstatus.cpp: linker input file unused since linking not done
> > gcc: ojmanager.cpp: linker input file unused since linking not done
> > gcc: moc_oj.cpp: linker input file unused since linking not done
> > gcc: ojstatus.o: No such file or directory
> > gcc: ojmanager.o: No such file or directory
> > gcc: moc_oj.o: No such file or directory
> > make[2]: *** [xojpanel] Error 1
> > make[1]: *** [release] Error 2
> > make: *** [release] Error 2
> > 
> > Any idea about how to proceed ?
> > Thanks a lot again
> > Marco
> > 
> > 
> > 
> > On Mon, 20 Nov 2000, David Paschal wrote:
> > 
> > > Marco Bruschi wrote:
> > > ...
> > > > checking for c++... no
> > > > checking for g++... no
> > > > checking for gcc... gcc
> > > > checking whether the C++ compiler (gcc  ) works... no
> > > > configure: error: installation or configuration problem: C++ compiler
> > > > cannot create executables.
> > > ...
> > > 
> > > Hi, Marco.  Make sure you have the C++ compiler installed.  I don't know
> > > what the package name is for SuSE, but on RedHat 6.2 it's "egcs-c++-1.1.2-30".
> > > 
> > > David
> 
> _______________________________________________
> hpoj-devel mailing list
> hpo...@li...
> http://lists.sourceforge.net/mailman/listinfo/hpoj-devel
> 

Re: [hpoj-devel] [hpoj-devel]

[<pa...@rc...>]

Sammy Redshaw wrote:
> Right I am little stuck getting my Office jet pro 1150c to work i've got drivers
> installed and it talking fine to the computer now problem no .1
> i done as per suggested in getting the office jet to work using print cap the
> only thing it dosen't work can you have a look at the wrapfilter file that
> resides in
> "$ /var/spool/lpd/lp0".
> and the etc/printcap file and edit them so that they do work.
Hi, Sammy.  /etc/printcap looks OK, wrapfilter doesn't.  See below for my
corrections.  If you still have problems with these changes, please give me
more information about what's wrong, such as any error messages you see.
Another thing -- make sure wrapfilter is executable (issue the command
"chmod +x /var/spool/lpd/lp0wrapfilter" if you haven't already).

> I've tried this
> with and with out the printer attached to port via the zip 250 drive make no
> difference.
The OfficeJet needs to be connected directly to your PC, not through the Zip
drive.

> Problem no. two patched sane-1.0.3 complies and installs fine only problem is to
> run it i have to go to"$ usr/local/bin then do "$ . /xscanimage" when i do this
> the scanner locks any idea why this is. I should see no problem with this
> installation even if i am running linux mandrake 7 on 2.2.14 kernal which is the
> same as red hat .
This is a known problem while will be fixed in the next version.  For now,
there is a patch available at "http://hpoj.sourceforge.net/todo.shtml".
In your case, you can download the "patch against 0.6"
(http://hpoj.sourceforge.net/download/patches/hpoj-0.6-smp-patch-20001120.txt)
into the "hpoj-0.6" directory.  cd into the "hpoj-0.6" directory, and issue
the command "patch -p 1 <hpoj-0.6-smp-patch-20001120.txt".

wrapfilter:
> 
> #! /bin/sh
    ^
    0
> 
> QUEUEDIR=/var/spool/lpd/lp
                            ^
                            1
> IEEE128444DIR=usr/local/bin
           ^    ^
           2    3
> 
> ${QUEUEDIR} /filter "$@" | ${IEEE12844DIR} /ieee12488_print
             ^                              ^       ^^^
             4                              4        5
0. I don't normally put a space here, but it's probably OK with a space.
1. You said this was in "/var/spool/lpd/lp0", so this needs to be consistent.
2. Remove the extra "4" (it should be "IEEE12844DIR").
3. Put a slash in front of "usr" (it should be "/usr/local/bin").
4. Remove the spaces between the "}" and the "/" (twice on this line).
5. "12844" instead of "12488" (should be "ieee12844_print").

So here's how wrapfilter should look in its entirety.  Remove the "> " at
the beginning of each line, of course:
> #!/bin/sh
> 
> QUEUEDIR=/var/spool/lpd/lp0
> IEEE12844DIR=/usr/local/bin
> 
> ${QUEUEDIR}/filter "$@" | ${IEEE12844DIR}/ieee12844_print

I hope this helps.

David

Re: [hpoj-devel] installation problems

[<pa...@rc...>]

Hi, Marco.  First of all, I'll say that this is a very strange problem.
What did you do to make ./configure work?  Do you have "g++" installed
now?

Somewhere in "apps/xojpanel/Makefile", there's a line that says "CC = gcc".
Try changing that to "CC = g++" and see if that helps.

David

Marco Bruschi wrote:
> 
> Hi, now the ./configure is works fine.
> I get problems on "make" with the following output
> 
> gcc: ojstatus.cpp: linker input file unused since linking not done
> gcc: ojmanager.cpp: linker input file unused since linking not done
> gcc: moc_oj.cpp: linker input file unused since linking not done
> gcc: ojstatus.o: No such file or directory
> gcc: ojmanager.o: No such file or directory
> gcc: moc_oj.o: No such file or directory
> make[2]: *** [xojpanel] Error 1
> make[1]: *** [release] Error 2
> make: *** [release] Error 2
> bruschi-rem:/usr/lib/hpoj-0.6 # less error.txt 
> bruschi-rem:/usr/lib/hpoj-0.6 # make > error.txt
> gcc: ojstatus.cpp: linker input file unused since linking not done
> gcc: ojmanager.cpp: linker input file unused since linking not done
> gcc: moc_oj.cpp: linker input file unused since linking not done
> gcc: ojstatus.o: No such file or directory
> gcc: ojmanager.o: No such file or directory
> gcc: moc_oj.o: No such file or directory
> make[2]: *** [xojpanel] Error 1
> make[1]: *** [release] Error 2
> make: *** [release] Error 2
> 
> Any idea about how to proceed ?
> Thanks a lot again
> Marco
> 
> 
> 
> On Mon, 20 Nov 2000, David Paschal wrote:
> 
> > Marco Bruschi wrote:
> > ...
> > > checking for c++... no
> > > checking for g++... no
> > > checking for gcc... gcc
> > > checking whether the C++ compiler (gcc  ) works... no
> > > configure: error: installation or configuration problem: C++ compiler
> > > cannot create executables.
> > ...
> > 
> > Hi, Marco.  Make sure you have the C++ compiler installed.  I don't know
> > what the package name is for SuSE, but on RedHat 6.2 it's "egcs-c++-1.1.2-30".
> > 
> > David