Let me get this straight...

[Marty]

If I'm running RC5 on a Win2K workstation that is oftentimes logged off, all I have to do to get it to run all the time is run "dnetc.exe -install" once?

Secondly, how can I make the computer flush more often than it fetches? I want it to buffer many blocks but still flush in, say, four hour intervals. How can I do this?

Thanks in advance...

Marty

 

[MWalkden]

My experience on Win2K in particular is that installing it as a service is as you just stated. You can easily check to see if it is running with the task manager or simply check you services.

The only way I can think of to make the client flush more often than fetching is to run a batch file as a scheduled task. [path]DNETC -FLUSH at the scheduled times. The client itself will 'update' as you have set it to in addition to this batch.

 

[Joe O]

Marty,
MKWalden'ssuggestion of a batch file will work. Another thing that you may check out is

<<

2) Buffer and Buffer Update Options

9) Additional buffer-level checking ==> 0 (none)

distributed.net client configuration: Buffer and Buffer Update Options
--------------------------------------------------------------------------

Additional buffer-level checking:

The following options are extensions to normal threshold management and are
not usually necessary:
0) no additional buffer-level checking. (default)
1) ensure that there is always work available.
2) ensure that all completed work is kept flushed.
3) both 1) and 2). (implied if 'Dialup detection options' are enabled)
4) update on per-project buffer exhaustion.

Options 1, 2 and 3 will cause the client to frequently check buffers levels.
(Frequency/interval is determined by the 'Buffer-level check interval' option)
You might want to use them if you have a single computer with a network
connection &quot;feeding&quot; other clients via a common set of buffers, or if you
want to ensure that completed work is flushed immediately.
Option 4 is a hint to the client to work on a single project as long as
possible (updating per-project buffers individually), rather than loop through
all active/enabled projects (one combined update per pass).

Default Setting: 0
Current Setting: 0
New Setting --> 0
>>


I think that sub option 2 is what you want