• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

FILE_IO_ERROR for SMP Client v6.22

C

CoW]8(0)

[H]ard|Gawd
Joined
Jul 25, 2005
Messages
1,427
I've keep getting this FILE_IO_ERROR:

Code: 
[13:33:50] Trying to unzip core FahCore_a1.exe
[13:33:50] Decompressed FahCore_a1.exe (2117632 bytes) successfully
[13:33:55] + Core successfully engaged
[13:34:09]
[13:34:09] + Processing work unit
[13:34:09] Work type a1 not eligible for variable processors
[13:34:09] Core required: FahCore_a1.exe
[13:34:09] Core found.
[13:34:09] Working on queue slot 01 [October 8 13:34:09 UTC]
[13:34:09] + Working ...
[13:34:11]
[13:34:11] *------------------------------*
[13:34:11] Folding@Home Gromacs SMP Core
[13:34:11] Version 1.76 (February 23, 2008)
[13:34:11]
[13:34:11] Preparing to commence simulation
[13:34:11] - Ensuring status. Please wait- Created dyn
[13:34:11] - Files status OK
[13:34:17] - Expanded 4805457 -> 24810145 (decompressed 516.2 percent)
[13:34:17] - Starting from initial work packet
[13:34:17]
[13:34:17] Project: 2665 (Run 2, Clone 686, Gen 56)
[13:34:17]
[13:34:18] Assembly optimizations on if available.
[13:34:18] Entering M.D.
[13:34:42]  percent)
[13:34:42] - Error: Bad work unit. Digital signatures don't match
[13:34:42] Error: Could not open work file
[13:34:42]
[13:34:42] Folding@home Core Shutdown: FILE_IO_ERROR
[13:34:42] Finalizing output

Anyone else having this sort of trouble with their clients? I've only just started getting these error messages.
 
What antivirus are you using? Some AV programs take a while to pick up on FAH, but once they do they wont leave it alone. I had this problem with NOD 32. Putting the work folder in the NOD 32 ignore folder did no good. It wouldn't leave it alone.

 
Delete your work and queue files and download a new unit. If that doesn't work, try doing it again but delete the Fahcore_a1.exe file as well.
 
Code: 
# Windows SMP Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.22 SMP Beta2

                          http://folding.stanford.edu

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

It's the 6.22 client. I'm not sure if its the r3 though. Is there a known problem related to this for the r3 client?
 
Yours is the original 6.22 (no revision). The r3 version fix this error so you should update the client ;)

 
You must log in or register to reply here.
Back
Top