Hi, In order to help hplip-os2 development, I need some test results from hp-mkuri from usb connected HP printers or MFPs. Please download http://smedley.id.au/hp-mkuri.zip and execute: hp-mkuri.exe -o Send me the screen output (if any) and also libusb.log My HP MFP gives no screen output, and libusb.log shows 'unable to send control message - rc= 280' Thanks, Paul
Hi All, per my earlier email, I've built usb.exe from CUPS 1.5.1 It's available from http://smedley.id.au/usb-cups-1.5.1.zip Not tested by me.... Cheers, Paul
If a brief perusal of the below indicates that I should further review
what may be available documentation which I have been unable to
locate, please simply advise - and I will then stop bothering the
readers and try to find my answer. So far I have been unable to
locate anything that would seem to solve the problem.
Initially, Cups recognized the subject, and eCS 2.0 also has a driver
for the F300 Series. So this part doesn't seem to be a problem.
I _think_ I have 1.4.8 installed properly. Due to an "invalid package
index '99'" error on the WPI file, I installed all the zip files
manually over a previous eCUPS003.wpi installation. However I believe
I might read somewhere that it might be wise to first use WarpIn to
uninstall earlier installations, something I didn't do here. If this
could be a step I shouldn't have avodied, please advise.
Trying to print a test page, after having added the printer, fails,
and yields a message of
"Paused - "Unable to write 320 bytes to printer!""
(Earlier messages indicated
"Unable to write 512 bytes to printer!"
and
"No %%BoundingBox: comment in header!".
Depite my inability to print a test page, I went ahead and created a
printer object. Dropping a PS file on it resulted in the same
failure. On it, similar to the test page efforts, the Access Log
indicated
localhost - - [04/Feb/2012:14:10:20 +0500] "POST
/printers/HP_Deskjet_F300_series HTTP/1.1" 200 614355 Print-Job
(Continue reading)Version 0.94 (preview 4) of the CUPS printer wizard is up. http://users.socis.ca/~ataylo00/os2/printing/#cupswiz See the website or the included release notes for the requirements and limitations. Testing and feedback are much appreciated! New in this release: - A few minor UI tweaks - Detected network printers should now show the actual printer name (manufacturer/model) as well as the URI. This depends on them correctly reporting this to the SNMP backend, however. - HPLIP printers SHOULD now be supported, although this has only been lightly tested. NOTE: This still requires CUPS to be installed (and running) LOCALLY, on the same computer. -- -- Alex Taylor Fukushima, Japan http://www.socis.ca/~ataylo00 Please take off hat when replying.
I've lately decided to take another look at debugging the problem which causes foomatic-rip to mangle the PostScript file when Ghostscript is used as the renderer. For some reason, though, I find that I can't get foomatic-rip to work at all anymore. This is the same system where I was working on this last year, and all the foomatic stuff is unchanged. I _have_ upgraded CUPS from 1.4.4 to 1.4.8 in the interim, so I'm wondering if a problem has crept into the latest releases. First of all, I got this: I [16/Jan/2012:14:56:56 -0900] [Job 13] Started filter /cups/lib/cups/filter/pstops.exe (PID 81) I [16/Jan/2012:14:56:56 -0900] [Job 13] Started filter /cups/lib/cups/filter/foomatic-rip.exe (PID 82) I [16/Jan/2012:14:56:56 -0900] [Job 13] Started backend /cups/lib/cups/backend/lpd.exe (PID 84) D [16/Jan/2012:14:56:56 -0900] Discarding unused job-state-changed event... D [16/Jan/2012:14:56:56 -0900] Returning IPP successful-ok for Send-Document (ipp://localhost:631/printers/LP-S3500_KC) from localhost D [16/Jan/2012:14:56:56 -0900] PID 82 (/cups/lib/cups/filter/foomatic-rip.exe) stopped with status 8! D [16/Jan/2012:14:56:56 -0900] PID 81 (/cups/lib/cups/filter/pstops.exe) did not catch or ignore signal 13. ... D [16/Jan/2012:14:56:56 -0900] [Job 13] /cups/lib/cups/filter/foomatic-rip.exe: Invalid executable file format I eventually figured out that it couldn't cope with the symbolic link(Continue reading)
Upon starting to run <cupsd.exe>, the CPU usage spikes to 99.9%, and killing it (through the C-A-D utility doesn't help. It seems the <...\cups\backend\usb.exe> tile is the cause and can't be stopped without a system boot. I think I have the proper commands in the object to open it, the parameters being </c detach O:\cups\sbin\cupsd.exe>. I also believe I have correctly unzipped all the necessary files with the proper setup. The Log file, produced by the "warn" command, shows simply: D [04/Jan/2012:15:59:20 +0500] [Job 4] Unloading... E [04/Jan/2012:16:07:26 +0500] Missing value for SystemGroup on line 13. E [04/Jan/2012:16:07:27 +0500] Unable to bind socket for address /cups/var/run/cups/cups.sock:0 - Operation now in progress. E [04/Jan/2012:16:07:27 +0500] [Job 4] No %%BoundingBox: comment in header! E [04/Jan/2012:16:07:27 +0500] [Job 4] No %%Pages: comment in header! E [04/Jan/2012:16:07:28 +0500] [Job 4] No pages found! The file produced by the "debug" command of course provides a plethora of entries, but it appears CUPS does recognize the printer but just insists on the 99.9% usage. Any idea what I have done wrong, or what more information is needed, or what might be the problem? -- --
Upon starting to run <cupsd.exe>, the CPU usage spikes to 99.9%, and killing it (through the C-A-D utility doesn't help. It seems the <...\cups\backend\usb.exe> tile is the cause and can't be stopped without a system boot. I think I have the proper commands in the object to open it, the parameters being </c detach O:\cups\sbin\cupsd.exe>. I also believe I have correctly unzipped all the necessary files with the proper setup. The Log file, produced by the "warn" command, shows simply: D [04/Jan/2012:15:59:20 +0500] [Job 4] Unloading... E [04/Jan/2012:16:07:26 +0500] Missing value for SystemGroup on line 13. E [04/Jan/2012:16:07:27 +0500] Unable to bind socket for address /cups/var/run/cups/cups.sock:0 - Operation now in progress. E [04/Jan/2012:16:07:27 +0500] [Job 4] No %%BoundingBox: comment in header! E [04/Jan/2012:16:07:27 +0500] [Job 4] No %%Pages: comment in header! E [04/Jan/2012:16:07:28 +0500] [Job 4] No pages found! The file produced by the "debug" command of course provides a plethora of entries, but it appears CUPS does recognize the printer but just insists on the 99.9% usage. Any idea what I have done wrong, or what more information is needed, or what might be the problem? -- --
Upon starting to run <cupsd.exe>, the CPU usage spikes to 99.9%, and killing it (through the C-A-D utility doesn't help. It seems the <...\cups\backend\usb.exe> tile is the cause and can't be stopped without a system boot. I think I have the proper commands in the object to open it, the parameters being </c detach O:\cups\sbin\cupsd.exe>. I also believe I have correctly unzipped all the necessary files with the proper setup. The Log file, produced by the "warn" command, shows simply: D [04/Jan/2012:15:59:20 +0500] [Job 4] Unloading... E [04/Jan/2012:16:07:26 +0500] Missing value for SystemGroup on line 13. E [04/Jan/2012:16:07:27 +0500] Unable to bind socket for address /cups/var/run/cups/cups.sock:0 - Operation now in progress. E [04/Jan/2012:16:07:27 +0500] [Job 4] No %%BoundingBox: comment in header! E [04/Jan/2012:16:07:27 +0500] [Job 4] No %%Pages: comment in header! E [04/Jan/2012:16:07:28 +0500] [Job 4] No pages found! The file produced by the "debug" command of course provides a plethora of entries, but it appears CUPS does recognize the printer but just insists on the 99.9% usage. Any idea what I have done wrong, or what more information is needed, or what might be the problem?
Hi All, Previous Ghostscript 9.0x builds would give a SIGSEGV when producing output using the CUPS device - which made them kinda useless for use with CUPS. I think I've fixed the problem - at least the SIGSEGV is gone when producing CUPS raster format and a testprint works. Please test the binary that is now available from http://os2ports.smedley.info Please note only the 26th December build of Ghostscript 9.04 contains the fix - the 21st December build was still broken with CUPS. Cheers, Paul
Over the course of the past week or so, I've updated the HOWTO quite extensively: http://svn.netlabs.org/ecups/wiki/HowTo I've expanded and clarified almost every section, and added small screenshots to illustrate various points. The instructions have been updated to deal with current versions of CUPS and other components. I've included a section on installing with WarpIN, and some notes on upgrading from older versions. Plus many, many other improvements. Since I was taking the screenshots on my own system, I had to change the examples to refer to my own home printer model (Epson PX-101); I hope nobody minds. <g> Ed's nice illustrated walkthrough I've moved to its own page: http://svn.netlabs.org/ecups/wiki/VisualStepByStep Partly this is to save space on the HOWTO, which now includes its own images, and partly because the screenshots are now quite out of date. It's still useful stuff, though, so the current HOWTO page has a link to it. I originally tried using WikiHtml to write this in, to make it easier to (a) write & preview locally before entering in Trac, and (b) provide as a standalone document in the CUPS installer. But I had to abandon this idea when I discovered that this method just has too many limitations. It should be easy enough to generate an HTML document out of the wiki page just by copying from the Page Source window... -- -- Alex Taylor Fukushima, Japan(Continue reading)
On Mon, 12 Dec 2011 16:47:09 UTC, Pete Brown <losepete@...> wrote: > > Probably because it's running detached, as a proper daemon should. > > I think Pete's old WPIs created it as a foreground window for some > > reason (possibly because Pete was unsure if it was safe to run > > detached). > > David must have installed from an early eCUPS003.WPI as in the later > package the eCUPS Daemon was modified to run Detached. > > With detached processes you need to look at the Process List to see that > they are running - and to be able to "kill" them. > > As David is using eCS he (probably) has Ctrl-Alt-Del installed to catch > that combo keypress and will be able to view (and kill) processes using > TOP from the Ctrl-Alt-Del menu screen. Indeed. It'd also be a useful way to check if USB.EXE is eating up the CPU and/or running multiple instances (as I've occasionally seen when it gets bollixed up). By the way, I've started on a massive overhaul of the HowTo. I'm doing it offline for various reasons, so I hope you're not planning any updates to the copy on the wiki over the next few days. <g> -- -- Alex Taylor Fukushima, Japan http://www.socis.ca/~ataylo00(Continue reading)
RSS Feed5 | |
|---|---|
16 | |
35 | |
38 | |
23 | |
7 | |
3 | |
7 | |
16 | |
3 | |
4 | |
77 | |
21 | |
18 | |
25 | |
11 | |
68 | |
12 | |
51 | |
34 | |
20 | |
35 | |
43 | |
44 | |
4 | |
25 | |
9 | |
6 | |
33 | |
33 | |
11 | |
49 | |
86 | |
36 | |
23 | |
55 | |
12 | |
13 | |
22 | |
8 | |
48 | |
107 | |
4 | |
9 | |
12 | |
19 | |
14 | |
2 | |
23 | |
6 | |
17 |
