microsoft vm update

[Guest]

In my automatic updates is the update for the microsoft VM. When I try to
install this update it says that it will only update over and existing
version of microsoft VM. How do I get an existing version, or what else do I
do?

 

[darkrats]

I thought that MS VM had been discontinued. Can you post the KB number of
that update, so I can check out it's home page?

 

[Rock]

In my automatic updates is the update for the microsoft VM. When I try to
install this update it says that it will only update over and existing
version of microsoft VM. How do I get an existing version, or what else do
I
do?

MS no longer supports it's VM since service pack 1, it was included in the
original SP1, but subsequently removed and the service pack reissued as SP1a
due to loosing their suit with Sun Microsystems. The MS VM is vastly out of
date and full of security issues. Don't use it. Get the Sun JVM. The
latest version is 6.

http://www.java.com/en/download/manual.jsp

 

[darkrats]

The first post mentioned that there was a MS VM Update included in the
Auto-Updates (if I read it correctly). This would indicate that MS is still
supporting it in some way.

 

[Dennis McCunney]

The first post mentioned that there was a MS VM Update included in the
Auto-Updates (if I read it correctly). This would indicate that MS is still
supporting it in some way.

Doesn't matter if they do or not. Sun sued Microsoft in the first place
because Microsoft made changes in their JVM that were incompatible, and
only worked in Internet Explorer and on Windows OSes. The essence of
Java is "Write Once, Run Anywhere", and properly written Java code
should execute the same way on any machine with a JVM.

Java is supposed to be cross-platform. Microsoft attempted to create a
proprietary fork of it that only worked on Windows. No surprise, since
what Microsoft wants is that *every* computer run Windows as the OS and
use Intel architecture CPUs. No surprise that Sun objected, since they
have their own OS (Solaris), and processor architecture (SPARC), and
there are lots of other things out there that aren't PCs, don't run
Windows, but *do* run Java, and there are lots of Java developers who
don't want to maintain two separate versions of their code. Sun finally
revoked MS's license to offer Java, which is what the suit was about.

Even if you can still get the JVM from Microsoft, Sun's version is
currently at 1.6, with continual security and performance enhancements,
as well as new core language features. I very much doubt MS has been
maintaining thier JVM to track the current standard, and I suspect a
fair amount of current Java code would not run correctly in it. (Lots
of Java apps I've seen want at least v1.4.2 of the JVM to work correctly.)

If you do anything that needs Java, get the current VM from Sun. If you
have the Microsoft JVM installed, remove it, and use Sun's instead.
______
Dennis

 

[Lem]

The first post mentioned that there was a MS VM Update included in the
Auto-Updates (if I read it correctly). This would indicate that MS is still
supporting it in some way.

Or that the OP has re-installed and is applying post-sp2 updates. The
last MSVM update is MS03-011 from April 2003:
http://www.microsoft.com/technet/security/current.aspx

 

[Rock]

The first post mentioned that there was a MS VM Update included in the
Auto-Updates (if I read it correctly). This would indicate that MS is
still supporting it in some way.

It's not being supported beyond the initial release which comes with the
Gold version of XP, and that update. Let me repeat, it is not being
supported.

 

[Guest]

It's not being supported beyond the initial release which comes with the
Gold version of XP, and that update. Let me repeat, it is not being
supported.

That is WRONG. MSJVM is supported on XP Pro SP2 and and all other Microsoft
OSes (that are supported) through December 31, 2007. Plus, it still works
just fine on no longer supported OSes like 98SE where Sun Java is a mess to
use.

That update in Windows Update is legit. It's for the stupid changes on the
Mainland this year for DST. We don't have DST where I live so I didn't need
the patch. Microsoft's agreement with Sun MicroSystems in April 2005 allows
for MS to patch and support the final version of JVM 3810 through December
31, 2007 but does not allow for MS to create new versions.

I detest Sun Java and I use JVM on my XP Pro SP2 machine. I will really hate
to see Jan 1 2008 when I am forced to use Sun Java. There are a LOT of users
like me who still use JVM exclusively.

I noticed this thread today only because I did a search to find posts about
removing JVM. Microsoft has removed the Removal Tool and has a harsh page up
about how only IT managers can get the Removal Tool. Gee, so what do all us
home users who still use JVM do? I see a lot of J++ dependencies on JVM when
I run the MSJVM Diagnostic Tool. What are we supposed to do about all those?
Are we supposed to just leave JVM installed after Jan 1 2008? But also
install Sun Java?