Moving F@H folder

The only registry references to the installation will be for the service, so if you move the folder(s) without first sorting the service, it won't find it and won't run. To fix this you must first remove the service (rerun the client with the '-configonly' and choose to remove the service when asked). Move to the new location and reinstall the service (again by running with '-configonly' option).

Hope this helps, null :)
 
This won't affect the work I have in progress?

What order woudl I do it in?

* stop service in WIn
* run configonly to remove service
* move folder
* run configonly again to apply service?
 
2bullish said:
Just delete the service from the registry, move to new folder, then run the client again with configonly, job done
Nah, that's messier than using the client to uninstall its own service as you'll be left with the FAH service on the services.msc list unless you manually purge that as well.

Procedure:
  1. Stop service
  2. Run client with -configonly
  3. Tell it to uninstall the service
  4. Press enter until the client exits
  5. Move all files in your FAH directory
  6. Run client with -configonly
  7. Re-enter your registry hacks
  8. Restart the service.
 
OK - tried all this and it moves but I can't restart the service

What I am trying to do is run F@H on a network drive (which is on a seperate server) so I can monitor the progress from one machine using FaHMon. Before you ask I can't access individual Pc's hard drives so don't suggest that one please.

Any ideas?
 
Seems to be installing the service as it is in the registry under the right drive and also in services.msc under the right drive - it's just when I start it in says it can not find the specified file (gives address) on the local computer (?) but I have it in winexplorer (!?) :confused:

Here's the fahlog file

--- Opening Log file [November 6 15:09:53]


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

Folding@Home Client Version 5.04beta

http://folding.stanford.edu

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

Launch directory: C:\Program Files\FaH1
Executable: C:\Program Files\FaH1\FAH504-Console.exe
Arguments: -configonly

[15:09:53] - Ask before connecting: No
[15:09:53] - Proxy: xxx.xxx.xxx.xxx:8080
[15:09:53] - User name: feriso (Team 10)
[15:09:53] - User ID: 76E90378719AD5DA
[15:09:53] - Machine ID: 1
[15:09:53]
[15:09:53] Configuring Folding@Home...


[15:10:05] - Ask before connecting: No
[15:10:05] - Proxy: xxx.xxx.xxx.xxx:8080
[15:10:05] - User name: feriso (Team 10)
[15:10:05] - User ID: 76E90378719AD5DA
[15:10:05] - Machine ID: 1
[15:10:05]
[15:10:05] -configonly flag given, so exiting.


--- Opening Log file [November 6 15:12:45]


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

Folding@Home Client Version 5.04beta

http://folding.stanford.edu

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

Launch directory: V:\GN1\fah-l-cm\FaH1
Executable: V:\GN1\fah-l-cm\FaH1\FAH504-Console.exe
Arguments: -configonly

[15:12:45] - Ask before connecting: No
[15:12:45] - Proxy: xxx.xxx.xxx.xxx:8080
[15:12:45] - User name: feriso (Team 10)
[15:12:45] - User ID: 76E90378719AD5DA
[15:12:45] - Machine ID: 1
[15:12:45]
[15:12:45] Configuring Folding@Home...


The program will continue in non-service mode now, working in V:\GN1\fah-l-cm\FaH1.
The next time the computer is starts up, you should see work automatically
continue there. Note that when this service is running, you should not try
to manually run F@H from that directory at the same time.


[15:13:05] - Ask before connecting: No
[15:13:05] - Proxy: xxx.xxx.xxx.xxx:8080
[15:13:05] - User name: feriso (Team 10)
[15:13:05] - User ID: 76E90378719AD5DA
[15:13:05] - Machine ID: 1
[15:13:05]
[15:13:05] -configonly flag given, so exiting.


--- Opening Log file [November 6 15:20:59]


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

Folding@Home Client Version 5.04beta

http://folding.stanford.edu

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

Launch directory: V:\GN1\fah-l-cm\FaH1
Executable: V:\GN1\fah-l-cm\FaH1\FAH504-Console.exe
Arguments: -configonly

[15:20:59] - Ask before connecting: No
[15:20:59] - Proxy: xxx.xxx.xxx.xxx:8080
[15:20:59] - User name: feriso (Team 10)
[15:20:59] - User ID: 76E90378719AD5DA
[15:20:59] - Machine ID: 1
[15:20:59]
[15:20:59] Configuring Folding@Home...


[15:21:11] - Ask before connecting: No
[15:21:11] - Proxy: xxx.xxx.xxx.xxx:8080
[15:21:11] - User name: feriso (Team 10)
[15:21:11] - User ID: 76E90378719AD5DA
[15:21:11] - Machine ID: 1
[15:21:11]
[15:21:11] -configonly flag given, so exiting.
 
Last edited:
Something along the lines of...

"Error : Cannot find specified service in V:\xxxxxxx on local computer"

But the V: drive is visable on the computer and is accessible and has been set in the registry by using the -configonly flag in the directory it now can not find.
 
Hmm thats quite strange :confused:

It says it's looking for V:/ on local computer, is that ok if it's a mapped network drive?

I can't really see any reason why it isn't working.
 
Hmm, you've mapped a network drive, but started as a service. Is that mapping actually active to the service's user account, before you have logged in as a user. Is the mapping user account the same as the service's user account. Presumably the user has full permissions to the mapped drive?
 
I started the service when I was logged in so there is no problem in terms of access rights to that drive. - if it was a problem with access then why did it allow me to run the -configonly and find the executable in the V:\ drive :confused:
 
Ah, but what account does the service use, the default one of windoze "local system", which will not have access to the mapped drive, or have you given it your own user account?

Running the config only option, you will have been doing under your own user name, and it would not have been operating as a service. Thus in configonly mode it would have seen the mapped drive.

As an experiment, stop the service, and run the F@H client executable direct without any options like configonly. In the popup window is it running and findding the file now?
 
Last edited:
That could well be the problem - the system does not have 'permission' to see the drives. Tried the log on tab in the services but afaik this is only for local accounts not netware based accounts

Runs the executable fine in the mapped drive btw....
 
If you run services.msc and go into the properties for the F@H service you should be able to see a "Log On" tab where you can specify another account than the Local System account - dunno if that will help at all
 
rich99million said:
If you run services.msc and go into the properties for the F@H service you should be able to see a "Log On" tab where you can specify another account than the Local System account - dunno if that will help at all

feriso said:
Tried the log on tab in the services but afaik this is only for local accounts not netware based accounts....

Can't get it so see/do Netware accounts - looks like I am going to have to admit defeat in this one..... :(
 
Back
Top Bottom