't Was een ruwe inschatting: ik ben nl. nog niet zo lang bezig
edit:
Aangezien dit 't officiële faq schijnt te zijn
, is hier nog wat aanvullende info:[quote]
Behind a firewall -- Install the program a second time on your home computer (or the one with the internet connection) in a different directory.
Copy that over to your work computer, and run it with the -nonet option. From time to time, move all the files ending in numbers from your work to home - there should be three files for every gene made (something like csum.123456, str.123456, output.chi.123456).
When those files are moved over, run the program from your home computer without any options... you should see it uploading each gene, and finally it will start to work on a new gene of it's own. At that point, press Ctrl-C to stop the program. You should now have a set of files ending in .2 - this is new data to be processed and should be moved over to your work computer. Note that your work computer can keep crunching away this whole time - it will begin work on the new data once the current set finishes.
P.S. If you're running it at home as well, make sure you always keep your work directory separate from the home one... move the files from work into the second directory, and run it from there. And if you have several computers at work behind a firewall, you'll need a different directory on your home computer for each one.
Running Genome@home minimized -- Does the Genome@home program window open on your screen at startup? If you would like the program to run in the taskbar after starting up, click on the MS-DOS icon at the top left of the program window. Select "Properties", then "Program". Change the "Run" option from "Normal Window" to "Minimized".
Increasing Processing Speed
Idle Sensitivity -- This is an often overlooked setting that can be adjusted in Windows 9x to increase the speed of work unit processing. In simple terms, "Idle Sensitivity" controls how sensitive Genome@home is to requests for CPU time from other applications, processes and services. By default, Genome@home is installed with a medium idle sensitivity setting. By lowering idle sensitivity (moving the slide bar to the left), Genome@home will run at a higher priority more frequently, thus processing work units more quickly. Most users won't notice an overall performance difference by running Genome@home at a lower idle sensitivity. To access this setting, go to c:\windows\system and find the file named conagent.exe (you will also see there an ms-dos icon called conagent, but you want the file conagent.exe). Right click on that file, choose "Properties", then "Miscellaneous". You will see the idle sensitivity setting in the column on the left. Note that changing this setting will affect all DOS programs that run on your computer. If that is an issue and you would like to adjust idle sensitivity for Genome@home only, copy the conagent.exe file to your Genome@home directory and make the changes to that file. It is then mandatory that you click on the MS-DOS icon at the top of the Genome@home program window, select "Properties", then the "Program" tab. Edit the Command line entry to point to the path of the conagent.exe file that was copied to your Genome@home directory.
[/quote]
Dit kan ook met het proggie TaskInfo2000 (zie onderstaande link)[quote]
3rd Party Utilities
File Monitor(
Executable/
Setup file: By TheJet. This program monitors the file input.inp to let you know if clients across a network are working. This is useful when a client recieves a bad WU and quits. People have been having problems with this, and this will let them know if a client has a problem.
Crashmonitor: This program checks the G@H... thread every 60 seconds. If it is running, nothing happens, but if G@H... has crashed it will restart it.
On the second restart, it deletes the WU and gets a new one.
Genome Voyeur, by Kevin Scott, is a Windows utility that allows the user to monitor the progress of Genome@home work unit processing.
Molecular Voyeur, also by Kevin Scott, is a slightly more robust utility that monitors the progress of both Genome@home and Folding@home work unit processing, and also includes statistical data regarding completed work units.
Electron Microscope, by Larry Perry, is a Windows utility that allows the user to monitor the progress of Genome@home work unit processing. It also allows the user to set some interesting program options for Genome@home such as hiding the G@H program window. It also allows the user to monitor the progress of up to 4 networked PC's. Check it out.
Special offer for DPC's users:
(rename to TEAMLOGO.GIF)
Aanrader!
Genome Counter, by Esthalan, is a Windows utility that allows the user to monitor the progress of Genome@home work unit processing over a network. It allows the user to monitor more network PC's than any existing Genome@home utility.
TaskInfo2000 is like a combination of the Windows Task Manager and System Information Utility. It visually monitors different types of System Information in Windows 95/98/NT/2000. TaskInfo2000 for Win95/98/NT/2000 shows real time information about all running processes and threads including ring0 VxD threads. For each process, information includes threads, CPU usage, scheduling rate, path, open files, command line, environment variables, memory usage, DLLs, version information and more. Taskinfo2000 can be used to change the priority assigned to the Genome@home program. Normally the program starts with priority = idle. Changing the ghclient program's priority to normal will increase the production of work units.
[/quote]
Om de cliënt te verbergen, kan je gebruik maken van:
[list]
•
HideIt (verbergt cliënt van desktop)
•
Window (Om te het progromma onder W9x te verbergen of weer naar voren te halen)
•
FireDaemon (Om cliënt als service te installeren)
After installation, load up the UI. The screen will look like this:
Type in a descriptive name for the service (we will use "gah" in this example). If you want to, type in a description (we will use "Genome@home client service"). To have the program start up upon reboot, or when a user is not logged in, change the startup type from "Manual" to "Automatic", which is the only other choice . To start the service automatically when you are done with firedaemon, check the "start immediatly" checkbox. It is also recommended that you select the "Auto restart" option as well.
Select the application's working directory. To do this, click on the question mark to the right of the text box, and navigate to the program. Most likely this is in "C:\Program Files\Genome@home." Next up is the application executable. Navigate to the directory as in the step above, by clicking on the question mark to the right of the text box. Once you have reached the directory, click on "ghclient.exe." This is the working executable of Genome@home.
You will not enter anything into the Application options dialog box at this time, as the Genome@home client does not support any client switches or options. Once you have completed all of the above, it is necessary to set the applications priority. Genome@home is very CPU intensive, and it is not recommended that users run it at any priority above "Idle" as the computer becomes very sluggish and unresponsive. To change this, click on the down arrow. Choose the "Idle (runs only when system is idle)" option. Once you have done this, choose the CPU0 option, as this will assign Genome@home to your processor. For those with multi-processor boxes, choose CPU0 as well. When this is done, and if you want to run another instance, repeat all of the steps above (substituting the service name "gah" with "gah2" or something of the like - it is also recommended that you change the service description to be representative of the instance number), and then choose CPU1 for the second instance, and so on.)
• Windows 95/98/Me:
W9xGAH.zip (Lees README.TXT voor installatie)
• Windows NT/2000: (Service Wrapper SRVANY.EXE)
SingleCPU-
DualCPU-
QuadCPU 
This is a wrapper to run the CLI Client as a background service. You can run this service either 24 hours a day, or use the AT command to limit it's run time. System drive is C. You will need to edit the install BAT and REG files if it is something different.
Instructions: Unzip the file to a floppy.
Replace the "ghclient.cfg" with one of your own (from another genome@home install). Go to the machine you wish to install Genome@Home on, put the disk in, and type a:\install.bat)
[/list]
:strip_icc():strip_exif()/u/4622/crop665491830651c_cropped.jpg?f=community)
)
:strip_exif()/u/9778/images%2520copy.gif?f=community)
:strip_exif()/u/3074/crop59297155bb677_cropped.gif?f=community)
:strip_exif()/u/12383/geintje_dance.gif?f=community)
:strip_icc():strip_exif()/u/21018/crop62d14985a5caa_cropped.jpg?f=community)
:strip_exif()/u/18782/gremming.gif?f=community)
:strip_icc():strip_exif()/u/12674/dscn2951_s2.jpg?f=community)
)
en daarna draait ie toch random en dan maakt het niks meer uit. Je kopieert namelijk de eerste gene en de uitkomst daarvan blijft gelijk, daarna gaat ie random draaien en zal het verschillend zijn.
:strip_exif()/u/17383/jagermyster.gif?f=community)
:strip_exif()/u/19153/e.gif?f=community)
/u/24798/60x60.png?f=community)
/u/13318/cafeineavatar.JPG?f=community){kind=avatar}
:strip_exif()/u/6899/tweakers-icon2.gif?f=community)
/u/127/chimera.png?f=community)
:strip_exif()/u/37312/cow_run.gif?f=community)
) naar G@H.
)
:strip_icc():strip_exif()/u/3163/smallcat.jpg?f=community)
:strip_icc():strip_exif()/u/19107/JIS.jpg?f=community)
:strip_exif()/u/24180/weena.gif?f=community)
