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