Need Help......Bad. F@H V5.02...Argh.
dragonV8
not here much New
Where to start..............Due to a mismatch between a P4 3.2E and a mobo, we changed mobo, re-installed XP, etc and the problem started with F@H V5.02.
Sofar we have lost WU after WU. (at least a dozen, only complete 4 to 10 frames and error out).
When installing the GUI, it was set up as machine ID 1. Got it going ok. Launch directory: C:\Folding 10
Next Sally set up the console. Set it up as machine ID 2 but the client said there was a conflict with another machine with the same ID. So she checked with the FAHLog on the GUI. Sure enough the client (GUI) had changed from ID 1 to ID 2 but not only that the console then came up with: Launch directory: C:\Folding 10...........same as the GUI at the start up of the log. It should have been \Folding 9. (Don't ask about the numbering system....that is a mystery only known to Sally. )
Nothing we know seems to fix it. Deleting and re-installing, going into the registry, you name it we (Sally) has tried it, even re installed version 4 just to get them working without any conflict. Now both the GUI and the console have each others machine ID for no apparent reason.
We have no idea what is happening. At a total loss. Never had this problem before, ever. Something new to challenge her. Never had the same problem twice.
Just looking over a lengthy log now of the GUI and it has deleted 2 WU's due to Core shut down : FILE_IO_ERROR. (CoreStatus = 75 (117).
Then the GUI got going again on the 3rd WU and decided to change Machine ID to 2..............it was 1.
If anyone has any idea what we (Sally) are doing wrong, please reply. We are not going anywhere.
Thanks in advance
Jon
Fold on.
Sofar we have lost WU after WU. (at least a dozen, only complete 4 to 10 frames and error out).
When installing the GUI, it was set up as machine ID 1. Got it going ok. Launch directory: C:\Folding 10
Next Sally set up the console. Set it up as machine ID 2 but the client said there was a conflict with another machine with the same ID. So she checked with the FAHLog on the GUI. Sure enough the client (GUI) had changed from ID 1 to ID 2 but not only that the console then came up with: Launch directory: C:\Folding 10...........same as the GUI at the start up of the log. It should have been \Folding 9. (Don't ask about the numbering system....that is a mystery only known to Sally. )
Nothing we know seems to fix it. Deleting and re-installing, going into the registry, you name it we (Sally) has tried it, even re installed version 4 just to get them working without any conflict. Now both the GUI and the console have each others machine ID for no apparent reason.
We have no idea what is happening. At a total loss. Never had this problem before, ever. Something new to challenge her. Never had the same problem twice.
Just looking over a lengthy log now of the GUI and it has deleted 2 WU's due to Core shut down : FILE_IO_ERROR. (CoreStatus = 75 (117).
Then the GUI got going again on the 3rd WU and decided to change Machine ID to 2..............it was 1.
If anyone has any idea what we (Sally) are doing wrong, please reply. We are not going anywhere.
Thanks in advance
Jon
Fold on.
0
Comments
Deleat all folders.
re-create them.
copy new core into each.
Unless Sally is REALLY attached to the pictures just use the console.
Run each with the -local -configonly flags.
One of my machines kept trying to re-name stuff. Ner folders and -local is the only way to keep it working right.
Oh, by the way, just noticed...........Not the right place for it, but.....
Seeing how Prof's not wel.
Congratulations. 100,000 points w00t :celebrate
:smokin: :smokin:
Sally managed to get both clients working as consoles. So far so good. Never having run 2 x consoles, it was foreign territory for us. Hoping it works out and keeps going.
If anyone has any idea about why we are having so much drama, as per our original post, please add comments.
We would still like to know the reasons.
Jon
Some of my files had been moved and pointers may not have been correct.
Just wipe the file and reinstall. You shouldn't really need the -local, but I use it on multi wu machines just in case.