[OS/2] Bug 443112: sync README files of all three apps with information for Gecko 1.9.1; add Java version requirements and update web links

(OS/2 only, so does not affect a CLOSED TREE)
This commit is contained in:
Peter Weilbacher 2009-01-10 13:31:01 +01:00
parent 330b60447a
commit 55808c0fb6
3 changed files with 506 additions and 275 deletions

View File

@ -1,6 +1,6 @@
================================================================================
= = = = = = = = = = = = = = Firefox Read Me = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = Firefox Read Me = = = = = = = = = = = = = = =
================================================================================
@ -12,11 +12,11 @@ installation instructions for the OS/2 build of Firefox.
For more info on Firefox, see http://www.mozilla.org/products/firefox/.
For more info on the OS/2 port see http://www.mozilla.org/ports/os2. To submit
bugs or other feedback check out Bugzilla at https://bugzilla.mozilla.org for
links to known bugs, bug-writing guidelines, and more. You can also get help
with Bugzilla by pointing your IRC client to #mozillazine at irc.mozilla.org,
OS/2 specific problems are discussed in #warpzilla and in the newsgroup
mozilla.dev.ports.os2 on news.mozilla.org.
bugs reports go to Bugzilla at https://bugzilla.mozilla.org.
For discussion and help for OS/2 specific problems, please use the newsgroup
mozilla.dev.ports.os2 on news.mozilla.org. You can also get help by pointing
your IRC client to the #warpzilla channel on irc.mozilla.org.
================================================================================
@ -27,12 +27,13 @@ mozilla.dev.ports.os2 on news.mozilla.org.
Official Milestone builds of Firefox are published on the release page at
http://www.mozilla.org/products/firefox/releases/
http://www.mozilla.com/en-US/firefox/releases/
OS/2 releases are not created by Mozilla.org staff and may appear on the page
http://www.mozilla.org/ports/os2 before the releases page. Be sure to read the
Firefox release notes linked on the releases page for information on known
problems and installation issues with Firefox.
OS/2 releases are not created by Mozilla staff and may appear on the
page http://www.mozilla.org/ports/os2 before the releases page. Be sure to read
the release notes linked on the releases page for information on known problems
and installation issues.
OS/2 specific problems with this version are listed below.
================================================================================
@ -41,8 +42,8 @@ problems and installation issues with Firefox.
================================================================================
- This release requires the C runtime DLLs (libc-0.6.3) from
ftp://ftp.netlabs.org/pub/gcc/libc-0.6.3-csd3.zip
- This release requires the C runtime DLL (libc063.dll) from
ftp://ftp.netlabs.org/pub/gcc/libc-0.6.3-csd3.zip
in order to run. You can unpack them in the same directory as the
Firefox executable or somewhere else in your LIBPATH.
@ -74,6 +75,9 @@ problems and installation issues with Firefox.
+ Convenience Pack 2 or eComStation 1.0 or later meet these requirements
out of the box.
+ Only Java plugins of version 1.4.1 or 1.4.2 are supported.
(IBM Java 1.3.1 or earlier will crash the application!)
- Useful optional software
The following packages enable additional features in Firefox. Download
locations are listed below with a detailed description of the features.
@ -86,58 +90,67 @@ problems and installation issues with Firefox.
================================================================================
For all platforms, unpack into a clean (new) directory. Installing on top of
previously released builds may cause problems with Firefox.
Unpack into a clean (new) directory. Installing on top of previously released
builds may cause problems with Firefox. It is therefore hightly recommended
to follow the instructions under "Separating profiles from installation
directory".
Note: These instructions do not tell you how to build Firefox.
For info on building the Firefox source, see
http://www.mozilla.org/build/
https://developer.mozilla.org/en/Build_Documentation
OS/2 Installation Instructions
------------------------------
On OS/2, Firefox does not have an installation program. To install it,
download the .zip file and follow these steps:
On OS/2, Firefox does not have an installation program. To install it,
download the .zip file and follow these steps:
1. Click the "Zip" link on the site you're downloading Firefox from
to download the ZIP package to your machine. This file is typically called
firefox-x.x.x.en-US.os2.zip where the "x.x.x" is replaced by the Firefox
version.
1. Click the "Zip" link on the site you're downloading Firefox from to
download the ZIP package to your machine. This file is typically called
firefox-x.x.x.en-US.os2.zip where the "x.x.x" is replaced by the
current Firefox version.
2. Navigate to where you downloaded the file and unpack it using your
favorite unzip tool.
2. Navigate to where you downloaded the file and unpack it using your favorite
unzip tool.
3. Keep in mind that the unzip process creates a directory "firefox"
below the location you point it to, e.g.
unzip firefox-3.0.en-US.os2.zip -d c:\firefox-3.0
will unpack Firefox into c:\firefox-3.0\firefox.
3. Keep in mind that the unzip process creates a directory "firefox" below
the location you point it to, e.g.
unzip firefox-3.1.en-US.os2.zip -d c:\firefox-3.1
will unpack Firefox into c:\firefox-3.1\firefox.
4. Make sure that you are _not_ unpacking over an old installation. This is
known to cause problems.
4. Make sure that you are _not_ unpacking over an old installation. This is
known to cause problems.
5. To start Firefox, navigate to the directory you extracted
Firefox to, make sure that the C library DLLs are copied to the
installation directory or installed in the LIBPATH, and then double-click
the Firefox.exe object.
5. To start Firefox, navigate to the directory you extracted Firefox to,
ensure that the C library DLL is copied to the installation directory or
installed in the LIBPATH, and then double-click the Firefox.exe object.
================================================================================
Tips and Problems
================================================================================
Running multiple versions concurrently
--------------------------------------
Because various members of the Mozilla family (i.e. Mozilla, Firefox,
If you want to run more than one copy of Firefox, you have to use the
-no-remote parameter or set MOZ_NO_REMOTE=1 in your environment.
Because various members of the Mozilla family (i.e. SeaMonkey, Mozilla, Firefox,
Thunderbird, IBM Web Browser) may use different, incompatible versions of the
same DLL, some extra steps may be required to run them concurrently.
One workaround is the LIBPATHSTRICT variable. To run Firefox one can create
a CMD script like the following example (where an installation of Firefox
exists in the directory d:\internet\firefox is assumed):
in the directory d:\internet\firefox is assumed):
set LIBPATHSTRICT=T
rem The next line may be needed when a different Mozilla program is listed in LIBPATH
rem set BEGINLIBPATH=d:\internet\firefox
rem The next line is only needed to run two different versions of Firefox
rem The next line is only needed to run two versions of the same program
rem set MOZ_NO_REMOTE=1
d:
cd d:\internet\firefox
@ -156,7 +169,7 @@ above depending on the system configuration.)
Finally, the simplest method is to use the Run! utility by Rich Walsh that can
be found in the Hobbes Software Archive:
http://hobbes.nmsu.edu/cgi-bin/h-search?key=Run!
http://hobbes.nmsu.edu/h-search.php?key=Run!
Read its documentation for more information.
@ -201,24 +214,24 @@ Find more information on this topic and other tips on
http://www.os2bbs.com/os2news/Warpzilla.html
Support for WPS objects in the browser
--------------------------------------
Support for WPS objects
-----------------------
Firefox can make use of Rich Walsh's Remote Workplace Server (RWS) library to
access Workplace Shell objects from the browser. This allows helper applications
for downloaded files to be selected based on their default WPS association. In
addition, the WPS icons of files will be displayed in the download dialog and in
directory views.
Firefox can make use of Rich Walsh's Remote Workplace Server (RWS) library
to access Workplace Shell objects from the application. This allows helper
applications for downloaded files to be selected based on their default WPS
association. In addition, the WPS icons of files will be displayed in the
download dialog and in directory views.
To enable this functionality, Firefox has to find the RWS DLLs. They have to be
located in a directory on the LIBPATH, in the Firefox directory, or already be
registered as a WPS class. For eComStation 2 this is already the case. If RWS
is not yet available on your system, download it from
http://hobbes.nmsu.edu/cgi-bin/h-search?key=rws08dll
To enable this functionality, Firefox has to find the RWS DLLs. They have to
be located in a directory on the LIBPATH, in the Firefox directory, or
already be registered as a WPS class. For eComStation 2 this is already the
case. If RWS is not yet available on your system, download it from
http://hobbes.nmsu.edu/h-search.php?key=rws08dll
If RWS is found on the system, it is used by Firefox automatically. In case you
need to disable RWS support, create an environment variable MOZ_NO_RWS and set
it to 1.
If RWS is found on the system, it is used by Firefox automatically. In case
you need to disable RWS support, create an environment variable MOZ_NO_RWS and
set it to 1.
Idle timer for internal cleanups
@ -242,33 +255,75 @@ executable can be selected. Any changes to these settings will be stored and
reflected in all URL objects once the user presses the "Set Default" button.
Two small applications make this change a bit easier and provide options to also
set default programs for mail and news as well as internet chat services:
set default programs for other types of internet-related activities:
- ConfigApps
http://hobbes.nmsu.edu/cgi-bin/h-search?key=configapps&sort=date
http://hobbes.nmsu.edu/h-search.php?key=configapps1_1
- Internet Application Integration
http://7cities.net/~mckinnis/os2/
Changed font handling
---------------------
To be able to display text, Firefox cannot make use of normal OS/2 routines
but has to use FreeType and FontConfig. This has the advantage that text can
be displayed with antialiasing, but at the same time has some caveats:
- Firefox cannot make use of OS/2 fonts like WarpSans and others which
are not available in Type1 or TrueType format. It is therefore
recommended to install the "Workplace Sans" font from
http://users.socis.ca/~ataylo00/creative/fonts/
or
http://hobbes.nmsu.edu/h-search.php?key=wpsu_ttf
which Firefox will use as a replacement of WarpSans.
- Display of text in some languages (e.g. Arabic) does not yet take into account
that different forms of some characters exist.
To tweak the appearance of text, you can add two preferences, preferably using
about:config.
- gfx.os2.font.antialiasing (Boolean)
This preference controls whether antialiasing is enabled, and defaults to
true.
- gfx.os2.font.hinting (Integer)
This preference controls the hinting level, and can be between 0 (no hinting)
and 3 (full hinting). The default value is 2.
Font hinting improves the contrast of displayed text, but may produce poor
results for certain characters of some fonts, most notably the OS/2 version
of "Times New Roman".
Note that these preferences only take effect when a font gets used for the first
time, so you may need to restart the application to see the full effect.
Known Problems of the OS/2 version
----------------------------------
Cross-platform problems are usually listed in the release notes of each
milestone release.
- Printing to normal OS/2 printer queues had to be disabled. It was slow even
for simple pages and used huge amounts of RAM, so that in most cases the
application crashed, see https://bugzilla.mozilla.org/show_bug.cgi?id=415522.
While the queues are still displayed in the printing dialog, any printing
operation will instead create a PDF file. By default this file is placed on
the Desktop, with the name Firefox_<date>_<time>.pdf, where <date> and
<time> are replaced by the current system time. If you want to use another
name, select "Print to file" before pressing the Print button.
The resulting PDF file can be printed using applications like Lucide, Acrobat
Reader, or GSview.
- Fonts with names containing special characters (like Asian Unicode names)
will not display correctly in the list of fonts in the Options panel.
- Firefox 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.
- Firefox cannot make use of OS/2 fonts like WarpSans and others which
are not available in Type1 or TrueType format. It is therefore
recommended to install the "Workplace Sans" font from
http://users.socis.ca/~ataylo00/creative/fonts/
or
http://hobbes.nmsu.edu/cgi-bin/h-search?key=wpsu_ttf
which Firefox will use as a replacement of WarpSans.
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/>.

View File

@ -1,182 +1,152 @@
==========================================================================
================================================================================
= = = = = = = = = = = = = SeaMonkey Read Me = = = = = = = = = = = = = =
= = = = = = = = = = = = = = SeaMonkey Read Me = = = = = = = = = = = = = = =
==========================================================================
================================================================================
SeaMonkey is subject to the terms detailed in the license agreement
accompanying it.
This Read Me file contains information about system requirements and
installation instructions for the OS/2 builds of SeaMonkey.
installation instructions for the OS/2 build of SeaMonkey.
For more info on SeaMonkey, see http://www.seamonkey-project.org/
For more info on the OS/2 port see http://www.mozilla.org/ports/os2.
To submit bugs or other feedback, see
http://www.seamonkey-project.org/dev/get-involved and check out Bugzilla
at https://bugzilla.mozilla.org/ for links to known bugs, bug-writing
guidelines, and more. You can also get help with Bugzilla by pointing your
IRC client to #mozillazine at irc.mozilla.org, OS/2 specific problems are
discussed in #warpzilla and in the newsgroup mozilla.dev.ports.os2 on
news.mozilla.org.
For more info on the OS/2 port see http://www.mozilla.org/ports/os2. To submit
bugs reports go to Bugzilla at https://bugzilla.mozilla.org.
For discussion and help for OS/2 specific problems, please use the newsgroup
mozilla.dev.ports.os2 on news.mozilla.org. You can also get help by pointing
your IRC client to the #warpzilla channel on irc.mozilla.org.
==========================================================================
================================================================================
Getting SeaMonkey
==========================================================================
================================================================================
You can download OS/2 nightly builds of SeaMonkey from the mozilla.org FTP
site at
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/
For the very latest builds, see
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-trunk/
Keep in mind that nightly builds, which are used by mozilla.org developers
for testing, may be buggy. If you are looking for a more polished version
of SeaMonkey, the SeaMonkey project releases builds of SeaMonkey regularly
that you can download from
Official Milestone builds of SeaMonkey are published on the release page at
http://www.seamonkey-project.org/releases/
Be sure to read the SeaMonkey release notes for information on known
problems and installation issues with SeaMonkey. The release notes can be
found at the preceding URL along with the releases themselves.
OS/2 releases are not created by SeaMonkey project or mozilla.org
themselves and may appear on the page http://www.mozilla.org/ports/os2
before the releases page. Be sure to read the SeaMonkey release notes
linked on the releases page for information on known problems and
installation issues with SeaMonkey.
OS/2 releases are not created by the SeaMonkey Council and may appear on the
page http://www.mozilla.org/ports/os2 before the releases page. Be sure to read
the release notes linked on the releases page for information on known problems
and installation issues.
OS/2 specific problems with this version are listed below.
==========================================================================
================================================================================
System Requirements
System Requirements on OS/2
==========================================================================
================================================================================
* OS/2
- This release requires the C runtime DLLs (libc-0.6.1) from
ftp://ftp.netlabs.org/pub/gcc/libc-0.6.1-csd1.zip
in order to run. You can unpack them in the same directory as
SeaMonkey's executable or somewhere else in your LIBPATH. The
SeaMonkey installer will not install the C runtime DLLs for you but
requires them to run.
- This release requires the C runtime DLL (libc063.dll) from
ftp://ftp.netlabs.org/pub/gcc/libc-0.6.3-csd3.zip
in order to run. You can unpack them in the same directory as the
SeaMonkey executable or somewhere else in your LIBPATH.
- Minimum hardware requirements
+ Pentium class processor
+ 64 MiB RAM plus 64 MiB free swap space
+ 35 MiB free harddisk space for installation
plus storage space for disk cache and mail
- Minimum hardware requirements
+ 400 MHz Pentium class processor
+ 128 MiB RAM plus 128 MiB free swap space
+ 40 MiB free harddisk space for installation
plus storage space for messages and disk cache
+ Graphics card and driver capable of displaying more than 256 colors
- Recommended hardware for acceptable performance
+ 500 MHz processor
+ 256 MiB RAM plus 64 MiB free swap space
NOTE: SeaMonkey's performance and stability increases the more
physical RAM is available. Especially for long browsing and IRC
sessions 512 MiB of memory is recommended.
- Recommended hardware for acceptable performance
+ 1.0 GHz processor
+ 512 MiB RAM plus 128 MiB free swap space
NOTE: SeaMonkey's performance and stability increases the more physical
RAM is available.
- Software requirements
+ Installation on a file system supporting long file names
(i.e. HPFS or JFS but not FAT)
+ OS/2 Warp 4 with Fixpack 15 or later
+ MPTS version 5.3
+ TCP/IP version 4.1
+ INETVER: SOCKETS.SYS=5.3007, AFOS2.SYS=5.3001, AFINET.SYS=5.3006
NOTE: Do not attempt to use MPTS & TCP/IP versions below these
INETVER levels. Although SeaMonkey may seem to start and run
normally with older stacks, some features SeaMonkey needs are not
implemented correctly in older MPTS versions, which may result in
crashes and data loss.
- Software requirements
+ Installation on a file system supporting long file names
(i.e. HPFS or JFS but not FAT)
+ OS/2 Warp 4 with Fixpack 15 or later (Warp 3 may work but is unsupported)
+ MPTS version 5.3
+ TCP/IP version 4.1
+ INETVER: SOCKETS.SYS=5.3007, AFOS2.SYS=5.3001, AFINET.SYS=5.3006
NOTE: Do not attempt to use MPTS & TCP/IP versions below these INETVER
levels. Although SeaMonkey may seem to start and run normally with older
stacks, some features SeaMonkey needs are not implemented correctly in
older MPTS versions, which may result in crashes and data loss.
+ Convenience Pack 2 or eComStation 1.0 or later meet these requirements
out of the box.
+ Convenience Pack 2 or eComStation 1.0 or later meet these requirements
out of the box.
+ Only Java plugins of version 1.4.1 or 1.4.2 are supported.
(IBM Java 1.3.1 or earlier will crash the application!)
- Useful optional software
The following packages enable additional features in SeaMonkey. Download
locations are listed below with a detailed description of the features.
+ Remote Workplace Server (RWS), version 0.8
+ Doodle's Screen Saver (DSSaver), version 1.8 or later
==========================================================================
================================================================================
Installation Instructions
==========================================================================
================================================================================
It is strongly recommended that you exit all programs before running the
setup program. Also, you should temporarily disable virus-detection
software.
Install into a clean (new) directory. Installing on top of previously
released builds may cause problems.
Unpack into a clean (new) directory. Installing on top of previously released
builds may cause problems with SeaMonkey. It is therefore hightly recommended
to follow the instructions under "Separating profiles from installation
directory".
Note: These instructions do not tell you how to build SeaMonkey.
For info on building SeaMonkey from the mozilla.org source code, see
http://developer.mozilla.org/en/docs/Build_Documentation
For info on building the SeaMonkey source, see
https://developer.mozilla.org/en/Build_Documentation
OS/2 Installation Instructions
------------------------------
To install SeaMonkey by downloading the SeaMonkey installer, follow
these steps:
On OS/2, SeaMonkey does not have an installation program. To install it,
download the .zip file and follow these steps:
1. Click the "Installer" link on the site you're downloading SeaMonkey
from to download the installer file to your machine. This file is
typically called seamonkey-x.xx.en-US.os2.installer.exe where the
"x.xx" is replaced by the SeaMonkey version.
1. Click the "Zip" link on the site you're downloading SeaMonkey from to
download the ZIP package to your machine. This file is typically called
seamonkey-x.x.x.en-US.os2.zip where the "x.x.x" is replaced by the
current SeaMonkey version.
2. Navigate to where you downloaded the file, make sure that the C
library DLLs are copied to the same directory or installed in the
LIBPATH, and double-click on the the SeaMonkey installer object to
start the Setup program.
2. Navigate to where you downloaded the file and unpack it using your favorite
unzip tool.
3. Follow the on-screen instructions in the setup program. The program
automatically ends any running SeaMonkey sessions and creates a
SeaMonkey folder on the Desktop. To start SeaMonkey the first time,
again make sure that the C library DLLs are copied to the
installation directory or installed in the LIBPATH and then
double-click the SeaMonkey program object inside this folder.
3. Keep in mind that the unzip process creates a directory "seamonkey" below
the location you point it to, e.g.
unzip seamonkey-2.0.en-US.os2.zip -d c:\seamonkey-2.0
will unpack SeaMonkey into c:\seamonkey-2.0\seamonkey.
To install SeaMonkey by downloading the .zip file and installing
manually, follow these steps:
4. Make sure that you are _not_ unpacking over an old installation. This is
known to cause problems.
1. Click the "Zip" link on the site you're downloading SeaMonkey from
to download the ZIP package to your machine. This file is typically
called seamonkey-x.x.x.en-US.os2.zip where the "x.x.x" is replaced
by the SeaMonkey version.
2. Navigate to where you downloaded the file and unpack it using your
favorite unzip tool.
3. Keep in mind that the unzip process creates a directory "seamonkey"
below the location you point it to, e.g.
unzip seamonkey-1.7.5.en-US.os2.zip -d c:\seamonkey-1.7.5
will unpack SeaMonkey into c:\seamonkey-1.7.5\seamonkey.
4. Make sure that you are _not_ unpacking over an old installation.
This is known to cause problems.
5. To start SeaMonkey, navigate to the directory you extracted
SeaMonkey to, make sure that the C library DLLs are copied to the
installation directory or installed in the LIBPATH, and then
double-click the seamonkey.exe object.
5. To start SeaMonkey, navigate to the directory you extracted SeaMonkey to,
ensure that the C library DLL is copied to the installation directory or
installed in the LIBPATH, and then double-click the seamonkey.exe object.
Running multiple versions of SeaMonkey concurrently
-------------------------------------------------
================================================================================
Because various members of the Mozilla family (i.e. SeaMonkey, Mozilla,
Firefox, Thunderbird, IBM Web Browser) may use different, incompatible
versions of the same DLL, some extra steps may be required to run them
concurrently.
Tips and Problems
One workaround is the LIBPATHSTRICT variable. To run Mozilla-based
applications one can create a CMD script like the following example
(where an installation of SeaMonkey exists in the directory
d:\internet\seamonkey is assumed):
================================================================================
Running multiple versions concurrently
--------------------------------------
If you want to run more than one copy of SeaMonkey, you have to use the
-no-remote parameter or set MOZ_NO_REMOTE=1 in your environment.
Because various members of the Mozilla family (i.e. SeaMonkey, Mozilla, Firefox,
Thunderbird, IBM Web Browser) may use different, incompatible versions of the
same DLL, some extra steps may be required to run them concurrently.
One workaround is the LIBPATHSTRICT variable. To run SeaMonkey one can create
a CMD script like the following example (where an installation of SeaMonkey
in the directory d:\internet\seamonkey is assumed):
set LIBPATHSTRICT=T
rem The next line may be needed when a different Mozilla program is listed in LIBPATH
@ -200,7 +170,7 @@ script above depending on the system configuration.)
Finally, the simplest method is to use the Run! utility by Rich Walsh that
can be found in the Hobbes Software Archive:
http://hobbes.nmsu.edu/cgi-bin/h-search?key=Run!
http://hobbes.nmsu.edu/h-search.php?key=Run!
Read its documentation for more information.
@ -208,16 +178,19 @@ Read its documentation for more information.
Separating profiles from installation directory
-----------------------------------------------
To separate the locations of the user profile(s) (containing the bookmarks
and all customizations) from the installation directory to keep your
preferences in the case of an update even when using ZIP packages, set the
variable MOZILLA_HOME to a directory of your choice. You can do this
either in Config.sys or in a script or using a program object as listed
above. If you add
To separate the locations of the user profile(s) (containing the bookmarks and
all customizations) from the installation directory to keep your preferences in
the case of an update even when using ZIP packages, set the variable
MOZILLA_HOME to a directory of your choice. You can do this either in Config.sys
or in a script or using a program object as listed above. If you add
set MOZILLA_HOME=f:\Data
the user profile(s) will be created in "f:\Data\Mozilla\Profiles".
the SeaMonkey user profile will be created in "f:\Data\Mozilla\SeaMonkey".
If you are migrating from Mozilla, SeaMonkey's import routine will only find
the existing Mozilla profile data if MOZILLA_HOME is correctly set to point to
it.
Other important environment variables
@ -227,36 +200,131 @@ There are a few enviroment variables that can be used to control special
behavior of SeaMonkey on OS/2:
- set NSPR_OS2_NO_HIRES_TIMER=1
This causes SeaMonkey not to use OS/2's high resolution timer. Set this
if other applications using the high resolution timer (multimedia apps)
act strangely.
This causes SeaMonkey not to use OS/2's high resolution timer. Set this if
other applications using the high resolution timer (multimedia apps) act
strangely.
- set MOZ_NO_REMOTE=1
Use this to run two instances of SeaMonkey simultaneously (e.g. debug
Use this to run two instances of SeaMonkey simultaneously (like e.g. debug
and optimized version).
- set MOZ_NO_RWS=1
Use this to disable Remote Workplace Server support (see below).
Find more information on this topic and other tips on
http://www.os2bbs.com/os2news/Warpzilla.html
Support for WPS objects
-----------------------
SeaMonkey can make use of Rich Walsh's Remote Workplace Server (RWS) library
to access Workplace Shell objects from the application. This allows helper
applications for downloaded files to be selected based on their default WPS
association.
To enable this functionality, SeaMonkey has to find the RWS DLLs. They have to
be located in a directory on the LIBPATH, in the SeaMonkey directory, or
already be registered as a WPS class. For eComStation 2 this is already the
case. If RWS is not yet available on your system, download it from
http://hobbes.nmsu.edu/h-search.php?key=rws08dll
If RWS is found on the system, it is used by SeaMonkey automatically. In case
you need to disable RWS support, create an environment variable MOZ_NO_RWS and
set it to 1.
Idle timer for internal cleanups
--------------------------------
If Doodle's Screen Saver (DSSaver) v1.8 or later is installed, SeaMonkey can
determine how long the user has been inactive. If the user has been inactive
for a while, cleanup operations may be performed.
DSSaver can be downloaded from
ftp://ftp.netlabs.org/pub/dssaver/dssaver_v18.zip
Setting the OS/2 default web applications
-----------------------------------------
The default web browser can be set using WPS URL objects. The properties
notebook of every URL object contains a "Browser" tab where the browser
executable can be selected. Any changes to these settings will be stored and
reflected in all URL objects once the user presses the "Set Default" button.
The default mail, news, and irc applications can be set by editing the USER_INI
file.
Two small applications make this change a bit easier and provide options to also
set default programs for other types of internet-related activities:
- ConfigApps
http://hobbes.nmsu.edu/h-search.php?key=configapps1_1
- Internet Application Integration
http://7cities.net/~mckinnis/os2/
Changed font handling
---------------------
To be able to display text, SeaMonkey cannot make use of normal OS/2 routines
but has to use FreeType and FontConfig. This has the advantage that text can
be displayed with antialiasing, but at the same time has some caveats:
- SeaMonkey cannot make use of OS/2 fonts like WarpSans and others which
are not available in Type1 or TrueType format. It is therefore
recommended to install the "Workplace Sans" font from
http://users.socis.ca/~ataylo00/creative/fonts/
or
http://hobbes.nmsu.edu/h-search.php?key=wpsu_ttf
which SeaMonkey will use as a replacement of WarpSans.
- Display of text in some languages (e.g. Arabic) does not yet take into account
that different forms of some characters exist.
To tweak the appearance of text, you can add two preferences, preferably using
about:config.
- gfx.os2.font.antialiasing (Boolean)
This preference controls whether antialiasing is enabled, and defaults to
true.
- gfx.os2.font.hinting (Integer)
This preference controls the hinting level, and can be between 0 (no hinting)
and 3 (full hinting). The default value is 2.
Font hinting improves the contrast of displayed text, but may produce poor
results for certain characters of some fonts, most notably the OS/2 version
of "Times New Roman".
Note that these preferences only take effect when a font gets used for the first
time, so you may need to restart the application to see the full effect.
Known Problems of the OS/2 version
----------------------------------
Cross-platform problems are usually listed in the release notes of each
milestone release.
- Printing to normal OS/2 printer queues had to be disabled. It was slow even
for simple pages and used huge amounts of RAM, so that in most cases the
application crashed, see https://bugzilla.mozilla.org/show_bug.cgi?id=415522.
While the queues are still displayed in the printing dialog, any printing
operation will instead create a PDF file. By default this file is placed on
the Desktop, with the name SeaMonkey_<date>_<time>.pdf, where <date> and
<time> are replaced by the current system time. If you want to use another
name, select "Print to file" before pressing the Print button.
The resulting PDF file can be printed using applications like Lucide, Acrobat
Reader, or GSview.
- Fonts with names containing special characters (like Asian Unicode names)
will not display correctly in the list of fonts in the Options panel.
- SeaMonkey 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.
- SeaMonkey cannot make use of OS/2 fonts like WarpSans and others which
are not available in Type1 or TrueType format. It is therefore
recommended to install the "Workplace Sans" font from
http://users.socis.ca/~ataylo00/creative/fonts/
or
http://hobbes.nmsu.edu/cgi-bin/h-search?key=wpsu_ttf
which SeaMonkey will use as a replacement of WarpSans.
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/>.
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/>.

View File

@ -1,6 +1,6 @@
================================================================================
= = = = = = = = = = = = = Thunderbird Read Me = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = Thunderbird Read Me = = = = = = = = = = = = = = =
================================================================================
@ -12,11 +12,11 @@ installation instructions for the OS/2 build of Thunderbird.
For more info on Thunderbird, see http://www.mozilla.org/products/thunderbird/.
For more info on the OS/2 port see http://www.mozilla.org/ports/os2. To submit
bugs or other feedback check out Bugzilla at https://bugzilla.mozilla.org for
links to known bugs, bug-writing guidelines, and more. You can also get help
with Bugzilla by pointing your IRC client to #mozillazine at irc.mozilla.org,
OS/2 specific problems are discussed in #warpzilla and in the newsgroup
mozilla.dev.ports.os2 on news.mozilla.org.
bugs reports go to Bugzilla at https://bugzilla.mozilla.org.
For discussion and help for OS/2 specific problems, please use the newsgroup
mozilla.dev.ports.os2 on news.mozilla.org. You can also get help by pointing
your IRC client to the #warpzilla channel on irc.mozilla.org.
================================================================================
@ -27,12 +27,13 @@ mozilla.dev.ports.os2 on news.mozilla.org.
Official Milestone builds of Thunderbird are published on the release page at
http://www.mozilla.org/products/thunderbird/releases/
http://www.mozilla.com/en-US/thunderbird/releases/
OS/2 releases are not created by Mozilla.org staff and may appear on the page
http://www.mozilla.org/ports/os2 before the releases page. Be sure to read the
Thunderbird release notes linked on the releases page for information on known
problems and installation issues with Thunderbird.
OS/2 releases are not created by Mozilla staff and may appear on the
page http://www.mozilla.org/ports/os2 before the releases page. Be sure to read
the release notes linked on the releases page for information on known problems
and installation issues.
OS/2 specific problems with this version are listed below.
================================================================================
@ -41,29 +42,28 @@ problems and installation issues with Thunderbird.
================================================================================
- This release requires the C runtime DLLs (libc-0.6.1) from
ftp://ftp.netlabs.org/pub/gcc/libc-0.6.1-csd1.zip
- This release requires the C runtime DLL (libc063.dll) from
ftp://ftp.netlabs.org/pub/gcc/libc-0.6.3-csd3.zip
in order to run. You can unpack them in the same directory as the
Thunderbird executable or somewhere else in your LIBPATH.
- Minimum hardware requirements
+ Pentium class processor
+ 64 MiB RAM plus 64 MiB free swap space
+ 35 MiB free harddisk space for installation
plus storage space for disk cache
+ 400 MHz Pentium class processor
+ 128 MiB RAM plus 128 MiB free swap space
+ 40 MiB free harddisk space for installation
plus storage space for messages and disk cache
+ Graphics card and driver capable of displaying more than 256 colors
- Recommended hardware for acceptable performance
+ 500 MHz processor
+ 256 MiB RAM plus 64 MiB free swap space
+ 1.0 GHz processor
+ 512 MiB RAM plus 128 MiB free swap space
NOTE: Thunderbird's performance and stability increases the more physical
RAM is available. Especially for long sessions 512 MiB of memory is
recommended.
+ Graphics card and driver capable of displaying more than 256 colors
RAM is available.
- Software requirements
+ Installation on a file system supporting long file names
(i.e. HPFS or JFS but not FAT)
+ OS/2 Warp 4 with Fixpack 15 or later
+ OS/2 Warp 4 with Fixpack 15 or later (Warp 3 may work but is unsupported)
+ MPTS version 5.3
+ TCP/IP version 4.1
+ INETVER: SOCKETS.SYS=5.3007, AFOS2.SYS=5.3001, AFINET.SYS=5.3006
@ -75,6 +75,14 @@ problems and installation issues with Thunderbird.
+ Convenience Pack 2 or eComStation 1.0 or later meet these requirements
out of the box.
+ Only Java plugins of version 1.4.1 or 1.4.2 are supported.
(IBM Java 1.3.1 or earlier will crash the application!)
- Useful optional software
The following packages enable additional features in Thunderbird. Download
locations are listed below with a detailed description of the features.
+ Remote Workplace Server (RWS), version 0.8
+ Doodle's Screen Saver (DSSaver), version 1.8 or later
================================================================================
@ -82,58 +90,67 @@ problems and installation issues with Thunderbird.
================================================================================
For all platforms, unpack into a clean (new) directory. Installing on top of
previously released builds may cause problems with Thunderbird.
Unpack into a clean (new) directory. Installing on top of previously released
builds may cause problems with Thunderbird. It is therefore hightly recommended
to follow the instructions under "Separating profiles from installation
directory".
Note: These instructions do not tell you how to build Thunderbird.
For info on building the Thunderbird source, see
http://www.mozilla.org/build/
https://developer.mozilla.org/en/Build_Documentation
OS/2 Installation Instructions
------------------------------
On OS/2, Thunderbird does not have an installation program. To install it,
download the .zip file and follow these steps:
On OS/2, Thunderbird does not have an installation program. To install it,
download the .zip file and follow these steps:
1. Click the "Zip" link on the site you're downloading Thunderbird from
to download the ZIP package to your machine. This file is typically called
thunderbird-x.x.x.en-US.os2.zip where the "x.x.x" is replaced by the
Thunderbird version.
1. Click the "Zip" link on the site you're downloading Thunderbird from to
download the ZIP package to your machine. This file is typically called
thunderbird-x.x.x.en-US.os2.zip where the "x.x.x" is replaced by the
current Thunderbird version.
2. Navigate to where you downloaded the file and unpack it using your
favorite unzip tool.
2. Navigate to where you downloaded the file and unpack it using your favorite
unzip tool.
3. Keep in mind that the unzip process creates a directory "thunderbird"
below the location you point it to, e.g.
unzip thunderbird-1.0.1.en-US.os2.zip -d c:\thunderbird-1.0.1
will unpack Thunderbird into c:\thunderbird-1.0.1\thunderbird.
3. Keep in mind that the unzip process creates a directory "thunderbird" below
the location you point it to, e.g.
unzip thunderbird-3.0.en-US.os2.zip -d c:\thunderbird-3.0
will unpack Thunderbird into c:\thunderbird-3.0\thunderbird.
4. Make sure that you are _not_ unpacking over an old installation. This is
known to cause problems.
4. Make sure that you are _not_ unpacking over an old installation. This is
known to cause problems.
5. To start Thunderbird, navigate to the directory you extracted
Thunderbird to, make sure that the C library DLLs are copied to the
installation directory or installed in the LIBPATH, and then double-click
the thunderbird.exe object.
5. To start Thunderbird, navigate to the directory you extracted Thunderbird to,
ensure that the C library DLL is copied to the installation directory or
installed in the LIBPATH, and then double-click the thunderbird.exe object.
================================================================================
Tips and Problems
================================================================================
Running multiple versions concurrently
--------------------------------------
Because various members of the Mozilla family (i.e. Mozilla, Firefox,
If you want to run more than one copy of Thunderbird, you have to use the
-no-remote parameter or set MOZ_NO_REMOTE=1 in your environment.
Because various members of the Mozilla family (i.e. SeaMonkey, Mozilla, Firefox,
Thunderbird, IBM Web Browser) may use different, incompatible versions of the
same DLL, some extra steps may be required to run them concurrently.
One workaround is the LIBPATHSTRICT variable. To run Thunderbird one can create
a CMD script like the following example (where an installation of Thunderbird
exists in the directory d:\internet\thunderbird is assumed):
in the directory d:\internet\thunderbird is assumed):
set LIBPATHSTRICT=T
rem The next line may be needed when a different Mozilla program is listed in LIBPATH
rem set BEGINLIBPATH=d:\internet\thunderbird
rem The next line is only needed to run two different versions of Thunderbird
rem The next line is only needed to run two versions of the same program
rem set MOZ_NO_REMOTE=1
d:
cd d:\internet\thunderbird
@ -152,7 +169,7 @@ above depending on the system configuration.)
Finally, the simplest method is to use the Run! utility by Rich Walsh that can
be found in the Hobbes Software Archive:
http://hobbes.nmsu.edu/cgi-bin/h-search?key=Run!
http://hobbes.nmsu.edu/h-search.php?key=Run!
Read its documentation for more information.
@ -162,13 +179,13 @@ Separating profiles from installation directory
To separate the locations of the user profile(s) (containing the bookmarks and
all customizations) from the installation directory to keep your preferences in
the case of an update even when using ZIP packages, set the variable
the case of an update even when using ZIP packages, set the variable
MOZILLA_HOME to a directory of your choice. You can do this either in Config.sys
or in a script or using a program object as listed above. If you add
set MOZILLA_HOME=f:\Data
the Thunderbird user profile will be created in "f:\Data\Thunderbird".
the Thunderbird user profile will be created in "f:\Data\Mozilla\Thunderbird".
If you are migrating from Mozilla, Thunderbird's import routine will only find
the existing Mozilla profile data if MOZILLA_HOME is correctly set to point to
@ -190,28 +207,119 @@ behavior of Thunderbird on OS/2:
Use this to run two instances of Thunderbird simultaneously (like e.g. debug
and optimized version).
- set MOZ_NO_RWS=1
Use this to disable Remote Workplace Server support (see below).
Find more information on this topic and other tips on
http://www.os2bbs.com/os2news/Warpzilla.html
Support for WPS objects
-----------------------
Thunderbird can make use of Rich Walsh's Remote Workplace Server (RWS) library
to access Workplace Shell objects from the application. This allows helper
applications for downloaded files to be selected based on their default WPS
association.
To enable this functionality, Thunderbird has to find the RWS DLLs. They have to
be located in a directory on the LIBPATH, in the Thunderbird directory, or
already be registered as a WPS class. For eComStation 2 this is already the
case. If RWS is not yet available on your system, download it from
http://hobbes.nmsu.edu/h-search.php?key=rws08dll
If RWS is found on the system, it is used by Thunderbird automatically. In case
you need to disable RWS support, create an environment variable MOZ_NO_RWS and
set it to 1.
Idle timer for internal cleanups
--------------------------------
If Doodle's Screen Saver (DSSaver) v1.8 or later is installed, Thunderbird can
determine how long the user has been inactive. If the user has been inactive
for a while, cleanup operations may be performed.
DSSaver can be downloaded from
ftp://ftp.netlabs.org/pub/dssaver/dssaver_v18.zip
Setting the OS/2 default mail and news program
----------------------------------------------
The default mail and news applications can be set by editing the USER_INI
file.
Two small applications make this change a bit easier and provide options to also
set default programs for other types of internet-related activities:
- ConfigApps
http://hobbes.nmsu.edu/h-search.php?key=configapps1_1
- Internet Application Integration
http://7cities.net/~mckinnis/os2/
Changed font handling
---------------------
To be able to display text, Thunderbird cannot make use of normal OS/2 routines
but has to use FreeType and FontConfig. This has the advantage that text can
be displayed with antialiasing, but at the same time has some caveats:
- Thunderbird cannot make use of OS/2 fonts like WarpSans and others which
are not available in Type1 or TrueType format. It is therefore
recommended to install the "Workplace Sans" font from
http://users.socis.ca/~ataylo00/creative/fonts/
or
http://hobbes.nmsu.edu/h-search.php?key=wpsu_ttf
which Thunderbird will use as a replacement of WarpSans.
- Display of text in some languages (e.g. Arabic) does not yet take into account
that different forms of some characters exist.
To tweak the appearance of text, you can add two preferences, preferably using
about:config.
- gfx.os2.font.antialiasing (Boolean)
This preference controls whether antialiasing is enabled, and defaults to
true.
- gfx.os2.font.hinting (Integer)
This preference controls the hinting level, and can be between 0 (no hinting)
and 3 (full hinting). The default value is 2.
Font hinting improves the contrast of displayed text, but may produce poor
results for certain characters of some fonts, most notably the OS/2 version
of "Times New Roman".
Note that these preferences only take effect when a font gets used for the first
time, so you may need to restart the application to see the full effect.
Known Problems of the OS/2 version
----------------------------------
Cross-platform problems are usually listed in the release notes of each
milestone release.
- Printing to normal OS/2 printer queues had to be disabled. It was slow even
for simple pages and used huge amounts of RAM, so that in most cases the
application crashed, see https://bugzilla.mozilla.org/show_bug.cgi?id=415522.
While the queues are still displayed in the printing dialog, any printing
operation will instead create a PDF file. By default this file is placed on
the Desktop, with the name Thunderbird_<date>_<time>.pdf, where <date> and
<time> are replaced by the current system time. If you want to use another
name, select "Print to file" before pressing the Print button.
The resulting PDF file can be printed using applications like Lucide, Acrobat
Reader, or GSview.
- Fonts with names containing special characters (like Asian Unicode names)
will not display correctly in the list of fonts in the Options panel.
- Thunderbird 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.
- Thunderbird cannot make use of OS/2 fonts like WarpSans and others which
are not available in Type1 or TrueType format. It is therefore
recommended to install the "Workplace Sans" font from
http://users.socis.ca/~ataylo00/creative/fonts/
or
http://hobbes.nmsu.edu/cgi-bin/h-search?key=wpsu_ttf
which Thunderbird will use as a replacement of WarpSans.
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/>.