Clearly, somethings amiss.
Click on the "Quit" button in the V7 client, wait 5 seconds so it can stop the cores it started, and then click on the "Configure" button, and then the "start" button.
When the client starts up, it puts valuable data into the top of the log file.
Then return to the V7 main page, and click on the "Log" button, and copy the first 50 lines or so, into a reply post here, so we can see what's doing.
It is much more difficult to describe, than to do.
If you paste it between code tags (use the Advanced editor), then it will look like this, and be quite easy to read since it keeps the original format.
It will look similar to this:
(the code tags icon in the editor is the # icon)
Code:
05:30:14: <!-- Network -->
05:30:14: <proxy v=':8080'/>
05:30:14:
05:30:14: <!-- User Information -->
05:30:14: <passkey v='********************************'/>
05:30:14: <team v='32'/>
05:30:14: <user v='Adak'/>
05:30:14:
05:30:14: <!-- Folding Slots -->
05:30:14: <slot id='0' type='SMP'/>
05:30:14:</config>
05:30:14:Trying to access database...
05:30:14:Database locked
05:30:14:Enabled folding slot 00: READY smp:8
05:30:14:Starting Unit 01
05:30:14:Running core: C:/Users/adak/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/x86/Core_a4.fah/FahCore_a4.exe -dir 01 -suffix 01 -lifeline 3052 -version 701 -checkpoint 30 -np 8
05:30:14:Started core on PID 3640
05:30:14:FahCore 0xa4 started
05:30:14:Unit 01:
05:30:14:Unit 01:*------------------------------*
05:30:14:Unit 01:Folding@Home Gromacs GB Core
05:30:14:Unit 01:Version 2.27 (Dec. 15, 2010)
05:30:14:Unit 01:
05:30:14:Unit 01:Preparing to commence simulation
05:30:14:Unit 01:- Ensuring status. Please wait.
05:30:17:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
05:30:23:Unit 01:- Looking at optimizations...
05:30:23:Unit 01:- Working with standard loops on this execution.
05:30:23:Unit 01:- Previous termination of core was improper.
05:30:23:Unit 01:- Going to use standard loops.
05:30:23:Unit 01:- Files status OK
05:30:24:Unit 01:- Expanded 2053858 -> 5365960 (decompressed 261.2 percent)
05:30:24:Unit 01:Called DecompressByteArray: compressed_data_size=2053858 data_size=5365960, decompressed_data_size=5365960 diff=0
05:30:24:Unit 01:- Digital signature verified
05:30:24:Unit 01:
05:30:24:Unit 01:Project: 7808 (Run 3, Clone 346, Gen 29)
05:30:24:Unit 01:
05:30:24:Unit 01:Entering M.D.
05:30:30:Unit 01:Using Gromacs checkpoints
05:30:30:Unit 01:Mapping NT from 8 to 8
05:30:30:Unit 01:Resuming from checkpoint
05:30:30:Unit 01:Verified 01/wudata_01.log
05:30:30:Unit 01:Verified 01/wudata_01.trr
05:30:30:Unit 01:Verified 01/wudata_01.xtc
05:30:30:Unit 01:Verified 01/wudata_01.edr
05:30:30:Unit 01:Completed 1070290 out of 1500000 steps (71%)
05:37:41:Unit 01:Completed 1080000 out of 1500000 steps (72%)
05:48:19:Unit 01:Completed 1095000 out of 1500000 steps (73%)
05:58:49:Unit 01:Completed 1110000 out of 1500000 steps (74%)
06:10:16:Unit 01:Completed 1125000 out of 1500000 steps (75%)
06:21:23:Unit 01:Completed 1140000 out of 1500000 steps (76%)
06:31:52:Unit 01:Completed 1155000 out of 1500000 steps (77%)
06:42:18:Unit 01:Completed 1170000 out of 1500000 steps (78%)
06:52:48:Unit 01:Completed 1185000 out of 1500000 steps (79%)
07:03:25:Unit 01:Completed 1200000 out of 1500000 steps (80%)
07:13:51:Unit 01:Completed 1215000 out of 1500000 steps (81%)
07:24:16:Unit 01:Completed 1230000 out of 1500000 steps (82%)
And there are some messages in there, that should be absolutely ignored, if you're reading them:
Code:
05:30:23:Unit 01:- Working with standard loops on this execution.
05:30:23:Unit 01:- Previous termination of core was improper.
05:30:23:Unit 01:- Going to use standard loops.
The above messages are left over errors from years gone by - there are no "standard loops" in the smp cores, so they can't possibly be used.
The previous termination was NOT improper.
For the oddest of reasons, these error messages seem to have a life of their own, and like the comic-book heroes, seem to live forever. Go figure.
But I digress. Post that data from your folding rig, and we'll see what's going on.