v5.1.0.27 finalDownloads:Workstation/Home/Standard:32-bit: http://www.bitsum.com/files/prolasso.zip64-bit: http://www.bitsum.com/files/prolasso64.zipServer Edition:32-bit: http://www.bitsum.com/files/server/prolasso.zip64-bit: http://www.bitsum.com/files/server/prolasso64.zipChanges:[.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...
Thursday, 15 December 2011
Friday, 2 December 2011
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...
v5.1.0.26 finalDownloads:Workstation/Home/Standard:32-bit: http://www.bitsum.com/files/prolasso.zip64-bit: http://www.bitsum.com/files/prolasso64.zipServer Edition:32-bit: http://www.bitsum.com/files/server/prolasso.zip64-bit: http://www.bitsum.com/files/server/prolasso64.zipChanges:[.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:...
Wednesday, 30 November 2011
v5.1.0.25 finalDownloads:Workstation/Home/Standard:32-bit: http://www.bitsum.com/files/prolasso.zip64-bit: http://www.bitsum.com/files/prolasso64.zipServer Edition:32-bit: http://www.bitsum.com/files/server/prolasso.zip64-bit: http://www.bitsum.com/files/server/prolasso64.zipChanges:[.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...
Monday, 28 November 2011
Monday, 17 October 2011
Process Lasso v5.1.0.7 beta released with new electricity saving featureThis 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...
Saturday, 15 October 2011
v5.1.0.6 betaSince 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.zip64-bit: http://www.bitsum.com/filesbeta//prolasso64.zipServer:32-bit: http://www.bitsum.com/files/server/beta/prolasso.zip64-bit: http://www.bitsum.com/files/server/beta/prolasso64.zipChanges:[.0]Change.GUI:...
Wednesday, 28 September 2011
This is a general maintenance release that fixes and improves a few items.DownloadsWorkstation:32-bit: http://www.bitsum.com/files/prolasso.zip64-bit: http://www.bitsum.com/files/prolasso64.zipServer:32-bit: http://www.bitsum.com/files/server/prolasso.zip64-bit: http://www.bitsum.com/files/server/prolasso64.zipChanges:[.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...
Tuesday, 20 September 2011
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...
Monday, 19 September 2011
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...
Thursday, 8 September 2011
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 n...
Tuesday, 6 September 2011
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...
Sunday, 4 September 2011
Licensed User Update Dialog - Activation code will be automatically populated in license validation boxFirst, 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...
Tuesday, 30 August 2011
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...
Saturday, 27 August 2011
Sunday, 21 August 2011
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 ...
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 short...
Saturday, 20 August 2011
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...
Friday, 19 August 2011
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...
Thursday, 18 August 2011
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...
Wednesday, 17 August 2011
I get tired of posting duplicate content, so please see: http://bitsum.net/forum/index.php/topic,761.msg4059.html#newUse 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...
Monday, 15 August 2011
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 ...
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 ...
Tuesday, 2 August 2011
Downloads:32-bit: http://www.bitsum.com/files/prolasso.zip64-bit: http://www.bitsum.com/files/prolasso64.zipChanges:[.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...
Monday, 1 August 2011
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...
Friday, 29 July 2011
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...
Sunday, 24 July 2011
Saturday, 23 July 2011
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.phpTry 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....
Friday, 22 July 2011
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 ...
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 fo...
Monday, 18 July 2011
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...
Saturday, 16 July 2011
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...
Thursday, 14 July 2011
Downloads:32-bit: http://www.bitsum.com/files/prolasso.zip64-bit: http://www.bitsum.com/files/prolasso64.zipChanges:[.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...
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...
Tuesday, 12 July 2011
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 cra...
Sunday, 10 July 2011
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...
Friday, 8 July 2011
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 ...
Tuesday, 5 July 2011
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:...
Wednesday, 29 June 2011
Thursday, 16 June 2011
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...
Tuesday, 14 June 2011
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;boar...
Monday, 13 June 2011
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.phpOLD 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...
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...
Sunday, 12 June 2011
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...
Thursday, 9 June 2011
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...
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 short...
Tuesday, 7 June 2011
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:...
Sunday, 5 June 2011
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...
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...
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...
Saturday, 4 June 2011
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:...
Friday, 3 June 2011
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'...
Wednesday, 1 June 2011
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 whi...
Tuesday, 31 May 2011
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:...
Monday, 30 May 2011
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...
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...
Sunday, 29 May 2011
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...
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...
Saturday, 28 May 2011
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...
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...
Thursday, 26 May 2011
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...
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 buil...
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 betasChange.GUI: Optimized mechanism of avoidance of certain processesChange.Core: Improved efficiency a good bitChange.GUI: Improved efficiency a good ...
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:This particular crash did NOT occur in the last final/stable build - v4.00.34This crash was manifested by the use of instance cont limi...
Wednesday, 25 May 2011
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.9Fix.GUI: Fixed HyperThreaded core avoidance menu items disabled on HyperThreaded systemsAddition.GUI: Added physical and logical CPU countsChange.Installer: No longer direct user to uninstall page on uninstallChange.AutoUpdater: Increase internal download step...
Monday, 23 May 2011
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 use...
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,...
Sunday, 22 May 2011
Saturday, 21 May 2011
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 ...
Thursday, 19 May 2011
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 immine...
Friday, 6 May 2011
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....
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...
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...
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...
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...
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...
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,...
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...
Subscribe to:
Posts (Atom)
