There were some minor fixes and adjustments that were supposed to be in the last minor update, but got reverted. I had some 'issues' and had done a 'full revert' to a previous day and lost many of them. These little (cosmetic) changes will be in this next minor update, along with some other improvements to handle a few rare error conditions better.I'm also trying to finish up this new little freeware project for the world. It will be very useful to everyone. Zero revenue, but... helpful ;). Process Lasso remains my top priority, so I can only do...
Friday, 29 July 2011
Sunday, 24 July 2011
Need a 'Pause' button? Here's a trick until we add it
Posted on 09:40 by Unknown
A 'pause' button is coming in the next beta series, but until then a trick to use is to sort by creation time. This is also useful to see what new processes have been created, and when. A lot of advanced users do th...
Saturday, 23 July 2011
RSS links switch back to BITSUM.COM
Posted on 08:25 by Unknown
Using a reverse proxy type with a single line of PHP, I have switched our RSS feeds all to BITSUM.COM. The BITSUM.NET reference feeds still work fine as well. This was important for search and indexing, where I want news feeds about Bitsum.com to be related to Bitsum.com. As always, they are listed here:http://bitsum.com/rsslinks.phpTry not refresh them too often, I like to edit my posts several hundred times after first making them ;p.I could move the entire Forum to bitsum.com this way, while keeping it isolated, and allow use of our SSL certificate....
Friday, 22 July 2011
Process Lasso v5.0.0.37
Posted on 22:37 by Unknown
Changes: [.37]Fix.Core: Fixed auto-reload of config changes might fail to occur for shared, remote configuration files [.37]Fix.GUI: Fix flicker in 'RAM Load', 'Show Graph', and 'Buy Now' buttons when changing window size, it is now very smooth. This was seen most prominently in the 'RAM Load' graph. [.37]Fix.GUI: Fixed issue where lower view tab did not extend to right most edge after activation (to cover space of old buy now button) [.37]Change.Core: A few code optimizations ...
New build coming today
Posted on 03:57 by Unknown
This next build has some fixes I have been eager to get out, but its been held up in this more extensive debugging. I simply had to take some time, get things settled, and make sure they are right before I could release again.After this, although continued maintenance on the current final will continue, I'm going in an exciting new direction. Stay tuned. I don't know how long it will take, and if I gave an estimate I'd just be wrong. I do know this will be what many have been 'waiting fo...
Monday, 18 July 2011
Next build coming, held up in QA as I fix some standing issues
Posted on 03:38 by Unknown
There have been a few little quirks I have wanted to debug and take care of for a while. Some more problematic to debug than others. I am addressing as many as possible in this next build. I hope not to hold it much longer, but I have a list of things I want to make sure are addressed. QA must be the top concern at all times. I've done a lot towards that in the last month, but more must be done. Not having a dedicated QA team means I rely heavily on user reports of problems, and I thank you for that. I'm improving the way and helpfulness in which...
Saturday, 16 July 2011
A jolt of enthusiasm
Posted on 12:25 by Unknown
Things are going to change in a big way here. I realize I've reached a plateau. Process Lasso must now evolve to the next level. That is what we are all waiting on, right? Well, I do have a plan for this, and am working towards it. I don't want to give it all away, and my plans change so often that half of it would be useless anyway.The minor maintenance will continue in the interim, but what I'm speaking of is a shift in paradigm so large that it brings back the excitement we all had when we first discovered Process Lasso (and the excitement many...
Thursday, 14 July 2011
v5.0.0.36 released
Posted on 04:56 by Unknown
Downloads:32-bit: http://www.bitsum.com/files/prolasso.zip64-bit: http://www.bitsum.com/files/prolasso64.zipChanges:[.36]Fix.GUI: Fixed and improved cleanup of auto update files (nothing that would accumulate)[.36]Fix.GUI: Fixed bad alignment of CPU % in listview tooltips[.36]Fix.GUI: Improved code and workings of several configuration dialogs[.36]Fix.GUI: Fixed prompt to save unadded new Watchdog entry in Watchdog Configuration dialog (behaves as others do now)[.36]Fix.GUI: Fixed prompt to save unadded new I/O priority entry in Default I/O Priority...
Nearly done with new configuration dialog cleanup and more
Posted on 03:13 by Unknown
It has been a bit tedious, but most all of the rule configuration dialogs have now been cleaned up and fixed up. Sure, they could always be better, but now they behave consistently and you can double click a rule to edit it (instead of having to remove, re-type, then add it). Some more work will continue incrementally, as I like to do. Also, there was a fix to the at-exit save prompts of many configuration dialogs, as they were not functioning as the user would expect as well, a fact I discovered during testing.Several other improvements are in...
Tuesday, 12 July 2011
Smaller minidumps means more submissions
Posted on 21:26 by Unknown
One of the changes in the last build was that I reduced the size of the minidumps that are generated in the rare event of a crash. They have been reduced in size several hundred percent (from megabytes to kilobytes).Please simply email me any generated minidumps. These are found in the user %APPDATA%\ProcessLasso folder. These help me to quickly diagnose some problems (not all).Of course, most users won't ever see any minidump. They are generated on the rare occasion of a cra...
Sunday, 10 July 2011
Fixing those annoying configuration dialogs
Posted on 03:57 by Unknown
I don't know about you, but when I use the configuration dialogs I think of how lazy the developer must be ;p. I am therefore cleaning them up. It may be a gradual process, not to happen overnight, but they will get progressively easier to use. For instance, the first change is that double clicking an 'entry' (in a list or listview) brings it back up into the editing area for modification. Having to remove then completely recreate entries is absurd. That I let this go for so long disappoints me, but ...On other news, the automated update downloader...
Friday, 8 July 2011
Licensing tightened down
Posted on 23:18 by Unknown
The licensing had been a bit excessively lax, which was not fair to paying customers. It is still far from totalitarian, but it makes sure nobody is getting more than their fair share. I had to go through several sample scenarios to make sure the system works as it should, supporting numerous resellers, license types, differing versions (for some resellers where this matters), and varying update subscription terms.If your activation code no longer works and you feel it should, please contact ...
Tuesday, 5 July 2011
v5.0.0.32 released
Posted on 16:08 by Unknown
[.32]Fix.Core: Fixed issue where watchdog entries quit working when forced mode was on if their time threshold was non-zero.[.32]Change.Core: Improved efficiency of core engine when Forced Mode is on and watchdog entries are active.[.32]Addition.Licensing: New offline activation mechanism ad...
v5.0.0.31 released
Posted on 11:21 by Unknown
Amongst more minor issues, this version updates the core engine Watchdog capabilities. They now perform nominally with regard to time over threshold.[.31]Addition.GUI: Added ProBalance menu option 'Lower I/O priority during restraint' to options menu (was only in dialog before)[.31]Fix.Core: Fixed watchdog 'time over threshold' not beind adhered to in all cases. This is NOT related to ProBalance.[.3]1Fix.Core: Fixed watchdog entries not always being enforced when they should be (sometimes deferred). This is NOT related to ProBalance.[.31]Change.Core:...
Subscribe to:
Posts (Atom)
