Home Forums SharewareOnSale Deals Discussion Connectivity Fixer PRO / Jul 21 2020 Reply To: Connectivity Fixer PRO / Jul 21 2020

#16184864 Quote
Peter Blaise
Guest

Umm … why, when I double-click on the desktop icon to raise the program, does it load a second separate copy of the program … and when I double-click again, a third copy of the program loads … does it mot see itself already loaded from the first time?

Is there something seriously dysfunctional in the SOS version ( or the Pro version altogether ) of BadoSoft Connectivity Fixer Pro?

Yup, they’ve each got different logs from each other, they are out of sync in their [ Netinfo ], their settings are different, as if the second does not inherit any knowledge of the first, then a popup says there’s a connection problem, it seems to be a popup from the second version in memory, I tell it to go ahead and fix the problem, and the log for the second version shows “fixed”. while the first version in memory has been happy and dormant during the entire time.

Document info: Connectivity Fixer PRO – Log file
Creation date: Wednesday, July 22, 2020-07-22
Autor: Badosoft (Connectivity Fixer PRO – Software)
Visit http://www.badosoft.com for more information.

22. 7. / 0:58 Connection unstable!
Connectivity Fixer PRO has detected a problem with your Internet connection!

22. 7. / 0:59 Connection state improved
Internet connection state has stabilized and improved!

22. 7. / 0:59 Connection unstable!
Connectivity Fixer PRO has detected a problem with your Internet connection!

22. 7. / 1:0 Connection interference!
Connectivity Fixer PRO has detected a slight interferences with your Internet connection!

22. 7. / 1:0 Connection lost!
Connectivity Fixer PRO has detected a problem with your Internet connection!

22. 7. / 1:1 Problem fixed!
Successfully fixed your internet connection!

So … Badosoft Connectivity Fixer Pro v2.2 for others acquired outside of this SOS offering … how does that behave? Doe anyone know? Should we SOS folks submit bug reports to Badosoft Helpdesk ( hey, jut to help them out, not expecting free support, especially after reading prior posts, just reporting misbehavior ), or is the SOS version so different that the only really relevant place to submit reports of misbehavior are here, since non-SOS acquisitions of the software will not experience the same misbehavior?

Should I keep clicking on the desktop icon and see how many separate copies of BadoSoft Connectivity Fixer Pro will load into memory and fill up and use all computer resources?

The last loaded one seems to be the boss, as the prior loaded ones still im memory seem to never see the “problems” the last loaded one sees – I’m guessing th elast instance sees the effects of the prior instances as the prior instances check the connection, ping, and whatever, and the last instance sees that as a problem to be fixed, then the first instances quiesce, and the last instance says “hey, I fixed it!” when actually, it did nothing but observe the comings and goings of the first instance(s).

I do not see this situation or condition under [ Bugs ] or [ Known Issues ] at the Badosoft Helpdesk.

I wasn’t trying to break it, it’s just that with an auto-hiding-task-bar, I was trying to bring the program window back on screen … click-click the desktop icon, and it starts a fresh copy, click-click again, and another fresh copy, and so on, and so on …

How to control this … the Pro version of a totally unrelated program from another vendor, Bitsum Process Lasso, offers to limit the number of instances of any program, does anyone know of another way to prevent accidental multiple instances of Badosoft Connectivity Fixer Pro?

And, by the way, what “fixes” did the second loaded instance of Badosoft Connectivity Pro think it applied that the first loaded instance missed?

And of course, Internet connectivity is gone while the multiple instances of Badosoft Connectivity Fixer Pro fight it out, so if anyone has a dead Internet when using this, check [ Task Manager ] to see if there are multiple instances loaded and running.

I guess I can use [ Task Manager ] to kill them all and restart just one, and remember this quirky behavior.

And, yes, it’s possible to have more than one autoload during startup, it’s easy to find them in Run, Startup, and Task Scheduler, I see 5 listed so far.

What does this fix, again?