CNET Download.com adds 'Download Installer' with bundled app

CNET Download.com added their own 'Download Installer' which has the BING Toolbar bundled with it. I noticed this today. It couldn't have been like this long. I was using them for my primary mirror, as they never pulled this before. I apologize to all users, I had no idea they made this change. I no longer direct users to their site for a download. Needless to say, all this 'Download Installer' does is wrap around whatever you are getting to give you the chance to get their wonderful toolbar, or free scanner, or whatever deal of the month they are bundling. This USED to be against their policies for listings at download.com.

Microsoft must really be throwing some money around to get this BING toolbar out there. I've heard they've thrown it out as a Windows Update even. Desperation.


UPDATE: This started about 1 month ago, apparently: https://upload.cnet.com/8301-21_5-20084419-9978525.html?part=rss&tag=feed&subj=DownloadProductReview

Read More

Process Lasso v5.0.0.40

Yes, v5.0.0.39 lasted about 12 hours ;o. During my maintenance I had adjusted some code to use a newer version of a function related to checking if a process was suspended. Sadly, this code had a typo (no 'NOT' in an expression), causing a bug that caused all processes to be listed as 'suspended'. This was highly frustrating to see this, but it is now fixed in v5.0.0.40. It just goes to prove, once again, that ANY change, no matter how minor requires regression testing.

I have some distractions coming up next week that won't allow for extensive work for a period of a few days. However, before then, I hope to get a few things done. There are a few little quirks I want to fix in the existing build, and there's also a second demo I want to release. I've had it in mind for a long time. I'll reveal more soon.

Thanks to all those who continue to support Process Lasso. I've heard a lot of complaints about the nags lately, so I decreased the frequency of ones that randomly show up when you open the main window. They are still there, but very rare now. People should remember, most 'freeware' these days stoops to bundling with toolbars. I don't think the nags are that annoying, you can click right by them. They don't have a timer, no pause. It isn't that bad. If it *is* that bad, you can always buy a license and help support development. After all, here at Bitsum I'm not just working on Process Lasso, I'm constantly creating little freeware tools like the new RegMerge utility to safely import or compare REG files. This freeware work, in addition to the constant work on Process Lasso, is made possible by those who purchase licenses of Process Lasso or PECompact, or make donations.

This capitalist world we live in seems to reward those who will stoop to any level to make a buck. Freeware authors are selling their soul everywhere, including toolbars in their software. If people can not accept that software development requires financial support, then this trend will continue. I personally believe that users should boycott all those who bundle toolbars or other apps. Even if you can deselect it at install time, this policy is simply atrocious. When you download a piece of software, you are wanting THAT software, not that software and 10 little friends to go with it.

I'm no saint, and far from perfect, but even if you can't support companies like Bitsum who refuse to participate in this toolbar bundle insanity, at least don't criticize us for daring to have a non-timed nag in our software that you can click right past. If a single click is that bothersome, buy a license ;).

I know, I know ... the thought of paying for software seems outrageous. If you feel I charge too much, you tell me what price you would pay. My experience thus far has shown that those willing to buy a license will pay a *fair* price. Those not willing to pay for a license will not pay a single dollar. Is this correct? If there's some price I could set to get a lot more people to buy a license, I'd certainly do it. If every user bought it for just $5, I'd be doing great.... if I set the price to $5, would YOU buy it?

Read More

Process Lasso v5.0.0.39

I get tired of posting duplicate content, so please see: http://bitsum.net/forum/index.php/topic,761.msg4059.html#new

Use the nifty RSS feed in your favorite news reader for the easiest way to monitor updates.

From here there are two tracks. One makes more incremental additions and improvements. The other branches to a new beta series with all the larger changes I'm constantly exciting myself about ;).

Now, back to RegMerge for a minute so I can finalize it. It's been quietly released as an early alpha for a while now. A few more things and it'll be good enough to call beta.

Read More

Minor maintenance release this week

I have another maintenance release that continues polishing and improving version 5. This one takes care of some long standing quirks in the GUI and elsewhere. I'll be releasing it some time this week. It could be any day really, though I have a few more reported bugs to investigate before I can release it.

Read More

Exciting new works on the horizon

I have some large changes in Process Lasso under development. I can't reveal them just yet, but I will soon. You're going to see - finally - some exciting new shifts in the product. Now, don't get too excited, this is just addressing some the largest 'issues' with the product - as I see them. Afterwards, there are still a plethora of features and improvements to work on.

Read More

Process Lasso v5.0.0.38

Downloads:

32-bit: http://www.bitsum.com/files/prolasso.zip
64-bit: http://www.bitsum.com/files/prolasso64.zip

Changes:

• [.38]Fix.GUI: Fixed 'CPU %' field on process tooltip in XP/2K
• [.38]Fix.GUI: Fixed Private Memory field in process tooltip in XP
• [.38]Fix.GUI: Fixed 'Manage processes of all users' Terminal Services disabled warning in XP errantly asking a question of the user to re-enable, when no such option was available
• [.38]Fix.Localization: The three-letter word 'Day' was not being localized correctly
• [.38]Addition.Core: Added safety catch for possible unusual error conditions
• [.38]Change.Core: Minor code optimizations
• [.38]Change.GUI: Dialog adjustments for some longer languages
• [.38]Change.GUI: Use dynamic unique ID for system tray icon to address a theoretical race condition in the creation of a new instance after an old instance remained active in an abnormal error condition long enough to prevent creation of the new system tray icon
• [.38]Change.GUI: Process Lasso system tray identifer is now variable between instances, an issue that could have caused problems during certain timing when two copies of the GUI were launched at approximately the same time
• [.38]Change.BuildEnv: Removed unnecessary and deprecated build configurations
• [.38]Addition.Activator: Added version resource to provide description of EXE and more

Read More

Running Process Lasso w/o Terminal Services enabled?

Although the product warns about this repeatedly, I am going to issue a more strong extra warning: Please turn on Terminal Services when using Process Lasso. This services is enabled (Manual start) by default in Windows, does no harm, is necessary for 'Fast user switching', has low overhead, and generally just needs to be enabled. The only users who have it disabled are those who have tweaked their systems with special utilities.

The side-effects of not having it enabled are simply growing increasingly problematic to handle, and I'm uncomfortable with them. Process Lasso already operates with the bare minimum, not mandating Performance Counters like most similar programs.

If Process Lasso has not warned you about this (repeatedly), then it is NOT an issue for you -- so no need to go and check. For Vista+, Terminal Services was renamed to Remote Desktop Services and always going to be available, so shouldn't be an issue.

What's up with this? Well, Terminal Services (now Remote Desktop Services) provides the facility for multiple users to be logged in at once. In Vista+, system services are isolated into a special user session, which is why this service will always be on - it MUST be to facilitate this system service isolation. Process Lasso is designed to work with multiple users, and needs to be able to identify the session and user name. Having to continually add exceptions in cases where the user name can not be retrieved is bothersome, though I do continue to do this, and regression test in environments without Terminal Services enabled.

Read More