Started by davitof, January 04, 2013, 12:33:49 PM
QuoteThere's a group policy setting for this. Go to Start -> Run (or Winkey+R), type gpedit.msc. Navigate to Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Search. Enable the policy "Prevent indexing when running on battery power to conserver energy"
QuotePausing tasks like that is a very bad idea that could massive problems.
Quote from: BenYeeHua on January 06, 2013, 10:49:50 AMAnd I wanna ask, how many background process that you has using the CPU most of the time?I has using Process Monitor to record which background process is using most of CPU time, and I found most of them just less than 10 second... So I just leave the services remain running without disable them to increase maybe 1-5 minutes battery life.
Quote from: edkiefer on January 04, 2013, 01:55:32 PMOP: are you using 3rd party disk defrag ? or is schedulrr not working, setup for you right .
Quote from: BenYeeHua on January 04, 2013, 01:22:39 PMAbout the search indexer, you can try this.And ya, it can be a new feature(for the watchdog/energy saver). If you wanna last longer, you can use windows 8, as they changing "core-parking" into parking the whole core, not the "fake-core".So you can keep i3/i5 with 1 core, 2 threads active, and 2 core, 4 threads active with an i7.
Quote from: Jeremy Collake on January 06, 2013, 02:51:15 AMThat is a good idea except for a technical detail . Pausing tasks like that is a very bad idea that could massive problems. It simply is not how Windows or Windows applications were designed to operate. Data loss is the first of many possible outcomes if that were to be done. Now, CLOSING those applications is another story. This could be done ... and is perhaps what you meant. Hmm, I will have to consider this. I'm working on major additions, and it would be a good one if I can represent it in a coherent way. It still wouldn't be 100% safe, but could be coded conservatively so that if it can't gracefully close a program, it doesn't forcibly do so.
Quote from: BenYeeHua on January 04, 2013, 01:22:39 PMThere's a group policy setting for this. Go to Start -> Run (or Winkey+R), type gpedit.msc. Navigate to Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Search. Enable the policy "Prevent indexing when running on battery power to conserver energy"
Quote from: davitof on January 09, 2013, 10:53:56 AMI am a bit surprised: any user can disable any service any time, so why couldn't Process Lasso to the same? Or are you implying that Microsoft forgot to put a big red warning above this option?
Quote from: Jeremy Collake on January 09, 2013, 11:15:20 AMOn Topic @OP, selectively allowing *some* safe tasks to be paused is a possibility here. These applications could even be 'tested' by doing controlled pauses for a period of time before the user approves them for management. So, this idea has evolved. I think I could implement it fairly easily. However, I need to improve my polish a bit.
Quote from: davitof on January 09, 2013, 11:08:03 AM... but wouldn't this work only on Pro versions? Do Premium versions of Windows allow to use gpedit now?
Quote from: davitof on January 09, 2013, 10:50:10 AM3dr party: Smart Defrag. Smart Defrag has an option to automatically disable itself when the machine is on battery, but strangely it still shows a balloon tip saying it is running in the background even when I'm on battery. I could try to check, but this is difficult to be sure because Smart Defrag is supposed to wait until I stop doing anything before resuming defragging.
Quote from: davitof on January 09, 2013, 10:59:32 AMI guess for most services it is indeed not worth the trouble. But there are exceptions. For example, I think I'd really try to disable my Comodo Firewall because it is doing a lot of access to disk and IMO this is not worth it when I'm not connected. Of course, I'd have to create a special profile "Not connected" because when I'm on battery and surfing via wifi, I definitely want Comodo to be awake!
Quote from: BenYeeHua on January 09, 2013, 12:09:56 PMI wonder why the Firewall need to access the HardDisk?Maybe it is writing the log?
Quote from: davitof on January 09, 2013, 12:59:16 PMBecause the firewall developers are putting more and more antivirus-like functions in their firewalls. Just as some antivirus developers are including firewall-like functions in their application (I am thinking of Avast here). I am not saying this is a good thing. I disabled all the "antivirus" functions of Comodo I could, but it still scans my disk and eats a lot of CPU at times. I am thinking of switching to another firewall, I feel Comodo is getting to heavy on my system. But this is getting OT.Yes, the log might be part of it, but I don't see what log it would have to write when I am not connected ;-)