SM2.28a1

[A.D. Fundum]

1. The Hobbes TXT files refers to the usual README.OS2 file, but this
file seems to be missing.

2. It seems there's no 2.28 under
ftp://ftp.mozilla.org/pub/seamonkey/releases/. I assume an older
(2.26) langpack has to be used.

--

[Dave Yeo]

Post by A.D. Fundum
1. The Hobbes TXT files refers to the usual README.OS2 file, but this
file seems to be missing.

Sorry about that, packaging error which is why I labeled it a1 for alpha
quality. I'll fix the package manifest.
Readme is at
https://github.com/bitwiseworks/mozilla-os2/blob/master/widget/os2/README.OS2

Post by A.D. Fundum
2. It seems there's no 2.28 under
ftp://ftp.mozilla.org/pub/seamonkey/releases/. I assume an older
(2.26) langpack has to be used.

Somebody reported success by using the language pack from 2.29 and
changing the version detection. I'd guess by opening the xpi (zip) file
and editing install.rdf to change the em:version
Dave

[A.D. Fundum]

So KAI0.DLL is a known new requirement, and so is the --safe-mode
parameter.

In non-safe mode there's this (translated) fatal error message in an
OS/2 Window:

XML-parsing error: undefined entity
Location: chrome://navigator/content/navigator.xul
Line number 142, column 7:

<menuitem id="viewSecurityInfo"
------^

[Dave Yeo]

Post by A.D. Fundum
So KAI0.DLL is a known new requirement, and so is the --safe-mode
parameter.
In non-safe mode there's this (translated) fatal error message in an
XML-parsing error: undefined entity
Location: chrome://navigator/content/navigator.xul
<menuitem id="viewSecurityInfo"
------^

Have you tried disabling all your add-ons and then re-enabling them one
by one? I had one that was screwing up my history and putting lots of
errors in the console.log
Dave

[A.D. Fundum]

Post by Dave Yeo
Have you tried disabling all your add-ons and
then re-enabling them one by one?

Now I've tried to disable all but one (NoScript) additional add-ons
with SM2.21b3.

Next I removed 2.21b3, installed 2.28a1, and apparently it works
without having to re-enable any add-on. I can see that e.g.
DownloadHelper is active, and about:addons only shows Disable-buttons.

I'll also take a look at upgrading add-ons, if there is an upgrade
which required a FF-version newer than 24. ISTR the Saved Password
Editor is an example of such an upgrade.

It looks the langpack caused the XML-problem. I've now imported the
older 2.26 langpack without any message that it's too old or disabled,
and cannot start SM anymore. I'll try to edit 2.29's, after restoring
the previous SM version with a disabled langpack.


--

[Dave Yeo]

Post by A.D. Fundum

Post by Dave Yeo
Have you tried disabling all your add-ons and
then re-enabling them one by one?

Now I've tried to disable all but one (NoScript) additional add-ons
with SM2.21b3.
Next I removed 2.21b3, installed 2.28a1, and apparently it works
without having to re-enable any add-on. I can see that e.g.
DownloadHelper is active, and about:addons only shows Disable-buttons.

I would have disabled them from the safe-mode window.

Post by A.D. Fundum
I'll also take a look at upgrading add-ons, if there is an upgrade
which required a FF-version newer than 24. ISTR the Saved Password
Editor is an example of such an upgrade.
It looks the langpack caused the XML-problem. I've now imported the
older 2.26 langpack without any message that it's too old or disabled,
and cannot start SM anymore. I'll try to edit 2.29's, after restoring
the previous SM version with a disabled langpack.

Perhaps the language pack from
http://www.seamonkey-project.org/releases/2.18b4#langpacks would be the
best fit. Still might need editing though.
Dave

[A.D. Fundum]

Post by Dave Yeo
I would have disabled them from the safe-mode window.

In my case FF>=SM, and SM==production, so nearly always I'm restoring
SM after a test or failed attempt.

Post by Dave Yeo
2.18b4#langpacks would be the best fit.

The difference between 2.18 and 2.28 is one digit, but perhaps not the
digit we're looking for... ;-)

Using your link, I'll try 2.26.1 and 2.29b1 first. Maybe editing (i.e.
changing the version number of SM or a langpack) isn't required then.
I was able to import 2.26's.


--

[A.D. Fundum]

Post by A.D. Fundum
Using your link, I'll try 2.26.1 and 2.29b1 first.

FTR: editing is required. 2.26.1 doesn't work, and 2.29b1 cannot be
used out-of-the-box.


--

[A.D. Fundum]

Post by Dave Yeo
Somebody reported success by using the language pack from
2.29 and changing the version detection. I'd guess by opening
the xpi (zip) file and editing install.rdf to change the em:version

Confirmed (with a 2.29b1 langpack), so far without any problem:

<em:minVersion>2.28</em:minVersion>


--

[A.D. Fundum]

Hardly worth mentioning: it looks like lxLite has touched the 16tx16
icon again.


--

[Dave Yeo]

Post by A.D. Fundum
Hardly worth mentioning: it looks like lxLite has touched the 16tx16
icon again.

Or I screwed up and restored the wrong icons. We worked around the
lxlite thing by lowering the bitdepth of the icons.
Dave

[A.D. Fundum]

Firefox has the same langpack-problem.

One SM-specific remark is that its initial CPU load is 100% for a
(short) while with a Pentium 4 CPU, while FF can be used almost
immediately after it has started visually (i.e. after about:blank is
displayed).

Post by Dave Yeo
Or I screwed up and restored the wrong icons.

A good icon (MAIN-WINDOW.ICO) is included in the package, so (if
needed) the user can use this untouched icon file instead of the one
linked to the EXE.


--

[Dave Yeo]

Post by A.D. Fundum
Firefox has the same langpack-problem.

Looks like an issue has been opened on Github so hopefully it will be fixed.

Post by A.D. Fundum
One SM-specific remark is that its initial CPU load is 100% for a
(short) while with a Pentium 4 CPU, while FF can be used almost
immediately after it has started visually (i.e. after about:blank is
displayed).

There seems to be problems with the cache and session restore. I suspect
this is why 2.28 was never finished and your CPU load problem may be
related. The SM team has a hard time keeping up with the ever changing
Firefox's Gecko changes.

Post by A.D. Fundum

Post by Dave Yeo
Or I screwed up and restored the wrong icons.

A good icon (MAIN-WINDOW.ICO) is included in the package, so (if
needed) the user can use this untouched icon file instead of the one
linked to the EXE.

Good to know.
Dave

[Dave Yeo]

Post by A.D. Fundum
Hardly worth mentioning: it looks like lxLite has touched the 16tx16
icon again.

Fixed by lowering the bit depth.
I'll try to upload a new build as soon as possible to align with the
Bitwise release of Firefox today.
Dave

[Dave Yeo]

Post by A.D. Fundum
2. It seems there's no 2.28 under
ftp://ftp.mozilla.org/pub/seamonkey/releases/

Turns out that there never was a 2.28 (or 2.27) release so there will be
bugs from upstream where the closest was 2.28B4.
Dave