This is a quick update, not doing much other than cosmetics. More to come.
Wednesday, 27 April 2011
Monday, 25 April 2011
In this beta I have done several things, but perhaps most importantly enabled the new delay before start of process rule enforcement and a periodic self-restart (in case anyone has a need or ever has a problem that should require such a thing.. it is mostly for betas).
I've got some new configuration dialogs to code, several bugs to fix, then final QA. I am not far from v4.1. Of course, I've said that for a couple months now, but seriously ;)
I've got some new configuration dialogs to code, several bugs to fix, then final QA. I am not far from v4.1. Of course, I've said that for a couple months now, but seriously ;)
Saturday, 23 April 2011
If you Google, you might see an ad like this:
I sure HOPE you did not click the ad for the fictional 'Process Lasso 2011'! The only reason the MyWOT RED icon is RED is due to my report of it there only about an hour ago.
It turns out this site is using hundreds (or thousands) of popular shareware utilities as adwords in an effort to distribute a 376KB trojan of some sort. ALL DOWNLOADS take you to this same file. Please BEWARE! It may take the anti-malware researchers time to catch up to this.
Remember, this is just not Process Lasso that was targeted as an adword, it is almost any shareware you can think of. It then directs you to a generic page that has the name and software description changed to whatever you had searched for. From there you get that 376KB trojan. I've heard its a BHO (browser extension for IE), but do not know as I haven't analyzed it. It likely is, and someone is getting paid for it per install. The thought of somebody getting rich from this is sickening.
Fortunately, it *seems* most likely that this is a simple IE browser extension, which is no good, but could be worse. At least it is *hopefully* easy to get rid of. I can NOT say that for sure though at this time.
UPDATE: This has been reported to Google and others. The ads for hundreds of fake 'products' continues as of 04/25/2011 (now).
I sure HOPE you did not click the ad for the fictional 'Process Lasso 2011'! The only reason the MyWOT RED icon is RED is due to my report of it there only about an hour ago.
It turns out this site is using hundreds (or thousands) of popular shareware utilities as adwords in an effort to distribute a 376KB trojan of some sort. ALL DOWNLOADS take you to this same file. Please BEWARE! It may take the anti-malware researchers time to catch up to this.
Remember, this is just not Process Lasso that was targeted as an adword, it is almost any shareware you can think of. It then directs you to a generic page that has the name and software description changed to whatever you had searched for. From there you get that 376KB trojan. I've heard its a BHO (browser extension for IE), but do not know as I haven't analyzed it. It likely is, and someone is getting paid for it per install. The thought of somebody getting rich from this is sickening.
Fortunately, it *seems* most likely that this is a simple IE browser extension, which is no good, but could be worse. At least it is *hopefully* easy to get rid of. I can NOT say that for sure though at this time.
UPDATE: This has been reported to Google and others. The ads for hundreds of fake 'products' continues as of 04/25/2011 (now).
Friday, 22 April 2011
I am tired of sticking my foot in my mouth, so let's just say this is a new release with some good changes. Not everything is fixed in the beta though, so some will be happy, others disappointed. More betas are going to come rapidly.
I went up a couple versions because I made changes at the last minute.
Many/most reported bugs are NOT YET fixed. I am moving as fast as I can. Please be patient until I get to whichever bug you've reported. Trust me, they are all on a list ;). If I get to 'RC1' and it still isn't fixed, then definitely remind me though ;o.
I went up a couple versions because I made changes at the last minute.
Many/most reported bugs are NOT YET fixed. I am moving as fast as I can. Please be patient until I get to whichever bug you've reported. Trust me, they are all on a list ;). If I get to 'RC1' and it still isn't fixed, then definitely remind me though ;o.
Wednesday, 20 April 2011
During QA it was noticed that the startup configuration wasn't being 'preserved' the and set for you the next time you did a manual install or update of the product (new automated updates are not affected). This fix allows proper discovery of the existing settings, even if you have manually changed them outside of Process Lasso (in other words it goes and looks and doesn't rely on some application registry setting). This little snafu actually exist in the last stable/final as well, though it isn't a huge deal. Since I am so close to v4.1, a backport probably will not occur.
Now onward to two very important beta edition bug fixes...
Now onward to two very important beta edition bug fixes...
Friday, 15 April 2011
I don't know about you, but I like to run my stuff in High Performance mode when I'm using it. When I'm not using it, I prefer to run it in lesser power schemes. Process Lasso has long supported the ability to do this by inducing High Performance mode when select processes are open.
In this new beta series support of 'default power schemes' (when a certain program is running switch to scheme X and revert when it closes) has been extended to support any power scheme you choose. There are lots of OEM created specific power schemes, which really aren't anything but fancier named system power schemes. Regardless, you can now use these and user defined power schemes. Honestly, on most systems you really need only the 3 default schemes, which can be tweaked to your liking in the Power Options where you'll find a plethora of settings for every piece of hardware installed. Renaming by OEMs is just a gimmick, with the most absurd named power schemes (like SuperDuperUperPerformance and PowerSaveLikeYourMommaWouldWant).
Forgetting those absurd names and going back to the 3 Windows default schemes, you may ask: Why not just use Balanced or Power Saver (or their equivalents) all the time? Well, that power saving has a price. Even though your CPU and other hardware 'scales up' based on demand, it takes TIME for it to scale up. So, you have a performance hit in anything but High Performance mode, no way around it.
Give the new beta a try (at your own risk, recognizing it is a beta) and experiment if you want. I believe it is approaching a good stable state. At this point I anticipate the new final to come next week sometime. I've still got to file my taxes, which ironically has caused me to get more work done (nothing will motivate you to want to do something else like filing taxes will, lol).
In this new beta series support of 'default power schemes' (when a certain program is running switch to scheme X and revert when it closes) has been extended to support any power scheme you choose. There are lots of OEM created specific power schemes, which really aren't anything but fancier named system power schemes. Regardless, you can now use these and user defined power schemes. Honestly, on most systems you really need only the 3 default schemes, which can be tweaked to your liking in the Power Options where you'll find a plethora of settings for every piece of hardware installed. Renaming by OEMs is just a gimmick, with the most absurd named power schemes (like SuperDuperUperPerformance and PowerSaveLikeYourMommaWouldWant).
Forgetting those absurd names and going back to the 3 Windows default schemes, you may ask: Why not just use Balanced or Power Saver (or their equivalents) all the time? Well, that power saving has a price. Even though your CPU and other hardware 'scales up' based on demand, it takes TIME for it to scale up. So, you have a performance hit in anything but High Performance mode, no way around it.
Give the new beta a try (at your own risk, recognizing it is a beta) and experiment if you want. I believe it is approaching a good stable state. At this point I anticipate the new final to come next week sometime. I've still got to file my taxes, which ironically has caused me to get more work done (nothing will motivate you to want to do something else like filing taxes will, lol).
Thursday, 14 April 2011
As users may know, when selecting multiple processes at once the menu is a bit different. I had not yet added support for I/O priorities (current and default) to the multi-process selection. That is now done. It will be in the next beta.
As a side note, the Help menu will back on the far right, instead of Updates menu (I had a user email me, and he's right it is very non-standard how I have it).
The updater in the last beta or two truncates some text, so that is also fixed in this next beta.
This new beta has been issued as v4.09.37 beta. Another one is likely coming quickly. I am not far from final.
As a side note, the Help menu will back on the far right, instead of Updates menu (I had a user email me, and he's right it is very non-standard how I have it).
The updater in the last beta or two truncates some text, so that is also fixed in this next beta.
This new beta has been issued as v4.09.37 beta. Another one is likely coming quickly. I am not far from final.
Wednesday, 13 April 2011
In the next beta the Keep Running (auto-restart) feature will have a 5 second delay instead of 2 second delay. The delay can be extended by lengthening the refresh rate, if needed. If a specific option needs to be created to set the delay time, I will create it. Users reported to me that some processes, during their own update and self-restart procedures may be interfered with. Even at 5 seconds this is still a definite possibility, so I'm guessing we'll end up with a new setting here (heck, got a setting for everything else, might as well ;p).
(separate topic)
NIS 2011 users:
Users of Norton Internet Security 2011 are advised to go ahead and update to the latest beta IF they are willing to take the risk of running a beta. The newer beta works better with the DeepGuard application.
(separate topic)
NIS 2011 users:
Users of Norton Internet Security 2011 are advised to go ahead and update to the latest beta IF they are willing to take the risk of running a beta. The newer beta works better with the DeepGuard application.
In an effort to keep the best build out there, I'm releasing a new beta. There's much more work to do, but many things have been taken care of. I'm cleaning up several portions. While I've developed a great new secret game plan for the future of Process Lasso, first I must finish up the existing version ;). This new beta is coming shortly. For the gamers: Yes, this beta does fix auto gaming mode.
Saturday, 9 April 2011
This build fixes the self-restart capability, which broke a few betas ago, at an inopportune time. I just now got around to fixing it. The logic in Vista+ needed changing, as the 'Manage processes of other users' option has a correlation with the elevation or not (impossible to do without elevation unless UAC disabled). Anyway, now upon changing the Manage processes of other users variable it will ask if you want to do it once, or forever. If forever, then it will permanently change the Elevation option as well. Most importantly, now the self-restart actually restarts again!! How embarrassing that I let this persist even in a BETA.
Several other small changes and fixes were made. Many more to go...
Several other small changes and fixes were made. Many more to go...
Friday, 8 April 2011
As my intuition told me, the memory leak was indeed within the new process icon code. I have reverted back to the old mechanism, which also fixes other icon problems that some people report. I'll switch to the new, more efficient, system as soon as it works completely. It is more complex, but faster and uses less virtual memory (when operating right).
Other fixes are small, but I wanted to get the ball rolling again. More fixes coming. A known bug is in the self-restart feature under some scenarios, which I'm working on.
Other fixes are small, but I wanted to get the ball rolling again. More fixes coming. A known bug is in the self-restart feature under some scenarios, which I'm working on.
Subscribe to:
Posts (Atom)