Is there a function that detects the death of a slave/node? How is that solved?
The ReFaMo "Energy Saving" feature gives the ability to reboot / shutdown a node when it is inactive after a certain period of time. This feature can be used to reboot a node depending on the CPU % and Time.  Screenshots available inside the manual (page -8-)

..."the application failed to initialize properly(0xc000135). click on ok to terminate...."
Install .NET 2.0 or higher. Available here: Microsoft .NET

What is the Energy Saving?: ..is your friend! Turn it on!
The Energy Saving feature is a very good way for reducing your electricity bill, extent the life of your machines and why not protect our very valuable Earth! Within couple of months Refamo will pay for itself.

Note: The below examples are based using a Renderfarm situation but can be applied to any king of computational intensive project.

For those related with 3D Images or Simulation effects they now that a good result usually takes a lot of Rendering / Simulation time. Especially when we need to render animation sequences. People let their Renderfarm overnight to finish an animation or even a entire weekend. Others run simulations or other computational intensive works for days. In both cases sometimes the Node(s) finish earlier than expected their task or due to wrong parameters or software bug they experience a software crash, ending up with computers running without any reason for hrs or even days.

Refamo Auto-detects when the CPU intensive process is finished and within minutes can specify various scenarios:  For further information download the latest manual

"cannot set up CPU monitor, invalid input string".

This particular problem is caused when your performance counters (in the registry) are corrupted in Windows.  

We are not sure yet which  software is causing this corruption, possibly a spyware, antivirus or badly written 3rd party application.  
First try running the following command from a command line window and  see if it helps:
First, run this:
cd %Systemroot%\System32
Then, for Server versions run:
lodctr /r
Or for XP versions, run this:
lodctr /r:PerfStringBackup.ini
And try loading the node program again.
If this doesn't work, try this fix, by Microsoft for the server line  of products: http://support.microsoft.com/kb/300956

Is it possible to install the Node as a service?
At the moment, the ReFaMo node runs as a user-level application.  It  is quite light and does not take up much resources.  There is no Windows Service version available at this time, although  this may change in the future.

Troubleshooting WOL (Wake On LAN) :
Make sure your Motherboard supports it.

Configuring your Network Card:
In order for WOL (wake on lan) to work, your network card must go into "standby mode" when you power down your computer. If any of your network card's lights are still lit after you shut down, then it's configured properly, and you can skip the rest of this section. Otherwise, if none of the lights remain lit after powering down, you'll need to do the following.

   * Double-click the Network icon in Control Panel, or right-click on your Network Neighborhood icon and select Properties.
   * Select your WOL-compliant network adapter from the list, click Properties, and choose the Advanced tab.
   * Highlight NDIS Driver Version, and change it's value to NDIS 4 (the default setting is Auto Select). If either the Advanced tab or the NDIS Driver Version setting are missing, then you'll need to obtain more up-to-date drivers from the manufacturer of your network card.
   * Also in the Advanced tab, change the settings for Wake on Link and Wake on Magic Packet accordingly, if they're there.
   * When you're done, click Ok, and then Ok again. Confirm that you want to restart Windows when asked.
   * After restarting, shut down and check the light again. If it still doesn't work, contact from the manufacturer of your network card for support.

What are the System Requirements?
The hardware requirements are very low. Any PC can run ReFaMo without any problems. Please refer to the manual for detailed System Requirements.