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?