MS Office Pro Plus 2010 - Error while installing.

[JavaWong37]

Heyy, I'm new here but not new with Wine, not an expert I'm intermediate.

This is the great dilemma I'm facing, as the title says I'm encountering an error message during installation on my Arch Linux.
I'm fine using the alternatives but work demands MS Office so here we are.

This is what I did:
1. Performed a system upgrade. (I already have winetricks and samba)
2. Setup clean 32 bit wineprefix.
3. Installed all the necessary and maybe even some unnecessary dependencies and libraries.

Code: Select all

WINEPREFIX=~/name_of_prefix winetricks corefonts dotnet35 msxml3 msxml6 mdac28 gdiplus

Code: Select all

sudo pacman -S lib32-libldap lib32-gnutls lib32-libxml2 lib32-ncurses lib32-libgpg-error lib32-sqlite lib32-libpulse lib32-openal lib32-mesa lib32-mpg123 lib32-ncurses lib32-libxslt lib32-libgcrypt

4. Then I run the installation through the command....

Code: Select all

WINEPREFIX=~/name_of_prefix wine /path/to/msoffice/folder/setup.exe

It returns the error...

Code: Select all

0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
00c8:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Bad EXE format for Z:\home\me\Downloads\office 2010\setup.exe.

5. So I just run it through wine without specifying the wineprefix. I have another wineprefix but I changed its settings to be identical to the one I want to install Office 2010, just in case.

Code: Select all

wine /path/to/msoffice/folder/setup.exe

The setup then runs but I get...

Please, what could be the problem? All help very much appreciated.

[dimesio]

You're probably running into https://bugs.winehq.org/show_bug.cgi?id=45208. It's unlikely to ever be fixed, but there are workarounds in the bug report.