Author: Komputer Korner
Date: 08:10:41 05/29/98
Go up one level in this thread
Sorry, if it appeared that way Ulrich, you need a tougher skin. This problem may not be Comet's fault. You take things too personally. If you want plaudits for making a great program you have my endorsement. Comet is great!!!!!!! I am just trying to get a match working with Crafty correctly. Any feedback you should appreciate. Don't slander the messenger just because there is a problem which might lie elsewhere( maybe Winboard or Crafty). We love Comet. We want to get Comet vs Crafty working in matches correctly. Please Ulrich don't get upset by us peons giving you feedback. Maybe this is a cultural thing because in North America, bug reporters give programmers fits and the poor programmer has to absorb these reports thinking that he has failed somewhere when in reality it is the programmer like you who is the God and it is peons like me who are your lowly faithful admirers. Just because I hype bug reports, don't get upset with that. Remember if you hadn't written Comet, we wouldn't have such a great program to discuss, so all of us peons are grateful even if you don't think that we show it enough. Long live Comet!!!!!!! On May 29, 1998 at 03:45:48, Ulrich Tuerke wrote: >On May 29, 1998 at 01:13:05, Komputer Korner wrote: > >>... >> >>I checked the log file of Comet. I guess it must have a limit of 32Mb >>hash table. >>I gave Comet 48Mb not knowing that the limit is 32Mb. I will change >>Comet's hash table size. However I have 144Mb of RAM in a WIN NT 4 >>system. WIN NT 4 unlike WIN 95 DOES NOT load 2 copies of the same >>application including hash tables every time into memory ( one into >>cache and the other into main memory). WIN NT 4 does not do this so you >>can run programs like Nimzo 98 and Crafty which will take all the hash >>RAM you can give it in WIN NT 4 without disk swapping. In WIN 95, you >>have to limit the hash tables to less than 50% of the RAM. Fritz is an >>exception. It does not have this problem in WIN 95 because it has >>extension modules that load as separate processes for the engines. They >>somehow get around the WIN 95 problem of loading 2 copies of a program. >>So my system and setup is not the cause of these timing problems. One >>simple solution would be for every engine programmer in Winboard not to >>send a move before the engine resigns, instead the engine should just >>resign if it is going to resign. > >Sorry, I can't follow your arguments. >Anyway, I am not quit happy with the way you treated the problem, KK. >Instead of emailing a bug report with debug data to me, you posted the >thing here with a title which makes my program appear ridiculous. >I will not support this problem any more, anyway wouldn't know what to >do.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.