Internet Explorer
From Wine-Wiki
Microsoft's Internet Explorer is often used by many in the Windows world to access web pages. While parts of Explorer are used by a number of third party programs and make it necessary to install, for those new to Linux, please be aware that there are many native Linux options for surfing the web (such as Firefox and many others - too numerous to briefly mention here) that install by default with your distribution. Webmasters need Internet Explorer to test their web designs. Install internet explorer using winetricks. However, do not install it unless you absolutely need it, as wine has it's own implementation of explorer which often is more than adequate.
Contents |
[edit] Wine Application Database
This Software is listed in the Official Wine Application Database
Winehq Main AppDB entry Versions IE1 to IE8
- Please consider submitting your test results for running this software under Wine.
| |
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.
Official Information Unofficial Information 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.
Further Help to Wine |
[edit] Comments
S. Dossinger [Jun 06]: Internet Explorer on wine is not guaranted to render things like Internet Explorer on Windows. You can reduce the differences by using as much native dlls as possible(mshtml, shdocvw, dcom, ...), but there might still be differences. If you run IE with the builtin dlls you have pretty much a Mozilla Gecko based Browser with the gui of IE. Just run the Acid 2 test in msie with builtin mshtml and compare the output to the rendering on Windows and the rendering in Firefox. What I want to say is that one can't really use wine to see if pages render correctly in IE. However, I still think that IE should be installable and work with its native dlls(including mshtml and dcom), because it is helpful to check if a bug in another application is caused by shdocvw, mhtml and friends. wine archive
R. Shearman: IE running in Wine still allows me to view sites that don't display properly in Firefox, so it definitely has a use. wine archive
There are scripts to install Internet Explorer and Wine now has a web browser which is making interesting progress. However you can assist wine by testing the install of Internet Explorer and then reporting the bugs. As many programs use parts of Explorer, fixing these bugs can improve Wine for many people. When reporting, be sure to check that it is a new bug and not a duplication.
D. Kegel wrote: Wine doesn't directly support running IE6. See http://www.tatanka.com.br/ies4linux/ or http://codeweavers.com for ways to run ie6 on Linux using Wine.
[edit] Current Status
The status of Internet Explorer changes quite regularly. It would be best to check the application database first.
- L. Rayhen [Aug 07 wine user]: All known regressions related to IE has been fixed in 0.9.43
- J. Ernst[Jun 06]: The problem is to find a good combination of native dlls to run IE (stock WineCVS let's you install it without problems now). You can see the current state of the How-To here: http://appdb.winehq.org/appview.php?versionId=469
- A user reported [Mar 2006 ]:I tried to install IE6SP1 under wine 0.9.9,[...]and it failed[...]. J. Hawkins reported that he would look into it.
- [Jan 06] . A user reported he had have Internet Explorer 5, 5.5 and 6 installed from IEs4Linux (http://www.tatanka.com.br/ies4linux/en/instructions/) which uses the Internet Explorers from the Browser Archive (http://browsers.evolt.org/download.php?/ie/32bit/6.0/ie60.exe). After the upgrade to Wine 0.9.4 IE6 crashes. IE5 and 5.5 do work.
- D. Kegel: You've probably run into bug http://bugs.winehq.org/show_bug.cgi?id=4128 [...] a fix has already been checked into cvs.
- [Dec 05] A recent patch seemed to hang installation of Internet Explorer. If I assign native ole32.dll to ie6wzd.exe or use the builtin ole32 before this submit then it's running. The freeze happens when completing the component selection dialog.
- [Nov 05] The first thing you have to do is use a native advpack.dll. The second part of the workaround is to register a native version of inseng.dll like so (a copy of that dll is apparently in some temp dir in the fake windows):
- regsvr32 inseng.dll
- Then ie6setup.exe should work. wine boot fails, but it should still run. [wine archive]
- [Oct 05] according to a "solution" in bugreport 3453 (http://bugs.winehq.org/show_bug.cgi?id=3453) there is not need to really
install IE60 to install MDAC. Inserting the registrykey just does fine for me. [...]Setting advpack.dll to native is still necessary to install IE60, though. But [...] it is NOT necessary to really have it in the System32 directory, since IE puts it there itself.) Wine Archive
- [Sept 05] The application database has an active maintainer with detailed information for differing wine versions.
- A user [Jun 05]: I've noticed some problems installing Internet Explorer 6 SP1 with any version of WINE newer than 20050310, and that includes CVS as of yesterday. Apparently, I'm not the only one; many other are also having issues with 20050419 and 20050524. With my current setup, I get this error repeatedly at 81% during installation:
- fixme:thunk:__regs_CommonUnimpStub generic stub: ?
- M. Hearn: IE installer unzips a native advapi32.dll into the same directory it runs from, so it overrides builtin advapi. Our GDI32 then calls a function which is exported by this native advapi but not implemented as part of a while conditional, so we enter an infinite loop. I debugged this a couple of years ago I guess, the solution now as then is to set "advapi32=b" as a DLL override. I'm not sure how else to fix this, except by making advapi32 one of the magic DLLs that will never be loaded as native. I think that solution was dropped though.
- Dosinger: to force advapi32 to builtin [using the config file or winecfg]
- [DllOverrides]
- "advapi32" = "builtin"
- [DllOverrides]
- The user did not report whether a solution was found Wine Archive
- Anon: I've installed IE6 (and other Win32 stuff, provided by WineTools) using some older Wine and after this i've installed CVS version, and everything works very well. Wine Archive
- R. May: The dll overrides need to actually be:
- [DLLOverrides]
- "*advapi32" = "builtin"
- "*advpack" = "native"
- [DLLOverrides]
- This gets it installed for me with only an error message about windows.hlp and atl.dll, however, I still can't run it
- further details unkown
[edit] Installation Scripts
[edit] ies4linux
quite a number [July 07] have been using ies4linux. However this is not recommended by the wine developers
J. Hawkins july 07 wine devel: If programs as ies4linux [are] promoted, then there is no incentive to fix entirely valid bugs in Wine affecting ie6, bugs that probably also affect other applications as well. Promoting ies4linux helps no one in the long run. I don't even mind if you mention ies4linux as long as you make it very clear that it is only a temporary workaround, and that a bug report should be filed. If you'll take a look at the backtrace Richard posted, Wine is crashing in mshtml. This is a perfect candidate for a bug report. Searching through bugzilla with 'ie6' as the title, there are 11 bug reports, none of which is similar to this bug. If you're still reading this Richard, the developers of the Wine project would really appreciate if you could file a bug at [1] for this problem.
One radical Developer has been known to close any bug with the word ies4linux included. A. Julliard reopend a bug report in August 07 which had been closed by this developer.
[edit] With Sidenet
First you need to goto Sidenet's Website and download the newest binary version of the setup program. This HOWTO was writen using version 1.7.4 of Sidenet's Configuration program.
Before running the setup program, we need to remove .wine directory because this program works better with a clean copy of Wine.
Removing .wine
$ rm -rf .wine
Next we need to untar Sindnet's program to configure Wine;
Untarring wine-config-sidenet-1.7.4.tgz
$ cd <To where to downloaded it> $ tar -xzvf wine-config-sidenet-< Version Number >.tgz $ cd wine-config-sidenet
Now, we start the program to install Internet Explorer;
Starting the Setup program
$ ./setup
Make sure to pick option number 1, because it's the easiest.
Once done, you have your self Internet Explorer ready to use.
[edit] With the Winetools
After installing and configuring your virtual Windows system with the Winetools, like described in the "Wine Installation HOWTO" section "Sarge", you should have Internet Explorer installed.
So launch it like this :
Launching Internet Explorer
$ ~/bin/ie6
Then the connection wizard will pop-up. Click on "Cancel" and check the hitbox so the connection wizard won't pop-up the next time you'll launch IE6.
The screenshot shows IE 6 displaying without any button images, but this is fixed in release 20050111.
Update: This doesn't work anymore. Microsoft do not allow the use of the Windows Update system from inside Wine anymore.
[edit] With IE4Linux
Just run the script. It installs a script named ie6 in ~/bin/.
[edit] Troubleshooting
A user noticed [Apr 06]: sometime in the last two weeks my Internet Explorer stopped working. My son said one day a message popped up and said Updates Available from Ubuntu so he did the update and he thought Wine was one of them. Anyway, I have to have IE for a IE only site.
J. Ernst: I guess you used some automatic technique to make IE work (winetools, ies4linux). If that's the case these versions won't work anymore with current Wine.
- Use the manual install method of the AppDB (http://appdb.winehq.org/appview.php?versionId=469) or use
- ies4linux 2.0 beta (http://www.tatanka.com.br/ies4linux/blog/2006/04/25/fresh-news-ies4linux-20-beta1-and-many-improvements/) which works with current Wine.
Segin: IEs4Linux uses seperate WINEPREFIX directories for each install.
[edit] Installing IE7
Hans has obviously been busy as he posted this screen shot in Jan 09 [wine devel]: http://permalink.gmane.org/gmane.comp.emulators.wine.devel/66315 and announced IE7 can run in Wine. He wrote: Well, sort of. I found bugs in shell32, rpcrt4, comctl32 and wininet that I had to implement, stub and override my way past before it would render a page, but finally, here's the obligatory screenshot. He has been working at sending the patches for his work and perhaps soon this will eventually work for the average wine user.
H Leidekker [Mar 06]: I know this affects the IE7 and MSI 3.1 installer, but probably more.[...] I've seen installers from Microsoft call QueryDosDevice on the whole alphabet and search any returned object name for the substrings "harddisk" and "ramdisk". On Wine they normally won't find any and quit with thefollowing error:
"Unable to find a volume for file extraction"
QueryDosDevice on Wine returns the filename pointed to by the drive link beneath the dosdevices directory. In a default Wine installation this is ../drive_c. So a simple fix for this problem is to use the a different name for that directory, for example the name used for the first harddisk in the NT object namespace: harddiskvolume1.
Anon [April 08 wiki post] generally anything that uses the update.exe mechanism, including Service Packs and Windows Media Player [call QueryDosDevice on the whole alphabet and search any returned object name for the substrings "harddisk" and "ramdisk"]. One thing you can do is to do this:
cd ~/.wine/dosdevices ln -s /tmp HardDisk0 ln -s HardDisk0 t:
This way it'll put all the temporary files under /tmp. I have successfully slipstreamed Windows XP SP3 into a directory containing RTM CD contents using the SP3 standalone installer this way (as of Wine 0.9.60).
- wine ~/pulldown/WindowsXP-KB936929-SP3-x86-ENU.exe -s:Z:\\mnt\\scratch\\xpcd
A. Julliard: QueryDosDevice needs to be fixed to return real device names instead of just reading the symlink. We can't require people to name their directories harddisk something. I'm working on it but it needs a bit more device infrastructure first. wine archive
[edit] Installing IE6
April 08 A bug report mentioned set winecfg to win2000 to install IE.
[Jun 06] Maarten Lankhorst schrieb: Windows seems to set internet explorer only during a new installation or upgrade of internet explorer, so I put it in wine.inf, which seemed appropriate. Changelog: Set version strings for Internet Explorer so programs dependent on it can install.
S. Paschukat: This breaks installation of real IE. Setting version to IE 5.5 would give the users a chance to install at least version 6. wine archive
[Jun 06] T.Lambreghts: [after discussing the download location error] I used the file from:
[Jun 06]
ie6setup fails with "The download location information is damaged"
E. Pouch: I have seen this problem recently and I can confirm that it also happens when trying to install IE6 on Windows 98. Here is what happens based on Ethereal traces and a good deal of patience. When you install IE6 it downloads the following URL:
The first time a computer (i.e. an IP address as visible from the Internet) tries to get that URL, it gets a 216 byte HTML file. Here it is in full:
- --- cut here ---
- <HTML><HEAD><META HTTP-EQUIV="Refresh" CONTENT="0.1;
- URL=/windows/ie/ie6sp1/download/rtw/x86/ie6sites.dat"> <META
- HTTP-EQUIV="Pragma" CONTENT="no cache"> <META HTTP-EQUIV="Expires"
- CONTENT="-1"> </HEAD></HTML>
- --- cut here ---
This is not what the IE6 installer expects and whenever it gets that it prints the error message mentionned above, even when running on Windows. However, if you redownload that URL within 20 minutes after that first try, you should get a 2788 bytes file that lists the available download servers. This is what the IE6 installer wants and then it will work fine (at least in CrossOver, there may be other issues in Wine). In some cases I only got the expected file on the third try. This is easy to check by running w get a couple of times. The 20 minutes have been determined through (automated) trial and error and are very annoying when trying to reproduce the problem. My guess would be that this is a configuration bug in Microsoft's server and that they don't care much since nobody installs IE6 from scratch (it comes preinstalled on Windows XP and greater).
So it's really not Wine's fault and there is not much it can do to work around that bug. wine archive
J. Hawkins: IE6 setup checks if the drive is remote, and will not install if it is, complaining with the completely non-related error that "The download location information is damaged." If you're not sure whether you're on a remote drive or not, and the IE6 setup is still not working, please post back and attach a +volume trace. I was frustrated that the setup was not working on my work machine, while it was on my home machine. Reading through [...] GetDriveTypeW was returning 4 for my work machine, which is DRIVE_REMOTE, and then it would fail with the message box. Hacking GetDriveTypeW to always return DRIVE_FIXED let me install onto my remote drive. Alternatively, you can go into winecfg->Drives->Show Advanced and change the Type from Autodetect to "Local hard disk". Peter offered a patch that set C as hard drive. wine archive
[May 06] J. Hawkins: To install IE6 with no native dlls, you must wine archive:
- upgrade to CVS
- copy a native inseng.dll to drive_c/windows/system32
[Nov 05]
/usr/lib/wine/dbghelp.dll.so) err:module:import_dll Loading library dbghelp.dll (which is needed by L"C:\\windows\\system32\\winedbg.exe") failed (error c000007a).
J. Hawkins: Did you install wine via rpm, source, deb? This sounds like wine is expecting glibc 2.3.4 but isn't finding it for whatever reason. [He then recommended installing wine from source] wine archive
[Nov 05] IE60 installs with a "fresh and clean" wine (CVS 11/11) and just "ADVPACK.DLL" set to "native". I've tested it with WINE-Version Win98, 2000 and XP.
[Nov 05] IE60 installs with a "fresh and clean" wine (CVS 11/11) and just "ADVPACK.DLL" set to "native". I've tested it with WINE-Version Win98, 2000 and XP. For Win98 I've done a minimalistic installation like Sidenet does, though. [...] I just can't Regsvr32 a native MSXML3.DLL with "standard" WINE. With sidenet it's working flawless.
[Nov 05] J. Hawkins tried to install IE6 with some success wine archive:
- used a native advpack.dll (wine's advpack isn't complete enough yet).
- The install bails out with the following errors on the command line:
err:ole:CoGetClassObject class {6e449686-c509-11cf-aafa-00aa00b6015c} not registered
err:ole:create_server class {6e449686-c509-11cf-aafa-00aa00b6015c} not registered
fixme:ole:CoCreateInstance no classfactory created for CLSID {6e449686-c509-11cf-aafa-00aa00b6015c}, hres is 0x80040150
- the UID belongs to inseng.dll, which is extracted to the temporary install directory. On windows, inseng.dll is already
registered by the time you run the installer, but is not registered on wine. A workaround which temporarily solves the problem is Running
- wine regsvr32 inseng.dll
wine: Call from 0x1013ac7 to unimplemented function advpack.dll.IsNTAdmin, aborting wine: Unhandled exception (thread 000b), starting debugger...
S. Leichter: The code path in use inside ie6setup changes around 9th July. The only way to get ie6 installed with currect wine for me is to set advpack dll to native. IsNTAdmin is not the last problem to solve. The next are TranslateInfString and ExecutCab i think Wine Archive
Installing IE6 from a cdrom
A user asked how to install ie6. S. Leicheter [july 05] Installing ie6 is no big magic. I have an installer from a cd, _not_ an installer that load most of the stuff from the ms web server. Wine Archive
- import the attached file into the registry using regedit.
- replace the link c:\windows\system\regsvr32.exe with a copy of link target owned by the user running the setup
- run the setup
Hope this will work for you too.
filename="IE6inst.reg"
REGEDIT4 [HKEY_CURRENT_USER\Software\Wine\DllOverrides] 1120292966 "advapi32"="builtin" "advpack"="native" //for wine 200507xx and newer "comctl32"="builtin"
err:rundll32:main Unable to find the entry point L"DelNodeRunDLL32C:\\\\Program" in L"adpack.dll"
M. Davison spotted that The INF parser had a bug [July 05]: This is responsible for the 15 0r so lines looking like:
err:rundll32:main Unable to find the entry point L"DelNodeRunDLL32C:\\\\Program" in L"adpack.dll"
In the console output of setup Rundll32 is fail to find an entry point DelNodeRunDll32C:\\Program, because the space has been erroneously stripped. The Line in the INF file looks like: rundll32.exe advpack.dll,DelNodeRunDLL32 "%24%\%LProgramF%\% UninstallData%\IE UserData NT"
A. Julliard: It looks like the bug is with quotes in the middle of tokens then. [And Posted a Patch which apparently fixed the problem] Wine Archive
wine: cannot open builtin library for L"C:\\windows\\system32\\regsvr32.exe": /home/[nobody]/wine/programs/regsvr32.exe.so: invalid ELF header
V. Margolen: The only time I have seen this message in relation to regsvr32.exe is only when Wine's builtin regsvr32.exe.so was overwritten with native PE executable. That could happen only of you have write access to the the place where you installed wine, or if you running it from the source tree. [It] Looks like a case of overwritten regsvr32.exe with native copy (like what IE6 installation will do...wine archive
[edit] Links

