I've developed an updated form of the batch files shown earlier in this thread (page 6?).
Basically, what prompted the messing around with these files is that I got tired of having the batch files restart at 1. It was either that or remember - and manually edit - the place to start.
So I...
Ver. 3 is faster on my PC. My average has already dropped, meaning it's quite a bit faster, considering I had 1000 units before changing over, and am now only approaching 1100...
Mike
Well, I finally got around to uploading the units, and have hit the 1K mark. That took a while! I don't have the 'slave labor' that the rest of the gang has...
I am also running the latest version of the command processor. It seems to run a little faster on my computers than the older one -...
Pat,
note that I used the /L flag in the FOR loop under Win2K. I did not use that under Win98SE. I also listed out every subdir (e.g. 1 2 3 4 5 ... 16) instead of the abbreviated version (1, 1, 16).
You might have to try that out if you're not running W2K - I just reconfigured my Win98SE...
Pat,
sure. I'll post it right here; it is pretty short and sweet.
It also builds upon other members' effort earlier in the old thread, so if you see something familiar, now you know why!
The executable seti client is called seticlient.exe. Comes straight from SETI, I just renamed it.
The...
Patrick,
I use the task scheduler in W2K. Settings, Control Panel, Scheduled Tasks, then I use a batch file to execute the client. Same batch file also has a loop so I can use a cache system.
Works like a charm - starts right up. Only thing is I cannot set the priority level that way, but...
Careful with SETIDriver on multiprocessor systems. I installed it last night on a dual processor system. The previous setup had two independent processes with preference to a particular CPU (cmdline version with -cpu 1, for example).
SETIDriver correctly identified the two processors, but...