Build  : 'L'
OS     : Win95/98  (Sol, NT...ok)

Everything is printed in B&W  on 95/98.  No levels of gray to represent color.

See attached testcase.
===============
This problem appears specific to PCL printers on win95/98.
The printers are not colour printers.
The same code works fine on NT
There are two different manifestations depending on whether the page
is printed using the raster or path graphics implementations.

If the raster path is invoked inside the implementation the page is
completely mangled with the scan stride appearing incorrect.

This is true as far back as 1.2FCS.

In kestrel beta, images can now be printed through the path graphics pipe.
There the page appears correct in pixel alignment, but a thresholding effect
is now apparent which makes the image pixels either black or white, rather
than using the printer's resolution to create a greyscale effect.


  xxxxx@xxxxx   2000-08-11

We are experiencing problems printing images (PNG, JPEG, GIF) from an
applet running inside Java Plug-in 1.3 on Windows95 machines. Our
problems range from "no graphics at all" to "very unusable quality
images". The printers are of PCL type. The same applet prints 
beautifully from NT 4.0 boxes to the same printers.

This internet application is aimed at our 43 million members who have
low end deskjet printers that do not have postscript capabilities.
Case in point is an HP DeskJet 950C Color printer.

The text on the page prints very well on all printers tested so far.
The rectangle around the image (drawn with a drawRect) shows up in all
cases.  The image does not.  

List of printers reporting problems:
HP 950C Color DeskJet (majority at beta sites - no image at all)
HP 2100TN (no image at all)
HP LJ3 Laser B&W (no image at all)
HP LJ5N Laser B&W  (no image at all)
HP 4500N (works well with a PS driver, prints very bad graphics with a PCL 
driver)


Please find attached a testcase which demonstrates this problem.
( xxxxx testcase.tar.Z - you will have to supply your image to test this applet.)
===========================

  xxxxx@xxxxx   2001-03-14
Verified on Ladybird build 14 with win98/95.
===========================

N/A

This is under investigation, but what is in kestrel beta is arguably a
real improvement over what was the results for 1.2FCS and 1.2.2, so fixing
this is not urgent for kestrel beta


Cause: Apparently, some Win 9x printer drivers cannot handle 32-bit top-down DIBs and/or new bitmap header.  
Fix: Use the old Bitmap header and 24-bit bottom-up DIBs.   This is more of a workaround to accomodate these printer drivers' lack of capability.   xxxxx@xxxxx   2000-09-07

My colleage and I have also experience this problem on a 
Fargo model 4250 printer in Windows 98. Windows NT works 
flawlessly. This is important because many of our clients 
use this model of printer under Windows 98.

Jacob Lewallen, PhotoLynx Inc.

I'm the colleage Jacob speaks of... we've given up on Sun 
and we're writing our own native printer.  Just for the 
record, we're using 1.1.8 and the problem is there too.  
Our problem may not be the exact same problem, but it sure 
sounds like it... this is what happens:  When an image is 
drawn to the printer, any pixels that are white or 
transparent show up correctly (no ink goes down there) 
however, any pixel that is not white or transparent gets 
set to the color of whatever setColor was last.  So our 
wherever a graphic was is a box that is filled w/ the the 
last setColor.  

Aaron Jensen, PhotoLynx, Inc.

   I also have run into this problem.  To make matters 
worse, I cannot find any information on how to implement 
the specified workaround.  Could someone who knows please 
send me the info?
Thanks very much in advance.
P.S. If anyone is interested in earning some Duke Dollars, 
my question is also posted in the community discussion 
forum under AWT, search "print", sort by date (May 6, 2001)

AlanSmoke1 here again trying to get my e-mail link to work

Oh well.  Here it is: smokefamily@hotmail.com  
By the way, my forum message was accually placed on May 9th.

  Arg!! Something is wrong.  Try this.

Hip-hip and horay!  I finally figured it out.  Dunce that I 
am, I did not realize that ladybird was accually JDK 1.3.1. 
Now that I am using it everything works fine.