I spent several frustrating days with cups, and I think I've got a good
handle on it.

The first step is to make sure your mime-type conversion files are correct.
Check them and make sure that the type references (filename extensions and
magic number information) match what your BMP is actually looking like.

In my system, for example, the defined BMP filter type in mime-types says
that the file needs to end with a '.bmp' extension or has to start with the
letter "BM".  If your graphics don't match one of these, makes it really
hard for cups to figure out how to print your file.

If they do, the imagetoraster program needs to be able to do the bmp to
raster conversion.  This would mean that you need to be sure that the BMP
renderer is actually where you think it's installed.

Since the imagetoraster program is working on jpg but not on bmp, I'd
venture to guess that the bmp conversion program is breaking (the error
message kind of alludes to that as well).


> -----Original Message-----
> From: tech-pkg-owner@netbsd.org [mailto:tech-pkg-owner@netbsd.org]On
> Behalf Of Sanesh Bodasing
> Sent: Friday, March 30, 2001 8:38 AM
> To: tech-pkg@netbsd.org
> Subject: BMP format problem
>
>
> Hi Guys,
>
> I am having a problem printing BMP files with CUPS-1.1.6.3nb2. From the
> command line, the "lpr myfile.bmp" seems to go through without
> any problems,
> but nothing is sent to the printer. The job is logged on the web interface
> as "aborted". When restarting the job from the interface, you get "Error:
> The requested method is not allowed with the resource"
>
> Interestingly, when printing the file from GIMP, the job is logged on the
> CUPS web interface as "completed", although nothing prints. Also JPEG and
> PostScript files print fine.
> I am using NetBSD-1.5 on an i386 machine.
>
> I had the same problem using NetBSD-1.4.2 with CUPS-1.1 and thought the
> upgrade might solve it. The problem seems to be with the graphics
> libraries
> and the way CUPS interprets the BMP format.
>
> Any advice on solving this problem?
>
> Regards,
> Sanesh
>
>
>
>