Firefox 17.0.5 for eCS (OS/2) Beta 2
Pre-releaseThis is the second beta release of Firefox for eCS (OS/2) version 17.0.5. It fixes a number of bugs discovered in the first beta, introduces OS/2 support for the OOP (out-of-process) technology and makes the Flash plugin work.
The CHANGES.OS2 file contains more detailed list of changes.
This is a beta release meaning that not all functions work properly. In particular, there are the following limitations:
- Due to bugs in MMPM, the current version of Firefox runs the Flash plugin in
"in-process" (traditional) mode instead of the new OOP (out-of-process) mode
used on other platforms. This will be fixed in future releases. - The OpenJDK (Java) plugin works but there are some problems with window
updates. This is to be addressed in future releases. - The
@font-face
HTML attribute is not yet supported. As a result, tiny boxes
with hex numbers are displayed instead of characters on pages that use it. - Fonts with names containing special characters (like Asian Unicode names)
will not display correctly in the list of fonts in the Options panel. - Mozilla apps will beep when copying more than 64 kB of text to the clipboard.
This is to alert users that many applications (most notably the system
editor, EPM, and applications running in VIO windows) cannot paste more
than this. - Other known problems can be found by following the link "Current Open
Warpzilla Bugs" on the OS/2 Mozilla page http://www.mozilla.org/ports/os2/.
The list of prerequisites for this version is as follows (sorry, GitHub has a surprising bug that prevents making clickable FTP links here so you have to copy-paste them):
- LIBC 0.6.5 Runtime — ftp://ftp.netlabs.org/pub/gcc/libc-0_6_5-csd5.wpi
- Freetype Runtume — ftp://ftp.netlabs.org/incoming/mozilla/MZFNTCFGFT_RUNTIME-0-0-1.wpi
Also, if you don't use RPM/YUM, you will need the following DLLs:
If you do have RPM/YUM installed, you may still need to do yum install pthread mmap libgcc446 libstdc++
in order to run Firefox.
Please refer to README.OS2 for more information about this release and for detailed installation instructions.
If you find a bug (which is likely), please create an issue at the issues page. But before you create a new issue, be sure it is not already reported by searching through the existing ones using the Search field at the top of this page.