v4.09.28 beta

I was hesitant to issue this interim update because I had not diagnosed all the new minidumps sent to me. That new functionality is definitely helpful, and will be more helpful as I refine it. Sadly, it isn't yet as helpful as I'd hoped, though is definitely a good clue and gives me an idea of where the problem occurred.

Consider it yet another 'nightly build'. I probably did NOT get to evaluating your minidump submission or crash report, I haven't gotten to them yet and am also attempting some more general fixes to improve safety conditions. Most crashes seem to occur when there is process destruction activity while an event is occurring upon that process, despite my design to avoid such problems. There is a flaw somewhere.

This beta fixes some minor anomalies before I embark on larger changes:

• Fix.QuickUpdater: (beta2beta) It seems the SFX archive mysteriously wasn't silent for some reason in the 32-bit build, likely having to do with the SFX archive being updated instead of wholly recreated each build iteration
• Fix.QuickUpgrade: (beta2beta) Fixed inability to terminate Process Lasso's GUI in most cases (new bug last build)
• Fix.Core: Keep Running processes were being launched and having Process Lasso's taskbar icon under *some* circumstances
• Fix.GUI: (beta2beta) Fix truncated text of new update available dialog
• Addition.QuickUpdater: Now has the ability to self-update
• Change.Core: Tweaked delay on Keep Running processes (to allow for system startup)
• Change.Core: Keep Running now doesn't force an exact match of process path, it will count instances via their base name too
• Change.Core: Change process launch flags for keep running processes
• Change.GUI: Shortened update dialog - less text, more direct info

Read More

Keep Running feature change in behavior

During testing I've noticed some undesirable behavior of the Keep Running feature under certain scenarios. Under one scenario, it kept launching the process over and over due to a misconfiguration caused by the new beta automated updater.

One, in the next beta build process instances will be counted by base names. The path names don't have to match up, as they previously did. I can provide an option if anyone needs the old behavior. That means if you want to keep c:\windows\system32\notepad.exe running, a copy running in c:\test\notepad.exe will already count. This was not true before, and the desired behavior is debatable.

I also tweaked the delay after startup at which it begins even caring about these keep running processes. It is based on your hardware, but there is a delay of at least X iterations before any keep running process is applied. This was true of previous versions too, it has simply been changed.

Additionally, I added a last minute verification that the process didn't suddenly get launched right before us with a new check of the NT processes and threads array.

Lastly, the child process has different flags associated with it, as I noticed applications launched by the governor were sometimes getting Process Lasso's shell icon in the taskbar. This should alleviate that problem, and potentially other problems, as the process is now less a child of the governor. Strangely, there seemed to be no rhyme or reason to whether Windows shell opted to use this icon or not. I do not know if it is an issue with the infamous shell icon cache or not, but I seem to have fixed it where it did appear (it didn't appear on a VM with the same config, so go figure).

Read More

Warning about beta auto-updater in testing

Those who have used the auto-updater have had their manifests changed, potentially causing errata in the latest betas. So, do a proper update. Yes, this issue was fixed once before, but the SFX archives used to silently update the product were being updated instead of recreated, causing the bug to persist.

Due to this possible manifest and configuration mismatch, to avoid certain bugs you need to run a proper update with the installer. Remember, the beta quick updater is still experimental. I've already seen problems in QA testing in XP of the latest beta build (failure to terminate PL). I will get it right by v4.1 for sure, but until then, remember that it is experimental.

In general, the auto-updater has not been particularly successful thus far, even though I thought it was. For some, it may have worked perfectly. However, for others, it may have never worked, or changed the application manifests, causing possible problems (result is Process Lasso and the governor no longer ran with highest rights).

UPDATE: I just completed new self-update of the updater capability, so we're getting there. Also, for those who saw the SFX extraction destination dialog (it wasn't silent), this was apparently due to the recreation of the archive too, in some way. It should now be fixed. I believe only 32-bit builds were affected.

Read More

v4.09.27 beta released

I didn't announce this release because I passed out shortly afterwards. It is only about 95% of what I wanted anyway. Still, it represents a large change. I did come across one snafu, and that is updating the self-updater when the self-updater is doing the update. There are several ways to work around the problem, but for now I'm not updating it. Therefore, keep that in mind ;o. Of course, if the self-updater didn't work ok, then I assume you got the full installer and now have the new quick updater that will hopefully do better in the future.

All changes since last beta (may have missed a few):

• Fix.GUI: Added new safeties if process is terminated while operations are being performed upon it (possible cause of some crashes)
• Fix.All: Rundll process name parsing had a spurious quotation mark at the end
• Change.All: Reverted back to our own drop-in replacement for the COM string alloc/free function, as we continue to migrate ancient code
• Change.GUI: Added a little more room for About box information, as it was sometimes vertically truncated with some character sets
• Change.GUI: Updated Serbian translation by Ozzi
• Change.GUI: Optimized a few more pieces of code
• Change.QuickUpgrade: Now does its own closing of running instances, instead of relying on InstallHelper (should fix some issues)
• Change.QuickUpgrade: Can now be used stand-alone, and files will be updated to the right place
• Addition.QuickUpgrade: Added new status bar to show what is currently going on in the background thread
• Addition.QuickUpgrade: Runs better in stand-alone situations
• Fix.QuickUpgrade: Fixed any failure to terminate and some other little issues
• Fix.QuickUpgrade: Fixed issue where error messages were in the background
• Fix.QuickUpgrade: Reduced max wait time on Stop command
• Removal.SFXQuickUpgrade: The QuickUpgrade EXE itself was removed from the SFX, as it is launching the SFX. This will be dealt with more properly soon.

Read More

New silent auto-updater finished up

The new auto-updater in this beta series has been fixed up and overhauled with a new status bar and working cancel and restart capabilities. It auto-starts and auto-terminates, of course, but still sometimes that is needed. It also fixes problems with previous editions.

This will be available in v4.09.26 beta, or possibly sooner as a stand-alone download. Remember, if used internally, you will be using the LAST rendition of the auto-updater for this next update. That is, unless you use one of our direct links to the newer updater.

Note that it ALWAYS does an update/reinstall. It never cares if the version is newer or not. The product itself takes care of that requirement. Speaking of that, the new updater in it with change log is the next thing to finish.

UPDATE: More work occurred after posting, but I'll soon have a new build, so it is of little consequence.

Read More

How the minidump works

I've had someone ask how to submit a minidump. Well, you get to do that when/if the crash happens. When/if Process Lasso crashes, you now see a message box telling you that a minidump was generated, and asking if you would like to open that folder. This makes it easy for you to ZIP and submit minidumps to Bitsum Technologies. Using this minidump, we can hopefully get a better idea of the cause or location of the crash. It remains to be seen just how useful they'll be, but we'll see. Be sure to ZIP or RAR before you send, as they can be quite large (especially on Vista+ x64 systems).

Now on to finishing this on up. I will soon have a release candidate for v4.1 I believe. There are some remaining features and the updater needs a lot of finishing and polishing, but we're really not far at all.

Read More

v4.09.25 beta released

The official release of v4.09.25 has occurred.

As I mentioned, this should take care of some of those GUI crashes, and the updater crash for the GUI, as some debug output was marked the wrong type, causing a virtual memory read error on some systems, x32 systems being the most affected. This did not exist in the last final because there was not this debug output there.

Read More

Fixed crash when checking for updates

I found the cause of the crash in the newer code. This would manifest as a seemingly random crash of the GUI (background update check), or when you did an update check -- but only when an update was available. The cause? A simple typo/mistake with some debug output (type defined wrong, causing failure under some cases). This will likely solve many/most cases of unknown GUI crashes in the most recent beta series.

This crash fix, amongst other fixes, will be available in v4.09.25 beta.

Read More

New Beta, and a warning

Note to some Vista+ users of the last automated BETA(only) update: It may have lowered your UAC level of Process Lasso, so you may need to reconfigure that and end up re-running the installer to be safe and sure. I discovered this bug in the beta series and wanted to convey it.

I have fixed the problem with it saying 'Can not Terminate all instance of Process Lasso' and am going to be issuing v4.09.25 beta soon. This is getting closer and closer to 'there'.

I've also got FULL minidump support. In the unfortunate case of a crash, no more lame non-working 'restart me?' prompt, instead a minidump is generated and you can optionally send that to me. Combined with archiving of critical debug files for every release and edition, it allows to 'take me to the crash' in many cases. I expect it to improve QA time and quality substantially (yes, there is a QA of QA ;p).

Read More

Valentine's day - What?!

What kind of holiday is this? Women get whatever they want, usually silly absurd things, and men get screwed (if they are lucky). Oh well, back to work after this torturous holiday. I soon will have a new beta with the aforementioned minidump support and improved auto updater (remember, improvements lag a build behind). More improvements coming, of course, all over...

Read More

Escalating QA: Minidumps

Ok, in my short-term haste I've made my own life harder by not using minidumps. That changes now. For all FUTURE builds when a crash occurs in Process Lasso a minidump will be generated. You can then send me that minidump and I'll have a much better idea of what just happened, and be able to fix it instead of willy-nilly around with code review or replication.

Now, this hasn't been just flicking a switch - We've had to code proper support within the application and within the build and release framework. In the long run, it will save considerable time though.

Don't worry, again we are taking extra time to preserve Windows 2000 support ;)

Read More

v4.09.24 beta - quick update

In some prior betas there was an extra zombie instance of the governor at boot, depending on the speed of the boot. This fixes that problem and updates the Russian translation (an important update given its rarity and direct RC translation), amongst other languages.

You can try the automated updater now too. I haven't even tested it myself in anything but Win7 x64, so that's where it is - but it should be fine (famous last words). In a worst case scenario, use the proper installer.

Enjoy.

Read More

Screenshot of quick upgrader

As described this stand-alone updater 'just does it'. You don't even need to click Start, it auto starts and auto closes. It still needs refinement. I am adding a Status bar to indicate connection status, hence the extra space left at the bottom. None-the-less here is a screenshot showing it downloading the update successfully and about to extract and self-terminate (I had to be quick with the screenshot, lol).

The cool thing is that I can put this up for download and it can upgrade even older versions. I haven't yet packaged it to do that, nor am I ready to, but I can, and may. I may say 'Upgrade by clicking here'. Of course, some constraints exist. In cases where the installation has substantially changed I may have to force a re-run of the installer, *or* make the changes myself.

Read More

If you really, really want to play...

For the curious, and although there are other extensions as well, if you want to see just how fast the update is (and I actually slowed it down because it was faster than the disk), then open the command prompt. Go to the PL installation directory. Then run QuickUpgrade.exe. This will upgrade your copy (to the current version). It still needs refinement, some tweaks and fixes, etc.. but there it is.

Read More

Releasing new beta, but you won't get to actually use auto update until next release

This new beta version has the long anticipated, and rumored to not exist, auto-update mechanism. It is revamped. Depending on your download speed it can take as little as 2 seconds to update your installation. No fuss, no mess. It just does it. For now, I've just got a button 'Try automatic upgrade'. In the future, I'll use this as the primary mechanism, once it is well tested, and turns out to be suited for the job. So, the NEXT update you'll get to actually try out this mechanism. I think it should work well. It self-downloads, which may be the only point of contention, though does use the general Internet Explorer settings as far as proxies go.

In the meantime, as always, this is a beta so may contain bugs or other errata. So, now you all will be waiting for me to issue the next update, eh? ;)

Again, this is a beta version. In fact, minor issues are KNOWN to exist. Some things I've had reported I've not yet fixed. The good news is you can use this cool new updater to get the fixes ;)

This new version is v4.09.23 beta and will be coming in the next few minutes after this post.

Read More

It works ;)

I'm proud to announce the new silent, automatic updater. It will be extended as time goes on, but I am about to publish the coolest little utility. Run it, and PL is updated. In future builds of Process Lasso, it will be run by Process Lasso for automatic updates. It is nice to see it up and going ;)

The allowance of this feature is actually the culmination of significant planning. Now, not every update will be silently and automatically updateable, but I'd guess 99% will be.

Read More

How the new automated updater works

The new automated updater is an independent EXE with independent resources. Once run, it does this simple task:

• Download appropriate update for version X
• Shut down Process Lasso
• Replace necessary files
• Restart Process Lasso

It may not work for everyone, but will for many. It will do all the above without user intervention, if they've selected to that.

This will be available in an upcoming beta soon. You WILL be able to try it out on the next beta upgrade because I'll provide a direct link to this new updater.

What's even better is that we are making this thing look cool with a few graphics and dancing unicorns ;). Ok, ok, no dancing unicorns, but I thought it was a good idea.

Read More

v4.09.22 beta looks good, moving on

I've already moved on to several new features, including properly checking the new 'Exclude from ProBalance' feature found in the LOG right-click context menu. That's right, you may not have noticed it -- but there it is. You can exclude a process no longer running without having to go through all those dialogs. I may expand this to simply include the entire standard process context menu, time will tell.

Since I've got a relatively good build out there, I'm going to stick with it and bunch the next batch of enhancements and fixes together.

In the meantime, as I analyze and go through this corporate crapware that has decided to try to copy my ProBalance algorithm. Stay away from them! In my opinion, they are much more concerned with separating you from your money rather than making a good product. I will grant them better artwork, no doubt about that.  However, fancy graphics come at a price in resource consumption, don't theme well, and often are incompatible with accessibility applications.

Well, my two cents... I'll issue an update 'soon' that will blow your minds. I hope to get that automated update finished, as I am tired of updating and want it to handle itself, like Google Chrome. I think I've got it all worked out now, I had the final epiphany last night. I think I can make it work in near 100% of installs, which was my aim.

Read More

v4.09.22 beta - Quick upload to address new default power schemes

I was notified by a tester that the default power schemes did not work in v4.09.22 beta, so wanted to issue a quick fix for that. I also wanted to issue a new build before I embarked on larger changes headed towards the completion of v4.1. I have shuffled the deck a bit, some sudden and wonderful things are coming.

Read More

Process Lasso v4.09.21 beta released

After considerable more digging than I anticipated, I have released a new BETA, restoring public access to this new beta series. I am working hard here to get this finished and v4.10 released.

Please note that some users who were using the previous betas may now notice the traffic light icon on more often. It comes on during periods of high loads or when other actions are being taken by the governor. In the previous betas, it did not, so don't be surprised. If it stays on *and* your CPU utilization is not 100%, then something may be amiss in the new beta though.

As always, exercise caution when experimenting with new beta versions. Thanks to all those who test these versions and report their experiences.

Read More

CNET picks up v4.00.33, download links from them available

CNET has picked up our last stable/final release of v4.00.33. Release of the new beta is pending, but shouldn't be much longer at all. As an aside, Process Lasso is now ranked #15 in its genre. Keep in mind, it is one huge genre. I'm glad to see it rise above the crapware though, and thank the users for keeping it there.

Or get the 64-bit build

Read More

Recent betas (only) may have issue applying user rules or defaults under some circumstances

A bug was discovered during testing of our most recent beta. It is being corrected in v4.09.20, coming soon.

The last final/stable version, v4.00.33, nor its predecessors are affected at all. -- NOT affected. This is a beta2beta problem in the new series only.

Read More

New installer - our own

I was considering what would make Process Lasso less 'retro' looking without having to do a complete UI overhaul and break accessibility support for the disabled (something many have emailed to appreciate, just FYI to other developers).

My brain tells me the installer. That's where I can do it better. I can make it automated. I can make it pretty. I can make it custom. After all, the things an installer does are pretty simple and straight-forward. Create few files, create a few shortcuts.

I don't know when this will occur, but you'll see it in the near future.

Read More

v4.00.33 - a new build from a rebuilt development VM

I decided to switch *back* to Windows 7 as my virtual development environment. Why? After extensive testing, I found that it actually performs better on my hardware than does XP. There are a multitude of factors, so we can only surmise why. Mostly, the integration with VMWare Tools is better. The copy&paste quit working in XP. So, anyway, we're back to Windows 7 x32 as my 'virtual build environment' where I keep the last final/stable release. My 'primary build environment' is the physical host, running Windows 7 x64, for those who are curious. This is where the betas, or a brand new stable build are built from.

All in all, v4.00.33 should be a good build. I was tempted to make other changes, but stuck to the script of fixes only. I did update a few languages from translators who have been perfecting their work.

A new beta is coming soon, once I finally complete the last steps on the new updater and track down a few bugs.

So, enjoy ;).

Read More

Back to it..

As I get back to coding, planning both a new final and new beta, I wonder why it is I feel another tooth starting to hurt. WTF is wrong with my body. I have to freaking use big fonts. Man, I am freaking old - 32. Feels more like 45.

Anyway, as I said, I do have a new final that is coming too. This is to fix a bug I've been aware of, but hadn't yet fixed until now (the 'processes sometimes show as restrained in GUI even after they have ended restraint'). Turns out the problem was simple, the boolean telling the core engine to send that notification wasn't getting set, causing it to tell the GUI 'just whenever' something else happened. While this was a cosmetic defect, and didn't impact functionality, I feel it is an important fix. The big promotion and such got me away from the work I should have been doing really perfecting version 4. Live and learn, or just live if that fails I guess ;).

Read More

Darn tooth pain, freaking ouch

Ok, in all the coding and sugar, maybe, just maybe my dental hygiene hasn't been top notch. I'm now being punished with excruciating pain. The good news, it keeps me from getting side tracked on anything else. Anytime I stray from the day's plan, I am put back in place by excruciating pain. I'd go to the dentist, but well, the last dentist I went to made matters worse in many ways, and second, I've always hated dentist. I would rather pull the damn back molar out myself than have another dentist go mucking around carelessly in my mouth. I won't even get into the whole amalgam filling controversy, something my previous dentist didn't warn me about as he accidentally dropped some down my throat. Oopsie.

While exposing me to significant levels of Mercury after convincing me to use the amalgam filling because it was easier for him, I'm still not convinced I even had cavities. He showed me an X-Ray, and I swear I didn't see it... I even questioned it, but you know, he's the Dentist. I wouldn't put it people (in general) them to do a few extra fillings, just like some mechanics, doctors, and about any other service that you pay for. There are good people and bad, last time I ran into a bad one.

So, I figure, at best my chances with a Dentist are 50/50 of them making matters worse.. and 70/30 for them making matters worse for at least a week. Maybe if I can coat the tooth with enough fluoride then I can create a barrier and the tooth can later repair itself (yes, they do that, contrary to popular belief by the orthodoxy who drills and fills) through my proper hygienic procedures. Of course, it can't grow back, but the enamel can harden.

Anyway, I will send a picture of my bloody mouth if I do use pliers to pull my own tooth out. It should be entertaining. Perhaps video is more appropriate. It sure will be cheaper, and sure will be as effective.

Read More

Oh the frustration with this corporate crapware!!

I now get uninstall feedback, as I solicit it (for better or worse). Once read, I can never go back, lol. Fortunately, most of it is actually positive, planning a reinstall, etc.. Anyway, I did have one German user say that he found a superior product. I went and checked it out. It did nothing like Process Lasso, but was a 'PC optimization' type utility I suppose. It hid its 50+MB memory presence with a little trick (paging yourself out). Most authors do it these days, sadly, to hide their true memory footprint. That is why Process Lasso shows the commit size before the working set in its display.

Needless to say, if you have a slow PC, the last thing you want to do is load up a highly resource intensive application that is always running in the background.

It also took a good 5 minutes to install. Ugh. Terrible software. Terrible.

The good news is that there was not one single choice or option, and I guess that is how most prefer it.

I just want to say, to those who believe there is ANY utility that can possibly come in and solve all your PC problems automagically -- it is NOT going to happen. The complexity of software environments is so great, especially when malware is thrown in. No utility can do it all and any that claims 200% speed improvements and the like is BSing you. Your BS alarm should go off right there.

All I'm saying.. is I've looked.. and don't get suckered by these companies. On the flip side, I need to start tightening down my own licensing some it looks like ;o. Just know, I'm not with 'them', lol.

Read More

Bug found when exiting 'No Sleep' mode

A user reported a crash in the core engine. Giving me accompanying information (and INI, and LOG files), I was able to track down the problem in about 5 minutes. It was a typo, as most bugs are I suppose. Anyway, this was part of the new inter-process communication brought in v4, so only applies to v4+. I have fixed it in a silent update to the last version, a quick new beta refresh is coming shortly, and new official builds coming soon. The new silent update of v4.00.32 is build 89900 with a build date of 2/3/11. It is NOT yet available at the time of this posting.

I don't like being so confessional about mistakes, but that is part of getting QA where it needs to be. I'm leaving no stone unturned and fixing all user reported bugs I can identify. I am also improving all test beds and automated testing, as always.

Read More

Improving on the last betas

I've been doing lots of improvements from the last betas, or even the last final, and am eager to issue a new build. I'm going to try to make sure my ducks are in a row before I release another mishap like v4.09.16 beta was, lol. That said, they are betas.

Read More

v4.09.18 beta issued

I went ahead and issued v4.09.18 beta to correct the immediate mistakes, now back to development work. Note this, as with the previous builds, as a beta so problems could (and do) exist.

Read More

v4.09.16 beta and v4.09.17 beta

I released v4.09.16 beta, then discovered I didn't quite finish my testing. I fixed it up, except apparently in XP/2K where the context menu is broken. I'll fix this shortly. These are beta builds, and hence the purpose is to identify any problems. Thanks to those who have reported them. There will be a v4.09.18 beta in a few hours.

Read More