Text 413, 94 rader
Skriven 2007-01-24 23:26:10 av Mike Luther (1:117/3001.0)
    Kommentar till text 407 av Sean Dennis (1:18/200)
Ärende: Seamonkey
=================
Sean (And others about this too).

In my long post about this Innotek Java deal I absolutely quoted the wrong date
of file issue for the working Java 1.4.2 version of this. I posted that the
correct version was:

  Here the only combination of releases that work for me are:

     The 240 release  ....    682,765 bytes   07-10-05
     The 260 Beta1 release  1,019,545 bytes   07-10-05

Well that is correct!   But you must have the 'correct' version of the actual
Innotek Java 1.4.2 product to merge with it as well!  And how and in what
sequence you install this stuff is critical, as I see it here.

I just went through another round of this on the old cloned box with the
XR_C006 test fixpack on it.  My local KBTX weather java radar page wouldn't
expand like it should.  I discovered that the \mozilla\plugins versions of the
Innotek java plugins were the above dates.  But that won't work.  The Innotek
Java 1.4.2 plugins that also had that same date are what causes the SYS3175 in
the Seamonkey browser failures.  They came from that same early release date
where I got them from Innotek and happened to still be on this box.

Taking a closer look at the working boxes here shows that the correct versions
that do work for the Java Plugins for the Seamonkey that are in the
\mozilla\plugins directory are actually:

     9-20-05   5:32p    117334           0  npj2.dll
     9-20-05   5:32p      9084           0  npj2_j11.dll
     9-20-05   5:32p      9093           0  npj2_j12.dll
     9-20-05   5:32p      9091           0  npj2_j13.dll
     9-20-05   5:32p      9066           0  npj2_j14.dll
     9-20-05   5:32p      9092           0  npj2_j32.dll
     9-20-05   5:32p      9065           0  npj2_jpi.dll

Not the other dates above.  And you get these from the following Innotek source
files:

     9-20-05  12:00a  21387711          74  install.exe
     9-20-05  12:01a  44382413          78  install_sdk.exe

The way this works is that if you installed the earlier Innotek product,you ran
it as an executable above.  It goes into your hard disk based on where you
first installed the basic Innotek utility directory.  Fine,but the earlier
Innotek Java product does not have an UNINSTALL feature! And, again, you can't,
per my research, do the install.exe above, then follow that with the
install_sdk.exe like you do with the IBM Java 1.3.1.

What you must do one way or another if you have the earlier or corrupt stuff in
there, is to do an 'over-install' of the Java 1.4.2 product you want.  As I
noted, I'm using the install_sdk.exe here.  When you do the 'over-install' it
will tell you that you must re-boot to enable it.  Not quite true here.  At
that point you then run the install_sdk.exe over again right away.  You will
notice that the installer now has a choice pane in it to UNINSTALL the thing. 
Do that!

Then .. install it AGAIN!  This time shut down the computer as it says you need
to do.  On reboot, when it comes up, look in the directory on your disk called
\jav142\jre\bin.  Inside that you will see the correct cited Innotek java
plugin files cited above.  Or else this is wrong.  At that point you have to
manually copy them into your \mosilla\plugins directory.  And while you are at
it, in case you have installed or had installed the IBM Java 1.3.1 prodcut and
spoken toward enabling it for your browser you will also see the following:

     6-05-06  11:41p    284740           0  npoji6.dll

It isn't good, so I am told, to have this one in there as well as the Innotek
product.  So I just name it as follows and leave it in case I have trouble with
the Innotek whatever and need it back for some reason:

     6-05-06  11:41p    284740           0  npoji6.dlk

Then, after this is straight, to finally solve the mess with the latest
versions of Seamonkey, you need to do an OVERINSTALL of the following file from
Innotek to properly synchronize the font stuff:

     7-10-05   7:57p   1019545           0  InnoTek_FT2LIB_260_Beta1.exe

The 240 official release will cause problems with the later Seamonkey products
as well.  And THAT will, as far as I can tell, stop the instability of the
Seamonkey product on some, but not all sites.  I have seen both SYS2070 and
SYS3175 errors pop up because of this.

I'm so sorry I didn't get my original answer right I tried with which to help
you...



--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)