Let me say this one more time. The _only_ bug in 22.0 is the smpnice bug. If you tried to use the original 22.0, and manually set smpnice=1, and mt=n (where n at least 2), and ponder=off, then it would crash/hang when it incorrectly terminated the extra processes. The current version, which was put up within an hour of someone pointing out the problem does not have that problem.geots wrote:bob wrote:Can't answer the question about the "exit". I tried it and it works perfectly normally here, although I have never put it at the end of my .craftyrc file. The only advice I have ever given there is that the last line should generally be a blank line, because using notepad to create the file often leaves the last line without a CR/LF on the end, which causes the last .craftyrc command to be combined with the next command sent to the engine. But your problem with the exit makes no sense and it _certainly_ has no effect on endgame table usage in crafty.geots wrote:Jim, maybe i should not be complaining because this is a free version, but it looks to me like it has catastrophe written all over it, setting aside the 64 bit and MP/SP issue. I mean i have 5 previous versions loaded, and i have never seen anything like this. In the rc file i put my tb path. I knew it was right- because all my other versions recognize it. But 22.0 would not. I had no idea until Martin in our testing group said he couldnt make the engine work right until he removed the word "exit" from the last line of the rc file. Just on a hunch- i removed the word exit, and now it accesses TB perfectly. Help me out here, please. Was i supposed to know that? How in God's name would anyone know they had to do that. Or that the word "exit" would even have anything to do with TB. Lastly, i have the log set to OFF in the rc file, and i unticked it in parameters, and it is still creating the files faster than rabbits can multiply. And they are not 0kb files either. Do you have any idea how i can get them to stop creating the files. I know all this is not your responsibility- but maybe you can tell me something that will help.
If you set "log=off" in your crafty.rc file, crafty absolutely will not produce log files, unless the gui or operator is overriding that. If it does create logs, look in the first log.nnn file to see what is wrong with your log=off command. I play this way on the cluster since I don't want the files either when playing tens of thousands of games, and it does not produce them if this is done correctly.
It would be much better to check what you are doing, before calling this a "disaster" since this specific version has played 50,000 games in the last 2-3 days alone, and we have seen zero problems. Only issue I have found was the smpnice command had one fix that was lost, but this other stuff is simply not related to this version...
I'd almost bet that the "exit" has no cr/lf, and that will certainly wreck things, but that is not a fault of crafty, it is a fault of the notepad/wordpad editor not following the convention of ending each line with a CR/LF...
Much Thanks,
George
Guessing that you dont care a bit for UCI anyway, im figuring that "zero" of the these games were run in chessbase with the WB to Uci adapters. ( I know, the hell with CB) Its not possible that 1% of the test games were run WB converted to UCI- because if they had been- this version would have been put on hold.
there are no other known issues. I don't care whether it is wbtouci, or winboard or xboard, so long as the other end adheres to the xboard protocol, everything is working, whether it be in windows or in linux.
So this version had no reason to be "put on hold", none of the protocol stuff has changed one scintilla in many versions now, because it simply works. If you get a bad compile, or someone does not know about specific issues in egtb where Eugene does some aliasing that will break an optimizer if the wrong options are used, then there's little I can do about that. We have four of us working on this all the time. I play thousands of games a day, both on the cluster and on ICC. tracy, mike and peter are doing the same, some with windows, some with linux, and we are having zero problems.
No, we don't use ponder=off on ICC, but I test on the cluster that way all the time and know that it works just fine. I have not been testing with smpnice=1 since I wrote the changes and tested them last Fall prior to CCT10, but that is the only thing that was not recently tested and the only thing that has been identified as a real problem. And it was fixed within 24 hours of the release.
So calling this a "disaster" is only the result of something beyond my control. My versions work flawlessly. I can't control how others build/run the program and completely mangle the crafty.rc/.craftyrc settings and then complain when they cause problems. "exit" does nothing in the crafty.rc file. Except to work around a known problem that has been explained often enough to categorize it as a user error when it happens.
If you can point out a specific problem that is reproducible with winboard/xboard, or in text mode, I can fix it, if there is such a problem. But if it only happens when using wb2uci or whatever, and not in native winboard, that sort of suggests where the problem lies...
Your comments suggest it was poorly tested, which is completely wrong, with the sole exception of testing with smpnice=1, because that is not an efficient way to test due to the slight time loss it causes...

