Possible regressions in IE6 SP1 install
Hello all, 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: ? It keeps looping like that on and on forever, and the install never finishes, but the UI stays responsive. I've had many issues installing IE in the past, but nothing like this. Can anyone give me any leads as to what might cause this? If it might help, I've applied Oliver Stieber's latest DX9 patch, and have tried both Wine Tools and Sidenet. Thanks very much, James Liggett
James Liggett wrote:
Hello all, 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: ?
It keeps looping like that on and on forever, and the install never finishes, but the UI stays responsive. I've had many issues installing IE in the past, but nothing like this. Can anyone give me any leads as to what might cause this? If it might help, I've applied Oliver Stieber's latest DX9 patch, and have tried both Wine Tools and Sidenet.
Don't use native (core) Win98 DLLs. Rob
On Fri, 17 Jun 2005 22:33:19 -0500, Rob Shearman wrote:
Don't use native (core) Win98 DLLs.
In this case it can't be avoided, 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. thanks -mike
On Saturday 18 June 2005 03:09, James Liggett wrote:
Hello all, 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: ? Try setting advapi32 to builtin only, this has helped me. ie6 setup seems to load some native dlls if they are set to builitn,native, so it's necessary to force advapi32 to builtin
[DllOverrides] "advapi32" = "builtin" Hope that helps, Stefan
After pulling the CVS changes yesterday, My Dreamweaver MX no longer starts (hangs on splash). I'm pretty sure I ran it against CVS on Thursday, so this must be a recent change. I turned on a couple of debug channels and it seems to be looping on a NtWaitForMultipleObjects whose signal never fires. Anyone else seeing this, or just me?
Evil wrote:
After pulling the CVS changes yesterday, My Dreamweaver MX no longer starts (hangs on splash). I'm pretty sure I ran it against CVS on Thursday, so this must be a recent change.
I turned on a couple of debug channels and it seems to be looping on a NtWaitForMultipleObjects whose signal never fires.
Anyone else seeing this, or just me?
There were a number of major changes made on Thursday to the configuration options. I would make sure all of your configuration settings are moved over to the new registry location first. Then if that doesn't work, you can start a binary search for regression using CVS. -- Rob Shearman
Robert Shearman wrote:
Evil wrote:
After pulling the CVS changes yesterday, My Dreamweaver MX no longer starts (hangs on splash). I'm pretty sure I ran it against CVS on Thursday, so this must be a recent change.
I turned on a couple of debug channels and it seems to be looping on a NtWaitForMultipleObjects whose signal never fires.
Anyone else seeing this, or just me?
There were a number of major changes made on Thursday to the configuration options. I would make sure all of your configuration settings are moved over to the new registry location first. Then if that doesn't work, you can start a binary search for regression using CVS.
I deleted the .wine directory and re-installed DreamWeaver (successfully), and it's hanging in the same place (splash, NtWaitForMultipleObjects)... so it probably is a regression issue. I'll attempt to figure it out mid-week, if someone doesn't beat me to it (crossing fingers <g>). -J
I finally got around to looking further into this today. It turns out the culprit wasn't actually a regression at all. When the settings were moved out of the config file to the registry, I didn't realize that I lost all the DLL override settings. Failure to use the native msvcrt.dll was what stopped it on the splash screen. After adding the override back via winecfg (and overriding comctl32 + commctl, to fix dialog problems), it appears to work as well as ever. Cheers, J Evil wrote:
Robert Shearman wrote:
Evil wrote:
After pulling the CVS changes yesterday, My Dreamweaver MX no longer starts (hangs on splash). I'm pretty sure I ran it against CVS on Thursday, so this must be a recent change.
I turned on a couple of debug channels and it seems to be looping on a NtWaitForMultipleObjects whose signal never fires.
Anyone else seeing this, or just me?
There were a number of major changes made on Thursday to the configuration options. I would make sure all of your configuration settings are moved over to the new registry location first. Then if that doesn't work, you can start a binary search for regression using CVS.
I deleted the .wine directory and re-installed DreamWeaver (successfully), and it's hanging in the same place (splash, NtWaitForMultipleObjects)... so it probably is a regression issue. I'll attempt to figure it out mid-week, if someone doesn't beat me to it (crossing fingers <g>).
-J
Hi Stefan, Thanks for the reply. I have tried this already, and it doesn't seem to work. I tried setting all dlls for ie6setup.exe to builtin, and while I got more fixme's than normal, the problem still didn't go away. Here's the config file I'm using: WINE REGISTRY Version 2 ;; All keys relative to \\Machine\\Software\\Wine\\Wine\\Config ;; If you think it is necessary to show others your complete config for a ;; bug report, filter out empty lines and comments with ;; grep -v "^;" ~/.wine/config | grep '.' [wine] "ShowDirSymlinks" = "1" "ShowDotFiles" = "1" [Version] ; Windows version to imitate (win95,win98,winme,nt351,nt40,win2k,winxp,win2k3,win20,win30,win31) "Windows" = "win98" ; DOS version to imitate "DOS" = "6.22" ;; For running Internet Explorer 6, Service Pack 1 ;[AppDefaults\\iexplore.exe\\Version] ;"Windows" = "win98" [DllOverrides] "*" = "builtin" I've modified the config file that's given in the how-to at franksconrner.org to use all builtin dlls, but I still see the problem. By the way, what is a thunk, anyway? I've been programming in Win32 for years and have never really come across them. Thanks a lot, James On Sun, 2005-06-19 at 14:32 +0000, Stefan Dösinger wrote:
On Saturday 18 June 2005 03:09, James Liggett wrote:
Hello all, 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: ? Try setting advapi32 to builtin only, this has helped me. ie6 setup seems to load some native dlls if they are set to builitn,native, so it's necessary to force advapi32 to builtin
[DllOverrides] "advapi32" = "builtin"
Hope that helps, Stefan
On Sunday 19 June 2005 18:56, James Liggett wrote:
Hi Stefan, Thanks for the reply. I have tried this already, and it doesn't seem to work. I tried setting all dlls for ie6setup.exe to builtin, and while I got more fixme's than normal, the problem still didn't go away. Here's the config file I'm using: Strange... No further idea :-(
Stefan
participants (7)
-
Evil -
Evil -
James Liggett -
Mike Hearn -
Rob Shearman -
Robert Shearman
-
Stefan Dösinger