Microsoft Office

From Wine-Wiki

Jump to: navigation, search

Microsoft Office is likely the largest and most well-known software suite currently available. Commercial companies and many users may prefer the Codeweavers commercial version of Wine, which provides support and apparently lets you install as easily as on Windows. The difference between Codeweavers and Wine is noticed with Office, as Codeweavers lists Office working as one of their main goals whereas Wine has emulating windows as its goal.

This wiki is mainly collecting unofficial tips and suggestions from the forums and does not replace the application database.

Contents

Wine Application Database

  • Please consider submitting your test results for running this software under Wine.
Become a Maintainer
Please consider volunteering to be an additional Maintainer for this software.

Regularly Submitting results for installing and running on the latest version of Wine makes a big difference for others considering using Wine. By looking at how well the software runs others can be encouraged to try it themselves and together you can make progress in finding workarounds. By testing the software you will also notice when something breaks and when you make a bug report, the bugzilla team will often point it out to the person who broke it. If you are slightly more technically minded, you are able to regularly compile wine and test it before each fortnightly release then you will catch breakages before each wine release.

  • Who can be a Maintainer? - anyone. no programming experience required.
  • What is required of a Maintainer? - not much, but you do make a real difference.

A big advantage of being a maintainer is that as you quickly become familiar with installing and using wine with your software, you can have a direct hand in improving wine and your software. Many times you will find very handy tips posted by others and by posting a summary many benefit from your work. When you are asked a question you don't know, simply post in the wine-users forum and perhaps someone can help.

Just by being there, you make a difference. A maintainer quickly tests each monthly release of wine, and adds to the application database a rating of how good it runs.. gold/silver/bronze or garbage. Wine is constantly being improved, and occasionally something breaks. When you do spot a breakage, file a bug in bugzilla and if you want to try and fix it you can then post to the wine-devel mailing list for advice. However, if you have a little spare time (usually about 2 hours, in between doing other things) regression testing allows you to identify which patch caused the break. By filling out a bugzilla report, posting the name of the software, and the patch which broke it to the wine-devel mailing list, the developer who broke it can have a look at fixing it.

  • This often results in very quick fixes.


Current Status

July 08 Parts of MS Office will install. Outlook does not but does have some success with codeweavers. As one poster wrote in wine user jul 08 Moreover, buying Crossover is a great way to support wine development.

Microsoft Office 2007

S. Edwards [Jun 06]: Office 2007 only runs on XP and higher and it expects the dll [gdiplus.dll] to already be there. M. Hearn: So we find some free application that contains it and install that first wine archive

Microsoft Office 2003

Wine Forum Comments

  • Sept 07 EA Durbin [wine bug9023] Office will install after running the installation disk a 2nd time and choosing reinstall.

__[Sept 06]__ A user tried to test install office 2003 on wine 0.9.21, but noticed errors. He then queried about this as office 2003 works on codeweavers.

J White explained the apparent mystery had a quite simple reason: Codeweavers version of Wine has changes that Alexandre deems unacceptable for the "clean" WineHQ tree.

James checked the Codeweavers version of Wine: there are a lot of "Codeweaver "HACK HACK HACK" Alerts" everywhere in key dlls.

C. Wright made an interesting suggestion: [if] you are a developer, why don't you clean codeweaver's hacks and resubmit the code

Ed: Codeweavers is trying to get a few programs working for now while they and Wine continue to work on the problems, whereas Wine is trying to get it right for all programs running on Wine. With two different objectives sometimes there are differences. The end result is that Wine continues to improve.

[May 06] Finally I have got Excel to work on Mandriva. [...] with wine version 0.9.13 wine archive

[Dec 05] A user confirmed by means of screen shots in the developer wiki, office 2003 runs with Wine on BSD. After J. Hawkins made some changes [Jun 05], M.McCormack said: Thanks for the fixes. This makes Office 2003 work again for me.Wine Archive

Tips and Tricks

Feel free to add some here

Troubleshooting Office 2003

Consistant progress is being seen in this area. A. Stewart [May 2005]: the basic [MSI installer] functionality and structure is [now] there. It also should allow you to actually start installing Office. With the current CVS tip Office2003 fails to install due to actions relating to MSXML failing but that is where our effort is now focused Wine Archives.

Further Reading

Office 2000

Microsoft Office components can be installed individually. Word, Excell have been known to work well. Microsoft Access with Codeweavers is rated [May 05] as Silver.

Office 2000 Application Database

Current Status Office 2000

  • A user reported [Nov 05] an issue with saving files: Basically it will only accept one character as a file name. Even when you type the complete name, the name is reduced to one character. wine archive
  • Not working well with Wine20050423 (May 2005)
  • A user [Aug 2005] attempted to install MS Office 2000 from a CD using wine but was not successful, 'as the Office installer apparently tries to install Internet Explorer version 4 and fails'. Wine Archive
    • Before installing Office it may be best to install Internet Explorer 4 or later with versions of wine since March 2004.
  • Further Details currently Unknown

Troubleshooting

  • feel free to add suggestions here 
warn:module:load_dll Failed to load module L"D:\\.wine\\drive_c\\Program
Files\\Microsoft Office\\Office\\MSACCESS.EXE"; status=c0000020 wine:
could not load L"D:\\.wine\\drive_c\\Program Files\\Microsoft
Office\\Office\\MSACCESS.EXE": Bad EXE format for

Toby: I've found a workaround: installing an English version of Office. The Italian version I was trying to install always triggers the "Bad EXE format for" error, no matter what I do. Wine archive

Office 97

Current Status Office 97

  • Jul 08 wine user, Dimesio: I dug out my Office 97 cd and just tested it in 1.1.1; it installed perfectly with no overrides or registry hacks whatsoever--I didn't even change the Windows version. I did a custom install of only Word, Excel, Powerpoint--that works fine. As for Access,[...] unfortunately, I don't have an answer [...]The help files for Word 97 are .hlp, and they do work, sort of. [..]after you've selected the help topic from the index, click the lower Okay button to get it to display [if it does not,] As far as getting Word to find the help files via the open file dialog, type c:\Program Files in the filename box and hit enter. You should be able to navigate from there by pointing and clicking. Another wrote that even Access worked after installing dcom98 with winetricks. i started up Word, PowerPoint, Excel, Binder, Access, and Photo Editor. They all started ok and seemed to work, although I didn't really use them--even Access. My only disappointment was Outlook, which i really wanted to use in order to remain compatible with my older systems. Outlook started up and flashed its startup screen but then just disappeared. As a note of interest a while back I tried the trial copy of Crossover and Outlook ran fine there.
  • [May 06] D. Kegel: I installed Office '97 on the latest wine from git (so, it's a preview of 0.9.13). The installation quit right at the end -- http://bugs.winehq.org/show_bug.cgi?id=3689 -- but it left Word and Excel in a usable state. msaccess fails [with] the the "no license" problem [...] It was looking for a particular set of registry keys presumably created during the installation of Access. Ihaven't had time to go suck the registry keys off a Windows system and try plugging them in...wine archive
  • [May 06] A user noted: when I try to save a document, all I get is the first letter of the file name. E. Flessa: This issue seems to have been resolved with wine 0.9.16.
  • [Nov 05] Progress is being made with the normal complete Office install. H Leidekker sent a patch http://winehq.com/pipermail/wine-patches/2005-October/021484.html and has another yet to be applied. D. Kegel tried it and reported: Yep, applying your patch to a clean wine tree from cvs builds a wine that seems to no longer need an override for odbccp32 when installing Office 97. (The install still fails later with "Accwiz.dll was unable to register itself in the system registry", but you expected that.) wine archive Fix: Select Custom Install; Select Access; Change Options; Uncheck Wizards.
  • [Oct 05] A user posted that: The MS Office 95/97 setup program fails when using the built-in odbccp32.dll. A native version of this dll is on the installation media. users should use winecfg to change "odbccp32" to "native, builtin" Wine Archive
  • [Sept 05]There are two issues with Winehq that prevent Office 97 from installing

and I need help with issue #2 if anyone has ideas.

    1. Wine needs to have the "PROCESSOR_ARCHITECTURE"="x86" string in the Key in HKLM\\System\\CurrentControlSet\\Control\\Session Manager\\Environment
      For Winehq we need to properly detect and report the CPU due to Winehq default mode being Win2k. I'll try to to submit a patch that does this as I think I know where it needs to be implemented.
    2. Wine is not properly handling some of the default values in key HKLM\\System\\CurrentControlSet\\Control\\Session Manager\\Environment
      CrossOver uses "%SystemRoot% where the default Wine system.reg had the values hard coded. My wifes Win2k box has these values set with "%SystemRoot% also. Is there a reason that Winehq is setup this way? Should they strings in the wine.inf just be changed for those values? With the default Winehq registry you get a message box error that says something along the lines of "This setup program is not supported under your version of Windows"
    • D. Riekenburg: IMHO, "wineprefixcreate" should be able to set "SystemDrive" and "SystemRoot" (maybe "profiles" and "temp" also). The Profile-Directory changed since w2k (localiced version of: "%SystemDrive%\Documents and Settings") Starting with W2k, the "TEMP" - Directory is relative to "USERPROFILE". (localiced version of: "%USERPROFILE%\Local Settings\Temp"). [The discussion ended there]

Tips and tricks

A user posted to the forum [July 05] his list of dll overrides: 

[DllOverrides]
"commdlg"      = "builtin, native"
"comdlg32"     = "builtin, native"
"ver"          = "builtin, native"
"version"      = "builtin, native"
"shell"        = "builtin, native"
"shell32"      = "builtin, native"
"shfolder"     = "builtin, native"
"shlwapi"      = "builtin, native"
"shdocvw"      = "builtin, native"
"lzexpand"     = "builtin, native"
"lz32"         = "builtin, native"
"comctl32"     = "builtin, native"
"commctrl"     = "builtin, native"
"advapi32"     = "builtin, native"
"crtdll"       = "builtin, native"
"mpr"          = "builtin, native"
"winspool.drv" = "builtin, native"
"ddraw"        = "builtin, native"
"dinput"       = "builtin, native"
"dsound"       = "builtin, native"
"opengl32"     = "builtin, native"
"msvcrt"       = "native, builtin"
"rpcrt4"       = "native, builtin"
"msvideo"      = "builtin, native"
"msvfw32"      = "builtin, native"
"mcicda.drv"   = "builtin, native"
"mciseq.drv"   = "builtin, native"
"mciwave.drv"  = "builtin, native"
"mciavi.drv"   = "native, builtin"
"mcianim.drv"  = "native, builtin"
"msacm.drv"    = "builtin, native"
"msacm"        = "builtin, native"
"msacm32"      = "builtin, native"
"midimap.drv"  = "builtin, native"
"ole2disp"      = "native, builtin"
; default for all other dlls
"*" = "native, builtin"

For Wine versions later than and including Wine20050628 the config file has been removed. You could either use winecfg or this could be made into a .reg file and imported into the registry. These dll overrides should be defined as application specific.

Further Reading

Troubleshooting

  • Feel free to add suggestions here, but remember to add to the application database. If you can, please become a maintainer for this software.

Links

Wine Links

(Official) Wine Links

(Unofficial) Wine-Wiki Links


External Links

Retrieved from "http://wiki.jswindle.com/index.php/Microsoft_Office"
Personal tools