FULL PRODUCT VERSION :
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)

FULL OS VERSION :
 customer  Windows XP [Version 5.1.2600] (Service Pack 1)

EXTRA RELEVANT SYSTEM CONFIGURATION :
 customer  Pentium  customer  (993 MHz)
1.00 GB or RAM
ATI Radeon 9700 PRO video card with dual monitor support

A DESCRIPTION OF THE PROBLEM :
When running a Java applet from Internet Explorer or Mozilla using Sun Microsystems' Java Plug-in 1.4.2 on the secondary monitor, the web browser will freeze if the screen is locked then unlocked.  This problem does not occur when the web browser window is on the primary monitor or on either monitor of a system using two NVIDIA Riva TNT2 cards and Windows 2000.  This problem does not occur if Direct Draw is disabled for off screen images by using the command line option -Dsun.java2d.ddoffscreen=false.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1) Download the Java plugin from java.sun.com
2) Open a web browser window and move it to the secondary monitor
3) Go to http://java.sun.com/products/plugin/1.4.2/demos/jfc/Java2D/Java2Demo.html and wait for the example applet to load
4) Press ctrl+alt+delete and choose "Lock Computer"
5) Press ctrl+alt+delete and enter password to unlock screen


EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The correct result would be for the applet to continue to run correctly.
ACTUAL -
The observed result is that the applet and web browser window stop responding.

REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
This behavior can be demonstrated with the applet at http://java.sun.com/products/plugin/1.4.2/demos/jfc/Java2D/Java2Demo.html
---------- END SOURCE ----------

CUSTOMER SUBMITTED WORKAROUND :
Use command line option -Dsun.java2d.ddoffscreen=false
(Incident Review ID: 190781) 
======================================================================

N/A

This bug was just filed and fixed (in an upcoming build of 1.5) this week.  See 4916767 for more details.   Verified that the fix to that other bug also fixed
the situation described in this bug.

Closing as a duplicate of that (slightly) older bug.

  xxxxx@xxxxx   2003-09-04