Another night of great work, new beta pending in probably 12 hours

Last night I completed a lot more work. In about 12 hours I'll be releasing a new beta version that:

• Completes the new Default Power Scheme support in every way. High Perfromance processes of the past are migrated to this superceding feature.
• Removes High Performance mode completely, replacing it with Default Power Schemes
• Has a few fixes
• Simplifies the governor main loop even further, making it tighter and more efficient than even before
• Limits communication between the core and GUI to only currently used stuff. Previously I was sending all notifications, with the anticipation of future use. However, until that day comes, there is no need to send notification of these events.
• (Already completed) I/O Priority and Default I/O Priority support
• Further updater work as we complete the half-finished new updater. This will be very close to the new v4.1 final release is going to look like.

So, let's get this party rolling for another night and 'bang it out' ;).

Read More

3rd night of excellent coding progress

As a small business owner, and family owner, it is very hard to find good time to code. I'm glad to say I'm a streak and am going to hope to remain on this streak. There will be no vacations. There will be no interruptions. There will be nothing, for so long as I can help it. Of course, I'll be responsive to support and user concerns, but for the most part - it is all code. Wish me luck ;). I've got v4.1 of PL to finish, and a final of PEC to finish... not to mention secret projects 1 through 52 ;p

Oh, and naturally, as many readers can sympathize - I've got friends and family constantly bringing me their PCs to fix as if I'm a technician. They don't know the difference. They just know I'm into computers. That's it to them.

Read More

Default Power Schemes, an introduction

These new power schemes, which will finally be fully functional (configuration dialog and context menu items added) in the next beta, replaces the previous High Performance mode. Processes configured to induce the High Performance power scheme via the previous mechanism will be automatically converted to haver an appropriate Default Power Scheme. This is one of MANY new features in v4.1 It is not all just bug fixes and cosmetic improvements ya know ;). As always, Process Lasso is an evolving beast.

Read More

High Performance processes become Default Power Scheme processes

In an effort to forever increase the robustness of betas, the High Performance processes are being changed to allow selection of ANY power scheme. Therefore, this will allow High/Low/Balanced/etc.. power profiles to be applied when process X is launched. Many may notice this starting to appear in the recent beta builds.

As for High Performance mode processes, I'll auto-convert them to the new format.

Read More

Process Lasso #19 in 'System Utilities' genre as far as download count

Process Lasso #19 in 'System Utilities' genre as far as download count. That's not bad, considering just how many utilities are in this genre (thousands I'd guess). Most are total and utter crap. In fact, most of those out-ranking Process Lasso are, IMHO, quite deficient in their actual behaviors -- though have nice pretty interfaces to lure you in ;o.

Anyway, I'll happily take 19th place, as strange as it may sound ;)

Read More

The systray icon of v4.09.13 beta

Since a couple have emailed very confused by it, let me say that I'm experimenting. The icon remains static, until double clicked - as all who have emailed have noted. Then it works as normal. This reduces GUI utilization to an absolute minimum. Now, do we always want/need that CPU meter? Perhaps I should make this an option? Or perhaps it is just too confusing? I wonder if a new user would be confused, or which they'd prefer?

Oh well, I intend to CHANGE IT BACK, so no worries there. I am simply experimenting.

Thank you all who have taken the time to email me. This is very important, as I need to hear of any troubles or complaints.

UPDATE: I am going to go ahead and upload a build that restores traditional behavior.

Read More

Soooo glad to be back to coding and making rapid progress

I'm making rapid progress on v4.1 (betas already available, as v4.09.x). I think we'll have an end result maybe sooner than anticipated, if QA goes well. I love doing promotions, but they sure to drain me -- all the user support, to which I make every effort with every user (or try to). It seems I fail sometimes, but often succeed. I'm learning to deal with the fact that at a certain point, not everyone can be pleased ;o. Still, I won't use that as an excuse to stop endeavoring to do so.

Then there were other 'complications' that popped up, as life throws at us all. Well, needless to say, I'm back (yes, from a couple days ;o) -- and with a renewed perspective that will benefit the project.

Read More

v4.00.31 - plans changed, quick fix issued, more coming in v4.00.32

I have released v4.00.31. This version has an important change for some users, especially server users. The Task Scheduler of Vista+ was terminating Process Lasso after 3 days of consecutive run-time. This is because this is the default value for new tasks created via the proper Windows COM interface (yes, strange, but..). This did not matter until I allowed 'hard termination' of the task in a previous minor update. I've now corrected the Task Scheduler entry so that there is no execution time limit.

• Fix.Startup: Fixed issue in Vista+ where, if started at login via the Task Scheduler, Process Lasso would be terminated after 3 days of continuous running
• Fix.Installer: Fixed issue where language was defaulting to Maylasian on upgrade (user could select English, but obviously Maylasian is a bad default).
• Fix.Installer: Fixed issue with backup server being case sensitive, and installer of 32-bit build referencing an old 64-bit build (when used on 64-bit systems)
• Removal.QuickUpgrade: Removed due to language assignment bug in a previous version. Will be restored.

Since these embarrassing bugs are of such high importance to those who are affected, I wanted to go ahead and issue it. Note that it does NOT apply to any user running XP or W2K, or any user running Vista+ w/o running Lasso with elevated rights.

Users of previous builds can correct this issue by editing the Task Scheduler entries themselves (if they prefer not upgrade and are indeed affected).

This update notification has NOT been pushed out to end users via the update check mechanism yet, those was pushed to server users. Other users will be notified shortly, probably upon v4.00.32, but perhaps earlier.

Read More

New 5/5 star editor review of Process Lasso

"All in all, Process Lasso offers a wide variety of ways to control how running programs are allocated to your CPUs. You choose the priority at which processes should run and on which CPUs they should run. It is simply your all-in-one automatic Windows process tuner!"

Ref: http://www.fiberdownload.com/Download/25035/Process-Lasso

Read More

Back to work, new beta needs issued

We're in one of the few times when the last final actually has fixes the latest beta doesn't. That's right, I haven't even had a chance to finish the latest beta because of several business occurrences that have left me dealing with support nearly 24/7. I do, after all, promise to provide such - so I do. Thankfully, things are dying down (finally) and we can go on as normal.

A new beta will appear soon, with those new fixes. It also has further improvements.

Thanks to my supporters and I apologize for this delay. Wearing so many hats is quite difficult at times. Now I've got to 'get right into coding mode', while still dealing with the occasional support email.

p.s. There were two other unrelated major business issues to complicate matters this weekend, which didn't help. I don't even want to go into them.

Read More

v4.00.30 final

This release back-ports some fixes I felt were important, and safe enough, to back-port. Unfortunately, my web server seems down for the moment. I uploaded the builds, as I have FTP access. Needless to say, I am TRYING to light a fire under someone's ass.

Read More

QA

I've been working lately (mostly) solely on QA. I am tracking down and fixing reported bugs, and bugs that I've noticed myself. Nothing major of course, else I'd issue an immediate update and be quite freaked out. All software is imperfect though, and these are simply slight improvements. This has been necessary for a while, as sometimes you have to back up and just go over everything again with a fine tooth comb. Moving forward is great, but you can't neglect your base code.

Read More

v4.00.29 final

There is also going to be a v4.00.30 final, so I'm not sure this update should be bothered with. I may not push it out via the update check mechanism. The next build will have included the new updater, to allow for use when the v4.1 migration is ready.

This release simply back-ports some GUI fixes I felt were important. Other minor GUI and cosmetic fixes may also be made and many languages updated.

As I said, when the new updater is completed and fully tested, it will be back-ported v4.00.30 will be released. That will be the last v4 release before the v4.1 final. Well, assuming all goes as planned. I am excited to get v4.1 final out. Remember, this isn't it -- this is a MINOR update to the EXISTING final version.

If you want multi-core hyperthreading optimization and other newer features, they are in the latest beta.

Read More

WARNING: Beware of third-party utilities that adjust process priorities (other than Process Lasso)

Recently I've seen either 'hacked on' additions to existing products, or new products, that have the ability to manipulate process priority classes. I have studied the effects of adjusting Windows process priority classes for years.

While testing the addition of such a feature to a popular window manager, I found it severely mucked things up (on its own). These utilities have several problems:

1. They do not respect application set priorities like they should (meaning if an application sets its own priority, it likely knows more about why than some external utility could guess, and should therefore be left alone).
2. They haven't had the type of 'real world' testing and exposure of Process Lasso
3. They are not conservative in their changes like Process Lasso
4. They can interfere with Process Lasso
5. They simply do things wrong. I know this. They don't. You do, at least now.

I am adding some warnings for some common utilities, but not the gimmicky ones. After all, I'm not going to call someone 'names'. However, in cases where the developer added a feature not realizing its full consequences, I am going to pop up a message and let you know to disable that extra little feature in the application.

Do not confuse this warning with application's that set their OWN priority. For these applications, let them do their thing - as they know what they are doing (most of the time).

Read More

Little teasers I haven't mentioned much in v4.1

Some of the v4.1 (the current beta series) improvements are graphical. Here's a few I haven't mentioned much. More pics coming of the more neat innovations. Development still top priority for now ;o.

Exclude directly from log (user suggestion):

Better application menu for updates:

More clarity in Activation Dialog (that it can be skipped):

These are all now available in the CURRENT beta - v4.09.09 beta. Even more is available, but that's just what I've taken shots of.

Read More

Investigating some bug reports in last beta

The updater is still on the verge of launching, but I'm going to try to get a few experimental fixes in before release. Those of you who follow me will be proud of how long I've kept a version without releasing it, lol. Anyway, it is coming soon.

I must be honest, today was one of those days where the world beat up on me, then I beat up on myself. Accomplishing something always makes me feel better, so that's what I aim today in tonight's work session.

As a side note, I must be getting old as I think my eyes are going out ;o.

Read More

Finish decision to hold or release new beta

Well, in the next hour I'll either pass out and wait for release, or go ahead with beta release. The longer I wait, the more that is done, but I am always eager. I am not sure at this point to be honest. I want to do some extended testing and may not make it. It is coming soon though, and you'll love the new updater. As mentioned several times, it will show you every change since your current version. Maybe too much information in some cases.

I've got some good work accomplished and am on track to delivering the finest and most innovative build of Process Lasso since v4. These new features really should make it v5. However, it is v4.1 -- and it is the build to have (when finished).

UPDATE: I'm holding until later in the day. I want this release right. No screw ups. Even though it is a beta, we all know people use betas and nobody wants a bad build.

Read More

Finishing it up

Ok, here goes ;). I should have the new beta by the end of my work session (8-12 hours). It will have the new updater, fully featured, have several other fixes and changes, and just generally be a giant leap towards v4.1 final. Thanks again to all those who use and support Process Lasso.

Read More

New Updater almost done

I took the bull by the horns tonight and got the application side and server side portions of the new product Updater almost done. I just lack a little more implementation, but it is all designed and properly working. I am eager to roll this out, as I know users have been wanting to see changes before they choose to update or not. Also, I know they want to validate their license prior to upgrade. I've already started putting revisions in the database, which will be the biggest change to get used to. We're almost there ;).

Yes, I do plan to allow for automated updates. In some cases it won't be feasible, but in most it will. So, you can opt-in for those in the near future. That will probably come in v4.2. As you can see from the silent upgrade already included in the ZIP distribution, I am close to achieving that goal. The only remaining portion is having Process Lasso self-download and execute really, easy stuff.

I can not issue a new beta at this time due to the updater being in this half-implemented state. There will likely be one in the next 12-24 hours though, after I get a brief nap. As soon as the implementation is done, it is going up for testing.

v4.1 really will be nice. I am so eager. Gotta do it step by step though, day by day.

Read More

New Year, and v4.1 will start if off soon

I'm pushing v4.1 through quickly (as I've said), so it will soon be your Jan 2011 present ;). There are still several little things to get to, but I will have it done in no time.

As always, I thank those users who have contributed to my small business in any way. Without YOU, Process Lasso simply wouldn't exist (much less be continually maintained and improved). All the planned innovations wouldn't exist, nothing would exist. I'd have some restrictive job, and my creativity would be hampered/dead. So, THANK YOU from the bottom of my heart. I hope to return this favor by helping others to empower themselves. In this virtual age, the means of production can be in anyone's hands. If you have an idea for any sort of virtual good, YOU can make it, sell it, etc... without needing to sign away your rights or have half your revenue taken by some unnecessary middle man. This is the new age, the age where implementing your own creative ideas is possible. The key is merely in following through. Man, has it taken dedication to keep Bitsum running. I do it though, and wouldn't trade it for anything.

Read More