Post by: IKV Nemesis D7L on March 19, 2004, 09:08:53 pm
Quote:
A year or so back I posted this set of instructions to assist people in setting up the SETI commandline client with SETIDriver. There was a recent request for a repost of them. The original no longer exists but Mazeppa had archived it and reposted it for us.
Here is an update with corrected links.
Setting up the SETI command line client with SETIDriver
Some people have requested assistance on setting up the Windows SETI commandline client and a caching program. Here is my attempt to provide such aid. Hopefully it will be of use.
These instructions are based on Windows 98 SE and Windows 2000Pro and may need to be adjusted slightly for other versions of windows. I anticipate that most users of other versions of Windows can adapt these instructions to their version.
The download locations below are the ones to which the SETI site itself directs you. These instructions assume that during the setup you stay connected to the internet. If not you will need to reconnect to do Step 4:
Step 1: Create directory from which you will run the SETI program. If you are already running the graphical version you should create a new location, just in case .
Step 2A: Download the SETI client from the address below to the prepared directory.
Link below is to ftp site for downloading the commandline client.
ftp://alien.ssl.berkeley.edu/pub/setiathome-3.08.i386-winnt-cmdline.exe
Step 2B: Download the SETIDriver utility from the following link to the same directory.
Link to SETIDriver
You will also need a utility such as Winzip or PKUnzip to open the SETIDriver archive. Most people here will already have one.
Link to GPL'ed unzip program for Windows Link to 7-Zip
Step 3: Open the directory to which you downloaded the programs with Windows Explorer. Extract SETIDriver from the archive using your chosen UnZipping program. Create a directory under that you extracted into to run SETIDriver from.
Example:
C:\Seti\SETIDriver.zip when unzipped creates:
C:\Seti\SETIDriver\SETIDriver.exe
Step 4:Run the SETIdriver program by doubleclicking on it. Do not have the setiathome client in the same directory as SETIDriver at this point.
A/ A window will open entitled "SETI Driver - Select CLI Client". Open the directory with the SETI Client (setiathome-3.08.i386-winnt-cmdline.exe), select that client. Click OK
B/ Clear the Hideprocessing box by clicking on it.
C/ Change the Desired Cache Size to 1.
D/ Click transmit. SETI will open in a DOS shell.
Step 5: At this point you are presented with 2 options.
The choices are:
1/ setup a new account
and
2/ log into an existing account. Choose the appropriate option.
These instructions will continue based on using an existing account.
Choose option 2: It will display "E-mail address:". Type your address and hit enter. SETI will then connect to the internet and download a Work Unit.
Step 6: Fill in your options:
SETI client priority - I suggest Low.
All other options should be based on your personal setup and preferences. If other people use your system you may wish to use the Hide Processing options and choose not to Display Transmit. I suggest a cache size sufficient to last one week, in case of SETI outages or your having internet connection problems, you may wish longer or shorter.
Those like myself with a dialup connection will wish to choose to set Auto Transmit off unless working with a SETIQueue (a follow up message will deal with that topic). Those with a persistant connection may wish to choose Auto Transmit on to transmit as they process.
Those with multiple processors or with a Pentium 4 with Hyperthreading may choose more than one in the Maximum Processes: option. SETIDriver does detect 2 processors at least and autmatically adjusts to use both. I don't know if it detects hyper threading processors or more than 2 CPUs. If SETIDriver does not do so automatically choose one process per processor or two per hyperthreading processor. Hyperthreading and multiprocessor use requires a Operating System that can use them. Windows 2000Pro or Windows XP Pro. Windows 98SE cannot use these features and I suspect Windows XP Home cannot either.
Click on the save config button.
Step 7: Basically you are done. Some may wish to enable SETIdriver to load on bootup or put an icon on the desktop. Those issues should be easily dealt with.
Post by: nexa1 on March 19, 2004, 09:21:26 pm
This is just what I was looking for.
Post by: IKV Nemesis D7L on March 19, 2004, 09:55:16 pm
Quote:
You are such the mind reader. *grin* You kick A$$!!
This is just what I was looking for.
I have to share the credit with Mazeppa and others. Mazeppa was the original inspiration to write it up back in the old forums, back when the team was more active. When the old forums went down he saved a copy. Ultimately when people asked for a repost he sent it on to me so that I could update it (and save my own copy this time) and repost it in the off topic forum. Since then a link has been in my signature for any who cared to follow it. Much of the information here was posted by others long before I joined the team. My primary contribution was to gather together what the team knew into one place that was more easily accessible without reading everything in the SETI thread(s).
I and others on the team will gladly help anyone who needs assistance with SETI. The more the merrier. Whether you can do 1 work unit a month or a thousand a day (like Raven) each unit is appreciated. Any unit could be the one, it could be found by someone who processes one and only one or by a giant like Raven. Anyone could win this lottery, Raven buys more tickets than I do but I can still "win", so can you.
Post by: Demandred on March 21, 2004, 08:42:17 am
Post by: The Postman on March 21, 2004, 10:24:04 am
Post by: IKV Nemesis D7L on March 21, 2004, 10:39:42 am
Quote:
Is there any way to do SETI on a machine with no connection to the internet? I have a small server that spends most of each day idle that I do web development on and I don't want accessible from the internet. If it's possible to send the processed work units from my desktop I might as well do it. The server is running Windows 2000 Advanced Server.
Yes. Though I have not done so. Here is a quick off the top of my head explanation of how to do it. It is not nearly as detailed as my SETIDriver install instructions above.
You need to have a common type of removable media on both machines and a compatible (to each other) OS on both.
1/ Set up SETIDriver on the machine connected to the internet. If you are already running SETI on that machine you need to set up a second copy to use for transferring data for the offline machine.
2/ Download data in a quantity that can fit on your removable media.
3/ Setup SETIDriver on the offline machine. When it tries to connect to the internet to download a data packet stop it.
4/ Zip the data (not the whole seti driver setup just the data) that you downloaded on the connected machine and place on the removable media. I say zip so that long file names are preserved. You will also need to preserve the directory structure.
5/ Unzip the data onto the offline machines SETIDriver directory.
6/ Run SETIDriver on the offline machine
7/ Zip the processed data on the offline machine unzip it onto the online machine, run the second copy of SETIDriver to transfer data to SETI and new data from SETI.
8/ Return to step 4/ and repeat the cycle.
Obviously since this is a hassle you don't want to do it more often then absolutely neccesary. So CD/RW is the best media. WUs expire after 4 weeks so I would not download more than a 3 week supply at a time. On my network I keep a 2 week cache to allow for connection problems (Currently that is 609 WUs
my Queue takes 239MB). Since you are only tranferring text files you should be pretty immune to transferring a virus to the offline machine.
While experimenting to get things right I suggest that you only tranfer one or two WUs at a time. It should also be possible to setup a batch file to do the zipping and unzipping on both ends.
There are in fact other ways. If I were doing it I would probably use SETIQueue instead of SETIDriver and copy the whole SETIQueue between machines. But so far I have not (and neither has anyone else here) written up full instructions on setting up a SETIQueue install. SETIQueue might fail if the offline machine does not have a network address of its own, I am unsure as I have not actually tried it on an offline machine.
Good Luck and let us know how it works out.
If it works out you might wish to consider writing up some full instructions on how you did it, if so I would suggest adding it to this thread. No pressure, just a suggestion.
Post by: ActiveX on March 21, 2004, 10:55:04 am
Post by: IKV Nemesis D7L on March 21, 2004, 10:59:43 am
Quote:
When the DOS winda wont do anything else, is it okay to terminate it from Windows?
Yes. I have done so more than once, never with a problem.
Post by: ActiveX on March 21, 2004, 11:04:48 am
Post by: IKV Nemesis D7L on March 21, 2004, 11:11:35 am
Quote:
Am I goin to have to point it to the CLI every time I run it?
Not if you followed my setup instructions.
Post by: ActiveX on March 21, 2004, 11:12:48 am
Quote:Quote:
Am I goin to have to point it to the CLI every time I run it?
Not if you followed my setup instructions.
I'll review then...
Post by: ActiveX on March 21, 2004, 11:16:47 am
Post by: Demandred on March 21, 2004, 04:38:34 pm
Quote:Quote:
Is there any way to do SETI on a machine with no connection to the internet? I have a small server that spends most of each day idle that I do web development on and I don't want accessible from the internet. If it's possible to send the processed work units from my desktop I might as well do it. The server is running Windows 2000 Advanced Server.
Yes. Though I have not done so. Here is a quick off the top of my head explanation of how to do it. It is not nearly as detailed as my SETIDriver install instructions above.
You need to have a common type of removable media on both machines and a compatible (to each other) OS on both.
1/ Set up SETIDriver on the machine connected to the internet. If you are already running SETI on that machine you need to set up a second copy to use for transferring data for the offline machine.
2/ Download data in a quantity that can fit on your removable media.
3/ Setup SETIDriver on the offline machine. When it tries to connect to the internet to download a data packet stop it.
4/ Zip the data (not the whole seti driver setup just the data) that you downloaded on the connected machine and place on the removable media. I say zip so that long file names are preserved. You will also need to preserve the directory structure.
5/ Unzip the data onto the offline machines SETIDriver directory.
6/ Run SETIDriver on the offline machine
7/ Zip the processed data on the offline machine unzip it onto the online machine, run the second copy of SETIDriver to transfer data to SETI and new data from SETI.
8/ Return to step 4/ and repeat the cycle.
Obviously since this is a hassle you don't want to do it more often then absolutely neccesary. So CD/RW is the best media. WUs expire after 4 weeks so I would not download more than a 3 week supply at a time. On my network I keep a 2 week cache to allow for connection problems (Currently that is 609 WUs
Since you are only tranferring text files you should be pretty immune to transferring a virus to the offline machine.
While experimenting to get things right I suggest that you only tranfer one or two WUs at a time. It should also be possible to setup a batch file to do the zipping and unzipping on both ends.
There are in fact other ways. If I were doing it I would probably use SETIQueue instead of SETIDriver and copy the whole SETIQueue between machines. But so far I have not (and neither has anyone else here) written up full instructions on setting up a SETIQueue install. SETIQueue might fail if the offline machine does not have a network address of its own, I am unsure as I have not actually tried it on an offline machine.
Good Luck and let us know how it works out.
If it works out you might wish to consider writing up some full instructions on how you did it, if so I would suggest adding it to this thread. No pressure, just a suggestion.
I'll have a go at doing it tomorrow. It's actually not going to be that much of a hassle because my desktop is networked to the server, removing the need to use compatible media (I could set up ICS to give the server internet access but I don't feel comfortable having an always-on box running IIS that can be connected to from outside the network). If it works out, I'll see about writing a short guide.
Post by: IKV Nemesis D7L on March 21, 2004, 09:48:54 pm
Quote:
I'll have a go at doing it tomorrow. It's actually not going to be that much of a hassle because my desktop is networked to the server, removing the need to use compatible media (I could set up ICS to give the server internet access but I don't feel comfortable having an always-on box running IIS that can be connected to from outside the network). If it works out, I'll see about writing a short guide.
If the two machines are networked it becomes much easier. SETIQueue is the program you want. It allows you to run both (or many more) machines off of one queue. I don't have set up instructions for it though. I have it running on my main machine and it handles uploads/downloads for all four machines. It also gives you some statistical information. With SETIQueue you don't need SETIDriver but using SETIDriver on each individual machine does protect you from network problems your Queue system crashing does not bring everything to a halt.
Post by: ActiveX on April 05, 2004, 09:17:23 am
Post by: ChAotiCIllusion on April 05, 2004, 09:38:14 am
Post by: ActiveX on April 05, 2004, 10:08:32 am
Post by: IKV Nemesis D7L on April 05, 2004, 04:54:09 pm
Quote:
Okay, it still wants me to point it to the CLI each time it starts up, I dunno what I did wrong...as far as I can tell everything is right...
My guess is that you missed the following comment, specifically the part in red.
Quote:
Step 4:Run the SETIdriver program by doubleclicking on it. Do not have the setiathome client in the same directory as SETIDriver at this point .
Post by: ActiveX on April 05, 2004, 05:24:07 pm
the client is at C:/SETI/
Post by: IKV Nemesis D7L on April 05, 2004, 05:38:36 pm
Quote:
SETI Driver is at C:/SETI/SETIDriver/
the client is at C:/SETI/
Try a totally unconnected directory. Such as C:/SetiTemp/
Post by: ActiveX on April 05, 2004, 05:41:46 pm
Post by: IKV Nemesis D7L on April 05, 2004, 06:02:06 pm
Quote:
I moved the SETIDriver directory straight to C:/ and it din work...
Then as of now I don't have a clue. What OS are you using?
If you are using Win2000 or XP did you try it as administrator?
Post by: ActiveX on April 05, 2004, 06:07:37 pm
Post by: IKV Nemesis D7L on April 05, 2004, 06:15:43 pm
Quote:
WinME...
Ouch. My condolences. I have only tried those instructions on win98SE and Win2000Pro. I have had reports of it working on WinXP. But Windows ME I don't recall any feedback on. If I think of anything else to try I will pass it on. If you manage a solution please post it here for others. Good Luck.
I tried ME at a friends and didn't like it, neither did he. After a few too many tech support calls he refused to continue selling it. He kept having to use a Linux boot disk to recover from ME's self imposed damage.
Post by: ActiveX on April 05, 2004, 06:56:53 pm
Ima be going XP soon as my tax returns get in...
Post by: nexa1 on April 05, 2004, 09:37:46 pm
What about just starting over with a fresh install?
I know, it sounds dumb.
Post by: ActiveX on April 05, 2004, 09:55:04 pm
Post by: nexa1 on April 05, 2004, 10:00:05 pm
I meant setidrv. My bad.
Don't listen to me, Nem is better at this then I am.
Post by: ActiveX on April 05, 2004, 10:02:17 pm
Post by: IKV Nemesis D7L on April 06, 2004, 05:43:57 pm
One thing you might check if you are comfortable with regedit is if there is an entry for the SETI CLI. At this point I would not suggest editing anything in, just checking. Mine has one listed and saved in the temp directory. You might try putting a copy in the temp directory manually.
Still looking for a solution.
Post by: ActiveX on April 06, 2004, 06:00:50 pm
Post by: IKV Nemesis D7L on April 06, 2004, 06:10:24 pm
Quote:
The search come up negative when I search for SETI CLI, but SETI brought up a bunch of things...
It would not actually say "seti cli" it would say the name of the program file itself. In my case "setiathome-3.08.i386-winnt-cmdline.exe". Sorry for being unclear.
Post by: ActiveX on April 06, 2004, 06:13:17 pm
Post by: IKV Nemesis D7L on April 07, 2004, 10:18:47 pm
Quote:
It comes up negative...
I have come up with one more thing to try.
On my Win98SE machine I am using a CLI that has been renamed to SETIATHOME.EXE instead of setiathome-3.08.i386-winnt-cmdline.exe. The hyphens and extra periods may be something that Win98SE and WinME has trouble with. Try renaming the CLI something that stays withing the DOS 8.3 naming limits.
Post by: ActiveX on April 08, 2004, 04:46:00 pm
Im not going to worry about it, its not hard to point it there, but it would have been nice to let the comp do it itself if Im away...
Post by: IKV Nemesis D7L on April 11, 2004, 09:22:56 am
The below is off the SETI @ home message boards in response to my posting there.
Quote:
I have Windows ME and I run Seti Driver, Seti CLI 3.03, and Seti Spy all in the same folder. No need to point Seti Driver to the CLI, just start Seti Driver and it will pick it up.
It is worth a try. It may be that under WinME that SETIDriver just does not complete the move but still expects it to be done. If it does not work as is you may wish to copy the file to the SETIDriver directory while SETI is running.
One other random thought. Check the properites of the client and make sure that it is not read only.
Post by: ActiveX on April 11, 2004, 06:50:23 pm
Post by: IKV Nemesis D7L on April 11, 2004, 07:57:43 pm
Quote:
It worked...
Great! Too bad it took so long.
Post by: IKV Nemesis D7L on April 16, 2004, 09:43:28 pm
SETIQueue is a program that downloads SETI workunits and allows SETI clients (including the screensaver) to download from it rather than fromSETI @ Home. The client also can upload results to SETIQueue and all SETIQueue to send them in. It is useful on a network to allow fine control over your internet connections. It also keeps some statistics and does graphs.
Example statistics:
Code:
Name RPD RY RT Avg CPU Last Result Wu Pend
#4 8.07 8 9 2h51m 10m32s 15
#3 7.71 7 8 2h56m 15m29s 15
#2 12.92 13 12 3h42m 24m08s 15
#1 13.53 12 13 3h31m 50m05s 15
Totals:
42.23 40 42 3h20m 60
What do the headings on the table mean?
RPD= Returned / day - your average daily output by machine and total over the last 7 days.
RY= Returned Yesterday
RT= Returned today
Avg CPU= Average time/CPU
Last Result= How long since the last result (lets you know which if any machine is not processing)
Wu Pend = How many WUs cached on that machine (unless you are using a separate caching progam like SETIDrive this will be 1, I have caches on all machines in case the Queue machine crashes)
When Should I use SETIQueue instead of SETIDriver?
When you want or need a central machine to control your upload / download cycle. SETIQueue can be set to transfer during specific time periods or on manual command. Useful when you wish to connect only when you won't otherwise be using your internet account or if off peak times are cheaper for you.
Where did the (SETIQueue) link come from?
GE-Raven posted it a LONG time ago and I just found it while browsing the old messages.
Setting up SETIQueue
Why are your slower machines putting out more WUs/day than the faster ones?
They are Dual CPU machines. Each one works on 2 WUs at the same time.
Post by: Glacier on May 06, 2004, 07:07:19 pm
In general, a 1-month cache isn't bad in terms of redundant results, but a 7-day cache is much better. An "optimal" cache (minimizing the likelihood that a result will have already passed integrity testing before you return it), however, shouldn't hold more than a 2 days of workunits. In the past, 1 month was pretty safe, but the ramifications of Moore's Law have made the cache window much smaller. Keep in mind, of course, that excepting the above case, redundancy is extremely important for testing the integrity of our data.
Post by: IKV Nemesis D7L on March 19, 2004, 09:08:53 pm
Quote:
A year or so back I posted this set of instructions to assist people in setting up the SETI commandline client with SETIDriver. There was a recent request for a repost of them. The original no longer exists but Mazeppa had archived it and reposted it for us.
Here is an update with corrected links.
Setting up the SETI command line client with SETIDriver
Some people have requested assistance on setting up the Windows SETI commandline client and a caching program. Here is my attempt to provide such aid. Hopefully it will be of use.
These instructions are based on Windows 98 SE and Windows 2000Pro and may need to be adjusted slightly for other versions of windows. I anticipate that most users of other versions of Windows can adapt these instructions to their version.
The download locations below are the ones to which the SETI site itself directs you. These instructions assume that during the setup you stay connected to the internet. If not you will need to reconnect to do Step 4:
Step 1: Create directory from which you will run the SETI program. If you are already running the graphical version you should create a new location, just in case .
Step 2A: Download the SETI client from the address below to the prepared directory.
Link below is to ftp site for downloading the commandline client.
ftp://alien.ssl.berkeley.edu/pub/setiathome-3.08.i386-winnt-cmdline.exe
Step 2B: Download the SETIDriver utility from the following link to the same directory.
Link to SETIDriver
You will also need a utility such as Winzip or PKUnzip to open the SETIDriver archive. Most people here will already have one.
Link to GPL'ed unzip program for Windows Link to 7-Zip
Step 3: Open the directory to which you downloaded the programs with Windows Explorer. Extract SETIDriver from the archive using your chosen UnZipping program. Create a directory under that you extracted into to run SETIDriver from.
Example:
C:\Seti\SETIDriver.zip when unzipped creates:
C:\Seti\SETIDriver\SETIDriver.exe
Step 4:Run the SETIdriver program by doubleclicking on it. Do not have the setiathome client in the same directory as SETIDriver at this point.
A/ A window will open entitled "SETI Driver - Select CLI Client". Open the directory with the SETI Client (setiathome-3.08.i386-winnt-cmdline.exe), select that client. Click OK
B/ Clear the Hideprocessing box by clicking on it.
C/ Change the Desired Cache Size to 1.
D/ Click transmit. SETI will open in a DOS shell.
Step 5: At this point you are presented with 2 options.
The choices are:
1/ setup a new account
and
2/ log into an existing account. Choose the appropriate option.
These instructions will continue based on using an existing account.
Choose option 2: It will display "E-mail address:". Type your address and hit enter. SETI will then connect to the internet and download a Work Unit.
Step 6: Fill in your options:
SETI client priority - I suggest Low.
All other options should be based on your personal setup and preferences. If other people use your system you may wish to use the Hide Processing options and choose not to Display Transmit. I suggest a cache size sufficient to last one week, in case of SETI outages or your having internet connection problems, you may wish longer or shorter.
Those like myself with a dialup connection will wish to choose to set Auto Transmit off unless working with a SETIQueue (a follow up message will deal with that topic). Those with a persistant connection may wish to choose Auto Transmit on to transmit as they process.
Those with multiple processors or with a Pentium 4 with Hyperthreading may choose more than one in the Maximum Processes: option. SETIDriver does detect 2 processors at least and autmatically adjusts to use both. I don't know if it detects hyper threading processors or more than 2 CPUs. If SETIDriver does not do so automatically choose one process per processor or two per hyperthreading processor. Hyperthreading and multiprocessor use requires a Operating System that can use them. Windows 2000Pro or Windows XP Pro. Windows 98SE cannot use these features and I suspect Windows XP Home cannot either.
Click on the save config button.
Step 7: Basically you are done. Some may wish to enable SETIdriver to load on bootup or put an icon on the desktop. Those issues should be easily dealt with.
Post by: nexa1 on March 19, 2004, 09:21:26 pm
This is just what I was looking for.
Post by: IKV Nemesis D7L on March 19, 2004, 09:55:16 pm
Quote:
You are such the mind reader. *grin* You kick A$$!!
This is just what I was looking for.
I have to share the credit with Mazeppa and others. Mazeppa was the original inspiration to write it up back in the old forums, back when the team was more active. When the old forums went down he saved a copy. Ultimately when people asked for a repost he sent it on to me so that I could update it (and save my own copy this time) and repost it in the off topic forum. Since then a link has been in my signature for any who cared to follow it. Much of the information here was posted by others long before I joined the team. My primary contribution was to gather together what the team knew into one place that was more easily accessible without reading everything in the SETI thread(s).
I and others on the team will gladly help anyone who needs assistance with SETI. The more the merrier. Whether you can do 1 work unit a month or a thousand a day (like Raven) each unit is appreciated. Any unit could be the one, it could be found by someone who processes one and only one or by a giant like Raven. Anyone could win this lottery, Raven buys more tickets than I do but I can still "win", so can you.
Post by: Demandred on March 21, 2004, 08:42:17 am
Post by: The Postman on March 21, 2004, 10:24:04 am
Post by: IKV Nemesis D7L on March 21, 2004, 10:39:42 am
Quote:
Is there any way to do SETI on a machine with no connection to the internet? I have a small server that spends most of each day idle that I do web development on and I don't want accessible from the internet. If it's possible to send the processed work units from my desktop I might as well do it. The server is running Windows 2000 Advanced Server.
Yes. Though I have not done so. Here is a quick off the top of my head explanation of how to do it. It is not nearly as detailed as my SETIDriver install instructions above.
You need to have a common type of removable media on both machines and a compatible (to each other) OS on both.
1/ Set up SETIDriver on the machine connected to the internet. If you are already running SETI on that machine you need to set up a second copy to use for transferring data for the offline machine.
2/ Download data in a quantity that can fit on your removable media.
3/ Setup SETIDriver on the offline machine. When it tries to connect to the internet to download a data packet stop it.
4/ Zip the data (not the whole seti driver setup just the data) that you downloaded on the connected machine and place on the removable media. I say zip so that long file names are preserved. You will also need to preserve the directory structure.
5/ Unzip the data onto the offline machines SETIDriver directory.
6/ Run SETIDriver on the offline machine
7/ Zip the processed data on the offline machine unzip it onto the online machine, run the second copy of SETIDriver to transfer data to SETI and new data from SETI.
8/ Return to step 4/ and repeat the cycle.
Obviously since this is a hassle you don't want to do it more often then absolutely neccesary. So CD/RW is the best media. WUs expire after 4 weeks so I would not download more than a 3 week supply at a time. On my network I keep a 2 week cache to allow for connection problems (Currently that is 609 WUs
my Queue takes 239MB). Since you are only tranferring text files you should be pretty immune to transferring a virus to the offline machine.
While experimenting to get things right I suggest that you only tranfer one or two WUs at a time. It should also be possible to setup a batch file to do the zipping and unzipping on both ends.
There are in fact other ways. If I were doing it I would probably use SETIQueue instead of SETIDriver and copy the whole SETIQueue between machines. But so far I have not (and neither has anyone else here) written up full instructions on setting up a SETIQueue install. SETIQueue might fail if the offline machine does not have a network address of its own, I am unsure as I have not actually tried it on an offline machine.
Good Luck and let us know how it works out.
If it works out you might wish to consider writing up some full instructions on how you did it, if so I would suggest adding it to this thread. No pressure, just a suggestion.
Post by: ActiveX on March 21, 2004, 10:55:04 am
Post by: IKV Nemesis D7L on March 21, 2004, 10:59:43 am
Quote:
When the DOS winda wont do anything else, is it okay to terminate it from Windows?
Yes. I have done so more than once, never with a problem.
Post by: ActiveX on March 21, 2004, 11:04:48 am
Post by: IKV Nemesis D7L on March 21, 2004, 11:11:35 am
Quote:
Am I goin to have to point it to the CLI every time I run it?
Not if you followed my setup instructions.
Post by: ActiveX on March 21, 2004, 11:12:48 am
Quote:Quote:
Am I goin to have to point it to the CLI every time I run it?
Not if you followed my setup instructions.
I'll review then...
Post by: ActiveX on March 21, 2004, 11:16:47 am
Post by: Demandred on March 21, 2004, 04:38:34 pm
Quote:Quote:
Is there any way to do SETI on a machine with no connection to the internet? I have a small server that spends most of each day idle that I do web development on and I don't want accessible from the internet. If it's possible to send the processed work units from my desktop I might as well do it. The server is running Windows 2000 Advanced Server.
Yes. Though I have not done so. Here is a quick off the top of my head explanation of how to do it. It is not nearly as detailed as my SETIDriver install instructions above.
You need to have a common type of removable media on both machines and a compatible (to each other) OS on both.
1/ Set up SETIDriver on the machine connected to the internet. If you are already running SETI on that machine you need to set up a second copy to use for transferring data for the offline machine.
2/ Download data in a quantity that can fit on your removable media.
3/ Setup SETIDriver on the offline machine. When it tries to connect to the internet to download a data packet stop it.
4/ Zip the data (not the whole seti driver setup just the data) that you downloaded on the connected machine and place on the removable media. I say zip so that long file names are preserved. You will also need to preserve the directory structure.
5/ Unzip the data onto the offline machines SETIDriver directory.
6/ Run SETIDriver on the offline machine
7/ Zip the processed data on the offline machine unzip it onto the online machine, run the second copy of SETIDriver to transfer data to SETI and new data from SETI.
8/ Return to step 4/ and repeat the cycle.
Obviously since this is a hassle you don't want to do it more often then absolutely neccesary. So CD/RW is the best media. WUs expire after 4 weeks so I would not download more than a 3 week supply at a time. On my network I keep a 2 week cache to allow for connection problems (Currently that is 609 WUs
Since you are only tranferring text files you should be pretty immune to transferring a virus to the offline machine.
While experimenting to get things right I suggest that you only tranfer one or two WUs at a time. It should also be possible to setup a batch file to do the zipping and unzipping on both ends.
There are in fact other ways. If I were doing it I would probably use SETIQueue instead of SETIDriver and copy the whole SETIQueue between machines. But so far I have not (and neither has anyone else here) written up full instructions on setting up a SETIQueue install. SETIQueue might fail if the offline machine does not have a network address of its own, I am unsure as I have not actually tried it on an offline machine.
Good Luck and let us know how it works out.
If it works out you might wish to consider writing up some full instructions on how you did it, if so I would suggest adding it to this thread. No pressure, just a suggestion.
I'll have a go at doing it tomorrow. It's actually not going to be that much of a hassle because my desktop is networked to the server, removing the need to use compatible media (I could set up ICS to give the server internet access but I don't feel comfortable having an always-on box running IIS that can be connected to from outside the network). If it works out, I'll see about writing a short guide.
Post by: IKV Nemesis D7L on March 21, 2004, 09:48:54 pm
Quote:
I'll have a go at doing it tomorrow. It's actually not going to be that much of a hassle because my desktop is networked to the server, removing the need to use compatible media (I could set up ICS to give the server internet access but I don't feel comfortable having an always-on box running IIS that can be connected to from outside the network). If it works out, I'll see about writing a short guide.
If the two machines are networked it becomes much easier. SETIQueue is the program you want. It allows you to run both (or many more) machines off of one queue. I don't have set up instructions for it though. I have it running on my main machine and it handles uploads/downloads for all four machines. It also gives you some statistical information. With SETIQueue you don't need SETIDriver but using SETIDriver on each individual machine does protect you from network problems your Queue system crashing does not bring everything to a halt.
Post by: ActiveX on April 05, 2004, 09:17:23 am
Post by: ChAotiCIllusion on April 05, 2004, 09:38:14 am
Post by: ActiveX on April 05, 2004, 10:08:32 am
Post by: IKV Nemesis D7L on April 05, 2004, 04:54:09 pm
Quote:
Okay, it still wants me to point it to the CLI each time it starts up, I dunno what I did wrong...as far as I can tell everything is right...
My guess is that you missed the following comment, specifically the part in red.
Quote:
Step 4:Run the SETIdriver program by doubleclicking on it. Do not have the setiathome client in the same directory as SETIDriver at this point .
Post by: ActiveX on April 05, 2004, 05:24:07 pm
the client is at C:/SETI/
Post by: IKV Nemesis D7L on April 05, 2004, 05:38:36 pm
Quote:
SETI Driver is at C:/SETI/SETIDriver/
the client is at C:/SETI/
Try a totally unconnected directory. Such as C:/SetiTemp/
Post by: ActiveX on April 05, 2004, 05:41:46 pm
Post by: IKV Nemesis D7L on April 05, 2004, 06:02:06 pm
Quote:
I moved the SETIDriver directory straight to C:/ and it din work...
Then as of now I don't have a clue. What OS are you using?
If you are using Win2000 or XP did you try it as administrator?
Post by: ActiveX on April 05, 2004, 06:07:37 pm
Post by: IKV Nemesis D7L on April 05, 2004, 06:15:43 pm
Quote:
WinME...
Ouch. My condolences. I have only tried those instructions on win98SE and Win2000Pro. I have had reports of it working on WinXP. But Windows ME I don't recall any feedback on. If I think of anything else to try I will pass it on. If you manage a solution please post it here for others. Good Luck.
I tried ME at a friends and didn't like it, neither did he. After a few too many tech support calls he refused to continue selling it. He kept having to use a Linux boot disk to recover from ME's self imposed damage.
Post by: ActiveX on April 05, 2004, 06:56:53 pm
Ima be going XP soon as my tax returns get in...
Post by: nexa1 on April 05, 2004, 09:37:46 pm
What about just starting over with a fresh install?
I know, it sounds dumb.
Post by: ActiveX on April 05, 2004, 09:55:04 pm
Post by: nexa1 on April 05, 2004, 10:00:05 pm
I meant setidrv. My bad.
Don't listen to me, Nem is better at this then I am.
Post by: ActiveX on April 05, 2004, 10:02:17 pm
Post by: IKV Nemesis D7L on April 06, 2004, 05:43:57 pm
One thing you might check if you are comfortable with regedit is if there is an entry for the SETI CLI. At this point I would not suggest editing anything in, just checking. Mine has one listed and saved in the temp directory. You might try putting a copy in the temp directory manually.
Still looking for a solution.
Post by: ActiveX on April 06, 2004, 06:00:50 pm
Post by: IKV Nemesis D7L on April 06, 2004, 06:10:24 pm
Quote:
The search come up negative when I search for SETI CLI, but SETI brought up a bunch of things...
It would not actually say "seti cli" it would say the name of the program file itself. In my case "setiathome-3.08.i386-winnt-cmdline.exe". Sorry for being unclear.
Post by: ActiveX on April 06, 2004, 06:13:17 pm
Post by: IKV Nemesis D7L on April 07, 2004, 10:18:47 pm
Quote:
It comes up negative...
I have come up with one more thing to try.
On my Win98SE machine I am using a CLI that has been renamed to SETIATHOME.EXE instead of setiathome-3.08.i386-winnt-cmdline.exe. The hyphens and extra periods may be something that Win98SE and WinME has trouble with. Try renaming the CLI something that stays withing the DOS 8.3 naming limits.
Post by: ActiveX on April 08, 2004, 04:46:00 pm
Im not going to worry about it, its not hard to point it there, but it would have been nice to let the comp do it itself if Im away...
Post by: IKV Nemesis D7L on April 11, 2004, 09:22:56 am
The below is off the SETI @ home message boards in response to my posting there.
Quote:
I have Windows ME and I run Seti Driver, Seti CLI 3.03, and Seti Spy all in the same folder. No need to point Seti Driver to the CLI, just start Seti Driver and it will pick it up.
It is worth a try. It may be that under WinME that SETIDriver just does not complete the move but still expects it to be done. If it does not work as is you may wish to copy the file to the SETIDriver directory while SETI is running.
One other random thought. Check the properites of the client and make sure that it is not read only.
Post by: ActiveX on April 11, 2004, 06:50:23 pm
Post by: IKV Nemesis D7L on April 11, 2004, 07:57:43 pm
Quote:
It worked...
Great! Too bad it took so long.
Post by: IKV Nemesis D7L on April 16, 2004, 09:43:28 pm
SETIQueue is a program that downloads SETI workunits and allows SETI clients (including the screensaver) to download from it rather than fromSETI @ Home. The client also can upload results to SETIQueue and all SETIQueue to send them in. It is useful on a network to allow fine control over your internet connections. It also keeps some statistics and does graphs.
Example statistics:
Code:
Name RPD RY RT Avg CPU Last Result Wu Pend
#4 8.07 8 9 2h51m 10m32s 15
#3 7.71 7 8 2h56m 15m29s 15
#2 12.92 13 12 3h42m 24m08s 15
#1 13.53 12 13 3h31m 50m05s 15
Totals:
42.23 40 42 3h20m 60
What do the headings on the table mean?
RPD= Returned / day - your average daily output by machine and total over the last 7 days.
RY= Returned Yesterday
RT= Returned today
Avg CPU= Average time/CPU
Last Result= How long since the last result (lets you know which if any machine is not processing)
Wu Pend = How many WUs cached on that machine (unless you are using a separate caching progam like SETIDrive this will be 1, I have caches on all machines in case the Queue machine crashes)
When Should I use SETIQueue instead of SETIDriver?
When you want or need a central machine to control your upload / download cycle. SETIQueue can be set to transfer during specific time periods or on manual command. Useful when you wish to connect only when you won't otherwise be using your internet account or if off peak times are cheaper for you.
Where did the (SETIQueue) link come from?
GE-Raven posted it a LONG time ago and I just found it while browsing the old messages.
Setting up SETIQueue
Why are your slower machines putting out more WUs/day than the faster ones?
They are Dual CPU machines. Each one works on 2 WUs at the same time.
Post by: Glacier on May 06, 2004, 07:07:19 pm
In general, a 1-month cache isn't bad in terms of redundant results, but a 7-day cache is much better. An "optimal" cache (minimizing the likelihood that a result will have already passed integrity testing before you return it), however, shouldn't hold more than a 2 days of workunits. In the past, 1 month was pretty safe, but the ramifications of Moore's Law have made the cache window much smaller. Keep in mind, of course, that excepting the above case, redundancy is extremely important for testing the integrity of our data.
Post by: IKV Nemesis D7L on March 19, 2004, 09:08:53 pm
Quote:
A year or so back I posted this set of instructions to assist people in setting up the SETI commandline client with SETIDriver. There was a recent request for a repost of them. The original no longer exists but Mazeppa had archived it and reposted it for us.
Here is an update with corrected links.
Setting up the SETI command line client with SETIDriver
Some people have requested assistance on setting up the Windows SETI commandline client and a caching program. Here is my attempt to provide such aid. Hopefully it will be of use.
These instructions are based on Windows 98 SE and Windows 2000Pro and may need to be adjusted slightly for other versions of windows. I anticipate that most users of other versions of Windows can adapt these instructions to their version.
The download locations below are the ones to which the SETI site itself directs you. These instructions assume that during the setup you stay connected to the internet. If not you will need to reconnect to do Step 4:
Step 1: Create directory from which you will run the SETI program. If you are already running the graphical version you should create a new location, just in case .
Step 2A: Download the SETI client from the address below to the prepared directory.
Link below is to ftp site for downloading the commandline client.
ftp://alien.ssl.berkeley.edu/pub/setiathome-3.08.i386-winnt-cmdline.exe
Step 2B: Download the SETIDriver utility from the following link to the same directory.
Link to SETIDriver
You will also need a utility such as Winzip or PKUnzip to open the SETIDriver archive. Most people here will already have one.
Link to GPL'ed unzip program for Windows Link to 7-Zip
Step 3: Open the directory to which you downloaded the programs with Windows Explorer. Extract SETIDriver from the archive using your chosen UnZipping program. Create a directory under that you extracted into to run SETIDriver from.
Example:
C:\Seti\SETIDriver.zip when unzipped creates:
C:\Seti\SETIDriver\SETIDriver.exe
Step 4:Run the SETIdriver program by doubleclicking on it. Do not have the setiathome client in the same directory as SETIDriver at this point.
A/ A window will open entitled "SETI Driver - Select CLI Client". Open the directory with the SETI Client (setiathome-3.08.i386-winnt-cmdline.exe), select that client. Click OK
B/ Clear the Hideprocessing box by clicking on it.
C/ Change the Desired Cache Size to 1.
D/ Click transmit. SETI will open in a DOS shell.
Step 5: At this point you are presented with 2 options.
The choices are:
1/ setup a new account
and
2/ log into an existing account. Choose the appropriate option.
These instructions will continue based on using an existing account.
Choose option 2: It will display "E-mail address:". Type your address and hit enter. SETI will then connect to the internet and download a Work Unit.
Step 6: Fill in your options:
SETI client priority - I suggest Low.
All other options should be based on your personal setup and preferences. If other people use your system you may wish to use the Hide Processing options and choose not to Display Transmit. I suggest a cache size sufficient to last one week, in case of SETI outages or your having internet connection problems, you may wish longer or shorter.
Those like myself with a dialup connection will wish to choose to set Auto Transmit off unless working with a SETIQueue (a follow up message will deal with that topic). Those with a persistant connection may wish to choose Auto Transmit on to transmit as they process.
Those with multiple processors or with a Pentium 4 with Hyperthreading may choose more than one in the Maximum Processes: option. SETIDriver does detect 2 processors at least and autmatically adjusts to use both. I don't know if it detects hyper threading processors or more than 2 CPUs. If SETIDriver does not do so automatically choose one process per processor or two per hyperthreading processor. Hyperthreading and multiprocessor use requires a Operating System that can use them. Windows 2000Pro or Windows XP Pro. Windows 98SE cannot use these features and I suspect Windows XP Home cannot either.
Click on the save config button.
Step 7: Basically you are done. Some may wish to enable SETIdriver to load on bootup or put an icon on the desktop. Those issues should be easily dealt with.
Post by: nexa1 on March 19, 2004, 09:21:26 pm
This is just what I was looking for.
Post by: IKV Nemesis D7L on March 19, 2004, 09:55:16 pm
Quote:
You are such the mind reader. *grin* You kick A$$!!
This is just what I was looking for.
I have to share the credit with Mazeppa and others. Mazeppa was the original inspiration to write it up back in the old forums, back when the team was more active. When the old forums went down he saved a copy. Ultimately when people asked for a repost he sent it on to me so that I could update it (and save my own copy this time) and repost it in the off topic forum. Since then a link has been in my signature for any who cared to follow it. Much of the information here was posted by others long before I joined the team. My primary contribution was to gather together what the team knew into one place that was more easily accessible without reading everything in the SETI thread(s).
I and others on the team will gladly help anyone who needs assistance with SETI. The more the merrier. Whether you can do 1 work unit a month or a thousand a day (like Raven) each unit is appreciated. Any unit could be the one, it could be found by someone who processes one and only one or by a giant like Raven. Anyone could win this lottery, Raven buys more tickets than I do but I can still "win", so can you.
Post by: Demandred on March 21, 2004, 08:42:17 am
Post by: The Postman on March 21, 2004, 10:24:04 am
Post by: IKV Nemesis D7L on March 21, 2004, 10:39:42 am
Quote:
Is there any way to do SETI on a machine with no connection to the internet? I have a small server that spends most of each day idle that I do web development on and I don't want accessible from the internet. If it's possible to send the processed work units from my desktop I might as well do it. The server is running Windows 2000 Advanced Server.
Yes. Though I have not done so. Here is a quick off the top of my head explanation of how to do it. It is not nearly as detailed as my SETIDriver install instructions above.
You need to have a common type of removable media on both machines and a compatible (to each other) OS on both.
1/ Set up SETIDriver on the machine connected to the internet. If you are already running SETI on that machine you need to set up a second copy to use for transferring data for the offline machine.
2/ Download data in a quantity that can fit on your removable media.
3/ Setup SETIDriver on the offline machine. When it tries to connect to the internet to download a data packet stop it.
4/ Zip the data (not the whole seti driver setup just the data) that you downloaded on the connected machine and place on the removable media. I say zip so that long file names are preserved. You will also need to preserve the directory structure.
5/ Unzip the data onto the offline machines SETIDriver directory.
6/ Run SETIDriver on the offline machine
7/ Zip the processed data on the offline machine unzip it onto the online machine, run the second copy of SETIDriver to transfer data to SETI and new data from SETI.
8/ Return to step 4/ and repeat the cycle.
Obviously since this is a hassle you don't want to do it more often then absolutely neccesary. So CD/RW is the best media. WUs expire after 4 weeks so I would not download more than a 3 week supply at a time. On my network I keep a 2 week cache to allow for connection problems (Currently that is 609 WUs
my Queue takes 239MB). Since you are only tranferring text files you should be pretty immune to transferring a virus to the offline machine.
While experimenting to get things right I suggest that you only tranfer one or two WUs at a time. It should also be possible to setup a batch file to do the zipping and unzipping on both ends.
There are in fact other ways. If I were doing it I would probably use SETIQueue instead of SETIDriver and copy the whole SETIQueue between machines. But so far I have not (and neither has anyone else here) written up full instructions on setting up a SETIQueue install. SETIQueue might fail if the offline machine does not have a network address of its own, I am unsure as I have not actually tried it on an offline machine.
Good Luck and let us know how it works out.
If it works out you might wish to consider writing up some full instructions on how you did it, if so I would suggest adding it to this thread. No pressure, just a suggestion.
Post by: ActiveX on March 21, 2004, 10:55:04 am
Post by: IKV Nemesis D7L on March 21, 2004, 10:59:43 am
Quote:
When the DOS winda wont do anything else, is it okay to terminate it from Windows?
Yes. I have done so more than once, never with a problem.
Post by: ActiveX on March 21, 2004, 11:04:48 am
Post by: IKV Nemesis D7L on March 21, 2004, 11:11:35 am
Quote:
Am I goin to have to point it to the CLI every time I run it?
Not if you followed my setup instructions.
Post by: ActiveX on March 21, 2004, 11:12:48 am
Quote:Quote:
Am I goin to have to point it to the CLI every time I run it?
Not if you followed my setup instructions.
I'll review then...
Post by: ActiveX on March 21, 2004, 11:16:47 am
Post by: Demandred on March 21, 2004, 04:38:34 pm
Quote:Quote:
Is there any way to do SETI on a machine with no connection to the internet? I have a small server that spends most of each day idle that I do web development on and I don't want accessible from the internet. If it's possible to send the processed work units from my desktop I might as well do it. The server is running Windows 2000 Advanced Server.
Yes. Though I have not done so. Here is a quick off the top of my head explanation of how to do it. It is not nearly as detailed as my SETIDriver install instructions above.
You need to have a common type of removable media on both machines and a compatible (to each other) OS on both.
1/ Set up SETIDriver on the machine connected to the internet. If you are already running SETI on that machine you need to set up a second copy to use for transferring data for the offline machine.
2/ Download data in a quantity that can fit on your removable media.
3/ Setup SETIDriver on the offline machine. When it tries to connect to the internet to download a data packet stop it.
4/ Zip the data (not the whole seti driver setup just the data) that you downloaded on the connected machine and place on the removable media. I say zip so that long file names are preserved. You will also need to preserve the directory structure.
5/ Unzip the data onto the offline machines SETIDriver directory.
6/ Run SETIDriver on the offline machine
7/ Zip the processed data on the offline machine unzip it onto the online machine, run the second copy of SETIDriver to transfer data to SETI and new data from SETI.
8/ Return to step 4/ and repeat the cycle.
Obviously since this is a hassle you don't want to do it more often then absolutely neccesary. So CD/RW is the best media. WUs expire after 4 weeks so I would not download more than a 3 week supply at a time. On my network I keep a 2 week cache to allow for connection problems (Currently that is 609 WUs
Since you are only tranferring text files you should be pretty immune to transferring a virus to the offline machine.
While experimenting to get things right I suggest that you only tranfer one or two WUs at a time. It should also be possible to setup a batch file to do the zipping and unzipping on both ends.
There are in fact other ways. If I were doing it I would probably use SETIQueue instead of SETIDriver and copy the whole SETIQueue between machines. But so far I have not (and neither has anyone else here) written up full instructions on setting up a SETIQueue install. SETIQueue might fail if the offline machine does not have a network address of its own, I am unsure as I have not actually tried it on an offline machine.
Good Luck and let us know how it works out.
If it works out you might wish to consider writing up some full instructions on how you did it, if so I would suggest adding it to this thread. No pressure, just a suggestion.
I'll have a go at doing it tomorrow. It's actually not going to be that much of a hassle because my desktop is networked to the server, removing the need to use compatible media (I could set up ICS to give the server internet access but I don't feel comfortable having an always-on box running IIS that can be connected to from outside the network). If it works out, I'll see about writing a short guide.
Post by: IKV Nemesis D7L on March 21, 2004, 09:48:54 pm
Quote:
I'll have a go at doing it tomorrow. It's actually not going to be that much of a hassle because my desktop is networked to the server, removing the need to use compatible media (I could set up ICS to give the server internet access but I don't feel comfortable having an always-on box running IIS that can be connected to from outside the network). If it works out, I'll see about writing a short guide.
If the two machines are networked it becomes much easier. SETIQueue is the program you want. It allows you to run both (or many more) machines off of one queue. I don't have set up instructions for it though. I have it running on my main machine and it handles uploads/downloads for all four machines. It also gives you some statistical information. With SETIQueue you don't need SETIDriver but using SETIDriver on each individual machine does protect you from network problems your Queue system crashing does not bring everything to a halt.
Post by: ActiveX on April 05, 2004, 09:17:23 am
Post by: ChAotiCIllusion on April 05, 2004, 09:38:14 am
Post by: ActiveX on April 05, 2004, 10:08:32 am
Post by: IKV Nemesis D7L on April 05, 2004, 04:54:09 pm
Quote:
Okay, it still wants me to point it to the CLI each time it starts up, I dunno what I did wrong...as far as I can tell everything is right...
My guess is that you missed the following comment, specifically the part in red.
Quote:
Step 4:Run the SETIdriver program by doubleclicking on it. Do not have the setiathome client in the same directory as SETIDriver at this point .
Post by: ActiveX on April 05, 2004, 05:24:07 pm
the client is at C:/SETI/
Post by: IKV Nemesis D7L on April 05, 2004, 05:38:36 pm
Quote:
SETI Driver is at C:/SETI/SETIDriver/
the client is at C:/SETI/
Try a totally unconnected directory. Such as C:/SetiTemp/
Post by: ActiveX on April 05, 2004, 05:41:46 pm
Post by: IKV Nemesis D7L on April 05, 2004, 06:02:06 pm
Quote:
I moved the SETIDriver directory straight to C:/ and it din work...
Then as of now I don't have a clue. What OS are you using?
If you are using Win2000 or XP did you try it as administrator?
Post by: ActiveX on April 05, 2004, 06:07:37 pm
Post by: IKV Nemesis D7L on April 05, 2004, 06:15:43 pm
Quote:
WinME...
Ouch. My condolences. I have only tried those instructions on win98SE and Win2000Pro. I have had reports of it working on WinXP. But Windows ME I don't recall any feedback on. If I think of anything else to try I will pass it on. If you manage a solution please post it here for others. Good Luck.
I tried ME at a friends and didn't like it, neither did he. After a few too many tech support calls he refused to continue selling it. He kept having to use a Linux boot disk to recover from ME's self imposed damage.
Post by: ActiveX on April 05, 2004, 06:56:53 pm
Ima be going XP soon as my tax returns get in...
Post by: nexa1 on April 05, 2004, 09:37:46 pm
What about just starting over with a fresh install?
I know, it sounds dumb.
Post by: ActiveX on April 05, 2004, 09:55:04 pm
Post by: nexa1 on April 05, 2004, 10:00:05 pm
I meant setidrv. My bad.
Don't listen to me, Nem is better at this then I am.
Post by: ActiveX on April 05, 2004, 10:02:17 pm
Post by: IKV Nemesis D7L on April 06, 2004, 05:43:57 pm
One thing you might check if you are comfortable with regedit is if there is an entry for the SETI CLI. At this point I would not suggest editing anything in, just checking. Mine has one listed and saved in the temp directory. You might try putting a copy in the temp directory manually.
Still looking for a solution.
Post by: ActiveX on April 06, 2004, 06:00:50 pm
Post by: IKV Nemesis D7L on April 06, 2004, 06:10:24 pm
Quote:
The search come up negative when I search for SETI CLI, but SETI brought up a bunch of things...
It would not actually say "seti cli" it would say the name of the program file itself. In my case "setiathome-3.08.i386-winnt-cmdline.exe". Sorry for being unclear.
Post by: ActiveX on April 06, 2004, 06:13:17 pm
Post by: IKV Nemesis D7L on April 07, 2004, 10:18:47 pm
Quote:
It comes up negative...
I have come up with one more thing to try.
On my Win98SE machine I am using a CLI that has been renamed to SETIATHOME.EXE instead of setiathome-3.08.i386-winnt-cmdline.exe. The hyphens and extra periods may be something that Win98SE and WinME has trouble with. Try renaming the CLI something that stays withing the DOS 8.3 naming limits.
Post by: ActiveX on April 08, 2004, 04:46:00 pm
Im not going to worry about it, its not hard to point it there, but it would have been nice to let the comp do it itself if Im away...
Post by: IKV Nemesis D7L on April 11, 2004, 09:22:56 am
The below is off the SETI @ home message boards in response to my posting there.
Quote:
I have Windows ME and I run Seti Driver, Seti CLI 3.03, and Seti Spy all in the same folder. No need to point Seti Driver to the CLI, just start Seti Driver and it will pick it up.
It is worth a try. It may be that under WinME that SETIDriver just does not complete the move but still expects it to be done. If it does not work as is you may wish to copy the file to the SETIDriver directory while SETI is running.
One other random thought. Check the properites of the client and make sure that it is not read only.
Post by: ActiveX on April 11, 2004, 06:50:23 pm
Post by: IKV Nemesis D7L on April 11, 2004, 07:57:43 pm
Quote:
It worked...
Great! Too bad it took so long.
Post by: IKV Nemesis D7L on April 16, 2004, 09:43:28 pm
SETIQueue is a program that downloads SETI workunits and allows SETI clients (including the screensaver) to download from it rather than fromSETI @ Home. The client also can upload results to SETIQueue and all SETIQueue to send them in. It is useful on a network to allow fine control over your internet connections. It also keeps some statistics and does graphs.
Example statistics:
Code:
Name RPD RY RT Avg CPU Last Result Wu Pend
#4 8.07 8 9 2h51m 10m32s 15
#3 7.71 7 8 2h56m 15m29s 15
#2 12.92 13 12 3h42m 24m08s 15
#1 13.53 12 13 3h31m 50m05s 15
Totals:
42.23 40 42 3h20m 60
What do the headings on the table mean?
RPD= Returned / day - your average daily output by machine and total over the last 7 days.
RY= Returned Yesterday
RT= Returned today
Avg CPU= Average time/CPU
Last Result= How long since the last result (lets you know which if any machine is not processing)
Wu Pend = How many WUs cached on that machine (unless you are using a separate caching progam like SETIDrive this will be 1, I have caches on all machines in case the Queue machine crashes)
When Should I use SETIQueue instead of SETIDriver?
When you want or need a central machine to control your upload / download cycle. SETIQueue can be set to transfer during specific time periods or on manual command. Useful when you wish to connect only when you won't otherwise be using your internet account or if off peak times are cheaper for you.
Where did the (SETIQueue) link come from?
GE-Raven posted it a LONG time ago and I just found it while browsing the old messages.
Setting up SETIQueue
Why are your slower machines putting out more WUs/day than the faster ones?
They are Dual CPU machines. Each one works on 2 WUs at the same time.
Post by: Glacier on May 06, 2004, 07:07:19 pm
In general, a 1-month cache isn't bad in terms of redundant results, but a 7-day cache is much better. An "optimal" cache (minimizing the likelihood that a result will have already passed integrity testing before you return it), however, shouldn't hold more than a 2 days of workunits. In the past, 1 month was pretty safe, but the ramifications of Moore's Law have made the cache window much smaller. Keep in mind, of course, that excepting the above case, redundancy is extremely important for testing the integrity of our data.