Just an FYI.
I've just realized that updating to Process Lasso v6.0.3.23 beta killed my config.
All my game processes etc went & the power saver settings, no sleep etc all disappeared.
Conclusion - ini eaten :P
I found that re-entering the power savings took 2 tries before they stuck. Coincidence/user error?
Seems allow display but not PC to sleep isn't working.
Did I see a request for a right click function on the above setting? If not, I think it might be useful to have one when selecting active processes in the GUI.
Should have backed up my ini more recently ::) not as if I didn't know it was a beta! :-[
I noticed when backing the ini up just now that if an ini already exists the save process doesn't warn about an overwrite. This might occasionally be a problem for some users, especially as the default write location is the install dir...
Ya, and luckily it is just a beta, just think about what will happen if it is stable version. :o
I the config ini should be backed up in the default path C:\Users\Ed\AppData\Roaming\ProcessLasso\config
One being used right now is in C:\Users\Ed\AppData\Roaming\ProcessLasso . It was copied over when the beta updated .
That said some features are not working right now, at least for me like power profiles .
When I export it goes to ..AppData\Roaming\ProcessLasso
Just found none of my prevent sleep functions are working. :o :'(
"Looks like I picked the wrong week to stop sniffing glue..." - Airplane ;D
Yes, this is something I've noticed and will be resolving. Much work still remains in this rather large update.
Rolled back to Process Lasso v6.0.3.4 & I find my CPU core parking dialog won't hold settings anymore (again) ??? :'(
Not done a clean uninstall/install yet tho - just fiddling :)
Quote from: bertie97 on May 02, 2013, 02:54:23 AM
Rolled back to Process Lasso v6.0.3.4 & I find my CPU core parking dialog won't hold settings anymore (again) ??? :'(
Not done a clean uninstall/install yet tho - just fiddling :)
It might be using a older version of Park-control, try download the newest version from here. :)
http://bitsum.com/about_cpu_core_parking.php
---OT line
And the link at the "Looking for?" is using the old one.
Which is http://bitsum.com/other/about_cpu_core_parking.php
Quote from: bertie97 on May 02, 2013, 02:54:23 AM
Rolled back to Process Lasso v6.0.3.4 & I find my CPU core parking dialog won't hold settings anymore (again) ??? :'(
Not done a clean uninstall/install yet tho - just fiddling :)
Yes, as BenYeeHua says, that is the old, unfixed version of ParkControl. While you patiently wait for me to finish the beta and make it final, again as BenYeeHua says, use the stand-alone version of ParkControl, if you have to.
Quote from: Support on May 02, 2013, 08:08:29 AM
Yes, that is the old, unfixed version of ParkControl. While you patiently wait for me to finish the beta and make it final, use the stand-alone version of ParkControl, if you have to. Once you set the parking settings, most people don't change them again regularly (that's what power profiles are for).
OK I can take the hint :D
I had assumed it was a reversion to the old PC but hadn't had time to cross check the version numbers. Decided to pad out the thread with useless whining instead. ;)
lol, I'm really criticizing myself here. I could/should have more done by now. I do what I can I suppose. It won't be long now, I don't think. Some barriers to productivity the last week have been dealt with and I'm moving forward again.
I'm now on the new beta .25b (thanks for pushing it out) & things are looking a lot better. :)
I did wonder about the number of threads shown in the GUI. I don't normally full-screen the GUI but just after boot today I did & found that whilst 73 process threads were running only about 18 were shown. (If windowed I would have to scroll down a little to see all the 18-20 entries so hadn't actually counted them previously. No 50" monitor yet :()
I seem to recall using PL to track svchost instances in the past but they aren't displayed now. ???
Is this an intentional pruning whose introduction has slipped past me?
Make sure you have "manage processes of all users" enabled in main menu .
Thanks edkiefer, somehow that had switched to an unticked state.
So familiar with it being active I hadn't even thought of that switch... ::)
Quote from: bertie97 on May 03, 2013, 08:48:33 AM
Thanks edkiefer, somehow that had switched to an unticked state.
So familiar with it being active I hadn't even thought of that switch... ::)
That's normal, as we has been asked to set this setting for the first time we start Process Lasso. :)
Quote from: BenYeeHua on May 03, 2013, 01:51:49 PM
That's normal, as we has been asked to set this setting for the first time we start Process Lasso. :)
Right, after you run through installer you get to startup options, in there you get option to set this .
I'm evaluating, resolving, and testing the configuration file migration now, btw.. I'm shooting for a new beta build later today. The existing configuration should never be lost, it will remain in its original path (%APPDATA%\ProcessLasso\prolasso.ini). The new one is in the 'config' subfolder at the same location.
I really can't express how invaluable your (all of you, plus a few more) contributions have been. As you know, there is no staff here other than myself, so your testing and bug reports really make a huge difference.
I normally see all the process activities so I guess when my config went that setting went too. Having not usually had to search for the switch in the menus it has slipped past me on this occasion.
I usually check the Make Process Lasso your System Overlord with absolute powers of life & death over all users box on install... :D
@ Support - Good to know that my/our gripes are useful on occasion :)
Quote from: bertie97 on May 04, 2013, 08:58:19 AM
@ Support - Good to know that my/our gripes are useful on occasion :)
Yes, and this is good, if any product has many weakness, and you don't gripes for that.
Then devs will not know about that, until devs found the weakness and improve/fix it. :)
I'm delayed a bit, which is no real surprise to anyone who knows me. After initially re-factoring the inter-process communication between instance(s) of the governor and instance(s) of the GUI, I decided to just rip that old system out. I never liked it, it's excessively complex. The new system relies on the log to pass most information, except for simple events.
@BenYeeHua: This change will fix the graph tooltip discrepancy that you noted a while back, among other things.
The log entries themselves are being better type defined to facilitate this. It is taking some time to properly define all log entry types and change the code round. Tedious, tedious work since there are so many log types. But, it won't be long.
Quote@BenYeeHua: This change will fix the graph tooltip discrepancy that you noted a while back, among other things.
Great. :D
Remember to put a old "vs" new screenshot/picture, as it is more understandable.(as I forgot about what's issue is that. ;D)
I'll show you. This is version is turning into a monumental chore, though it's needed. The end result of this beta series will be a new major version.
This sounds like an interesting development. Looking forward to trying it...
Even if it does eat my config!
(But really, I know this is unlikely given the mod mentioned above ;D)
Quote from: bertie97 on May 07, 2013, 02:38:04 AM
This sounds like an interesting development. Looking forward to trying it...
Even if it does eat my config!
(But really, I know this is unlikely given the mod mentioned above ;D)
So, did you has started backup the config file? ;D
Quote from: BenYeeHua on May 07, 2013, 05:02:05 AM
So, did you has started backup the config file? ;D
I would not like to advertise myself here, but I use my own solution for Process Lasso INI backup: https://bitsum.com/forum/index.php/topic,3114.0.html
Quote from: hanemach_gt on May 07, 2013, 10:08:05 AM
I would not like to advertise myself here, but I use my own solution for Process Lasso INI backup: https://bitsum.com/forum/index.php/topic,3114.0.html
My config don't change too much(I only enable "manage all processes" for now), backup the config everyday might be useless for me. ;D
I think there's something wrong with the way PL is reading the config settings, or with where it's trying to load them from. It's not saving my settings on exit, or if it hasn't reset them entirely from the last update, it isn't reading the config file properly.
Yes, it has issues with saving .
Last few beta have many changes under the hood and may take some beta's to get there, give it some time .
As the code is finalized and regression tested, there may be cases where the configuration file is lost, especially in beta->beta updates. By the final, the migration from the previous final build will be guaranteed. I recommend you export your configuration file if you need to make sure it's preserved. You can then re-import it. The paths used are shown in the About box, so you can check there to see if they have been set anomalously.
@BYH - yep I did ensure I had a config backup this time :D
@hanemach_gt - I did just try your script, looks like you covered a few bases there. I liked the prefix # that could be really helpful when I'm messing about. ;)
Quote from: bertie97 on May 09, 2013, 03:15:24 AM
@BYH - yep I did ensure I had a config backup this time :D
Good. ;)
I don't see any reason for not being backup a small important config file everyday, except you don't touch it too much, just like me. :)
I am looking at this problem in a test bed, so will be sure it is resolved here shortly. The symptoms are that no configuration changes are saved.
I am merging this issue with a similar thread regarding the loss or inefficacy of the configuration file in the new beta.
What is actually happening in the current beta is that the configuration file is being reset when Process Lasso is restarted (on some systems where an upgrade was performed). It should work properly in v6.0.4.3 beta.
Quote from: Support on May 09, 2013, 01:53:18 PM
What is actually happening in the current beta is that the configuration file is being reset when Process Lasso is restarted (on some systems where an upgrade was performed). It should work properly in v6.0.4.3 beta.
Will test for it after you push that version. :)
The 6.4.0.1b did eat my config during the auto-upgrade today ....but I had a backup ready ;D :P
That build will most likely keep eating it. The migration was broke under some installs, such that it would constantly kill your configuration file when it restarts.
v6.4.0.3 should do better. It's uploading now.
6.4.0.3 seems to be working better . It is saving ini in the config folder .
I am having issue with log setting on power profiles from sticking (its off default, all other logs on)
Edit : the power profiles don't seem to switch either . I don't see the line in the ini to to edit .
Using v6.4.0.3 beta now.
And I found every start of Process Lasso, the Actions Log will showing Action:action 0x3b, which showing More info:Managing processes for user(s):All users.
----
And did you tweak a bit the default setting?
I saw a windows jump up and asking me to restore to ProBalance default, or this is caused by the unsaved config?
Quote from: BenYeeHua on May 09, 2013, 04:40:56 PM
Using v6.4.0.3 beta now.
And I found every start of Process Lasso, the Actions Log will showing Action:action 0x3b, which showing More info:Managing processes for user(s):All users.
----
And did you tweak a bit the default setting?
I saw a windows jump up and asking me to restore to ProBalance default, or this is caused by the unsaved config?
yes, that shows in log when you change managing user in main . think its new log entree that shows on startup
Quote from: edkiefer on May 09, 2013, 04:21:05 PM
I am having issue with log setting on power profiles from sticking (its off default, all other logs on)
Yes, I see the problem with 'Log application power profile change events'. I will correct that. Thanks!
Quote from: edkiefer on May 09, 2013, 04:21:05 PM
Edit : the power profiles don't seem to switch either . I don't see the line in the ini to to edit .
The application power profiles?
Quote from: BenYeeHua on May 09, 2013, 04:40:56 PM
Using v6.4.0.3 beta now.
And I found every start of Process Lasso, the Actions Log will showing Action:action 0x3b, which showing More info:Managing processes for user(s):All users.
That just means there is no string for that action yet. I am slowly adding them, and will disable any that don't have an associated string by final.
Quote from: BenYeeHua on May 09, 2013, 04:40:56 PM
I saw a windows jump up and asking me to restore to ProBalance default, or this is caused by the unsaved config?
It's a leftover from an old change to some defaults. I'm going to kill it, thanks for reminding me!
Thanks!
Quote from: Support on May 09, 2013, 05:07:22 PM
Yes, I see the problem with 'Log application power profile change events'. I will correct that. Thanks!
The application power profiles?
yes app power profile switching . I tested with my default power profile and run game I have it enabled (high performance) and alt-tab and checked no change .
Edit: not sure if this is wrong or right but when I use option , right click on action window "jump to log file on disk" It opens a new explorer process (so you get 2 explorer.exe running) . Closing the folder does bring count back down .
If I open folders normal way 1 explorer can handle all of them .
Quote from: Support on May 09, 2013, 05:09:04 PM
It's a leftover from an old change to some defaults. I'm going to kill it, thanks for reminding me!
Thanks!
This show that, every detail is important to report, it don't care it is less or more important. ;)
Quote from: edkiefer on May 09, 2013, 05:11:18 PM
Edit: not sure if this is wrong or right but when I use option , right click on action window "jump to log file on disk" It opens a new explorer process (so you get 2 explorer.exe running) . Closing the folder does bring count back down .
If I open folders normal way 1 explorer can handle all of them .
It might be windows used for prevent crash, if it launch by other process instead of Explorer.exe?
As I has "Folder options-Launch folder windows in a separate process" ticked, this is normal for me. :)
Quote from: BenYeeHua on May 09, 2013, 06:14:26 PM
This show that, every detail is important to report, it don't care it is less or more important. ;)It might be windows used for prevent crash, if it launch by other process instead of Explorer.exe?
As I has "Folder options-Launch folder windows in a separate process" ticked, this is normal for me. :)
I just checked ,that option is not enabled "Launch folder windows in a separate process"
Like I said if I open multiple folders from my computer I see only 1 explorer process for all folders open .
Its not big deal, I guess he coded it with that flag on .
Quote from: edkiefer on May 09, 2013, 06:27:09 PM
I just checked ,that option is not enabled "Launch folder windows in a separate process"
Like I said if I open multiple folders from my computer I see only 1 explorer process for all folders open .
Its not big deal, I guess he coded it with that flag on .
I think you can try tick/enable it, if you open a folder with many picture/video and scroll with fast speed/one of the video has high bitrate, it(explorer.exe) might be crash by the thumbnailer. ;)
I rather not have multiple processes . I just tried scrolling though my raw images in picture folder, no slow downs or anything .
Maybe if I had all pics in one folder but I have it set it makes a timestamp folder when I DL from camera to picture folder .
OT ::)
Ya, the issues that I facing with Explorer.exe is, the IE has some malware active-x or other thing.
When I open My Computer, it will crash because of that, and I fixed it by running IE(No add-on) and reset it.
And when I open a folder with a high bitrate video, it hang because it want to thumbnail that video, which using maybe one core for that.
----
I just thinking that, what is the difference with "Launch folder windows in a separate process", did it reduce leak just like Chrome?
Or it just want to prevent some crash for the main Explorer.exe? :)
not sure , I guess it can add some stability having more explorer exe run for each folder .
The downside would be added resources used maybe .
Quote from: edkiefer on May 10, 2013, 06:52:11 AM
not sure , I guess it can add some stability having more explorer exe run for each folder .
The downside would be added resources used maybe .
I think yes.
From the Help.
QuoteIncrease the stability of Windows by opening every folder in a separate part of memory. (Use this setting if your PC frequently stops working and you want to minimize or troubleshoot problems. Choosing this setting might slow down your PC.)
It might slow down your PC while the Ram is almost full. ;)
Quote
Edit: not sure if this is wrong or right but when I use option , right click on action window "jump to log file on disk" It opens a new explorer process (so you get 2 explorer.exe running) . Closing the folder does bring count back down .
If I open folders normal way 1 explorer can handle all of them .
That's right, it's a secondary explorer instance. This really isn't a large waste of resources since they share so much of their virtual memory, and regardless is the preferred way to launch the folder view for the time being.
Quote
yes app power profile switching . I tested with my default power profile and run game I have it enabled (high performance) and alt-tab and checked no change .
Is it possible that this was simply a side effect of the failed configuration file? It appears to be working, now at least. I'll issue a new build some time in the next few hours.
Strange power profiles don't work for me . on latest 6.4.0.5beta
The log setting for profiles are enabled .
I have graph open which shows profile . I launch app with HP profile set to switch . I check PL graph and windows with it running and doesn't change from my profile (custom ).
I even removed said app and reentered it .
Ok, checked few things but can't figure out the problem . PL is able to change power profile from main menu if I manually do it , so that part is working fine its just what app I have in the list don't seem to work . I add calculator as test base but can't get it to work .
Game mode works fine .
INI file looks ok , whatever I add shows up in PL root folder ini (not in config folder, that one is not updated and changing it doesn't affect it )
Quote from: edkiefer on May 11, 2013, 08:18:42 AM
Strange power profiles don't work for me . on latest 6.4.0.5beta
The log setting for profiles are enabled .
I have graph open which shows profile . I launch app with HP profile set to switch . I check PL graph and windows with it running and doesn't change from my profile (custom ).
I even removed said app and reentered it .
Don't using that function yet, will test it now.
----
Working here, did you try other default power plans like Powersave, High Performance?
How about other software?
yes, I put it back to balance to see maybe it doesn't like my custom profile but same thing it doesn't change .
You know I noticed few days ago my profile was on high performance by default . maybe it switched and now out of sync . Though I just tried to change it to HP with a HP app running but it didn't switch or change .
I didn't change or add anything that would stop power profiles That I know of .
As I said I can even do it manually from PL menu so PL is able to switch it just for some reason app power profiles not working here .
Edit: uninstalled it went back to last official 6.0.3.4
that didn't work either ,neither did log app power profile .
went back to 6.0.2.8 and power profile switch ok
Did auto-update to beta 6.0.4.5beta
Ok, found issue . in configure app power profile , path method is not working , but if you enter the process name only "calc.exe" it does work . even though path shows correctly in ini .
On issue I am having is log app power profiles is not showing .setting is changing in ini but not showing change in action log window .It is working (changing power profile) .
Also log doesn't show PL info on startup version , company name etc like it used to .
Can you send me your configuration file please? I believe this is the fastest way to figure out what's going on. Thanks!
Quote from: Support on May 11, 2013, 05:38:48 PM
Can you send me your configuration file please? I believe this is the fastest way to figure out what's going on. Thanks!
sent email
in the config I have calc.exe set by path and you notice it doesn't work, no change to power profile.
Thanks for sending the config file!
I must do some testing, but I do see one anomaly, an anomaly that I am programmatically correcting now. That is your Energy Saver configuration is in an invalid state. Whether this is affecting the application power profiles, I can't say for sure at this time.
The errant lines are:
Quote from: prolasso.ini
EnergySaverForceActivePowerProfile=True
EnergySaverUpPowerProfileName=
When EnergySaverForceActivePowerProfile is True, EnergySaverUpPowerProfileName should always be populated. This is the setting that tells Energy Saver to force a particular power profile when the PC is in a non-idle state. However, the power profile name is empty.
Edit:Fixed a small typo. :)
Quote from: Support on May 11, 2013, 06:02:35 PM
Thanks for sending the config file!
I must do some testing, but I do see one anomaly, an anomaly that I am programmatically correcting now. That is your Energy Saver configuration is in an invalid state. Whether this is affecting the application power profiles, I can't say for sure at this time.
The errant lines are:
When EnergySaverForceActivePowerProfile is True, EnergySvaerUpPowerProfileName should always be populated. This is the setting that tells Energy Saver to force a particular power profile when the PC is in a non-idle state. However, the power profile name is empty.
I never added anything to energy saver but I did open it and unchecked the first option and closed it .
So I should have it false in ini "EnergySaverForceActivePowerProfile=True>false
To sumorize with calc.exe as example
Just adding "calc.exe" as process in power profile window it works fine but if I use search path option and get c:\windows\system32\calc.exe as path.
It doesn't work .
And again either if it works or not no action log shows up when it does work .
Right, and, yea, I'm sure it got that way thanks to some badly written code on this end. I am going to work on that.
QuoteJust adding "calc.exe" as process in power profile window it works fine but if I use search path option and get c:\windows\system32\calc.exe as path. And again either if it works or not no action log shows up when it does work .
Thanks, that is probably what I have been missing while skimming these posts. I'll report back soon.
right, I could not figure out how it worked for others but I asked you to add search option so you find exe .
I guess others do it either off process list or entering proper name only .
Log entries:
The log entries were not being emitted due to a logic error in some of the new code. If you *disable* the new log toggle for power profile changes, then they show up. That is now changed, of course.
Failed application power profile when rule uses a pathname
The governor does not properly support application power profiles by pathname. That is why the pathname is failing. I'm adding support for pathnames to the core engine now, so that it matches the GUI's acceptance of them.
Alright, I got it all fixed up in v6.4.0.7 beta. I'm building it now.
Quote from: Support on May 11, 2013, 06:48:45 PM
Log entries:
The log entries were not being emitted due to a logic error in some of the new code. If you *disable* the new log toggle for power profile changes, then they show up. That is now changed, of course.
Failed application power profile when rule uses a pathname
The governor does not properly support application power profiles by pathname. That is why the pathname is failing. I'm adding support for pathnames to the core engine now, so that it matches the GUI's acceptance of them.
Thats funny and I made sure that was on in log setting .
Yup it works with it off .
Cool , I'll test it as soon as out .
PS: I like that PL has all app paths under help>about PL .
more software should do that , some do but many don't .
Ok, 6.4.0.7beta works with app power profiles .
One tiny issue I had . I had calc.exe open when I auto=updated and when PL restarted it did switch to high performance as it should but it go stuck in HP mode even after I closed calculator .after restting profile to my default. then retesting all worked .
Ok, here easy way to test it , set calc.exe as HP, run it now close PL and restart it . you'll see it get stuck on HP mode.
maybe store default power profile mode in ini ?
The log of app power profiles is only showing one log with it enabled or disabled in log setting .
It either shows entering HP mode or shows terminating HP and back to default but never both .
Log app power profile off and shows only termination of HP and back to default .
Log app power profile on and only show starting HP power profile
hope that makes sense .
Quote from: edkiefer on May 11, 2013, 07:44:02 PM
One tiny issue I had . I had calc.exe open when I auto=updated and when PL restarted it did switch to high performance as it should but it go stuck in HP mode even after I closed calculator .after restting profile to my default. then retesting all worked .
Ok, here easy way to test it , set calc.exe as HP, run it now close PL and restart it . you'll see it get stuck on HP mode.
maybe store default power profile mode in ini ?
Yup, this has been reported before. :)
And I think it will affect some people after the silent update is provided, for example, gamer.
Quote from: edkiefer on May 11, 2013, 07:44:02 PM
One tiny issue I had . I had calc.exe open when I auto=updated and when PL restarted it did switch to high performance as it should but it go stuck in HP mode even after I closed calculator .after restting profile to my default. then retesting all worked .
Ok, here easy way to test it , set calc.exe as HP, run it now close PL and restart it . you'll see it get stuck on HP mode.
The issue here is that when the governor closes, it doesn't revert application power profiles for processes that remain running. When Process Lasso is restarted, knowledge of the original power profile it switched from is lost, so it can't be restored when the process terminates. I'm working on a fix now.
Alright, I've adjusted the code, though I do have more I plan to do on this issue.
yes, if it could store last known default i think that may work . that way if it see's a process with power profile it knows what mode it is in .
Good thing I think most app that would be used like this are ones that be full screen ones , games, photo editing, 3dmax that kind of stuff so it shouldn't come up unless auto-update happens in the middle of using the app .
It doesn't bother with storing anything, it instead reverts the changes as it exits. I do have improper termination recovery mechanisms for power profile change events, but I need to work on them with regards to application power profiles.
ok , more i thought about it that could be trouble to if it got out of sync with OS .
You know best, it was just idea that came to mind :)
Edit: tested new beta 6.0.4.9 and it switches properly, even leaving the power profiled app running and closing /restarting PL .
Good, thanks for testing!
The Energy Saver function currently stores the original power profile in the registry for later recovery, in case of improper termination of the governor.
As you suggest, I'll do the same for application power profiles. First I wanted to make sure the proper termination sequence worked correctly, then work on handling improper termination.
Step by step. :D
The additional failsafe is included in v6.4.1.1 beta, a build that is undergoing final regression testing (lots fixed in this build). There are a couple known issues I will tackle during testing, and then I will release. This build further cleans up code and makes portions much more efficient. I am feeling fairly pleased with this release.
that's big list of changes in the change-log . ;D
Yea, it's completely unmanageable. The latest builds added some new things, such as a parent indication in launched processes logs. The build I'm about to upload, which I'm calling rc1 despite not being signed off on a couple more things, adds the export to CSV and more.
I will summarize the changes on final, though don't expect to offer a complete list either way.
Quote from: Support on May 13, 2013, 06:24:09 PM
Yea, it's completely unmanageable. The latest builds added some new things, such as a parent indication in launched processes logs. The build I'm about to upload, which I'm calling rc1 despite not being signed off on a couple more things, adds the export to CSV and more.
I will summarize the changes on final, though don't expect to offer a complete list either way.
Yes, to be honest it so big I lost track of what got fixed each beta to test . Maybe leave the beta build that the fix was fixed, or have timestamp of fix .
Not sure what is best w/o a lot of extra work .
With a one man team it hard to do or your time is spent documenting stuff .
Quote from: edkiefer on May 13, 2013, 06:39:34 PM
Yes, to be honest it so big I lost track of what got fixed each beta to test . Maybe leave the beta build that the fix was fixed, or have timestamp of fix .
Not sure what is best w/o a lot of extra work .
With a one man team it hard to do or your time is spent documenting stuff .
Ya, I lost track in the beta update too.
It can be just like the normal build update, having the separate change log.
---OT line
But, sometimes one man team is better, you don't need to keep too much tracking with other people, don't need to tell him you just changed which part of code, what are you trying to do, why you change that part of code...
And yes, it is just sometimes(rarely), having someone review the code or other thing will make the software better.
So, it depend on many thing, like your communication with your teammate, the target is the same or not etc. :)