That would be the 3810 build of the MSVM?
It still has security concerns - ones that will *never* be fixed,
given as how it is obsolete & unsupported by the manufacturer
(for sime time now). MS' latest advice on Java (I saw) was..
"Get it from Sun".
Well, most software that requires Java installs Sun JRE ..
If Java software is launched(/installed) using Java Web Start,
it will use any suitable JRE found. Here are some examples.
<
http://www.physci.org/jws/>
(Note that JWS is Java 1.2+ - no 1.1 VM understood the
JNLP launch files)
..and in most cases
this is *not* the latest version. ..
That sounds more like a Java app. wrapped up as a Win.
installer, with a JRE co-bundled. That is not the preferred
way to distribute Java software, JWS is. Any developer
that appears on the comp.lang.java.* usenet groups asking
how to 'make an exe' is strongly encouraged to try JWS
first.
..Therefore, I remove that JRE stuff any-
way after the automatic installation. In many cases, the software runs
fine with the "MS Java VM" only.
I find that hard to believe. There has been very little
AWT GUI work done in the last few years, most of
the Java GUIs of recent times are coded using Swing
(Java 1.2+).
..There was some poor software insisting
in the existence of a particular and outdated(!) Sun JRE version ..
That is suspicious. Sometimes a Java app. will require
reliance on earlier buggy behaviour that has been fixed,
for quite innocuous reasons, but that indicates poor design
or maintenance of their own code. Even if the reasons for
using an earlier JRE are innocent, it limits the ability of the
end-user to use the JRE with the latest security updates.
..and that
software was subject to be removed instantly as well.
That sounds a good plan. I would not tolerate any Java
app. that requires a specific earlier version.