Skip to main content

b08 - Can't enable the new-gen plugin even when all browsers closed

8 replies [Last post]
Joined: 2003-06-11

In the advanced section, check the Enable new gen plugin option. However, it always complains about browser windows open, even though there are none!

Thus, unable to activate the new plugin at all.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2004-03-16

Let me relate my own experiences on XP latest service pack and FF

1. Initial JRE install went awry because I first downloaded the b08 JRE, then the b08 compiler and did not immediately restart browsers. Reinstalled JRE after which, the JRE was OK.
2. Control Panel, Java, Advanced, JavaPlug In.
3. Can toggle ON just fine when FF is closed. Cannot toggle ON unless FF is closed.
4. The JavaPlugIn selection does indeed maintain its checked state between browser restarts.
5. Testing the java VM at
results in the error messages mentioned in previous messages on this forum.
6. Reminder, cannot toggle JavaPlugIn OFF while browser is up.
7. Close browser. Toggle JavaPlugIn OFF (i.e. unchecked). Restart browser.
8. When browser is restarted, can successfully test Java VM above URL

Best wishes getting a fast Java out,

Joined: 2003-06-16

Documentation on testing the new Java Plug-In is forthcoming. If you close all browser windows (esp. Firefox and/or the SeaMonkey office suite, and including anything that embeds IE for its help, such as the MSDN Documentation) and toggle the setting in the Advanced tab of the Java Control Panel, you should be able to switch back and forth between the new and classic Java Plug-Ins with no problems. This has been verified with the posted b08 bits on Windows XP. The behavior in b09 will be better, and will not require browsers to be closed in order to make the switch (although they will still need to be restarted in order for it to take effect).

In the Firefox family of browsers, the new Java Plug-In only works on Firefox 3. Attempting to use it with Firefox 2 will cause an error dialog to be displayed on Windows. This is the behavior in 6u10 b08. In b09 and the latest FF 3 the behavior will be better: if you run FF 2 you will get the old plug-in, and if you run FF 3 you will get the new plug-in.

Joined: 2004-02-10

Does it not work on Firefox 2 because of a limitation in Firefox, or in the plugin itself? Even when Firefox 3 comes out of beta, not everyone will upgrade.
It would be much better for Java if the new plugin ran on Firefox 2 too...

Joined: 2003-06-16

Limitations in Firefox. In order to make the new plug-in work in Firefox, we worked closely with for several months. Two public APIs on the browser side were needed (for better support of multithreaded NPAPI browser plug-ins, and for more powerful NPRuntime-scriptable plug-ins), along with a large code refactoring in the browser around Java/JavaScript interactions. We also found several bugs in the browser related to scripting plugins in general via NPRuntime. All of this work would have to be backported to Firefox 2. understandably doesn't want to do this as it will introduce risk into their stable train, and as the new plug-in project lead I agree with them. Eventually most people will update their browsers, and people who don't want to but who want the new plug-in will have an extra incentive to do so.

Joined: 2003-06-11

Latest FireFox Stable: Hardly old :) FF3 is not final yet, you know...

I don't see how it relates, can't find any processes for IE or FF :(

(To answer the question how) - it's in the Java Control Panel (you may need to run javacpl directly from jre/bin, there's another issue with it disappearing from the control panel). Advanced tab -> Java Plug-in node. Checking the checkbox is never persisted due to the above error.

Joined: 2004-11-15

If you are using FF 2.0, you should see an message saying that you will need FF 3.0. Yes, FF 3.0 is not final yet, but that is the constraint. I installed last night's FF's 3.0 build and have had success. On IE this should not be an issue. If you are using IE and still seeing this issue I would be interested in getting some more information from you.

b08 is the first build that contains anything related to the new plugin.This new feature is not yet complete, there are a number of issues, which we will be addressing in b09. When b09 is available we will have more information on the 6uN 'hub page' You are free to use the feature, just know that we are really holding back on looking for feedback on this feature until b09.

Joined: 2004-11-17

Which version of browser are you using? It is a known issue for old Firefox 2. It should work fine with IE and Firefox 3.

Joined: 2003-08-11

Forgive my ignorance, but how can someone tell that the new-gen plugin is being used and not the old one. I thought the new plugin is turned off by default. What do you do to turn it on? And on which browser versions can you do it? For instance I looked in the advanced options under IE6, there nothing there that says new plugin vs old plugin? Am I missing something? Also, is b08 the first build that has the new plugin?