M3 Release Notes

• Installation Instructions - Unix
• Installation Instructions - Win32
• Installation Instructions - Mac OS
• Files Created or Used
• Limited Support Features
• Known Issues
• International Issues

Installing the M3 Release Build

Unix Instructions

1. Create a directory named "mozilla" and move the tar.gz file into the mozilla directory.
2. Change to the mozilla directory (cd mozilla) and untar the archive (gzip -cd mozilla-i686-pc-linux-gnu.tar.gz | tar -xvf -).

This will create a directory called "package."
3. Change to the "package" directory.
4. Type (pwd) and remember the result; you will need it for steps 4-6. It might look like:  /home/me/mozilla/package.
5. If you are running tcsh or csh, type

( setenv MOZILLA_FIVE_HOME RESULT_OF_STEP_4 )
and then type
( setenv LD_LIBRARY_PATH RESULT_OF_STEP_4:/lib:/usr/lib )
6. If you are running bash, sh, or ksh, type

( export MOZILLA_FIVE_HOME=RESULT_OF_STEP_4 )
and then type
( export LD_LIBRARY_PATH=RESULT_OF_STEP_4:/lib:/usr/lib )
7. Enter (cd ..) and create a directory named "user".
8. Change to directory "user" and type

../package/apprunner

Win32 Instructions

1. Click once on the mozilla-win32.zip link. The file will be downloaded to your default folder.
2. Click on the mozilla-win32.zip file to launch WinZip.
3. After clicking  "I Agree" to terms of WinZip shareware, click the Extract button in the WinZip tool bar. An x86 folder with application and associated files will be unzipped.
4. Select Apprunner from x86 folder to launch the program.

• Run "apprunner.exe" to use browser and mail.
• Run "viewer.exe" to run only the gecko layout engine

Mail Win32 Instructions

1. Unzip/extract the seamonkey.zip file.

It should create a "\x86rel" directory with subdirectories (cache, components, mimeplugins, plugin and res).
2. The current build reads the following preferences, assuming a preferences (prefs.js) file exists in the same directory as Apprunner. Substitute your actual preferences for the dummy values. (Use notepad.exe or other text editor and be sure to save the file with a ".js" extension):
user_pref("mail.rootFolder", "c:\\program files\\netscape\\users\\test\\mail");
user_pref("network.hosts.pop_server", "dredd");
user_pref("network.hosts.smtp_server", "dredd");
user_pref("mail.smtp_name", "test");
user_pref("mail.pop_name", "test");
user_pref("mail.pop_password", "clear text pop password");
user_pref("mail.identity.reply_to", "test@netscape.com");
user_pref("mail.identity.organization", "Mozilla.Org");
user_pref("mail.identity.useremail", "test@netscape.com");
user_pref("mail.identity.username", "Mozilla Q. Dragon");
user_pref("browser.download_directory", "C:\\TEMP\\");

Note: If you are unable to send mail, make sure the directory specified at "browser.download_directory" actually exists.

3. Verify the prefs.js file is in the \x86rel directory.
4.  You can bring up Messenger using any of these methods:

a) from command line using this argument:  url resurce:/res/samples/mailshell.xul
b) or, from within apprunner's UI under Tasks | Messenger
c) or, from command line using -mail argument
The application should show a mail UI.
5. You should be able to see your Inbox with messages.  Also, you should be able to see your mail folders in the folder pane.

MacOS Instructions

1. Click once on the mozilla-mac.sea.bin link. The file will be downloaded to your default folder (usually the desktop) and Stuffit will start up and convert it to mozilla-mac.sea for you. Then stuffit will open up mozilla-mac.sea and convert it to a folder called mozilla-mac for you.
2. Open the mozilla-mac folder and double-click the file "apprunner." (Note: you no longer need the .bin files.)

If you do not have  Stuffit Expander™ installed or your browser is not properly configured:

1. Make sure you have Stuffit™ somewhere on your hard drive.
2. Click and hold the mozilla-mac.sea.bin link.
3. Choose "Save this link as...".

You see a file dialog box where you can select where you want to save the file (for example, your Desktop).
4. Click the Save button.
5. Double-click on the newly created icon "mozilla-mac.sea.bin".
6. Stuffit™ will start up and simultaneously create a file "mozilla-mac.sea", and a folder called "mozilla-mac."
7. Open the mozilla-mac folder and double-click the file "apprunner." (Note: you no longer need the .bin files.)

Files Created or Used

*Note:"cookterm.txt" is a file created for Windows, used to selectively accept cookies from certain sites and not from others. It is used only if you set your preferences so you see a warning before accepting cookies. To do that, hand edit the prefs.js file to include:

 
user.pref ("network.cookie.rememberAboutCookies", true);

Limited Support Features

 
 

Available Navigator Functionality

Functionality	Description	Comments
Back, Forward, Reload
Location Field	Can browse by entering URLs
Various Menu Commands	Menus do work, but many commands not hooked up.  Menus items that do work include: File menu: New Browser Window, New > Blank Page / Page using Template ... / Page using Draft ..., Quit;  Go menu; Bookmarks menu (except Add commands)
Toolbars	Toolbars display above and below content window, most buttons working though a couple are not hooked up to execute a command.	No toolbar hiding or moving enabled yet.
Link Buttons	Buttons that simply link to a web address, including the N brand button, Home, My Netscape.
Access Personal Toolbar	Links in Personal Toolbar display and can be used	Can't add or edit
Access Bookmarks	Access Bookmarks through Bookmarks menu, can't add or edit.	Can load your current bookmarks file.  See instructions under platform installations.
Access via Manage  Bookmarks Window	Can open and close folders, one click to launch bookmarked URL in new toolbar-less window. File menu > New Window command also works.
Status Display	Toolbar beneath content area, status during loading of URLs.

Additionally:

• Apprunner reads the Preferences file from the current directory, not from the executable directory. The preferences file names are:

 
• Windows: prefs.js
• UNIX: preferences.js
• MacOS: Netscape Preferences

 
• On UNIX, preferences are not read from ~/.mozilla/.

Known Issues

• MacOS only: Apple and applications menus are missing. Also, Apprunner starts up with a blank window. Workaround: Remove all non-7-bit ASCII characters and slashes from all superdirectories of your Apprunner file.

 
• Loading problems (possible crash or freeze) sometimes occurs on pages which contain applets.

 
• Within Viewer, the Debug & Tools menu options are not currently working or produce unpredictable results. Choosing Java Console from the Tools menu causes the application to freeze or crash.

 
• If you have local folders with many saved messages (hundreds or thousands), don't point the Mail application at your actual local folder hierarchy. All folders reparse at startup, and vast quantities of memory could be consumed if your total number of messages is high.

 
• Floppy diskettes inserted while Apprunner is running are not mounted.

 
• Information about preferences related to saving username/password or form data:
1. To see a warning prompt before saving username/password or form data, set the following preference (by hand) in your prefs.js file:

 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

user_pref("wallet.useDialogs", true);

This pref is false by default, so saving will be done silently. This is done because there currently are no dialog boxes and the warning prompt would occur in the console window.
1. To suppress saving of form data altogether, set the following preference (by hand) in your prefs.js file:

 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

user_pref("wallet.captureForms", false);

This preference is true by default.

2. To supress saving of username/password, set the following preference (by hand) in your prefs.js file:

 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

user_pref("network.singon.rememberSignons", false);

This preference is true by default.

• Issues in the Mail Compose window:

 
• The cursor does not appear in the message field until you begin typing.
• At the end of a line, you may need to press Enter twice before the cursor moves to the next line.
• The received message does not wrap lines, so you may want to embed hard returns in your messages.
• Messages may contain either too much vertical white space or not enough.

 
• The following toolbar and menu items are either not fully functional or disabled:
• Back button (doesn't work with manually entered URLs)
• Stop button
• Close menu item (use Close box to close windows)
• Print (toolbar button & menu item) and Print Preview

 
Also, keyboard shortcuts/command keys are not available for most menu items with the exception of the following for the mail compose window: Ctrl-C (copy), Ctrl-V (paste), Ctrl-Z (undo). and Ctrl-Y(redo) and their Unix and MacOS equivalents.
 

International M3 Release

• For M3, you must use a font with an ASCII font name. Some Japanese Windows users will not be able to use native fonts which come with Windows-Japanese versions and should download these Bitstream Cyberbit fonts from the ftp server:    ftp://ftp.netscape.com/pub/communicator/extras/fonts/windows/CYBERBIT.TTF.  Refer to the    "READMEfirst.txt" file for usage information.
• Font preference setting, modify prefs.js directly. For Japanese or non-Japanese Windows browsing only with Bitstream Cyberbit font installed:

             // Netscape User Preferences
            // This is a generated file!  Do not edit.
            user_pref("intl.character_set", 2308);
            user_pref("intl.font260.win.fixed_font", "Bitstream Cyberbit");
            user_pref("intl.font260.win.fixed_size", 12);
            user_pref("intl.font260.win.prop_font", "Bitstream Cyberbit");
            user_pref("intl.font260.win.prop_size", 12);

• For non-Japanese Windows browsing only with MS Gothic font installed (licensed only for IE users). If the Japanese MS Gothic font happens to work OK with M3 on your Japanese Windows, then   replace the English name "MS Gothic" below with the Japanese name:

Note: these are browsing only settings. For Japanese mail display, additional mail server info must be provided. See below in the Mail section for detailed info. 

• Browsing Japanese HTML Pages
• Platforms:

Win32 Ja
MacOS 8.5 w/Japanese Language Kit
• Encodings:

Shift_JIS
EUC-JP ISO-2022-JP
• (Non-Latin1) Pages must have charset info in <META> tags
• Need to click Reload to correctly display the first part of (a non-Latin1) page

• Browsing Latin1 HTML Pages
• Platforms:

Win32
MacOS 8.1 (or higher)
Linux
 
• Printing disabled for M3

International M3 Mail Application

• Platforms: Win32 Ja
• 8-bit display im mail is dependent on the system charset. Japanese display requires Japanese Windows.
• US Windows can display Latin 1, but not other charsets, etc.  Note that no special font settings are required for Latin 1 display under US Windows -- just modify the mail server settings in the prefs.js file.
• For a sample prefs.js file for Japanese mail and browsing with the Bitstream Cyberbit font, download  the following sample file and modify the mail server settings as needed:     http://home.netscape.com/eng/intl/docs/comm5/cyberbit-prefs/  (prefs.js file for Bitstream Cyberbit font)
• Because of the limitation noted in the browser section for this release, "MS Gothic (in Japanese)" font may  not work for all Japanese Windows settings. But if the Japanese MS Gothic font works OK on your Japanese Windows system with M3, then, download the following sample prefs.js file for "MS Gothic" font and change the font name into Japanese and modify server info as needed. Note that the English font name "MS Gothic" will not work on Japanese Windows:   http://home.netscape.com/eng/intl/docs/comm5/msgothic-prefs/ (prefs.js file for Japanese MS Gothic font)
• Features that are not supported:
• No Japanese rendering on Linux
• No Japanese IME support
• "View|Character Set" menu not functional (Bug 2341)
• No Japanese Auto-Detect
• No MIME decoding in mail thread pane
• No Japanese mail composition (including forward and reply)
• No MIME-compliant Latin1 mail composition (M3 strips out 8-bit characters in email)
• No posting non-ASCII forms data
• No Japanese printing on Linux