Microsoft Office (installer only)

What works

First window describing a progress of extraction of the files.

What does not

Actual installation of application.

Workarounds

What was not tested

Everything possible was tested.

Hardware tested

Graphics:

• GPU:
• Driver:

Additional Comments

Testing platform: AMD Phenom II X2 550 BE [OC 3.6 GHz] Palit GeForce 7300GT [256MB; 512MHz core and memory] Realtek 7.1 sound 4 GB 800 MHz Kingston HyperX DDR2 RAM 23 XI 2009 - Terminal stated an error connected to the 64-bit architecture just before start of installation. I will investigate further and submit new data daily. All operations are made using PlayOnLinux application. Standard procedure: Terminal > playonlinux > Install > Install unsupported application > Existing Environment > Set & configure wine version > 1.1.33 > tweaking > installation 23 XI 2009 - Wine basic configuration, set to Windows 7: Running install menu fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:reg:GetNativeSystemInfo (0x32f9bc) using GetSystemInfo() err:process:create_process starting 64-bit process L"C:\\windows\\temp\\OWPe132.tmp\\setup.exe" not supported on this platform 24 XI 2009 - Wine basic configuration, set to Windows 2008: Running install menu fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:reg:GetNativeSystemInfo (0x32f9bc) using GetSystemInfo() err:process:create_process starting 64-bit process L"C:\\windows\\temp\\OWPe0.tmp\\setup.exe" not supported on this platform 24 XI 2009 - Wine basic configuration, set to Windows Vista: Running install menu fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:reg:GetNativeSystemInfo (0x32f9bc) using GetSystemInfo() err:process:create_process starting 64-bit process L"C:\\windows\\temp\\OWPe7.tmp\\setup.exe" not supported on this platform 24 XI 2009 - Wine basic configuration, set to Windows 2003: Running install menu fixme:reg:GetNativeSystemInfo (0x32f9bc) using GetSystemInfo() err:process:create_process starting 64-bit process L"C:\\windows\\temp\\OWPe1.tmp\\setup.exe" not supported on this platform 24 XI 2009 - Wine basic configuration, set to Windows XP: Running install menu fixme:reg:GetNativeSystemInfo (0x32f9bc) using GetSystemInfo() err:process:create_process starting 64-bit process L"C:\\windows\\temp\\OWPfe.tmp\\setup.exe" not supported on this platform 24 XI 2009 - I can't think of any other wine manipulations that can be can done to bypass these errors. Later I will test 32-bit beta. This version seems impossible to install because of lack of wine 64-bit support.

1. Test in a clean wineprefix, using plain Wine. 
   
2. Specify exactly which edition of Office 2010 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. ­

1. Test in a clean wineprefix, using plain Wine. 
2. Specify exactly which edition of Office 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.