Many of the instructions for installing Office 2003 that can be found on various websites are badly outdated.
Current versions of Wine do not require any overrides to install Office 2003 Pro. Install as you would in Windows: insert the cd and run setup.exe.
Do not report bugs for the installer if you have used any overrides.
If you are using a version of Wine older than 1.0, you should upgrade to either the current stable or development release.
Once Office 2003 is installed, you may wish to set an override for
riched20.dll so that Office will use the riched20 that it installs
itself. (There is no need to copy the file or use winetricks--just set
the override in winecfg.)
Known regressions (do not attempt to install in these versions):
1.1.17 through 1.1.23
1.1.1 and 1.1.2
1.1.2 through 1.1.9 (German and Spanish versions of Office 2003)
Older versions of Wine apparently had problems with the language bar. A user posted these instructions to disable it:
$ wine cmd
$ c:\>regsvr32.exe /u msutb.dll
$ c:\>exit
Now rename ctfmon.exe in your .wine/drive_c/windows/system32 to something else (or just delete it).
Questions?
The comments below are not regularly monitored. Please post any questions or requests for help on the forum.
Guidelines for Submitting Test Reports
Test in a clean wineprefix with plain Wine.
Specify exactly which edition of Office 2003 you tested (Standard, Pro, etc.) This is crucial--bugs that affect one edition may not affect others.
Specify exactly what type of install you tested (Typical, Custom, Minimal, etc.)
Limit your report to the installer only. Reports on the performance of individual apps should be filed under their respective AppDB entries. Problems with running any of the apps should only be mentioned if it is clear that it is due to a problem with the installer.
If you used any overrides during the install, please list them and explain exactly what problem each override was needed to solve.
Test reports that do not follow these guidelines will be rejected.
