Are you running both the gui client 5.03 and SMP client at the same time?
If so stop the smp client and let the gui client complete its work unit but don't let it get another wu by using the -oneunit flag (or whatever the equivalent setting is for the gui client). On a dual core cpu you should not run any other client with the smp client.
The gui client only uses a single core so it will only show 50% utilization.
If you tried running the smp client on the same machine, unless you changed the machine id under advanced settings for the smp client machineid to something other than the default '1' then the clients are conflicting with each other.
So let the gui client finish its work unit (wu) then stop and uninstall it. We never want to delete a WU since it hurts the science.
After it has finished, you have some choices but i suggest you run 2 standard 5.04 clients so you get familiar with them. Since you are trying to get your college to fold, this is the client you should be recommending, and so you should get familiar with it.
Once you have crunched a few standard client wu's and got yourself familiar with it, then you could switch over to the smp client for better point production.
To run 2 standard single core clients on your dual core rig, download the 5.04 text client to a directory eg FAH1. Copy fah1 to a second directory called fah2.
Setup a shortcut to each fahconsole.exe edit the properties on the shortcut (right click on the shortcut to set properties). At the end of the target field add " -forecasm -verbosity 9" ... note the blank before -forecasm.
forceasm will ensure optimizations are used when you restart after a power failure etc. verbosity 9 puts more info onto the console and into the fahlog.txt file so you (and we) can diagnose problems better.
When you run each exe by lanching the shortcuts you will be prompted for configuration parameters.
For maximum points answer yes to receive large wu's and yes to advmethods.
On the second instance, you also need to answer yes to advanced settings and then answer '2' to the machineid prompt. This lets the stanford servers distinguish between the 2 instances on your machine.
I suggest answering no (the default) to 'running it as a service' for now so you get familiar with seeing what is shown on the console. For your borgs at the college, you will run them as a service to keep them hidden from users. This is also the only 'supported' way to run the BETA smp client later. You can change one of the clients to run as a service later, or start with one that way if you want.
Unless you need to, leave the settings for using IE settings and use proxies to the default no.
The correct way to stop a client running on the desktop (not as a service) is to click on its window and type in ctrl-c.
To stop a cleint running as a servcice you need to use the windows services manager interface.
Don't stop the client by closing the window or killing it with windows task manager ... you have a good chance of corrupting the wu if you do.
Hopefully i haven't confused you but post away if you have any questions.
