Windows 2000 Support

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

Thursday, 1 October 2009

Two new features and UNICODE

Posted on 10:29 by Unknown

New Features

Yesterday I released v3.65.2 beta. Amongst continued optimization of the new no-COM code base, I've added a couple new features. Well, ok, one new feature with the other coming in the next build. These are in the new 'When Running' process context menu:
    (when running)
  • Prevent PC sleep
  • Enter High Performance power scheme

When Running Menu Pic Here

Both do just what they say. The Prevent PC Sleep feature prevents the PC and display from sleeping while a process is running. The Enter High Performance power scheme feature switches the PC to the High Performance power scheme when the process is running.

This last feature (Enter High Perf..) is not yet fully completed in the core engine, so I disabled it in this build. It will come in the next. I expect it to be highly useful to many people. Imagine, when you're playing your favorite game your laptop will instantly go into the High Performance power scheme, possibly eking out a little more performance. When you close your game, it returns to the original power scheme.

UNICODE users rejoice!


I'm also happy to announce that the next beta will be the first 100% UNICODE build. Prior to this, I had kept the project multi-byte (ANSI), but transformed select pieces of code to wide characters (UNICODE). Although I wrote almost all the code to easily support either character set by using TCHARs, this transition still requires full regression testing. I figured since I was going to have to do full regression testing anyway, now was the time to finally make the switch.

Silent update to v3.64.3


Lastly, for anyone who cares, I performed a silent update of v3.64.3 final. This build has no real changes. It simply re-enables the warning about the French translation being incomplete. It was also built in a newly created virtual development environment, but that's hardly something that matters to end users. Of course, I did make sure to run it through the usual final build tests since I had utilized the new build environment.
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

  • 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)
  • ►  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)
      • Process Lasso v3.70.2 released
      • Tightening the Governor
      • Process Lasso v3.70.1 released
      • Process Lasso v3.70 launched
      • ProcessGovernor improvements
      • New final coming soon
      • Is Process Lasso Windows 7 ready? - Yes, it is!
      • Process Lasso v3.65.7 beta released
      • Process Lasso v3.65.3 beta released
      • Two new features and UNICODE
    • ►  September (3)
    • ►  August (1)
    • ►  July (9)
    • ►  June (2)
    • ►  May (3)
    • ►  April (4)
    • ►  March (4)
Powered by Blogger.

About Me

Unknown
View my complete profile