http://bugs.winehq.org/show_bug.cgi?id=13590
--- Comment #10 from Danila Sentiabov dsent@mail.ru 2008-06-05 15:49:06 --- I'm applying the same file: Office2003SP3-KB923618-FullFile-ENU.exe sha1 81e8e5b08aa073287ddf5d46b3484e3626659696
I just started it all from scratch to reproduce exactly what's working and what's not. Working scheme: 1) Install 0.9.52. Note, that I don't have any version of wine installed in my system. I have all compiled versions from 0.9.12 to 1.0~rc3 in separate folders and a bunch of home-made bash scripts to manage different prefixes and run different programs with different wine versions. But there is no way that files from different wine versions may interfere and I always install each program to it's very own prefix, so I think that installing/reinstalling appropriate wine versions should result in exactly the same behaviour, apart from taking more time. 2) export WINEPREFIX=~/brand_new_wine-prefix; wineprefixcreate; cd /mount/office-cd wine setup.exe 3) Go through Office 2003 installation process. Very annoying fact: in advanced custom install there is no possibility to select "Install entire feature" - one have to manually select each subfeature. Less annoying issues: required space isn't shown and each time you press on "Next", installation window loses focus. 4) cd /tmp/folder-where-our-service-path-is wine Office2003SP3-KB923618-FullFile-ENU.exe 5) So, that's it. Now update wine to 1.0~rc3 and it's working. I also run winetricks as follows: winetricks allfonts, gecko, gdiplus, msxml3, riched20, riched30 But it seems that it's not required (or make any defference at all) during installation.