SeaMonkey 2.0 freezes WPS
A.D. Fundum
but it always freezes immediately after closing it. The clock
is still updated, but that's it. Does it require eCS 2.0, or does
it reqiure at least a Pentium 4 or better?!
I always updated it using the *.EXE. But this time I used the
*.ZIP. That's the only other different thing. v1.1.18 is restored
(re-installed) without any problem, using its INSTALL.EXE.
Dave Yeo
> SeaMonkey 2.0 works on several eCS 1.2-machines here,
> but it always freezes immediately after closing it. The clock
> is still updated, but that's it. Does it require eCS 2.0, or does
> it reqiure at least a Pentium 4 or better?!
Hopefully you read the readme in full. IIRC it states a minimum of 500
Mhz for CPU. And Warp v4, fp13 and the 32 bit stack. Runs fine on my Warp 4
>
> I always updated it using the *.EXE. But this time I used the
> *.ZIP. That's the only other different thing. v1.1.18 is restored
> (re-installed) without any problem, using its INSTALL.EXE.
You did install to a different directory?
Dave
m...@privacy.net
>SeaMonkey 2.0 works on several eCS 1.2-machines here,
>but it always freezes immediately after closing it. The clock is still
>updated, but that's it. Does it require eCS 2.0, or does it reqiure at
>least a Pentium 4 or better?!
I see a freeze with it after closing part of the time. All it takes here
to correct this is to hit ctl-esc and wait for a popup about a unknown
process is not responding and either click the button or hit the esc key
and the system is unlocked again. These events often put an entry in
POPUPLOG.OS2 that I am told indicate a problem with flash is the cause. I
should note that I see the same problem with 1.1.18 as well, so this is
not a 2.0 problem.
Regarding requirements for SM2, I am running it on my TP600E which is a
P366 with 544M of RAM and find it only a little slower than 1.1.18 is on
this system. I did find that I needed to use SP to start it at idle
priority to keep it from impacting operation of the rest of the system,
but this has minimal impact on SM2 itself. The same thing is possible
using RUN! as well, if you don't have a copy of SP to use.
-- Dave
-----------------------------------------------------------
dhdurgee<at>verizon<dot>net
-----------------------------------------------------------
A.D. Fundum
>> Pentium 4 or better?!
Got that, my first try was with a P3 500 MHz with it maximum of
786 MB RAM.
> And Warp v4, fp13 and the 32 bit stack.
Got that covered too,with eCS 1.2. I won't try it with Warp 4,
because you mention fp13. That's not available for my NLV.
> Runs fine on my Warp 4
Without flash installed?
> You did install to a different directory?
No, but I DELTREE'd the existing one. Installed 2.0 without any
error messages or warnings, it applied my 1.1.18-profile, and I
re-installed my NLV package. And flash... :-o
A.D. Fundum
> a popup about a unknown process is not responding and
> either click the button or hit the esc key and the system is
> unlocked again.
Understood. I'll try that next time, first without Flash installed,
and after that with Flash, just to see this:
> These events often put an entry i POPUPLOG.OS2 that I
> am told indicate a problem with flash is the cause.
That seems likely indeed. I installed my SM NLV package,
and the second time I installed flash (flash7a63RW). I've not
used it, and didn't get further than an "about:plugins"-visit.
That was enough to generate the freeze after SM's close. I
didn't visit a website with any *.SWF-content.
> I should note that I see the same problem with 1.1.18 as well,
> so this is not a 2.0 problem.
For me it is. Flash isn't perfect, but any freeze is 'rare' and isn't
that common. And it's different from my 2.0 freeze.
> Regarding requirements for SM2, I am running it on my
> TP600E which is a P366 with 544M of RAM and find it
> only a little slower than 1.1.18 is on this system.
I haven't tried SM2 on a TP600E/X yet, but's that's because
the freeze stopped me from distributing it.
> The same thing is possible using RUN! as well
There's RW again! :-)