Microsoft KB Archive/190438

LM1: “Archive is Not a Jar File” Viewing Animation in Netscape 4

PSS ID Number: Q190438 Article last modified on 07-22-1999

WINDOWS:1.0

WINDOWS

================================================================ ==

The information in this article applies to:

 == Microsoft Liquid Motion for Windows 1.0 == 

= SYMPTOMS =

When you view your animation in Netscape Navigator version 4.0 or later, you may receive the following error message:

Smart Update failed: Downloaded archive is not a JAR file.

After clicking OK, the Web page displays without the animation.

= CAUSE =

This behavior occurs when the Web server is not properly configured to serve the Lminstall.jar file. This Lminstall.jar file is necessary to install the Liquid Motion accelerator and Java player classes on the client browser.

= RESOLUTION =

To resolve this behavior, use one of the following methods.

NOTE: You should perform these procedures on the server that is hosting the Liquid Motion animation. If a Web Presence Provider (WPP) or Internet Service Provider (ISP) hosts your Web, please contact them.

Method 1: Add the JAR MIME Type on the Web Server
Edit the MIME types on the Web server and add the JAR (Java Archived Redistribution) format. To do this using an Apache or NCSA Web server, follow these steps.

NOTE: Because there are several versions of UNIX and several versions of the Apache and NCSA server, the following steps may be different on your computer. If they are, please consult your product documentation to complete these steps.

  Open the mime.types file in a text editor. By default, this file is located in the folder under the server root.   Add the following line: application/java-archive jar   Save and close the file.   Restart the Web server.   After you restart the Web server, view the animation using the Netscape Navigator 4.0 or later browser and a computer running Windows 95, Windows 98, or Windows NT 4.0. If you receive the same error described in the “Symptoms” section of this article, go to method 2. 

To add the JAR MIME type on servers that do not use the same mime.types files, you must add the MIME type using the interface that your Web server provides and perform these steps:

<ol style="list-style-type: decimal;">  Configure the MIME Type on your server by using the following settings:   Associated Extension: jar </li>  Content Type (MIME): application/java-archive </li></ul> </li>  Restart your Web server. </li>  After you restart the Web server, view the animation using the Netscape Navigator 4.0 or later browser and a computer running Windows 95, Windows 98, or Windows NT 4.0. NOTE: Do not view the animation from the same computer that is running the Web server. If you receive the same error described in the “Symptoms” section of this article, go to method 2. </li></ol>

Method 2: Configure the default MIME type
To configure the default MIME type on an Apache or NCSA Web server, follow these steps.

NOTE: Because there are several versions of UNIX and several versions of the Apache and NCSA Web server, the following steps may be different on your computer. If they are, please consult your product documentation to complete these steps.

<ol style="list-style-type: decimal;">  Open the Srm.conf file in a text editor. By default, this file is located in the folder under the server root. </li>  Find the line (not beginning with a comment tag or pound sign [#]) that begins with DefaultType. </li>  If this line is present, change it to the following: DefaultType text/plain If the line is not present, add it. </li>  Save and close the file. </li>  Restart your Web server. </li></ol>

To configure the default MIME type on servers that do not use the same Srm.conf files you must use the interface that your Web server provides.

Additional query words: 1.0

=
========================================================= Keywords : lmnscp Version : WINDOWS:1.0 Platform : WINDOWS Hardware : x86 Issue type : kbprb ============================================================================= Copyright Microsoft Corporation 1999.