headers
Paul Smedley | 11 Jun 2007 11:47

New build

Hi All,

I've just uploaded a package consisting of CUPS 1.2.11 (www.cups.org) 
+ ESP Ghostscript 8.15.4 (http://www.cups.org/espgs/) + Gutenprint 
5.1.2 (http://gimp-print.sourceforge.net/)

This combination should allow printing on OS/2 & eComStation with 
printers that have not previously had drivers for our favourite OS - 
see  http://gutenprint.sourceforge.net/p_Supported_Printers.php3 for 
details

The package can be downloaded from: 
http://svn.netlabs.org/ecups/wiki/CupsPort

Also at that site are some directions on how to use the package.

Assuming success with the directions at that site, people could also 
try Bart's cups port driver in order to be able to print from existing
OS/2 applications using CUPS (ftp://ftp.netlabs.org/pub/ecups)

As usual, feedback is appreciated to either 
paulDESPAM@... or to the ecups mailing list at 
news://news.gmane.org/gmane.org.netlabs.ecups.devel

--

-- 
Cheers,

Paul.
Permalink | Reply | 5 comments |
headers
Pete | 11 Jun 2007 16:48

Re: New build

Hi Paul

Paul Smedley wrote:
> Hi All,
> 
> I've just uploaded a package consisting of CUPS 1.2.11 (www.cups.org) 
> + ESP Ghostscript 8.15.4 (http://www.cups.org/espgs/) + Gutenprint 
> 5.1.2 (http://gimp-print.sourceforge.net/)
> 
> This combination should allow printing on OS/2 & eComStation with 
> printers that have not previously had drivers for our favourite OS - 
> see  http://gutenprint.sourceforge.net/p_Supported_Printers.php3 for 
> details
> 
> The package can be downloaded from: 
> http://svn.netlabs.org/ecups/wiki/CupsPort
> 
> Also at that site are some directions on how to use the package.
> 

Sorry but the directions do not seem to work for me.

I am trying to setup cups to work with my printer which is connected to
the printer port on my router.

Should I be using ipp or lpd? and how?

Here is an example of an lpadmin line:-

lpadmin -p PIXMA -E -v lpd://192.168.2.1/lpt1 -m
(Continue reading)

Permalink | Reply | 4 comments |
headers
Paul Smedley | 11 Jun 2007 22:56

Re: Re: New build

Hi Pete,

Pete wrote:
> Sorry but the directions do not seem to work for me.
> 
> I am trying to setup cups to work with my printer which is connected to
> the printer port on my router.
> 
> Should I be using ipp or lpd? and how?
Depends on the make/model of the router.  What protocol to you use to 
print to it now?
> 
> Here is an example of an lpadmin line:-
> 
> lpadmin -p PIXMA -E -v lpd://192.168.2.1/lpt1 -m
> gutenprint/5.1/en_gb/stp-bjc-iP4000.5.1.ppd.gz
> 
> results in
> 
> lpadmin: Bad device-uri "lpd://192.168.2.1/lpt1"!
This looks correct to me - perhaps it's objecting to the lpt1 as the lpd 
port name for some reason..

> Is it simply a case of I'm getting something wrong or is it not possible 
> to set the output port on the router using cups?
You can definitely set the output lpd driver name - my examples specify 
an lpd queue name....

> Another question is should I be using the ppd.gz file in 
> gutenprint/5.1/en_gb or the version in gutenprint/5.1/C ?
(Continue reading)

Permalink | Reply | 3 comments |
headers
Pete | 12 Jun 2007 01:29

Re: New build

Hi Paul

Paul Smedley wrote:
> Hi Pete,
> 
> Pete wrote:
>> Sorry but the directions do not seem to work for me.
>>
>> I am trying to setup cups to work with my printer which is connected to
>> the printer port on my router.
>>
>> Should I be using ipp or lpd? and how?
> Depends on the make/model of the router.  What protocol to you use to 
> print to it now?

I currently use the slpr port to print, slpr prints happily to 
192.168.2.1:lpt1

>>
>> Here is an example of an lpadmin line:-
>>
>> lpadmin -p PIXMA -E -v lpd://192.168.2.1/lpt1 -m
>> gutenprint/5.1/en_gb/stp-bjc-iP4000.5.1.ppd.gz
>>
>> results in
>>
>> lpadmin: Bad device-uri "lpd://192.168.2.1/lpt1"!
> This looks correct to me - perhaps it's objecting to the lpt1 as the lpd 
> port name for some reason..
>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Paul Smedley | 12 Jun 2007 01:46

Re: Re: New build

Hi Pete,

On Tue, 12 Jun 2007 00:29:29 +0100
  Pete <losepete@...> wrote:
>>> lpadmin: Bad device-uri "lpd://192.168.2.1/lpt1"!
>> This looks correct to me - perhaps it's objecting to the 
>>lpt1 as the lpd 
>> port name for some reason..
>> 
> 
> 
> That would not be good - the router will not print if 
>the port is
> missing.
Actually - now I think about it, I think the error is 
because it thinks that the lpd backend is not available.

Cups is in /cups isn't it?

Edit /cups/etc/cups/cupsd.conf and increase debug from 
info to debug2, then remove /cups/var/log/cups/error_log, 
and restart cupsd and try the lpadmin command again.

Send me /cups/var/log/cups/error_log

Cheers,

Paul.
Permalink | Reply | 1 comment |
headers
Pete | 12 Jun 2007 18:47

Re: New build

Paul Smedley wrote:
> Hi Pete,
> 
> On Tue, 12 Jun 2007 00:29:29 +0100
>  Pete <losepete@...> wrote:
>>>> lpadmin: Bad device-uri "lpd://192.168.2.1/lpt1"!
>>> This looks correct to me - perhaps it's objecting to the lpt1 as the 
>>> lpd port name for some reason..
>>>
>>
>>
>> That would not be good - the router will not print if the port is
>> missing.
> Actually - now I think about it, I think the error is because it thinks 
> that the lpd backend is not available.
> 

Should there be an lpd executable somewhere?

> Cups is in /cups isn't it?
> 

Yes, all packages were simply unzipped to H: (boot drive) retaining the
directory structures.

Snip from previous post:-
[H:\cups\sbin]lpadmin -p .....

> Edit /cups/etc/cups/cupsd.conf and increase debug from info to debug2, 
> then remove /cups/var/log/cups/error_log, and restart cupsd and try the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Smedley | 13 Jun 2007 11:28

Fix1 for CUPS

OK - a packaging problem crept in :(

Uploading a fix now...

http://download.smedley.info/cups-1.2.11-fix1.zip

Without this fix - the package won't work...

--

-- 
Cheers,

Paul.
Permalink | Reply | 0 comments |
headers
Pete | 18 Jun 2007 17:27

ecups.pdr - does it work? and other problems

Hi All

Anyone managed to get this ecups port to work?

I have the current cups package installed and can print the test page 
from both command line and the (very slow) browser interface to my cups 
printer, PIXMA.

I seem to have added the necessary ppd file to the os/2 pscript.drv 
correctly but with some strange results: Opening Job properties will 
display numbers as Defaults for some options.

This is a chunk of the ppd file in use:-

*OpenUI *MediaType/Media Type: PickOne
*OrderDependency: 10 AnySetup *MediaType
*StpStpMediaType: 0 1 0 0 0.000 0.000 0.000
*DefaultMediaType: Plain
*StpDefaultMediaType: Plain
*MediaType Plain/Plain Paper:	"<</MediaType(Plain)>>setpagedevice"
*MediaType Transparency/Transparencies: 
"<</MediaType(Transparency)>>setpagedevice"
*MediaType TShirt/T-Shirt Transfers:	"<</MediaType(TShirt)>>setpagedevice"
*MediaType GlossyPaper/Glossy Photo Paper: 
"<</MediaType(GlossyPaper)>>setpagedevice"
*MediaType Coated/High Resolution Paper: 
"<</MediaType(Coated)>>setpagedevice"
*MediaType Envelope/Envelope:	"<</MediaType(Envelope)>>setpagedevice"
*MediaType PhotopaperPro/Professional Photo Paper: 
"<</MediaType(PhotopaperPro)>>setpagedevice"
(Continue reading)

Permalink | Reply | 14 comments |
headers
David McKenna | 18 Jun 2007 23:01
Picon

Re: ecups.pdr - does it work? and other problems

Pete,

  No luck here either. I too can print from the command line and the CUPS web interface (using an HP 
DJ990C attached to a JetDirect server), and I was able to import the gutenprint ppd file to the 
psecups driver, but I cannot get the driver to show any job properties... no idea why. Maybe I should 
try the standard pscript driver. In any case my experience is like yours... I try to print from an app and 
nothing happens - no print job appears in CUPS either.

Dave McKenna

On Mon, 18 Jun 2007 16:27:29 +0100, Pete wrote:

>Hi All
>
>Anyone managed to get this ecups port to work?
>
>I have the current cups package installed and can print the test page 
>from both command line and the (very slow) browser interface to my cups 
>printer, PIXMA.
>
>I seem to have added the necessary ppd file to the os/2 pscript.drv 
>correctly but with some strange results: Opening Job properties will 
>display numbers as Defaults for some options.
>
>This is a chunk of the ppd file in use:-
>
>*OpenUI *MediaType/Media Type: PickOne
>*OrderDependency: 10 AnySetup *MediaType
>*StpStpMediaType: 0 1 0 0 0.000 0.000 0.000
>*DefaultMediaType: Plain
(Continue reading)

Permalink | Reply | 13 comments |
headers
Paul Smedley | 19 Jun 2007 05:28

Re: Re: ecups.pdr - does it work? and other problems

Hi David,

On Mon, 18 Jun 2007 17:01:38 -0400 (EDT)
  "David McKenna" <davidmckenna@...> wrote:
>  No luck here either. I too can print from the command 
>line and the CUPS web interface (using an HP 
> DJ990C attached to a JetDirect server), and I was able 
>to import the gutenprint ppd file to the 
> psecups driver, but I cannot get the driver to show any 
>job properties... no idea why. Maybe I should 
> try the standard pscript driver. In any case my 
>experience is like yours... I try to print from an app 
>and 
> nothing happens - no print job appears in CUPS either.

If you can't get the job properties to display, then it 
generally means that the postscript driver doesn't like 
something about the PPD file that has been imported, in 
which case, the driver won't print either.

I'm in a similar position with the PPD for my Epson RX650 
- I need to try and work out what parts of the PPD pin.exe 
doesn't like and try removing them.

You may well have some entries in popuplog.os2 about 
psecups.drv too given that the job properties can't be 
displayed.

We still have a lot of work to do, but I'm sure it will be 
worth it in the end!
(Continue reading)

Permalink | Reply | 11 comments |

Gmane