NetSetMan Support

1techconsultant

Member

Registered: 2007-01-19

Posts: 3

2.3.3 (Pro) Still Buggy

Starting with NSM Pro version 2.3.2, previously defined settings in the profiles are not loaded.  Reverting to version 2.3.1 recovers those settings.

Example: In 2.3.1, I set a profile called "test" and name the first tab "tab1." I set an IP address ("Use the following IP address") of 192.168.4.1.  I then upgrade to 2.3.2 (or 2.3.3 to get rid of the debug message.) When I go to the "test" profile and "tab1" the IP address is missing (but the check box to use it is set.)

Perhaps the "Registration information moved from registry to NSM folder" enhancement was not a "complete" move?

Will this be fixed in 2.3.4? I'd rather not have to enter all that data again (I have 7 profiles with all 6 tabs utilized...with most individual settings used!).

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: 2.3.3 (Pro) Still Buggy

After several tests I was not able to reconstruct your problem.
Could you please send me an email with your settings.ini attached so I can have a closer look at this problem? This file is located in the program folder.

1techconsultant

Member

Registered: 2007-01-19

Posts: 3

Re: 2.3.3 (Pro) Still Buggy

Hi Ilja.

Much as I would like to send that file, I cannot: It contains too much sensitive information about client networks which I cannot divulge due to confidentiality agreements.

If there is any other way I can help (something I can look for, a test I can perform, etc.) let me know.

I tried installing version 2.3.3 into a new directory, inserting a test entry and comparing the old and new settings.ini files.  The structure is a bit different.  Notably:

Old file IP information structure:

IP1=192
Sub1=255
Gate1=192
DNSP1=192
DNSA1=
WINS1=
IP2=168
Sub2=255
Gate2=168
DNSP2=168
DNSA2=
WINS2=
IP3=0
Sub3=255
Gate3=0
DNSP3=0
DNSA3=
WINS3=
IP4=150
Sub4=0
Gate4=5
DNSP4=5
DNSA4=
WINS4=

New file IP information structure (A change to single line format?):

IPList=192.168.0.150:255.255.255.0
GatewayList=192.168.0.5

Based on this, it is no wonder that my IP info is missing after upgrading to 2.3.3: The program is (now) expecting the IP info by reading the IPList entry, not as IP1, IP2, etc.

Does that point you in the right direction?

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: 2.3.3 (Pro) Still Buggy

I think I've got the problem. The settings might not have been converted to the new address-format correctly.

Would you like to do a short beta test?

1techconsultant

Member

Registered: 2007-01-19

Posts: 3

Re: 2.3.3 (Pro) Still Buggy

Absolutely! I get quite a bit of use from the program and have ample opportunity for real world testing.

bensil

Member

Registered: 2007-03-30

Posts: 1

Re: 2.3.3 (Pro) Still Buggy

After activating my work profile this morning, my RoboForm taskbar was reporting Firefox as an unsupported browser. I fixed the problem by reinstalling the add-on from the RoboForm website. I didn't check out IE before the reinstallation, as I don't use it much. I was expecting to have to rejoin the domain at work after switching to a workgroup at home, but I was pleased that I didn't have to. I would like to not have to reinstall RoboForm every day, either. Let me know if I should be doing something differently.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: 2.3.3 (Pro) Still Buggy

I don't think this has something to do with the other problem (which btw is already solved).

Actually I don't really know how I can help you with RoboForm, because I'm not familiar with that tool and I don't know what settings you're changing in that profile.

I can only guess that it might have something to do with changing the proxy settings in the Firefox. Those settings are written in the profile file of Firefox. If a certain settings line doesn't exist it's created at the end of the file. The whole file is sorted automatically by Firefox at every start.
If a changed profile file is a problem for Roboform then you should probably stop using it or the proxy feature of NetSetMan.

You can also try to close Firefox and start it again without reinstalling anything.