Hi danzigrules,
I copied this from my reply yesterday:
...SetiDriver should be controlling cli 3.0.1, not SetiSpy. If you configured the Client in SetiSpy, then take it out. Start both programs and it should work!!
Your wrote: I have the spy set up to use the clent.
When running SetiDriver, you DO NOT setup client info in SetiSpy. That is only used IF, and ONLY IF, you do not run SetiDriver!! In this configuration SetiSpy only keeps track of info on the WU's, which it does very well.
Good luck!