Based on the info at :
http://java.sun.com/javase/6/webnotes/install/system-configurations.html
Those with Win XP SP2 or "newer", should be running the 1.6 series;
those with Win XP SP1 or "older", should be running the 1.5 series .
"Mixing" the "release dates" of the 2 different Series should not be done
to determine IF you have the latest version .
Spiritsongs, this is what is strange… I can’t understand that the official site does not have version 6… we can only get it in third party sites… I can’t understand…
I consider the "Official" site to be :
http://java.sun.com/javase/downloads/index.jsp , which I got from
"Corrine", the former Administrator of the Lavasoft Ad-Aware Support
and presently a Microsoft Most Valuable Professional . It lists "JRE 6 ",
but if one is not careful, may select one of the JDK 6 versions . Since one
MAY select the incorrect version, I prefer to use the majorgeeks site .
I consider www.java.com to be a "semi-official" site, which currently
is offering only the "older" JRE 5 ( 1.5... ) .
Spiritsongs, I agree in your user point of view. I thank you for your effort as a Java user like me.
But, thinking in the Java Company… I can’t believe such a behavior… it’s weird, bizarre…
I can’t reconcile the fact that 1.5.11 was released after 1.6 with still calling 1.6 the most current version unless they serve different purposes. Is it possible 1.6 is for Vista while 1.5.11 is for XP?
And it seems logical that the Sun Microsystems site would make the current version the easiest to find while making roll back versions more difficult to locate. Yet they continue to show 1.5.11 as the most current version.
A word of caution when using 1.6, I have hardware DEP enabled on my computer, When I tried version 1.6 I couldn’t even start IE7 without getting DEP warnings which caused IE7 to terminate. Rolling back to 1.5.11 fixed the problem.
I don’t know if it was just my PC, but I thought I would give a heads up to everyone.
I did read somewhere (can’t find the site) of Java 6 causing display problems so maybe they’ve gone back to 1.5.xx temporarily until these issues with 6 are resolved. But this is just a guess.