Results 1 to 11 of 11

Thread: Winsock OCX

  1. #1

    Thread Starter
    Lively Member
    Join Date
    May 2000
    Location
    Atlanta, GA
    Posts
    80

    Question

    Can you write straight to the MSWINSCK.DLL rather than using the M$ Winsock control in VB? Problem is that I have a small chat EXE to distribute and don't want to force everyone to run a setup or manually register MSWINSCK.OCX.

    Thanks,
    Kevin

    VB6 w/SP4

  2. #2
    Frenzied Member Jop's Avatar
    Join Date
    Mar 2000
    Location
    Amsterdam, the Netherlands
    Posts
    1,986
    hmm... I think the Winsock Control isn't big for nuthin' but maybe it's possible with the API.
    I'm sorry I can't help you but I'm also interested... Maybe ask it in the Internet Forum (also at this site)

    Jop - validweb.nl

    Alcohol doesn't solve any problems, but then again, neither does milk.

  3. #3
    Guest
    Why don't you have your program register it silently?

  4. #4

    Thread Starter
    Lively Member
    Join Date
    May 2000
    Location
    Atlanta, GA
    Posts
    80
    Then I would have to include the OCX with the EXE. And how do I determine if it has already been registered?

  5. #5
    Guest
    How about the first time the program is loaded..have your program register it once and that's all. Write an ini file or to the registry saying that it has been registered.

  6. #6
    Addicted Member Tiovital's Avatar
    Join Date
    Apr 2000
    Posts
    249
    Do you want to use API function Instead Of winsock control in VB?



  7. #7

    Thread Starter
    Lively Member
    Join Date
    May 2000
    Location
    Atlanta, GA
    Posts
    80

    Exclamation

    Tiovital,

    Yes. Definitely!

  8. #8
    Hyperactive Member
    Join Date
    May 2000
    Posts
    367
    Can you write straight to the MSWINSCK.DLL rather than using the M$ Winsock control in VB? Problem is that I have a small chat EXE to distribute and don't want to force everyone to run a setup or manually register MSWINSCK.OCX
    first of all do you mean the winsock.dll? I dont have anything called mswinsck.dll

    second, if you do mean the winsock.dll why would you want to write to it? It contains the api calls for winsock, which is stuff that you probably dont want to mess with.

  9. #9

    Thread Starter
    Lively Member
    Join Date
    May 2000
    Location
    Atlanta, GA
    Posts
    80
    All I want to do is get the functionality of the Winsock control without using the winsock control itself. Are there API calls that would allow me to make a network connection, transmit a message, receive a response message, and disconnect?

    My app is very small and it is more of a hassle distributing the Winsock Control with the EXE.

    Thanks!

  10. #10
    Hyperactive Member
    Join Date
    May 2000
    Posts
    367
    Yeppers, use the winsock api calls.

    There are some examples out there that use the winsock api calls.


  11. #11
    Addicted Member Tiovital's Avatar
    Join Date
    Apr 2000
    Posts
    249
    ksutton,
    I think i have what u want in my other computer - BUT - I am in a long weekend - and when ill return - i will search it and send it for u...

    Regards

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