18 years ago
17 years ago


(Reporter: gdresch, Assigned: dcone)



Firefox Tracking Flags

(Not tracked)




18 years ago
Build ID 2001091812, emxrt version 0.94, OS/2 Warp4 , Fixpak 5

Clicking the print icon or selecting Print... from the File menu produces a 
Print queue popup allowing printer selection and print job properties, however
nothing is printed and no files are sent to the print queue.
Printing is ok from all other applications.
Can you please give more information on the printer and driver?

Another user that reported this problem was able to fix it by switching to a 
later driver or another printer.

Comment 2

18 years ago
also try on a recent build....we made some fixes to Win2K printing last week.
which may not affect your problem.

Comment 3

18 years ago
please re-install the driver and try again.

printing is working for everyone else.

Comment 4

18 years ago
Printing is not working for me. Same build; I'm using Warp 4, FP15, and a
Lexmark 5700 printer with driver version 2.513. I click on print, it defaults to
the Lexmark, I click on OK, and nothing whatsoever happens. No job appears in
any print queue.
Here is a post from the newsgroup"

>  0.9.4 build 2001091812 like still does not print (to my 
> physical printer).  Printer is a Lexmark Optra 310 with Lexmark's 
> drivers - both PCL5 and Postscript.  OS/2 is Warp 4 with FP15.
[rest of auto citation cut]

  Something I didn't think of when I posted the above.  Creating another 
print object with OS/2's HPLasjet driver allowed the zilla to print! 
 The Lexmark responds to HPLaserjet code.

  Now the question is what's wrong with the Lexmark driver?

Victor Bien
Fix checked in.

Commented out extra BeginDocument in nsDeviceContextOS2.cpp.

Hopefully this won't break anything.
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 7

17 years ago
Graham, please try again now with this fix...let us know if it works for you
now..also mark this bug VERIFIED-FIXED.

Comment 8

17 years ago
Michael, no response from Graham, can you verify this one?

This is definitely working now for us with this driver.
You need to log in before you can comment on or make changes to this bug.