https://bugs.winehq.org/show_bug.cgi?id=5163
Mark themh@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |themh@gmx.de
--- Comment #104 from Mark themh@gmx.de --- @Anastasius Focht: This analysis from 2008 was a blast to read. Very educational.
Meanwhile, since the fix to this bug is in staging, I managed to install Office 2002 almost completely working with this method. I thought I might share it for others who stumble upon this, even though Office 2002 today has probably rather niche usecases.
1. I used a 32bit wineprefix with Wine 6.11-staging, without installing mono or gecko. I used PlayOnLinux for easy installation, but you could probably compile it yourself, too.
2. Install Access, Word, Excel and Powerpoint with the installer. De-select all autocorrection options in the installer. They won't install properly (probably another bug) and if you don't de-select them, Office keeps asking to insert the installation medium at every start.
3. I then copied the prefix in my default wine environment, which is currently 5.0-stable, ran winecfg and changed the mode to Windows XP. It probably runs in Windows 7 mode, to, but since it's Office XP you might as well put it to the proper OS version.
4. The installation is now complete. Finally, I manually created 4 launchers for the progams via alacarte (you can google that if you're unfamiliar with menu editing)
The launchers have to look similar to that: env WINEPREFIX="/home/username/.wine-mso" wine-stable /home/username/.wine-mso/drive_c/Program\ Files/Microsoft\ Office/Office10/WINWORD.EXE