UBBFriend: Email This Page to Someone!
Get 3DNow! Message Board
DCypher.Net Support Forum
need help flushing blocks
profile | register | preferences | faq | search
|
UBBFriend: Email This Page to Someone!
|
Get 3DNow! Message Board DCypher.Net Support Forum need help flushing blocks
|
| Author | Topic: need help flushing blocks |
| seanlong Follower of Athlon |
 posted February 08, 2000 10:35  
Hello, I have a computer running the gamma flux client, and it's on my LAN behind my win98SE maching running internet connection sharing. The first day or two I was running it, it would connect and flush just fine. I was also able to get it to flush to a proxy running on my gateway machine. It won't flush anymore over ICS, and I don't want to run the proxy because it causes my hard drive to twitch every 10 seconds whenever it's running. I can ping keys.dcypher.net from the computer running the dcypher client (300-350ms pings), but it still won't flush. All other programs that use the network will work correctly from this client computer as well. When the client tries to flush, the network activity lights on the network card and my hub blink, so somethings happening... Any assistance will be appreciated. Sean Long
[This message has been edited by seanlong (edited February 08, 2000).] IP: Logged |
| Osiris Priest of Athlon |
posted February 08, 2000 11:23
Make sure port 4356 is open. Steve IP: Logged |
| seanlong Follower of Athlon |
posted February 08, 2000 11:37
It's not being blocked. I even tried flushing with my network firewall blocker protection shield software thingy (it's not a proxy, not a true firewall) turned off, and it still wouldn't flush. If port 4356 was blocked, I wouldn't expect the proxy to work, but it does. The client came pre-configured with a static ip address instead of keys.dcypher.net, so I changed it back to keys.dcypher.net, and that didn't help. I'm kinda stumped. Everything else I use (including the distributed.net stuff) works fine. IP: Logged |
| Armin High Priest of Athlon |
posted February 08, 2000 11:51
I had a problem with that too because often the proxies would be busy and not accept the block. I am now running local proxies for both my networks and flush in 50 block quantities, that works very well. You may want to try a ramdisk for the proxy files to cut on the disk accesses. IP: Logged |
| seanlong Follower of Athlon |
posted February 08, 2000 12:14
More info - When I click flush on the GUI wrapper, my modem lights blink with both send and receive packets. The client displays "Sending xx blocks to the server, but never shows anything else. The modem lights blink for a few seconds then stop, and the client resumes it's work shortly thereafter. I'm not going to do too much system configuring just to get this thing to work... Running the proxy on my main computer isn't a very good option and I'm certainly not going to set up a ramdisk just for this one purpose. FWIW, I quit running the seti@home client because if it couldn't connect to the network on the first try, it would halt my computer until I clicked away the error message dialog box. That means I couldn't let it run unattended. The dcypher client is much better behaved than the seti client was, but I don't like the idea that I'll have to babysit it all the time. IP: Logged |
| Postmand_Per Follower of Athlon |
posted February 08, 2000 16:06
Do you have loggin enabled? If you have then try to look after some error-messages and post them here. Otherwise enabled it and try flush so the error get logged and then post it here. Mayby that could help identifying your problem.
------------------ IP: Logged |
| seanlong Follower of Athlon |
posted February 08, 2000 16:19
The error message reported in the log file is "network timeout" IP: Logged |
| Postmand_Per Follower of Athlon |
posted February 09, 2000 06:22
A bad connection maybe? ------------------ IP: Logged |
| seanlong Follower of Athlon |
posted February 09, 2000 08:22
The connection works fine. It's through a 100mpbs switch on my lan (fast!) straight to my gateway computer, and from there to dcypher. When I run the proxy on my gateway computer, it connects without any problems. I can run programs that use the internet just fine on the client computer as well, and I can ping keys.dcypher.net from the client computer with around 330ms pings and zero packet loss. IP: Logged |
| Postmand_Per Follower of Athlon |
posted February 09, 2000 14:42
If your gateway computer doesn't have any problems flushing the blocks then there must be some problems with ICS...can't help you with that. Why don't you just set up the other machines on your LAN to flush to your gateway machine? You don't have to have the pproxy running all the time, you can just start it when you want to flush and then wait until the clients has finished their current block and then let them automatically flush to your proxy and then flush the proxy to the keyserver. ------------------ IP: Logged |
| seanlong Follower of Athlon |
posted February 09, 2000 17:54
The reason I don't want to have to start and restart the proxy is that it's a big pain in the behind to have to babysit a project like this. I honestly don't enjoy doing that. I'm participating because I have an excess of cpu cycles that could go to a greater cause, not so I can fiddle around with the thing endlessly. I also need the setup to be self-sustaining (like the distributed.net clients I'm running) so I can go on vacation for 2 weeks and expect it to work all by itself. Plus my job takes me away for a few days at a time, so there are more shorter times that I need the distributed effort to be a hands off operation. If I want to constantly fiddle with something, I'll try to get Samba working again on my Linux box Thanks for the suggestions, I'm just afraid that "your computer and lan is broken and you're going to have to update manually" isn't all that good of an answer. I'm not slamming anyone, that's just the way it is from my point of view. Sean IP: Logged |
| Colin Morey Follower of Athlon |
posted February 09, 2000 18:30
Well, how about running a proxy on your gateway with a large buffer, I've tried this, and collected over 600 blocks of CSC in one go, and I was away for the week, if you don't feel that your gateway is stable enough to host the proxy for longer than 2 weeks, try it on another machine, and proxy it across to the gateway when you want to flush, Order goes something like this (good for modem users.) client => stable proxy (permanently up)=> gateway proxy (on when ever you want to flush) => main server,. if its the harddrive 'twitching' that's the problem, try running it (and the clients for a 20%+ speedup) on a ramdisk, (there are ones for win95/98 and WinNT/2000 +linux) and some can even autosave contents to a file every so often (i'm using a 2 min time), and autostart. Colin IP: Logged |
| Zypher Follower of Athlon |
posted February 09, 2000 18:36
You think thats bad? Try having 100+ blocks sitting in a buffer, that refuses to flush. Every time I try to flush, it REDUCES the number of blocks in the buffer WITHOUT me getting any credit for them at the other end. (stats) And I'm on a direct DSL connection...no proxies of any kind do I use...man that sounbds like Yoda, but anyway... My buffer right now is 124/2, and the actual blocks done is around 180...it stopped giving me credit this morning (I'm 60 in the hole, so to speak) and it seems the client doesn't "see" the only network connection on my computer. (dsl modem) 2 hours of dicking with it didn't work. I tried replacing static ip to keys.dcypher.net as well, no go :/ Every other program on my computer has no trouble with my connection... I saw something in Dcypher news about the 'internal network' having problems, then later they said it was 'all fixed'. I still can't flush the damn blocks.
You can install a dnet client on a computer and FORGET about it. I commandeered ~40 or so crappy P100 WinNT boxes, and the last I touched one of them was 18 months ago. (I stuck the client as a process on the master clone image, so when they get restored or reinstalled...you get the idea I enjoy Dcypher, and like that it trys to do something useful, RC5 is 64b[or]i[ng]t, 64bit is too weak, whoopdedo, I will now use 512bit IP: Logged |
| seanlong Follower of Athlon |
posted February 09, 2000 18:56
Amusingly enough, after griping about it in here for a few days, my GF client finally was able to flush. I didn't change anything, didn't even reboot after watching it fail to flush 30 minutes ago. It smells like a timing problem actually, with the timeout gate being too small. That's a guess of course 'cause I don't have a packet sniffer running or anything that lets me see what's really happening. IP: Logged |
| Postmand_Per Follower of Athlon |
posted February 10, 2000 05:07
Colin, Do you know where I could find a ramdrive to Win2000? ------------------ IP: Logged |
| LeBlatt Follower of Athlon |
posted February 10, 2000 08:04
RamDisk98 and RamDiskNT are shareware at http://www.jlajoie.com/ramdsk98 / Doubt it will work with 2K but it's worth a try ------------------ IP: Logged |
| Postmand_Per Follower of Athlon |
posted February 10, 2000 15:19
Thanks LeBlatt. The site says that there's a version there have been tested, and found working, under Win2000 RC2 so I'm going to try that out later tonight. ------------------ IP: Logged |
| Colin Morey Follower of Athlon |
posted February 10, 2000 21:55
Well, I'll be installing win2k final as ms Outlook has stopped collecting my email (shakes his head in disbelief (sp?) _not-). so I'll let you know how it goes.... Colin. *has just seen the person he was catching up with on the stats page sumbit 4000 blocks* IP: Logged |
| Arete Wish I had an Athlon |
posted February 11, 2000 01:10
I don't know if anyone else is having the same problem, but all today I've been having problems keeping a connection alive between keys.dcypher.net and my own machine. My pproxy is set to flush every 50 blocks, and I haven't managed a full flush in almost a day. Even when I manually flush the pproxy (f), the pproxy starts sending, then loses its connection to the keyserver after a few transfers. I don't know if this is the problem that you might be having, but this has been affecting me recently. Another thing to check is to make sure that the keyserver port that your .ini file has is the same as port that the master keyserver listens on. When I was first setting up my pproxy, the port settings (either in the client .ini's or the pproxy .ini) didn't match up at first. This prevented my clients from using the pproxy. Look for a very similar number, that's why I didn't spot it at first. IP: Logged |
| LeBlatt Follower of Athlon |
posted February 11, 2000 02:56
Yep the wrong number was like 4536 or something. can't recall if it was proxy listen or client send port, but it prevented clis to flush blocks. this was released early jan. IP: Logged |
| Postmand_Per Follower of Athlon |
posted February 11, 2000 17:29
That program works great with Win2000  It's very nice not have to listen to ones harddisk all the time
------------------ IP: Logged |
| adam04 Follower of Athlon |
posted February 12, 2000 10:11
I use Ramdisk NT. I use it on my dual celeron box running one instance of the client. I run another copy of the client normally. However there is almost no speed difference. Most people seem to get a 10% boost but I dont on the NT box (I do get speedups on Win 98 boxes and laptops but of the order of 5%) Anybody have any guesses? The spec is as follows Abit BP6 mobo Adam IP: Logged |
| Postmand_Per Follower of Athlon |
posted February 12, 2000 14:40
I didn't get any speed-improvements either. I'm just glad that I don't have to listen to my hdd any more
------------------ IP: Logged |
| Ken_g6 Follower of Athlon |
posted February 12, 2000 21:17
Okay, this is weird. I run ramdrive.sys for my ramdisk, on Win98, and I get that 10% speedup - but only when the client is running in a dos box and the dos box is selected. Adam, how were you running the client on those 98 boxes? Ken IP: Logged |
| adam04 Follower of Athlon |
posted February 13, 2000 09:38
Ken, Wierd. Usually I run GF in a minimised dos box but as you say when it is selected it does run faster. I estimate about 8%. Aren't computers fun. (This trick doesn't appear to work on the NT box though, at least for me) Adam IP: Logged |
| adam04 Follower of Athlon |
posted February 13, 2000 09:38
Ken, Wierd. Usually I run GF in a minimised dos box but as you say when it is selected it does run faster. I estimate about 8%. Aren't computers fun. (This trick doesn't appear to work on the NT box though, at least for me) Adam IP: Logged |
| Colin Morey Follower of Athlon |
posted February 14, 2000 17:04
Well, just for some info These compare speeds before and after using ramdiskNT Windows Nt 4 - from 110k to 120k average Rays per sec. These were with the same block, so as far as I am aware the speed increase should be roughly correct. Colin Morey IP: Logged |
| adam04 Follower of Athlon |
posted February 15, 2000 13:31
The highlighting of the dos box seems to spped up GF whether or not it is running on a ramdisk. I have a AMD 380Mhz Win 98 notebook which runs GF at 4800 Rays/s when the dos box is minimised and at 6300 Rays/s when the dos box is selected. A dramatic improvement. I have tried this trick on a NT box but there is no improvement. Adam IP: Logged |
| All times are ET (US) | next newest topic | next oldest topic |
|
|
|
|
|
|
All submissions are copyrighted by their respective authors and are not for re-use in any form without their explicit written consent.
Powered by: Ultimate Bulletin Board, Version 5.37
© Madrona Park, Inc., 1998 - 1999.
Membaca review slot online bisa menjadi panduan yang sangat berguna. Review sering kali memberikan informasi tentang RTP slot tertinggi dan pengalaman pemain sebelumnya. Dengan memilih slot gacor yang telah direkomendasikan, peluang untuk menang dapat meningkat. Jadi, jangan lewatkan untuk memeriksa ulasan sebelum mulai bermain.
At least 30 of them are _still_ sending in RC5 blocks that I get credit for. *18 months* without the client getting stalled, crashed, or stuck. This is during the same time the host OS, WinNT, DOES get stalled, crashed, and stuck