Recent Posts

Pages: 1 ... 8 9 [10]
91
Process Lasso / Re: Question regarding prolasso.ini
« Last post by edkiefer on June 09, 2016, 11:11:33 AM »
How do I set the option to always keep a program running via it?
Not sure why you want to do it this way as setting a process to always running using GUI is much more user friendly (right click on process and use "keep running" option.

But here what I did, set a test process, (I used calc.exe, add it to keep running and then open ini and you see this line.

KeepRunningProcesses=c:\windows\system32\calc.exe;;0

So you can add/change/add any process with path and exe name if you like.
92
Process Lasso / Re: Non-Existent Processes
« Last post by Zero3K on June 09, 2016, 10:58:40 AM »
How about adding an option to automatically close suspended programs?
93
Process Lasso / Question regarding prolasso.ini
« Last post by Zero3K on June 09, 2016, 10:44:13 AM »
How do I set the option to always keep a program running via it?
94
Yes I could see in regedit that the value was incorrect - set to 100 hex instead of decimal. This is actually the first time I've needed to edit the registry on this install of Windows so if the registry has been affected by something before this it wasn't manual tampering.
I noticed it was the specific profile with an issue because i quickly tabbed through all of the other power profiles in there and they all had the correct 100 decimal entry.
Like I say, not saying it's definitely Process Lasso, it's just super strange that it was specifically hex 64 and only affecting the process lasso power profile.
95
I can assure you that it correctly uses decimal and hexadecimal, so I'm thinking what you are seeing is a perceptual or display problem. Thus, how is it you are determining that it's set to only 64 (decimal)?

EDIT: If by RegEdit, please know it displays DWORD values in hexadecimal by default. Also, the failure to be able to set settings in ParkControl may be due to prior manual registry edits. This is something I've been trying to reproduce.
96
I tried the built in one but it said it couldn't set the values when I hit apply.
97
I noticed today that I had some cores parking in a task manager. I was pretty sure I had never set this and I'm pretty sure its off by default in Win 10.

I checked under the Bitsum Highest Performance power profile that 'Processor performance core parking min cores' was set to 64%! Also the range of the entry would only go up to 64% maximum!
I had to edit the registry key at the following location so I could set the value to 100% again.:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\06cadf0e-64ed-448a-8927-ce7bf90eb35d


Potential bug in a recent update? 100 in hex is 64 in decimal so maybe a value was entered as hex by accident when it should not have been.
Not saying it was definitely a process lasso issue, just seems a strange one and I thought I would give you guys a friendly heads up :)
Hi, Thanks for report.

That is not the default values set by Bitsum HP power profile, all CPU management should be 100%.
IMO something had to alter this, have you used any kind of tweaking app, speed up app.

Also please give version you are using, if it was ProcessLasso built in Core Parking or standalone Core Parking.

Thanks, Ed
98
I checked mine on the latest version, and everything is set as it should be.
99
I noticed today that I had some cores parking in a task manager. I was pretty sure I had never set this and I'm pretty sure its off by default in Win 10.

I checked under the Bitsum Highest Performance power profile that 'Processor performance core parking min cores' was set to 64%! Also the range of the entry would only go up to 64% maximum!
I had to edit the registry key at the following location so I could set the value to 100% again.:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\06cadf0e-64ed-448a-8927-ce7bf90eb35d


Potential bug in a recent update? 100 in hex is 64 in decimal so maybe a value was entered as hex by accident when it should not have been.
Not saying it was definitely a process lasso issue, just seems a strange one and I thought I would give you guys a friendly heads up :)
100
Process Lasso / Re: How do I know if Process Lasso is working?
« Last post by edkiefer on June 06, 2016, 12:38:21 PM »
I am not sure if my Process Lasso is working.
Hi  max , that is good question and answer will vary depending on Hardware (system specs) and what app you are running.

I will assume you installed and left it all in default config.
The easy way to tell is look at your log (Action log or log view), you should see some actions going on in your daily activity , but again it will depend on how you use your system and what you have running. In general the more CPU bound (high CPU%) your running apps with more multi-tasking in your work, you see more action in log.
Anyway, look for lines like xxx.exe - Process priority temporarily lowered by Probalance.
You can also just check Insights (button down on action log, it will show most active restraint processes.
There also a lot more to ProcessLasso than just Probalance but that depends on your needs.

The default config settings  is a very good starting point and nothing wrong with leaving it set like that, that is the  preferred setup.
That said, we can maybe give suggestions depending on what you use your system for mainly.
Pages: 1 ... 8 9 [10]