I didn't help. However that was such an obvious suggestion I am quite ashamed of myself for having missed it. Some days are like that. Unfortunately, they are increasing in frequency as the birthdays keep rolling around. Sigh.
Well, it appears that Java isn't as important as flash for viewing websites. There is perhaps something frightening in that. -- John Mandeville jemandy at norp5424b dot hsc dot usc dot edu On Mon, 11 Feb 2002 16:28:04, Michael Kaply <[EMAIL PROTECTED]> wrote: > > What about just turning off the JIT completely? > > John Mandeville wrote: > > > Well, I get the same error message described in that bugzilla entry. > > > > One person there suggested that they can load a test page from his own > > computer with open file--that he only gets the the problem over the > > internet. However, I get the problem both places. (Unlike that > > contributor, I am not going through a proxy.) > > > > You suggested that there was a problem with running NS 4.61 at the > > same time as running Mozilla. I rebooted before tested without first > > running the older NS. I still get the same problem. > > > > You suggested making sure making sure that the java is the latest java > > service level. I have the latest I could find which is J2RE 1.3.0 IBM > > build co130-20010925. I had installed this over top a previous build. > > So I tried uninstalling Java 1.3 altogether and reinstalling it. I > > also cleaned out my profile. This changed the behavior: I got a SYS > > 3175 in zip.dll (located in the Java13 tree). That was odd because > > that SYS 3175 was the behavior I got before I first tried to upgrade > > to the more recent Java 1.3 build. > > > > Another person there suggested playing with jctrlpnl.cmd and removing > > the two files in java13\jre\_java . This caused the failed pipe > > connection message to return. I ran jctrlpnl.cmd again to create the > > two deleted files, but I still got the failed pipe message. > > > > I guess none of this helps too much since: 1) as you note in > > bugzilla, this appears to be a Java problem, not a Mozilla problem, > > and 2) you have not been able to recreate the problem. > > > > Ugh. > > > > -- > > John Mandeville > > jemandy at norp5424b dot hsc dot usc dot edu > > > > On Thu, 7 Feb 2002 05:33:38, Michael Kaply > > <[EMAIL PROTECTED]> wrote: > > > > > > Can you see if anything in this bug helps? > > > > > > http://bugzilla.mozilla.org/show_bug.cgi?id=122751 > > > > > > Mike > > > > > > John Mandeville wrote: > > > > > > > > I haven't been able to get Java 1.3 to work in any version of Mozilla. > > > > I used to get a sys3175 in zip.dll. I finally got my Software Choice > > > > subscription fixed so I could download the latest refresh of Java13 > > > > and installed that. I also copied the npoji6.dll from the fresh > > > > install. Now I get another message before Mozilla dies: "JVM Script > > > > Startup Failure. Unable to create pipe connections to JVM. RC = 4 > > > > [0x00000004]". >
