OK, this is getting really irritating...I installed SetiQueue, installed as a service...seemed to be running ok.
Installed the multi-CPU 1 & 2 files...ended having to reboot the server in order to get a single instance running. Modified the .reg files to point to my own SetiQ, rather than OK's. I have a valid SetiID and user.sah files.
Each service runs, but I can't tell if S@H is actually doing anything. SetiQ is also logging multiple failures trying to d/l new WUs (tonight).
What's up w/ this?
SetiWatch was put into each client directory, but it can't seem to tell me if the local client is doing anything either.
OS: W2K Server, 2CPU, SP2.
--Woodie
Installed the multi-CPU 1 & 2 files...ended having to reboot the server in order to get a single instance running. Modified the .reg files to point to my own SetiQ, rather than OK's. I have a valid SetiID and user.sah files.
Each service runs, but I can't tell if S@H is actually doing anything. SetiQ is also logging multiple failures trying to d/l new WUs (tonight).
What's up w/ this?
SetiWatch was put into each client directory, but it can't seem to tell me if the local client is doing anything either.
OS: W2K Server, 2CPU, SP2.
--Woodie
