Shoutbox

If it's possible, which one ?

Thanks

In my webserver script i was working on i used

code:

---

new ActiveXObject( "MSWinsock.Winsock.1" );

---

Doesn't seem to work here |:

code:

---

function Test()
{
var ws = new ActiveXObject( "MSWinsock.Winsock.1" );
return 'abc';
}

---

doesn't return anything

code:

---

function Test()
{
//var ws = new ActiveXObject( "MSWinsock.Winsock.1" );
return 'abc';
}

---

returns 'abc'

Any ideas ? |:

quote:

---

Originally posted by Pai
Doesn't seem to work here |:

code:

---

function Test()
{
var ws = new ActiveXObject( "MSWinsock.Winsock.1" );
return 'abc';
}

---

doesn't return anything

code:

---

function Test()
{
//var ws = new ActiveXObject( "MSWinsock.Winsock.1" );
return 'abc';
}

---

returns 'abc'

Any ideas ? |:

---

Well when you use return "abc" your saying the return value of the function is "abc".

How about trying this :

code:

---

function Test(){
    var ws = new ActiveXObject( "MSWinsock.Winsock.1" );
    return ws.LocalIP;
}

---

Yes you are right, but my point was that "something wrong" happened when I declared the new ActiveXObject, stoping the function so that it didn't reach the line to return something.

I've tried that return ws.LocalIP in the past and also didn't work (and obviously I just retried it to make sure), making me believe that "MSWinsock.Winsock.1" isn't a valid ActiveXObject, at least in my pc

Indeed not everyone has "MSWinsock.Winsock.1". Thus:

quote:

---

Originally posted by -dt-
In my webserver script i was working on i used

code:

---

new ActiveXObject( "MSWinsock.Winsock.1" );

---

---

Never use the "blahblah.1", "blahblah.2", "blahblah.3", etc objects. Not everybody has them.

The ".x" indicates that there are multiple versions registered on your computer (which may on its turn indicate duplicated, even corrupted objects).

When you omit the ".x", the default one is loaded instead (as that is its proper name; thus without that ".x"). And if present, the system will search for the latest (or not corrupted) version on its own.

Note1: This goes for all ActiveX objects, not just for "MSWinsock.Winsock".

Note2: When you use non standard ActiveX objects, or objects which depend on other possibly not installed stuff, always check if they exist on the hosts computer. Don't automatically assume that everybody has them.

True, however, remember that Messenger Plus! Live cannot run on anything below Windows XP, this means that you can happily use any object that comes with XP without worrying about backward compatibility (just make sure you don't use objects installed by the SP2 or make sure your script displays appropriate errors to the user).

Well, Winsock without the .1 doesn't work with me either.

I appreciate everyone's explanation, but before I started this topic I googled a bit (ok a lot) and found a couple of Winsock ActiveXObjects ("OSWINSCK.Winsock" and "MSWinsock.Winsock") which I have tried and didn't work, so "MSWinsock.Winsock" didn't work for me either

After debugging my script, I found an interesting thing:

» when I use ActiveXObject "MSWinsock.Winsock" or "MSWinsock.Winsock.1", I get in the debugger

code:

---

Error: unknown.
       Line: 128. Code: -2147221230.

---

» when I use ActiveXObject "MSWinsock.Winsock.x", I get error

code:

---

Error: The Automation server can't create the object.
       Line: 128. Code: -2146827859.

---

So, I *should* be able to use that but my PC can't create it ?

PS: The debugger text was translated back to english as close as I can get, because it was in Portuguese, so it might not be as accurate as the proper english text.

edit:

PS2: How can I find out for sure what ActiveXObjects I have installed in my system ? Or a way to find out which Objects I have, because I'm starting to think that something went wrong when I installed XP and the winsock object didn't got installed :X

quote:

---

Originally posted by Pai
PS2: How can I find out for sure what ActiveXObjects I have installed in my system ? Or a way to find out which Objects I have, because I'm starting to think that something went wrong when I installed XP and the winsock object didn't got installed :X

---

I use ActiveX manager