Process Lasso v5.1.0.27 final

v5.1.0.27 final

Downloads:

Workstation/Home/Standard:
32-bit: http://www.bitsum.com/files/prolasso.zip
64-bit: http://www.bitsum.com/files/prolasso64.zip

Server Edition:
32-bit: http://www.bitsum.com/files/server/prolasso.zip
64-bit: http://www.bitsum.com/files/server/prolasso64.zip

Changes:

• [.27]Fix.GUI: Fixed failure in unchecking process watchdog rules via the context menu.
• [.27]Fix.GUI: Fixed disabled 'Change CPU affinity during restraint' ProBalance menu option
• [.27]Fix.Core: Fixed theoretical issue where certain services could be lowered in priority class by ProBalance even if services were set to be excluded (the default)
• [.27]Change.Core: First step of a series of ProBalance adjustments planned (incrementally being phased in for maximal safety)
• [.27]Addition.Core: Added 'any' memory metric for watchdog options
• [.27]Addition.GUI: Added UI (dialog) support for 'any' memory metric for memory watchdog actions
• [.27]Addition.GUI: Added new mechanism to check to see if you are using the latest recommended defaults (only asks once per change of the defaults, unless you tick 'do not ask me again')
• [.27]Change.GUI: New process watchdog memory rules now are created with default of 'Any Metric'
• [.27]Change.All: Adjusted ProBalance defaults for better system-specific auto-tuning
• [.27]Change.GUI: Several languages updated

Read More

ASUS Motherboard Utilities Self-Lower in Priority

I was updating my ASUS motherboard's included software suite of useful and useless utilities, and found that they all behaved 'nicely'. What I mean is that the resident (always running) ones lowered their priority class to Below Normal when not active. Yes, very reminiscent of Process Lasso's ProBalance. Could it be, that ProBalance is affecting the design decisions developers make? It is possible. After all, Google set the example in Chrome, with it lowering the priority class of its forked processes (tabs).

If more software made a conscious effort to set its own process priority class and/or individual thread priorities, then perhaps the PC would be a better environment. That is why Process Lasso ignores (by default) processes with non-normal priority classes. It assumes they have been adjusted by the program itself, the user, or a third-party application and so shouldn't be changed. Thread priorities, of course, remain relative to the process priority class, thus their relation to each other is not changed when the priority class is adjusted.

Read More

Process Lasso v5.1.0.26 final

v5.1.0.26 final

Downloads:

Workstation/Home/Standard:
32-bit: http://www.bitsum.com/files/prolasso.zip
64-bit: http://www.bitsum.com/files/prolasso64.zip

Server Edition:
32-bit: http://www.bitsum.com/files/server/prolasso.zip
64-bit: http://www.bitsum.com/files/server/prolasso64.zip

Changes:

• [.26]Change.GUI: New German graph legend
• [.26]Change.GUI: German out of date warning removed
• [.26]Change.GUI: Russian out of date warning removed (an oversight, as it was/is up to date)
• [.26]Change.GUI: Updated Traditional Chinese
• [.26]Change.GUI: Updated Italian
• [.26]Change.GUI: Updated Polish
• [.26]Change.GUI: Updated Finnish
• [.26]Change.Core: Default ProBalance parameters tweaked a little for higher end systems (more mods under testing)

Read More

Process Lasso v5.1.0.25 final

v5.1.0.25 final

Downloads:

Workstation/Home/Standard:
32-bit: http://www.bitsum.com/files/prolasso.zip
64-bit: http://www.bitsum.com/files/prolasso64.zip

Server Edition:
32-bit: http://www.bitsum.com/files/server/prolasso.zip
64-bit: http://www.bitsum.com/files/server/prolasso64.zip

Changes:

• [.23]Fix.GUI: Fixed issue with the some metrics of tamper protected security products being shown incorrectly - though most are unavailable
• [.23]Fix.GUI: Fixed issue with tamper protected processes being listed in the Active Processes list
• [.23]Change.GUI: Gray out Vista Multimedia Scheduler menu option in XP
• [.23]Change.GUI: Graph is hidden by default in NT5 or below, unless user preference overrides (reset this version only)
• [.23]Change.GUI: Improved code efficiency related to avoidance of tamper protection processes
• [.23]Change.GUI: Updated German
• [.24]Change.Core: Improved important code that has implications throughout, boosting performance and thread safety both in many places
• [.24]Change.Core: Decreased CPU consumption of core engine
• [.24]Change.GUI: Minor string adjustments
• [.24]Change.All: Refactored some internal code to improve performance
• [.24]Change.GUI: Several language updates
• [.25]Fix.All: Fix small activation state problem in .24 that lasted a few hours

Read More

Bitsum Technologies on Google+

I am often posting to Google+ these days, under our new business profile there. You can access it here: https://plus.google.com/111452122533164797807/posts

Read More

Introducing Energy Saver - new electricity saving feature

Process Lasso v5.1.0.7 beta released with new electricity saving feature

This build is likely to be followed quickly, so I did not make a big deal of its release. However, in this new version I did complete an exciting new feature that can conserve electricity for those who demand the highest performance. In this build it was called 'Power Saver', but in future builds it will be called 'Energy Saver'. Basically, this allows you to keep your PC in High Performance (or whatever power profile), but then drop it back down when you go Idle. When you return, your previous power scheme is restored.

All Power Profiles, including custom ones, are supported. As with other Power Profile features of Process Lasso, this is only for Vista+, as Microsoft re-factored the code for power profiles in Vista and I've not yet added support for the now deprecated XP Power Schemes. Remember, this is in beta testing.

http://bitsum.com/prolasso.php

Read More

Process Lasso v5.1.0.6 beta

v5.1.0.6 beta

Since previous beta changes weren't listed here, I'll list them along with the current version changes. Much more work is ongoing behind the scenes. You will see very soon. We've improved our QA further with more unit tests, automating the process of regression testing more of our code.

Downloads:

Workstation:
32-bit: http://www.bitsum.com/files/beta/prolasso.zip
64-bit: http://www.bitsum.com/filesbeta//prolasso64.zip

Server:
32-bit: http://www.bitsum.com/files/server/beta/prolasso.zip
64-bit: http://www.bitsum.com/files/server/beta/prolasso64.zip


Changes:

• [.0]Change.GUI: Changed startup code to avoid condition where solication dialog may become hidden, and prevent Lasso from starting
• [.0]Change.Core/GUI: Add Symantec (Norton and other) and F-Protect processes with tamper protection back to the list *without* triggering tamper protection events (in testing)
• [.0]Much more work underway, being phased into this build
• [.2]Fix.GUI: Fixed I/O priorities of multi-selection process context menu not grayed out in XP
• [.2]Fix.GUI: Fixed sort of process restraint history column **RE-EVAL
• [.2]Change.InstallHelper: Early prep for DSN support
• [.2]Change.All: Added Japanese to International Server Edition (via Nettool affiliate)
• [.2]Change.GUI: Updated Serbian, Polish, Italian.
• [.4]Change.GUI: Improved cosmetics and behavior of new items in InstallHelper config dialog 2
• [.4](hackported in .51) Fix.Core: Theoretical code error condition, unknown if ever manifested in real world
• [.4](backported in .51) Fix.Core: Adjusted sharing permissions on .pg-active, a filesystem based locak the governor uses, and an issuing for some backup and imaging software
• [.4]Build.System: Misc adjustments throughout
• [.5]Change.GUI: Re-arranged Options menu in a big way, with subcategories and such
• [.5]Change.Core: Some code optimization and refactoring
• [.5]Fix.Core: Minor code fixes and refactoring
• [.5]Change.GUI: Added new message for sanity check failure
• [.6]Addition.GUI: Finished Categorization of Media Player support in GUI
• [.6]Addition.BuildTools: Modified our in-house translation tools to allow use of the deprecated strings file if no translated string is in the primary file
• [.6]Fix.InstallHelper: [beta2beta] Fixed, during update when using global paths, 'use global path' option radio box could be set along with conflicting one (no functional problem)
• [.6]Change.GUI: Several misc cosmetic changes
• [.6]Change.Core: [beta2beta] Experimental code speed improvements
• [.6]Change.GUI: Some code optimizations
• [.6]Fix.Updater: [beta2beta] Fixed issue with new Server betas not being properly uploaded in some cases

Read More

Process Lasso v5.0.0.49

This is a general maintenance release that fixes and improves a few items.

Downloads

Workstation:
32-bit: http://www.bitsum.com/files/prolasso.zip
64-bit: http://www.bitsum.com/files/prolasso64.zip
Server:
32-bit: http://www.bitsum.com/files/server/prolasso.zip
64-bit: http://www.bitsum.com/files/server/prolasso64.zip

Changes:

• [.49]Fix.Core: Automatically terminate newly configured disallowed processes, don't wait for next attempted launch to start enforcement
• [.49]Fix.GUI: Fixed context menu not popping up in the Active Processes tab in some cases (started last minor build)
• [.49]Fix.GUI: Fixed double click on process in Active Tab not taking you to corresponding process in All Processes tab (started last minor build)
• [.49]Change.GUI: Japanese included in international server Edition
• [.49]Change.Core: Internal code refactoring on hard coded exclusion list (which user can selectively over-ride)
• [.49]Change.Core: Further improved NIS2012 compatibiilty
• [.49]Addition.GUI: Added more Server Edition indications in About box of Server Edition
• [.49]Addition.GUI: Added 64 to About box of 64-bit build
• [.49]Change.Docs: Updated docss

Read More

Process Lasso v5.0.0.48

Changes:

• [.48]Change.GUI: Do not show 'Activate Now' menu item after activation
• [.48]Change.GUI: Adjusted logging thread CPU and I/O priorities, which may improve fluidity of Process Lasso and its core engine during high storage I/O loads
• [.48]Change.GUI: Some code speed optimizations
• [.48]Change.GUI: Addressed discrepency between 'K' and 'KB' being used in the all and active process listviews, respectively
• [.48]Change.GUI: Re-arranged active process listview column default positions
• [.48]Change.GUI: Adjusted handling of more known applications for better default behavior
• [.48]Change.GUI: Better integration with Symantec Endpoint Protection
• [.48]Fix.GUI: Fixed instant update of CPU % graphs when Active Processes sorted by CPU use
• [.48]Fix.GUI: Fixed sorting issues in the Active Processes listview (only) - sort of memory metrics and priorities
• [.48]Fix.GUI: Fixed sort of CPU % graphs in Active Processes listview (a)
• [.48]Fix.GUI: Fixed instant update of embedded CPU % graphs when Active Processes listview scrolls (b)

Read More

Windows 8

First, I have a minor maintenance release coming later today. This just fixes a few small cosmetic issues in the GUI, as well as a few other little tweaks and fixes.

Second, Process Lasso has been fully tested with Windows 8 (preview release). It works fine. Of course, Process Lasso's functions are as needed as ever, nothing has changed - nor has anything Process Lasso offers now integrated into the OS.

The Windows 8 OS itself is... different ... designed for touch input while maintaining mouse and keyboard support. If you haven't seen it, it's quite the change. The OS itself is difficult (for me) to navigate with a mouse. However, the Windows 7 style interface is mostly still around, though many OS components have been changed to accommodate touch input.

The Metro UI isn't something you can show with screenshots. The lock screen has to be 'slid' like a phone or tablet. Notifications and some panes are large, mono-color windows with big text. The mouse acts more like a 'finger' would in many areas, dragging things around. Then of course there are the tiles, which take some getting used to.

For those who are curious, here is a glimpse of what the Windows 8 Task Scheduler looks like. If the only changes were UI revamps like this, Windows 8 would be great, hands down. However, marrying touch and traditional input is still far from perfect, so I can't give the whole endeavor a thumbs up yet. It will be nice for Microsoft to have a unified OS that is touch friendly, but the marriage of the two input methods seems far from perfect in this early preview -- in my humble opinion. It will likely improve before final release.

This is the first major change to the Windows Task Scheduler in years. Of course, the Resource Monitor was introduced in Vista, but the Task Scheduler remained largely the same. Here, it is completely rewritten - intended for readability and usability on tablets and other touch screens. Notice how the listview headers are large and clickable. The text is also in multiple font sizes for easier visibility (more so seen on the other pages). It sure does use a lot more RAM though, as shown here -- more than 4x that of Process Lasso's GUI! The memory utilization shown here is the private working set.

Read More

Process Lasso v5.0.0.47 released

Yes, already ;). This version was pushed on out because I discovered a slow memory leak in the core engine when Process Lasso was in the presence of certain processes that had special handling. The cause was one of my more advanced code optimizations. The governor's safety mechanisms would have eventually induced a self-restart of the governor, but obviously a memory leak is a critical issue that mandated an immediate fix. It is recommended all users update to this new version, whether affected by the bug or not.

Read More

Process Lasso v5.0.0.46 released

This release fixes a memory leak seen *only* in Windows 2K/XP with Terminal Services disabled. The cause was a bug in Windows 2K/XP that Microsoft never fixed. It only affected systems where Terminal Services is disabled, something Process Lasso would have warned about repeatedly, and a non-default system state (something the user had to change). On affected systems, the governor's sanity checks would have periodically induced a self-restart before memory use became a large concern. This release also does other minor maintenance, including populating the update dialog with your activation code for easy license validation (registered users only), and waiting for TS or RDS to fully initialize at startup, when appropriate and able.

Downloads
Workstation:
32-bit: http://www.bitsum.com/files/prolasso.zip
64-bit: http://www.bitsum.com/files/prolasso64.zip
Server:
32-bit: http://www.bitsum.com/files/server/prolasso.zip
64-bit: http://www.bitsum.com/files/server/prolasso64.zip

Changes:

• [.46]Addition.All: At startup, wait for Terminal Services (or RDS in Vista+) to fully initialize (with timeout), unless service disabled
• [.46]Addition.Core: Added to default exclusion list
• [.46]Fix.Core: Fixed rare, slow memory leak seen *only* in XP or 2K installs with Terminal Services disabled. This turned out to be a known memory leak/bug in a Windows TS API that was not fixed until Vista.
• [.46]Fix.GUI: Fixed cosmetic error that appeared in .44 in InstallHelper config dialog #2 (extraneous static group controls)
• [.46]Fix.All: Fixed error message 'error cleaning up global config folder' for some older installs that still used prosuper.ini as config filename (instead of newer prolasso.ini)
• [.46]Change.GUI: Licensed update dialog now automatically populates activation code, for easy optional validation of your license prior to update (for updates after this one)
• [.46]Change.GUI: Improved handling of potential error condition where corrupt listview column settings could cause an empty listview (no columsn are shown)
• [.46]Change.GUI: Language updates

Read More

Licensed user update dialog - Activation code will be automatically populated in license validation box

Licensed User Update Dialog 
- Activation code will be automatically populated in license validation box

First, to be clear, the license validation shown upon update notification is optional. If you know when your license will expire (if ever), don't worry about it. The fact that it is optional was not clearly shown though, so many took it as mandatory, or were truly concerned that their license is about to expire. Either way, they went to the tedious trouble of finding and entering their key every update. I apologize for that!

This dialog is now auto-populated with the license activation code. Checking your license to ensure you are still able to get updates will be a one-click, or perhaps zero-click, option from now on.

This change will be in v5.0.0.46. However, you will not see it until the first update after that. Until then, remember, it is optional.

Of course, for lifetime users, ignore all this.

Read More

v5.0.0.44 released

This update adds support for UNC paths of global configuration and log folders, and improves unattended (silent) install support.

• [.44]Addition.All: UNC pathname support for global configuration and log folders, BUT use of these incur a performance penalty in the GUI (to be improved in subsequent updates). The core engine is mostly fine, though logging may want to be tuned down if network I/O is an issue.
• [.44]Addition.InstallHelper: Recursively create given global configuration folder and any necessary parent folders if it does not exist (as manually typed in configuration dialog, or given as a command line parameter during unattended installation)
• [.44]Addition.InstallHelper: Recursively create given global log folder and any necessary parent folders if it does not exist (as manually typed in configuration dialog, or given in command line)
• [.44]Addition.InstallHelper: More robust and expanded auto-cleanup of situation where prolasso.ini was embedded in a redundent subdirectory by the same name
• [.44]Addition.InstallHelper: Added new command line parameter /key for unattended installs
• [.44]Addition.InstallHelper: Provide more descriptive errors on unattended/silent install
• [.44]Addition.InstallHelper: Abort with error code 3 on critical config import errors
• [.44]Addition.InstallHelper: Abort with error code 4 with failure to create specified or default folder(s)
• [.44]Addition.InstallHelper: Abort with error code 5 with failure to create necessary registry key(s)
• [.44]Change.Logging: If specified global log folder does not exist, it is created along with any necessary parent folders
• [.44]Fix.InstallHelper: Improvements and fixes to /importconfigfrom command line switch
• [.44]Fix.InstallHelper: Fix bug where 'prolasso.ini' could be created as an unnecessary subdirectory, with prolasso.ini stored inside
• [.44]Fix.Licensing: Adjusted activation key code for server edition
• [.44]Fix.All: Fixed improper handling of empty global configuration path
• [.44]Docs.Update: Fixed poor sizing in Docs index
• [.44]Docs.Update: Updated command line options page

Read More

Process Lasso v5.0.0.42

Minor release. See http://bitsum.net/forum/index.php/topic,761.msg4158.html#new  More coming. Less time rambling, more time coding. Lots going on.

Read More

v5.0.0.41 released

This build makes the aforementioned graph tooltip size change. The next build has more extensive changes and improvements. The cosmetic quirks I've mentioned before I'm finally cleaning up, as well as continuing advancement in many other areas. This next build will be at least a week away though ;o. I wanted to issue one last minor update before I was forced to take a break due to the burdens of marriage ;p.

Read More

Dynamic sized graph tooltips

I should have done this long ago, but here it is now .. for what it is worth. It took just a few minutes to do. One of those things that I hit myself over the head and say -- why didn't I get to this before? What am I speaking of? Dynamic sized graph tooltips. Yep, no more one size fits all.

This is coming in an update I'm publishing shortly.

Read More

Update

I must apologize for 'losing it' when I found, despite my moral objections to toolbar bundles, my primary mirror had done this for me -- and was profiting off my free users. It is even more insulting when you consider I pay CNET $9 a month per listing, to keep my software mirrored and ... well, actually I'm not sure what I pay that for.

One of the sad things is how this will further hurt proliferation of Process Lasso. By directing new users to CNET, I was increasing the download count there. I wouldn't care much about CNET, but in their close cooperation with Microsoft, their downloads are used as the basis for the little known Windows MarketPlace... a software store for Windows that never really caught on, except maybe in the mobile space, for the few people who have Windows Mobile phones. Still, I prefer to be listed there, and have the 'standing' that comes with having a Download.com listing.

Anyway, it seems the general consensus of users is that they don't mind toolbar bundles. It has become a norm. I'm still not doing it, but the fact is that it is the norm. I believe this should change, for the good of the entire industry.

An ethical software framework should be developed, outlining what should and should not be done. It should ban deceptive practices. It should mandate clean uninstalls. There is nobody to enforce this though, and this is hardly the only area of our society that is rife with ethical violations.

In the meantime, despite my whining, my primary objective must be improving my software. Towards that end, I do have a new and more polished RegMerge on the way, along with another update to Process Lasso (may be a week on it though). I have definite plans, and know what I need to do.

Wish me luck ;). As always, I thank all those who use my software, and especially those who like it enough to buy a license. Even if you haven't bought a license, you are still a friend to me, and do be sure to put those annoying trolls in their place when you see them on reviews ;p. I've gotten to where I just can't read reviews anymore, I take them too personally. The last time I did read them though there were the typical trollish comments you'd expect on the internet. I am confident no matter what anyone does, no matter how perfect, there will always be critics... so, I don't let it bother me much.

Read More

CNET Download.com adds 'Download Installer' with bundled app

CNET Download.com added their own 'Download Installer' which has the BING Toolbar bundled with it. I noticed this today. It couldn't have been like this long. I was using them for my primary mirror, as they never pulled this before. I apologize to all users, I had no idea they made this change. I no longer direct users to their site for a download. Needless to say, all this 'Download Installer' does is wrap around whatever you are getting to give you the chance to get their wonderful toolbar, or free scanner, or whatever deal of the month they are bundling. This USED to be against their policies for listings at download.com.

Microsoft must really be throwing some money around to get this BING toolbar out there. I've heard they've thrown it out as a Windows Update even. Desperation.


UPDATE: This started about 1 month ago, apparently: https://upload.cnet.com/8301-21_5-20084419-9978525.html?part=rss&tag=feed&subj=DownloadProductReview

Read More

Process Lasso v5.0.0.40

Yes, v5.0.0.39 lasted about 12 hours ;o. During my maintenance I had adjusted some code to use a newer version of a function related to checking if a process was suspended. Sadly, this code had a typo (no 'NOT' in an expression), causing a bug that caused all processes to be listed as 'suspended'. This was highly frustrating to see this, but it is now fixed in v5.0.0.40. It just goes to prove, once again, that ANY change, no matter how minor requires regression testing.

I have some distractions coming up next week that won't allow for extensive work for a period of a few days. However, before then, I hope to get a few things done. There are a few little quirks I want to fix in the existing build, and there's also a second demo I want to release. I've had it in mind for a long time. I'll reveal more soon.

Thanks to all those who continue to support Process Lasso. I've heard a lot of complaints about the nags lately, so I decreased the frequency of ones that randomly show up when you open the main window. They are still there, but very rare now. People should remember, most 'freeware' these days stoops to bundling with toolbars. I don't think the nags are that annoying, you can click right by them. They don't have a timer, no pause. It isn't that bad. If it *is* that bad, you can always buy a license and help support development. After all, here at Bitsum I'm not just working on Process Lasso, I'm constantly creating little freeware tools like the new RegMerge utility to safely import or compare REG files. This freeware work, in addition to the constant work on Process Lasso, is made possible by those who purchase licenses of Process Lasso or PECompact, or make donations.

This capitalist world we live in seems to reward those who will stoop to any level to make a buck. Freeware authors are selling their soul everywhere, including toolbars in their software. If people can not accept that software development requires financial support, then this trend will continue. I personally believe that users should boycott all those who bundle toolbars or other apps. Even if you can deselect it at install time, this policy is simply atrocious. When you download a piece of software, you are wanting THAT software, not that software and 10 little friends to go with it.

I'm no saint, and far from perfect, but even if you can't support companies like Bitsum who refuse to participate in this toolbar bundle insanity, at least don't criticize us for daring to have a non-timed nag in our software that you can click right past. If a single click is that bothersome, buy a license ;).

I know, I know ... the thought of paying for software seems outrageous. If you feel I charge too much, you tell me what price you would pay. My experience thus far has shown that those willing to buy a license will pay a *fair* price. Those not willing to pay for a license will not pay a single dollar. Is this correct? If there's some price I could set to get a lot more people to buy a license, I'd certainly do it. If every user bought it for just $5, I'd be doing great.... if I set the price to $5, would YOU buy it?

Read More

Process Lasso v5.0.0.39

I get tired of posting duplicate content, so please see: http://bitsum.net/forum/index.php/topic,761.msg4059.html#new

Use the nifty RSS feed in your favorite news reader for the easiest way to monitor updates.

From here there are two tracks. One makes more incremental additions and improvements. The other branches to a new beta series with all the larger changes I'm constantly exciting myself about ;).

Now, back to RegMerge for a minute so I can finalize it. It's been quietly released as an early alpha for a while now. A few more things and it'll be good enough to call beta.

Read More

Minor maintenance release this week

I have another maintenance release that continues polishing and improving version 5. This one takes care of some long standing quirks in the GUI and elsewhere. I'll be releasing it some time this week. It could be any day really, though I have a few more reported bugs to investigate before I can release it.

Read More

Exciting new works on the horizon

I have some large changes in Process Lasso under development. I can't reveal them just yet, but I will soon. You're going to see - finally - some exciting new shifts in the product. Now, don't get too excited, this is just addressing some the largest 'issues' with the product - as I see them. Afterwards, there are still a plethora of features and improvements to work on.

Read More

Process Lasso v5.0.0.38

Downloads:

32-bit: http://www.bitsum.com/files/prolasso.zip
64-bit: http://www.bitsum.com/files/prolasso64.zip

Changes:

• [.38]Fix.GUI: Fixed 'CPU %' field on process tooltip in XP/2K
• [.38]Fix.GUI: Fixed Private Memory field in process tooltip in XP
• [.38]Fix.GUI: Fixed 'Manage processes of all users' Terminal Services disabled warning in XP errantly asking a question of the user to re-enable, when no such option was available
• [.38]Fix.Localization: The three-letter word 'Day' was not being localized correctly
• [.38]Addition.Core: Added safety catch for possible unusual error conditions
• [.38]Change.Core: Minor code optimizations
• [.38]Change.GUI: Dialog adjustments for some longer languages
• [.38]Change.GUI: Use dynamic unique ID for system tray icon to address a theoretical race condition in the creation of a new instance after an old instance remained active in an abnormal error condition long enough to prevent creation of the new system tray icon
• [.38]Change.GUI: Process Lasso system tray identifer is now variable between instances, an issue that could have caused problems during certain timing when two copies of the GUI were launched at approximately the same time
• [.38]Change.BuildEnv: Removed unnecessary and deprecated build configurations
• [.38]Addition.Activator: Added version resource to provide description of EXE and more

Read More

Running Process Lasso w/o Terminal Services enabled?

Although the product warns about this repeatedly, I am going to issue a more strong extra warning: Please turn on Terminal Services when using Process Lasso. This services is enabled (Manual start) by default in Windows, does no harm, is necessary for 'Fast user switching', has low overhead, and generally just needs to be enabled. The only users who have it disabled are those who have tweaked their systems with special utilities.

The side-effects of not having it enabled are simply growing increasingly problematic to handle, and I'm uncomfortable with them. Process Lasso already operates with the bare minimum, not mandating Performance Counters like most similar programs.

If Process Lasso has not warned you about this (repeatedly), then it is NOT an issue for you -- so no need to go and check. For Vista+, Terminal Services was renamed to Remote Desktop Services and always going to be available, so shouldn't be an issue.

What's up with this? Well, Terminal Services (now Remote Desktop Services) provides the facility for multiple users to be logged in at once. In Vista+, system services are isolated into a special user session, which is why this service will always be on - it MUST be to facilitate this system service isolation. Process Lasso is designed to work with multiple users, and needs to be able to identify the session and user name. Having to continually add exceptions in cases where the user name can not be retrieved is bothersome, though I do continue to do this, and regression test in environments without Terminal Services enabled.

Read More

New Process Lasso being finished up (probably today)

There were some minor fixes and adjustments that were supposed to be in the last minor update, but got reverted. I had some 'issues' and had done a 'full revert' to a previous day and lost many of them. These little (cosmetic) changes will be in this next minor update, along with some other improvements to handle a few rare error conditions better.

I'm also trying to finish up this new little freeware project for the world. It will be very useful to everyone. Zero revenue, but... helpful ;). Process Lasso remains my top priority, so I can only do the freeware stuff in my spare time, which is why it has taken so long. One more stride and I think I'll have it done too.

UPDATE: Delayed a couple more days as there are still items on the todo list and no compelling reason to issue this update yet. This should be a relief to those who struggle to keep up with the updates anyway. I told you things would slow down once v5 was polished a bit.

Read More

Need a 'Pause' button? Here's a trick until we add it

A 'pause' button is coming in the next beta series, but until then a trick to use is to sort by creation time. This is also useful to see what new processes have been created, and when. A lot of advanced users do this.

Read More

RSS links switch back to BITSUM.COM

Using a reverse proxy type with a single line of PHP, I have switched our RSS feeds all to BITSUM.COM. The BITSUM.NET reference feeds still work fine as well. This was important for search and indexing, where I want news feeds about Bitsum.com to be related to Bitsum.com. As always, they are listed here:

http://bitsum.com/rsslinks.php

Try not refresh them too often, I like to edit my posts several hundred times after first making them ;p.

I could move the entire Forum to bitsum.com this way, while keeping it isolated, and allow use of our SSL certificate. I am considering doing just that, but I have wasted a lot of time on this issue and so am going to wait. I want to make sure I've got everything considered. The Forum must be isolated, that's all there is too it. I have to assume that it will be hacked, even if it never is. That's one more barrier to protect customer data (note we keep very little info, no credit cards or other billing stuff.. in fact, we don't even ever get access to your billing info).

Why very few Forums on the internet use SSL I don't know. Honestly, I am of the belief every site should use it all the time -- except for the cost (which may answer my question). It is not only costly, but quite the documentation hassle. The cost is why I have a 'non-wildcard' certificate that only works for 'bitsum.com' (e.g. not 'www.bitsum.com').

Read More

Process Lasso v5.0.0.37

Changes:

• [.37]Fix.Core: Fixed auto-reload of config changes might fail to occur for shared, remote configuration files
• [.37]Fix.GUI: Fix flicker in 'RAM Load', 'Show Graph', and 'Buy Now' buttons when changing window size, it is now very smooth. This was seen most prominently in the 'RAM Load' graph.
• [.37]Fix.GUI: Fixed issue where lower view tab did not extend to right most edge after activation (to cover space of old buy now button)
• [.37]Change.Core: A few code optimizations
• [.37]Change.GUI: Substantially sped up icon retrieval
• [.37]Change.GUI: Instead of blank icons for processes w/o icons, the 'default no-icon' icon is used
• [.37]Change.GUI: Changed GUI memory management a little
• [.37]Fix.Updater: Fixed automatic update download dialog still not localized (will again take 2 updates to first see fix)
• [.37]Change.Updater: Quick upgrade is no longer system modal, to prevent inteference with fullscreen games when it goes to do an automatic update

Read More

New build coming today

This next build has some fixes I have been eager to get out, but its been held up in this more extensive debugging. I simply had to take some time, get things settled, and make sure they are right before I could release again.

After this, although continued maintenance on the current final will continue, I'm going in an exciting new direction. Stay tuned. I don't know how long it will take, and if I gave an estimate I'd just be wrong. I do know this will be what many have been 'waiting for'.

Read More

Next build coming, held up in QA as I fix some standing issues

There have been a few little quirks I have wanted to debug and take care of for a while. Some more problematic to debug than others. I am addressing as many as possible in this next build. I hope not to hold it much longer, but I have a list of things I want to make sure are addressed. QA must be the top concern at all times. I've done a lot towards that in the last month, but more must be done. Not having a dedicated QA team means I rely heavily on user reports of problems, and I thank you for that. I'm improving the way and helpfulness in which users can report problems all the times. First it was minidumps, next it will be automated submission of them along with configuration.

Read More

A jolt of enthusiasm

Things are going to change in a big way here. I realize I've reached a plateau. Process Lasso must now evolve to the next level. That is what we are all waiting on, right? Well, I do have a plan for this, and am working towards it. I don't want to give it all away, and my plans change so often that half of it would be useless anyway.

The minor maintenance will continue in the interim, but what I'm speaking of is a shift in paradigm so large that it brings back the excitement we all had when we first discovered Process Lasso (and the excitement many new users of Process Lasso get to this day). For the rest of us, minor maintenance has gotten dreary and routine. If you ever think you don't need Process Lasso's ProBalance, you will be like many who have tried without it for a bit, then remember why they loved it ;). Boy does it make a difference in responsiveness during Visual Studio builds of projects on even a high-end system. With applications making increased use of multiple cores, the need for ProBalance is as great as ever - as the chances of all your system CPUs being maxed out are getting higher. Then there is the inverse trend towards lower power CPUs like those found in netbooks, Windows tablets, and UMPCs.

"With applications making increased use of multiple cores, the need for ProBalance is as great as ever - as the chances of all your system CPUs being maxed out are getting higher. Then there is the inverse trend towards lower power CPUs like those found in netbooks, Windows tablets, and UMPCs."

We need a new jolt of kick-butt new features and massive user interface improvements. As a low level coder, I'm not all about user interfaces, but it should be a pleasant experience to use an application - not a painful one.

I thank everyone for their continued support and patience. The next minor update has some good maintenance and you will be pleased by it. Everyone is loving those automated updates by now I'm sure? Remember, if not using the automatic/automatic updates, the license validation is optional. The idea is to let you know if your license is going to be expired. If it is close, you might want to check.

We MAY start sending out emails before licenses expire, something we've not done before, but seems like a darn good idea. We don't want anyone taken by surprise. The good news is that if anyone ever is taken by surprise, you can always download an older version in the Support area and use it (even if your license is expired).

Let's hope for the best.

Also, I'm about to announce a little piece of freeware I've been working on... I didn't like taking time from Process Lasso, so rushed through it, but it is surprisingly functional and good. The power users that like Process Lasso will like this too.

Read More

v5.0.0.36 released

Downloads:

32-bit: http://www.bitsum.com/files/prolasso.zip
64-bit: http://www.bitsum.com/files/prolasso64.zip

Changes:

• [.36]Fix.GUI: Fixed and improved cleanup of auto update files (nothing that would accumulate)
• [.36]Fix.GUI: Fixed bad alignment of CPU % in listview tooltips
• [.36]Fix.GUI: Improved code and workings of several configuration dialogs
• [.36]Fix.GUI: Fixed prompt to save unadded new Watchdog entry in Watchdog Configuration dialog (behaves as others do now)
• [.36]Fix.GUI: Fixed prompt to save unadded new I/O priority entry in Default I/O Priority Configuration dialog (behaves as others do now)
• [.36]Fix.GUI: Fixed prompt to save unadded new Throttle entry in Default Throttle Configuration dialog (behaves as others do now)
• [.36]Fix.GUI: Fixed prompt to save unadded new Keep Running in Keep Running Configuration dialog (behaves as others do now)
• [.36]Fix.GUI: Improved compatibility with Comodo Defense+ (log events do not keep repeating, filling up the log). This can also be fixed by adding ProcessLasso.exe to the correct trusted processes list in Comodo Defense+.
• [.36]Change.GUI: Increased aggressiveness of process icon loads
• [.36]Change.GUI: Re-enabled asynchronous process icon retrieval
• [.36]Change.GUI: Double click a rule in the Watchdog configuration dialog to bring into edit mode
• [.36]Change.GUI: Double click a rule in the Default CPU Priorities configuration dialog to bring into edit mode
• [.36]Change.GUI: Double click a rule in the Default I/O Priorities configuration dialog to bring into edit mode
• [.36]Change.GUI: Double click a rule in the Default Throttle configuration dialog to bring into edit mode
• [.36]Change.GUI: Double click a rule in the Default Instance Limits configuration dialog to bring into edit mode
• [.36]Change.GUI: Double click a rule in the Keep Running configuration dialog to bring into edit mode
• [.36]Change.Core: Prevent excessive error messages, limit 1 error message per process - particularly important in Forced Mode
• [.36]Removal.Core: Removed message box if minidump was generated, goes to auto-restart and log
• [.36]Removal.Core: Removed log entry about where the log was being written to (seems quite redundant at present)
• [.36]Addition.Core: Core engine writes LOG message if it performed a self-restart
• [.36]Addition.Core: Added new self-restart feature if a crash or other anomaly occurs
• [.36]Change.Installer: Some in-house istall facilitation tools not previously signed now are
• [.36]Change.QuickUpdater: Allowed for proper localization of it (brief download dialog was English only before)
• [.36]Change.GUI: More efficient switch on process listview notification messages
• [.36]Change.All: Adjusted size of minidumps again (still much smaller than they once were)
• [.36]Change.All: Updated Russian
• [.36]Change.All: Updated French

Read More

Nearly done with new configuration dialog cleanup and more

It has been a bit tedious, but most all of the rule configuration dialogs have now been cleaned up and fixed up. Sure, they could always be better, but now they behave consistently and you can double click a rule to edit it (instead of having to remove, re-type, then add it). Some more work will continue incrementally, as I like to do. Also, there was a fix to the at-exit save prompts of many configuration dialogs, as they were not functioning as the user would expect as well, a fact I discovered during testing.

Several other improvements are in this next build as well. I'm trying to finish it on up in the new few hours. I have a good bit of testing and code review to do after finishing the remaining code chores, but it is doable.

Read More

Smaller minidumps means more submissions

One of the changes in the last build was that I reduced the size of the minidumps that are generated in the rare event of a crash. They have been reduced in size several hundred percent (from megabytes to kilobytes).

Please simply email me any generated minidumps. These are found in the user %APPDATA%\ProcessLasso folder. These help me to quickly diagnose some problems (not all).

Of course, most users won't ever see any minidump. They are generated on the rare occasion of a crash.

Read More

Fixing those annoying configuration dialogs

I don't know about you, but when I use the configuration dialogs I think of how lazy the developer must be ;p. I am therefore cleaning them up. It may be a gradual process, not to happen overnight, but they will get progressively easier to use. For instance, the first change is that double clicking an 'entry' (in a list or listview) brings it back up into the editing area for modification. Having to remove then completely recreate entries is absurd. That I let this go for so long disappoints me, but ...

On other news, the automated update downloader you briefly see is now localizable - one of the very few areas that wasn't. This will occur in the next build, and as translators update their languages.

The activation system has been made more robust, and I'm starting to make it easier for people to renew or upgrade licenses.

Work, work, work ;)

Read More

Licensing tightened down

The licensing had been a bit excessively lax, which was not fair to paying customers. It is still far from totalitarian, but it makes sure nobody is getting more than their fair share. I had to go through several sample scenarios to make sure the system works as it should, supporting numerous resellers, license types, differing versions (for some resellers where this matters), and varying update subscription terms.

If your activation code no longer works and you feel it should, please contact me.

Read More

v5.0.0.32 released

• [.32]Fix.Core: Fixed issue where watchdog entries quit working when forced mode was on if their time threshold was non-zero.
• [.32]Change.Core: Improved efficiency of core engine when Forced Mode is on and watchdog entries are active.
• [.32]Addition.Licensing: New offline activation mechanism added

Read More

v5.0.0.31 released

Amongst more minor issues, this version updates the core engine Watchdog capabilities. They now perform nominally with regard to time over threshold.

• [.31]Addition.GUI: Added ProBalance menu option 'Lower I/O priority during restraint' to options menu (was only in dialog before)
• [.31]Fix.Core: Fixed watchdog 'time over threshold' not beind adhered to in all cases. This is NOT related to ProBalance.
• [.3]1Fix.Core: Fixed watchdog entries not always being enforced when they should be (sometimes deferred). This is NOT related to ProBalance.
• [.31]Change.Core: I/O Priority Lower during restraint now reset if ProBalance defaults restored
• [.31]Change.GUI: Allow manual entry of CPU % in Watchdog dialog instead of forcing use of combobox
• [.31]Change.GUI: Rearranged configuration dialog menu items a little
• [.31]Change.GUI: A few small cosmetic fixes for some languages
• [.31]Change.GUI: Improved handling of system tray icon recovery if explorer crashes (near instant instead of delayed a few seconds, and more redundancy on failure)
• [.31]Change.GUI: Other misc cosmetic tweaks
• [.31]Change.GUI: Several other misc code tweaks
• [.31]Change.GUI: Updated Russian
• [.31]Change.GUI: Updated French
• [.31]Change.GUI: Updated Finnish
• [.31]Change.GUI: Restored older Traditional Chinese translation
• [.31]Change.Installer: No longer force language reselection (Japanese build only), as automatic update is now most common method to upgrade and it doesn't reset language anyway

Read More

v5.0.0.30 released

Although I wanted to get a little more done, I felt I had reached a good stopping point and translators were all waiting patiently for me to finally get their updates out. The new build is described here: http://bitsum.net/forum/index.php/topic,761.msg3835.html#new

Read More

Process Lasso v5.0.0.29

Changes:

• [.29]Change.GUI: Graph now laid out in horizontal rectangles instead of squares
• [.29]Change.GUI: Change increment/interval length on graph
• [.29]Change.GUI: Updated Italian, Polish
• [.29]Change.GUI: Optimized graph painting some
• [.29]Change.GUI: Removed some performance profiling code from release build
• [.29]Change.Core: Adjusted hard-throttle levels for wider spread and more aggressiveness at higher levels
• [.29]Fix.GUI: Fixed Memory Load graph could be unpainted for a second after another window clips it in 2K/XP only
• [.29]Fix.GUI: Fixed lost first character on some rundll32 formatted process names
• [.29]Fix.Core: Fixed issue where default power scheme may not stay or wouldn't revert as expected in some circumstances when multiple default power scheme processes were running
• [.29]Fix.Core: Fixed 'EMPTY STRING' seen in ProBalance end log message description column (not shown by deafult)

Read More

Forum RSS feeds now primary release notification

For those who want to stay up to date with the latest releases and change logs, instead of subscribing to this blog, I recommend using the Forum. As of v5.0.0.25 I began publishing minor updates in the release announcements there.

To subscribe, add this URL to your feed reader (e.g. Google Reader):
http://www.bitsum.net/forum/index.php?action=.xml;type=rss2;board=3

Read More

v5.0.0.28 graph change

More graph lines, better consistency with other system graphs. I have some more tuning I'll be doing. I have decided to simply emulate the typical Windows graph instead of trying to forge my own path.

Read More

CPU Parking revisited: How to enable or disable CPU Parking yourself without registry edits

This post has been superceded by this newer, better, and more up to date one.. including a new freeware utility called ParkControl that can assist in enabling or disabling CPU core parking. For information, see http://bitsum.com/about_cpu_core_parking.php

OLD ARTICLE (still better than all those that tell you to edit the registry)

A month ago I wrote a long blog post about CPU Parking, a new feature of Windows 7 / 2008 R2. Since I later deferred release of a quick feature to toggle this system setting, I deleted the rambling blog post. I decided it was past time to restore some information on CPU Parking.

CPU Parking is a feature of multi-core/SMP systems that disables cores when the system load is low enough to allow such. Windows provided no direct way to adjust this via the user interface, as they likely thought everyone would want to keep this enabled. According to public documentation on the feature, unpark time is near instantaneous. Indeed, it may very well be. Additionally, by parking CPUs you can potentially reduce core thrashing - when a thread is swapped between cores unnecessarily, causing a performance hit.

However, for systems where power consumption and heat are not an issue, but maximum performance is, it may be desirable to disable CPU Parking. The fact is that even if unparking is near instantaneous, CPU utilization usually occurs in very brief bursts, something I mention frequently. If you look at your CPU utilization and see 15%, that is actually the percentage of time the CPU was active within a relatively large interval (usually 1 second). Actual CPU utilization most often occurs in micro-bursts where the CPU is fully consumed for a few nanoseconds or microseconds. You want those bursts to execute as fast as possible, and this is why all power saving technologies, including frequency scaling, incur *some* performance hit. This is also why a faster CPU does matter, even if you typically don't utilize 100% of available CPU time over a larger interval.

Whether or not Core Parking is actually used on your PC depends on a few factors. First, your PC must be have at least 2 physical or logical cores/CPUs. Most of the time it is enabled for laptops and servers, but not for desktops. It can also vary between vendors, as many create sets of custom power schemes supposed to offer better performance or improved battery life (rarely do they). It also can vary between Windows editions. The Server Editions tend to make more aggressive use of it by default.

Want to see if it is active or not? Fire up the Windows Resource Monitor and go to the CPU tab. Parked cores will be clearly shown as 'Parked' in the caption of their graph. CPU Parking is actually done quite aggressively. On a dual-core HyperThreaded Core i5 (4 logical cores), I have seen cores parked even as total CPU utilization approaches 50%. Windows seems fairly smart, parking the HyperThreaded/fake cores first.

Changing CPU Parking Settings

Many places on the internet tell you to edit the registry directly when adjusting CPU Parking. I don't actually recommend this. Instead, use the console mode powercfg.exe. Using it you can also tune the CPU Parking so that a certain percentage of your cores must remain unparked at any given time.

You must run this utility with elevated rights, so be sure to open an elevated console window by right-clicking 'cmd.exe' and selecting 'Run as Administrator'.

To mandate 50% of available cores always remain unparked, run:

powercfg -setacvalueindex scheme_current sub_processor bc5038f7-23e0-4960-96da-33abaf5935ec 50

To adjust it so that only 25% of available cores remain active at all times, allowing 75% of available cores to be parked, you'd run:

powercfg -setacvalueindex scheme_current sub_processor bc5038f7-23e0-4960-96da-33abaf5935ec 25

Yes, you can use '0' - Windows is not stupid enough to park all cores at once, it will always leave at least one core active. In fact, this is usually the default setting when it is enabled. For example, to enable maximum use of CPU Parking:

powercfg -setacvalueindex scheme_current sub_processor bc5038f7-23e0-4960-96da-33abaf5935ec 0

To disable CPU Parking completely, you'd want to run:

powercfg -setacvalueindex scheme_current sub_processor bc5038f7-23e0-4960-96da-33abaf5935ec 100  

After changing the power scheme settings for CPU Parking as desired, you then want to make the changes active by running the command:

powercfg -setactive scheme_current

When I first wrote this I included allowing specification of AC or DC (battery) values for the power scheme. Setting the DC power value isn't documented, so I am going to skip that. Still, to do so you'd simply replace '-setacvalueindex' with '-setdcvalueindex'. It also is not entirely clear if this is supported for every power scheme, though it certainly appears to be. Sadly, Microsoft's documentation is quite scarce.

You should not have to reboot for these changes to take effect. Go ahead and check the Resource Monitor and verify that CPU Parking is indeed as you set it.

I hope this helps some people. Why would you go around making manual edits to the registry when powercfg can do the job for you? You shouldn't. Registry edits are prone to mistakes and are generally more tedious and less clear.

Enjoy ;)

Read More

Process Lasso v5.0.0.28

This build continues maintenance, fixing several items and also making a nice improvement to the graph's display. Further, the last selected process tab is now preserved on restart. The most important fixes are the configuration file would reset on XP systems with Terminal Services disabled, and the governor could get stuck pending deletion on a reinstall or upgrade when it was configured to run as a service.

• [.28]Addition.GUI: Persist current upper tab view across restarts (save upper tab selection)
• [.28]Change.InstallHelper: Reworked Terminal Services non-critical, but suggested, dependency check
• [.28]Change.InstallHelper: Reworked Task Scheduler service non-critical, but suggested, dependency check
• [.28]Change.Installer: Removed 'Restore system tray icon' start menu item
• [.28]Change.GUI: Increased number of horizontal graph lines, improving look of graph
• [.28]Change.GUI: Slowed process icon retrieval in cases where the GUI is first opened during a high disk load
• [.28]Change.ServiceMgr: Wait for service to stop when requested
• [.28]Fix.All: Fixed issue with an improper registry key path, auto-cleanup
• [.28]Fix.GUI: Fixed issue where when Terminal Services is disabled in XP, a logic error in the GUI would cause configuration to reset
• [.28]Fix.GUI: Fixed message box warning when Terminal Services is disabled ask a question, but no Yes/No option is actually available
• [.28]Fix.GUI: 'Configure Default I/O Priorities' application menu item was not being properly disabled and grayed in XP and 2K
• [.28]Fix.InstallerHelper: Fix date/time format could get misremembered
• [.28]Fix.InstallHelper: Fixed issue when reconfiguring the governor startup type when was/is set to start as a service, would fail until next reboot with a pending service deletion error

Read More

Windows XP w/o Terminal Services config file reset bug

One issue I've had reported was that the configuration was being reset. Thanks to a user report I finally was able to determine what was going on. It ONLY affected people running Windows XP *and* who had Terminal Services (TermService) disabled. The default setting for this service is Manual, and that is certainly what I recommend. Contrary to popular belief, disabling services really doesn't gain you much performance or save many resources. What it does do is muck with the operation of the system and applications. Now, this bug wasn't actually due to Terminal Services, rather a logic error in the GUI caused the configuration file to be reset when this condition was found. Basically the GUI was changing a setting to deal with the lack of Terminal Services availability, then saving the configuration file before it was ever loaded to start with. This bug likely crept in during the last beta as some of the initialization code was re-arranged.

This has been FIXED internally and is pending release in v5.0.0.28, a build that has an assortment of minor fixes and improvements. Even the graph has changed in appearance, for the better I do believe. This new build is being prepared now.

Read More

v5.0.0.27: A few fixes and restores Windows 2000 support

This minor update fixes a crash of the Process Lasso GUI in Windows 2000 as well as a few other items.

• [.27]Fix.GUI: Fixed crash seen in Windows 2000. Note that process icons are disabled in W2K, at least for now, as the issue is in the new code to more efficiently resolve them using system APIs not available in W2K.
• [.27]Fix.Core: Fixed premature exit of default power scheme in certain cases where multiple default power scheme processes were running
• [.27]Fix.GUI: Fixed Russian activation dialog had User and Code captions reversed
• [.27]Fix.All: Fixed theoretical cause of settings being reset under rare circumstances

Read More

Fix for Windows 2000 users coming next build

I've fixed a crash in the GUI seen in Windows 2000. It was caused by use of the new process icon resolution code, which depended on newer APIs not available in Windows 2000. I suppose I shouldn't be surprised that Windows 2000 is still in use. For many tasks I do suppose it is a viable OS and there is no reason to change. Of course, many vendors have dropped support for it, but I have restored proper support in v5. This will be in v5.0.0.27, which is coming shortly.

Read More

Betanews publishes Process Lasso v5 release article

One of my favorite web sites is Betanews. They regularly post useful and interesting articles, keep me updated on new software releases, and have a great community of users who generally tell it like it is. I was therefore very pleased to see an article about Process Lasso on the home page!

Read More

v5.0.0.26: A few very minor adjustments

This is a very minor update. In fact, I may delay or not push out update notifications for this build. The primary fix in this build I wanted to get out was a small mistake in a previous minor update that caused the 'Automatic updates' option to NOT persist for users first enabled it in a recent version. I had removed an extra EULA confirmation and in doing so introduced a small bug that prevented it from ever being true. This is fixed. In addition, some general maintenance to the service management code base was performed.

• [.26]Change.GUI: Updated Italian
• [.26]Fix.GUI: Fixed bug that started a few minor updates ago, causing automatic updates to not actually be turned on (though it appeared checked at first)
• [.26]Change.InstallHelper: Further consolidated the service creation code
• [.26]Change.InstallHelper: Added critical section timeout system registry value check, to ensure no user set it to an improperly low value

Read More

v5.0.0.25: Portable Edition goes final, command line param fixes

The Portable Edition is now coming out of beta. I finally finished this up, something I should have done a long time ago given the interest in this edition. As I worked on the new portable edition, I noticed some bugs in the command line parameter handling. This build also resolves those bugs.

• [.25]Change.GUI: Automatic updates no longer marked as experimental
• [.25]Change.Portable: Changed distribution to simple ZIP archive of Process Lasso program with a batch file to start
• [.25]Change.Portable: Configuration file and log file now stored alongside program file
• [.25]Change.Portable: Automated updates now work with the portable edition, though only automated updates at this time
• [.25]Addition.SrvStub: Added version resource
• [.25]Addition.GUI: Added /configfolder command line option for optional use instead of /configfile
• [.25]Change.All: /configfolder now expands '.' as current working directory, as does /logfolder
• [.25]Change.GUI: Remove random nag shown 1/6 main window opens from system tray
• [.25]Fix.GUI: Fix 'Keep Running' processes were sometimes associated with the PL main window, depending on if the GUI had launched the governor or not
• [.25]Fix.All: Fixed a command line parsing issue with quote encapsulated paths
• [.25]Change.Build: Improved speed of build environment (internal)
• [.25]Fix.Log.subsystem: Fixed global log folder command line specification
• [.25]Fix.Log.subsystem: Fixed a string reference not properly defined as const and written to improperly by a subfunction (no actual bug manifests as it was unused)
• [.25]Addition.Core: Added new log entry indicating the log path
• [.25]Change.GUI: Changed first minimize to tray message so it is slightly less ugly
• [.25]Fix.Portable: Disabled manual updates, automatic updates now work for this edition

Read More

Portable Edition: Changing distribution format

I was contemplating the Portable Edition and it occurred to me that we're going to be better off if I simply distribute an archive of all the Process Lasso program files, instead of a single self-extracting archive that extracts and runs on-demand. The reason is simple: Updates. The former requires a complete (and different) update mechanism. I'm working on building this now, along with other improvements to the Portable Edition.

Additionally, the log and configuration files will now be stored on the removal media. This will allow you to take your settings and log events around with you. These locations can easily be changed via the batch file.

Read More

Product description and marketing maintenance

I've been working on improving the product description, updating the web pages and site, and creating some new marketing images. Frankly, few people realize the true capabilities of Process Lasso. There is nothing more annoying than having people quickly dismiss it as yet another task manager. Of course, if they read the existing description they'd know that isn't true, but still it is frustrating. Towards this end I've planned some new ways to convey the multitude of features. I've also got a new web site design in progress, something I've wanted for a while as frankly I am sick of looking at the existing web site. Sadly, one of the hardest things in the world for me is to make things look attractive, though I suppose that is obvious ;).

I've also decided to reduce the frequency of the nags in the next version, as I don't want them to be too annoying. The advanced features should be what compels purchase, and honestly I don't think the existing nags are very annoying. I often run the free version myself for weeks on end, and they aren't annoying enough to me to register my own program. Still, they can be toned down a little without any major effect on licensing, so I'll be doing that. Keep in mind these fast click-through nags with *NO* timer are vastly preferred over what many freeware programs do: add toolbars and other crap to the installer. Those who complain about the nags should consider the alternatives, and I mean *real* alternatives that take into account the real world.

Of course, my licensing aggressiveness typically goes up and down, as I struggle to find and maintain a balance. I want Process Lasso to be as free as possible, that's the absolute truth. However, I also simply must generate enough revenue to cover the costs of Process Lasso and my other projects. Heck, web hosting and related services alone cost me $200 a month now. The automated updater was a part of that, as I simply had to have a reliable primary web server if I was going to offer automated updates. I got by on shared servers for many years, but this year it became clear my time with shared hosts was over.

Read More

v5.0.0.24: Re-enable full self memory optimizations

Welcome to v5.0.0.24. I do have more work ongoing, but am launching this build with well tested changes I've been wanting to make for a while. The largest is that full memory optimizations in the core engine have been re-enabled. Some of these optimizations were disabled a while back as I evaluated a bug I'd seen. I tracked down and addressed the bug, and after some lengthy memory utilization testing, I am ready to release this build with them re-enabled. CPU use and memory utilization of the core engine will be improved with this build.

• [.24]Change.GUI: Hide unavailable I/O priority column by default in 2K/XP (for new installs or listview reset)
• [.24]Change.Installer: Don't warn about Terminal Services disabled
• [.24]Change.Core: Decreased memory utilization in environments with a lot of processes
• [.24]Change.Core: Re-enabled full memory optimizations, they had been disabled in a previous build while I studied utilization
• [.24]Change.Core: Removed non-visible debug output entirely, a call stub had previously remained.

Read More

v5.0.0.23: Fix some minor issues, larger update being tested still

My source code repository and virtual development environment lets me do some cool things. For instance, I've got some large changes I'm still testing, but I wanted to go ahead and release a minor update to correct a few little cosmetic and GUI quirks. Thus, I'm launching v5.0.0.23, as I'm unsure how much longer it will be until I'm done with other, larger, changes for v5.0.0.24.

• [.23]Change.GUI: Added more assertive cleanup of auto update archive
• [.23]Fix.GUI: Fixed new throttle dialog warning truncated and corrupted
• [.23]Fix.GUI: Fixed 'Edit INI' Advanced option
• [.23]Change.All: Reworked log queue synchronization object
• [.23]Change.Core: Reworked hard throttle mechanism - Note this is not ProBalance, this is a separate non-recommended function for advanced users
• [.23]Change.Core: Changed throttle timing levels quite a bit, should offer wider range of hard throttling

Enjoy ;).

Read More

New minor update coming soon

The next minor update will fix a few little issues with the GUI and make other improvements. This build does need more testing than previous minor updates, hence the delay. I've already accomplished most of what I plan to, but am making sure this is a good build. I'd like for this to be the last minor update for a while.

Read More

v5.0.0.22: A build a day keeps the doctor away

Here I go again with v5.0.0.22, a build I am finishing up and uploading in just a few minutes. This build does more maintenance, fixing some GUI quirks. It amazes me just how mucked up the GUI had become to be honest. The last beta series was long and convoluted, and I suppose that is the reason. Numerous new features were added. Regardless, this version has certainly come a long way in the last 4 days. No new feature additions, but lots of fixes and improvements.

• [.22]Change.Updater: Re-enabled Server Edition automated updates
• [.22]Fix.GUI: Fixed manual process suspension
• [.22]Fix.GUI: Fixed quirk in Power Scheme Defaults configuration dialog
• [.22]Change.GUI: Tweak to synchronization objects referenced in configuration dialogs
• [.22]Change.GUI: Updated Italian

Read More

v5.0.0.21: Fix failure of web links within Process Lasso on some systems

I've had reports of sporadic failure of the web links within Process Lasso. I've analyzed this situation for a while today and found it rather perplexing. The identical code in older versions would work on a system, but not in the newer version. I thought it might be a variance in the default verb, but that was not the case, as I've always used the default verb (double checked in source repository). Meanwhile, on system Y and Z, there are no problems with either version. Changing the default browser doesn't seem to matter. I speculate it may have something to do with the security software, but this makes little sense too. Strange. Anyway, I wrote some code to directly find the default web browser and open it. This seems to work much better. Of course, if it fails I defer to ShellExecute. So, this is now fixed.

Users should remember -- You need not grab every update. Just turn on the Automatic Updates and you need not worry with keeping Process Lasso up to date at all. Of course, it does not check for updates every day - the interval is actually every 3 days, or now 2 days with this update.

I say this because I don't want users to go crazy trying to keep up with every minor update. Most are NOT important to the majority of users. I simply want to make sure the latest and greatest code is always available. After all -- as I said, why wait?

Read More

v5.0.0.20: Fix to core engine memory issues seen on a small minority of systems

One of the optimizations I employ is reusing memory instead of having to free and reallocate it. Yes, it does make things a bit more complicated, but it improves efficiency considerably. Sadly, while I reviewing the code I saw a logic error that needed repairing. I have no idea if it ever manifested in the real world, I've not seen it. It would have manifested most likely as a crash.

However, I did fix something that I know did manifest in an XP test bed I have with a unique software environment that includes NIS 2011: a very small memory leak in the core engine. I do not know how many systems were affected, I certainly have not seen this on any other test beds. Also, it is a very small and slow leak that would take a good amount of time to build up (and be continually paged out in the meantime). So, it is unlikely anyone who was affected actually noticed. Regardless, I repaired it and am issuing this update.

Thus, we have v5.0.0.20:

• [.20]Fix.Core: Fixed a logic error in memory reuse optimization (unknown if manifested in real world)
• [.20]Fix.Core: Fixed a small memory leak seen in exhaustive testing under XP /w NIS 2011 present (special handling involved with NIS2011)
• [.20]Change.GUI: Updated Serbian Latin
• [.20]Change.GUI: Updated Finnish

Please keep in mind that version 5 was a large leap, and I certainly do wish I had polished it more prior to the first final version. However, we are where we are, and I can say that it is now where it should have been to start with. Yes, I am embarrassed with the admission that I discovered more bugs. At least I discovered these before they were even reported, for what it is worth ;).

The polishing continues... I already have another minor update to improve a few cosmetic non-critical issues in the GUI coming down the pipeline. Of course, this goes without saying, I always have a new build coming down the pipeline.

Read More

v5.0.0.19: Small fixes to the governor's No Sleep and Auto Gaming mode rules (general fix affected both)

I had a user report that rules weren't being enforced in a timely manner. I partially addressed this in v5.0.0.17, but it turned out there was one more little fix remaining. This fix resolves the proper application of No sleep and automatic gaming mode.

I do apologize for overlooking this. I thank all users who report bugs. There are so many features of Process Lasso and it runs in so many different environments that it is imperative users report these bugs. Usually I fix bugs very rapidly once I become aware of them (often within 1 hour I have a new build out). It is exceedingly important that this version excel. Although it is embarrassing that any bugs slipped through testing, I must admit and own up to them - so users know they existed and know a fix is now available.

ProBalance, default priorities, default affinities, and most other rules were never affected. Only No Sleep and Gaming Mode were guaranteed to be affected, with an imperceptible improvement to the performance of Default Power Schemes (though it never malfunctioned).

This build is being created now and should be available in the next few minutes.

Read More

v5.0.0.18: Fix auto updater in XP

During testing a few hours ago I noticed the auto-update was failing in some XP installations. Specifically, it would appear to stall at the end of the download. The actual problem was with use of the shell API that resolves common filesystem paths.

It worked in testing of other environments, and had previously worked in XP until a change apparently broke it. Thus I simply missed this in testing until now. Yes, I don't stop testing even after final release. As I've said elsewhere, there is nothing that kicks me into high gear like the pressure of a new final.

So, this build fixes the updater, BUT it will not start working until the *next* update after this one because this build contains the fix.

This should be the last fix to the automatic updater. Now I can begin issuing updates like a crazy person ;p.

This build will be available in the next few minutes, it is building now.

Read More

v5.0.0.17 final - Minor fixes

This build fixes a reported issue with the watchdog rules (re: not default affinities, priorities, power schemes, but rather the terminate/restart/affinity on X% CPU/MEM). They were not being applied instantaneousness and a fix was applied to the Clear All button in their dialog.

Russian and Italian languages were also updated.

The previous minor updates were me mucking around with an emergency situation where the old web server was overloaded. As mentioned, I have upgraded the web server to deal with this. This new server went up in perhaps record time (4 hours from time of order to final configuration and upload on my end) and is fully operational already. Both servers will remain active until the DNS change has fully propagated (it should be propagated to the majority of users already).

Read More

Beta users -- be sure you got the new final

I noticed that the beta URLs weren't updated yesterday, which could have caused users of the last beta to not get the new final. I do apologize for this and am updating the URLs now. It is important you update to the new final.

Read More

New real dedicated web server - and minor language updates

I've thrown a few minor updates out, simply minor language updates. Some may be pushed out the updater, others now. I am trying not to saturate the system, but am trying to keep the latest build up.

I discovered yesterday that my little VPS was vastly underpowered. I had more resources with a shared server in fact. The traffic crippled the web server twice, forcing me to take create some restrictive firewall rules to keep it running for most of the world. Good news -- no more of that!

Immediately upon seeing the problem I ordered a real dedicated web server and began the transition. Within 4 hours the new server was fully operational and the DNS change began propagating. As of now most people will likely already be referencing the new server, though some may have to wait until this evening or later. Clearing your DNS cache and/or switching DNS servers may accelerate the transfer. That said, BOTH servers are fully operational so it shouldn't matter which you get to.

Note that I've had a handful of people tell me the Support area was done, but this seemed to be because people were still using the old URL to the month-gone IIS server (likely bookmarked). We no longer use the MerchantSecure.com service for SSL. Instead, we found that SSL certificate prices (at least non-wildcard) had gone down and purchased a SSL certificate for bitsum.com. Therefore, the Support area can be found at: https://bitsum.com/phplogin . Please note the missing 'www', else you'll get a certificate error since we couldn't afford a wildcard certificate.

Who did we go with? LunarPages. I've been impressed with their customer service and wide variety of hosting options. They are not the cheapest, but they are competitively prived and reliable.

So... everything should be good. Enjoy ;)

Read More

v5.0.0.12 final

Welcome to the future. I'll not ramble on about changes, as there have been hundreds. We pretty much know what has been added. I/O Priorities, Default Power Schemes, HyperThreaded core avoidance, automated updates, and a variety of improvements and optimizations.

This final fixes a handle leak that occurred in the last couple *betas*(only) - specifically, those released in the last 48 hours or so. Therefore, it is important you go ahead and upgrade if you were using the last couple betas. The handle leak isn't something that would affect the rest of the system, it would only eventually cause Process Lasso's memory utilization to increase.

This build should be a good one, though of course you can expect to see the usual barrage of minor updates as I continue polishing and perfecting the code - a chore that never ends. In fact, I already have the next minor update planned, lol. The good news is that the new AUTOMATED UPDATES should allow users to easily keep up to date. I believe the system is functioning nominally now, though this will be the first public final/stable build test of it.

Enjoy!

Read More

Auto update to v5.0.0.10 beta x64 would be v5.0.0.9, old version

Users who updated the x64 build to v5.0.0.10 might have gotten v5.0.0.9 again. This was due a typo in the build system, causing it to not upload the new x64 workstation auto update because it got deleted while creating the x64 server edition auto upload. In other words, it would fail depending on the order I created the builds.

Read More

v5.0.0.10 beta

Welcome to v5.0.0.10 beta. We are getting really close to final now. I want to do some extended testing due to the internal changes in this beta, but we are perhaps a day or less away.

• Fix.Core: Fixed crash seen in use of instance count limits of last many betas
• Change.GUI: Optimized mechanism of avoidance of certain processes
• Change.Core: Improved efficiency a good bit
• Change.GUI: Improved efficiency a good bit

Read More

Fixed crash seen in beta governor by some people

After quite a long search, I have finally determined the cause of a crash that affected a minority of users. I have now corrected it and the fix will be in v5.0.0.10 beta, to be released soon. I do still have a bit more cleanup to do, but am launching this build ASAP.

Note a couple other things:

1. This particular crash did NOT occur in the last final/stable build - v4.00.34
2. This crash was manifested by the use of instance cont limits.

Read More

5.0.0.9 beta

Sadly, my change in version naming did confuse some users who thought v5 was final already. Well, it is close, but not there --- I am rapidly cleaning things up and regression testing. I have also resuming documentation of minor changes. Here are the latest:

• Specific minor changes in v5.0.0.9
• Fix.GUI: Fixed HyperThreaded core avoidance menu items disabled on HyperThreaded systems
• Addition.GUI: Added physical and logical CPU counts
• Change.Installer: No longer direct user to uninstall page on uninstall
• Change.AutoUpdater: Increase internal download step size to 64KB
• Fix.AutoUpdater: Prevent new caching of auto update file and prevent using any existing cached copy
• Change.GUI: Removed some experimental code, load time faster
• Fix.GUI: Fixed a possible crash found during code review
• Specific minor changes in v5.0.0.7
• Fix.Updater: Fixed handling of bad input data
• Change.GUI: Improved handling of bad input data to updater (in cases of server misconfiguration, as occurred a couple hours near midnight EST on 05/24/2011 resulting in a crash)
• Change.GUI: Make updater wait longer before first check
• Change.GUI: Removed secondary EULA acceptance on automatic update since the EULA never changes
• Change.GUI: Removed 'beta' checkbox on automated update dialog
• Change.GUI: Several changes to updater
• Change.Core: Replaced 'DEAD' with 'EMPTY STRING' for string error checks

Read More

32-bit standard/home auto update in beta fixed

The 32-bit workstation build's auto update was broken a couple builds ago when I added support for the server edition. A typo caused it to grab the 64-bit build instead. This has been fixed, though it won't be until you update *from* v5.0.0.6 beta or later that the automated updater will work. 64-bit standard edition users will be fine, as well as server edition users.

Read More

v5.00.05 beta - Fixing oopsie in last couple betas

I noticed during regression testing that the last couple betas would simply refuse to do just about anything besides ProBalance and current actions (no default/sticky process settings). This was a little oversight in my eagerness to get the build out. I've corrected it now, along with more flaws, such as the failure of the core engine to stop on request -- a bug that has been around for a while in this beta series.

I also discovered a possible cause for a core engine crash, and have fixed it. There may be some more rare ones, I am getting to them, rest assured of that.

Read More

v5.0.0.3 - process icon optimizations and more

In this build I re-enabled some process icon optimizations that should speed the load time of Process Lasso's GUI. I have much more work to do before final, as I must go through a list of reported errata and ensure each item is fixed.

Read More

Automatic update finished for Server Edition

The next build, which I'll be uploading shortly, takes more steps towards finalization. Amongst other things, I've finished the automated update for the Server Edition, something that was incomplete until this time. Generally speaking, things are moving rapidly. The new final is subject to appear as soon as all regression tests are passed and some extended evaluation time elapses. Now that users have an easy automated way to keep the product up to date, any further maintenance can be done post-release.. and there is always more maintenance ;).

Read More

New versioning rules

To avoid confusion I've now decided to adopt a less unique set of versioning rules. The next version will be named v5.0.0.0 RC1 BETA. Eventually it will traverse to 5.0.0.x final. This is in contrast to the version naming that would have called the pre-final builds v4.9.9.x beta. Versions will be incremented based on their level of changes, with no limit on the minor version numbers (e.g. 5.0.42.75 is possible).

As a status update, this next beta is now imminent.

Read More

Welcome to our new, new web server

This last week has been miserable. Why? The web hosting I took for granted fell out from under my feet with a bad server problem that persisted for days, inducing a switch in hosts. Sadly, my second choice wasn't such a great choice as the new host decided to block half of Europe and Asia, as I've described a few times with colorful words. Finally, I selected a new VPS, spending more money than I had previously committed to. Now, this new box is NOT a supercomputer or super-server, but my experience so far has been that it is fast and reliable. It is a little slow on the latency side, but that is made up for with fast downloads (at least for me).

Enjoy ;). This SHOULD be our new home for the indefinite future. We've got a virtual server we have FULL control over.

The activation system still references the old server for the time being, as until the DNS changes propagate (with our own nameservers), the secondary domain could not be aliased. It should work, but be a little slow due to long-distance database connections.

For those that experienced the 'database unavailable' or other errors in the last couple days, that was on our 2nd host, who was apparently blocking outgoing remote MySQL connections. I didn't worry much with it, knowing the DNS change would propagate fast and be near immediate for most NEW users. Sadly it was the users who had recently visited us that mostly got the cached nameserver resolution.

• Primary web services: Tested, functioning
• Order fulfillment: Tested, functioning
• Support area: Tested, functioning
• Update system: Tested, functioning
• Activation system: Tested, functioning (slowly due to old server being in use)

For those who have experienced various problems this last week, I do apologize. These have ranged from our web site being unavailable, to various errors, to a malfunctioning update system. I am glad to be putting all this crap behind me and moving forward!

Don't know if you're at the new server? It resolves to 74.50.8.189 and can be accessed at processlasso.com as well.

Read More

Process Lasso v4.09.51 beta - quick update

This is a quick update, not doing much other than cosmetics. More to come.

Read More

Process Lasso v4.09.49 beta - Delay start and Periodic self-restart implemented

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 ;)

Read More

WARNING: Malware site is using Google adwords to distribute fake shareware (hundreds or thousands, including Process Lasso)

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).

Read More

v4.09.46 beta

This beta does some more polishing from the last beta, cleaning up some little things. More rolling on through very soon ... You know how I like to have the latest and greatest code out there, even if it is in beta form.

Read More

v4.09.45 beta released

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.

Read More

v4.09.42 beta - Fixed existing startup config detection in Vista+

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...

Read More

Watchdog operations fixed in v4.09.38 beta

I neglected to mention that late list night I released a new beta to correct the watchdog anomalies. It actually isn't a full correction (yet), but does cause them to be enforced instantly. I am still working on fixing the timing, which is ignored for the time being.

Read More

Going Green with Process Lasso

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).

Read More

I/O priority control added to multi-selection context menu

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.

Read More

Keep Running extended time before restart

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.

Read More