Windows 2000 Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Tuesday, 23 March 2010

Process Lasso v3.82.3 final

Posted on 23:32 by Unknown
Update confusion
I released Process Lasso v3.82.3 a couple days ago. It has only a few very minor fixes and adjustments to the user interface. I did not feel this update warranted being pushed out to users of v3.82.2. To be clear, users of prior versions (i.e. v3.82.0) *would* get notified of this minor update.

Unfortunately, this caused some confusion, as I've had a few people ask me if the update system is broken. For that reason, I've decided to go ahead and push v3.82.3 out to all users - even those of v3.82.2. I am not sure if this is the right move or not, as I really hate to bother users with unnecessary updates.

What do you think? Should I always tell users of every update, no matter how minor -- or should I continue to leave it at my own discretion? Keep in mind that Process Lasso only checks for updates once a week, a parameter I intend to allow for changing when I finally finish the automated updates code.


My users are the best
I say this every post, but I have the best users in the world. Please, keep telling me of even the smallest anomalies in the user interface or elsewhere. I want a perfect product, and sometimes I miss the little user interface things in QA. I test the core engine well because its testing is automated, but the user interface is much more difficult to test since it requires manually going through each option, etc. I do code review, and try my best, but it is users who make the difference. Yes, I still haven't gotten over the pane positioning anomalies in the first builds of v3.80. Who knows how many users they cost me, and how badly my reputation was damaged. Worst, it hurt my self-confidence, but I'm recovering now. Nobody is perfect, and at least the quirk wasn't something critical like a memory leak.

Memory leaks in other applications
Speaking of memory leaks, I noticed one in a competitor's software the other day. I see these in so many applications. It is no wonder so many users have to reboot their computers daily! I know, I am far from perfect myself, but memory leaks are a serious issue that can cause severe performance degradation as the paging subsystem becomes overwhelmed. For the record, I am NOT speaking of Process Tamer, which is fine software written by my friend Mouser. I will not mention the competitor by name, as I don't want to talk badly of anyone.



Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Process Lasso v5.0.0.28
    This build continues maintenance, fixing several items and also making a nice improvement to the graph's display. Further, the last sele...
  • Anti-virus software - the #1 cause of PC performance troubles
    Many users realize their anti-virus software consumes massive amounts of system resources, and hope that Process Lasso will somehow keep it ...
  • Next update, Options menu gets some changes
    I decided to make the Options menu a little more consistent and move the ProBalnce configuration down with the rest of the rules configurati...
  • Optimizing process icon memory use & New core feature coming..
    Two in one post. Yes, here at Bitsum we're going Green by conserving bandwidth ;). Of course, that's just a joke and I fully support...
  • 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...
  • WARNING: Cracks for Process Lasso may modify HOSTS file
    WARNING:  Cracks for Process Lasso have been seen to modify your system HOSTS file so that you can no longer access  bitsum.com  and/or  bit...
  • Tightening the Governor
    Most users of Process Lasso are familiar with its core engine, ProcessGovernor.exe. It is the silent background process that applies all pro...
  • The many instances of Chrome
    As many readers of this blog may know, Google Chrome is different from other Windows web browsers. It isolates each of its tabs into an indi...
  • Process Lasso and WDFME
    Since Process Lasso can be complex for the layman, something we are working on, I wanted to list a set of steps to address the commonly abu...
  • BETA: Vista startup configuration
    Ok, I've got this fully correct now I think. In some cases in previous builds you could end up with both registry and Task Scheduler sta...

Blog Archive

  • ►  2013 (1)
    • ►  March (1)
  • ►  2012 (6)
    • ►  September (1)
    • ►  July (1)
    • ►  June (2)
    • ►  January (2)
  • ►  2011 (166)
    • ►  December (3)
    • ►  November (2)
    • ►  October (2)
    • ►  September (6)
    • ►  August (12)
    • ►  July (14)
    • ►  June (17)
    • ►  May (19)
    • ►  April (13)
    • ►  March (27)
    • ►  February (31)
    • ►  January (20)
  • ▼  2010 (203)
    • ►  December (23)
    • ►  November (34)
    • ►  October (38)
    • ►  September (17)
    • ►  August (19)
    • ►  July (19)
    • ►  June (11)
    • ►  May (16)
    • ►  April (8)
    • ▼  March (6)
      • In accordance...
      • Can users see through the hype?
      • Anti-virus software - the #1 cause of PC performan...
      • Process Lasso v3.82.3 final
      • Process Lasso v3.82.2 final
      • ProBalance restrain by CPU affinity adjustment fea...
    • ►  February (6)
    • ►  January (6)
  • ►  2009 (43)
    • ►  December (6)
    • ►  November (1)
    • ►  October (10)
    • ►  September (3)
    • ►  August (1)
    • ►  July (9)
    • ►  June (2)
    • ►  May (3)
    • ►  April (4)
    • ►  March (4)
Powered by Blogger.

About Me

Unknown
View my complete profile