PDA

View Full Version : SMP not working

Douken
03-03-08, 03:18 AM
(I'm sleepy so I'll be quick)

I have dual Core X2 4000+, I'm trying to run SMP client but I get Runtime Error R6002 -floating point not loaded. which leaves me with the Regular Client only... help needed



--- Opening Log file [March 3 08:57:05]


# SMP Client ################################################## ################
################################################## #############################

Folding@Home Client Version 5.91beta6

http://folding.stanford.edu

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

Launch directory: C:\Program Files\Folding@Home Windows SMP Client V1.01
Executable: C:\Program Files\Folding@Home Windows SMP Client V1.01\fah.exe


[08:57:05] - Ask before connecting: No
[08:57:05] - User name: Douken (Team 32)
[08:57:05] - User ID: 7D1976497649
[08:57:05] - Machine ID: 1
[08:57:05]
[08:57:05] Loaded queue successfully.
[08:57:05]
[08:57:05] + Processing work unit
[08:57:05] Core required: FahCore_a1.exe
[08:57:05] Core found.
[08:57:05] Working on Unit 08 [March 3 08:57:05]
[08:57:05] + Working ...
[08:57:05]
[08:57:05] *------------------------------*
[08:57:05] Folding@Home Gromacs SMP Core
[08:57:05] Version 1.74 (March 10, 2007)
[08:57:05]
[08:57:05] Preparing to commence simulation
[08:57:05] - Ensuring status. Please wait.
[08:57:22] - Looking at optimizations...
[08:57:22] - Working with standard loops on this execution.
[08:57:22] - Previous termination of core was improper.
[08:57:22] - Going to use standard loops.
[08:57:22] - Files status OK
[08:57:22] put
[08:59:22] ding@home Core Shutdown: MISSING_WORK_FILES
[08:59:22] Finalizing output
[08:59:25] CoreStatus = 1 (1)
[08:59:25] Client-core communications error: ERROR 0x1
[08:59:25] Deleting current work unit & continuing...
[09:01:45] - Preparing to get new work unit...
[09:01:45] + Attempting to get work packet
[09:01:45] - Connecting to assignment server
[09:02:06] - Couldn't send HTTP request to server
[09:02:06] + Could not connect to Assignment Server
[09:02:07] - Successful: assigned to (171.64.65.64).
[09:02:07] + News From Folding@Home: Welcome to Folding@Home
[09:02:07] Loaded queue successfully.
[09:03:09] + Closed connections
[09:03:14]
[09:03:14] + Processing work unit
[09:03:14] Core required: FahCore_a1.exe
[09:03:14] Core found.
[09:03:14] Working on Unit 09 [March 3 09:03:14]
[09:03:14] + Working ...
[09:03:14]
[09:03:14] *------------------------------*
[09:03:14] Folding@Home Gromacs SMP Core
[09:03:14] Version 1.74 (March 10, 2007)
[09:03:14]
[09:03:14] Preparing to commence simulation
[09:03:14] - Ensuring status. Please wait.
[09:03:31] - Looking at optimizations...
[09:03:31] - Working with standard loops on this execution.
[09:03:31] - Previous termination of core was improper.
[09:03:31] - Files status OK
[09:03:32] ndard loops.
[09:03:32] - Files status OK
[09:03:40] (decompressed 513.0 percent)
[09:03:40] 9 (decompressed 513.0 percent)
[09:03:40] - Starting from initial work packet
[09:03:40]
[09:03:40] Project: 2653 (Run 11, Clone 144, Gen 68)
[09:03:40]
[09:03:44] Entering M.D.
[09:03:50] Rejecting checkpoint
[09:03:51] OPC
[09:03:51] Writing local files
[09:16:45] CoreStatus = 7B (123)
[09:16:45] Client-core communications error: ERROR 0x7b
[09:16:45] Deleting current work unit & continuing...
Adak
03-03-08, 05:44 AM
Looks like you are not signed into the account with full administrative rights and a password.
Or you installed it without being signed into such an account, or the same account and password that you're using now.

For XP: *net framework 2.0 or better, full admin account with password, which you are currently signed into, (and now are signed into, same as when you first installed it). Run install.bat.

Vista: Turn off UAC, full admin account with password, which you are signed into currently, and was signed into when you first ran install.bat.

Re-check the above when you're not sleepy, and let us know. :)
Douken
03-03-08, 10:46 AM
I did run it in the Administrator account, which is the one I normally(always) use (I don't know if it has problems by using the Admin account, since I don't have any other accounts I wouldn't know. I did put the Log on name "Administrator" with the password of this windows account. So I don't know what's going on. A similar error occurred to me with media player classic, I had to wipe it out and reinstall. But reinstalling the f@h didn't work out. Im using XP.
7im
03-03-08, 01:32 PM
Too much overclock can also throw ERROR 0x7b errors.

As can network settings changes while folding, but they usually occur in the middle of a work unit, not so much at the start.

Please also confirm you have .NET 2.0 or new installed.
Douken
03-04-08, 12:40 AM
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

I guess I have it, I'll try to see if there is an updated version I'm missing.
ChasR
03-04-08, 06:51 AM
Normally, you don't log on as THE "administrator" on an XP machine unless you're in safe mode, unless you entered administrator as the user name. So I'm a little unclear as to what you're doing. Anyway, the user account that runs FAH must have administrator rights and a password and that account (install defaults to the current account) and password must be entered when you run install.
cw823
03-04-08, 07:02 AM
Too much overclock can also throw ERROR 0x7b errors.

As can network settings changes while folding, but they usually occur in the middle of a work unit, not so much at the start.

Please also confirm you have .NET 2.0 or new installed.

WinSMP will not install without 2.0, so that shouldn't be the issue. I always found that particular error to be a hardware issue, more than anything.
ChasR
03-04-08, 09:11 AM
I think you've got it nailed CW. Hardware instability. If it were a password error, core status would be CoreStatus = 63 (99).

Here's what it says in the Wiki about Douken's error (pretty much what 7im said):

7B
CoreStatus = 7B (123)
Client-core communications error: ERROR 0x7b
Deleting current work unit & continuing...
This is an unknown error from the fahlog of SMP clients. Because 0x7b is not defined in the F@h client or SMP fahcore, it is believed to be a Windows or SMPD/MPICH error code. Known causes are unstable systems from too much overclocking, changing network settings while the client is running, or stopping restarting the client. The error is also caused by Windows updates that need to restart your machine. See the List of Known Issues.


A recent contributor thinks memory fault is the primary cause.
Douken
03-04-08, 07:03 PM
ummmm, I'll try changing my memory, since my 2GBs are in my little bro's PC since I'm not fully utilizing them right now, tonight I'll make the change and let you know by tomorrow. If that doesn't work I'll default the OC to factory.