Closed Bug 223431 Opened 23 years ago Closed 23 years ago

Firebird requires java plugin although it is already installed

Categories

(Firefox :: General, defect)

x86
Windows 98
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: asherman, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 If I open http://chem.kcn.ru/applets/mainapplet.html there will be "Click here to get the plugin", and if I click that firebird will search for application/x-java-vm plugin. But if by entering about:plugins I can see Java Plug-in File name: NPOJI610.dll Java Plug-in 1.4.2_01 for Netscape Navigator (DLL Helper) MIME Type Description Suffixes Enabled application/x-java-vm Java Virtual Machine for Netscape Yes Reproducible: Always Steps to Reproduce: 1. Install java plugin from Sun 2. Open http://chem.kcn.ru/applets/mainapplet.html 3. Firebird will require java plugin Actual Results: Requiring Java plugin already installed. Expected Results: Correct using Java VM plugin
Arkady, if you're still reading this, please check out the following page: http://plugindoc.mozdev.org/faqs/phoenixwin.html and look under the question: "How do I install the Java Plugin?" Apparently you may have to apply a registry patch to get Java to work with Firebird. It seems that if you've run the standard Mozilla browser in the past (which most people have at some stage), then the registry item most likely already exists. But if you don't have Mozilla as well, then the Java plugin fails to work. Lemme know if this works :)
Thanks a lot, it's worked after gegistry patch applied :). But better, I belive, is to check this registry key at the starting firebird and add it if necessary.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Yeah, I don't pretend to understand the way Firebird works, but I know they're moving towards an installer now. So maybe that'll stop it happening :)
You need to log in before you can comment on or make changes to this bug.