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

Dialup

B

bot2600

Platinum Member
Lets say someone has a box and they only connect to the internet every 3 days or so. Their machine is on 24/7. If I put the client on there, when they do connect, will it lag their connection while the dnet client fetches/flushes? I have 3 people that are on dialup that have given me permission to put the client on their boxes(I built the boxes) but I would NOT want it to interfer with their internet connection when they do get around to logging in.

Thanks,
Bot
 
My dialup will allow fetch&flush while loading pages, it just slows the loading a bit. Why not just let the client connect automatically when it needs to?
 
How would you set it to connect automatically. I have a few boxes out there that use AOL. And another uses Earthlink?
Daz
 
I think the clients default setting is to connect when it detects a connection and since its dialup it will detect it....
 
I believe the default is to trigger autodial when the client needs work.
The config options menu varies some from one client version to another, this box uses;
dnetc v2.8010-463-CTR-00071214 for Win32 (WindowsNT 4.0)
But I am pretty sure they all default to auto dialup. So unless the config has been changed, you should be okay.
 
I have set up several machines with the Dnet client on dial-up connections.

Here is what you should do.

with the 463 client-
2>Buffer update options
6>Keyserver/client connectivity options
9>Dial-up detection
option 1 enables auto dial when the client is running out of new work
option 2 is "lurk only" where the client will detect a connection and initiate a flush only then. Under the scenario you described, this option would be fine.

Be sure to buffer enough work to last the client for an extended period of time. You can use the time in hours option to automatically set this.
Also, and this I have found to be important, set your client prefferred block size to 33. The client has a default limit of 500 packets, and at the default block size of 8 work unit packets will limit you to a max of 4000 work units, which may not last a fast machine for an extended period of time. The block size of 33 means that the clent will request packets of 32 work units in size which is best for the proxies, keyservers and stats boxes anyway.

As far as the flushing process getting in the way of normal Internet use, the client runs at the lowest priority, even for use of the Internet connection. The client does not seem to interfere with this in any perceptable way.

As for AOL, ver. 6 (and I think 5) will work nicely as I have described above. it will not work with ver 4 or below, although you can manually flush.

Hope this helps.

viz
 
Well I won't be able to check these until Tuesday, I have them set to store 2000 Buffers. I have 1 machine that is flushed manually everyday, to my pproxy. But the work PC I like to keep hidden so noone messes with it. Boss tells me when the PCs turned on so I can flush it. I know that if its needed and a connection is made it will flush/fetch automatically. It would be nice to have it dialout automatically, so I can set the buff-in lower so a daily flush will happen. I get days that I dont get to flush it, and that sometimes screws things up with stats.
Eventhough it seems I may be knocking on Phatstlys door soon🙂
Daz
 
Thanks guys. From this conversation I gleaned that Dnet either does not effect the connection or effects it very little, therefore ON WITH THE ASSIMILATION! Heh. You guys have me saying it now.

Bot
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top