Results 1 to 2 of 2

Thread: Winsock, Not Reponsive

  1. #1

    Thread Starter
    Fanatic Member
    Join Date
    Jun 2001
    Location
    Oregon
    Posts
    643

    Angry Winsock, Not Reponsive

    i have 2 programs, a client and a server..

    Client program needs to connect to the server and update files, then disconnect and start the main portion of the program with the newly updated files.

    Server just sits there and listen's, once connected it will transfer the info, disconnect, then start listening again.


    First problem i ran into was the error address in use. So i set local port to 0 clientside, since thats where the error was at. Then i started getting the same error on the server side, so i made a range of ports. Ports start at 700 and goto 740, if the client cant connect on 700, it will retry on 701 and work its way to 740.

    When the server receives the address in use error, it will do localport + 1 to get the next port, if localport+1 > 740 then localport = 700

    Well my next problem is why i am here. At first, after i set the program to listen after it disconnected, it seemed like it wasnt doing it.. So i use the shell command to close and restart the program again. It always comes up working and listening on port 700. But everytime it restarts the server, its minimzed.. And about 90% of the time, the server is completly unresponsive unless i restore it so that its not minimized anymore.. But sometimes it works minimized!

    Whats going on here, and how can i fix this? Also i'd like to have it running in the system tray, but unless somebody knows a quick way to do that, and fix this issue, i'll be glad to hear that as well.

  2. #2

    Thread Starter
    Fanatic Member
    Join Date
    Jun 2001
    Location
    Oregon
    Posts
    643

    Re: Winsock, Not Reponsive

    ok i figured out the first part, i did this:

    Code:
    Shell App.Path & "\Server.exe", vbNormalFocus

    So now it opens it normally every time, and it works.. But the next problem is how can i get it to open minimized to the system tray without having that first error again?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width