Hi Not sure if this would help you but as I use Java 118 as my default JVM I have no Java 131 statements in my config.sys - I use a script which sets all necessary Java and Mozilla paths to start Mozilla.
Here is a script I use to start Mozilla with the Profile Manager:- /* mozstart.cmd - Rexx script to start Warpzilla with the ProfileManager */ /* Add any necessary PATH type statements */ '@SET MOZILLA_HOME=j:\' '@set PATH=H:\JAVA131\JRE\bin;%path%' '@set BEGINLIBPATH=H:\JAVA131\JRE\bin;H:\JAVA131\JRE\dll;j:\Moz1RC\bin;' '@SET CLASSPATH=' '@set java_home=H:\JAVA131\JRE' /* Start Mozilla with Profile Manager as parameter */ '@j:\Moz1RC\bin\mozilla.EXE -l en_US -ProfileManager' Maybe you want to modify that for your system and see if it works. I also use SET SHELLHANDLESINC=50 in my config.sys file. My os2.ini entries for Java 131 are:- App: Java Plug-in Key: JAVA_HOME Value: H:\JAVA131\JRE APP: JAVA131 Key: USER_HOME Value: H:\JAVA131\JRE I have also found it useful to have this entry:- App: Netscape Key: 6.2 Value: J:\MOZ1RC\BIN This allows the Java 13x installer to automatically install the plugin to J:\MOZ1RC\BIN\PLUGINS I hope some of the above is of use. Regards Pete Dan Drake wrote: > On Fri, 7 Jun 2002 20:32:48 UTC, Michael Kaply <[EMAIL PROTECTED]> wrote: > > >>Try this: >> >>SET SHELLHANDLESINC=30 >> >>in your CONFIG.SYS >> >>Should workaround the problem. >> >>It's a bug in Java that we are working on getting fixed. > > > Regret to say, I tried it, rebooted, and got the same result: the ZIP.DLL > bomb. > > SHELLHANDLESINC=30 > says a set | grep operation I just did to confirm that I really had set > it in Config. > > Oops gosh darn. Now I get that same error when run the test after > bringing up Mozilla from the WPS object! Before, I had reached the point > where it gave me the message about being unable to connect a pipe to JVM. > (OS2.INI still has the Java-Home value set correctly.)
