>> The latest FF assumes an eCS 2.x environment
> The latest FF, which Bitwise compiled to target a i486
> due to the need for the GCC atomics, runs fine on my
> OS/2 ver 4+fp15
In general it doesn't. FF + OS/2 = missing DLLs. You had to eCS 2'ify
your OS/2 system, which requires quite a few extraordinary efforts
from an user's point of view (the requirements of requirements of
requirements of requirements of required software). It will work, wehy
not, but I wouldn't sell it as OS/2 software. Your customers will
complain that they cannot find all DLLs, and the solution to obtain
those DLLs ... su^G^Gblows. Engineers (it works) vs humans. ;-)
> I did end up buying eCS2.1 so I could take advantage
> of both cores as Warp V4 has too many none SMP
> safe libraries.
I couldn't install eCS 1.2 using an IBM/Lenovo T60p after disabling
one of the cores. So far that's the only reason why I could consider
an upgrade to eCS 2 DE/EN. An outdated browser may be the next reason.
> I target my Warp V4+fp15+other free fixes such as the 32 bit stack.
Please keep in mind that you're one of the happy few, nowadays
restricted to the most active languages in this thread: DE/EN. FP15 is
not GA. There's no such thing as a GA Korean FP15 (FP5:
There's OS/2 (386), there's a Y2K FP (386, we've lost a few OS/2
languages back then), there are non-GA fixpaks to reduce the number of
OS/2 languages (386), there's eCS 1 (i686+, less languages), and
there's eCS 2 (i686, DE/EN only).
Hence the suggestion to rename readme.os2 and makefile.os2 to *.ecs,
to assume the use of a i686+. Users of FP15 will be aware of possible
problems. A language is a good reason to keep using such an old beast.
Off topic: I'll understand eCS 2 DE/EN, but often that comes down to
using ELF (English as a Lingua Franca). ELF, we're using it right
here, is one of the worst solutions. In our case you may have the
advantage of native language, but I may be restricted to the
vocabulary of a child, and my users may not speak English or German at
> even the later refresh of Warp V4 needs an i486 to install
Retorical: GA, or only a version for the happy few?
Not retorical: it will be safe to use i486 as the bottom line, but you
should document it. I can recall one newsgroup report of 386 user,
but that was a museum piece instead of an used computer. Imn other
words, he owned a 386 but didn't use it for anything. I'm using a 486,
mainly for testing purposes. Nevertheless I'm still not using VAC's
switch /G4 to target 486, because the gain, if any, requires
documentation because it isn't a 386.
> Are you using the 486?
Yes, but of course not frequently. And I'll use Netscape instead of
FF/SM, if I would have to view a (local) HTML file. Software can stop
working, and I have even used my 486 to answer a Mozilla's font
question of Peter Weilbacher, IIRC. It also is one of my three
Warp-installs (2x 486, 1x 586), the rest is eCS 1.2.
> I'd assume that it wouldn't support enough memory
> to run Mozilla.
A pimped pentium II notebook hardly has enough memory to use the last
FF/SM for OS/2, and an animated GIF will kill the remaining
performance. In case of an "emergency" it can be used. Or, for
example, you may decide that you don't need a $1599 8THz CPU to
download a large file with a modem.
> Generally when I port something, I do target the default i386
> unless there is a reason to target newer.
I think video-related DLLs of FF/SM can target the i586 (supported by
IBM?) or i686+ (anything "newer than i486"?). The user of an
unofficial Korean FP15 could still develop it, and it requires hardly
more than renaming *.OS2 to *.eCS. And a fully working compiler
A Pentium 4 is hardly fast enough to watch modern HQ videos. A PIII
may still work. You don't grab a PII to watch a video.
Off topic:iIt would help if I was able to disable the second core and
use newer hardware than 10+ years old Pentium IIs-4s, but the eCS 1.2
installer seems to stop after displaying the blue eCS logo and after
disabling the second core.