Text 409, 115 rader
Skriven 2007-01-22 22:43:54 av Mike Luther (1:117/3001.0)
    Kommentar till text 407 av Sean Dennis (1:18/200)
Ärende: Seamonkey
=================
As well Sean ..

 SD> You would ask me that. :>

 SD> I think I'm using the beta version that's on their 
 SD> (Innotek's) website.  At least on this machine.  On my 
 SD> other machine, I'm not sure what I am using. I'll 
 SD> check.

You might note that the only way I've been able to fix this on a couple of
boxes is to use the UNINSTALL for the font engine.  Then I have to install it
again!   And then and only then can I get it to work.  And on some boxes with
some whatever incantations, I also have to first do the earlier beta .. then ..
I have to install over that with the 2.60 beta and then .. it works!  I've
found that for some reason, things that look like just the same work on one box
and not another.  You have to force feed all this to make it work on some boxes
and not others.  Why?

Ask Alice!  Maybe she'll feed you a strange tasting brownie from long long ago,
grin.

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

What went wrong seems to be that Innotek had something foul up with the same
number releases that may carry file dates other than the above! That same I
HATE THIS game where when you download with a Web Browser you get not the file
date but your download date and time.  When all this went wrong IIRC Innotek
fixed the download with a bad attitude. But the date for the only stable one(s)
I could find happens to be what was first offered, then changed for the bad
boy, then replaced with the one that works.  Innotek didn't make it too easy,
as well, to even find the files in the way they set up their web site, in my
opinion.

As well, as a second piece to this puzzle, the Innotek Java 1.4.2 which works
with all this can be installed in either of two ways, but not, it seems both,
like unto IBM's Java 1.3.1 whatever!  The Java 1.4.2 packages which are stable
here are:

     install.exe           21,387,711 bytes   09-25-05
     install_sdk.exe       44,382,413 bytes   09-25-05

The secret to this mess is that you have to decide which of the two you want to
use, but I've found you can't do the one, then overwrite it with the other like
you can do in the IBM product.  So in my case, I've just used the SDK thing, in
that I might want it sometime, and that is that. If you can't figure all this
out from the Innotek site, I may be able to orient you to the files here via
FTP if you have a broadband service.

You'll have to get a clean font game done before you do the other, as I recall
all this too.  Then, after you get this all done you have to carefully hand
copy the needed Innotek DLL's into the \plugin directory for your Seamonkey
operation.  As well, you really should change the IBM 1.3.1 DLL to a change
namw of .DLK to keep from conflicting things.

As a last comment, for anyone following along here, the Seamonkey '0fficial'
1.1 release has now hit the download site on the MOZ nightly server.  And it
was just released for a second version as of today,January 22, 2007.  I've
moved that to all my boxes here and it seems to be working fine without any of
the Newsreader memory junking and CPU hogging that I and others found earler
between the November 26th Beta 3 release and the December 24th Beta 4 release.

I've always used the installer way of doing this.  However, if you are doing an
upgrade from the Seamonkey 1.0.7 game you really need to perform an uninstall
formally for it.  Then you do the install for the 1.1 version, placing it in
the same directory and path as your 1.0.7 product occupied.  When you fire it
up you won't get the SYS2070 error you'll otherwise see.  And your profile you
were using before will, if it goes like all of mine have gone, work fine with
the 1.1 release just out.
                      
Note!  There have already been two 'final' releases from Mike Kaply,which use
the GCC compiler and the LIB05 DLL package.  Soon to be released, per Peter
Weilbarger will be his custom enhanced releases for his private releases of all
this.  You need to know that his releases use the LIB06 DLL and later GCC
compiler tools.  One reason to really think about using Peter's versions is
that he and Paul Smedley and others are working hard on a HIGH MEMORY version
of Seamonkey to help get out of the VIRTUALMEMORY limit trap which is now
showing up particularly in the eCs group's work.  The HIGH MEMORY version of
his releases cured some very curious long left up Seamonkey system locks for me
and others where over a long time and many site plus flash and java uses there,
we'd hit an out of memory condition which jammed the whole system.  This issue
seems particularly of focus on folks who are fooling with ODIN and XWP and
other Windows likee code design as it creeps toward the OS/2 op system.  And as
a part of eCS installs...

You'll have to also pay attention to the required LIB06 source for that code
and copy those DLL's into your \OS2\DLL directory.  The current 'standardized'
release of the latest LIB06 DLL operation uses a special bridge to coordinate
the LIB05 work to the new LIB06 needs. However this standardized latest release
will work not only with Peter's releases, but all of Paul Smedley's cross port
work from Linux to OS/2.  It has some failure to post system traps to the
POPUPLOG.OS2 and SYS trap display needs of OS/2, but that's another story.

And as well, the move to Seamonkey 1.5 is already in LIB06 anyway.  I have
Seamonky 1.5 Alpha running for test on another box now and the latest release
for it is also January 22, 2007.  It behaves about exactly like the 1.1 formal
release, but the menu icon display is more modern in it.  Note!  You'll have to
do the formal UNINSTALL of the Seamonkey 1.1, leaving the profile behind, then
reselect the install directory all over again for the Seamonkey 1.5 initial
install.  Or it will be back to SYS2070 all over again here too!

Hate to be a yapit puppy dog here, but if I can save anyone some trouble,
that's what I want to do.


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

Mike @ 1:117/3001



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