I tried it over the work net last night. I ran the program from my laptop, installing to a server over the network. Both are running Win2K (laptop is Pro, Server is Server, of course )
Several things:
1. It only loaded 1 instance of SETI even though it was a dual proc server. Did I have to specify it had 2 CPUs?
2. I almost got caught by the network install defaulting to install all named PCs and having the Install or Not Install reversed from the usual setup and could have installed SETI on the headquarters PCs in Chicago. NOT a good thing, could have meant the end of SETI and my career at work. :Q (It's a good thing I was trying to READ the info on the screen, and not just fly by... )
Suggestions:
A - Swap the Install & Not Install so the Not Install is on the left, the Install is on the right
B - Default to Not Installed, and have a way to select 1, 2, many, or All workstations to move over to Install
C - Have a Reset, and/or be able to move workstations back to Not Installed
3. I rebooted my laptop afterwards, and got a strange Windows Messsage about C:\Program not being correct or duplicate, and wanting to change it to c:\Program1
4. Future release please add SETIDRIVER as part of the installation.
5. Future release please add an Uninstall feature that works like the Install over the network. It would be very handy for managing the herd, as sometimes you might have to do an Uninstall on a remote PC(s) that you physically can't get to right away.
Comments: Other than that listed above, it was very straight forward and easy to use. AND FAST! When I hit the Install, it came back so fast that I thought there was a problem. When I went to check the server, it had installed and was running! :Q Dang that was fast!
If I had permission to install SETI on the entire work fleet, I would definitely use this. It would save a LOT of time.
Dasm Great Job!
I wish I had this when I first installed SETI on the work fleet!!