[VB6] Winsock Problem

[TheZam]

Hey im sorry if this is a noob question since i just started VB6, but a few months ago i upgraded to Windows Vista Home Premium. So when i open VB6 and when i click on the winsock icon i get this error messege:

License information for this component not found. You do not have an appropriate license to use this functionality in the design enviornment.

Here is a screenie:

Any suggestions on how to fix?

 

[FragFrog]

Get a legal copy of VB.

Also, your topictitle did not adhere to the coders section rules - adhere to them from now on. Next time its a lock + infraction.

 

[TheZam]

ok sorry.

 

[Sprayz]

btw VB is a good "language" t get a taste of what programming is but if you play doing somthing that is independant of a bunch of runtime files...better start learning somthing real like c++,when I turned from VB to c++ i though"WTF i was doing with vb?",a nd im still a noob who knows almost nothing from both :throw:

 

[bitblaster]

I've had that problem on Visual Studio 6 learning edition; I had to upgrade to another version, I chose the Professional Edition.

And yeah, I bought them both... the learning edition will do that - from experience, it doesn't have to do with an "illegal copy".... although that was in my situation.

 

[jetgod]

Initially upgrade,
Also possible is that vista aint supporin' it.

 

[bitblaster]

I do have a question for you - how did you install Visual Studio 6 on Windows Vista?

I never seems to install for me, during setup, it tries to install Microsoft's Java Runtime, and then basically crashes.

 

[Nuklear]

I have an illegal copy and it still works. 0.o

 

[nlyp54]

i had the same problem but then i went to some tutorial or w/e and its something to do with start -> run -> regedit (or something) sry if i knew more id help

 

[username1]

sage

http://www.google.com/search?hl=en&ie=ISO-8859-1&q=winsock&meta=

So you need a bloody license to use functions in DLLs that you already own and come with every single version of Windows since 95? Looks like M$ is deceiving these VB "programmers", since all you need is a compiler to write some Winsock code. See the sample I put in the Showcase subforum for an example.

p.s. the faceless and the truth cannot be silenced