Strange article from Microsoft?

  • Thread starter Thread starter George Hester
  • Start date Start date
Java is not and has never been MS's product, they licensed it
from Sun Microsystems. In usual MS fashion they implemented
"improvements" to Java which rendered standard Java
incompatible. Sun sued MS and won their case. The ruling
requires MS to stop shipping Java with Win2000.

Use Sun's Java, it's better anyway:
http://java.sun.com/j2se/1.4.2/download.html

Rick

http://support.microsoft.com/default.aspx?scid=kb;en-us;818421

I thought msjava came with Windows 2000. I thought any change to msjava.dll in Windows 2000 required a Service Pack installation.
Is it true that Windows 2000 will accept a JVM installation from any other source then a Windows 2000 Service Pack? And since W2K
came with MSJava why would this article "fix" anything? Thanks.
 
See http://www.microsoft.com/mscorp/java/faq.asp

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.


http://support.microsoft.com/default.aspx?scid=kb;en-us;818421

I thought msjava came with Windows 2000. I thought any change to msjava.dll
in Windows 2000 required a Service Pack installation. Is it true that
Windows 2000 will accept a JVM installation from any other source then a
Windows 2000 Service Pack? And since W2K came with MSJava why would this
article "fix" anything? Thanks.
 
Gee I don't know Rick. I have msjava that works fine and I am developing with Sun's j2sdk with no issue "yet." Sun has improved thier plugin that is for sure. Too bad no major browser supprts Java 2. I doubt they ever will. Because msjava is different then Sun's is not what that article was about. I thought it was about putting msjava in Windows 2000 which is already included in Windows 2000 and my understanding is that msjava cannot be installed or updated outside of a Service Pack release.
 
Thanks for that article Marc.

"Are you running a version of Windows (Windows 95, Windows 98, Windows 98 Second Edition, Windows Millennium Edition, Windows 2000 Professional, Windows NT® 4.0, or Windows XP) on your computer?
If yes, then you probably have MSJVM installed on your computer."

This is what I was referruing to. Windows 2000 already has msjava installed. It came with the operating system and is a system file. It cannot be removed (in the normal sense of the word) AND it cannot be installed or updated outside of a Windows 2000 Service pack. That is what makes the article I referred to so "weird." It cannot be done as stated in that article in Windows 2000. Right? And in fact if tried the user stands a good chance of corrupting MSJVM in their system.

I am not one that thinks everything bad about the MSJVM. In my book it was a much better Run-time environment than Sun's. One example no nag. As was true with Sun's. Sun has decided to remove the nag. And without that I believe it stands a good chance of success. We'll see.
 
George Hester said:
I thought msjava came with Windows 2000. I thought any change to
msjava.dll in Windows 2000 required a Service Pack installation. Is it
true that Windows 2000 will accept a JVM installation from any other
source then a Windows 2000 Service Pack? And since W2K came with MSJava
why would this article "fix" anything? Thanks.

Actually, msjava has been updated a couple of times n between service
packs. I have three such updates stored away. The article seems to be a
clumsy description of a mechanism to force an update to the latest version
of msjava. I wouldn't bet on it working, even before the cutoff date.
 
George Hester said:
This is what I was referruing to. Windows 2000 already has msjava
installed. It came with the operating system and is a system file. It
cannot be removed (in the normal sense of the word) AND it cannot be
installed or updated outside of a Windows 2000 Service pack.

Sure it can. Any Windows component can be replaced if it's properly
packaged. Both Microsoft and non-Microsoft products that use Java were
typically accompanied by an installer package for the for the JVM so that
it could be installed on the target machine if not present or upgarded to
the required version if out of date. That won't be the case much longer.
 
Oh OK. Yes I know about that with System files. It seems to me though that msjava in the Visual J++ CD-ROM is not going to be of a higher version then that in Windows 2000 SP4. Following this article is a sure-fire way of hosing the client's MSJVM. Weird article.
 
Me NEITHER. Weird article. It almost looks like it is an honest attempt to hose Windows 2000'ds MSJVM. I know the installer technology should stop it from installing but I am pretty sure Visual 6 J++ did not use that technology.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top