Re: java virtual machine

From: Carey Frisch [MVP] (mrxp2004_at_nospamyahoo.com)
Date: 10/06/03 

Date: Mon, 6 Oct 2003 08:00:00 -0500

Download & install MS Virtual Machine Build 3805.
Then visit the Windows Update website to obtain the
security updated version (Build 3810).
http://www.virtualmachine.tk/ 

-- 
Carey Frisch 
Microsoft MVP
Windows XP - Shell/User
-------------------------------------------------------------------
"Travis" <thill@bpatpa.com> wrote in message:
 news:075701c38c08$927df0a0$a001280a@phx.gbl...
I have a user who keeps getting an error message about 
java virtual machine and when they go to download they 
get taken to the below site.  Anyone have any knowledge 
on this and an easy fix?  Thanks
Transitioning from the Microsoft Java Virtual Machine
July 23, 2003
Due to a settlement agreement in January 2001 that 
resolved a legal dispute with Sun Microsystems, as of 
January 2004 Microsoft will no longer be authorized to 
support the Microsoft® Java Virtual Machine (MSJVM). 
Microsoft will not be able to address potential security 
issues, nor will the company be able to make any product 
enhancements. In preparation for this change, Microsoft 
began phasing out the MSJVM in its products after the 
settlement was reached. Going forward, the MSJVM will not 
be included in any future Microsoft products.
Minimizing Impact for Our Customers
Microsoft's top priority is to provide its customers a 
computing experience that is trustworthy. As part of that 
effort, the company is committed to helping customers end 
their MSJVM dependencies and move to alternate solutions.
Microsoft will offer customers running the MSJVM several 
tools and options for transition and migration. As those 
options are built, the primary focus will be minimizing 
customer inconvenience.
The transition and migration options Microsoft offers 
will be customized to address the needs and circumstances 
of different types of customers. Depending on the 
specific customer situation, recommended courses of 
action may range from doing nothing at this time to 
identifying and addressing a customer's MSJVM dependency.
Steps for Developers, IT Pros, and Business Customers
Microsoft has identified steps that developers, IT 
professionals, and businesses can take in order to make 
the transition and migration as convenient as possible:
Start work now to understand your MSJVM dependency. 
Decide on your transition and migration path. 
Start migration and testing. 
Microsoft will provide transition and migration tools and 
guidance to system integrators, value-added providers, 
and others who offer services for small businesses and 
other customers.
In the near future, Microsoft will have tools and 
guidance available to developers and IT pros on 
Microsoft.com and MSDN®. Beta versions of some of these 
tools are already available.
Steps for Businesses That Redistribute the MSJVM
Microsoft recommends businesses that redistribute the 
MSJVM in their products make their transition as soon as 
possible. Microsoft is also formulating a strategy to 
help independent software vendors through the MSJVM 
transition and migration process. Information for 
businesses that redistribute the MSJVM will be available 
at this site in the near future.
Transition and Migration Options for Business Customers
There are several migration options available for 
business customers:
Migrate to .NET. In July 2002 Microsoft released Visual 
J#® .NET, a development tool for building applications 
and services on the Microsoft .NET Framework. This tool 
offers a simple way to take existing Microsoft Visual 
J++® or Microsoft SDK for Java applications and move them 
to the .NET Framework while still retaining the Java 
language syntax. J# Browser Controls (JBC) round out 
support in Visual J# .NET for migrating applet code. In 
addition, in February 2002 Microsoft announced the Java 
Language Conversion Assistant (JLCA). It automatically 
converts most existing Java-language source code into C#, 
converting both language syntax and library calls. 
Migrating to .NET may require access to source code. 
Migrate to other rendering technologies. Although 
Microsoft cannot vouch for the security and reliability 
of solutions offered by other companies, several offer 
rendering technology that can be viewed in a number of 
browsers. Technology options include Microsoft ASP.NET, 
DHTML, Macromedia Flash, and others. Migrating to other 
rendering technologies requires access to source code. 
Lock down Internet Explorer security zones while 
continuing to use the MSJVM. Locking down security zones 
allows for limited usage of the MSJVM even after it 
becomes unsupported while helping to limit security risks 
by restricting the use of MSJVM to specific sites. This 
can be done in parallel with other migration options and 
can be performed today by IT professionals. This option 
will also be addressed in the forthcoming Microsoft Java 
Virtual Machine Transition Guide. 
Switch to a third-party Java Run-time Environment (JRE). 
Although Microsoft cannot vouch for the security and 
reliability of solutions offered by other companies, non-
Microsoft solutions are available. Customers choosing to 
explore such solutions should engage in testing prior to 
pursuing this migration path. 
Microsoft strongly recommends that an IT professional 
perform a dependency analysis specific to your 
implementation, regardless of your solution choice. Any 
solution will require testing, and understanding the 
range of systems will greatly improve the results of 
subsequent testing.
Transition and Migration Options for Consumers
There is no immediate call to action for consumers and 
other non-enterprise users. Microsoft is working to offer 
such transition options, and updates to address this 
issue will be available in the future.
Transition and Migration Tools, Utilities, and Solutions
Several tools and utilities to assist customers with 
their transition and migration plans are available now or 
are in development:
MSJVM Transition Guide (Draft Version) 
This guide walks developers and IT pros through various 
transition options.
 Get the draft version of the MSJVM Transition Guide (476 
KB Adobe Acrobat file / 2.3 min @ 28.8 Kbps) 
J# Browser Controls (JBC) 
J# Browser Controls recompile applets to run on the 
Microsoft .NET Framework. The beta version is available 
now; final release is scheduled for late this year.
Get the J# Browser Controls Beta 
Java Language Conversion Assistant 2.0 (JLCA) 
The JLCA helps convert Java applications to C#.
Get the Java Language Conversion Assistant 
Internet Explorer Security Zone Lockdown Solution 
As mentioned previously, IT pros can today lock down 
Internet Explorer security zones to restrict the use of 
the MSJVM. Additional guidance will be provided in the 
forthcoming Microsoft Java Virtual Machine Transition 
Guide.
Diagnostic Tool 
A beta version of the Diagnostic Tool for the Microsoft 
VM, which is designed to help customers understand their 
MSJVM dependencies, will be released in late 2003.
For More Information
Customer fact *** on the removal of Java from Microsoft 
Windows® 
Visual J# .NET 
MSJVM-related security bulletins