CapCrunCh
Comment #2 Sunday, December 7, 2003 2:44 AM
Comment #2 Sunday, December 7, 2003 2:44 AM
it might require an updated winsock control, i dont know the cause of the error hard to say in which control did the error occure?
Hus
Comment #3 Sunday, December 7, 2003 2:50 AM
Comment #3 Sunday, December 7, 2003 2:50 AM
Sorry, should of posted that info for you. It happens in "ConnectBtn".
CapCrunCh
Comment #4 Sunday, December 7, 2003 2:55 AM
Comment #4 Sunday, December 7, 2003 2:55 AM
line 23 in Connectbtn is DesktopX.ScriptObject("MySock").Control.Close
and it is the first thing i can see it would run into the winsock control the other line 23 of the other script ojects dont seem to relate to anything like that so im just guessing here that it is indeed the error you are recieving.
MySock is the winsock control i believe im useing the Microsoft WinSock Control Version 6
please let me know if this helps
and it is the first thing i can see it would run into the winsock control the other line 23 of the other script ojects dont seem to relate to anything like that so im just guessing here that it is indeed the error you are recieving.
MySock is the winsock control i believe im useing the Microsoft WinSock Control Version 6
please let me know if this helps
Hus
Comment #5 Sunday, December 7, 2003 3:08 AM
Comment #5 Sunday, December 7, 2003 3:08 AM
Cap, I am also using version 6 of mswinsck.ocx, if you want, you can email me here instead of leaving all these comments. 
alonb@optonline.net
alonb@optonline.net
kongit
Comment #6 Sunday, December 7, 2003 4:44 AM
Comment #6 Sunday, December 7, 2003 4:44 AM
sweet capn'crunch this is amazing. 
I don't use IRC but the sheer amount of ingenious deserves a great rating and a pat on the back.
I don't use IRC but the sheer amount of ingenious deserves a great rating and a pat on the back.
CapCrunCh
Comment #7 Sunday, December 7, 2003 4:53 AM
Comment #7 Sunday, December 7, 2003 4:53 AM
Thank You Travis!
i thought it was rather ingenious myself
im glad you like it, i spend a whole day working on it
and so far i am really happy with the outcome.
besides the error, Sir Hus has so generously pointed out.
i am currently working on a fix for this error and keep comming up short, if anybody has any information on this error please dont hesitate to add your 2 cents.
thank you!
i thought it was rather ingenious myself
im glad you like it, i spend a whole day working on it
and so far i am really happy with the outcome.
besides the error, Sir Hus has so generously pointed out.
i am currently working on a fix for this error and keep comming up short, if anybody has any information on this error please dont hesitate to add your 2 cents.
thank you!
Stockholm Syndrome
Comment #8 Sunday, December 7, 2003 6:05 PM
Comment #8 Sunday, December 7, 2003 6:05 PM
wonderful idea. I'd love to see this get going. 
I am getting the same error as Sir Hus. It also crashes DesktopX after when I close it.
Cap what OS are you using? I don't have that Winsock file on my machine at all, this is Windows 2000. (Yes, I unchecked "hide system files" before searching.)
I am getting the same error as Sir Hus. It also crashes DesktopX after when I close it.
Cap what OS are you using? I don't have that Winsock file on my machine at all, this is Windows 2000. (Yes, I unchecked "hide system files" before searching.)
CapCrunCh
Comment #9 Sunday, December 7, 2003 6:25 PM
Comment #9 Sunday, December 7, 2003 6:25 PM
Well stockholm i am running windows xp pro with service pack 1 but i have the visual basic runtimes and the .net framework im wundering if that is what is going on here
i have managed to reproduce the error myself and i am haveing truble trying to figure it out, i have copied over the MSWINSCK.OCX from my machine here and registerd it etc and when i load it into desktopx the control has no properties and i still get the same error, i have done everything short of installing the .net framework on that machine and am hopeing this is not the case as the .net framework is big. i will give it a shot just for the cause
if it works i will know the answer. wish me luck!
i have managed to reproduce the error myself and i am haveing truble trying to figure it out, i have copied over the MSWINSCK.OCX from my machine here and registerd it etc and when i load it into desktopx the control has no properties and i still get the same error, i have done everything short of installing the .net framework on that machine and am hopeing this is not the case as the .net framework is big. i will give it a shot just for the cause
if it works i will know the answer. wish me luck!
[brazen weep]
Comment #10 Sunday, December 7, 2003 6:48 PM
Comment #10 Sunday, December 7, 2003 6:48 PM
Very nice, CapCrunCh! And thanks for the props on the AddLine sub! I've never used IRC, but I'll have to give it a try now that I see this object! Nice work!! 
CapCrunCh
Comment #11 Monday, December 8, 2003 1:19 AM
Comment #11 Monday, December 8, 2003 1:19 AM
Well thanks again for the exelent comment Brazen Weep.
I have downloaded several objects of your fine work and have to say your stuff makes up allot of whats on here, i just hope i can have sutch a fine library of exalent objects on here aswell.
As for the MSWINSCK.OCX error..
i have yet to figure out why it only runs with visual basic installed. it is not the .net framework and i think its safe to say it has nothing to do with it.
i have worked quite awhile on finding a reason to this and have failed miserably.. if anybody has any info on why i cant see the properties of the MSWINSCK.OCX control in the script control info pane unless i have visual basic installed. what happends differently durring the installation of visual basic that could change the control? does it register it differently? any information would be helpfull.
I want to thank everybody who has/had shared/shares interest in this object.
and wish everybody Happy Holidays!
I have downloaded several objects of your fine work and have to say your stuff makes up allot of whats on here, i just hope i can have sutch a fine library of exalent objects on here aswell.
As for the MSWINSCK.OCX error..
i have yet to figure out why it only runs with visual basic installed. it is not the .net framework and i think its safe to say it has nothing to do with it.
i have worked quite awhile on finding a reason to this and have failed miserably.. if anybody has any info on why i cant see the properties of the MSWINSCK.OCX control in the script control info pane unless i have visual basic installed. what happends differently durring the installation of visual basic that could change the control? does it register it differently? any information would be helpfull.
I want to thank everybody who has/had shared/shares interest in this object.
and wish everybody Happy Holidays!
CapCrunCh
Comment #12 Monday, December 8, 2003 10:02 PM
Comment #12 Monday, December 8, 2003 10:02 PM
Im sad to say i have found the cause of the MSWINSCK.OCX error msg.
It is a licensing issue. Generally this Microsoft control cannot be used in VBScript unless you have a Visual Studio or other appropriate design application installed on your PC or have this control licensed.
I will do what i can to try and get arround this problem, mabe even write my own Sock control using API (if im up to it). If anybody has a better solution or a different sock control i can use i would appresheate it very much thank you and sory to dissapoint...
It is a licensing issue. Generally this Microsoft control cannot be used in VBScript unless you have a Visual Studio or other appropriate design application installed on your PC or have this control licensed.
I will do what i can to try and get arround this problem, mabe even write my own Sock control using API (if im up to it). If anybody has a better solution or a different sock control i can use i would appresheate it very much thank you and sory to dissapoint...
[brazen weep]
Comment #13 Monday, December 8, 2003 11:02 PM
Comment #13 Monday, December 8, 2003 11:02 PM
CapCruCh: Check http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=44590&lngWId=1 for a VB project that contains an API-only Winsock wrapper. This should help in creating your own Winsock.OCX easily !
!
[brazen weep]
Comment #14 Monday, December 8, 2003 11:04 PM
Comment #14 Monday, December 8, 2003 11:04 PM
You may also want to check http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=9996&lngWId=1 for a complete Winsock .OCX replacement. You'll just have to compile it yourself and give credit I think
CapCrunCh
Comment #15 Tuesday, December 9, 2003 12:02 AM
Comment #15 Tuesday, December 9, 2003 12:02 AM
Thank you Brazen i have just tried this one http://www.gurgensvbstuff.com/index.php?ID=27 that i found it is like you said just a wrapper but i am haveing trubble with it aswell. it is hard for me to edit this now without removeing visual basic so i must do it on a different machine (that is much slower) but i will indeed try your links next (soon as i clean this all up again). so i guess i just need some time with this.. thank you for your help and i will try to have this updated as soon as i can.
on a side note do you think this would work? http://www.piclist.com/techref/os/win/instMSwinsock.htm
it sounds illegal to me. anywase Thanks again brazen for the links!
on a side note do you think this would work? http://www.piclist.com/techref/os/win/instMSwinsock.htm
it sounds illegal to me. anywase Thanks again brazen for the links!
CapCrunCh
Comment #16 Tuesday, December 9, 2003 12:40 AM
Comment #16 Tuesday, December 9, 2003 12:40 AM
i have checked this http://www.piclist.com/techref/os/win/instMSwinsock.htm
and it does indeed work!
you can download the files needed here http://www.sxlist.com/images/mswinsock.zip
use it at your own risk! (or at least till i find a better way)
i have no idea if it is indeed illegal or not but it does allow my control to function the way it does on my machine.
i don't hold any responsability for anybodys actions but myown, i dont think anybody should download it because it is defying a license agreement from microsoft.
i found the link just doing a search on google.com
i have also already started working on my own fix (using again some great links from Brazen Weep) and it should be ready shortly (unless other complications).
PS: i do have one question for everybody, did anybody get it to work without error? LOL
and it does indeed work!
you can download the files needed here http://www.sxlist.com/images/mswinsock.zip
use it at your own risk! (or at least till i find a better way)
i have no idea if it is indeed illegal or not but it does allow my control to function the way it does on my machine.
i don't hold any responsability for anybodys actions but myown, i dont think anybody should download it because it is defying a license agreement from microsoft.
i found the link just doing a search on google.com
i have also already started working on my own fix (using again some great links from Brazen Weep) and it should be ready shortly (unless other complications).
PS: i do have one question for everybody, did anybody get it to work without error? LOL
CapCrunCh
Comment #17 Thursday, December 11, 2003 4:47 AM
Comment #17 Thursday, December 11, 2003 4:47 AM
i have been running myself into the ground trying to fix this object and have found out why this cant be done using the microsoft winsock.ocx control. http://support.microsoft.com/default.aspx?scid=kb;EN-US;q31398 to microsoft
anywase it goes on saying how the control must be on a form still and cant be used the way i need to use it.. so i think i will take a vote on removing this object or not
i will try to find a different walkaround perhaps using the socks api within the script (i havent even tried that yet) so while i do this post your vote (YAY or NA)..
Thank you..
anywase it goes on saying how the control must be on a form still and cant be used the way i need to use it.. so i think i will take a vote on removing this object or not
i will try to find a different walkaround perhaps using the socks api within the script (i havent even tried that yet) so while i do this post your vote (YAY or NA)..
Thank you..
CapCrunCh
Comment #18 Saturday, January 10, 2004 3:33 AM
Comment #18 Saturday, January 10, 2004 3:33 AM
I have released a new version of this object that WORKS!
yes i have found a walkaround for the stupid winsock error. it is a winsock wrapper i have found (thanks to brazen weep for links) and i think it might just be the ticket as it is working great right now! althoe it is in alpha stages it is also currently Waiting Approval i will have a link from here as soon as i can. thank you for you support.
yes i have found a walkaround for the stupid winsock error. it is a winsock wrapper i have found (thanks to brazen weep for links) and i think it might just be the ticket as it is working great right now! althoe it is in alpha stages it is also currently Waiting Approval i will have a link from here as soon as i can. thank you for you support.
CapCrunCh
Comment #19 Saturday, January 10, 2004 7:28 PM
Comment #19 Saturday, January 10, 2004 7:28 PM
the new version can be found https://www.wincustomize.com/skins.asp?library=3&SkinID=3214 here but it is still real basic and needs some work still.
i will be updateing it soon thank you.
i will be updateing it soon thank you.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading files.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Comment #1 Sunday, December 7, 2003 2:38 AM
Object doesn't support this property or method: 'DesktopX.ScriptObject(...).Control'
Line: 23