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

Help me use SetiDriver

Ben98SentraSE

Senior member
Ok, I've finally got a chance to try it and I can't get it to start processing a WU. I chose the Seti CLI client for it to use, max processes to 1, Desired cache size to 1, entered in my proxy server IP which is the same machine (maybe that's the problem?) Did Save Config, transmitted a million times, clicked on Use SETI Driver for progress monitoring, clicked on update progress now several times, and it won't process any WUs, not to mention trying to continue the current WU in progress.

Help 🙁
 
Ok I just got it to work. Weird! I chose "new client" to begin with and when I chose my client it deleted the CLI! What the hell? I moved it back there and transmitted and now it's running fine.

Why did it delete my CLI program?!?!
 
Ben - as soon as you start configuring SetiDriver, it immediately defaults to setting the cache size to 1 and proceeds to try to connect to seti in the background to grab a WU once you get your proxy info in there (if that's what's required for it to connect). While you continue to configure, it's usually already running the WU in the background.

But... at least you got it working though... 🙂
 
Ben,

<< &quot;new client&quot; >>

is a neat feature, but misunderstood. If you have SetiDriver up and running and a NEW Client is realeased, you can copy it to the directory (with a unique name) and use that button. It will finish the current WU with the &quot;old&quot; client and then start the new WU with the new client. It doesn't delete the old WU imeadiately, rather it changes the name to &quot;old...&quot; and copies it to the directory of the currently active WU.
 
Assimilated 2 more PCs tonight. 🙂 I feel so evil assimilating PCs at work after everyone goes home. 🙂

I'll assimilate a few at a time so it won't take a lot of notice for people. When I explain that I'm using their extra CPU cycles for a worthly cause, instead of the computer sitting there idle since it's on all the time anyways, and that it will be completely seamless and they won't notice a thing, they warm right up to it.

The *only* issue I may see from here is that most of the computers here are turned off at night. Basically all of the hourly folk's PCs. They have to reboot them so damned often I would hate for them to leave them on all night and make it more of an inconvience for them to have to reboot more. There would be no more security issues than there are now since the only people after hours who would have access to them would be the cleaning people, but several of the management people's PCs are left on anyways and they could get to them. They are all 9x machines so the cleaning people could just hit Cancel on the Windows Networking logon screen anyways and screw up the local PC. So I don't see it as a new security threat either. I hope they won't think power is a factor. Potentially it would mean about 30 more PCs on around the clock. I would explain to them that the monitors and printers are what suck up most of the power. What was that one fact about how much power a computer uses? Something in comparison to a 60 watt bulb or a TV?

Most of the machines are Pentium-class boxes, but some are PII's, PIII's, and PPros. I just assimilated a PIII of unknown MHz and a PPro 200 256k. 🙂

Let the work assimilations commence! BWHAHAHAHAH!!! 🙂

And no, my signature is not at all up to date... 🙂
 
On those win9x machines you will find it very useful to locate a file in your windows directory named &quot;conagent.exe&quot; and turn off the &quot;warn if active&quot; option (or something like that, on the last tab) under the file's properties. This will keep your machines from hanging when trying to shut down or reboot.
 
If you get to assimilate any NT or W2K machines, let me or Office Boy know, so we can make up an install disk that installs SETI as a service. This way it'll run at the logon screen.
 
As for the power issue, you could probably equate a basic computer (no monitor) to a 60 or 100 watt bulb, but I would be very afraid of a computer that used as much power as a standard TV, since a TV is about the equivalent of a 600 watt bulb in power usage... 😉
 
Binky:

When I run conagent.exe it just flashes up a DOS box and ends immediately. Does the program require a switch or something? How can I execute it properly? I'm doing it from Start -> Run. It won't run from a DOS box.
 
Back
Top