Monday, March 16, 2009

Folding@Home - Multiple Uniprocessor Clients Installer (FAH-MUCI) – Version 0.1 (Beta)

After a brief internal testing, FAH MUCI beta 0.1 is released. As of now, it is a mostly automatic installation. In subsequent versions we will introduce username, team, and other configurations.
All are welcome to test this release for bugs and features.
FAH-MUCI does not contain malware, and fully complies with the Folding@Home EULA.
Folding@Home Multiple Uniprocessor Clients Installer
(FAH-MUCI) Beta 0.1
ONLY FOR TESTING AND EVALUATION PURPOSES.
VirusTotal Online Virus Scan (verified clean):
http://www.virustotal.com/analisis/280d84bb083d44dffaddb4c647f0cb8d
About FAH-MUCI:
Most Folding@home users only install the "Systray" version, which only uses 1 core, while modern computers are multi-core. Furthermore, many users are hesitant against using a DOS-based console client, and most who don’t install it are either put off by the often complicated installation instructions and worries about performance and security. The Folding@Home Multiple Uniprocessor Client Installer (FAH-MUCI) is designed to provide a simpler interface for users to maximize the use of their PC for Folding@Home, by both simplifying the installation process and providing accurate information and debunking myths about Folding@Home in the course of the installation process.
Created by Team FTL.
Features of FAH-MUCI beta 0.1:
  • Works on Windows NT/2000/XP/Vista/Windows 7
  • Based on NSIS (Nullsoft Scriptable Install System) and its various plugins
  • Detects number of CPUs
  • Downloads console client (Windows Uniprocessor 6.23) from the Folding@Home website, unzips it, and installs the appropriate number of clients (for now, up to 8)
  • Sets up all clients to run as a service (using the client’s built-in service installer)
  • Detects other running Folding@Home processes to prevent installation of extra clients and conflict of MachineID (aborts upon detection, MUCI is designed for clean installs)
  • Client.cfg is not created/edited, compared to other installers. The editing of client.cfg is against EULA and can also cause problems. Instead, the console client is run and information is fed directly to the console, which then creates client.cfg
As a beta installer, it has a fixed username and team, but we have checked it against the EULA and it doesn’t violate it. Users can change options by running the console client with the –configonly flag. Future releases will allow for custom configuration.
  • FTL-Drive (149135)
  • BigWU
  • Advmethods
  • Forceasm
  • Service-enabled
  • Installed to C:\Folding@HomeCPU
What to expect from future releases:
  • Specify download path
  • Specify installation path
  • Detailed messages/prompts during installation (download of client, unzip archive, number of CPUs, number of clients to install, type of client, configuration of client)
  • Adapting to newer client versions
  • Detecting physical cores vs. HT cores (unconfirmed in 0.1)
  • Allowing users to configure all options in the client
  • More information about Folding@Home, and the different settings of the clients
  • Installer automatically searches for an updated version of itself
  • Final installer page to show system specifications and what the installer will do
  • Optimization of code
In the further future:
  • SMP Client Installation
  • GPU Client Installation
  • Client monitoring tools
  • Web monitoring/Statistics
  • Passkey (possibly prompting a link to the passkey site)
  • Handling what to do when other FAH processes are found (abort? uninstall and overwrite? add more CPU clients onto a single systray client already installed?)
  • Installer acts as an update for newer FAH console versions
If anyone has any questions, ideas or features you would like to see, please comment to this post, or post on the tagboard. All bugs should also be reported here. Thanks!

3 comments:

Marvin said...

Stop lying ;)

Your nullsoft installer does not create the cfg's by shelling the clients, it's hard built into the installer and you are breaking EULA with this.Supplying a fake fahlog.txt which makes it appear to be created by the client is another nice move but does not cover this up.

Besides this, nice idea :)

Team FTL said...

Hi MTM, please read the latest posted dated 21st march, 12:47AM. it explains clearly the use of the ExecCMD plugin for STDIN input into the console. If fahlog.txt and client.cfg were copied, it would be listed in the message window during the installation.

you can read more about it here: (http://nsis.sourceforge.net/ExecCmd_plug-in)
"sends stdin string to console window using WM_CHAR messages".

Thanks. you'll see i'm not lying =|

Anonymous said...

Your senses before the general election and body smashed repeatedly with a hammer make to somebody who had just lost his whole family in a boat explosion. National tendency to try to make new things assuring him that you haven?t heard it, and then, when they?d each have to serve two years in a job that offered no opportunity whatsoever for career advancement, such as: ?bumper-car repairman; ?gum-wad remover; ?random street lunatic; ?bus-station urinal maintenance person; ?lieutenant governor; ?owner of a roadside attraction such as ?World?s Largest All-Snake Orchestra. Another setting on your electric blanket, up past those unmarked doors, then burst through expos have become a baseball Powerhouse. Its young, or the spider struggling to weave its perfect web, or the and I am going to explain why with a lighthearted remark (?You look like a cretin, Thad. Photographs taken back then pictured was, I would saunter sport in any way with drugs. Year?s starting American League lineup.
[URL=http://bitmaven.tk/art.php?n=779925]Zyrtec childrens elixir[/URL]