Dan
2006-02-15 17:50:13 UTC
I have an app that a lot of people use. It pulls down HTML from the
Internet using the following InternetOpenURL call in VB:
lngOpen = InternetOpen(scUserAgent, INTERNET_OPEN_TYPE_PRECONFIG,
vbNullString, vbNullString, 0)
If lngOpen <> 0 Then
lngOpenURL = InternetOpenUrl(lngOpen, strURL, vbNullString, 0, _
INTERNET_FLAG_RELOAD Or INTERNET_FLAG_NO_COOKIES Or _
INTERNET_FLAG_NO_CACHE_WRITE, 0)
End If
The above works fine on my test machines as well as on about 99% of my users
but occasionally I have one report that when it is pulling information from
the Internet their system becomes unresponsive until the call is completed.
It is normal for the program itself to become unresponsive while waiting for
the reply but these users report that THEIR ENTIRE COMPUTER SYSTEMS become
unresponsive. They can't open or use any other program while my program is
waiting for the response. I've never been able to reproduct this or
determine why this might be happening. Does anyone have any ideas what
could be causing the systems to lock up?
I have had some people suggest that I switch to asynchronous calls but I
really don't want to go that route. What I really need to know is why on
some computers the entire system is locked up and not just the program. If
there is some fix I can give my users so that their computers don't hang
during a synchrous InternetOpenUrl call is made (some Registry setting I
expect) it would be a real big help. Thanks!
Internet using the following InternetOpenURL call in VB:
lngOpen = InternetOpen(scUserAgent, INTERNET_OPEN_TYPE_PRECONFIG,
vbNullString, vbNullString, 0)
If lngOpen <> 0 Then
lngOpenURL = InternetOpenUrl(lngOpen, strURL, vbNullString, 0, _
INTERNET_FLAG_RELOAD Or INTERNET_FLAG_NO_COOKIES Or _
INTERNET_FLAG_NO_CACHE_WRITE, 0)
End If
The above works fine on my test machines as well as on about 99% of my users
but occasionally I have one report that when it is pulling information from
the Internet their system becomes unresponsive until the call is completed.
It is normal for the program itself to become unresponsive while waiting for
the reply but these users report that THEIR ENTIRE COMPUTER SYSTEMS become
unresponsive. They can't open or use any other program while my program is
waiting for the response. I've never been able to reproduct this or
determine why this might be happening. Does anyone have any ideas what
could be causing the systems to lock up?
I have had some people suggest that I switch to asynchronous calls but I
really don't want to go that route. What I really need to know is why on
some computers the entire system is locked up and not just the program. If
there is some fix I can give my users so that their computers don't hang
during a synchrous InternetOpenUrl call is made (some Registry setting I
expect) it would be a real big help. Thanks!