How do I run SETI on a rig not connected to the net?

[Niege]

I have an opportunity to run SETI on a rig that is not connected to the net and I don't know how to set it up, transfer WUs, transfer results etc. Any easy 'How To' thread or FAQ I can look at? Thanks!

 

[Electrode]

Quite a few methods I can think of:

1. Plain old sneakernetting. Put a SETI client on a floppy. Stick it in a connected computer and get a WU, then bring it over to the unconnected rig for processing, then bring it back to the connected computer to upload the result and get another WU. Repeat ad nausium.
2. Ghetto queue. Same thing, but with several clients, with a batch file or shell script to make them run one after another.
3. Run a SetiQueue on the unconnected box. Fill it up with WUs on a connected system, then bring it over to the unconnected rig. That'll keep it busy for awhile.
4. Connect it to your network! NICs are dirt cheap, and if running cable is a problem, there's always 802.11b

 

[Assimilator1]

If you are forced to transfer WU's & results via floppies then best & eastiest addon to use is SETIHide

It has an import/export function

If you use it & the sites instructions don't cut it ,then let us know here

 

[Spacehead]

If floppies are smaller than you need & both comps have CD burners or zip drives, try this.
I used CD-RW's & SETI Driver but you could probably use any caching add-on you want.
The only file attribute problem i had was one time my burner was giving me problems & i tried using my CD-ROM drive to put the finished WU's onto my connected computer. Attributes got all screwed up. I left the "note" at the bottom though, just so you're aware.
This has worked pretty well for me though.
Be aware of the way you format your CD too.



Getting started:
1. On the connected PC, create a SETI folder just for the non-connected PC. We'll call this SETI #1 for this example. Place a copy of the CLI.exe & SETI Driver in this folder.
2. Turn off the SETI client running on your connected PC. Start up SETIDRIVER in the SETI #1 folder, configure the # of WUs to cache, turn off auto-transmit, save config, then initiate transmit, let it download WUs.
3. Shutdown SETIDRIVER, cut/paste all of SETI #1 folder to zip or CD-RW.
4. Take ZIP or CD-ROM to non-connected PC.
5. Cut/paste the SETI #1 folder to the hard drive.
6. Right click on the folder and change attributes(if needed).
7. Start SETIDRIVER. Turn off auto-transmit. Save configuration.

Once WUs are completed on non-connected PC:
1. On non-connected PC, stop SETIDRIVER, cut/paste the entire SETI #1 folder to ZIP drive or CD-RW.
2. Take to connected PC, cut/paste the entire SETI #1 folder to the hard drive.
3. Right click on the folder and change attributes(if needed).
4. Turn off the SETI client running on your connected PC. Startup SETIDRIVER from SETI #1 folder, transmit completed WUs.
5. Once WUs transmitted, and new WUs filled, cut/paste SETI #1 to ZIP or CD-RW.
6. Take to non-connected PC, cut/paste SETI #1 folder on hard drive. Start SETIDRIVER.
7. repeat steps 1 through 5.


NOTE: If using CD-RW, be sure to change the properties of the folders/files from READ ONLY after copying them to the hard drive from the CD (if needed).

 

[Assimilator1]

Or you could still use the import/export functions on SETIHide ,though you'd need to do a similar thing to above & have SETIHide installed on your net connected PC too.
Btw SETIHide has much better logging features than SETIDriver ,though its icon doesn't change colour when its out of WU's etc.

 

[Niege]

Thanks, guys. I really needed a very basic step by step, Spacehead! More WUs on the way!