We’ve added to the Bitsum Community Forum the capability to register and login via various social media sites. There’s not much else to say on this one, so I’ll leave it at: Enjoy 😉
Process Lasso v8.6 has been released. This version fixes some minor bugs, adds new connectivity checks for the licensing system, and adds support for next-gen license codes. These next gen codes will come from our new web site that will be unveiled soon.
|22.214.171.124||Addition||Core||Add log entry to indicate if pro-only features of the governor have expired in the workstation edition|
|126.96.36.199||Addition||Licensing||Add internet connection check prior for better error reporting when activation fails|
|188.8.131.52||Addition||Licensing||Show specific error message if next-gen license code is inactive|
|184.108.40.206||Addition||Licensing||Add preliminary support for next-gen licensing system codes|
|220.127.116.11||Addition||Localization||Add Korean to localization pack (not yet available to end users)|
|18.104.22.168||Fix||GUI||Improve error handling cleanup in update check code.|
|22.214.171.124||Fix||GUI||Fix case where internet connectivity check in workstation edition left a TCP connection in CLOSE_WAIT state.|
|126.96.36.199||Fix||GUI||Improve startup speed and fix case where ProcessLasso.exe startup could stall a few seconds if the internet is disconnected as a connectivity check times out (now removed)|
|188.8.131.52||Fix||GUI||Fix solicitation message not shown at first startup for unlicensed users|
|184.108.40.206||Fix||GUI||Fix very small non-repetitive memory leak in connectivity check code (didn’t accumulate)|
|220.127.116.11||Fix||Core||Improve interoperability with latest NIS version|
|18.104.22.168||Fix||Licensing||Fix issue where some users had to enter their activation code again (this can also be caused by bad registry cleaners)|
|22.214.171.124||Fix||Uninstall||Fix case where ‘Bitsum Highest Performance’ power plan is not removed if the user had manually engaged when they uninstalled Process Lasso|
|126.96.36.199||Change||GUI||Set window title to ‘Process Lasso Pro’ to more clearly demarcate the Pro edition. Occurs instantly after product activation.|
|188.8.131.52||Change||Build||Update to latest version of WinRAR|
|184.108.40.206||Change||Licensing||Improve connectivity check to include database accessibility|
|220.127.116.11||Change||Licensing||Extend advanced feature evaluation to 14 days for workstation build|
|18.104.22.168||Change||Localization||Update Italian, German, and Japanese|
Process Lasso 8.2 was released a few days ago and has full Windows 10 support. There weren’t many changes necessary, as we were already prepared. However, there was one auto-start problem that needed correction. We’ve granted eligibility to all single-version promotional Pro users who would of otherwise not been eligible for this update, just to make sure they have full Windows 10 compatibility.
As for Windows 10 – It’s GREAT! The desktop is restored to the center-stage, where it belongs on a PC. It’s got all the enhancements of Windows 8, but more like Windows 7 for traditional PC users. It has improved themes and looks better. Process Lasso actually looks quite well running on it.
Microsoft further made a great move by giving Windows 10 away freely to most users. This will help ensure users upgrade and that Windows remains the dominant operating system for most of the home desktop/laptop and business world. We truly believe you’ll like it, especially if you hated Windows 8, as we, and many of our customers, did.
Below is a screenshot of Process Lasso Pro running on Windows 10.
For those users wondering what happened to ‘Windows 9′, this was skipped to avoid confusion with the old Windows 95/98/Me series, which of course used a different, much less secure, kernel and code base. The kernel in Windows 10 has been changed in version as well, but is essentially NT 6.4 – had they not also changed the NT version number to ’10’. In other words, not much has changed with regards to hardware and driver compatibility, which is a good thing.
To put this in a readable list:
- Windows NT – NT 4.0 – original NT kernel, not used by Win95/98/Me
- Windows 2000 – NT 5.0
- Windows XP – NT 5.1
- Windows Vista – NT 6.0 (major kernel refactoring)
- Windows 7 – NT 6.1
- Windows 8 – NT 6.2
- Windows 8.1 – NT 6.3
- Windows 10 – NT 10 (but really would be 6.4)
I’ve been asked a couple times lately what users can do to return their PC to that ‘brand new’ performance level.
Well, first a bit of bad news — No software will do this for you, no matter what it claims. That’s why, for both security and performance, I recommend, at a minimum, yearly Windows re-installs. Full, new, clean installs – no repairs, etc..
Of course, first thing you should install is Process Lasso and your favorite browser, then make sure you adhere to good and safe usage habits. Don’t install crap with bundles. Don’t install anything that’s unsigned, unless you are really, really sure about it.
I don’t recommend third-party security suites because they reduce performance, and Windows Defender is built-in, though it’s so quiet you may never notice. After all, if security suites were really effective, there wouldn’t be a malware problem, would there? I think their real-world malware detection rate is around 40% at last estimate. They do manage high rates of false positives though. Windows Defender has one of the best track records when it comes to false positive rate, perhaps because they have no interest in selling you anything, so don’t need to scare you over benign objects on your PC.
This will also ensure you have proper data backup habits.
As a side note, if you store your data in the Cloud, use BoxCryptor (I have no affiliation). It enables transparent client-side encryption of data stored to *any* cloud provider, from DropBox to OneDrive, and even supports filename encryption.
The worst fear of any server maintainer is a breach, and not through any negligence or fault of their own. One of the ways you can help protect your server is by making sure you keep critical files under version control systems like Git or Subversion (SVN). Then you can monitor for any file system changes, any remote access trojans inserted, etc.. Of course, limitations apply if the server is fully compromised, rootkit style.
Still, this is an important safeguard and I’m not sure many server admins are aware of it (since they aren’t primarily developers).
We at Bitsum do everything we can to keep what limited data we store (basically your name and contact info) secure.
We continue to knock things off our TODO list, while at the same time working on our new BitsumSDK. This SDK will offer all new features we develop. That way, we can easily expose them in any application, using a shared and inter-operable code base. Much like the ‘governor’ is to Process Lasso now.
Anticipated release date of Lasso 8.0 is in a week or less (yes, that fast). We don’t have much left to do, just to integrate, review, and test — all of which we’re already doing.
We continue to thank our users for their support. Please, our software is very liberally licensed, so we encourage you to buy a license if you can.