do you have fah502 in your startup folder or does EMIII start it or any other program starting it as well as the method you mentioned earlier?
I've just never see the startup of the log appear like that or if I have it hasn't been for quite a while since the days that I used others startup methods is why I ask.
This is the console version which comes with its own service installer (it uses srvany). There is nothing in the startup folder and it's independent of EMIII. It starts at boot time like any other automatic service.
I did find the client.cfg file. I'd be willing to bet that adding the appropriate command in it would get me going. Anyone else with the 502-console service self-installer using -advmethods have a client.cfg I could compare it to?
did it make a folder called "service" and put srvany and "instrv" in it?
reason I'm asking is because this is what I used prior to fah 5.00+ anyway and I thought maybe what I have is leftovers from the past.
idunno this is too wierd!
maybe if you stop the client and delete the fahlog.txt then restart is using services.msc it will show us something different?
did it make a folder called "service" and put srvany and "instrv" in it?...maybe if you stop the client and delete the fahlog.txt then restart is using services.msc it will show us something different?
Yes as to srvany and instrv. Deleting the log made no difference.
I'm pretty sure that it will require a line in the client.cfg file, also in the folder created when I installed the service. All the other questions it asked during the install (username, team#, Internet settings, etc) are noted there. I might try to guess at what it would be and see if it makes a difference. The only reason I hesitate is that I am a little leery of experimenting with a setting for an automatic service.
I stopped the service and the core, then renamed the client.cfg file to "client.cf_". Then I ran the FAH502-Console.exe installer and answered "yes" to the option for advmethods.
Folding@home Client Version 4.00
###########################
Arguments: -service -advmethods
Then I finished a WU and immediately got another rinky-dink WU...
Oh, well. I'm sure the juicy WU's will come my way eventually.
I checked the other computers I installed the console on at the same time I did this one and they all indicated version 5.02 in the log...
I was at the end of a WU so I deleted the whole mess, lock, stock, and barrel, then downloaded the console again and re-installed it. I now have the correct version and am now crunching a 343 Point WU - the first WU my new Athlon64 3500+ has seen that is over 100 points in size.
Guess what? There is NO -advmethods in the @#!%&* log, even though I am sure I set it up right... :bawling:
I need a vacation. Since I can't afford one right now I might just go and get drunk instead...
EDIT: I stuck the command back in the registry and all is well. I'm going to shut up and leave you guys alone for a while.
You know what's weird? I downloaded the FAH502-Console.exe program and copied it to the other four computers on my LAN. They were all fine. I also deleted the graphical client I had running on this machine. It must have latched on to a previous version referenced in the registry somewhere.
You know what's weird? I downloaded the FAH502-Console.exe program and copied it to the other four computers on my LAN. They were all fine. I also deleted the graphical client I had running on this machine. It must have latched on to a previous version referenced in the registry somewhere.
Have you gotten it fixed now prof? Are you getting the wu's you wanted yet?
Comments
Sorry for being such a noob, but when it comes to the console version, I am.
it should be towards the end at the last restart of the log.
# Windows Console Edition #####################################################
###############################################################################
Folding@Home Client Version 5.02
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: D:\f@h
Service: D:\f@h\fahconsole
Arguments: -svcstart -advmethods
Here's what I have:
Edited for obviously extraneous material
I've just never see the startup of the log appear like that or if I have it hasn't been for quite a while since the days that I used others startup methods is why I ask.
I did find the client.cfg file. I'd be willing to bet that adding the appropriate command in it would get me going. Anyone else with the 502-console service self-installer using -advmethods have a client.cfg I could compare it to?
Here's mine:
I really didn't know how it was installing itself until now thanks.
reason I'm asking is because this is what I used prior to fah 5.00+ anyway and I thought maybe what I have is leftovers from the past.
idunno this is too wierd!
maybe if you stop the client and delete the fahlog.txt then restart is using services.msc it will show us something different?
I'm pretty sure that it will require a line in the client.cfg file, also in the folder created when I installed the service. All the other questions it asked during the install (username, team#, Internet settings, etc) are noted there. I might try to guess at what it would be and see if it makes a difference. The only reason I hesitate is that I am a little leery of experimenting with a setting for an automatic service.
I stopped the service and the core, then renamed the client.cfg file to "client.cf_". Then I ran the FAH502-Console.exe installer and answered "yes" to the option for advmethods.
Then I finished a WU and immediately got another rinky-dink WU...
Oh, well. I'm sure the juicy WU's will come my way eventually.
Thanks, everybody - especially you, csimon!
ROFLMAO ...
prof you told me your were using the FAH502_Console didn't you?
I doubt you'll ever get the wu you're looking for with this client.
and you're welcome ...always willing to help!
It's supposed to be the latest version...
I checked the other computers I installed the console on at the same time I did this one and they all indicated version 5.02 in the log...
I was at the end of a WU so I deleted the whole mess, lock, stock, and barrel, then downloaded the console again and re-installed it. I now have the correct version and am now crunching a 343 Point WU - the first WU my new Athlon64 3500+ has seen that is over 100 points in size.
Guess what? There is NO -advmethods in the @#!%&* log, even though I am sure I set it up right... :bawling:
I need a vacation. Since I can't afford one right now I might just go and get drunk instead...
EDIT: I stuck the command back in the registry and all is well. I'm going to shut up and leave you guys alone for a while.
We do it cause you're ....um ...special - yeah that's the word I'm looking for!!!
As long as everything's ok that's all that matters ...I just can't stop laughing now!
-advmethods is now in the log and all is finally as it should be. My five local machines are all tied into a 600-point WU at the moment. :thumbup