Review and testing continues

I'm going to be continuing my rather tedious review of every code change and continue testing on all my test beds here. I'm hoping to knock out any user reported errata during this phase of development. RC2 will come soon, then following quickly (hopefully) by RC3 after performance testing is complete. At that point, if no major errata exists, version 4 will be released.

As of right now, I know there are a couple user reported problems that have yet to be addressed. I've fumbled around and stalled on them, waiting for the completion of my own review. I find that carefully reviewed code is often the best method of avoiding errata to start with. It is very similar to proof-reading. Sadly, as with proof-reading, it is difficult to do on your own code -- at least not right away (when you look again later after a break, problems then tend to be more visible).

Besides all this product work, our server-side activation system is getting a bit of a boost too. It is being relocated to a more geographically centered server. This offers better access time and performance during high loads, and it will isolate that server. This will be our third web and third database server needed to keep Bitsum Technologies safely afloat. I say safely afloat because the isolation of each server to its specific task is largely to improve overall security.

Read More

Process Lasso fully tested with Windows 7 SP1 rc1

I've fully tested Process Lasso with the pre-release of Windows 7 Service Pack 1 (RC1), for anyone concerned about this. As anticipated, no problems at all.

Read More

v4.00.8 RC1 beta - More fixes

This fixes the inability to unelevate Process Lasso's GUI from the main menu, amongst other things. It also updates several translations, makes a few misc changes, and has rolled up fixes from about 4 silent updates to the last beta build.

Performance of the X64 build has also been improved, per previous blog post.

Read More

Going back to VC10 for x64 build of Process Lasso (no W2K or XP pre-SP2 compatibility for X64)

I have decided to go back to the newer VC10 platform toolset (compiler, linker, CRT) for the x64 build of Process Lasso. I figure most people using Windows 2000 or XP pre-SP2 don't need an x64 build (or could theoretically use the 32-bit build on a 64-bit system if they needed).

What this means is that the improved x64 optimizations in Visual C++ 2010 will be included again. I think this will keep everyone happy.

I am fortunate that one of the improvements in Visual Studio 2010 was to allow for such easy backwards compatibility, when needed -- as Microsoft has completely dropped anything below XP SP2 from support.

Read More

Pushed out v4.00.07 RC1 update

Some users who initially downloaded v4.00.07 beta in the first few minutes might get notified of an update that is v4.00.07. Just update to it, this is a different build.

Note the below ONLY applies to the new v4 BETA, it does NOT apply to the last final. Also, it only applies to Vista+ users who have chosen to start Process Lasso with elevated rights.

I fixed some relatively large problems with Vista+ Task Scheduler settings after the first build and didn't want to change the version number. It turns out the defaults for new Windows Task Scheduler 2 tasks are totally whack. For instance, little known to me, the default (if not otherwise set) is to terminate a task once the PC switches to battery power. That means for Process Lasso on laptops this beta was 'just stopping' the moment it went off AC power. The same applies to bigger PCs with UPSes. Now, what Microsoft developer thought that 'stop task if switched to battery power' is a good default? Really? The majority of tasks would find this setting ideal? Maybe it was some new 'green' initiative, who knows.

Another, perhaps more serious, strange default is that 3 days is the default task run time. Yes, 3 days. Why 3 days? Who knows. Why would you arbitrarily set the default task runtime to 3 days? How about infinite unless otherwise specified? How about keeping it running on battery power, unless otherwise specified? It is a good thing I checked these, as I'm rarely out of the office and on battery power.

I am continuing to fix up these defaults and will be publishing another beta. I am surprised I didn't hear of this bug, though perhaps users saw it and misinterpreted it.

I'll likely issue another update (silent or not) later, but that goes without saying as this process of debugging continues.

Read More

v4.00.07 RC1 beta silent update

I've fixed more bugs that users have reported in the new beta version. Some have been long standing because I couldn't reproduce or they were rare, but I am dedicated to tracking down every bug report of this new beta before final release.

At this time this is a silent update because I have a couple more bugs to address, then plan to issue another non-silent update. I simply do not want to bother people too often with updates, beta or not.. so long as the fixes are non-critical at least.

Read More

v4.00.06 RC1 beta - Minor adjustments

I've made a few minor adjustments and released v4.00.06 RC1. Testing is going well, and we're on our way to release. I'm glad to have what I believe is a good, stable, complete beta version out there that offers compelling features over the last final.

Brave users may want to give it a try, but it is still beta - so be sure you understand what that means and the potential for errata to exist.

UPDATE: I just issued a minor update to fix the About box being broken in W2K and XP pre-SP2. This was only a problem in v4.00.06 (not v4.00.05), and was due to my experimenting with the new SysLink control in that requires v6 of the common controls DLL to be installed.

Read More

v4.00.05 RC1 beta - Bug fixes to beta

Since I waited until RC1 to begin exhaustive testing, it is no surprise that there were some bugs to fix. Fortunately, I've knocked them out very quickly. While some may remain, we're looking at a decent beta build fully compatible with Windows 2000 through Windows 7.

The aforementioned user (all or current) problem has been addressed and *improved*. It has been *tested* on both Windows 7 x64 and Windows XP x32, and seems to manage the current user or all users just fine. Furthermore, the previously disabled menu toggle 'Manage all users' is no longer disabled in XP.

There have also been cosmetic tweaks and other adjustments. Other bugs have been fixed earlier, such as some regarding watchdog events.

More work remains, I'm sure some minor bugs still exist, and a few things still need to be polished. The bottom line is that I think we've got a good beta build now. We'll see how continued QA and performance testing goes, but we're well on our way.

After months of careful planning and engineering, it is exciting -- and at times frustrating -- ironing out the last few glitches and ensuring performance is as good or better than the previous version.

Read More

Beta version rewrite of 'manage all users' vs. 'manage current user'

As we know, Process Lasso (in its robustness) allows you to configure it so that an individual instance of the core engine manages ALL user processes, *or* configure it so that each user has his or her own instance of the core engine managing only his or her processes.

Well, after optimizing this code in the current BETA, I ran into problems during testing in XP. Depending on how fast certain services start during bootup, the username may not initially be available. In fact, if you have your XP or 2K system in a tweaked state, perhaps it won't be able to resolve the username at all. This caused some problems -- namely that at first reboot the process list might be empty or incomplete (until you restarted Process Lasso).

I am working on this problem now, getting the code straight for Windows 2000 through Windows 7. I'll be done soon, but until then any user affected (their process list is empty, or near empty) should probably just restart Process Lasso after you start up your PC. I have issued a new beta that forces a showing of all processes, no matter which ones are actually managed by the core engine. However, a better update is pending that properly shows the processes that are managed by the core engine (only).

Of course, in Windows Vista and Windows 7, there is a second variable to the equation; whether or not Process Lasso runs elevated to also manage elevated processes of the current user, or elevated processes of any user.

I must admit, I have an unrealistic expectation for my code to be perfect the first go-round. Must be over confidence, lol. I want even my beta versions to always be reliable, and I really won't ever settle for less. That's why this is an immediate priority.

The last final version, v3.84.8, is NOT affected by this problem. It manages processes slightly differently in multi-user environments. Again, please use it until I declare v4 released and ready.

At this time, I can honestly not recommend anyone update to the newer beta unless you are wanting to help me beta test it. It simply isn't 'there' yet, and won't be until I get finished -- whenever that is. Trust me when I say I am more eager than you. I am so close.. but the last few footsteps can't be skipped and we call the race won. No, we race to the very end. Who am I racing with? I dunno ;p. My point is that almost isn't done.

Read More

Fixing bugs, and a synopsis of our versioning policy

Continuing work on v4, I'm fixing up bugs reported by the QA team, and found in my own testing. I have fixed several so far, and more to come. A new build will be released later today. I must say that I am not happy with the state of RC1. I mean, its alright -- but just not all 'clicking' yet (to sum it up). The new release will be v4.00.02 RC1 (yes, still RC1.. I have my own versioning system ;p).

Here is how my versioning works, so you know where we're at:

• BETA = not all features implemented or likelihood of bugs exist
• RC1 = All features implemented and no more to be added (feature freeze). Generally works, but not bug free.
• RC2 = Better tested, bugs squashed
• RC3 = Performance tested, ensured to be as good or better than last final
• FINAL = Fully tested and ready for general use

Yes, it could be said I'm not using RC1 as literally as they should be. After all, it should be a true Release Candidate. Maybe, but again I'll let Microsoft set the example. Their RCs are about like the above system.

Read More

Early testing shows more work to do, but we're getting there

Early RC1 test results have shown more work remains, but we're getting there. What this really marks is me 'having it all done'. Now, we'll iron out the bugs and any parts that don't work. Then there will be version 4 ;). A personal relief for me, and a new contribution to the world.

My PECompact users are rather jealous that Process Lasso has gotten so much attention lately, lol ;)

Read More

v4.00.01 RC1 beta - Newer RC1 beta now available

After a near heart attack after discovering in early testing that the governor in the initial build of RC1 (and recent betas) has a memory leak. I quickly got to work with a fix. This fix has been issued in the form of v4.00.01 RC1 beta (build 83100).

Beta or not, I'm against memory leaks ;o. The thing is that processes these days use so much damn memory that to stand out requires it leak for days, lol. Oh well. This memory leak probably persisted on the last few days of un-pushed beta versions.

The cause was an optimization.. well, an error in an optimization. I'm not going to quit optimizing though, it is important. Most developers wouldn't confess this, and perhaps I'm an idiot for doing so. It happens to every native code developer though on large projects.

That's why we test for it. Thank goodness I did immediately start running tests ;o. Once I found it, fix was within minutes.

Read More

Restraint history fixed up

I've fixed up the new restraint history in the beta. This fix, with others is active in v3.99.41. Now, back to it.. no more updates until RC1.

Read More

v3.99.41 beta released for testing

I've been working the last 7 hours to bring this thing to final, there's just so much to do. Maybe I set the bar too high, too much at once. No matter, I will get it done. I already clipped off the one feature not fully working right (afaik). I am aware of a few more little quirks, which I continue to work on. It just takes time, all simple stuff. I'm also cleaning up the code, ensuring its efficiency, and making final commits and code freezes to specific objects.

Well, this silent update is for testing the latest changes for immediate feedback ... Another build is coming, as always - and I hope it to be RC1 with polished graph tooltips (mythical now, lol).

Ok, this was my break.. quit typing, more coding (yes, I am talking to myself... somebody has to manage me, lol)

Read More

ESR feature deferred

Since ProBalance mostly handles ALL preventable stalls (unless set up wrong), I've decided to postpone the Emergency Stall Recovery feature until v4.1. The issue has been that once a stall has been induced, action can not be taken (because even the high priority thread of the governor is starved). If I make it too aggressive, then it is simply ProBalance ignoring all exclusions -- which won't work.

So, for now, ProBalance will do its job just fine of preventing stalls. In a worst case scenario where an excluded process is the one causing problems, .. Well, you'll have to un-exclude that process or wait for v4.1 ;(.

This decision is the correct one, I believe. It lets me get v4 on out the door. I'm already quite late, at least if going by my self-imposed guesstimates on delivery date. We're there now, and I'm clipping out anything that isn't done (with the exception of the graph tooltips, which I'm polishing before release and finally enabling).

Read More

Process creation log event minor change (note for admins)

Since some network administrators may rely on our log format, another minor change has occured. The format remains the same, no worries. On process creation events, the command line is used if arg0 (pathname) is present. If not, the pathname is prepended to the command line and used. So, count on a 'proper' full command line being in the description column. This was necessary as the presence of arg0 isn't mandatory, and so will vary depending on the parameters used when CreateProcess is invoked (iow, depending on how the process was launched).

This starts as of v3.99.40, coming soon.

Read More

v3.99.39 beta silent update

I uploaded a quick update to address some anomalies found during code review. We're almost there.

I am eating well, and focusing tonight. I will achieve peak efficiency and finish this. It isn't easy, being a one man show, but my many supportive users, translators, and friends make it possible.

I apologize v4 has taken so long. I kept raising the bar on myself. The bar is set now though, and has been for some time. Also please remember ALL the order processing and server side code had to be updated to facilitate our new license activation system.

The good news is that it is a great new version, and a base from which the future can built from. We can do things with version 4 that will amaze you. Just wait ;)

Read More

Performance boost of governor in v3.99.39 great, but cleaning up the code continuing to take time

I am happy to report that my high hopes for the performance optimizations I mentioned before were not misplaced. Upon performing a few benchmarks, I found they have done wonderfully - especially on multi-user environments. If Process Lasso's core engine was lean before, then it is near transparent now in server environments with large numbers of users. Of course, even the home user will see a benefit.

I'm still working to clean the remaining chores up, as I have been saying for a while now. What can I say? There have been a lot of little things to clean up.

One of the many things I've cleaned up is the setting to Manage all users (or not), and to run with elevated rights (or not) in Vista+. These things have been completely polished up and work as you tell them to at install now.

Well, this was my break time. Enough rambling. Back to work.

Read More

Refresh (F5) now also refreshes governor's enforcement of process rules

Refresh (F5) now also refreshes governor's enforcement of process rules. Normally this only happened if you had Forced Mode on, or made some change to the configuration file. Now, if a process has changed from its default setting -- you can easily hit refresh and have the default re-applied.

For v3.99.39 beta *unreleased*

Read More

Command lines now shown in log

Full paths and command lines of newly created processes are now shown in log. As I said, all these things are getting enabled and tested tonight -- we're getting it done and knocking this TODO list down.

For v3.99.39 beta *unreleased*

Read More

v3.99.38 beta - the quick update before the storm

This update restores Windows 2000 compatibility, though I had one report the Active Processes is blank in W2K. I wonder though if perhaps Windows 2000 simply has a lot fewer active applications, lol. It truly does. In CPU use, nothing beats W2K. It is amazing in that way. Of course, it also lacks lots of cool features -- but those cool features could have mostly been implemented in better ways (IMHO).

You've got to give Microsoft a lot of credit for the driver situation though. Remember, they having to develop an OS and coordinate with a large number of hardware vendors to create reliable drivers for PC hardware -- which varies considerably. Sometimes Microsoft has to even create their own drivers when vendors are out of business or uncooperative (or incompetent). They've come a long way in this area. They did what they had to do.

Now it is just a shame Windows 7 doesn't run quite as fast as Windows 2000, despite all its optimizations, lol.

Read More

Kickin' it, old school

Ok, I'm switching back to the old method process icon extraction. The newer method, while more robust, had no real advantage and caused problems in some cases (and wasn't W2K compatible on top of that). Don't worry, my memory saving optimizations are still in place, allowing reduced memory usage by the GUI.

Thanks to MANY people testing our beta versions, I'm confident and am moving forward quickly now. I believe Release Candidate 1 (yes, with graph tooltips) will come within 48 hours. That's my prediction. No, I wouldn't bet anyone's life on it... but I think I can do it.

I may throw out an interim beta real fast to update with the latest improvements before finalizing the new features still disabled and releasing v4 RC1 ;).

Read More

Windows 2000 compatibility restored to v3.99 - (as of v3.99.38, unreleased)

I have restored Windows 2000 compatibility to v3.99. Our new icon extraction code wasn't backwards compatible with Windows 2000. I spent a lot of time on that code, and now I wonder if it is even worth using to be honest. While I debate that, I have uploaded daily beta builds of v3.99.38 here that *should be* fully Windows 2000 compatible:

http://www.bitsum.com/files/daily/prolasso.zip
http://www.bitsum.com/files/daily/prolasso64.zip

Read More

Increase in applications that responsibly manage their own priority class

I'm seeing an increase in applications that responsibly manage their own priority class. This is great news. Google Chrome is the king of them, lowering the priority of background tabs when they aren't visible to Below Normal -- just like ProBalance would have done (if they were active at all). Now I've noticed other random software also being a little more friendly.

Perhaps the importance of lowering your application's priority when you know it is doing nothing that important is a trend that is catching on. Perhaps Process Lasso even helped developers become aware of this need. There is nothing better than an application that manages its own priority well.

Fortunately Process Lasso is designed to work wonderfully with applications that manage their own priority -- by simply ignoring them (unless Forced mode is on). A lesser product might not have a Forced mode (or always have it on/off), but Process Lasso was designed to do things right. I'm certainly not perfect, but do try hard to do things right. I encourage users to keep this is mind when choosing ANY software -- Does it look like the developer cared if things really got done right, or were they more interested in a flashy UI to make a quick $?

Well, from a note about a trend with applications doing better at managing their own priorities to a sales pitch, lol.. quite a blog post here at 6:04am. What am I up doing? Restoring W2K compatibility. I really hope there are more than 5 of you guys left ;).

Read More

Great new progress and new daily builds

I've continued to make great strides forward. v3.99.37 beta has been a stable build, as I predicted. It isn't perfect, as I've already done a lot more cleaning, adding, and polishing since it.

As for latest internal developments: The graph tooltips *will* finally be enabled soon on public builds. I had to both finish them, then ensure they worked efficiently and without problems. Since they are tied closely to the inter-process communication, much of the work has been on it, preparing for the final unveiling of those new graph tooltips. I know, this is the 20th time I've said this -- I'm for real though.

I actually have the power to show tooltips anywhere on the graph, but for now will just show information about ProBalance events. When you're hovering over a highlighted area of the graph, you'll see all events that happened at that time (yes, I support multiple events during the same time interval -- of course).

I've added a new throttle level, for the few that use hard throttling for whatever purpose. I've also changed the existing throttle levels. Note to readers, the throttling I am speaking of is NOT ProBalance priority adjustments. It is a specialized type of CPU throttling.

The process context menu has been improved, so that things you want are more easily found - I think. The dialogs are getting improved.

Every line of code I've changed since v3.84 is getting reviewed. We're almost there.

Thank you so much to those who have stuck with me through this evolution in Process Lasso. The creative process isn't one you always have control over. You can't just 'do it' sometimes. It takes a little inspiration -- and without YOU I'd not have that inspiration.

Daily builds

Daily builds are now available here:

http://www.bitsum.com/files/daily/prolasso.zip
http://www.bitsum.com/files/daily/prolasso64.zip

These builds will have experimental features disabled as with normal betas, but may not be versioned correctly. They are mostly intended for translators who may need to see updated strings in use, etc.. They are also for someone who needs some particular fix *today*, and that fix has been implemented.

Read More

v3.99.37 beta released - This should be a stable beta

To clear up confusion from a botched v3.99.36 beta version, I've released v3.99.37 beta. This *should* be a good, clean beta. I've really got to finish work on the remaining debugging and features, but it was also important a reasonably stable and efficient beta version be available. Here it is.

I apologize for the botched beta release, it happens though (experimental code was in it causing crashes of the GUI). I am simply more determined than ever to get this new version finished with. I am tired of releasing new builds, tired of adding features.. and ready to get this thing (v4) done!

Part of the hold up is that v3.84 is such a good build. I mean, it really is nice, stable, and efficient. To top that requires more than adding new features. It requires really increasing efficiency to offset the additional mass, and it requires lots and lots of QA.

Read More

v3.99.36 beta - Quick official update

This official update, v3.99.36 beta, is another quick update. Since the last official launch of v3.99.35 beta, lots of things have changed though (see list below). ANOTHER build is going to come quickly, maybe by the end of this work 'day' for me. I say day because I've adopted 3rd shift to get maximal focus and minimize distractions.

You will NOT be notified of this update via the update checker if you're using v3.99.35, at least not yet. Like I said, I hope for a better build by the night's end anyway.

(Since v3.99.35 beta)

• v3.99.36 beta build #81800
• Addition.GUI: Added easy menu option to reset entire configuration (all of it)
• Addition.GUI: Added Indonesian language by Ivan Chin
• Addition.GUI: Added Serbian (latin char set) by Dražen Milovanović - Note Serbian Cyrillic is already avaialable and kept up to date by the diligent Ozzii
• Change.GUI: Language selection is now saved in HKLM, but can be overridden by HKCU
• Change.GUI: Switching languages is now done by picking your new language, then restarting Process Lasso (instead of wiping out old pick and restarting Process Lasso)
• Fix.Installer: Fixed language being reset to English on silent upgrade
• Fix.GUI: (beta2beta) Potential/likely fix missing system tray icon in Vista or Windows 7 afer user login (PL GUI was being launched before explorer by the Task Scheduler)
• Fix.GUI: (beta2beta) Fixed positioning of RAM graph outline (group control surronding RAM graph)
• Change.GUI: (beta2beta) Experimental switch back to non-persistent pipes
• Change.GUI: Better handling of user configured selection to manage only their processes, or not (for XP and Vista/7)
• Change.GUI: Faster handling in cases where lots of processes are ignored for one reason or another
• --much more--

Read More

VS2010 - you dog

Looking more into my sudden development environment problem, Visual Studio 2010 appears to get stuck in a recursive memory eating loop as it tries to simply enumerate the resources of my solution for the resource view (showing an entirely blank resource view while doing so). Giving it time, it simply eats up all available memory. So, now I've got to revert to last night's solution and re-do any changes to the solution made since then -- hopefully without causing this strange recursive loop to occur again. My goodness Microsoft ;o. Under NO circumstances should that be allowed to occur.

UPDATE: This was verified to be the cause. Reverting ONLY my .SLN file solve the issue. Visual Studio 2010 actually saved my solution in a way that caused its resource editor to get stuck in a memory eating infinite loop. If this isn't a good example of why ProBalance is handy, I don't know what is, lol ;). Even the best (or not so best) software sometimes malfunctions.

Read More

Build system maintenance, issuing another silent replacement of v3.99.35

I'm going to have to spend a little time repairing my primary development environment, so figured I'd issue another silent update to v3.99.35. This one self-describes itself as v3.99.36, at least partially. An official v3.99.36 (or v3.99.37) release is coming shortly as well, after the build system maintenance and after a bit more work. I've got a lot accomplished tonight already. I'm going to try to keep my stride. This build system problem, which I won't go into detail (VS2010 is a buggy POS), is just a distraction when I was on a roll.

I swear, I wish I would have never switched to VS2010 in v4. In fact, I ended up having to revert to the older CRT anyway to preserve XP pre-SP2 compatibility ;o. The IDE is nice, but dead slow even on modern hardware. This sudden bug is just... inexplicable. To have to waste time either tracking down the cause, or (first) attempting a reinstall is just annoying. How it could just start I have no idea. No, it wasn't because of anything I did. It has simply mis-configured my solution in a way that results in a blank resource view, despite some 70 projects in the solution. That should never be allowed to occur.

Microsoft: Come on guys, you know what I say about VS2010 is true -- you use it. I'll make a deal with you: You get a service release for VS2010 out, and I'll get PL v4 out. Let's fix the world up together ;). I *do* appreciate your ambitions with VS2010, but something is off on the implementation. You need more optimizations and more safety catches, or something.

This is, at least, a reminder of what can happen when even a good upgrade is released before it has been fully tested. Version 4 brings a lot of cool things, but it isn't worth the upgrade until it has been through proper QA.

Read More

Boosting performance, you naughty boy!

I just can't help myself.. I need to be finishing and testing this code, but I keep boosting performance when I see a chance. The next build will perform more optimally on systems where there are a large number of processes skipped for whatever reason (by config or access rights). Basically it 'remembers' these ignored processes better and doesn't have to re-evaluate them. Yea, a marginal bit of CPU cycles unless there are 10,000 ignored processes -- which might be the case on some servers.

Since little optimizations like this are one of many things that differentiate Process Lasso from imitators, I do feel compelled to mention them.

I have been working non-stop on v4. I've gotten many bugs worked out, reviewed a good portion of the code, but it is still beta.. as much as I want it to be release candidate. I'll get it there, don't worry. I'm tired. I'm weary, but I'm feeling good and optimistic. I see the light at the end of the tunnel very brightly. It's all planned, mostly done, just a matter of time and debugging patience to ensure the QA you've come to expect from our final builds.

Read More

Silent update to v3.99.35 beta

I posted a silent update to v3.99.35 beta that includes new languages and certain portions of new or rewritten code. Unfinished things are disabled, as usual. Still waiting on next new beta, as I have a lot more to do before I want to issue it. Update is 'engine' build number 81600 (in about box).

Read More

Dedication to localization - new Serbian variant

For better or worse, it seems I spend about half my time working on, updating, or integrating new languages -- thanks to the hard and consistent work of an army of volunteers. If using anything but English, you have the translator named in the About box to thank for your translation. You should be grateful ;).

We're adding a variant of Serbian. We already have a great Serbian Cyrillic translation from Ozzii, but now have a Serbian Latin translation for anyone who wants it instead for whatever reason.

So, this makes 11.5 languages. Enjoy, and I do hope all this localization work is worth it. I think it is ;).

Read More

Work continues on new beta ...

Ok, I know I delete half the posts I write here, but I wanted to provide a new status update. As I've went through the code review, cleaning things up, rewriting portions, I've decided I'm holding this beta until I get a build I am satisfied with it. I hope to have a build tonight, but I'm keeping it held until it is 'right'. Namely I'm talking about the GUI, as the core engine has been fine in this beta series.

Read More

Indonesian language added - That makes 11

Thanks to the work of Ivan Chin, an Indonesian (Bahasa Melayu) translation will be included in v3.99.36. This will be the first time even he has seen it, so it may still need work -- but it is mostly done ;).

Process Lasso is now available in these languages:

1. English
2. Japanese
3. Portuguese/Brazilian 
4. Russian
5. Serbian
6. Dutch (out-dated)
7. Simplified Chinese
8. Traditional Chinese
9. Italian
10. Finnish
11. Indonesian

That's 11 languages thanks to the dedicated work of volunteers! It has been a lot for me to keep up with, which is why I wrote automated tools to do our own style of localization (info in Forum).

I did also have a Polish translation, but sadly it is too far out of date to include. The Dutch translation is also a bit dated.

Read More

v3.99.35 beta released

I've continued my work in v3.99.35 beta. It is another minor incremental update in the series. I have a larger update pending (as always it seems). I am hoping this build fixes some complaints I've heard, though I'm *sure* it won't address them all.

• Addition.GUI: Added user column to Active Processes tab
• Change.Core: Use binary search instead of sorted linear search on larger process lists
• Change.GUI: Fix Finnish graph legend and possibly other text (I hope)
• Change.Core: INI change certification disabled, as it was deemed useless
• Fix.InstallHelper: (beta2beta) If user selects 'Manage processes of all users' then unselects the auto-selected 'Elevate at login', then it is now implied they wanted elevation anyway
• All.Fixes: Misc improvements and fixes throughout

I'd recommend waiting another build or two if you are hoping for a near done release.

Read More

Bitsum Technologies - Become an affiliate. An opportunity for you?

Ok, now at this stage what normally happens is the developer 'sells out' to some company promising to handle all the marketing and sales. They give over control to these people. I mean, you can understand how it is appealing. I barely have time to code given all the support, business development, and marketing I must do.

But we've all seen the consequences on numerous great software products. You know, you grow to love something, then it is ruined by these professional marketers and managers. These people can't make good software, that's been proven. Only FREE developers make good software. That's because they care more about the code than the bottom line.

Well, I'm not selling out. Now, that may make me a fool and jeopardize my personal wealth, but it 'feels' right. I develop my software because it is my contribution to society, and an extension of me. I am not going to hand over control to anyone else, as they simply won't care as much (by default, no matter who the person/organization).

So, here's to hoping and praying Bitsum Technologies continues to remain profitable. I'll, at least, have low overhead staying a one man show. At some point I do need to develop more business alliances, which I've been working on, to help market the software in other countries. After all, I can't speak anything but English, so can't provide adequate support to non-English speaking customers.

At present our proud partners are:

1. NetTool, Japanese translator and reseller
2. dadagoo, inc., German, Swiss, and Austrian translator and reseller
3. Volker Imre, Commercial German Sales 
4. All the individual level translators that have stepped up to the plate
5. Join the list by emailing us - We need more partners to offload my work without signing my soul away! It may not make you rich, but it might be a fun endeavor.. and who knows what the future holds.

To those waiting for me to finish our relationship; I'm sorry and please be patient. Business development is yet another full time job that I must take on myself ;o. Please do not hesitate to remind me if you've not heard from me on any outstanding issue.

Read More

New releases - but don't get excited

I've released v3.84.8 final. This is a minor update to the last final build. So minor that it simply updates the code signing. Anything else would require extensive regression testing and that's what v4 is for.

As for v4, v3.99.34 beta is being issued. This is a quick update too. The watchdog menus are flaky still because I haven't got to them yet. It does re-add the Russian translation thanks to Dmitry Yerokhin, our very hard working Russian Translator. Russian is the last language not using our new format, which is why it gets disabled when it goes out of date.

The Finnish translation has also been updated and improved, as has other languages. I don't want to start listing credits, as I'll be listing them all night ;o. It suffices to say, whoever's name is in the About box as the translator for your language you should be appreciative of. I am working out ways to better reward these individuals (of course they already get free licenses and more).

A few changes were made though; lots of little fixes and adjustments not worth mentioning. Now that we have a code signing certificate again, and I'm personally 'feeling the code', we'll be issuing new builds rapidly the next few days.

Read More

Finishing the GUI

The last few days have been horrible. I've restored XP pre-SP2 compatibility to the beta series and fixed numerous bugs. Unfortunately not all bugs left in the beta have been squashed yet. I built up expectations too quickly I think, as a couple users will disappointed bug X or Y wasn't fixed. I am getting to them ASAP. Most of the watchdog stuff is still a little flaky, and certain system configurations seem problematic in the beta.

I've done what I can. It hasn't been easy. Version 4 has been a large leap forward. It may not look like much, but it is a platform to build upon. I now can implement new optimizations I couldn't before, and can do other things I don't want to yet reveal.

We'll be final before we know it, but it has to be done right. I can't rush it. I know everyone is eager, and I am too. The more I try to rush it the more mistakes I'll make, which will only slow me down during QA. I'm about 95% complete, so I'm just going to take it slow and steady to cross the finish line.

After version 4 I have several other plans, but one thing at a time ;).

Read More