The following notes apply to use of this release on Windows Vista platforms.
a.. On Windows Vista, there is a more restrictive sandbox for signed
applets. A user has fewer privileges than if they were running on another
Windows OS.
On a Windows OS other than Windows Vista, when running a signed applet, a
user is prompted with a security warning dialog box and must respond. If
"Yes" is clicked, the applet will have AllPermissions to run on the user's
machine. This includes permission to write/delete a file from the local
disk.
On a Windows Vista OS, this is no longer true. Instead, AllPermissions is
limited to Java Applet scope, not Windows scope. Because a process running
in IE has a low integrity level, it will not be able to write/delete a file
from a medium/high integrity level directory.
b.. A signed JNLP application can run only with medium integrity. Granting
AllPermissions in a Java Web Start application only permits the Security
Manager to allow operations that it would otherwise deny by throwing
SecurityExceptions. It does not in any way elevate the permissions a user or
a process has on the system.
c.. Due to limitations of Windows Vista, Java Plugin will no longer be
able to write any file into the jre/lib/ext directory from IE protected
mode. Java plugin extension install will not work as it does on other
Windows OS platforms.
d.. On Windows Vista the use of DirectDraw for hardware acceleration is
currently disabled by default because of incompatibilities with Vista's
Desktop Window Manager.
The -Dsun.java2d.noddraw=false property can be used to re-enable the use
of the DirectDraw pipeline. However, this is not recommended due to
rendering artifacts and performance problems. To also enable the Direct3D
pipeline, a combination of the aforementioned flag and -Dsun.java2d.d3d=true
should be used.
See bug report 6343853 for more information
