Menu
▾
▴
hpoj-devel — HPOJ development/support list
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: dau <kar...@fe...> - 2001-06-30 21:02:10
|
Hallo,
Thank you Burkhard Kohl for your help.
The problem was :
Yast2 , and my way to see things, and do them like I saw , I'v done
before .
Not all Scr where installted and so the 'build' wasn't. After a few
houres, I stept to restart my Installation ( even it was a brand new
Installation )
But now, having a better installt SuSE 7.2 , and doing things by
reading,understanding and then doing .
I saw that the project has problems with ieee12844 on Kernl 2.4
Is this still reel ?
I tring now Kernl 2.2.19, but no doesn't work .
(see hpoj_on_2..2.19)
where to i wrong
I compiled old src, to find out a
hpoj-0.4 OK
hpoj-0.5 OK
and hpoj-0.6 same as hpoj-0.7
make install installes on /usr/local/lib
libptal.so (a symlink to libptal.so.0.1)
libptal.so.0 (a symlink to libptal.so.0.1)
libptal.so.0.1
make don't touche the other Makefile's
Charlie
|
|
From: Bob P. <bpa...@cs...> - 2001-06-30 15:14:15
|
> You could use the cdj550 (DeskJet 550) driver that comes standard with > ghostscript. However, for the best print quality you should also install > the latest version of the hpinkjet driver (currently 0.97). I've been using the 550 driver with my OJ710. I didn't see 710 listed in hpinkjet, any reason I should switch? I've never been able to get GhostScript to build from source. Always get some kind of error about unknow size of limit in zdev some thing or other. |
|
From: Joe P. <joe...@sn...> - 2001-06-30 05:27:53
|
David: I have some code available for an xhpcontrol app. It looks somewhat like what you last requested (sorry it took so long to respond), but does not yet have any useful abilities. It can be downloaded from my site at http://pages.cthome.net/jsp/hpoj-linux-gui/index.html . There is also a patch for hpoj/configure.in that will allow the app to be built under hpoj/apps/ . Some of the files / classes are just skeletons, but there is enough code to create a bare framework. There are many parts of the application that need a more experienced coder than me. I can do the "grunt work" of adding the many needed widgets, but the file i/o, plugin architecture, device communication, etc. should be handled by someone with more experience in those areas. There are also some areas involving Qt that I'm not yet familiar with. If someone wants to and has the ability to help with any of it, It would be fine with me. The package probably isn't ready to be added to the hpoj module in CVS. Would it be a good idea to temporarily add it to the project as a separate CVS module? Can that be done? I included in the tarball some documentation generated by Doxygen. It wouldn't necessarily be useful to keep the docs in the project, but having some extra documentation may help potential contributors understand the application a little quicker / better. I'm not sure which versions of Qt will be necessary to build xhpcontrol. Versions below 2.0 won't work. It probably would be difficult to make the application compatible with 1.x.x. I don't think it would be worth the trouble. I am unable to use any 2.x.x version other than 2.3.0+ on my system, so if someone with an early version (2.0.1 ?) installed and working can test the build, it would be very helpful. -- Joe |
|
From: Joe P. <joe...@sn...> - 2001-06-30 05:13:36
|
On Wednesday 27 June 2001 08:22 am, David Paschal wrote: > Hi, > > I just added the capability for "ptal-hp scan" to auto-detect the image > length/height even in situations where the device doesn't report it. > This means the end of "corrupt JPEG data" errors and oversized images. > The "-length" switch is still supported if you really want to override > the image height, and it now also supports decreasing or increasing the > height if you put a plus or minus in front of the number. I updated > SCAN-HOWTO to reflect these changes. It seems to work OK. It certainly makes scanning easier. -- Joe |
|
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2001-06-30 03:09:08
|
Steve Miller wrote: > In searching for printer drivers while shopping for a > Linux-compatible printer, I stumbled across your project. If > I could get my OfficeJet 600 to work, I could solve my > printer problems. I run SuSE 7.1 with kernel 2.4. I have the > 0.7 version of the HPOJ driver and the patch mentioned on the > site. Maybe I am not too swift, but how do I use the patch? > Am I patching the kernel, its source, or a Makefile? Hi, Steve. The patch is actually for the files in the hpoj-0.7/ieee12844 directory. I just added an explanaton on the TODO web page of how to apply the patch. > Once > that is done, is installing 0.7 enough or do I also need to > install the 0.96 version of the inkjet driver? You could use the cdj550 (DeskJet 550) driver that comes standard with ghostscript. However, for the best print quality you should also install the latest version of the hpinkjet driver (currently 0.97). hpoj-0.7 doesn't support scanning on your model. If you want scanning support right away, then you can try out the development (unstable) code in CVS. Around the beginning of August I plan to release version 0.8, which will also incorporate this functionality. > I tried to > find a FAQ, but to no avail. There's no mention of hpinkjet in the 0.7 documentation because it hadn't been released by the time I released 0.7. I haven't yet updated this in CVS, but I'll do it before 0.8. David |
|
From: BEN M. <ben...@us...> - 2001-06-29 22:04:37
|
I thought I would post this to help others having problems. This is comi=
ng
from memory as I'm at work so feel free to correct any problems you see. =
Also
the hpinkjet code is not in Debian yet so I am using the gimp print drive=
rs
for now. The maintainer hopes to have this included sometime soon.
First, my setup. I use a fairly regularly updated Debian unstable. cust=
om
compile of kernel 2.4.5. I have an G55 with a USB connection. I have th=
e CVS
of hpoj. It may be slightly out of date but that shouldn't matter for th=
is.
Here are the steps I followed.
1) Follow the INSTALL doc and make sure that ptal-connect is working
and you can print basic text files.
2) I then grabbed the following packages: gimp1.2-print, =
cupsys-driver-gimpprint, cupsys, and maybe cupsys-client
3) In your favorite graphical browser(not sure if this works with =
lynx, etc...) go to http://localhost:631
4) Go to the administration tab and login as root when prompted. You=
may be able to use a different user depending on the permissions =
you have set up
5) Now add a new printer. Use the following options
a)Fill in whatever you want for the name, location, etc fields
b)Disk file, then use file:/dev/ptal-printd/mlc_usb_0
c)HP
d)And then the gimp print driver for the 900 series(this may vary=
if you are using a different printer)
e)Use your common sense(or ask) on any other stuff but I think
those were the only ones
6) Restart cupsys by running, as root, "/etc/init-d/cupsys restart"
7) Try printing a test page and hope it works.
I got this working basically by messing around for awhile. If there are =
any
problems, missing packages, typos, or suggestions for improvement please =
let
me know. Also if you do use this and find it useful let me know. If the=
re is
enough interest I would be willing to clean it up, formalize it, and send=
it
to David for inclusion with the package.
Hope you enjoy it,
Ben
____________________________________________________________________
Get free email and a permanent address at http://www.amexmail.com/?A=3D1
|
|
From: Steve M. <ste...@my...> - 2001-06-29 16:56:09
|
Hi, In searching for printer drivers while shopping for a Linux-compatible printer, I stumbled across your project. If I could get my OfficeJet 600 to work, I could solve my printer problems. I run SuSE 7.1 with kernel 2.4. I have the 0.7 version of the HPOJ driver and the patch mentioned on the site. Maybe I am not too swift, but how do I use the patch? Am I patching the kernel, its source, or a Makefile? Once that is done, is installing 0.7 enough or do I also need to install the 0.96 version of the inkjet driver? I tried to find a FAQ, but to no avail. Thanks. Steve ------------------------------------------------------------ --== Sent via Deja.com ==-- http://www.deja.com/ |
|
From: <pa...@rc...> - 2001-06-27 12:21:24
|
Hi, I just added the capability for "ptal-hp scan" to auto-detect the image length/height even in situations where the device doesn't report it. This means the end of "corrupt JPEG data" errors and oversized images. The "-length" switch is still supported if you really want to override the image height, and it now also supports decreasing or increasing the height if you put a plus or minus in front of the number. I updated SCAN-HOWTO to reflect these changes. David |
|
From: Burkhard K. <bu...@bu...> - 2001-06-26 23:48:22
|
Charlie Reinl
> Hallo,
>
> I changed to a 7.2 SuSE, new System and got ... see 'make.log'
> not knowing what's happend and not understanding the message
> I made hpjo-4 to hpjo-7 on kernel 2.2.7 to 2.2.16 and it worked (not
> too much problems).
> But what is 'uname -r' or better, what is it on a SuSE 7.2 ?
Well, just type
$ uname -r
to find out - it is the command line to request the version number of the
kernel you are running on your box.
> Where i find the makefile(s)
> what is the name of the symbolic link to change to /lib/modules/ 'uname
> -r'/build .
>
> Found a 'vmlinuz.version.h' in my /boot
>
> thanks Charlie
I haven't seen SuSE 7.2 yet, but what the fuzz is about, if you include
header files from /usr/include{linux,asm}, then you are including them from
the kernel source tree to which symlink /usr/src/linux points to. This is
fine as long as you just keep one set of kernel sources. A developer will run
into {confusion,trouble} if she keeps different versions of kernel trees
(like 2.2.19 and 2.4.5) at the same time on the same box.
/usr/src/linux usually is a link that points to a particular version (let's
say /usr/src/linux-2.2.19). If you try to build against the other kernel
version tree you first have to break the link and then set it to e.g.
/usr/src/linux-2.4.5.
> bash-2.05# make
> ptal
> make[1]: Entering directory `/opt/hpoj-0.7/ptal'
> make[1]: Nothing to be done for `release'.
> make[1]: Leaving directory `/opt/hpoj-0.7/ptal'
> ieee12844
> make[1]: Entering directory `/opt/hpoj-0.7/ieee12844'
> gcc -O -I/opt/hpoj-0.7/include -I/opt/hpoj-0.7/ptal -I/usr/src/linux/include -I/usr/include/ucd-snmp -I/usr/lib/qt-2.3.0/include -Wall -Wstrict-prototypes -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -c ieee12844pp.c
> In file included from ieee12844pp.c:44:
> /usr/src/linux/include/linux/module.h:21: linux/modversions.h: Datei oder Verzeichnis nicht gefunden
> In file included from /usr/src/linux/include/linux/module.h:261,
> from ieee12844pp.c:44:
> /usr/include/linux/version.h:2: #error "======================================================="
> /usr/include/linux/version.h:3: #error "You should not include /usr/include/{linux,asm}/ header"
> /usr/include/linux/version.h:4: #error "files directly for the compilation of kernel modules."
> /usr/include/linux/version.h:5: #error ""
> /usr/include/linux/version.h:6: #error "glibc now uses kernel header files from a well-defined"
> /usr/include/linux/version.h:7: #error "working kernel version (as recommended by Linus Torvalds)"
> /usr/include/linux/version.h:8: #error "These files are glibc internal and may not match the"
> /usr/include/linux/version.h:9: #error "currently running kernel. They should only be"
> /usr/include/linux/version.h:10: #error "included via other system header files - user space"
> /usr/include/linux/version.h:11: #error "programs should not directly include <linux/*.h> or"
> /usr/include/linux/version.h:12: #error "<asm/*.h> as well."
> /usr/include/linux/version.h:13: #error ""
> /usr/include/linux/version.h:14: #error "To build kernel modules please do the following:"
> /usr/include/linux/version.h:15: #error ""
> /usr/include/linux/version.h:16: #error " o Have the kernel sources installed"
> /usr/include/linux/version.h:17: #error ""
> /usr/include/linux/version.h:18: #error " o Make sure that the symbolic link"
> /usr/include/linux/version.h:19: #error " /lib/modules/`uname -r`/build exists and points to"
> /usr/include/linux/version.h:20: #error " the matching kernel source directory"
> /usr/include/linux/version.h:21: #error ""
> /usr/include/linux/version.h:22: #error " o Now copy /boot/vmlinuz.version.h to"
> /usr/include/linux/version.h:23: #error " /lib/modules/`uname -r`/build/include/linux/version.h"
> /usr/include/linux/version.h:24: #error ""
> /usr/include/linux/version.h:25: #error " o When compiling, make sure to use the following"
> /usr/include/linux/version.h:26: #error " compiler option to use the correct include files:"
> /usr/include/linux/version.h:27: #error ""
> /usr/include/linux/version.h:28: #error " -I/lib/modules/`uname -r`/build/include"
> /usr/include/linux/version.h:29: #error ""
> /usr/include/linux/version.h:30: #error " instead of"
> /usr/include/linux/version.h:31: #error ""
> /usr/include/linux/version.h:32: #error " -I/usr/include/linux"
> /usr/include/linux/version.h:33: #error ""
> /usr/include/linux/version.h:34: #error " Please adjust the Makefile accordingly."
> /usr/include/linux/version.h:35: #error "======================================================="
Pretty much repetition, including a single log for one source file would have sufficed.
I would suggest that you run
$ uname -r
and create a symlink accordingly. E.g. in case you are running
2.2.19 you will find a directory /lib/modules/2.2.19. Below that directory
create a symlink "build" with the command line
$ ln -s /usr/src/linux-2.2.19 /lib/modules/2.2.19/build
and then copy /boot/vmlinuz.version.h to
/lib/modules/2.2.19/build/include/linux/version.h following the directions
above and change the Makefile accordingly (-I/lib/modules/`uname -r`/build/include).
Note that changing the Makefile is just a quick hack, when you run ./configure
again in hopj-0.7 you will loose your changes, so be sure to edit Makefile.in
as well.
Note too that you don't want to hardcode the kernel version into your Makefile,
that's why `uname -r` is used - it is a shell command that substitutes this
construct with the result of the uname command. That way you will be using
the right header files automatically whatever kernel version you are building
against.
I am sure, David will take care of this issue within the next release :-)
BTW: In my humble opinion this fuzz is not really a great idea - it might
help developers a bit, but doesn't the majority of users just run/keep one
kernel on their boxes? Indirection is a great tool, but human brains tend
to miss the thread when facing too much of it.
BTW2: If SuSE decides to use a binutils version that requires the
/lib/modules/`uname -r`/build symlink, why don't they just set it
up properly? I suggest to open a call, so SuSE's software engineers
learn about this particular problem.
Burkhard
--
Burkhard Kohl bu...@bu...
|
|
From: Charlie R. <kar...@fe...> - 2001-06-26 21:58:21
|
Hallo, I changed to a 7.2 SuSE, new System and got ... see 'make.log' not knowing what's happend and not understanding the message I made hpjo-4 to hpjo-7 on kernel 2.2.7 to 2.2.16 and it worked (not too much problems). But what is 'uname -r' or better, what is it on a SuSE 7.2 ? Where i find the makefile(s) what is the name of the symbolic link to change to /lib/modules/ 'uname -r'/build . Found a 'vmlinuz.version.h' in my /boot thanks Charlie |
|
From: Obi-Wan <bv...@in...> - 2001-06-25 16:57:33
|
>> OK, I duplicated it. It happens after I successfully scan one photo.
>> When I want to scan another photo at a different orientation (horz vs
>> vert), I hit the magnifier-undo, then the magnifier-minus (zoom out),
>> then hit "acquire preview". It scans virtually the entire image, then
>> locks up xsane. After a few minutes, the PSC makes a noise, then prints
>> the LCD message "Power system failure. Turn power off then on again."
>> Still no response from xsane. No cron jobs this time.
>
> So are you saying that this particular procedure causes the problem every
> time? Also, what version of xsane are you currently running?
Three times, anyway.
# xsane --version
xsane-0.70
package xsane-0.70
SANE-1.0
compiled with GTK-1.2.8
with GIMP support, compiled with GIMP-1.2.0
XSane output formats: jpeg, png, pnm, ps, raw, tiff
It was installed via the debs, and that's the newest version available
from the unstable distribution.
>> The stack trace
>> isn't very useful, since it wasn't compiled with -g.
>
> ptal-mlcd normally is compiled with -g. Did you take that out of the
> Makefile?
No, I haven't touched it. My last few installs were done with:
# cvs update && ./configure && make && make install
> It would be a good idea to restart xsane if you have to power cycle the
> peripheral. When a SANE backend device is opened, the backend probes the
> device for various things and sets some values in the device. It's quite
> likely that the ruler spacing is based on some of these one-time settings,
> and power cycling the device pulls the rug out from under the software.
Ah. Noted for future reference.
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: <pa...@rc...> - 2001-06-25 09:41:01
|
Obi-Wan wrote: > OK, I duplicated it. It happens after I successfully scan one photo. > When I want to scan another photo at a different orientation (horz vs > vert), I hit the magnifier-undo, then the magnifier-minus (zoom out), > then hit "acquire preview". It scans virtually the entire image, then > locks up xsane. After a few minutes, the PSC makes a noise, then prints > the LCD message "Power system failure. Turn power off then on again." > Still no response from xsane. No cron jobs this time. So are you saying that this particular procedure causes the problem every time? Also, what version of xsane are you currently running? > The stack trace > isn't very useful, since it wasn't compiled with -g. ptal-mlcd normally is compiled with -g. Did you take that out of the Makefile? > Power cycling the PSC seems to be the only thing necessary to fix > the problem. I didn't have to restart xsane or ptal-mlcd, and it > started working again. > > Upon revival, the rulers are off again. The numbers along the top > are exactly double the numbers along the left. ... > Are these ruler numbers dependent on info reported by the device? > Is this what happens when it reports a different vertical vs horizontal > resolution, for instance? It would be a good idea to restart xsane if you have to power cycle the peripheral. When a SANE backend device is opened, the backend probes the device for various things and sets some values in the device. It's quite likely that the ruler spacing is based on some of these one-time settings, and power cycling the device pulls the rug out from under the software. David |
|
From: Obi-Wan <bv...@in...> - 2001-06-23 06:15:59
|
OK, more scanning problems.
After I got xsane revived (see previous post), I grabbed a preview of
a third photo. I took the master off the scanner bed to compare color
and adjust the scanner settings, then hit "start scan". OOPS! I'm
still holding the photo in my hand. Quickly (like a second after I
hit 'scan'), I hit "cancel scan". Xsane is now locked up. The PSC's
LCD still says "waiting to scan."
ptal-mlcd dumped this to stdout:
--------------------
llioService: llioReverseToForward failed!
ptal-mlcd: ERROR at ExMgr.cpp:868, dev=<par:psc500>, pid=25968, errno=11
exClose(reason=0x0010)
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=49) timed out!
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=23) timed out!
--------------------
and this to syslog:
--------------------
Jun 23 00:42:58 tatooine ptal-mlcd: ptal-mlcd: ERROR at ParPort.cpp:705, dev=<p
ar:psc500>, pid=25968, errno=11 readEcpByte: received ECP command=0xFF!
Jun 23 00:42:59 tatooine ptal-mlcd: ptal-mlcd: ERROR at ParPort.cpp:163, dev=<p
ar:psc500>, pid=25968, errno=11 statusWaitSetClear(event=45) timed out!
Jun 23 00:42:59 tatooine ptal-mlcd: ptal-mlcd: ERROR at ParPort.cpp:163, dev=<p
ar:psc500>, pid=25968, errno=11 statusWaitSetClear(event=49) timed out!
Jun 23 00:42:59 tatooine ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:2362, dev=<pa
r:psc500>, pid=25968, errno=11 llioService: llioReverseToForward failed!
Jun 23 00:42:59 tatooine ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:868, dev=<par
:psc500>, pid=25968, errno=11 exClose(reason=0x0010)
Jun 23 00:42:59 tatooine ptal-mlcd: ptal-mlcd: ERROR at ParPort.cpp:163, dev=<p
ar:psc500>, pid=25968, errno=11 statusWaitSetClear(event=49) timed out!
Jun 23 00:42:59 tatooine ptal-mlcd: ptal-mlcd: ERROR at ParPort.cpp:163, dev=<p
ar:psc500>, pid=25968, errno=11 statusWaitSetClear(event=23) timed out!
Jun 23 00:43:28 tatooine ptal-mlcd: ptal-mlcd: SYSLOG at /usr/local/build/hpoj/
mlcd/bp/ex/ExMgr.h:540, dev=<par:psc500>, pid=25968, errno=11 ptal-mlcd
successfully activated.
--------------------
gdb claims ptal-mlcd is in that same select() call.
Power cycling the PSC 500 revives xsane and dumps this to syslog:
--------------------
Jun 23 01:09:09 tatooine ptal-mlcd: ptal-mlcd: ERROR at ParPort.cpp:705, dev=<par:psc500>, pid=25968, errno=11 readEcpByte: received ECP command=0xFF!
Jun 23 01:09:09 tatooine ptal-mlcd: ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11 statusWaitSetClear(event=45) timed out!
Jun 23 01:09:09 tatooine ptal-mlcd: ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11 statusWaitSetClear(event=49) timed out!
Jun 23 01:09:09 tatooine ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:2362, dev=<par:psc500>, pid=25968, errno=11 llioService: llioReverseToForward failed!
Jun 23 01:09:09 tatooine ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:868, dev=<par:psc500>, pid=25968, errno=11 exClose(reason=0x0010)
Jun 23 01:09:10 tatooine ptal-mlcd: ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11 statusWaitSetClear(event=49) timed out!
Jun 23 01:09:10 tatooine ptal-mlcd: ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11 statusWaitSetClear(event=23) timed out!
--------------------
and this to stderr:
--------------------
ptal-mlcd: ERROR at ExMgr.cpp:2362, dev=<par:psc500>, pid=25968, errno=11
llioService: llioReverseToForward failed!
ptal-mlcd: ERROR at ExMgr.cpp:868, dev=<par:psc500>, pid=25968, errno=11
exClose(reason=0x0010)
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=49) timed out!
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=23) timed out!
ptal-mlcd: ERROR at ParPort.cpp:705, dev=<par:psc500>, pid=25968, errno=11
readEcpByte: received ECP command=0xFF!
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=45) timed out!
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=49) timed out!
ptal-mlcd: ERROR at ExMgr.cpp:2362, dev=<par:psc500>, pid=25968, errno=11
llioService: llioReverseToForward failed!
ptal-mlcd: ERROR at ExMgr.cpp:868, dev=<par:psc500>, pid=25968, errno=11
exClose(reason=0x0010)
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=49) timed out!
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=23) timed out!
ptal-mlcd: ERROR at ParPort.cpp:705, dev=<par:psc500>, pid=25968, errno=11
readEcpByte: received ECP command=0xFF!
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=45) timed out!
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=49) timed out!
ptal-mlcd: ERROR at ExMgr.cpp:2362, dev=<par:psc500>, pid=25968, errno=11
llioService: llioReverseToForward failed!
ptal-mlcd: ERROR at ExMgr.cpp:868, dev=<par:psc500>, pid=25968, errno=11
exClose(reason=0x0010)
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=49) timed out!
ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:psc500>, pid=25968, errno=11
statusWaitSetClear(event=23) timed out!
--------------------
Ptal-mlcd was compiled Jun 13 4pm, using whatever CVS source was
current at the time. There haven't been many changes since then,
as I recall.
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: Obi-Wan <bv...@in...> - 2001-06-23 06:04:12
|
>> did anyone here successfully manage to get an OfficeJet working >> on Debian? I tried installing the driver from >> hpinkjet.sourceforge.net, but after I installed ghostscript-hpijs >> on my box, gs stopped working completely... :( >> >> I *did* manage to get cups working with the cdj550 driver, but >> that doesn't allow using duplex... :( >> >> Any help on getting another driver to work (preferably one >> supporting duplex printing), would be nice... ;) >> >> Benedikt > > Hi, Benedikt. I'm not familiar with setting up hpinkjet on Debian, so you > may be better served by using the hpinkjet "help" forum. I'm also CCing > lin...@hp..., but the address you gave (hp...@he...) isn't valid. > > If you tried to install the ghostscript-hpijs RPM onto Debian through alien, > then that could be a problem. In situations where binaries aren't available > for your specific distribution, then you'd probably be better off building > hpinkjet from source. I managed to get HPIJS running on Debian 2.2 for my PSC 500 using the DJ8xx driver. I grabbed the source deb for gs-5.50 and then built that with the mods described in the inkjetserver documentation. Add this to your /etc/apt/sources.list to grab the source: deb-src http://http.us.debian.org/debian unstable main I don't remember exactly all the hoops I jumped through, since it was over a month ago, but I seem to recall it was pretty straightforward once I got the source on my machine. Holler if you've got specific questions. -- Ben "Obi-Wan" Hollingsworth ob...@je... The stuff of earth competes for the allegiance I owe only to the Giver of all good things, so if I stand, let me stand on the promise that You will pull me through. -- Rich Mullins |
|
From: Obi-Wan <bv...@in...> - 2001-06-23 05:49:53
|
I didn't mean to rush you with my tiny little problems. I just didn't
want to have gotten kicked off the list or be dumping it due to a
typo in a mail filter or something.
>> I also had sane lock up on me while scanning. I was getting a preview
>> scan of the entire bed after putting in a new photo. It had scanned
>> almost the entire thing, when it just stopped. XSane wouldn't refresh
>> its windows. There were no syslog messages & nothing to
>> stdout/stderr.
>> After a minute or two, the scanner light returned to home, but still
>> no refresh from xsane.
>
> If the lockup happened right when the cron job started, then I suspect it's
> more than coincidence, because ptal-mlcd does its parallel-port signalling
> in user mode and could theoretically be affected if it's starved for CPU
> time. If this happens again, it would be helpful if you could attach gdb to
> the running(?) ptal-mlcd process and get a stack trace ("bt" I think) to see
> what it's blocked on. Note that when you attach gdb to a running process
> like this, the process will be suspended until you exit gdb or issue the
> "continue" (I think) command.
OK, I duplicated it. It happens after I successfully scan one photo.
When I want to scan another photo at a different orientation (horz vs
vert), I hit the magnifier-undo, then the magnifier-minus (zoom out),
then hit "acquire preview". It scans virtually the entire image, then
locks up xsane. After a few minutes, the PSC makes a noise, then prints
the LCD message "Power system failure. Turn power off then on again."
Still no response from xsane. No cron jobs this time. The stack trace
isn't very useful, since it wasn't compiled with -g.
tatooine:/usr/local/build/hpoj/mlcd# gdb ptal-mlcd 25968
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
/usr/local/build/hpoj/mlcd/25968: No such file or directory.
Attaching to program: /usr/local/build/hpoj/mlcd/ptal-mlcd, Pid 25968
Reading symbols from /usr/lib/libstdc++-libc6.2-2.so.3...done.
Loaded symbols for /usr/lib/libstdc++-libc6.2-2.so.3
Reading symbols from /lib/libm.so.6...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
0x40150c3e in select () from /lib/libc.so.6
(gdb) where
#0 0x40150c3e in select () from /lib/libc.so.6
#1 0x0 in ?? ()
(gdb) quit
The program is running. Quit anyway (and detach it)? (y or n) y
Detaching from program: /usr/local/build/hpoj/mlcd/ptal-mlcd, Pid 25968
tatooine:/usr/local/build/hpoj/mlcd# psg ptal
root 25968 0.1 0.6 1824 204 pts/3 S Jun20 6:42 /usr/local/sbin/ptal-mlcd par:psc500
root 25970 0.0 0.0 1260 0 pts/3 SW Jun20 0:00 [ptal-printd]
Power cycling the PSC seems to be the only thing necessary to fix
the problem. I didn't have to restart xsane or ptal-mlcd, and it
started working again.
Upon revival, the rulers are off again. The numbers along the top
are exactly double the numbers along the left.
> I've thought about that, but the problem is that there may be situations,
> such as a "kill -9", where it's not possible to log a message. ptal-mlcd
> logs a message when it hits a "fatal error", so the only remaining
> situations I can think of without a log message are where it segfaults or
> you kill it.
Good point.
>> Upon restarting xsane, I see that the vertical ruler is now correct.
>> Hmmm...
>
> Perhaps the peripheral got confused and power cycling it got it back in a
> good state. Do you remember what you had been doing before this problem
> happened?
Are these ruler numbers dependent on info reported by the device?
Is this what happens when it reports a different vertical vs horizontal
resolution, for instance?
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2001-06-23 00:05:13
|
Obi-Wan [mailto:bv...@in...] wrote:
> Tap tap tap... is this thing on? I haven't received anything
> since Tuesday.
Yes, "this thing" is "on", but I haven't been "on" the last several days.
:-) Sorry about that.
> So, David, are you the sane owner, too? If so, I just
> noticed a couple
> problems tonight.
>
> First, with xsane, the size rulers along the top & left of the preview
> window don't seem to mesh. When set to inches, the top seems OK, but
> the side is garbage. The numbers are roughly 1.5 X too high.
I only "own" the changes I made to the SANE HP backend to support the SCL
OfficeJets. A problem like this could either be an xsane bug, an HP backend
bug, or a scanner bug. If you can figure out a way to reproduce it then
I'll look into it. Since Oliver Rauch (the xsane developer) makes frequent
updates, you should make sure you're running the latest version, just in
case that has anything to do with it. You could also try "xscanimage" and
see if it acts strangely too.
> I also had sane lock up on me while scanning. I was getting a preview
> scan of the entire bed after putting in a new photo. It had scanned
> almost the entire thing, when it just stopped. XSane wouldn't refresh
> its windows. There were no syslog messages & nothing to
> stdout/stderr.
> After a minute or two, the scanner light returned to home, but still
> no refresh from xsane. This happened just as cron launched a very
> large tar followed by gzip, but that may be coincidence.
If the lockup happened right when the cron job started, then I suspect it's
more than coincidence, because ptal-mlcd does its parallel-port signalling
in user mode and could theoretically be affected if it's starved for CPU
time. If this happens again, it would be helpful if you could attach gdb to
the running(?) ptal-mlcd process and get a stack trace ("bt" I think) to see
what it's blocked on. Note that when you attach gdb to a running process
like this, the process will be suspended until you exit gdb or issue the
"continue" (I think) command.
> When attempting to restart xsane, it brought up the "scanning for
> devices" window and hung. I had to kill -9 xsane. I stopped &
> restarted the ptal brothers. I then noticed my PSC 500's LCD said
> "Scanner system failure. Turn system off and on again,"
> which I did.
> That all seemed to fix the problem. Still no log entries other than
> the startup banners. (Perhaps a log entry for every shutdown would
> also be in order.)
I've thought about that, but the problem is that there may be situations,
such as a "kill -9", where it's not possible to log a message. ptal-mlcd
logs a message when it hits a "fatal error", so the only remaining
situations I can think of without a log message are where it segfaults or
you kill it.
> Upon restarting xsane, I see that the vertical ruler is now correct.
> Hmmm...
Perhaps the peripheral got confused and power cycling it got it back in a
good state. Do you remember what you had been doing before this problem
happened?
David
|
|
From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2001-06-23 00:04:11
|
> did anyone here successfully manage to get an OfficeJet working > on Debian? I tried installing the driver from > hpinkjet.sourceforge.net, but after I installed ghostscript-hpijs > on my box, gs stopped working completely... :( > > I *did* manage to get cups working with the cdj550 driver, but > that doesn't allow using duplex... :( > > Any help on getting another driver to work (preferably one > supporting duplex printing), would be nice... ;) > > Benedikt Hi, Benedikt. I'm not familiar with setting up hpinkjet on Debian, so you may be better served by using the hpinkjet "help" forum. I'm also CCing lin...@hp..., but the address you gave (hp...@he...) isn't valid. If you tried to install the ghostscript-hpijs RPM onto Debian through alien, then that could be a problem. In situations where binaries aren't available for your specific distribution, then you'd probably be better off building hpinkjet from source. Note that hpinkjet doesn't currently support duplex printing. If that's what you're looking for, then you could try the "cdj970" driver mentioned on http://www.linuxprinting.org. David |
|
From: Obi-Wan <bv...@in...> - 2001-06-22 16:23:34
|
Tap tap tap... is this thing on? I haven't received anything since Tuesday.
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: <hp...@he...> - 2001-06-20 21:05:14
|
Hi there, did anyone here successfully manage to get an OfficeJet working on Debian? I tried installing the driver from hpinkjet.sourceforge.net, but after I installed ghostscript-hpijs on my box, gs stopped working completely... :( I *did* manage to get cups working with the cdj550 driver, but that doesn't allow using duplex... :( Any help on getting another driver to work (preferably one supporting duplex printing), would be nice... ;) Benedikt By three methods we may learn wisdom: First, by reflection which is noblest; second, by imitation, which is the easiest; and third, by experience, which is the bitterest. - Confucius (B.C. 551-479) |
|
From: Obi-Wan <bv...@in...> - 2001-06-20 07:18:33
|
> Scanning with SANE is not yet supported on this model, but it's on my TODO
> list.
So, David, are you the sane owner, too? If so, I just noticed a couple
problems tonight.
First, with xsane, the size rulers along the top & left of the preview
window don't seem to mesh. When set to inches, the top seems OK, but
the side is garbage. The numbers are roughly 1.5 X too high.
I also had sane lock up on me while scanning. I was getting a preview
scan of the entire bed after putting in a new photo. It had scanned
almost the entire thing, when it just stopped. XSane wouldn't refresh
its windows. There were no syslog messages & nothing to stdout/stderr.
After a minute or two, the scanner light returned to home, but still
no refresh from xsane. This happened just as cron launched a very
large tar followed by gzip, but that may be coincidence.
When attempting to restart xsane, it brought up the "scanning for
devices" window and hung. I had to kill -9 xsane. I stopped &
restarted the ptal brothers. I then noticed my PSC 500's LCD said
"Scanner system failure. Turn system off and on again," which I did.
That all seemed to fix the problem. Still no log entries other than
the startup banners. (Perhaps a log entry for every shutdown would
also be in order.)
Upon restarting xsane, I see that the vertical ruler is now correct.
Hmmm...
--
Ben "Obi-Wan" Hollingsworth ob...@je...
The stuff of earth competes for the allegiance I owe only to the
Giver of all good things, so if I stand, let me stand on the
promise that You will pull me through. -- Rich Mullins
|
|
From: <pa...@rc...> - 2001-06-19 08:55:05
|
Clifford Heath wrote: > I have an HP Officejet 635. Last December I spoke with Mary Kumar, whose > daughter worked with us over summer. Mary is head of Support for HP > Corporate. I worked previously with her in HP's Australian Software > Operation. Anyhow, she said she'd been asked to radically revamp HP's > support practises and asked if I had any input. I said yes, I have a > nice OJ635 but no Linux drivers - why doesn't HP provide support for > the open source community? Anyhow, I don't know if that's what changed > things, but I'm glad they have changed! Hi, Clifford. This project had actually been started by several people outside of HP. I joined it on my own initiative as a side project on my own time, because I recognized that there was an unmet need for this level of support. Gradually I have gotten more and more support from HP management, to the point where this project is now an official part of my job description. I'm glad that this project has been well-received by many people in the community, and I've certainly enjoyed being a part of it. > I recently built (from source) the ptal, hpoj, sane and xsane software > on my Debian 2.2 (Potato) system, as the available .deb required a few > upgrades: ... > Now, the "hpo" command works fine, but the test scan command hangs. Here's > the diagnostic output from the command: > PTAL_DEBUG=2 SANE_DEBUG_HP=128 scanimage -d hp:mlc:mlcpp0 --test ... > There is a delay of several seconds after the scsi_flush lines, then the > final two lines appear. > > Have you any idea what's going wrong here? Scanning with SANE is not yet supported on this model, but it's on my TODO list. In the meantime, you can scan using the "ptal-hp" command-line utility, which is available with the development code in CVS (not 0.7) and will go into the next stable release (0.8, probably sometime in August). For more information, see "http://hpoj.sourceforge.net/hpoj-cvs/SCAN-HOWTO", but don't pay any attention to the part that talks about SANE. David |
|
From: Clifford H. <cj...@os...> - 2001-06-19 01:06:39
|
Folk, I have an HP Officejet 635. Last December I spoke with Mary Kumar, whose daughter worked with us over summer. Mary is head of Support for HP Corporate. I worked previously with her in HP's Australian Software Operation. Anyhow, she said she'd been asked to radically revamp HP's support practises and asked if I had any input. I said yes, I have a nice OJ635 but no Linux drivers - why doesn't HP provide support for the open source community? Anyhow, I don't know if that's what changed things, but I'm glad they have changed! I recently built (from source) the ptal, hpoj, sane and xsane software on my Debian 2.2 (Potato) system, as the available .deb required a few upgrades: (Reading database ... 24449 files and directories currently installed.) Preparing to replace xsane 0.70-1 (using xsane_0.70-1_i386.deb) ... Unpacking replacement xsane ... dpkg: dependency problems prevent configuration of xsane: xsane depends on libc6 (>= 2.1.97); however: Version of libc6 on system is 2.1.3-13. xsane depends on libgimp1.2 (>= 1.2.0); however: Package libgimp1.2 is not installed. xsane depends on libgtk1.2 (>= 1.2.8-3); however: Version of libgtk1.2 on system is 1.2.7-1. xsane depends on libsane (>= 1.0.3); however: Package libsane is not installed. xsane depends on xlibs (>= 4.0.1-11); however: Package xlibs is not installed. dpkg: error processing xsane (--install): dependency problems - leaving unconfigured Errors were encountered while processing: xsane Now, the "hpo" command works fine, but the test scan command hangs. Here's the diagnostic output from the command: PTAL_DEBUG=2 SANE_DEBUG_HP=128 scanimage -d hp:mlc:mlcpp0 --test [sanei_debug] Setting debug level of hp to 128. [hp] sane_init called ptalInit(): debug level set to 2. ptalInit() ptalDeviceProbe: dev=<mlc:mlcpp0>. ptalDeviceAdd(provider=<mlc>,name=<mlcpp0>): dev=0x08050440. ptalDeviceProbe: dev=<mlc:mlcpp1>. ptalDeviceAdd(provider=<mlc>,name=<mlcpp1>): dev=0x08050770. [hp] sane_init will finish with Success [hp] sane_open called [hp] hp_read_config: hp backend v0.94 starts reading config file [hp] hp_read_config: processing line <#scsi HP> [hp] hp_read_config: processing line <#/dev/scanner> [hp] hp_read_config: processing line <> [hp] hp_read_config: processing line <# Parallel-port-connected MFP:> [hp] hp_read_config: processing line <mlc:mlcpp0> [hp] hp_read_config: processing line <option connect-ptal> [hp] hp_read_config: attach mlc:mlcpp0 [hp] hp_get_dev: New device mlc:mlcpp0, connect-ptal, scsi-request=0 [hp] sanei_hp_device_new: mlc:mlcpp0 ptalMlcDeviceOpen(name=<mlcpp0>): found matching dev=0x08050440. ptalChannelAllocate(dev=0x08050440): chan=0x08054840. ptalChannelSetRemoteService(chan=0x08054840,serviceType=2,socketID=0,serviceName=<>) [hp] scsi_flush: writing 2 bytes: [hp] 0x0000 1B 45 .E ptalChannelOpen(chan=0x08054840): fd=4. ptalChannelWrite(chan=0x08054840,buffer=0x0805400E,count=2) There is a delay of several seconds after the scsi_flush lines, then the final two lines appear. Have you any idea what's going wrong here? |
|
From: <pa...@rc...> - 2001-06-18 10:01:28
|
Joe Piolunek wrote: > These error messages appear to have been logged shortly after boot. I don't > think the printer was in active use at the time. > > Jun 16 09:26:22 tumbleweed ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:727, > dev=<par:0>, pid=786, errno=11 fdRegister(invalid fd=-1,r=1,w=0) > called from ExMgr.cpp:2079! > Jun 16 09:26:22 tumbleweed ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:2082, > dev=<par:0>, pid=786, errno=11 exContext=4, scd=8, state=5! > Jun 16 09:26:22 tumbleweed ptal-mlcd: ptal-mlcd: SYSLOG at > /home/joe/CVS/hpoj_copy/mlcd/bp/ex/ExMgr.h:540, dev=<par:0>, pid=786, > errno=11 ptal-mlcd successfully activated. Hi, Joe. I figured out what the problem is and checked in a fix. Let me know if you still see error messages like this, although I removed the second one since it's no longer needed. The activation above would have occurred due to any attempted access to the peripheral, which includes running xojpanel, setting the clock, or other uses of the hpoj software that one might not consider "active use" of the peripheral. David |
|
From: Joe P. <joe...@sn...> - 2001-06-17 04:34:56
|
On Wednesday 13 June 2001 07:19 am, David Paschal wrote: <...> > > > > Jun 12 19:05:05 tumbleweed ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:708, > > dev=<par:0>, pid=1185, errno=11 > > Jun 12 19:05:05 tumbleweed ptal-mlcd: fdRegister(invalid fd=-1,r=1,w=0) > > called from ExMgr.cpp:2056! > > I haven't yet determined with 100% certainty why this happens, but I added > an extra error message after this particular failed call that prints out > some interesting variables. I somehow managed to hit this on the first > try after adding the extra error message, but only once. In my case, the > extra information was "exContext=4, scd=8, state=5". Let me know if you > or anybody else sees this again, especially if becomes reproducible. I'll > try to get to root cause instead of applying a superficial fix that makes > the error go away but doesn't actually fix the underlying problem. > > David Similar error messages appeared in /var/log/messages today. I've included all of the ptal-related messages generated during the session. These startup messages would have been logged at boot. I start ptal-printd and ptal-mlcd from /etc/rc.d/rc.local . Jun 16 09:22:12 tumbleweed ptal-mlcd: ptal-mlcd: SYSLOG at ExMgr.cpp:679, dev=<par:0>, pid=786, errno=111 ptal-mlcd successfully initialized. Jun 16 09:22:12 tumbleweed ptal-printd: ptal-printd(mlc:par:0) successfully initialized. These error messages appear to have been logged shortly after boot. I don't think the printer was in active use at the time. Jun 16 09:26:22 tumbleweed ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:727, dev=<par:0>, pid=786, errno=11 fdRegister(invalid fd=-1,r=1,w=0) called from ExMgr.cpp:2079! Jun 16 09:26:22 tumbleweed ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:2082, dev=<par:0>, pid=786, errno=11 exContext=4, scd=8, state=5! Jun 16 09:26:22 tumbleweed ptal-mlcd: ptal-mlcd: SYSLOG at /home/joe/CVS/hpoj_copy/mlcd/bp/ex/ExMgr.h:540, dev=<par:0>, pid=786, errno=11 ptal-mlcd successfully activated. -- Joe |
|
From: <le...@t-...> - 2001-06-16 06:05:14
|
Hello, you are right David. Scanning on my HP OfficeJet 710 is only possible up to 300 dpi. I was wrong because the default resolution is below 300 dpi and it seems that the driver interprets all higher resolutions (e.g. 600 dpi) as 300 dpi. I will come back periodically to see what's with SANE. But in the meantime scanning from the commandline is enough for me. Thanks: Rainer Lehrig |
28 messages has been excluded from this view by a project administrator.
