Voor de mensen die geen frans kennen hier een engelse babalfisch vertaling:
FoldingRemote WinNT/2K: guide installation and of use (by JWhy)
Etes you administrator of a data-processing park under Windows NT/2K?
Have several computers being functioned under NT/2K, in network, at your disposal?
Please be made turn folding@home on each one of them?
Too lazy Etes you to manually install folding@home on each computer?
If you answered Oui has these questions, then script " FoldingRemote WinNT/2K " is for you!
FoldingRemote WinNT/2K is a script turning only on GCV whose operating system is Windows NT or Windows 2000
This script allows, from a station waiter, to install the version automatically comforts folding@home in service on several stations customers.
It is necessary for that to have the rights of administrator on the network or local administrator on the distant machines.
Read all the article well before starting has to use this script
Considerons that you have a PC waiter turning under WinNT/2K (that has to leave of which you will install and "monitorer" the various customers, by ex) that one will appelera WAITER and 2 GCV customers turning under WinNT/2K that one will call CLIENT1 and CLIENT2
Recuperez the file zip: RemoteFolding.zip (~100K) and dézippez to it (by keeping the tree structure) in a repertoire WAITER (C:\REMOTEFAH, by ex.)
You should obtain this:
C:\REMOTEFAH (4 bat scripts + a textual file)
C:\REMOTEFAH\DATA \ (vacuum)
C:\REMOTEFAH\TOOLS \ (5 executables)
The license of use of folding@home not allowing the redistribution of the software customer, I it provided not with this script!
Copy in C:\REMOTEFAH\DATA \ the customer comforts that you use (or the last available on the official Web site ) and re-elect the fahconsole.exe
Likewise, copy your file of configuration client.cfg in this repertoire C:\REMOTEFAH\DATA \
Do not touch has anything of what is in C:\REMOTEFAH\TOOLS
Approximately, all that I will say for the installation is valid for the desinstallation, therefore all the modifications which you will make to configure the script of installation (INSTALLSERVICE.BAT) will have to be made for the script of desinstallation (UNINSTALLSERVICE.BAT)
It is possible 2 to launch the script of installation:
N time (1x by computer to be installed): by lancant INSTALLSERVICE NOM_DE_L_ORDI
1 time for all: by lancant MASS_INSTALL
launching with MASS_INSTALL requires to know the computers customers.
For that, a file COMPUTERS.TXT must exist containing ONLY the list of the names (not IP addresses) of the customers (1 name by line)
by ex:
CLIENT1
CLIENT2
In all cases (MASS_INSTALL or not), it is necessary to define the parameters which will be used at the time of the installation.
That is done in file INSTALLSERVICE.BAT.
Open it with notepad or your préferé text editor.
All that is between the lines
REM
REM TO BE CHANGED IF NECESSARY
REM
and
REM
REM C FINISHED EAST ONE TOUCHES ANY MORE A NOTHING
REM
are parameters which can be modified to personalize the installation in service.
The current configuration of script, such as you downloaded it, also benefits from it to make more furtive the execution of the service.
Instead of having a Folding@home service which launches a FahConsole.exe file being in C:\FOLDING (enough seeing!) script creates a service mmc (Microsoft Management Comforts) lancant a file mmc.exe being in C:\WINNT\System32\Microsoft\mmc (Ca should be less "visible" for a user lambda)
Attention nevertheless at the time of this kind of acrobatics that:
1. a service of the same name already does not exist!
2. a repertory of the same name already does not exist!
3. a file of the same name already does not exist!
Let us see seeing what one has in the modifiable part of script
Small recall on scripts batch: modify only what is on the right "equal" sign and do not use accentuated characters as | > < & (I believe that it is all)
rem -- disc of installation on the distant ordi
set REMOTE_DRIVE=D
Relatively simple: from which disc the files folding camera will be copied
a letter: C or D (or other...)
C it is ok
D it is ok (if the disc exists)
C: it is incorrect
C: \ it is incorrect
etc...
rem -- repertoire of installation on the distant ordi (without the disc)
set REMOTE_PATH=\WINNT\System32\Microsoft\mmc
Idem: in which repertory want to copy these files: give C:\FOLDING (or comparable) if you do not want to make furtive installation.
The first \ is necessary and the last \ of should not be there
\WINNT\System32\Microsoft\mmc it is OK
WINNT\System32\Microsoft\mmc it is incorrect
WINNT\System32\Microsoft\mmc \ it is incorrect
:\WINNT\System32\Microsoft\mmc it is incorrect
etc...
If the repertory does not exist on the distant machine, it will be created
CAUTION: use well a repertoire dedicated for folding camera since this repertoire will be suprimé at the time of the desinstallation...
Thus if you decide to install the service in C:\WINNT ( BAD IDEA ), at the time of the desinstallation of the service it is VERY WINNT AND ITS UNDER REPERTORIES which WILL BE REMOVED!!! ( VERY BAD IDEA! )
rem -- Name of the service on the distant ordi
set SERVICE_NAME=mmc
The name of the service!
I never tried to put a name of service with odd characters (@, space, etc...)
With you to see whether Ca goes (with your risks and dangers)
rem -- not necessary, but it is possible to put a more explicit name (posts in the snapin)
set SERVICE_DISPLAY_NAME=Microsoft Management Comforts
set SERVICE_DESCRIPTION=Microsoft Management Comforts
When you launch the list of the services from the Control panel, during the posting of the properties of the service, these 2 information is that which will apparaitront... if the SERVICE_DISPLAY_NAME is empty, the SERVICE_NAME will be posted. If the SERVICE_DESCRIPTION is empty, nothing will be posted!
rem -- Standard of demarrage
rem -- car
rem -- demand
set SERVICE_START=demand
Type of starting of the service:
car: the service will start as of the boot of the machine
demand: the service will start only if you explicitly say to him to start (I use this option which enables me to better control my scripts thanks to the planner of tasks: arreter has 7h morning (except the WE), to start the evening has 20h, etc...)
With you to see what you prefer and/or need!
rem -- name of the executable on the distant machine
set REMOTE_FAH_EXE=mmc.exe
Under which name you want that the file fahconsole.exe is copied from the machine outdistances: give fahconsole.exe if you do not want to make furtive installation.
rem -- name of the executable on the machine room (for the copy)
set LOCAL_FAH_EXE=fahconsole.exe
It is the name of the customer whom you copied in repertoire local C:\REMOTEFAH\DATA
Ca can be fah3console.exe, fah.exe or others... With you to see: either you re-elect the file, or you modify script so that it finds its small
rem -- name of the file of config on the machine room (for the copy)
set LOCAL_FAH_CFG=client.cfg
It is the name of the file of configuration being in C:\REMOTEFAH\DATA
Normally you do not have anything has to change...
Verifiez when same that the client.cfg is correctly configured (username, TEAM, etc)
rem -- parameters of line of order has to use
set FAH_PARAMS=-room - service
Parameters of the line of order folding@home...
Nothing to change there either... You can add parameters (- advmethods or other), but - local and - service are necessary!
Veiled, I believe that it is all... Do not forget to save all the modifications which you made!
For the deinstallation, open file UNINSTALLSERVICE and adjust the parameters. There is much less than the script of installation thus if you left yourselves there with INSTALLSERVICE, you will modify UNINSTALLSERVICE without any problem
You should now be able to launch the script of installation according to the method which you will have chosen (MASS_INSTALL or INSTALLSERVICE).
Once again (I will never répeterai it enough ), during the execution of the installation read with attention what it with to post there on the screen in runs before passing to the following screen.
Once that folding@home is installed successfully on the distant machine, it will be necessary to launch the service in the following way
C: \ > netsvc NOM_DU_SERVICE \\CLIENT1/start
To check if the service turns:
C: \ > netsvc NOM_DU_SERVICE \\CLIENT1/query
For arreter service (there is a trap):
C: \ > netsvc NOM_DU_SERVICE \\CLIENT1/stop
The trap is that as a folding camera, there have a customer (fahconsole) and a core (FahCore_65.exe).
However, even if the service arrete correctly with the order given above, it is possible that the core continues to turn (and thus potential problem when you decide to start again the customer, etc...)
Thus once that you arreté the customer, it is necessary to force the stop of the core while making:
C: \ > pskill \\CLIENT1 FahCore_65
The problem, it is that there can is to have several Core (Tinker, Gromacs, Genome, etc...) thus one needs all the arreter (same if they are not perhaps to launch...)
Thus let us imagine that you have 2 CLIENTs with monitorer, it will be necessary for you to launch the following orders.
I largely advise you to create scripts to launch these orders if you need to frequently use them.
I also recommend to you to copy the contents of repertoire TOOLS in your repertoire WINNT, history to have the path and not to have to repair all the way each time!
launching:
C: \ > netsvc NOM_DU_SERVICE \\CLIENT1/start
[... ]
C: \ > netsvc NOM_DU_SERVICE \\CLIENT2/start
[... ]
monitoring:
C: \ > netsvc NOM_DU_SERVICE \\CLIENT1/query
[... ]
C: \ > netsvc NOM_DU_SERVICE \\CLIENT2/query
[... ]
stop:
C: \ > netsvc NOM_DU_SERVICE \\CLIENT1/stop
[... ]
C: \ > pskill \\CLIENT1 FahCore_65
[... ]
C: \ > pskill \\CLIENT1 FahCore_78
[... ]
C: \ > pskill \\CLIENT1 FahCore_c8
[... ]
C: \ > pskill \\CLIENT1 FahCore_c9
[... ]
C: \ > netsvc NOM_DU_SERVICE \\CLIENT2/stop
[... ]
C: \ > pskill \\CLIENT2 FahCore_65
[... ]
C: \ > pskill \\CLIENT2 FahCore_78
[... ]
C: \ > pskill \\CLIENT2 FahCore_c8
[... ]
C: \ > pskill \\CLIENT2 FahCore_c9
[... ]
Like known as the proverb, "prevention is better than cure".
Therefore, if you have questions, do not hesitate to pose them over the forum before starting to use these scripts.
toon volledige bericht
:strip_exif()/u/8454/crop60505b5af36cb.gif?f=community)
)
2)
2):strip_exif()/u/53217/koei1loeiend.gif?f=community)
:strip_icc():strip_exif()/u/47854/Bitchin.jpg?f=community)
/u/68265/tuxcool.png?f=community)
:strip_icc():strip_exif()/u/7270/liss.jpg?f=community)
:strip_exif()/u/55496/mymoodWK.gif?f=community)
:strip_icc():strip_exif()/u/53754/crop5f96dc1010e28_cropped.jpeg?f=community)
Hoe lang is dat wel niet geleden dat ik frans heb gelezen? 
aan ons lenen? We halen die halbewoners maar niet in! 
:strip_exif()/u/82668/koffie-avatar.gif?f=community){kind=avatar}
Je weet toch dat iedere idle-cycle er eentje teveel is /u/80310/joy.png?f=community)
:strip_exif()/u/37312/cow_run.gif?f=community)
:strip_exif()/u/8553/logo.gif?f=community){kind=logo}