Attn: anyone who has assimilated school computers....

[BiggieN]

if anyone can contact me via email and give me a run through as the proper way to put the cows on a school network of computers i would appreciate it. i have permission to use 5-8 computers in one unused lab which are PIII 500-700 mhz with 128mb-192mb of ram. i already installed it on my personal computers but i heard that it was different on school computers. they will be on win98se or ME if and when they upgrade.

Once again, I would like to ask anyone with an extra alpha cooler for a flip chip to sell it to me so i can devote my personal computer 24/6 to rc5 cracking. this is also my gaming computer but rc5 alone puts more heat on it then my games at full load by themsleves.

Every little bit counts right? These 5-8 computers are unused so they can be dedicated 24/7 to rc5 cracking. it is actually in a locked room, a storage room. it is a personal lan center for our games but since school started we won't be using it for games.

 

[DanC]

We LOVE YOU MAN! (Quote from One of Borg)

 

[BiggieN]

a day has gone and no emails have come...maybe i'll go join DPC and be Dutch for a while....J/K (normally there would be a smiley here but the new smileys is suck so i will refrain from using them) my email is in my sig. do i just install them as regularly done? i heard that there was a stealthing program for them. guess no one is interested in my herd. *sniff sniff* =*(

 

[ZapZilla]

You should run the client as a service. There are many ways to achieve this, here is one way:

During client installation, check boxes for enter configuration, and start client operation.

Then in configuration, set up things such as your email address, keyserver, packet size, OGR=0, etc. Also set up a log file, then set the "Disable all screen output" to "yes". After finishing installation...

Then explore the Distributed.net folder and make a short cut for the dnet client application, then edit its properties by adding

-config

[one space, then -config]

to the end of the command line.

Then rename the shortcut to "dnet -config" (or the like.)

You can then enter the configuration easily by using the shortcut.

When running as a service (hidden mode) you won't see any screen output, so you can view the log file, or quickly check the dates on the buff.in and buf.out files for client operation.

Hope this helps, if not ask again.

PS: The above does not include "Remote Cows" network stuff, but rather is for configuring each comp individually...[don't know 'nuthin 'bout remoting them thar networks-but I wanted to respond]

PPS: I think because you piggy-backed on this old thread you didn't get the responce you might have had you started your own thread...

 

[SSP]

Just to add (I know this is an old thread... but)

To install it as a service, use the "-install" [without the quotes] command (if you don't have access to a dos window, then do what Zapzilla said).

Then start the service by using "-svcstart" [with out the quotes].

Then on the key server settings, use HTTP, and port 80. This will let you get pass the firewall problem.

To make sure it has enough grass to feed on (work units), use the "-fetch" command. It'll give you an error if it can't connect to the key server.