Topic: Installing SETIDriver and the SETI@Home commandline client  (Read 14061 times)

0 Members and 3 Guests are viewing this topic.

ActiveX

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #60 on: April 05, 2004, 05:41:46 pm »
I moved the SETIDriver directory straight to C:/ and it din work...

IKV Nemesis D7L

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #61 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?  

ActiveX

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #62 on: April 05, 2004, 06:07:37 pm »
WinME...

IKV Nemesis D7L

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #63 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.  

ActiveX

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #64 on: April 05, 2004, 06:56:53 pm »
:P

Ima be going XP soon as my tax returns get in...

nexa1

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #65 on: April 05, 2004, 09:37:46 pm »
 It is working great for me and I have XP.

  What about just starting over with a fresh install?
 I know, it sounds dumb.  

ActiveX

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #66 on: April 05, 2004, 09:55:04 pm »
Im not reinstalling WinMe ever again, the next clean sweep I do will be followed with an install of XP...

nexa1

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #67 on: April 05, 2004, 10:00:05 pm »
no no no

I meant setidrv.  My bad.

  Don't listen to me, Nem is better at this then I am.  

ActiveX

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #68 on: April 05, 2004, 10:02:17 pm »
 

IKV Nemesis D7L

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #69 on: April 06, 2004, 05:43:57 pm »
I have posted on the SETI @ Home message boards asking for help.  So far nothing that we have not already covered.  

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.  

ActiveX

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #70 on: April 06, 2004, 06:00:50 pm »
The search come up negative when I search for SETI CLI, but SETI brought up a  bunch of things...

IKV Nemesis D7L

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #71 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.    

ActiveX

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #72 on: April 06, 2004, 06:13:17 pm »
It comes up negative...

IKV Nemesis D7L

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #73 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.    

ActiveX

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #74 on: April 08, 2004, 04:46:00 pm »
That din work either...

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...

IKV Nemesis D7L

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #75 on: April 11, 2004, 09:22:56 am »
I don't give up easily.  

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.  

ActiveX

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #76 on: April 11, 2004, 06:50:23 pm »
It worked...

IKV Nemesis D7L

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #77 on: April 11, 2004, 07:57:43 pm »
Quote:

It worked...  




Great!   Too bad it took so long.    

IKV Nemesis D7L

  • Guest
A link to setting up SETIQueue.
« Reply #78 on: April 16, 2004, 09:43:28 pm »
What is SETIQueue?

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.  

           

Glacier

  • Guest
Re: Installing SETIDriver and the SETI@Home commandline client
« Reply #79 on: May 06, 2004, 07:07:19 pm »
Here is a thought on caching I found on the seti@home FAQ:

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.