start telling people to uninstall MSJVM without worrying about explaining to them unfounded "consequences" and other nonexistent nonsense.
We have been telling people to switch to Sun Java and keep it updated for a long time. (Those of us who believe in Java at all- there are those who recommend ditching it completely, of course.)
Nobody is saying anything other than that MSJVM is a security risk and has to go. I believe this whole thing started with me saying that Encyclopedia Britannica ceased to work when MSJVM was no longer present, even though Sun Java was (Yes, correctly) installed.
I also said that I ditched the program rather than have the security risk of MSJVM on my computer.
This doesn't seem to have been an unfounded consequence or non-existent nonsense. My point was that some applications may not work if MSJVM is removed, which has to be borne in mind when removing MSJVM, which, to repeat, I accept is vital for security.
You have made some stark claims here:
How does that effect your OS and other programs?
It doesn't, just install Sun's Java instead.
What are the dangers?
None.
I have simply made there may in fact be consequences to removing MSJVM. I was quite surprised at your reaction, considering that the Microsoft site says the same thing.
What software? You say some, show me a list that includes no workaround. I have no way to test EB to see if it will work with Sun's Java properly installed. This is the problem you are making declarations as if some huge list of applications exists that breaks. This not even remotely true. So far you have mentioned one unconfirmed application, that doesn't even relate to "some".
So again please provide proof of your claims.
You have NO proof it is dependant to begin with. You have no proof there are other applications out there that are.
I don't claim to be an expert here, but I believe that some applications are dependent on MSJVM.
It seems to be freely admitted by MS that developers may have some work to do in 'migrating MSJVM-based applications':
Third-party Java Runtime Environments These may also be an option. Be aware that these solutions are not supported by Microsoft. Depending on the amount of MSJVM-specific dependencies within the application (for example, WFC, JavaCOM, ms.*), there may be varying degrees of manual conversion that you will be required to perform.
The Microsoft Journal for Developers
http://msdn.microsoft.com/msdnmag/issues/04/10/EndBracket/This is perhaps why there may be a problem. Microsoft as usual did not implement specifications but decided to do things its own way:
Microsoft VM for Java
The Microsoft VM for Java provides a complete implementation of Sun's JVM specification. However, it provides extensions to the specifications that target Windows platforms. The VM extends the standard JVM to provide the capability to load component object model (COM) classes and expose COM interfaces of Java classes.
http://jdj.sys-con.com/read/36072.htmIt's not hard to find evidence that some applications have not been able to migrate:
Why the product is Free? What is the catch?
There is no catch. From the beginning of year 2004 Microsoft does not support its Java Virtual Machine (MSJVM) any longer. Since "ZBit Zip-Unzip Component lite" relies on MSJVM we feel that we can not charge money for product that requires a platform that is not being supported anymore. That is because honesty and integrity are fundamental principles of ZBit Inc. (see our mission statement). However, component still works fine on machines with MSJVM installed and many people find it very useful for basic zipping unzipping functionality on their web sites and in standalone applications. So, we decided not to discontinue the product but rather give it away for free.
http://www.zbitinc.com/faq.asp?p=2I respect your experience in the field of moving computer users away from MSJVM. I'm quite sure that any problems with applications ceasing to work are very, very rare and very, very minor.
However, as with my encyclopedia, it's not inconceivable that somebody might experience a problem. It don't believe it's worth making a big deal of the issue. Everybody here is in agreement that MSJVM has to go, and that there's no reason to keep it, even if it means finding a work-around for old software, or even ditching it completely.