F@H2 as a service!!!

[Kendan]

Here is a link that tells you how to run Fah2 as a service. It is from the overclockers Australia. They have it as a sticky on their board.
http://forums.overclockers.com.au/showthread.php?s=&threadid=19917
They are right behind us and gaining.

[Ploaf]

Thanks Kendan

Has anyone made this work? I've tried this over and over again while trying to do a write up on it and I cannot get it to work. We had this problem before and I did manage to get it to work by making a service out of the core_65.exe as well, but it really shouldn't need to be that way. Besides, it gave me trouble like that as well.

[Dunga Bee]

I did not read the post at OC.au, but I am running F@H2 as a service on a Win2K server. I only set up the graphical client as a service and allowed it to interact with the desktop. It automatically starts up the Core_65.exe.

The only problem is that when you stop the service, Core_65 does not stop. Not a major problem, but it is not perfect :confused:

DB

[Ploaf]

Maybe that's what I was doing wrong. I didn't let it interact with the desktop. I'll give that a try. Did you use the text only version or the gui version?

[Dunga Bee]

GUI version.

Even though you set it to interact, it still starts up just fine before anyone logs on. The only difference is that once a person logs on to the console, they see the icon in the tray.

[Ploaf]

I missed the chance to try it out. My protein has advanced too far and I'll let it finish out.

What I really wanted to accomplish is completely hiding the client though. That way end users won't be able to mess with it. This can still help since it starts the clinet no matter who logs in.

[Dunga Bee]

I hear you. Completely hiding it is what I was after too. But at least auto-start is good.

I was thinking maybe if you create a dummy account and have it start under that account, perhaps it would not show in the taskbar if just a 'regular' user signs on ?

Or maybe there is a switch on the startup of the GUI to hide it? Probably wishful thinking.

[Digital-Monk]

Originally posted by Ploaf
Thanks Kendan

Has anyone made this work? I've tried this over and over again while trying to do a write up on it and I cannot get it to work. We had this problem before and I did manage to get it to work by making a service out of the core_65.exe as well, but it really shouldn't need to be that way. Besides, it gave me trouble like that as well.

Hey, from OCAU, I got the service thing to work on an NT4 box today. I found it pretty straight forward from the instructions. And it's nice to get the console out of the taskbar :D

[sifu quoc]

post the instructions here... i dont wanna register at oc.au

[Kendan]

Here is another link. http://www.dslreports.com/forum/remark,1645416
Hope this helps.

[sifu quoc]

what does running it as a service do?

[Dunga Bee]

Running as a service allows 2 things:

1) It runs totally in the background and the user sees nothing so they can't stop it or even know it is there (unless they look at the Task Manager).

2) It will start up automatically when the machine starts without needing anyone to log on. That is especially important on servers where no one may log in after they boot up.

[asmodean]

I used to run F@H v1 as a service on 2k w/ firedaemon. Did that with the v2 console too. EM can be used to show the window if needed, as long as the clients name is correct. Otherwise it'll just stay in the background.

I haven't checked those links, but I think it'll work if you substitute the graphical client binary with the console binary.