Note: Please read the license agreement (FAH504-Console.exe -license). Further
use of this software requires that you have read and accepted this agreement.
The file FAHlog.txt has been locked by the operating system and cannot be
opened for writing (possibly because it is open in another application).
Before you next run F@H, please ensure FAHlog.txt is not open anywhere,
or simply delete it. For now, FAHlog2.txt will be used.
--- Opening Log file [December 1 01:39:12]
# Windows Console Edition #####################################################
###############################################################################
Folding@Home Client Version 5.04beta
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Program Files\Folding@Home
Executable: C:\Program Files\F@H1\FAH504-Console.exe
[01:39:12] - Ask before connecting: No
[01:39:12] - User name: pbrown (Team 36120)
[01:39:12] - User ID: 499E21481F205083
[01:39:12] - Machine ID: 1
[01:39:12]
[01:39:12] Loaded queue successfully.
[01:39:12] + Benchmarking ...
[01:39:15]
[01:39:15] + Processing work unit
[01:39:15] Core required: FahCore_78.exe
[01:39:15] Core found.
[01:39:15] Working on Unit 01 [December 1 01:39:15]
[01:39:15] + Working ...
[01:39:15]
[01:39:15]
TB, I would reccommend she does a search, and dumps all instances of FAH, and starts over. Sounds like the old one is still there.
dfwddr is right. F@H is pulling the existing WU and client.cfg, not allowing you to reinstall the program.
Check your FReepmail.
Life will soon be good.