-
Hi all,
I recently made the switch in one of my programs from the Inet control to the winsock control. The differences so far have been negative. Has the following happened to you too?:
1) During run time, when I close my program, it takes almost 10 seconds to close and return to VB.
2) Sometimes VB freezes during this process, and then my whole computer freezes soon after that. Ctrl-Alt-Dlt doesn't work.
About #1. I thought this might be something having to do specifically with the program I was working with at the time. However, I made a little test program to be sure.
Here's what I did: I made a new project, and added the winsock control to form1 (and that's all I did). When I ran the program, it STILL caused the program to wait about 10-15 seconds before it returned to design/develop mode. What is going on here?!
I am using VB 6.0 btw.
One more thing: This started happening before I switched to winsock. When I try to close VB6, it closes all the child windows, and then sits there for about 5 seconds before it closes the whole program. What is the deal?
I am using a PII-450 with 128 RAM, so these problems really shouldn't occur.
If anyone can shed some light, I'd be eternally grateful. Thanks mucho,
Tyler C :)
-
Hi,
I've got the same problem and I don't really know why but I think it has to do with looking for a internet/network connection. I think it's the same problem like the computer freezes (sometimes) if you want to open a folder.
On my computer it happens ~every 10 times starting the program.
I think it CANNOT depend on your because I've got a PIII-500, 128MB.
Fox
------------------
[email protected]
...
Every program can be reduced to one instruction which doesn't work.
-
If you have an open connection with winsock when you close it it might take a while to close. Try using the Winsock1.Close command before you exit.
------------------
-FirePoweR-
[email protected]
