This bug is reported on behalf of Netiva Software. The same bug was reported
via JDK 1.1 Bug Report Web Page by Netiva last week:

We are doing a very simple print test based on the sample code in the 1.1
JDK. When trying to acquire a graphics context from the printer we receive
the following:

c:\jdk1.1\java\test\print>java TestPrint
loading C:\JDK1.1\JAVA\BIN\..\lib\awt.properties
pJob.getPageDimension = java.awt.Dimension[width=816,height=1056]
pJob.getPageResolution = 96
java.lang.InternalError: printing StartPage failed
        at sun.awt.windows.WGraphics.<init>(WGraphics.java:55)
        at sun.awt.windows.WPrintGraphics.<init>(WPrintGraphics.java:39)
        at sun.awt.windows.WPrintJob.getGraphics(WPrintJob.java:66)
        at TestPrint.printIt(TestPrint.java:125)
        at TestPrint.action(TestPrint.java:109)
        at java.awt.Component.handleEvent(Component.java:1854)
        at TestPrint.handleEvent(TestPrint.java:84)
        at java.awt.Window.postEvent(Window.java:288)
        at java.awt.Component.postEvent(Component.java:1459)
        at java.awt.Component.postEvent(Component.java:1459)
        at java.awt.Component.dispatchEvent(Component.java:1356)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:109)

One interesting note is that the page resolution came back 96dpi (which is a
screen resolution) rather than the expected 300 or 600dpi. 816x1056 pixels
for page dimension works out to 8.5x11" at 96dpi. We do not have the source
for sun.awt.Windows.WGraphics.java so cannot research this problem any
further. We have attached the code for the test program (see /home/phyllisc/
netiva/TestPrint.java)

Here is the user environment:

JDK Build: 1.1 Beta 3
Environment: Windows NT 4.0 (Workstation)
Printer: HP LaserJet 5M accessed via TCP/IP (Windows) network
Classpath: c:\jdk1.1\java\lib\classes.zip

phyllis.cheng@Eng 1997-02-18

--------------------------------------------------------------------------------Netiva tested out the JDK 1.1 FCS with the same test program and reported that
the GPFault in WINAWT.DLL on Windows95:

JAVA caused an invalid page fault in
module WINAWT.DLL at 0137:01e3c684.
Registers:
EAX=00000000 CS=0137 EIP=01e3c684 EFLGS=00010202
EBX=00e68448 SS=013f ESP=0237fe20 EBP=0237fe2c
ECX=006bfab8 DS=013f ESI=00e66dd0 FS=0dc7
EDX=0237ff4c ES=013f EDI=0079b8c0 GS=0000
Bytes at CS:EIP:
8b 08 8b 51 14 8b 1a 8b 4b 08 85 c9 74 1b 8b 4d
Stack dump:
006bfae0 006bfae4 006bfab8 006bfaa8 01e4d09d 00e68448 00e66dd0 0000001f
00000033 006bfae0 006e23fc 10038472 006bfae0 0237ff04 006bfab8 0237ff94

On Windows NT 4.0, the same test program did not GPFault in WINAWT.DLL,
but it also did not work:

calling getPrintJob
java.lang.InternalError: printing STARTDOC failed
        at sun.awt.windows.WGraphics.<init>(WGraphics.java:56)
        at sun.awt.windows.WPrintGraphics.<init>(WPrintGraphics.java:43)
        at sun.awt.windows.WPrintJob.initJob(WPrintJob.java:54)
        at sun.awt.windows.WToolkit.getPrintJob(WToolkit.java:434)
        at TestPrint.printIt(TestPrint.java:118)
        at TestPrint.action(TestPrint.java:107)
        at java.awt.Component.handleEvent(Component.java:1936)
        at TestPrint.handleEvent(TestPrint.java:82)
        at java.awt.Window.postEvent(Window.java:416)
        at java.awt.Component.postEvent(Component.java:1543)
        at java.awt.Component.postEvent(Component.java:1543)
        at java.awt.Component.dispatchEventImpl(Component.java:1425)
        at java.awt.Component.dispatchEvent(Component.java:1361)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:58)

phyllis.cheng@Eng 1997-02-19

Netiva just reported back that the printing bug have not been fixed in JDK1.1.1
(March 5 build). See the attached e-mail from Netiva Software. Please re-evaluate it and re-fix it. Thanks!

phyllis.cheng@Eng 1997-03-13