[smith288]

I wonder if using the -local option will help... though it seems strange that the client.cfg file is getting wiped out or corrupted. Perhaps one of the other folks that have been running F@H as a service will have other ideas; I might lean towards suggesting a therapeutic uninstall and reinstall to see if that clears things.

Tried that and still no go.

I did remove everything and redo the service install and now its holding the configuration but its still killing my linksys 802.11g pcmcia card.

Im running a Toshiba Satellite Intel Celeron 1.5ghz with 480mb of ram.

It was running fantastically until about a week ago I noticed it doing this. Could my processor not be getting cool enough and a fault is built in to protect my devices?

[Klutz Dohanger]

Try this.

Stop the service, and edit the config file with notepad.

Set the cpu usage to 80%, restart the service, and see if it
still kills the wireless card. I had to do that with my dell 9300 laptop. If it works then, you can adjust the settings up, until the point where it kills it again.

[RebelTex]

"Could my processor not be getting cool enough and a fault is built in to protect my devices?"

Laptops can really get hot with heavy device usage.  If you are not actively surfing the web or otherwise using the network, then consider removing the Linksys card until the fah core needs to send or retrieve a WU.  PCMCIA cards are always drawing current when plugged in, whether in use or not, and they really run hot.  This wouldn't normally be a problem with normal use, but if the CPU is running at 80% or more, that adds to the heat build up.  More heat is generated with a lot of drive activity, hard drive or CD or floppy.

Hope this helps.  Good Luck.

RT