Windows 2000 Support

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

Friday, 1 March 2013

Process Lasso and WDFME

Posted on 01:51 by Unknown
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 abusive process of WDFME.EXE, a part of Western Digital SmartWare. This process monitors your file system and collects statistics on your file types even when you are NOT using the backup service it is associated with. It is very resource heavy.

Here are the exact steps to make Process Lasso (as of v6.0.2.48) terminate WDFME.EXE every time it is run:


1. First, open Process Lasso's main window. 
2. Go to the 'Main' menu and select 'Run Process Lasso with Elevated Rights'.
3. A dialog box will pop up. At the top of it there is a checkbox, 'Elevate Process Lasso'. It should already be checked, but check it if not.
4. Process Lasso will restart itself, click Yes to do so at the message box.
5. If you don't see WDFME.EXE listed now, then do step 6. Otherwise, skip to step 7.
6. Go to the 'Main' menu again and check (if not checked) 'Manage Processes of All Users'
7. Select and right-click on WDFME.EXE. select the menu item 'Terminate Always [DISALLOWED PROCESS]'


Read More
Posted in | No comments

Wednesday, 5 September 2012

Surprising Benchmarks on AMD Processors - Why the old Phenom II x6 remains a great CPU

Posted on 20:15 by Unknown

Surprising Benchmarks on AMD Processors

The good old x6 Phenom II performs *almost* as fast as the latest unreleased generation of AMD processors!

Remember the last processor AMD made before Bulldozer? The Phenom II? Remember its x6 rendition, the 1100T and its smaller brother the 1050T (iirc). Of course, *now* what were originally all physical processors in the first AMD Bulldozer processor, the 1150 x8, are considered pairs of logical processors. This means that the AMD 1150 would today be marketed as having 4 physical cores, and has been treated by the Windows CPU Scheduler ever since a hotfix to it shortly after the release of Bulldozer.

Well, check out this latest Benchmark from ExtremeTech ...


The good old x6 Phenom II performs *almost* as fast as the latest unreleased generation of AMD processors, running at 700mhz less clock speed! Further, NONE have more than 4 physical cores (as advertised anyway, count them as you prefer I guess).

Therefore, the AMD Phenom II x6 is perhaps the last AMD processor to have 6 fully independent cores for some time. Perhaps they may even command a market premium for this (or should).

The only *problem* is that the AMD Phenom II was constantly in a state of boosting some core frequencies, using its TurboBoost technology. They couldn't clock the whole chip at full load that high, but could clock a few cores a bit higher if the load was not too great. Thus, they made this compromise, but it results in a chip that really has to 'work for its money'.






Read More
Posted in | No comments

Monday, 23 July 2012

Version 6 Goes Final

Posted on 21:26 by Unknown
Version 6 Goes Final as v6.0.0.58

I don't even know where to start with the changes, so I'm going to refer you to two documents. Neither one lists every change that v6 has, but a lot is listed.

Upgrade Guide
Revision History

Process Lasso's priority optimization, I/O priority optimization, CPU affinity optimization, and Watchdog rules make it the premium choice for Windows process setting automation.

Version 6 is an excellent upgrade. It really stabilizes and improves a lot of the code. Of course, I'm not done yet - not ever done ;). 6.1 and 7 are already planned.

In the interim, there will be lots of minor updates - as always. As I test and implement new code, etc...

Read More
Posted in | No comments

Sunday, 10 June 2012

WARNING: Cracks for Process Lasso may modify HOSTS file

Posted on 16:15 by Unknown
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 bitsumactivationserver.com .. OR they may redirect you through a proxy, serving as a man in the middle, potentially compromising you.
Read More
Posted in | No comments

Friday, 8 June 2012

ParkControl updated to v1.0.0.0

Posted on 01:30 by Unknown

This nifty utility, included in Process Lasso v6, lets you enable or disable CPU core parking in REAL TIME, no reboot required. It also lets you set the core parking preferences per power profile.

More FREEWARE from Bitsum. Please consider contributing to our efforts.


Read More
Posted in | No comments

Friday, 13 January 2012

More about Bulldozer

Posted on 15:02 by Unknown
Further on the new AMD Bulldozer architecture, one will see that it is actually made up of blocks of 2 cores. Each of these is called a 'Bulldozer module', and each shares an L2 cache, an FPU, and more. When looking at it from this perspective, this will help people to understand why it is most efficient to *try* to keep the workload on every other core, if possible. Not only for TurboCore, but also due to the intrinsic properties of the platform.


Read More
Posted in | No comments

Thursday, 12 January 2012

AMD Bulldozer hotfix appears - changes Scheduler awareness of CPU from X real cores to 1/2 X real cores

Posted on 19:50 by Unknown
AMD Bulldozer hotfix appears - changes Scheduler awareness of CPU from X real cores to 1/2 X real cores

After appearing briefly a few weeks ago, then disappearing due to reported user complications, the AMD Bulldozer hotfixes for Windows have been re-released, or in the process of being re-released. A helpful supporter of Bitsum pointed this out. Over the course of the day, I noticed an additional download became available (at the first link).


This update DOES change the way the Windows sees your CPU, and can cause Process Lasso to deactivate under some scenarios. This is because it changes the CPU Scheduler's recognition of these AMD processors from (for example) 8 real cores to 4 real cores with 4 hyper-threaded (fake) cores. This is essentially a cheap hack to get performance on par and make use of TurboCore and the intrinsic characteristics of the Bulldozer architecture (e.g. shared L2 cache per 'module' of 2 cores) by telling the scheduler to keep its load on no more than 1/2 of the processors, if it can - and keep any large load off the other cores, if it can.


For example, before this update the below would read "[8 cores: 8 logical]". Meaning, 8 physical (real) cores, 8 total cores.




Now, as the reader can see, the OS thinks there are only 4 real cores, and 4 hyper-threaded (fake) cores. In this way, it is an easy and quick 'hack' to get the Scheduler to play nice with the Bulldozer platform and its 'paired' CPUs with shared L2 caches. Microsoft simply used the pre-existing support for HyperThreaded CPUs.


This will not hurt performance, it will help it. The other cores will get *fully* used under highly threaded situations, they are just avoided. These cores are also now frequently in a 'parked' state, so this update may conserve energy as well.

http://support.microsoft.com/kb/2645594
http://support.microsoft.com/kb/2646060

Read More
Posted in | No comments
Older Posts Home
Subscribe to: Comments (Atom)

Popular Posts

  • 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...
  • Process Lasso v3.65.3 beta released
    I've released the first new beta that is 100% UNICODE. I've regression tested almost all the software, though there may still be som...
  • 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...
  • v5.0.0.18: Fix auto updater in XP
    During testing a few hours ago I noticed the auto-update was failing in some XP installations. Specifically, it would appear to stall at the...
  • 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...
  • Process Lasso v5.0.0.48
    Changes: [.48]Change.GUI: Do not show 'Activate Now' menu item after activation [.48]Change.GUI: Adjusted logging thread CPU and I/O...
  • v5.0.0.17 final - Minor fixes
    This build fixes a reported issue with the watchdog rules (re: not default affinities, priorities, power schemes, but rather the terminate/r...
  • v5.0.0.21: Fix failure of web links within Process Lasso on some systems
    I've had reports of sporadic failure of the web links within Process Lasso. I've analyzed this situation for a while today and found...
  • One bit of bad news, one bit of good news
    One disappointing thing is that I've decided to cancel the change history shown in the update dialog, at least for v4.1. I may add it in...
  • Oh the frustration with this corporate crapware!!
    I now get uninstall feedback, as I solicit it (for better or worse). Once read, I can never go back, lol. Fortunately, most of it is actuall...

Blog Archive

  • ▼  2013 (1)
    • ▼  March (1)
      • Process Lasso and WDFME
  • ►  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)
    • ►  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