(Updated 2012-03-19)

1.4-rc1: SP2 & SP3 do not install correctly

1.3.30

1.3.21: SP2 does not install correctly

1.3.16-1.3.17
1.3.7­­­
1.3.2
1.2.0 and 1.2.1 (Ubuntu and other distro packages compiled with fortify)
1.1.17 throug­h 1.1.23
­
­all versions prior to 1.1.3 ­(i­ncludes 1.0.1)

­­­­­(Updated 2012-2-26)

­Note: these instructions have been tested and verified to work on the Enterprise, Pro, and Home & Student editions of Office 2007, installing from a cd.

How To Install Microsoft Office 2007

Use the most recent version of Wine known to work for Office 2007 (see list of known bad versions above). In most cases this will be the latest development release. 

Install to a clean wineprefix (no winetricks or other tweaks, no other applications installed).

­­Note: I­f you have 64 bit Wine inst­alled, you must create a 32 bit wineprefix for Office 2007 or the installed programs will not be usable.­

­ WINEARCH=win32 WINEPREFIX=/path/to/wineprefix winecfg

­­(Substitute the actual path for /path/to/wineprefix in the above command.) ­

Make sure your version of wine is set to Windows XP. 

Insert the disk.

Open the disk and right click on setup.exe and select "Open with wine windows program loader." Or open a terminal, navigate to the disk, and run the installer with: 

wine setup.exe

The progress bar in the installer window may stop when it reaches about 2/3 of the way. The installation is continuing, even though the the progress bar is not moving. Wait for it to finish.

Note :­No overrides are nee­ded to install Microsoft Office 2007. However to get Microsoft Office 2007 to run correctly once it has been installed some overrides may be necessary. See below for instructions.

Post Installation Instructions­

Once installed, one override is necessary. Without it, Powerpoint and Infopath with not start, and some dialog boxes in other Office apps will not display correctly. Follow the steps below:

Open winecfg by going to Applications > Wine > Configure Wine. Or open a terminal and type: 

winecfg

In the Libraries tab in the area labeled "New override for library" type in riched20.dll and click on Add.

You will see it appear in the list below. Now select the riched20 in the list that we just added and click on the Edit button.

Set it to Native (Windows) and click OK.

This will allow Powerpoint and the other applications to run correctly.

Note :Do not install riched20 with winetricks. Office 2007 installs its own version of riched20.

If Office is installed in a separate wineprefix (strongly recommended), you can safely set the override globally. If not, set the overrides separately for each Office application. Note that if you do the latter you must set the override for all exes installed by Office, not just the main ones.

­Installing Office 2007 Service Packs­

Service Packs install correctly for versions 1.3.18 through 1.3.20, and 1.3.22 and later. In 1.3.21 the installer­ will report success, but PDF and ODF support are not added.

If you are still experie­ncing problems check the Post Install Tweaks section below.

(updated 2011-10-27)

Note : Do not file bug reports for the installer if you have used any native DLLs.

Once installed, the following tweaks may be needed:

• wingdings.ttf: Most of the default bullet characters are from this font; if it is not installed on your system, Wine will substitute characters from a font that is installed on your system. If you want the bullets to look the same as they do in Windows, install this font.

The above are the most commonly-used tweaks. Individual AppDB entries may contain additional, app-specific information.

1. Test in a clean wineprefix, using plain Wine. 
   
2. Specify exactly which edition of Office 2007 you tested (Standard, Pro, etc.). This is crucial--bugs that affect one edition may not affect others.
3. Specify exactly what type of install you tested (Typical, Custom, Minimal, etc.)
4. 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.
   
5. 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.