• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

automating seti service install

blcjr

Golden Member
I have a script (batch file) I run to automate the seti service install on my network clients. However, it is not fully automated: it always runs the prompt asking whether to use a new account, or existing account, forcing me to select "2" and then entering the email address of the account I'm using.

I copy my "user_info.sah" into the folder where seti is being installed as part of the script. Shouldn't this be enough to supply the necessary information automatically? I thought so, but apparently not, or I'm doing something wrong.

Any tips on getting over this last hurdle to an automated install script?

-baz
 

No, I "rolled my own" install script. I just downloaded the FlexInstaller, but because it is an .exe file I cannot really determine how it works without actually using it, and I'd rather not do that so I can maintain a consistent setup across my clients. I've already run my script on 70 clients, and don't relish redoing them.

Besides, this installer apparently tries to "hide" the installation. I cannot see the purpose of that, unless one is installing it where they shouldn't be. I'm not trying to hide anything.

-baz
 
Originally posted by: soni
Else check my seti as service install script.
It does the same, you should be able to figure out the difference..

I looked at your install.bat, and don't really see where you are doing anything different than I am. FWIW, here is my script (with a couple of minor transcriptions to maintain some privacy):

c:
mkdir "\program files\seti@home"
cd "\program files\seti@home"
net use s: \\servername\sah
copy s:*.*
seti_control install -proxy ipaddy:5517
net start seti@home

The files copied from "s:" are:

seti_control.exe
seti_service.exe
setiathome.exe
user_info.sah

The *.exe files are from Ted Dennison's seti service install. I think they merely do what your script does with the *.reg and srvany.exe and instsrv.exe files. setiathome.exe is the actual cli client.

It seems to me that the crux is in the user_info.sah file. We both copy that to our installation folders. Could there be something wrong with my user_info.sah file? Further, FWIW, here's the contents"

type=user info
id=1755578
key=xxx'd out here for privacy
email_addr=baz@bazilla.net
name=bazilla
url=
country=United States
postal_code=72113
show_name=yes
show_email=no
venue=3
register_time= 2451600.61350 (Sat Feb 26 02:43:26 2000)
last_wu_time= 2451696.04770 (Wed May 31 13:08:41 2000)
last_result_time= 2452414.94933 (Mon May 20 10:47:02 2002)
nwus=791
nresults=25613
total_cpu=837954556.231335
params_index=0

Do you see anything askew here?

-baz

 
I do manual "SETI as a service" installs and despite the fact that my user.sah file is in the working directory I'm still prompted.

I do not use the FlexInstaller because it does not have a simple uninstall feature.
 
Originally posted by: Robor
I do manual "SETI as a service" installs and despite the fact that my user.sah file is in the working directory I'm still prompted.
So I'm not alone. I wonder what others do go avoid the prompt?

I do not use the FlexInstaller because it does not have a simple uninstall feature.
Yes, that would be a consideration, too. Ted Dennison's seti_control.exe has an uninstall switch. It has come in handy.

I'm sure the FlexInstaller is just the ticket for many. I like to have more control over my service installs.

-baz

 
The reason people run it hidden is when you as a network admin or support have gotten approval to run SETI (or other DC apps) on the company network, and you don't want the users to start asking a bunch of questions about that SETI icon.

It reduces the likely hood of some "knowitall" complaining that SETI is screwing up their PC (instead of that 50meg screensaver and all the Comet Cursor, Kazaa, etc. adware/spyware they have running).

There are legitimate reasons for running apps DC and otherwise, "hidden".
 
Well, I can't see any problems in the user_info.sah-file. 😕

But trying a little, by making a new user_info.sah in a text-editor, this doesn't work, since here the lines is termited with ascii 13 10 while seti is only using 10... Maybe this is a problem here, but if you've copied from a working seti-install, I don't understand how this can crop up...

And no, I've got a couple of user_info.sah-files, and I'm never being asked to make a new account or log in...


 
Try to make a new user_info.sah with the setiathome.exe you use.

Thats the best suggestion I have 🙁
 
Try including a w/u as well, you may not get credit for it if you're using the same w/u over and over again but it's worked for me.
 
Back
Top