Reqiurements for running the
If the Applet is not loading,
there are two requirements that you need to have:
- Make sure you are working in a browser that can support muView
Netscape: 4.77 (Linux)
7.02 (Linux i686, X11) - Mozilla/5.0 - java 1.5.0 plugin;
7.02 (Mac OS X) - Mozilla/5.0 - java 1.5.0 plugin;
Safari: 1.0 (Mac OS X) - java 1.5.0 plugin;
-You need to have the full Netscape version and the
plug-in enabled. To enable your java plug-in, go to
'Enable Java'. For more information on java plug-ins for your
platform, you can visit: Plug-in-doc.
This site will guide you through the java plug-in installation and the
browser set-up processes.
- Generally, all new versions of
Netscape should easily support this Applet. So if your browser is not
in the list above and you don't feel like downloading other versions,
you can still try to go through the steps below to try to enable the
muView Applet to load on your browser.
- You need to copy the .java.policy file into a specific place on your
|Where to save the .java.policy file
(home directory of your
|Mac OS X
place the file in your home directory. MAC OSX has a Unix-like
user home directories.
One way to do
this is to open a terminal window, which runs the Unix-like tcsh shell.
This starts you in your home directory. Then you can
edit (with vi, or another text editor)
the .java.policy file and cut and paste the above
contents into it.
|Windows 95/98 (single-user)
|Windows 95 (multi-user)
|Windows NT (multi-user)
Note that the '.java.policy' file allows all the permissions for any
applet to load in your browser. It looks like this:
If you want to allow your browser to open only the muview applet, you
need to edit the '.java.policy' file and set a code base where the
muview project is located.
Here are a few examples (note that you can have all of the examples
below all in the same '.java.policy' file which will enable all of the
applets that they refer to.
This is when the project is on your own machine (you must use
the 'file:///...' indentation in order for it to work)
These ones below will read the files from the musr.org and
This File is also included with the downloadable muViewPackage (see
for more details)
Note that when you are saving the .java.policy file as a text
file, some operating systems may append a .txt extension. If this
happens, you must rename the file and remove the extension.
Notes For Windows
In the various Windows operating systems, there is a
setting which can hides the file extension. Go to the "Folder Options"
settings, and make sure the box labeled "Hide file extensions for known
file types" is NOT checked. You can get to the "Folder Options" from
the Windows Explorer "View" menu on Windows 98, or the "Tools" menu on
Windows NT and 2000.
If you do all of the above and the "Save As" buttons still do
not become active, there is one more thing you can try. You can tell
the Java Plug-in exactly where the .java.policy file is by doing the
1. Open the
Java Plug-in Control Panel and find the entry box for "Java Runtime
(See step 1. in the plugin memory boost page for how to get to the
Plug-in Control Panel.)
2. In the area where
enter "Java Runtime Parameters", you can put the following statement:
assumes that you put the .java.policy file in C:\WINDOWS.
-Note: The .java.policy file will not
make any other system permissions
than the ones mentioned above. If you feel unsafe about having this
policy file in your home directory, you can erase it (or copy it into a
different directory) when you are done with using the muView.