^Yep. That's the tricky part of the equation. You'd need to get that information somehow. If not through devcon, then some other way. I'd guess polling the registry would be how a pro would get it.

Given permissions being set that disallow normal users from disabling the adapters, how is using devcon, (which I've used for other things), going to help?

Guess I'll have to fire up XP Pro and have a play in the Group Policy editor.

Scratch that, looks like server OS only.

Time to put the thinking cap on.

^ You are correct. There is a 32 and a 64bit version. Completely forgot about that.

The 64bit version included is for Intel Itaniums, (ia64), won't work on x64 installations.

i don't think you're a cracker failure.

I wasn't suggesting I'm a cracker failure, perish the thought, I was suggesting my next program would be a cracker failure....as in format your drive type  

^Yep. That's the tricky part of the equation. You'd need to get that information somehow. If not through devcon, then some other way. I'd guess polling the registry would be how a pro would get it.

devcon listclass net >list.txt

Then string match the first 3 characters of each line to USB, PCI or BTH - should pick up almost any network hardware, giving you hardware ID, (for devcon), and adapter name, (for GUI).

Man, this adapter ID thing is totally the reason why there are no good third party network software for windows.  I've always wondered why there were no cool little software out there to improve on little annoyances like this related to networks.

It would be nice to know whether devcon worked in your situation before proceeding along this path.

Any chance you can download DEVCON, do the following in a CLI and paste the results in list.txt here?

devcon listclass net >list.txt

Then we could give you a devcon command to try and disable the adapter, if it doesn't work then there doesn't seem to be an easy way around the permissions.

Has anybody here ever even seen an Itanium-based machine, let alone worked with one?

I have, both seen and worked with, but it wasn't running Windows but HP-UX. It's rock-steady, and performs quite good, for the tasks it was designed for. Not particularly good in any Windows environment though.

sweet!

OK, give this a try - it uses devcon to get the status and (dis|en)able the network adapter.

I don't see how it's going to work if you're blocked from (dis|en)abling via the Network Connections Control Panel but who knows, stranger things have happened.

If it doesn't work, then the only option left is to either modify the program to elevate to SYSTEM user or try and run the devcon command elevated and see what happens.

NOTES: You no longer have a choice of toggling ALL connections.

Actual fact it probably works better than NetToggle because the status is more consistantly reported but it does have a LOT less error checking

4wd, you've almost got it!  Please don't stop!
i just tried the file listed above, and it works functionally, but it gives the following error dialog when toggling it on or off:


So I get that error when toggling the button on and off, and sometimes the save nic dialog pops up again.  So the program is working, it's just a little buggy.  Cmon, we can do this.  er...you can...

i just tried the file listed above, and it works functionally, but it gives the following error dialog when toggling it on or off: (see attachment in previous post)
So I get that error when toggling the button on and off,

OK, that's a result of me not getting the syntax of DevCon correct - it's (en|dis)abling all matching interfaces instead of just the selected one.  I don't have a machine with two NICs with the same ID but different instances.  Plus not closing the STDIO handle after running DevCon.

The attached should fix that.

and sometimes the save nic dialog pops up again.

Are you sure you're not hitting the RMB, (that will bring up the interface selection window), on the icon instead of the LMB ?

LMB - Toggle
RMB - Config

There's only three ways to call the NIC Selector routine:
1) First run of the program will call it when it doesn't find NICToggle.ini in the same directory as the executable.
2) If you run the program and the previously saved NIC hardware ID instance, (has to match exactly), doesn't exist it will open the selector to pick another one, (eg. you're running it from a flash drive and plugged it into a new machine).
3) You click the right mouse button on the icon.

Next time it happens can you try and recreate and/or note the steps taken, state of NIC before/after, etc?

NOTES: There's an arbitrary limit of 10 physical NICs, (PCI or USB), I'm sure there's a reason to have more, I just couldn't think of it.

v0.2

• Fixed - DevCon parameters NQR, was acting on all matching ID strings.
• Fixed - Forgot to close STDIO after each DevCon execution.  
• Added - Rescans available NICs when the config is called, (in case a USB NIC is plugged in).

To do:

• Add back 'All interfaces' option, (should easy - FLW).
• Add comments to source, (CYM).

UPDATED: See here.

OK I just tried it.  First, I don't get an error anymore.  It seems to work fine, but it's a little unstable.  My computer has to local area connections.  I chose the first one and it was the one I wasn't using.  I clicked on the icon, and it turned red.  I clicked again, and nothing happened.  i right clicked, and it seemed to just be frozen.  i had to kill it.  Then I ran it again, I right clicked, changed to the other connection.  I clicked, it turned red, and my connection was off.  Great!  I clicked again and it was back on.  Great!  Then...I didn't know how to exit.  It needs an exit.  If I were you, I'd make the right click bring up a menu, that says:
Change Connection
Exit

That's about it.  There's some crashing, but it works overall...and add an exit.

To exit: Right-click to bring up the select connection window, then just close it, (not Save).

But I'll change it to a Config menu just to be a conformist    

With the two connections:
Is the one that caused the lockup connected to a network, (ie. it has a cable and choose between networks to connect to) ?
Or, is it just an unused network port ?

I'll have to plug another NIC into my machine and have a play.

Strange, I can't replicate the problem here.

Can you try it again on the unused port and before you have to kill it can you see if devcon.exe appears in Task Manager or just NICToggle.exe.

Also, have Network Connections open and see if you can see the connection toggling between Enabled and Disabled.

Oh, and the contents of the ini file thanks.

Ah, I had it do it that once but could never get it to repeat it so wrote it off as some weird conflux of tongue position and astrological star positions.

EDIT: I think I found it - seems to happen if you initiate events too close together.  I've put a 5 second pause between event polling and it seems to have stopped it.

I'll try and get the RMB menu version up today, (that's my today, not yours), hopefully.

I'm assuming that because nobody has said it's wiped all their gmail accounts that it generally works?

Well, it seems to be working.  But it's a little funny.  The first time I ran the new version and clicked it, it made my computer really active for about 30 seconds.  Then the light flashed red, and immediately back to green.  So i clicked it again, and it flashed like that again...also with a lot of computer activity.  The third time, it stayed red, and worked.  So it's a little unstable, and it's doing a whole lot of pretty intense stuff when you click on it (I can hear my hard drive making noises, and all the open programs kind of pause a little, but for 20-30 seconds).

4wd: just to make sure that people find their answer quickly in this thread, maybe you could edit your first post and add the file to it instead?