Settings reset for no apparent reason

[DAOWAce]

Started up PL today to add DOSBOX to my non-HT/game list and discovered that every single custom config for processes was empty.

I had quite a substantial amount of processes built up over the last 2 years I've used the program.

I had upgraded to a beta version not too long ago for the first time as I wanted one of the fixes included in it.  I now question if that was the cause for the wipe.  Also, one of the updates reset the UI again, so I had to go through the process of reconfiguring how I had my columns setup; maybe that update actually reset everything and I just didn't notice.  I think my tray icon also defaulted during this time..

Regardless, is there any sort of backup config file kept somewhere? It would really suck quite badly if I had to re-add everything from scratch.

[edkiefer]

I have not noticed this using any of beta's and I use ever one pretty much . I don't run any sepecific priority settings but do have power profiles and game app in list , all good so far .

there is a backup in for me this path (I am on Win7 )

C:\Users\[username]\AppData\Roaming\ProcessLasso

[DAOWAce]

Thanks, don't know why I didn't find this before; have known about it for ages, must be too tired.  Unfortunately, my backup config is quite out of date (May), but at least it's there!

Any input on these?

PipeDisabled
LogOutOfControlProcessesRestored2
WatchdogRules2

Just wondering if the '2' is a mistake or not and what this 'pipe' is, as it was set to true but is no longer found in the current config.

[edkiefer]

LogOutOfControlProcessesRestored2
WatchdogRules2

I have both these but I have no watchdogrules set

The PipeDisabled is not in my current ini and I forget what it was before .
It was set to PipeDisabled=False in my older one . Not that that matters now as its not included anymore .

[BenYeeHua]

I also being update to beta many times, I don't facing this issues.
I guess it can be the config is corrupt while adding that process, or there are a new bug that we don't know.
As running the shortcut to reset the PL will jump up a dialog and asking confirm now, so human error can be exclude.

Did you try adding it again with a clean config, and see how's going?
----
Wait...
I think I also found a new bug...

I only found a old config backup at the AppData\Roaming\ProcessLasso, but not AppData\Roaming\ProcessLasso\config.
It look like after moving the prolasso.ini into config folder, Process Lasso will not backup the prolasso.ini anymore.
Confirm?

[Jeremy Collake]

When updating from older versions the watchdog rules can be lost. Going forward, they will be properly migrated, but that doesn't do anything for users who already lost their watchdog rules during the update.

This loss should be a one time event.

Fortunately, there is a backup of the INI file - which you discovered.

Unfortunately, you need to wait for me to issue an update before the watchdog rules in it are properly migrated. I actually made this change (migration fix) last week, but have not yet released any new build with /this capability. So, v6.7.0.35 beta or above.

When I do upload a new build,  to import your existing rules you need to:

1. Copy any key containing 'Watchdog' (e.g. Watchdog or Watchdog2) from your old INI file to the current INI file
2. *OR* 'import' the old INI file via the Options menu.

Bitsum sincerely apologizes to anyone affected by this.

The pipe setting is no longer used.

[BenYeeHua]

Fortunately, there is a backup of the INI file - which you discovered.

But, it look like the backup INI file don't get update after May, which is the same with OP.
Can it be some bug on the backup system?

[Jeremy Collake]

No, that is not a bug. It is not actually a scheduled backup. It is just left-over from where the configuration file storage location was moved to the 'config' sub-folder. It was backed up there in case something went wrong during that process, or you later downgraded.

[edkiefer]

I seem to have 3 PL.ini files .

1) in C:\Users\Ed\AppData\Roaming\ProcessLasso > prolasso.ini.bak
2) C:\Users\Ed\AppData\Roaming\ProcessLasso\backup > prolasso.ini
3) C:\Users\Ed\AppData\Roaming\ProcessLasso\config > prolasso.ini

the config one is active one .

Maybe one of these should be cleaned up ?

[Jeremy Collake]

I don't know about the backup folder. Maybe you created that, or maybe it was created by an older version.

[edkiefer]

ok, I might of done that, trying to debug stuff .
I know I did add something .

[BenYeeHua]

No, that is not a bug. It is not actually a scheduled backup. It is just left-over from where the configuration file storage location was moved to the 'config' sub-folder. It was backed up there in case something went wrong during that process, or you later downgraded.

Ok, so I wonder did you has any plans to adding a scheduled backup, or just write a bat for it.

[hanemach_gt]

Ok, so I wonder did you has any plans to adding a scheduled backup, or just write a bat for it.

I have already created one my friend.
I don't know if it will work, if it doesn't, I will update it.

https://bitsum.com/forum/index.php/topic,3114.msg12201.html#msg12201

[BenYeeHua]

I guess it will works, as it don't access Program File, which need Admin right.
Maybe next time, after I start using Process Lasso for managing 50+ process, so far I only set 2-3 rules only.