Autoswitch causes NetSetMan to lockup on Win7, etc. / Bug Reports / NetSetMan Support

NetSetMan Support

Search for already answered questions about NetSetMan (Pro) or ask new ones

You are not logged in.

#1 2019-11-27 17:47

TRTMan
Member
Registered: 2019-11-27
Posts: 3

Autoswitch causes NetSetMan to lockup on Win7, etc.

Win7 x64, NetSetMan 4.7.2, NSM Service running.

When AutoSwitch for a profile is set to "Show system notification" and that profile is autoswitched to, NetSetMan freezes, the system tray icon superimposes a small gear, sometimes rotating, and the profile's IP configuration is never completed. All's well when AutoSwitch for that profile is set to "Show notification and activation dialog".

Second, my profile to configure the "Local Area Connection" is set to autoswitch when the Adapter Status is "Connected". AutoSwitch does not engage once the WiFi adapter is disabled and the ethernet adapter, enabled. Subsequently, it will immediately begin to autoswitch when the AutoSwitch dialog is opened on any profile.

Otherwise, an essential program!

Offline

#2 2019-11-27 18:13

TRTMan
Member
Registered: 2019-11-27
Posts: 3

Re: Autoswitch causes NetSetMan to lockup on Win7, etc.

OK! NetSetMan make liar out of TRTMan!

Autoswitch now does engage when the WiFi adapter is disabled and ethernet adapter enabled. TRTMan has revenge: if the "Network Location" condition is added and set to require "TellRTale" to be available, AutoSwitch does not engage when the WiFi adapter is disabled and ethernet adapter enabled. The "Adapters Details" tool reports the Network Location GUID to be TellRTale {blah blah blah} but AutoSwitch will only engage subsequently when the AutoSwitch dialog is opened.

Back atcha, NetSetMan!

Offline

#3 2019-11-28 17:09

NetSetMan Support
Administrator
Registered: 2005-08-06
Posts: 1,878

Re: Autoswitch causes NetSetMan to lockup on Win7, etc.

AutoSwitch is a complex feature, because it has to take a lot of different information into account.
For not stressing the system too much, there might be some delay, before AutoSwitch recognizes that a profiles needs to be activated.

Having said that, we have already completely reworked the AutoSwitch functionality. It will be available with the next bigger update. There will be a much better overview over the conditions, making it more clear why a profile has been activated and why not. All triggers and conditions have been reworked as well.

Because of that, we're afraid, we won't be able to analyze your case (with the "old" AutoSwitch) in detail. Please try to use it as it is for now and test your scenario as soon as we released the next big version. Unfortunately, we cannot give an estimate for the release date yet.

Offline

#4 2019-11-29 01:11

TRTMan
Member
Registered: 2019-11-27
Posts: 3

Re: Autoswitch causes NetSetMan to lockup on Win7, etc.

No problem. I will enthusiastically give the new new version a workout when it comes out. I suspect "Show system notification" is my Win7 problem but hopefully it was yours, ha ha.

Thanks for your diligence.

Offline