Closed Bug 18248 Opened 25 years ago Closed 25 years ago

OJI does not work on Windows

Categories

(Core Graveyard :: Java: OJI, defect, P3)

Product:
Core Graveyard
Component:
Java: OJI
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: pawyskoczka, Assigned: ryang)

References

(
URL
)

Details

Overview Description:
Install seamonkey (commercial build)along with JRE using the latest installer
Loading a applet fails because it does not recognize the applet tag
Steps to Reproduce:
1)Install seamonkey and JRE using seamonkey.exe
2)Load the above url after launching mozilla.exe
3)Error message display indicating the the applet did not load

Actual Results:
Error message: alt="Your browser understands the <Applet> tag but isn't running
the applet for some reason. Your browser is completely ignoring the <Applet>
tag!

Expected Results:
Applet should load and be displayed

Build Date & Platform Bug Found:
1999110809-M11  - Windows

Additional Builds and Platforms Tested On:
None

Additional Information:
Not sure if this is a block for M11 but OJI is not useable.
Summary: OJI does not work on Windows → OJI does not work on Windows
Adding Jan to the cc list.
Assignee: drapeau → edburns
Re-assigning to Ed Burns for investigation, copying Leila Garin for
verification.
Looks like the JRE install is broken and therefore not get installed.  Need an update.

Added Frank Petitta to the cc lisit
I have requested a new installer from sun.
Lithium has been updated with a new JRE122.exe from Sun.  I did a quick test and
it seems to work.  I didnt get it in time to be in todays builds.....
Have either Frank or Paul tried the latest Sun JRE? (JDK 1.3 Early Access)  You
should have it internally there; if you need help finding or getting it, please
send me email and I'll gladly help you.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
After solving the network problem of the browser not being able to resolve
www.javasoft.com, the applet did load, and the little hangman thingy appeared.
However, I was unable to type letters, but I believe that's another bug.
Status: RESOLVED → VERIFIED
Marking this bug Verified.
Status: VERIFIED → REOPENED
Reopened....my bad...OJI not working on current build.
Resolution: WORKSFORME → ---
Clearing WorksForMe resolution.
The problem with the JRE 1.2.2 has been solved.  The one the came with the commercial  build was corrupted and the new copy is
good.  I tried loading and displaying an applet  and I still get the same error.  Are we all using the same software?  I an currently using
build 1999111017-M11 commercial build.
I'm using the latest JDK1.3 and a build of mozilla from yesterday.

Paw, I'll send you the same JDK1.3 I used.
Status: REOPENED → ASSIGNED
Ok, I will check it out.
Assignee: edburns → ryang
Status: ASSIGNED → NEW
The applet successfully loads and displays, but when I click in the applet
display area, I get an endless stream of

Opening http://www.javasoft.com/applets/other/Hangman/classes/META-INF/services/
javax.sound.sampled.spi.MixerProvider proxy=webcache-cup.eng.sun.com:8080
Opening http://www.javasoft.com/applets/other/Hangman/classes/META-INF/services/
javax.sound.sampled.spi.MixerProvider proxy=webcache-cup.eng.sun.com:8080
Opening http://www.javasoft.com/applets/other/Hangman/classes/META-INF/services/
javax.sound.sampled.spi.MixerProvider proxy=webcache-cup.eng.sun.com:8080
Opening http://www.javasoft.com/applets/other/Hangman/classes/META-INF/services/
javax.sound.sampled.spi.MixerProvider proxy=webcache-cup.eng.sun.com:8080
Looks like the NPJava*.dlls are not being copied to the Seamonkey plugins folder.
How would an installation program know where to install said plugins ?
Add Sean to the cc: list
I am able to reproduce this with Mozilla.  I also took a snapshot of the applet
and repackaged it for the Java Plugin (MSIE/NS4.x) and the same thing
occurred.  Turns out there's an outstanding bug report very similar to this
filed against java sound in 1.3.  Apparently the fix is in progress but not yet
available.

BTW Regarding the installation of the NPJava*.dll's :  these are normally
installed to Netscape 4.x plugin directories.  If you have Netscape 4.x and the
JRE installed, then if you delete or rename your Mozilla plugin directory,
these DLL's are taken from the Netscape 4.x plugin directory instead.

I know that doesn't help the situation for someone who only has Mozilla
installed, but at some point there will have to be a way for the JRE
installation program to know where to put the NPJava*.dll's for Mozilla.  For
Netscape 4.x, there are registry keys to look at.  I don't know how the JRE
installation program will know where to put these DLL's for Mozilla.
mozilla installer will eventually update the windows registry so other apps can
locate it.

I guess that the current workaround is to have the mozilla installer copy the
NPJava*.dll's to its Plugins folder.

I'll file a bug on that and leave this one open.
I just tested with some fixed source sent to me from the Java media folks and
it definitely looks like the problem will be fixed in the next promoted build
of JDK1.3 ("P").  I think it should be available to me and Ed next week, if not
sooner.

Should I reassign this to someone else for verification ?
No, I can do  the verification if you will notify me when the sw is available.  It's important to test with the commercial build and
installation.
does this mean that the windows installer no longer needs to copy the
npjava*.dll files into the seamonkey's Plugins folder?

Let me know because I just updated the installer to do this for tomorrow's
seamonkey build.  I can easily undo it if necessary.
No - my apologies, I meant the *sound* bug should be fixed in the next build.
The installation problem still remains, AFAIK.
I tried it with JRE1.3 build "P" as of Monday 11/29 and the Mozilla build we
have dated 11/23 and the Hangman applet works fine.  If somebody could verify
that would be great.
Sound bug is fixed in the 1999120109-M12 build.  There seems to be a huge memory leak  when trying to play hangman.
maybe if you could guess the word a little faster
I suspect the memory leak is related to bug 14712.  Some problems currently
exist with OJI and applet refresh/shutdown.  Can we close this bug now ?
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
I'll mark it fix and then verify it.
Verified in the 1999120109-M12 build
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.