it doesnt work for me

here is the log it comes up with

Code: [Select]


Note: Please read the license agreement (Folding@home-Win32-x86.exe -license). F
urther
use of this software requires that you have read and accepted this agreement.



--- Opening Log file [August 12 20:51:32 UTC]


# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: D:\warning
Executable: D:\warning\Folding@home-Win32-x86.exe


[20:51:32] - Ask before connecting: No
[20:51:32] - User ID: 491F6E5D6B5757D4
[20:51:32] - Machine ID: 1
[20:51:32]
[20:51:33] Loaded queue successfully.
[20:51:33]
[20:51:33] + Processing work unit
[20:51:33] Core required: FahCore_78.exe
[20:51:33] Core found.
[20:51:33] Working on queue slot 04 [August 12 20:51:33 UTC]
[20:51:33] + Working ...
[20:51:33]
[20:51:33] *------------------------------*
[20:51:33] Folding@Home Gromacs Core
[20:51:33] Version 1.90 (March 8, 2006)
[20:51:33]
[20:51:33] Preparing to commence simulation
[20:51:33] - Ensuring status. Please wait.
[20:51:50] - Looking at optimizations...
[20:51:51] - Working with standard loops on this execution.
[20:51:51] - Previous termination of core was improper.
[20:51:51] - Files status OK
[20:52:34] - Expanded 3866875 -> 20813811 (decompressed 538.2 percent)
[20:52:37]
[20:52:37] Project: 2611 (Run 1, Clone 355, Gen 182)
[20:52:37]
[20:52:39] Entering M.D.
[20:53:06] (Starting from checkpoint)
[20:53:06] Protein: p2611_POPE
[20:53:06]
[20:53:06] Writing local files
[20:53:07] OX¥J85¿‡IT{LCV
i wasnt planing on continueing this F@H anyway
i just wanted to try it almost as a PC benchmark

why not keep it for it's doing no harm

except my temps are sky high
it sometimes works sometimes prints gibberish
sounds like memory leak 2 me

except if the program had a memory leak others would experience it too.

maybe its a conflict with a driver then
whats with the last log entry?
right now its working but last time it wasnt

its acting up again

why are you asking this in 2 topics

i only posted one topic
its working right now so just ignore the topic