Yah.
Run dnetc with the -install switch to install it as a service. This is pretty much invisible in Win9x, because there isn't an easy way to show what services are running(is it the same in ME?). It'll show up in NT or 2000 under the services as "distributed.net client unless you name it otherwise(what's the command line for this? I know some remote cow programs can rename the client in the automated installs(which are nice, put in the machine name on the network and BANG! instant cow)).
Run it with -uninstall to get rid of the service.
BTW, this doesn't "install" anything except a service(a redirect to run a program at boot time and is invisible cept for the registry and the services icon on the control panel in NT and 2K). Remember to either do a dnetc -svcstart or use the net start command to start the service, because while -install installs a service, it doesn't start it. The d.net service will automatically start next time you boot if you don't want to manually start it.
This is a good way to prevent numbskulls from turning it off, plus it's running even when you aren't logged in.
Keep in mind, you shouldn't install it on computers that you don't have permission to run it on.
One more thing. If you're running NT or 2K, and you're using remote buffers, you should probably edit the service to use your login and PW to get access to shares. I did that for a while until I switched to a pproxy. I run 5 P3 933's and 3 P2 450's at work and I can't have them all logged in as me all the time, and I don't want them only to run when someone is logged in. Services are the only way to go at work.
I need sleep. NOW! MOO! How now brown cow!
/me passes out.
