http://bugs.winehq.org/show_bug.cgi?id=4939
------- Additional Comments From aran(a)discardmail.de 2006-26-03 14:02 -------
My dear Anton.
Your problem is one of the uglyst Bugs in Wine.
It is reproted more than a couple of time here in Bugzilla and for some reason
the developer of wine dont have the knoweledge or the profession to solve this
probleme or they dont want to fix this Internet bug in wine.
Maybe they have first to crack windows to look have the hole Internet thing in
windows work before they implement it in wine. I dont know why exactly this very
ugly Internt Bug is still not solved in wine.
Your problem is the Timeout of Internet Connection.
If you look your Error report you will find the following message
http://bugs.winehq.org/attachment.cgi?id=2142&action=view
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (12000):
STUB
If you go now to my 300 Bugnumbers before reported Bug with the number 4689 you
will find the same error message and the answer why does the application crash.
http://bugs.winehq.org/show_bug.cgi?id=4689#c6
"fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (800):
STUB"
http://bugs.winehq.org/show_bug.cgi?id=4689http://bugs.winehq.org/show_bug.cgi?id=4689#c1
I have voted for your Bug.
Please change the status of your Bug to Critical or Blocker so it can be handle
it by the developers.
I cant belive that this very ugly Internet Bug isnt allready solved by the
developers of wine.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4806
------- Additional Comments From Speeddymon(a)gmail.com 2006-26-03 13:59 -------
It has been discussed before that it is ok to forward certain bugs to wine-devel
once a patch can be easily implemented. As for the broken PE Headers being
bypassed by M$'s tests, I was not aware of that. In that case, yes you are
right, and the patch submitted would be a good fix. Of course, the better fix
would be to get in touch with the app developers and let them know that their
headers are broken due to a bad linker, and that they _should_ find a better
one, but that is really beyond the scope of support for wine, isn't it?
Eiother way, if we do that, and the developers do get a working one, great, if
not, it's their loss...
Tom
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3789
tony.lambregts(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Additional Comments From tony.lambregts(a)gmail.com 2006-26-03 13:27 -------
Closing duplicate.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3788
tony.lambregts(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Additional Comments From tony.lambregts(a)gmail.com 2006-26-03 13:27 -------
Closing duplicate.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3758
tony.lambregts(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Additional Comments From tony.lambregts(a)gmail.com 2006-26-03 13:26 -------
Closing duplicate.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3757
tony.lambregts(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Additional Comments From tony.lambregts(a)gmail.com 2006-26-03 13:25 -------
Closing duplicate.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3751
tony.lambregts(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Additional Comments From tony.lambregts(a)gmail.com 2006-26-03 13:23 -------
Closing Duplicate.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4939
------- Additional Comments From marcus(a)jet.franken.de 2006-26-03 13:21 -------
Host is NULL after
Host = HTTP_GetHeader(lpwhr,szHost);
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1654
------- Additional Comments From jmranger(a)hotmail.com 2006-26-03 12:59 -------
mohan1991 (comment #4):
If by "fail while selecting the directory to install", you mean that clicking on
"next" after selecting directory to install to, nothing happens, try to erase
your $HOME/.wine directory.
During my experiments with S&T 2005 on Debian Sarge (which supplies Wine
20050310), I upgraded to Wine 0.9.7 (from sarge-backports) and got that problem.
Erasing that folder fixed "next button does nothing" problem - only to hit
another one, see my other comment.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.