Hmm, that link worked an hour or so ago.

The summary is, in the command line which you use to start JEmplode, add "-Dsun.java2d.d3d=false" after the command name "java".

/me goes and looks at the script I use to run JEmplode.

Ah, it's complicated, because Mike ships a long script that runs JEmplode. Now I think of it, I recall spending hours hacking at it to make it work. I think you can get it working by setting the environment variable "options" to "-Dsun.java2d.d3d=false" in the command's environment, like "options=-Dsun.java2d.d3d=false jemplode" (if you would normally type "jemplode" to run it), or equivalently, add a line "lax.nl.java.option.additional=-Dsun.java2d.d3d=false" (without the quotes, of course) to the JEmplode.lax file in JEmplode's install directory (e.g. for me, it's /usr/local/JEmplode_2.0/JEmplode.lax).

If you're on a non-Unix platform (which you must be, to be seeing a Windows driver bug), I'd recommend the latter.

Caveat: I haven't tested this (and can't, without buying an OS I don't want!).