You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
(111) |
Oct
(63) |
Nov
(64) |
Dec
(116) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(49) |
Feb
(27) |
Mar
(136) |
Apr
(59) |
May
(122) |
Jun
(72) |
Jul
(167) |
Aug
(77) |
Sep
(103) |
Oct
(128) |
Nov
(86) |
Dec
(87) |
2002 |
Jan
(150) |
Feb
(111) |
Mar
(112) |
Apr
(139) |
May
(204) |
Jun
(228) |
Jul
(202) |
Aug
(244) |
Sep
(215) |
Oct
(311) |
Nov
(127) |
Dec
(229) |
2003 |
Jan
(252) |
Feb
(119) |
Mar
(163) |
Apr
(166) |
May
(91) |
Jun
(84) |
Jul
(106) |
Aug
(98) |
Sep
(93) |
Oct
(161) |
Nov
(82) |
Dec
(62) |
2004 |
Jan
(58) |
Feb
(44) |
Mar
(56) |
Apr
(67) |
May
(50) |
Jun
(57) |
Jul
(20) |
Aug
(25) |
Sep
(33) |
Oct
(35) |
Nov
(61) |
Dec
(95) |
2005 |
Jan
(61) |
Feb
(31) |
Mar
(17) |
Apr
(10) |
May
(2) |
Jun
(13) |
Jul
(4) |
Aug
(10) |
Sep
(9) |
Oct
(33) |
Nov
(2) |
Dec
(7) |
2006 |
Jan
(11) |
Feb
(3) |
Mar
(3) |
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Carlos P. <cp...@ro...> - 2001-05-17 05:54:44
|
[embarrased] the printer had (somehow) shut down at some point in the afternoon, thus it was not listed, as pete z. pointed out. now, after restarting it, it does in fact seem like the printer is indeed now detected by the printer module: bash# lsmod | egrep "usb|printer|Module|uhci" Module Size Used by printer 4928 1 uhci 22144 0 (unused) usbcore 49664 1 [printer uhci] bash# i am astonished and embarrased to report that things just work now, after two *d@mned* days of fiddling with this problem in various ways. sorry for bothering you guys - now ... what _really_ bothers me now is that i have no idea what is the right thing to do... i noted the modules running (uhci), and rebooted the linux box ... hmmm, it does not work. the ptal daemos are there ... yet the printer module is *not* used: bash# get ptal root 670 0.0 0.1 1864 612 ? S 00:32 0:00 /opt/hpoj-010515/bin/ptal-mlcd usb:0 -device /dev/usb/lp0 root 672 0.0 0.1 1372 404 ? S 00:32 0:00 /opt/hpoj-010515/bin/ptal-printd mlc:usb:0 -like /dev/lp0 bash# lsmod | egrep "usb|printer|Module|uhci" Module Size Used by printer 4928 0 (unused) uhci 22144 0 (unused) usbcore 49664 1 [printer uhci] bash# like this, lpr just "sucks" print jobs into oblivion. i tried rebooting the printer ... this shows up ... May 17 00:38:04 tcb kernel: usb.c: USB disconnect on device 4 May 17 00:38:48 tcb kernel: hub.c: USB new device connect on bus1/2, assigned device number 5 May 17 00:38:48 tcb kernel: printer.c: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 but nothing, the daemons come up, bash# get ptal root 1812 0.0 0.1 1864 612 ? S 00:38 0:00 /opt/hpoj-010515/bin/ptal-mlcd usb:0 -device /dev/usb/lp0 root 1814 0.0 0.1 1372 400 ? S 00:38 0:00 /opt/hpoj-010515/bin/ptal-printd mlc:usb:0 -like /dev/lp0 bash# but the printer is still unused: bash# lsmod | egrep "usb|printer|Module|uhci" Module Size Used by printer 4928 0 (unused) uhci 22144 0 (unused) usbcore 49664 1 [printer uhci] bash# looking at the /var/log/messages, i am going to try to reconstruct what happened before, the only interesting things that happened are: May 16 17:34:06 tcb kernel: usb.c: USB disconnect on device 2 [must have been when the printer shut itself off?] then ... i am not sure what happened here to trigger this (kernel autoclean of modules?): May 16 21:53:02 tcb kernel: usb.c: deregistering driver usblp May 16 21:53:02 tcb kernel: usb.c: USB disconnect on device 1 May 16 21:53:02 tcb kernel: usb.c: USB bus 1 deregistered May 16 21:53:02 tcb kernel: usb.c: USB disconnect on device 3 May 16 21:53:02 tcb kernel: usb.c: USB bus 2 deregistered May 16 21:53:16 tcb kernel: PCI: Found IRQ 9 for device 00:04.2 May 16 21:53:16 tcb kernel: PCI: The same IRQ used for device 00:04.3 May 16 21:53:16 tcb kernel: uhci.c: USB UHCI at I/O 0xb400, IRQ 9 May 16 21:53:16 tcb kernel: usb.c: new USB bus registered, assigned bus number 1 May 16 21:53:16 tcb kernel: hub.c: USB hub found May 16 21:53:16 tcb kernel: hub.c: 2 ports detected May 16 21:53:16 tcb kernel: PCI: Found IRQ 9 for device 00:04.3 May 16 21:53:16 tcb kernel: PCI: The same IRQ used for device 00:04.2 May 16 21:53:16 tcb kernel: uhci.c: USB UHCI at I/O 0xb000, IRQ 9 May 16 21:53:16 tcb /etc/hotplug/usb.agent: ... no drivers for USB product 0/0/0 May 16 21:53:16 tcb kernel: usb.c: new USB bus registered, assigned bus number 2 May 16 21:53:16 tcb kernel: hub.c: USB hub found May 16 21:53:16 tcb kernel: hub.c: 2 ports detected May 16 21:53:16 tcb /etc/hotplug/usb.agent: ... no drivers for USB product 0/0/0 and then, this (i'm sure about this) must have been a little bit ago when i got tipped that the printer was not connected and printing worked: May 17 00:19:32 tcb kernel: hub.c: USB new device connect on bus1/2, assigned device number 6 May 17 00:19:32 tcb kernel: usb.c: USB device 6 (vend/prod 0x3f0/0x11) is not claimed by any active driver. May 17 00:19:32 tcb kernel: usb.c: registered new driver usblp May 17 00:19:32 tcb kernel: printer.c: usblp0: USB Bidirectional printer dev 6 if 0 alt 0 and i cannto reproduce the situation. i tried unloading printer and uhci, then starting the printer and various other things ... printer is still unused: bash# lsmod | egrep "usb|printer|Module|uhci" Module Size Used by printer 4928 0 (unused) uhci 22144 0 (unused) usbcore 49664 1 [printer uhci] bash# thank you for your patience ... if you have any ideas, please let me know. to finish up, here is the /proc/bus/usb/devices: bash# cat /proc/bus/usb/devices T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 8 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI-alt Root Hub S: SerialNumber=b000 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 7 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI-alt Root Hub S: SerialNumber=b400 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=01 Prnt=07 Port=01 Cnt=01 Dev#= 9 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0011 Rev= 1.00 S: Manufacturer=Hewlett-Packa S: Product=OfficeJet G55 S: SerialNumber=SGD05106RCVL C:* #Ifs= 1 Cfg#= 1 Atr=00 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 3 Cls=07(print) Sub=01 Prot=03 Driver=usblp E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=255ms bash# thanks, -c __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ |
From: Carlos P. <cp...@ro...> - 2001-05-17 03:09:14
|
hi, i am trying to debug the situation of an hp officejet g55 connected to one of the onboard usb ports in my spakin' new asus a7v133. the printer is recognized but there is no way to print or scan from it (connecting it at the parallel port works fine both for i have updated to the latest bios, since people in the asus newsgroup were indicating that the previous ones were funky. suposedly, i have tried two bios that "should work well". so, maybe the problem is in the kernel. i am running a fresh redhat 7.1 install. i am trying to run the printer drivers from the hpoj group. when i run them in the parallel port mode they work fine. when running them with the usb mode, the first indication that there is something wrong is that open() calls to the /dev/usb/lp0 return -1 in the ptal-mlcd daemon when someone tries to use it: open("/dev/usb/lp0", O_RDWR) = -1 ENODEV (No such device) i have tried this with the usb-uhci and the uhci modules and the same thing happens: bash# killall -HUP ptal-printd ptal-mlcd ptal-printd: no process killed ptal-mlcd: no process killed bash# lsmod | egrep "usb|printer|Module" Module Size Used by printer 4928 0 usb-uhci 20720 0 (unused) usbcore 49664 1 [printer usb-uhci] bash# ptal-mlcd usb:0 -device /dev/usb/lp0 bash# lsmod | egrep "usb|printer|Module" Module Size Used by printer 4928 0 usb-uhci 20720 0 (unused) usbcore 49664 1 [printer usb-uhci] bash# ptal-devid mlc:usb:0 ptal-mlcd: ERROR at ExMgr.cpp:1974, dev=<usb:0>, pid=2627, errno=19 llioOpen: open failed! ptalMlcDeviceGetDeviceIDString(dev=usb:0): unsuccessful status=13! ptalDeviceGetDeviceIDString(dev=mlc:usb:0) failed! bash# killall -HUP ptal-printd ptal-mlcd ptal-printd: no process killed bash# rmmod printer usb-uhci bash# lsmod | egrep "usb|printer|Module" Module Size Used by usbcore 49664 1 bash# modprobe uhci bash# lsmod | egrep "usb|printer|Module|uhci" Module Size Used by uhci 22144 0 (unused) usbcore 49664 1 [uhci] bash# msg bash# killall -HUP ptal-printd ptal-mlcd ptal-printd: no process killed ptal-mlcd: no process killed bash# ptal-mlcd usb:0 -device /dev/usb/lp0 bash# ptal-devid mlc:usb:0 ptal-mlcd: ERROR at ExMgr.cpp:1974, dev=<usb:0>, pid=2700, errno=19 llioOpen: open failed! ptalMlcDeviceGetDeviceIDString(dev=usb:0): unsuccessful status=13! ptalDeviceGetDeviceIDString(dev=mlc:usb:0) failed! bash# lsmod | egrep "usb|printer|Module|uhci" Module Size Used by uhci 22144 0 (unused) usbcore 49664 1 [uhci] bash# - shouldn't the ptal-mlcd process cause the uhci and/or printer module to be "in use"? although i believe the driver does not talk to the printer unless it is required. - are there any known issues with this controller? bash# lspci | igrep usb 00:04.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) 00:04.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) bash# - what module should i be using? - i got the patch form the pat-o-matic in your web site from the kernel in the rh7.1 distribution, and things are indeed somewhat ahead in your cvs three, though, i am not sure how much. - are there any tools i could use to figure out this problem? (i am 100% new to usb ...) - is there any way to recompile just the usb modules without having to recompile the whole kernel? (make dep; make modules?) more info (is there any more info i could provide that would be useful?): bash# cat /proc/bus/usb/devices T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 5 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI-alt Root Hub S: SerialNumber=b000 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 4 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI-alt Root Hub S: SerialNumber=b400 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms bash# i would appreciate any ideas on how to get inside this problem to figure it out (i would really like to run this printer/scanner with usb due to performance issues). thanks in advance, -carlos ps: please cc: me in the reply, since i am not in the linux-usb-devel (but i am in the hpoj-devel). ===== C. Puchol <cp...@ro...> __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ |
From: Joe P. <joe...@sn...> - 2001-05-16 22:55:51
|
On Wednesday 16 May 2001 15:43, PASCHAL,DAVID (HP-Roseville,ex1) wrote: > > Using gimp, I cropped to the photo and printed the resulting > > image from the > > command line. Even though gimp reported the image as being > > about 3.5 x 5 in., > > when it printed, something automatically scaled it up to fit > > nearly the whole > > page. > > So I guess that's the culprit. What happens if you load the image in > Netscape or Gimp and print it there, where presumably there is no > fit-to-page? I didn't try it in gimp yet, but netscape greatly scales it up onscreen and prints it at full-page size. The image had been scanned at 300x300, resulting in a pixel size (after cropping) of 1057x1526. That's bigger than my video display (currently set at 1024x768). Apparently gimp was reporting its size in relation to the resolution setting for the scan, as if it would be printed at 300x300 dpi. Scanning a similarly sized object with -res 100, cropping in gimp, then printing the jpeg from netscape produces an image that is almost exactly the same size as the original. Printing the jpeg from the command line though, produces an image that is larger than (150% of) the original. This isn't much more than a guess, but it seems as if a small 300x300 image is treated as if it's (or converted to) a large low-res (100x100?) image, then being scaled down as needed to fit the paper. > So does the clock really "need to be set in order to scan", or just to get > rid of the message on the front panel telling you to set the clock? Normally the clock on the 600 does not need to be set to allow scanning. If one of the "SYSTEM ERRORXXXX" messages appears however, the printer will not scan again if it is simply restarted by pushing the power button once. Hitting the power button restarts or resets the printer in this case rather than shutting it off. To get the printer to accept the scan command again, I have been resetting the printer's clock by issuing the command "ptal-hp mlc:par:0 clock -set -mmddyy -12hour". The printer will scan again after that. If a "system error" messag appears again, I'll use the panel buttons to set the clock to see if that has the same effect on scanning. I'll also try restarting the printer twice with the power button instead of setting the clock. That should work, I think. -- Joe |
From: Heinz R. <ruf...@ya...> - 2001-05-16 22:26:54
|
Hi I just downloaded the hpoj-0.7 package and tried to compile it on my RH7.1 box (Kernel 2.4.2). It didn't work (see details below) After this I read the following statment in the downloaded INSTALL file: BUG: The kernel drivers currently fail to compile under kernel 2.4. They also do not work with SMP (any kernel version). These two problems are being worked on. When I'm reading the same file online on sourceforge (http://hpoj.sourceforge.net/hpoj/INSTALL), I can not find this statement. So my question is, can it be compiled under 2.4.2? Thanks a lot Heinz ./configure (worked ok) [ruffieux@locarno hpoj-0.7]$ configure creating cache ./config.cache checking operating system... Linux checking for Linux kernel source... /usr/src/linux-2.4.2 checking for SNMP... no. Try "./configure --with-snmp=3D<dir>" checking for QT... no. Try "./configure --with-qt=3D<dir>" checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking for c++... c++ checking whether the C++ compiler (c++ ) works... yes checking whether the C++ compiler (c++ ) is a cross-compiler... no checking whether we are using GNU C++... yes checking whether c++ accepts -g... yes checking for a BSD compatible install... /usr/bin/install -c checking whether ln -s works... yes checking how to run the C preprocessor... gcc -E checking for errno.h... yes checking for stdio.h... yes checking for stdlib.h... yes checking for unistd.h... yes checking for sys/socket.h... yes checking for sys/ioctl.h... yes checking for linux/version.h... yes checking for linux/parport.h... yes checking for net/sock.h... yes checking how to run the C++ preprocessor... c++ -E updating cache ./config.cache creating ./config.status creating Makefile creating ieee12844/Makefile creating ojlib/Makefile creating ptal/Makefile creating apps/Makefile creating apps/cmdline/Makefile creating apps/print/Makefile creating apps/xojpanel/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Configuration done. Created Makefiles using the following substitutions: prefix =3D /usr/local MAIN_MAKE_SUBDIRS =3D ptal ieee12844 ojlib apps APPS_MAKE_SUBDIRS =3D cmdline print bindir_program =3D ptal/ptal-connect ptal/ptal-printd scripts/addcr scripts/addpjl apps/cmdline/hpo apps/print/ieee12844_print libdir_program =3D libdir_data =3D ieee12844/ieee12844.o ieee12844/ieee12844pp.o includedir_data =3D ptal/ptal.h DEFINES_CMDLINE =3D -DHAVE_MLC INCLUDE_CMDLINE =3D -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include LIBRARY_CMDLINE =3D -L/opt/kits/hpoj-0.7/ojlib -L/opt/kits/hpoj-0.7/ptal LIBSNMP_CMDLINE =3D LINUX_VERSION =3D 2.4.2 QT_MOC =3D make (Problem) Note:=20 Wechsel in das Verzeichnis Verzeichnis =3D> Change to directory Verlassen des Verzeichnisses Verzeichnis =3D> Leave directory Fehler =3D> Error make[1]: Wechsel in das Verzeichnis Verzeichnis =BB/opt/kits/hpoj-0.7/ptal=AB cc -O1 -Wall -g -DHAVE_MLC -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -L/opt/kits/hpoj-0.7/ojlib -L/opt/kits/hpoj-0.7/ptal -fPIC -c -o ptal.o-shared ptal.c ptal.c: In function `ptalDeviceIsConnected': ptal.c:319: warning: control reaches end of non-void function ptal.c: In function `ptalDeviceGetDeviceIDString': ptal.c:324: warning: control reaches end of non-void function ptal.c: In function `ptalPmlObjectAllocate': ptal.c:893: warning: control reaches end of non-void function ptal.c: In function `ptalPmlObjectEnumerate': ptal.c:898: warning: control reaches end of non-void function ptal.c: In function `ptalPmlObjectDeallocate': ptal.c:902: warning: control reaches end of non-void function ptal.c: In function `ptalPmlObjectSetID': ptal.c:906: warning: control reaches end of non-void function ptal.c: In function `ptalPmlObjectGetID': ptal.c:910: warning: control reaches end of non-void function cc -O1 -Wall -g -DHAVE_MLC -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -L/opt/kits/hpoj-0.7/ojlib -L/opt/kits/hpoj-0.7/ptal -fPIC -c -o ptal-hpjd.o-shared ptal-hpjd.c ptal-hpjd.c: In function `ptalHpjdChannelOpen': ptal-hpjd.c:363: warning: passing arg 2 of `connect' from incompatible pointer type ptal-hpjd.c: In function `ptalHpjdPmlGet': ptal-hpjd.c:482: warning: control reaches end of non-void function ptal-hpjd.c: In function `ptalHpjdPmlGetNext': ptal-hpjd.c:486: warning: control reaches end of non-void function ptal-hpjd.c: In function `ptalHpjdPmlSet': ptal-hpjd.c:490: warning: control reaches end of non-void function cc -O1 -Wall -g -DHAVE_MLC -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -L/opt/kits/hpoj-0.7/ojlib -L/opt/kits/hpoj-0.7/ptal -fPIC -c -o ptal-mlc.o-shared ptal-mlc.c ptal-mlc.c: In function `ptalMlcDeviceConstructor': ptal-mlc.c:96: warning: unused variable `cbd' ptal-mlc.c:95: warning: unused variable `dev' ptal-mlc.c: In function `ptalMlcDeviceDump': ptal-mlc.c:102: warning: unused variable `dev' ptal-mlc.c: In function `ptalMlcChannelConstructor': ptal-mlc.c:109: warning: unused variable `dev' ptal-mlc.c: In function `ptalMlcChannelDump': ptal-mlc.c:115: warning: unused variable `chan' ptal-mlc.c: In function `ptalMlcPmlGet': ptal-mlc.c:200: warning: control reaches end of non-void function ptal-mlc.c: In function `ptalMlcPmlGetNext': ptal-mlc.c:204: warning: control reaches end of non-void function ptal-mlc.c: In function `ptalMlcPmlSet': ptal-mlc.c:208: warning: control reaches end of non-void function cc -O1 -Wall -g -DHAVE_MLC -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -L/opt/kits/hpoj-0.7/ojlib -L/opt/kits/hpoj-0.7/ptal -fPIC -c -o ptal-providers.o-shared ptal-providers.c cc -O1 -Wall -g -DHAVE_MLC -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -L/opt/kits/hpoj-0.7/ojlib -L/opt/kits/hpoj-0.7/ptal -shared -Wl,-soname,libptal.so.0 -o libptal.so.0.1 ptal.o-shared ptal-hpjd.o-shared ptal-mlc.o-shared ptal-providers.o-shared -lc ln -sf libptal.so.0.1 libptal.so.0 ln -sf libptal.so.0.1 libptal.so cc -O1 -Wall -g -DHAVE_MLC -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -L/opt/kits/hpoj-0.7/ojlib -L/opt/kits/hpoj-0.7/ptal -c -o ptal-connect.o ptal-connect.c cc -O1 -Wall -g -DHAVE_MLC -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -L/opt/kits/hpoj-0.7/ojlib -L/opt/kits/hpoj-0.7/ptal -lptal -o ptal-connect ptal-connect.o ln -sf ptal-connect ptal-print cc -O1 -Wall -g -DHAVE_MLC -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -L/opt/kits/hpoj-0.7/ojlib -L/opt/kits/hpoj-0.7/ptal -c -o ptal-printd.o ptal-printd.c cc -O1 -Wall -g -DHAVE_MLC -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -L/opt/kits/hpoj-0.7/ojlib -L/opt/kits/hpoj-0.7/ptal -lptal -o ptal-printd ptal-printd.o make[1]: Verlassen des Verzeichnisses Verzeichnis =BB/opt/kits/hpoj-0.7/ptal=AB ieee12844 make[1]: Wechsel in das Verzeichnis Verzeichnis =BB/opt/kits/hpoj-0.7/ieee12844=AB >ieee12844.ver gcc -E -O -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -Wall -Wstrict-prototypes -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -D__GENKSYMS__ ieee12844.c | \ /sbin/genksyms -k 2.4.2 >ieee12844.ver gcc -O -I/opt/kits/hpoj-0.7/include -I/opt/kits/hpoj-0.7/ptal -I/usr/src/linux-2.4.2/include -Wall -Wstrict-prototypes -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -c ieee12844pp.c ieee12844pp.c: In function `ecp_fwd_to_rev': ieee12844pp.c:549: warning: implicit declaration of function `parport_write_econtrol' ieee12844pp.c:553: `PARPORT_CONTROL_DIRECTION' undeclared (first use in this function) ieee12844pp.c:553: (Each undeclared identifier is reported only once ieee12844pp.c:553: for each function it appears in.) ieee12844pp.c: In function `ecp_rev_to_fwd': ieee12844pp.c:644: `PARPORT_CONTROL_DIRECTION' undeclared (first use in this function) ieee12844pp.c: In function `mlcpp_intr': ieee12844pp.c:1199: `tq_scheduler' undeclared (first use in this function) make[1]: *** [ieee12844pp.o] Fehler 1 make[1]: Verlassen des Verzeichnisses Verzeichnis =BB/opt/kits/hpoj-0.7/ieee12844=ABmake: *** [release] Fehler 2 [ruffieux@locarno hpoj-0.7]$=20 --=20 \\\|/// \ ~ ~ / (\ @ @ /) --oOOO--(_)--OOOo---------------------------------- Heinz Ruffieux Home: +41 26 670 40 85 Dipl. El.-Ing HTL Mobile: +41 79 353 62 23=20 Hintere Gasse 2 CH-3285 Galmiz / Switzerland ooO -----( )--Ooo------------------------------------ |
From: Heinz R. <ruf...@ya...> - 2001-05-16 21:12:16
|
Hi I just downloaded the hpoj-0.7 package and tried to compile it on my RH7.1 box (Kernel 2.4.2). It didn't work. After this I read the following statment in the downloaded INSTALL file: BUG: The kernel drivers currently fail to compile under kernel 2.4. They also do not work with SMP (any kernel version). These two problems are being worked on. When I'm reading the same file online on sourceforge, I can not find this statement. So my question is, can it be compiled under 2.4.2? Thanks a lot Heinz -- \\\|/// \ ~ ~ / (\ @ @ /) --oOOO--(_)--OOOo---------------------------------- Heinz Ruffieux Home: +41 26 670 40 85 Dipl. El.-Ing HTL Mobile: +41 79 353 62 23 Hintere Gasse 2 CH-3285 Galmiz / Switzerland ooO -----( )--Ooo------------------------------------ |
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2001-05-16 19:43:41
|
Hi, Joe. Joe Piolunek wrote: > I also scanned a narrow page > to see if it > would print at correct size on wider paper. It still printed > smaller than the > original. I then scanned a page with the -length option > artificially small. > There was a small size gain in the copy, but not enough. Even if you scan a narrow document, you still end up with a full-width image, because the scanner doesn't know how wide the page is. That's why I suggested cropping the image, which you did next: > Using gimp, I cropped to the photo and printed the resulting > image from the > command line. Even though gimp reported the image as being > about 3.5 x 5 in., > when it printed, something automatically scaled it up to fit > nearly the whole > page. So I guess that's the culprit. What happens if you load the image in Netscape or Gimp and print it there, where presumably there is no fit-to-page? > There have > been strings of related error messages shown during the OS > shutdown process, > but I haven't had a chance to copy them down. They typically > seem to appear > when the printer is power cycled while the hpoj daemons are running. Error messages are normal when communication is lost, such as when the peripheral is power cycled. Hopefully you never need to restart the daemons to get things working again. If you ever get a "FATAL ERROR" message, that's bad, because it means that ptal-mlcd died. > I got a different LCD error message today after a failed scan: > "SYSTEM ERROR9364". I added it to the list to look into. I also add a link on the webpage to a list of error codes. > As with the other "system error" mesg I reported earlier, a > power cycle and > clock reset allowed the printer to scan again. > > When the 600 is started or restarted without one of the > system errors having > occurred, the clock does not need to be set in order to scan. So does the clock really "need to be set in order to scan", or just to get rid of the message on the front panel telling you to set the clock? David |
From: Joe P. <joe...@sn...> - 2001-05-16 19:10:16
|
On Tuesday 15 May 2001 04:21, David Paschal wrote: > > > The size of the printed "photo" in the page was always about 80% of the > > original at '-res 300'. I haven't rechecked the lower resolution settings > > yet. > > It would be interesting to try copying at all the resolutions, keeping > everything else constant. It's possible that some auto-scaling is > happening somewhere in the print pipeline. I'm not sure why I saw an image that was too large before. At all of the supported resolutions, the 600 prints scanned pages at @80% of original size. Thinking that maybe the software was scaling down the jpeg to be able to print it all between the margins, I set up a new print queue with margins set to '0'. It made no difference. I also scanned a narrow page to see if it would print at correct size on wider paper. It still printed smaller than the original. I then scanned a page with the -length option artificially small. There was a small size gain in the copy, but not enough. > Since you're copying a photo, you could also try stripping out the empty > part of the image to see if the remaining image prints without > auto-reduction. Using gimp, I cropped to the photo and printed the resulting image from the command line. Even though gimp reported the image as being about 3.5 x 5 in., when it printed, something automatically scaled it up to fit nearly the whole page. > > > Several times when trying to scan I got the message > > "ptalChannel Read returns 0!" > > "Broken pipe" > > Restarting the scan usually worked. > > Did ptal-mlcd report any errors? Nothing was reported at the command line or in /var/log/messages. There have been strings of related error messages shown during the OS shutdown process, but I haven't had a chance to copy them down. They typically seem to appear when the printer is power cycled while the hpoj daemons are running. I got a different LCD error message today after a failed scan: "SYSTEM ERROR9364". As with the other "system error" mesg I reported earlier, a power cycle and clock reset allowed the printer to scan again. When the 600 is started or restarted without one of the system errors having occurred, the clock does not need to be set in order to scan. -- Joe |
From: Tim W. <tw...@re...> - 2001-05-16 16:04:31
|
On Wed, May 16, 2001 at 02:09:29AM -0700, David Paschal wrote: > Hi, Bob. >=20 > Bob Paddock wrote: > > First of all can some one tell me how to STOP parport from loading at b= oot=20 > > time? I've done a recursive grep of the /etc directory and don't find = any=20 > > thing that looks relevant. dmesg shows winbond and parport are loadin= g, see=20 > > end of this message. > In my experience that's easier said than done. If you're just > trying to keep parport from interfering with ptal-mlcd, then I would > suggest adding the "-device /dev/lp0" switch to the ptal-mlcd > command line. That causes ptal-mlcd to keep that device open while > it's using the parallel port for two purposes: to get the drivers > loaded so the driver interference gets out of the way, and to > prevent other processes from opening /dev/lp0 and causing problems. Is putting 'alias parport off' in /etc/modules.conf no good? > On the other hand, if these drivers are compiled into the kernel (as > opposed to being dynamically loaded modules), then the only way to > get rid of them is by reconfiguring them as modules (or disabled) > and recompiling the kernel. Or booting with 'parport=3D0'? Tim. */ |
From: <pa...@rc...> - 2001-05-16 09:12:40
|
Hi, Bob. Bob Paddock wrote: > First of all can some one tell me how to STOP parport from loading at boot > time? I've done a recursive grep of the /etc directory and don't find any > thing that looks relevant. dmesg shows winbond and parport are loading, see > end of this message. In my experience that's easier said than done. If you're just trying to keep parport from interfering with ptal-mlcd, then I would suggest adding the "-device /dev/lp0" switch to the ptal-mlcd command line. That causes ptal-mlcd to keep that device open while it's using the parallel port for two purposes: to get the drivers loaded so the driver interference gets out of the way, and to prevent other processes from opening /dev/lp0 and causing problems. On the other hand, if these drivers are compiled into the kernel (as opposed to being dynamically loaded modules), then the only way to get rid of them is by reconfiguring them as modules (or disabled) and recompiling the kernel. However, as I said above, the "-device /dev/lp0" switch should make this unnecessary. > Next how do I set up a Queue? The docs refere to the Red Hat printtool. I > don't know if that is the same as the Mandrake printtool or not? At any rate > this 'printtool' wants to be helpful and provide a menu of drivers. I don't > see where to enter the required /dev/ptal-printd/mlc_par_hpoj. You would enter this wherever you would traditionally enter "/dev/lp0" to indicate which device to open to send the print job. With RedHat printtool, when adding a local print queue there's a main screen where you select the queue name and "Printer Device" (which is where you would enter "/dev/ptal-printd/mlc_par_hpoj" or whatever). There is a button that you can click to set up a print filter, which is where you get the list of ghostscript drivers. Of course, this may or may not be the same with Mandrake's printtool. David |
From: Bob P. <bpa...@cs...> - 2001-05-15 23:08:45
|
I have a HP710 connected to my local parallel port and I'm runing Mandrake 8.0, using CUPS. I've build all of the hpoj and installed all of the hpoj related items but I'm having trouble getting them working. Hope some one here can point me in the correct direction. First of all can some one tell me how to STOP parport from loading at boot time? I've done a recursive grep of the /etc directory and don't find any thing that looks relevant. dmesg shows winbond and parport are loading, see end of this message. Next how do I set up a Queue? The docs refere to the Red Hat printtool. I don't know if that is the same as the Mandrake printtool or not? At any rate this 'printtool' wants to be helpful and provide a menu of drivers. I don't see where to enter the required /dev/ptal-printd/mlc_par_hpoj. Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ... SMSC Super-IO detection, now testing Ports 2F0, 370 ... 0x378: FIFO is 16 bytes 0x378: writeIntrThreshold is 16 0x378: readIntrThreshold is 16 0x378: PWord is 8 bits 0x378: Interrupts are ISA-Pulses 0x378: ECP port cfgA=0x10 cfgB=0x40 0x378: ECP settings irq=<none or set by other means> dma=<none or set by other means> parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,COMPAT,ECP] parport0: irq 7 detected parport0: cpp_daisy: aa5500ff(98) parport0: assign_addrs: aa5500ff(98) parport0: Printer, Hewlett-Packard OfficeJet Series 700 |
From: Carlos P. <cp...@ro...> - 2001-05-15 18:00:07
|
hi, i tried configuring the printer with parallel port with redhat 7.1 and it works beautifully - gave no problems at all compiling or installing. i only tried printing some on-page pdf. now the original intention, though, was to connect it via a usb port to take advantage of the speed, especially when scanning. i am still having the same kind of trouble with it, but provide more information below. David Paschal <pa...@rc...> wrote: > Carlos Puchol wrote: > > hi, i tried installing hpoj on my newly > > reinstalled redhat 7.1 printer server, > > this time i connected the officejet g55 > > via the usb port. > > > > rh7.1 has a 2.4.2-2 kernel running. i compiled hpoj > > from cvs as of approx. Thu May 3 05:26:39 UTC 2001, > > and all seems to compile and install fine. > > the messages file had said (while booting) the following > > abou usb: > ... > > May 3 04:58:40 tcb kernel: usb.c: registered new driver usblp > > May 3 04:58:40 tcb kernel: printer.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 > > > > i then ran: > > > > ptal-printd mlc:usb:0 -like /dev/lp0 > > ptal-mlcd usb:0 -device /dev/usb/lp0 > > > > with this, i try again: > > > > hpoj# ptal-devid mlc:usb:0 > > > > ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:184, dev=<usb:0>, pid=4179, errno=11 > > Reply timer popped on port=0, count=1! > ... > > note that it takes about 5 to 10 seconds for the message to show up. > > >From looking at your debug output, it appears that the InitReply from the > peripheral is getting lost. What kind of USB hardware do you have? On i have the following, in the motheboard: 00:04.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) 00:04.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) > Since there are currently two UHCI drivers in the kernel, you could try the > other one (uhci instead of usb-uhci). as you suggested, i tried both the usb-uhci (the onle that originally loaded up) and the other one, the uhci. unfortunately, i am still getting the same problem as before: =========================================================================== ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:184, dev=<usb:0>, pid=16974, errno=11 Reply timer popped on port=0, count=1! ptal-mlcd: ERROR at ExMgr.cpp:859, dev=<usb:0>, pid=16974, errno=11 exClose(reason=0x3002) ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:184, dev=<usb:0>, pid=16974, errno=11 Reply timer popped on port=0, count=1! ptal-mlcd: ERROR at ExMgr.cpp:859, dev=<usb:0>, pid=16974, errno=11 exClose(reason=0x3002) ptalChannelOpen(chan=0x0804AFD8): provider failed open! ptal-printd(mlc:usb:0): ptalChannelOpen failed! Will delay and retry. ... [over and over] =========================================================================== now i thought i may not have the recommended printer.c. redhat 7.1, judging by the sources in the kernel-source rpm, has the following printer.c: /* * printer.c Version 0.6 * * Copyright (c) 1999 Michael Gee <mi...@li...> * Copyright (c) 1999 Pavel Machek <pa...@su...> * Copyright (c) 2000 Randy Dunlap <ran...@in...> * Copyright (c) 2000 Vojtech Pavlik <vo...@su...> * * USB Printer Device Class driver for USB printers and printer cables * * Sponsored by SuSE * * ChangeLog: * v0.1 - thorough cleaning, URBification, almost a rewrite * v0.2 - some more cleanups * v0.3 - cleaner again, waitqueue fixes * v0.4 - fixes in unidirectional mode * v0.5 - add DEVICE_ID string support * v0.6 - never time out * v0.? - fixed bulk-IN read and poll (David Paschal, pa...@rc...) */ which is newer than the one in the web site. > the motherboard, or on a PCI card? I've had trouble with defective > built-in USB host controllers before, which I solved by adding a PCI USB > card. mine is in the motherboard. hmmm, i may have to buy a usb card ... > Has anybody else had any success of failure with using ptal-mlcd with USB > on kernel 2.4? i have not heard of any sucess stories in the list ... :-( > I haven't tried it yet, but I've got a fresh RedHat 7.1 on > a spare PC at work which I will play around with at some point. let me know how it goes! now, trying to debug a little, it seems like the messages have stopped. the other thing i notice is that the uhci is unused, though /dev/usb/lp0 and /dev/ptal-printd/mlc_usb_0 is open. not sure when, how or why... bash# lsof | grep lp | grep usb ptal-mlcd 16974 root 7u CHR 180,0 740868 /dev/usb/lp0 lpd 17108 root 5w FIFO 3,1 709693 /dev/ptal-printd/mlc_usb_0 mf_wrappe 17109 lp 1w FIFO 3,1 709693 /dev/ptal-printd/mlc_usb_0 magicfilt 17113 lp 1w FIFO 3,1 709693 /dev/ptal-printd/mlc_usb_0 bash# ps auxww | grep lp root 16972 0.0 0.1 1384 460 pts/0 S 11:39 0:00 ptal-printd mlc:usb:0 -like /dev/lp0 root 16974 0.5 0.1 1884 708 pts/0 S 11:39 0:25 ptal-mlcd usb:0 -device /dev/usb/lp0 lp 17103 0.0 0.3 2776 1156 ? S 12:07 0:00 lpd Waiting lp 17107 0.0 0.3 2800 1344 ? S 12:07 0:00 lpd (Server) 'lp' lp 17108 0.0 0.3 2820 1404 ? S 12:07 0:00 lpd (Worker - Print) 'lp' lp 17109 0.0 0.2 1924 888 ? S 12:07 0:00 /bin/bash /usr/share/printconf/mf_wrapper -Acpg@lprserver+217 -CA -Ff -Hlprserver.domain.com -N/tmp/AcroP7rvJb -Plp -Qlp -aacct -b136594 -d/var/spool/lpd/lp -edfA217lprserver.domain.com -f/tmp/AcroP7rvJb -hlprserver.domain.com -j217 -kcfA217lprserver.domain.com -l66 -ncpg -sstatus -t2001-05-15-12:07:57.000 -w80 -x0 -y0 acct lp 17113 0.0 0.2 1640 800 ? S 12:07 0:00 /usr/bin/magicfilter-t /tmp/printconf.pGEv2A -Acpg@lprserver+217 -CA -Ff -Hlprserver.domain.com -N/tmp/AcroP7rvJb -Plp -Qlp -aacct -b136594 -d/var/spool/lpd/lp -edfA217lprserver.domain.com -f/tmp/AcroP7rvJb -hlprserver.domain.com -j217 -kcfA217lprserver.domain.com -l66 -ncpg -sstatus -t2001-05-15-12:07:57.000 -w80 -x0 -y0 acct root 17164 0.0 0.1 1624 600 pts/0 R 12:51 0:00 grep lp bash# lsmod Module Size Used by ide-cd 26848 0 (autoclean) cdrom 27232 0 (autoclean) [ide-cd] uhci 22144 0 (unused) nfs 79008 2 (autoclean) nfsd 69696 8 (autoclean) lockd 52464 1 (autoclean) [nfs nfsd] sunrpc 61328 1 (autoclean) [nfs nfsd lockd] tdfx 58640 0 agpgart 23392 1 printer 4928 1 autofs 11264 1 (autoclean) tulip 38544 1 (autoclean) usbcore 49664 1 [uhci printer] bash# lpq Printer: lp@lprserver Queue: 1 printable job Server: pid 17107 active Unspooler: pid 17108 active Status: processing 'dfA217lprserver.domain.com', size 136594, format 'f', IF filter 'mf_wrapper' at 12:07:57.600 Rank Owner/ID Class Job Files Size Time active cpg@lprserver+217 A 217 /tmp/AcroP7rvJb 136594 11:43:17 bash# again, all i did was bash# ptal-printd mlc:usb:0 -like /dev/lp0 bash# ptal-mlcd usb:0 -device /dev/usb/lp0 bash# /etc/init.d/lpd restart Stopping lpd: [ OK ] Starting lpd: [ OK ] bash# any more ideas? (aside from "go by a decent usb controller" :-) thanks, -c |
From: awanita <aw...@aw...> - 2001-05-15 12:00:34
|
Thanks for getting back to me. The answers to your questions are as follows: Our operating systems is Windows Me, the only steps I have taken so far are installing the stupid thing and checking all the print setup options. I don't know what print driver though. This may be the problem. Howeverm wouldn't it have come on the installation disc? You suggested I may have Netscape, I don't. I use Microsoft 5.5. Please let me know what to do to fix the problem. It has never printed in color, but it use to print email and web pages in color. Now it doesn't even do that much. Lost..., Cathy |
From: <pa...@rc...> - 2001-05-15 08:27:35
|
Allen Barnett wrote: > I came up with a recipe for adding the ability to use the HP inkjet > drivers (http://sourceforge.net/project/showfiles.php?group_id=16846) > with RedHat 7.1's printing system. If anyone is interested, send me > e-mail and I'll forward you a copy. > > Because it requires modifying several system files, I'm leary of just > posting it. Are there standard disclaimers I should append to it? Hi, Allen. If you don't want to publicly post it yet, then you can send it to both of my e-mail addresses as well as to "lin...@hp...". I'm sure the hpinkjet people would be interested in it as well, although they may already be working on RedHat 7.1 support. David |
From: <pa...@rc...> - 2001-05-15 08:24:27
|
Hi, Joe. Joe Piolunek wrote: > When trying to scan using the option '-o out.pnm', the pnm option seemed to > be ignored. ptal-hp displayed this message - "Saving in JPEG instead of PNM > format". That's because the OfficeJet 600, 700, T, and PSC 300 series all insist on JPEG compression with grayscale and color scans, so unfortunately there's no choice. ptal-hp does no decompression or image processing. It just saves the image data to a file and in some cases supplies or modifies JPEG headers. You can use the "-raw" or "-jpeg" switches to attempt to force one way or the other. However, the resulting image file won't be viewable if the device doesn't honor the request. The OfficeJet 500 series does some funny stuff in its JPEG compression that I don't know how to deal with, but fortunately it supports raw grayscale scanning, unlike the other OfficeJet models, so ptal-hp just uses that. The LaserJet 1100A, 1220, and 3200 support both raw and JPEG. By default ptal-hp uses raw, unless the "-jpeg" switch is given. > There was always a long wait between issuing the print command and the actual > start of printing. The file sizes were usually @5M and took @5 minutes to > begin printing. At such a high resolution there is a lot of work involved in JPEG->bitmap decompression, bitmap->PostScript->bitmap conversion, color correction, bitmap->PCL conversion, and transmission on the part of libjpeg, ghostscript, hpijs, ptal-printd, ptal-mlcd, and possibly other things. > I was quite pleased with the print quality after scanning a photo. I'm quite pleased that you're quite pleased. :-) It makes all of our (my and the hpinkjet people's) efforts worthwhile. > The size of the printed "photo" in the page was always about 80% of the > original at '-res 300'. I haven't rechecked the lower resolution settings yet. It would be interesting to try copying at all the resolutions, keeping everything else constant. It's possible that some auto-scaling is happening somewhere in the print pipeline. Since you're copying a photo, you could also try stripping out the empty part of the image to see if the remaining image prints without auto-reduction. > Several times when trying to scan I got the message > "ptalChannel Read returns 0!" > "Broken pipe" > Restarting the scan usually worked. Did ptal-mlcd report any errors? > The page I was scanning had been printed with this printer. When printing a > scanned photograph, the result is very high quality. Four feet away, the > print looks like a photo. I'm sure the hpinkjet people will be glad to hear this. > ]$ ptal-pml mlc:par:0 get 1.2.2.1.15 > 1.2.2.1.15 failed (status=0x83)! OK, so the sharpening coefficient is indeed unsupported on the 600 series. David |
From: <pa...@rc...> - 2001-05-15 07:43:46
|
f.r...@in... wrote: > IT WORKS!!! (Thanks David) > Loading the latest hpoj the printer works fine. > I could connect by "ptal-mlcd", tried out positively the tests and printed without problems. > I also installed SANE 1.0.4 and followed the SCAN-HOWTO procedure up to point 14 (hp.conf was modified as follow : ... > What is the problem now? > Thanks for the patience > Jimmi Hi, Jimmi. Scanning on the 700 series is not yet supported by SANE. For now, use the "ptal-hp" command-line application, which is part of the hpoj package in CVS. To do a color scan, just insert your document and run the command "ptal-hp mlc:par:0 scan". Append the "-help" switch for a list of options. I will make this clearer in the documentation eventually. David |
From: <f.r...@in...> - 2001-05-15 04:59:33
|
IT WORKS!!! (Thanks David) Loading the latest hpoj the printer works fine. I could connect by "ptal-mlcd", tried out positively the tests and printed without problems. I also installed SANE 1.0.4 and followed the SCAN-HOWTO procedure up to point 14 (hp.conf was modified as follow : # Parallel port connected MFP: mlc:par:0 option connect-ptal) and trying out the test I got the following : "[root@localhost hpoj]# scanimage -d hp:mlc:par:0 --test ptalChannelOpen(chan=3D0x080547C0): provider failed open! ptalChannelOpen(chan=3D0x080547C0): provider failed open! scanimage: open of device hp:mlc:par:0 failed: Error during device I/O [root@localhost hpoj]# scanimage --test ptalChannelOpen(chan=3D0x080547C0): provider failed open! scanimage: no SANE devices found" What is the problem now? Thanks for the patience Jimmi |
From: Joe P. <joe...@sn...> - 2001-05-15 00:27:11
|
On Friday 11 May 2001 04:23 am, David Paschal wrote: <...> > > The scanned pages never seem to display or print at the original > > size (either too small or too large). For pc-assisted copying, would > > automatic scaling be needed? > > If none of the device-native resolutions are quite right, then scaling > might need to be done. However, if the hpinkjet driver is really capable > of 300 dpi the way it claims, then it seems to me that you should be able > to scan and print at that resolution and not need any scaling. What > threshold of resolutions did you observe between too small and too large? I did several "scan and print from file" jobs using the same object each time. It was a 3-1/2 x 5 in. color photograph inside a 8-1/2 x 11-1/2 in. clear scan sleeve with white background. I tried the scan several times with different command line options, all with a scan resolution of '-res 300'. A '-length' option of 3600 works well with the scan sleeve at '-res 300'. A '-length' option of 3380 works well with US letter-size (8-1/2 x 11 in.) paper at '-res 300'. When trying to scan using the option '-o out.pnm', the pnm option seemed to be ignored. ptal-hp displayed this message - "Saving in JPEG instead of PNM format". I tried a scan with '-contrast 70'. The contrast seemed to be greater. There was always a long wait between issuing the print command and the actual start of printing. The file sizes were usually @5M and took @5 minutes to begin printing. I was quite pleased with the print quality after scanning a photo. The size of the printed "photo" in the page was always about 80% of the original at '-res 300'. I haven't rechecked the lower resolution settings yet. Several times when trying to scan I got the message "ptalChannel Read returns 0!" "Broken pipe" Restarting the scan usually worked. > > > The color scans always seem somewhat grainy, even at -res 200. My system > > doesn't handle color 300x300 scans well, so I haven't tried it again. > > I've scanned on many different devices in my testing but haven't been > paying much attention to the image quality. Here are some thoughts off the > top of my head: > > - Depending on what you're scanning, especially at a higher resolution > you might end up seeing the dithering that was used when the page was > originally printed. > The page I was scanning had been printed with this printer. When printing a scanned photograph, the result is very high quality. Four feet away, the print looks like a photo. > - There is a "sharpening coefficient" PML object on some models which may > make a difference. However, my sources indicate that it was first > supported on the PSC 300 series, which came out after the OfficeJet 600 > series. Try "ptal-pml mlc:par:0 get 1.2.2.1.15" and see if you get an > error back. If not, then try hacking a different value into "int > sharpeningCoefficient=0x37;" in ptal-hp, since I haven't yet made it > adjustable on the command line. ]$ ptal-pml mlc:par:0 get 1.2.2.1.15 1.2.2.1.15 failed (status=0x83)! -- Joe |
From: Allen B. <ba...@lo...> - 2001-05-14 21:20:48
|
I came up with a recipe for adding the ability to use the HP inkjet drivers (http://sourceforge.net/project/showfiles.php?group_id=16846) with RedHat 7.1's printing system. If anyone is interested, send me e-mail and I'll forward you a copy. Because it requires modifying several system files, I'm leary of just posting it. Are there standard disclaimers I should append to it? Allen |
From: awanita <aw...@aw...> - 2001-05-14 17:45:59
|
Thanks for getting back to me. The answers to your questions are as follows: Our operating systems is Windows Me, the only steps I have taken so far are installing the stupid thing and checking all the print setup options. I don't know what print driver though. This may be the problem. How do I install the driver? Wouldn't have come on the installation disc? You suggested I may have Netscape, I don't. I use Microsoft 5.5. Please let me know what to do to fix the problem. It has never printed in color, but it use to print email and web pages in color. Now it doesn't even do that much. Lost..., Cathy |
From: <pa...@rc...> - 2001-05-14 01:20:22
|
Joe Piolunek wrote: > The brackets are gone. > > I attached a tarball containing the two replacement files for xojpanel, and a > patch for xojpanel/Makefile.in . Thanks, it's checked in now. I made a few more changes to Makefile.in, including renaming xojpanel.moc.* to xojpanel-moc.*, rearranging the dependency lines (so that "all" is the default target), and making the indentation more consistent. It builds and runs fine. David |
From: Joe P. <joe...@sn...> - 2001-05-13 16:17:16
|
On Sunday 13 May 2001 05:48 am, David Paschal wrote: <..> > > I have the two new files (xojpanel.cpp, xojpanel.h) > > and a patch for Makefile.in ready to send, but before I do that, I'd like > > your input on the format of the titlebar text. The CVS version displays > > > > "OfficeJet Status: [ mlc:par:0 ]". > > > > I think it may look a little better without the brackets like this: > > > > "OfficeJet Status: mlc:par:0". Your opinion? > > It does look better (less cluttered) without the brackets IMO. > The brackets are gone. I attached a tarball containing the two replacement files for xojpanel, and a patch for xojpanel/Makefile.in . -- Joe |
From: <pa...@rc...> - 2001-05-13 09:51:27
|
Hi, Joe. Joe Piolunek wrote: > No problem with that. I have the two new files (xojpanel.cpp, xojpanel.h) and > a patch for Makefile.in ready to send, but before I do that, I'd like your > input on the format of the titlebar text. The CVS version displays > > "OfficeJet Status: [ mlc:par:0 ]". > > I think it may look a little better without the brackets like this: > > "OfficeJet Status: mlc:par:0". Your opinion? It does look better (less cluttered) without the brackets IMO. > About the 'xhpcontrol' app - I started a hand-coded (not qt designer) version > from scratch which so far has only a "HpcLcdView" widget in the window. > > I created the widget by separating out xojpanel's PTAL code from the LCD > display code and placing them in different classes. There is now a HpcLcdView > class and a HpcPTALdevice class. > > HpcLcdView is now a widget in itself that can be placed on any other widget. > It contains the whitespace-stripping, scrolling and display code. It does not > communicate with the peripheral, but will get the lcd messages from a > HpcPTALdevice object. > > HpcPTALdevice contains all of the device-communication code, and each > instance will hold information on a single PTAL device (current lcd messages, > configuration info, etc.). > > The HpcLcdView object is not yet able to get the lcd strings from the > HpcPTALdevice object, but they are both working otherwise. > > I have it building in hpoj/apps/xhpcontrol. > > Before I go too far with this, does it make sense? I think it's a good start, but it'll take more than this. I thought about it for a while and went through several different designs trying to figure out how to put it all together. (If nothing else, you might want to call the second class "HpcPtalDevice" to be consistent in capitalization with the first class, since LCD and PTAL are both acronyms.) I think we'll need the following classes: - PTAL device -- Contains the ptalDevice_t handle and any other per-device state. - Dialog display -- Manages the user interface widgets for a particular tabbed dialog box. - Dialog device (for lack of a better name) -- Contains the ptalPmlObject_t handles for a particular device needed by a particular dialog box display object. It could also contain methods to abstract the getting/setting of the PML objects, to be called by the dialog display class. - An application class to tie it all together. The application could be thought to contain lists of PTAL device and dialog box display classes, and a two-dimensional table of dialog device classes, where the row indices refer to the device and the column indices refer to the dialog display. At startup, the application would: - Load (via dlopen()) plugin libraries and lookup (via dlsym()) and call an init function with a well-known name. The init function would construct a dialog box display object, which would get added to the list, both the internal list and the visual tab list. - Call ptalInit(). - Read in PTAL device names from somewhere, construct device objects, and add them to the device list, both internally and visually. - For each device object and for each dialog display object, call a dialog display method that constructs a dialog device object, and place it in the right spot in the table. When a device name is clicked on (defaulting to the first one at startup), a method in the currently selected dialog display would be called with a pointer to the new dialog device object. The dialog display would query PML objects or whatever (or let the dialog device object do this) as needed and update the display. When a dialog display tab is clicked on, the previous dialog display would be told to hide itself, and the new dialog display would be enabled and given its dialog device pointer for the existing device, as described above. Although the above description is probably just scratching the surface, I think it provides a workable framework to get started. Let me know what you think. David |
From: <pa...@rc...> - 2001-05-13 09:51:27
|
Doug Kunzman wrote: > Hi, > > I have C2890A OfficeJet printer and if it would be helpful I am willing to > be a beta > tester for the driver. I am interested in knowing that if I can get it to > work will > I be able to print from a NT machine across my network to a linux based > print server > with C2890A connected and get reasonable output if we are lucky ? Hi, Doug. Does your model just say "OfficeJet" on the front, or "OfficeJet LX"? You're certainly welcome to try out the development code in CVS. First of all, run the ptal-mlcd daemon and see if you can run ptal-devid to get a device ID string. If you're able to get that far, then you should be able to set up printing according to PRINT-HOWTO. Since OfficeJets before the 500 series don't print in color, you may have to experiment to figure out what ghostscript DeskJet driver (perhaps DeskJet Plus) to use. Also try running "ptal-connect mlc:par:0 -socket 6" ("mlc:par:0" assuming you invoked ptal-mlcd with "par:0"), type a few lines of text, and see if they get echoed back to you. It died when I tried this on an OfficeJet 300 a while back, but I now suspect it to be related to another bug I've seen intermittently on newer models. If you see ptal-mlcd error messages about lookupChannel failures, then you could try invoking ptal-mlcd with the "-porttype spp" switch. Scanning is less likely to work right away. Pre-500-series OfficeJets also don't support scanning in anything other than 1-bit black&white (no 8-bit grayscale or 24-bit color), so even if it does work, the quality may not be very good except possibly for text and line drawings. In any case, if the hpoj software just won't work, or if all you really care about is printing anyway, then you can just bypass the hpoj software altogether and set it up just as you would any other printer, and configure Samba to share it with Windows clients. BTW, in the future when replying to messages (especially mailing list digests), please delete all the existing text that you're not specifically replying to. I had to scroll down many screens to find what you wrote. It would also be helpful to configure your mail software to put ">" at the beginning of quoted lines, as shown above. David |
From: Kunzman, D. <DKu...@Sk...> - 2001-05-11 20:38:41
|
-----Original Message----- From: hpo...@li... [mailto:hpo...@li...] Sent: Friday, May 11, 2001 8:02 PM To: hpo...@li... Subject: hpoj-devel digest, Vol 1 #197 - 8 msgs Send hpoj-devel mailing list submissions to hpo...@li... To subscribe or unsubscribe via the World Wide Web, visit http://lists.sourceforge.net/lists/listinfo/hpoj-devel or, via email, send a message with subject or body 'help' to hpo...@li... You can reach the person managing the list at hpo...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of hpoj-devel digest..." Today's Topics: 1. Re: ptal-hp scan changes (T series now supported!) (David Paschal) 2. Re: xojpanel changes (Alexander Zimmermann) 3. Re: Officejet G95 via Jetdirect questions (David Paschal) 4. Re: OfficeJet T45xi (David Paschal) 5. Re: xojpanel changes (David Paschal) 6. Re: Next stable release (David Paschal) 7. Re: xojpanel changes (Tim Waugh) 8. Re: xojpanel changes (Joe Piolunek) --__--__-- Message: 1 To: hpo...@li... Cc: pa...@rc... Subject: Re: [hpoj-devel] ptal-hp scan changes (T series now supported!) From: pa...@rc... (David Paschal) Date: Fri, 11 May 2001 01:23:30 -0700 Reply-To: hpo...@li... Hi, Joe. Joe Piolunek wrote: > I'm happy to see color scanning begin to work. ... > Some of the defaults work well. Using the command "ptal-hp mlc:par:0 scan > -length 1110" produced a 100x100 color scan that didn't quite match the size > of the original, but was close. > > The scanned pages never seem to display or print at the original > size (either too small or too large). For pc-assisted copying, would > automatic scaling be needed? If none of the device-native resolutions are quite right, then scaling might need to be done. However, if the hpinkjet driver is really capable of 300 dpi the way it claims, then it seems to me that you should be able to scan and print at that resolution and not need any scaling. What threshold of resolutions did you observe between too small and too large? > The color scans always seem somewhat grainy, even at -res 200. My system > doesn't handle color 300x300 scans well, so I haven't tried it again. I've scanned on many different devices in my testing but haven't been paying much attention to the image quality. Here are some thoughts off the top of my head: - Depending on what you're scanning, especially at a higher resolution you might end up seeing the dithering that was used when the page was originally printed. - It's possible that the scanning hardware on an older model like the 600 doesn't have quite as good clarity as a more recent model (but I don't know for sure). There might be some image processing that can be done in software to improve this, but IMO this is best left to dedicated IP tools like GIMP. Of course, a copy app might need to do something like this automatically. - There is a "sharpening coefficient" PML object on some models which may make a difference. However, my sources indicate that it was first supported on the PSC 300 series, which came out after the OfficeJet 600 series. Try "ptal-pml mlc:par:0 get 1.2.2.1.15" and see if you get an error back. If not, then try hacking a different value into "int sharpeningCoefficient=0x37;" in ptal-hp, since I haven't yet made it adjustable on the command line. - This probably isn't the right answer, but the scanner strip might be in need of cleaning. Just be careful not to damage anything if you try to clean it. > When trying to scan with "-res 200" , the printer often quits near the end of > the scan and displays the LCD message "SYSTEM ERROR2252". I think it also > happened once at -res 150. After power cycling the printer, it is able to > scan again, but only after resetting its clock. I used ptal-hp to do that. I've seen problems like this under certain circumstances. I'll need to research this to find out what's causing it. From your description it sounds like it's repeatable but doesn't happen every time. > When opening out.jpg in gimp, an error message often appears that is similar > to "Corrupt JPEG data: 8472 extraneous bytes before marker 0xd9". The number > of extraneous bytes varies, but the message always ends in '0xd9'. That's because the length you specified was too short, and it truncated the image. However, it's probably OK if you're not missing anything important at the end. David --__--__-- Message: 2 Date: Fri, 11 May 2001 10:53:27 +0200 (MEST) From: Alexander Zimmermann <Ale...@fm...> Subject: Re: [hpoj-devel] xojpanel changes To: hpo...@li... Reply-To: hpo...@li... On 10 May, Joe Piolunek wrote: > If as you reported earlier, the problem with using gcc-2.95.2 on your > system stems from incompatible libraries, I don't know what I can do > as a workaround. You probably can do nothing! And you also shouldn't care about it. I've got problems on my system only due to my pighead, because I don't like to use the "unready", unofficial development compiler gcc-2.96 shiped with RH 7.x. Keep your attention on more urgent things. -- Alexander --__--__-- Message: 3 To: hpo...@li... Cc: pa...@rc..., mj...@so... Subject: Re: [hpoj-devel] Officejet G95 via Jetdirect questions From: pa...@rc... (David Paschal) Date: Fri, 11 May 2001 01:54:04 -0700 Reply-To: hpo...@li... Michael Dikkema wrote: > Hi, I installed the hpoj software from CVS yesterday, and I haven't been > able to get anything working. The documentation mentions nearly nothing > about jetdirect. I can't figure out if I need ptal-mcld or just > ptal-printd or neither, considering the rm= line in printcap allows me to > print blank pages at least. Hi, Michael. I'll try to make all this clearer when I reorganize the documentation in the near future. The PRINT-HOWTO does mention JetDirect, including the "rm=" and "rp=" fields when you're not using RedHat printtool. You don't need either ptal-mlcd or ptal-printd. > I've also installed ghostscript with hpijs, but I can't figure out how > that fits in either. I'm not running redhat, nor do I have printtool. I > basically need the lines in printcap that are relevant to getting gs > working. At the moment, I'm not really sure how to do this without RedHat printtool, but you can probably gleam the necessary information out of the Linux Printing HOWTO (http://www.linuxprinting.org) and the hpijs documentation. Try searching around in the hpinkjet help forum and posting a help request if you don't find what you're looking for. I do know that for the OfficeJet G series you use the DJ9xx (not DJ9xxVIP) driver. Alternatively, you could start with the standard ghostscript cdj550 (DeskJet 550) driver, which you should be able to accomplish just from reading the Linux Printing HOWTO and using "rm=" and "rp=". Once you get that working, then you can move up to DJ9xx. David --__--__-- Message: 4 To: hpo...@li... Cc: pa...@rc... Subject: Re: [hpoj-devel] OfficeJet T45xi From: pa...@rc... (David Paschal) Date: Fri, 11 May 2001 02:03:38 -0700 Reply-To: hpo...@li... aw...@aw... wrote: > Hello. We have purchased the Office Jet T45xi and have never been able to > get it to print in color. What is wrong??? > > Thank You, > Cathy > Awanita Staff Hi, Cathy. Based on what you've said, I can't give you any useful advice. For starters it would be helpful to know the following things: - What sort of system (and operating system) are you using? - What steps have you taken so far to get you to where you are now? - What print driver are you using? Even though I have no information about your situation, one "gotcha" I can think of offhand is that if you're printing from Netscape, and possibly other applications, the Print dialog box has a selection for printing in color or black&white. So even if your printer is correctly configured to print in color, you can't print in color if your application isn't. David --__--__-- Message: 5 To: hpo...@li... Cc: pa...@rc... Subject: Re: [hpoj-devel] xojpanel changes From: pa...@rc... (David Paschal) Date: Fri, 11 May 2001 02:20:27 -0700 Reply-To: hpo...@li... Joe Piolunek wrote: > I made more changes to the xojpanel application that include the ability to > change the lcd text color, and many smaller code changes. The format of the > devicename string in the titlebar is a little different also. Hi, Joe. Thanks for your submission. I apologize I haven't had a chance to look at it yet, or at your earlier patch on May 3. I assume this supercedes the earlier patch, since you're including all the files. > I also changed some of the filenames to those that I think make more sense > based on their contents and the application. Makefile.in is modified to > correspond to the new filenames. While you're at it, I'm wondering if it would be feasible to combine the two .cpp files into a single xojpanel.cpp, and rename the .h file to xojpanel.h. It would make things a little more compact and less spread out. I don't know if there is some technical reason (i.e. Qt restriction) why the main() function needs to be in a separate file from the classes, but I suppose it was done that way originally to pave the way for something larger like the xhpcontrol application we've talked about. In the latter case, I think it's safe to combine xojpanel/*.cpp for now, because it may be better to write xhpcontrol from scratch anyway, using xojpanel as an example where appropriate. > I didn't know if I could make a reliable patch to send, so I tarred up all of > the modified files. I'm hoping filenames in CVS can be changed without > causing problems. It's a matter of removing the old files and adding the new. Of course, the old files aren't really deleted, but rather moved into the "attic" directory, which you can see in various parts of the codebase if you browse the CVS repository on the web. David --__--__-- Message: 6 To: hpo...@li... Cc: pa...@rc... Subject: Re: [hpoj-devel] Next stable release From: pa...@rc... (David Paschal) Date: Fri, 11 May 2001 02:35:47 -0700 Reply-To: hpo...@li... Rainer Dorsch wrote: > I just seen that OJ6xx scan support is in CVS. I am just wondering, when the > next stable release (0.8?) of hopj may be expected. Hi, Rainer. As you can see at http://hpoj.sourceforge.net/todo.shtml, there is still some functionality I need to implement and a number of robustness and usability issues I need to address before it's ready for another stable release (0.8). At the moment my working goal is around the end of July. I realize this is a much longer development/release cycle than that between the last three releases, but there's a lot of new code to stabilize. In the meantime, you're certainly welcome to try out the development code in CVS, especially if you're interested in trying out the new "ptal-hp scan" feature, which supports scanning on the OfficeJet 600 series, among other models. David --__--__-- Message: 7 Date: Fri, 11 May 2001 10:46:49 +0100 From: Tim Waugh <tw...@re...> To: hpo...@li... Subject: Re: [hpoj-devel] xojpanel changes Reply-To: hpo...@li... --Dxzxec4+BSbG6TGA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, May 11, 2001 at 10:53:27AM +0200, Alexander Zimmermann wrote: > because I don't like to use the "unready", unofficial development > compiler gcc-2.96 shiped with RH 7.x. If you know of bugs in the 2.96 compiler, please make sure they are filed in https://bugzilla.redhat.com/bugzilla so that they can be fixed (in 2.96 and in the 3.0 branch if the bug appears there too). Thanks, Tim. */ --Dxzxec4+BSbG6TGA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6+7UIONXnILZ4yVIRAp//AKCLOxiy0JKqwV2KhWPil8LBEJdhWACfbJCC yAt14oLe3nnBlsUnrj8fhc0= =WlmP -----END PGP SIGNATURE----- --Dxzxec4+BSbG6TGA-- --__--__-- Message: 8 From: Joe Piolunek <joe...@sn...> To: hpo...@li... Subject: Re: [hpoj-devel] xojpanel changes Date: Fri, 11 May 2001 13:13:53 -0400 Reply-To: hpo...@li... On Friday 11 May 2001 05:20 am, David Paschal wrote: <...> > > Hi, Joe. Thanks for your submission. I apologize I haven't had a chance > to look at it yet, or at your earlier patch on May 3. I assume this > supercedes the earlier patch, since you're including all the files. I didn't make it clear at the time, but that patch was meant for Alexander to try. I was planning to send a later patch intended for CVS. > While you're at it, I'm wondering if it would be feasible to combine the > two .cpp files into a single xojpanel.cpp, and rename the .h file to > xojpanel.h. It would make things a little more compact and less spread out. > I don't know if there is some technical reason (i.e. Qt restriction) why > the main() function needs to be in a separate file from the classes, but I > suppose it was done that way originally to pave the way for something > larger like the xhpcontrol application we've talked about. In the latter > case, I think it's safe to combine xojpanel/*.cpp for now, because it may > be better to write xhpcontrol from scratch anyway, using xojpanel as an > example where appropriate. Hi, I have C2890A OfficeJet printer and if it would be helpful I am willing to be a beta tester for the driver. I am interested in knowing that if I can get it to work will I be able to print from a NT machine across my network to a linux based print server with C2890A connected and get reasonable output if we are lucky ? Doug Kunzman dku...@sk... |
From: Joe P. <joe...@sn...> - 2001-05-11 17:14:45
|
On Friday 11 May 2001 05:20 am, David Paschal wrote: <...> > > Hi, Joe. Thanks for your submission. I apologize I haven't had a chance > to look at it yet, or at your earlier patch on May 3. I assume this > supercedes the earlier patch, since you're including all the files. I didn't make it clear at the time, but that patch was meant for Alexander to try. I was planning to send a later patch intended for CVS. > While you're at it, I'm wondering if it would be feasible to combine the > two .cpp files into a single xojpanel.cpp, and rename the .h file to > xojpanel.h. It would make things a little more compact and less spread out. > I don't know if there is some technical reason (i.e. Qt restriction) why > the main() function needs to be in a separate file from the classes, but I > suppose it was done that way originally to pave the way for something > larger like the xhpcontrol application we've talked about. In the latter > case, I think it's safe to combine xojpanel/*.cpp for now, because it may > be better to write xhpcontrol from scratch anyway, using xojpanel as an > example where appropriate. > No problem with that. I have the two new files (xojpanel.cpp, xojpanel.h) and a patch for Makefile.in ready to send, but before I do that, I'd like your input on the format of the titlebar text. The CVS version displays "OfficeJet Status: [ mlc:par:0 ]". I think it may look a little better without the brackets like this: "OfficeJet Status: mlc:par:0". Your opinion? About the 'xhpcontrol' app - I started a hand-coded (not qt designer) version from scratch which so far has only a "HpcLcdView" widget in the window. I created the widget by separating out xojpanel's PTAL code from the LCD display code and placing them in different classes. There is now a HpcLcdView class and a HpcPTALdevice class. HpcLcdView is now a widget in itself that can be placed on any other widget. It contains the whitespace-stripping, scrolling and display code. It does not communicate with the peripheral, but will get the lcd messages from a HpcPTALdevice object. HpcPTALdevice contains all of the device-communication code, and each instance will hold information on a single PTAL device (current lcd messages, configuration info, etc.). The HpcLcdView object is not yet able to get the lcd strings from the HpcPTALdevice object, but they are both working otherwise. I have it building in hpoj/apps/xhpcontrol. Before I go too far with this, does it make sense? -- Joe |