<html><head><style type="text/css"><!-- DIV {margin:0px} --></style></head><body><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">WSH might be easier for you:<br><br>1. Since you can use JScript and VBScript, the learning curve is easier than PowerShell especially if you already know those languages or Javascript<br>2. WSH does not require .NET so it will work on legacy Windows systems like Win98/WinME.<br><br><span>The main site for WSH is <a target="_blank" href="http://msdn.microsoft.com/scripting">http://msdn.microsoft.com/scripting</a>. If you choose WSH, you'll need COM or ActiveX objects which wrap the winsock API. There are literally dozens of such objects available for free, including at least one from Microsoft (</span><a href="http://support.microsoft.com/?kbid=209905">Winsock Control)</a>. However, you might find COM objects specifically targeted for WSH easier to use,
such as <a href="http://www.arcticlabs.com/products/baseline/wsh.html">this one</a>. Please do your own research and analysis though; I haven't used these objects and am not endorsing them. The nice thing about using the Microsoft Winsock Control is that many people probably already have it installed.<br><br><a href="http://www.winscripter.com/WSH/Internet/79.aspx">Here</a> is sample code showing how someone used the Winsock Control with WSH JScript. I'm sure you can find lots more samples if you search.<br><br>
If you choose PowerShell, you'll want to use the classes in the <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemNetSockets.asp">System.Net.Sockets namespace</a>. They are managed classes wrapping the native winsock Win32 API functions.<br><br>Good luck,<br>Eric<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Anothony Georgeo <anogeorgeo@yahoo.com><br>To: or-talk@freehaven.net<br>Sent: Wednesday, August 2, 2006 9:41:27 PM<br>Subject: Re: Re[4]: Using Tor signals on Win32 NT (eg. pseudo-signals)?<br><br>Hi eric,<br><br><b><i>eric.jung@yahoo.com</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid; margin-left: 5px; padding-left: 5px;"> <style type="text/css"><!-- DIV {margin:0px;}--></style><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><div style="font-family: arial,helvetica,sans-serif; font-size:
10pt;">>I know some people are averse to installing .NET and, if that's the case with Anothony, then I doubt there's a viable (free) scripting solution.<br><br>I take this back. I forgot you can invoke COM objects from Windows Script Host (WSH) scripts. WSH only requires wscript.exe, not .NET (it predates .NET by a number of years). There are countless COM objects that handle socket communications.<br><br>Let me know if you need more info.<br></div></div></blockquote>Any extra info you feel like posting would be *extremely* helpfull as I am not a programmer. I have been reading up on PowerShell but I'm a bit
more confortable with traditional WSH.<br><br>I would prefer to use WSH as .Net is not required and WSH seems a bit easier than PowerShell.<br><br>I am most comfortable/knowledgeable with batch scripts (eg. .cmd's) but I'm willing to study and do what it takes to to learn WSH or PowerShell to achive my goal. I will use which ever you deem the most appropriate and efficient.<br><br>I really appreciate all the help/guidence you've given me so far but I don't want to become a pest.<br><br>I intend to post the script here (if Nick and Roger don't mind) as I am sure most users of Tor and Win32 NT would love to have access to the final script.<br><br>Thank you very much for your time, Anogeorgeo :-)<br><p>
</p><hr size="1">Do you Yahoo!?<br> Everyone is raving about the <a id="bodyLinks" rel="nofollow" target="_blank" href="http://us.rd.yahoo.com/evt=42297/*http://advision.webevents.yahoo.com/handraisers"> all-new Yahoo! Mail Beta.</a></div><br></div></div></body></html>