This does not seem to be too common a problem, unless you are like me and always like to have the latest update done to your system.
Joel Tanis wrote:
> I like, I like...
> I just can't get a "handle"; (Browser handle that is.)
> Am I missing something?
> Using Cosmo beta3 and Navigator 3.0; Win95.
[snip]
> * index.html loads smoothly, Cosmo plugin loads with embedded basic.wrl
> * editor window opens ok
> * editor works fine(I know, it's "alpha")
> * write to output window works
> * but vrml doesn't update, because...
> * Navigator Java Console says:
> Attempting to get Browser handle
> static getBrowser() call failed, attempting Javascript method
> Browser not available
>
> hmmmm.......seems my Browser has "wandered" off somewhere ;-)
> Any ideas? Suggestions? I'm not at "guru" level with Java yet, so I might
> be overlooking the obvious here. ;-)
Well you are not alone. This problem, as you will see below effects more than
just my applet. It effects anything that runs Java or JavaScript. Read on
for the solution
Here is my story..
My development system here is Cosmo Beta3, NS 3.01, NT 4.0 service pack 1. (hardware - P166, 64MB, Millenium 8MB etc)
Everything worked fine when I installed SGI's Cosmo 2a. At that stage I had NT 4 without the service pack. I updated to beta 3 (well many updates because I have an arrangement with them for alpha-beta test). These all worked fine. I installed the service pack. It stopped working.
Since then I have completely stripped the machine of all references to any and all internet references, This has included hand purging the system registries and deleting of all software, browsers, plugins, everything. I reboot the machine, install a new copy of NS 3.01 with default settings and then immediately install Cosmo beta 3, again with all defaults. Reboot machine when asked. Upon login in I immediately start NS, and load VermelGen. Not go, same error. I go through the same setup of all the usual customisations etc etc. Still no go.
I have tried the HTML file both with and without the MAYSCRIPT parameter and it does not work. I also tried just a very simple class file that contained the following code
Completely stumped, I go to the Netscape site to try and find answers. The closest answer that I can find is the following article in the tech information section. The URL is http://help.netscape.com/kb/client/961024-6.html
This is related to a Microsoft's update for Remote Process
Communication protocol.
After the installation of this update, Netscape's Java and JavaScript
don't work -- JavaScript doesn't work period, and Java fails with a
dialog box with text to the effect:
file java_30 could not be found in the CLASSPATH Your current
CLASSPATH variable is:
Obviously, the file is in the right location.
To check if you are affected, find a file called rpcrt4.dll on in
your windows/system directory, and right-click on it.
Click "properties". If your version is 4.00.953, you are affected.
To get Netscape working again, you will have to replace this file
with the older version.
If you installed cabinet file viewer (available on Microsoft's web
site) on your computer, you can extract the file rpcrt4.dll from
archive Win95_11.cab on your windows95 CD-ROM in WIN95 directory.
To install the file, you will have to place the "good" version in a
temporary location (C:\TMP will do). Restart the computer in DOS
mode. Change directory to C:\WINDOWS\SYSTEM rename the "bad" file
(REN rpcrt4.dll rpcrt4.953), and move the "good" file in its place
(MOVE C:\TMP\RPCRT4.DLL C:\WINDOWS\SYSTEM). Type "EXIT".
The reason for all this trouble is if a dll is active ("used by the
system"), you can not rename or replace the file.
Notice: this procedure may not work if your Windows partition is
compressed.
Java and JavaScript CLASSPATH error/problem
C:\Program Files\Netscape\Navigator\Program\java\classes\java_30 etc.
With NT 4 the same problem afflicts us except that the answer lies in getting the Service pack #2 installed on your system.
If you have NT 4 and service pack 1 you willNOT see output in the VRML window browser. You will see the same series of messages that was seen above. You must be running either the original version or service pack 2.
If we look at the silver lining in this black cloud - it forced me to write code that allowed me to keep working even in the absence of a browser. Hence you could theoretically run this using the AppletViewer (although I have never tried).
5 Jan 1997