Tips Wake on Lan from Power Off State (S5) on Asus P9X79 Pro

My PC built on top of an Asus P9X79 Pro can be waked up from Lan when it is in Sleep Mode (=S1 state) but not when it has been completely turned off (=S5 state). Googling a bit I found the exact solution on Ryan's Bliggity Blog: enable the "Network Stack" in the Bios.

Click to Read More

So, as a resume, here is my configuration:

  1. Windows Power Options
    1. Open Control Panel > Hardware and Sound > Power Options
    2. Click on "Change what the power buttons do" on the left
    3. Click on "Change settings that are currently unavailable"
    4. Uncheck the option "Turn on fast start-up (recommended)"
  2. Bios
    1. Enter your UEFI bios (I am using the latest version when posting his)
    2. Click on "Exit/advanced mode" button in the upper-right corner and enter the advanced mode
    3. Go to the "Advanced" tab and select the entry "APM"
      1. Enable the option "Power On By PCI/E/PCI".
      2. Enable also the "Network Stack"
    4. Possibly go next to the "Boot" tab and
      1. Either disable the option "Fast Boot"
      2. Or if you enable it, enable its sub-option "Network Stack Driver Support"
  3. Network adapter settings:
    1. Open Control Panel > Network and Internet > Network and Sharing Center
    2. Click on "Change Adapter Settings" (on the left)
    3. Right-Click the Network Adapter "Intel(R) 82579V Gigabit Network Connection" and select "Properties"
    4. In the "Networking Tab", click "Configure"
    5. In the "Power Management" tab, yous should now see and tick the option "Wake on Magic Packet from power off state"
    6. Keep the "Wake on Magic Packet" option ticked too (to wake from Sleep State).

All about System Power States can be found on Intel website:

  • System Power State S0 the ON state: The system is completely operation, fully powered and completely retains the context.
  • System Power State S1 the Sleep state: The system consumes less power than S0 state. All Hardware & Processor context is maintained.
  • System Power State S2 the Sleep state: The system consumes less power than S1 state. Processor loses power and processor context and contents of the cache are lost.
  • System Power State S3 the Sleep state: The system consumes less power than S2 state. Processor & Hardware context, cache contents, and chipset context are lost. The system memory is retained.
  • System Power State S4 the Hibernate state: The system consumes the least power compared to all other sleep states. The system is almost at an OFF state, expect for a trickle power. The context data is written to hard drive (disk)and there is no context retained.
  • System Power State S5 the OFF state:The system is in a shutdown state and the system retains no context. Note that in power state S4 the system can restart from the context data stored on the disk, but in S5 the system requires a reboot.

Tips Boost Windows 8 Start-up Process

Although I am running my OS on one of the fastest SSD (a Samsung Serie 840 Pro), I still have the feeling that the elapse time is much too long between the log-on and the moment when I have the hand on Windows. This is due to the Services and Applications run at start-up.

There is fortunately solutions to  optimize your Start-up Process by delaying Applications and Services from starting up as soon as you log into your computer. Doing that, your computer becomes usable a lot faster.

Click to Read More

Delay the start-up of Applications

You can have a look on the applications started with Windows in the Task Manager (CTRL-SHIFT-ESC) > Tab "Start-up".

In that tab, you see which applications have an impact on the Start-up Process.There are several possible values:

  • High - the application uses more than 1000 millisecond of CPU time or more than 3MB of disk I/O
  • Medium - the application uses 300 to 1000 ms of CPU time or 300KB to 3MB of disk I/O
  • Low - the application uses less than 300 milliseconds of CPU time and less than 300KB of disk I/O
  • Not Measured - This could happen with some of the third party apps where windows is unable to determine the impact. An application like BootRacer (Free for non-commercial use) could be used to determine the impact.

Next, install "Startup Delayer" from R2 Studios, a simple but very flexible application used to postpone the startup of applications. You can customize how much you want to delay them and in which order you want to start them. E.g.: as long as there is not enough CPU available. I did delay all the applications that are not critical IMO to use Windows. I.e.: I kept only Acronis (backup), Avast (Antivirus), Audio and Video managers. And all the other ones have been delayed. A simple Drag&Drop can be used to move an application from "Normal Startup" to "Delayed" or "Disabled", or to reorder the delayed ones.

Startup Delayer

In the screenshot of the Task Manager, all delayed applications appear grouped under "Startup Launcher".

Start-up Applications Delayed

Start-up Applications Delayed

A famous alternative to "Startup delayer" is "WinPatrol" but it does much more than just delaying start-up applications. And as always, I prefer simple applications that fit one single need than one big application trying to fit all needs...

Delay the start-up of Services

Services starting up can be delayed via the Service Management console (Services.msc). Use the "Automatic (Delayed Start)" option:

Services Delay

Services Delay

Here are the services that I have delayed:

Delayed Services

Delayed Services

Tips Run MediaBrowser 2.6.1 on Windows 8.1

MediaBrowser 2.6.2 does not run anymore on Windows 8.1.

The problem is that it needs the version 6.1.0.0 of the MS libraries "mediacenter". But the version available on Windows 8.1 is 6.3.0.0. Configuring the adequate BindingRedirect fix the problem.

Click to Read More

Simply edit the config files "Configurator.exe.config" and "MediaBrowserService.exe.config" located by default in "C:\Program Files (x86)\MediaBrowser" or "C:\Program Files\MediaBrowser" depending respectively if Windows is a x64 or x86.

Search for 6.2.0.0 and replace each occurrence with 6.3.0.0 (using Notepad++ run as administrator)

It works for me... both for the service and the configurator ;)
This is a workaround for those who don't want to move from MediaBrowser 2.6.2 to 3...

Here is the Configurator.exe.config file:
And here is the MediaBrowserService.exe.config file: