Vista Wi-Fi Signal Strength

Figured it out!

Set oShell  = CreateObject("WScript.shell")
strCommand = "cmd /c netsh wlan show networks mode=bssid > c:\testing.txt"
oShell.run strCommand, 0, True

Won't be long and I'll have a working Wi-Fi meter that runs in Vista!

I just submitted a working Vista Wi-Fi meter.  Pending moderation, it should be available in a couple of days.  Here is the script if anyone is interested:

That is so cool Cap'n!

Can't wait to see it!

Well, the first version isn't too fancy.  It's more of a proof of concept for me than anything else.  I plan to spruce it up with more user definable options, and fancier graphics.  I designed this version to fit on my DX built taskbar, so it's small and basic so it does not take up much space. 

Does it work on XP too?

It should.  It uses the standard netsh (Network Services Shell) command to do its business, which is included with XP. 

Quoting Zubaz, reply 5

Does it work on XP too?

I will try to test it on my XP machine so I can give a definate answer.  The existing Wi-Fi meter objects in the Wincustomize library look like they work fine on XP(and are very nice) - based on the user comments.  I would have been content to use one of these, but I tried a long time to get them to work on Vista and after some research found out that the WMI calls used won't work, so that's why I made it.

Just tested it on my XP machine.  Does NOT work on XP.  I geuss the netsh command has a little more functionality in Vista then in XP.  XP users will have to use one of the other existing wifi widgets, sorry.

Going to update the description to indicate that?

Hey CaptainBeaker!

A little bit of feedback:

• creating a file at the root folder isn't really nice (plus you might not have the rights to do it anyway). It might be better to put that file in the temp directory. You can get it with the following script:

• you can probably save the whole file creation and use the Exec command on the WScript.Shell object. It returns a WshScriptExec object with access to the StdOut and StdErr channels (ie. no need to redirect output). Take a look at the WScript help, there are a few examples on how to use it.
•  that big switch case is hurting my eyes . What's wrong with a few ifs and elses?

Sorry for the garbled script (and the edit button is not working ).

Good job on the widget. Looking forward for a version using the canvas

Thanks for the suggestions.  I have done away with the select case and used your code to place the file in the user temp folder.

I'm still reading about WshScriptExec.  It would be nice to capture the output of netsh without having to mess with a file.  I did a quick test.  The Exec command seems to call up a command window briefly when executing the NETSH command.  I have to find a way to supress this command window or I'll be stuck with my method.

Me too!  However, I have to get Canvas working on my Vista machine(s) first.  I imported your .dxpack included in the latest build and still nothing.  I put one of my drawing scripts into a new object and started the script.  Got a (Null) error from my script on the following line:

Set ctx = canvas.getContext("2d")

The Canvas plug-in was added to the 'Additional Abilities' of the object

Mmmh, not good. I'm going to add some logging to the next beta so we can track down that problem. There is an error when creating the cairo surface and context for some reason (and it's strange that it's not crashing, given that this part is done earlier and lacks some error checking... oops )

I've been (partly) successful using Exec instead of Run and capturing the stdout  and putting the result into a variable.   The code bolw does exactly what I need it to do, but... It does not run under DX.  It runs from the desktop fine - suppresses the cmd window and puts stdout into a variable.  I don't think Wscript attributes are visible from within DX. I get object undefined errors wherever I have Wscript when I run the script from inside a Dx object.  Telling the object to use an external script (containing the code below) still results in the same errors.

However, I have found a better solution which still uses the Run command and does not use a file.  I had a revelation of sorts...Output from most command line functions can be directed to a file using ">", but starting with Server 2003, this same output can be directed to the Clipboard using "|clip" .

I've replaced all of the file saving and reading stuff with:

strCommand = "netsh wlan show networks mode=bssid |clip"

oShell.run strCommand, 0, True 

netshresults = System.Clipboard

In my code, I save the current clipboard contents into a temp variable before I put the netsh stuff into it, then read the clipboard into a variable so I can parse it up.  I then put the original contents of the clipboard back.

I'm currently testing everything right now and everything seems to be working.  I'll post the update tonight. 

You could add some code to see if they are running XP or Vista, then use the above code for Vista and this WMI Call for XP:

Function to get Windows Version:

yep.. EDIT btn aint working.. ignore the <br> in the Function call at the top of the code..

Enjoy

Great idea!

Might be better to check for XP and use WMI only there, since it probably won't work with Windows 7 either.

I never used DX and don't know how it exactly works, but i needed to know the signal of the wlan i'm connected to for samurize and used:

C:\Windows\System32\cmd.exe /c FOR /F "tokens=2 delims=: " %i IN ('netsh wlan show interfaces ^| find " Señal"') DO @echo %i

or directly on a command prompt

FOR /F "tokens=2 delims=: " %i IN ('netsh wlan show interfaces ^| find " Señal"') DO @echo %i

IMPORTANT NOTE: it works for me both in Vista and 7. But my system is in spanish, so probably you'll have to use "Signal" instead of "Señal" or you could also get any other info shown in netsh wlan show interfaces.

EDIT: For the 'show network' command it should be:

Again, changing "Señal" to "Signal" (or however it's written in english) for it to work in english systems.

Hope this helps