Ubuntu 9.04
Play Tactical Game
Start From Current Position
eg:
8/8/8/8/6k1/1N6/5B2/2K5 w - - 0 1
Don't know if this matters: I play through several "I Resign" messages. (click
ok and continue).
SCID crashes. Terminal says "Segmentation Fault"
Any suggestions?
By the way, Is there a way to have
Gahh, I goofed when I said this:
Also, 32 bit Rybka under wine reports that it processes 436k nodes/sec.
> 64bit Rybka under microwine reports 300k nodes per sec for the same
> position. My wine won't run 64bit Rybka, so I don't know how that would
> fare.
I had throttled the 64Kbit Rybka down t
An update about this:
When I start Rybka under Scid (4.0 DEVEL), it creates one process per CPU,
> and each process runs at full CPU capacity. When I close the analysis window
> or quit Scid, only one Rybka process is killed (the one with the lowers PID,
> I think). The other processes go to 0% CP
> Pascal, may I make this another feature request for upcoming releases?
> In the "Game list" tab, could you
> - either allow me to move games up and down per drag and drop?
> - or when I right-click a game, in the menu that pops up, offer me the
> option to "Move this game up/down XY ranks".
If w
> In this case I admit that I prefer to dump it down in PGN, then use vi
> to add the lines and reimport the games. This is much faster than
> GUI-clicking in Scid, especially if you have similar lines. (And 26
> clipboards help a lot here...) I've also a simple perl script at hand
> that allows to
Dale Emery wrote:
Hi!
> Is there a preference or option I can set, in either Scid or
> Rybka, to instruct Scid to kill ALL Rybka threads and not just
> the first one?
> I do not know such an option in Scid. However, I wonder if it's a
> bug in Rybka as Scid sends a
Alexander Wagner wrote:
...
> What do you call your "testing group"?
The other engines I test against. Stockfish, Fruit, Crafty and so on.
...
>
> BTW: Did you get ProDeo running on Linux? I admit that I
> never really succeeded with the setup. (In case we could
> discuss this in PM, if you p
Hi Alexander,
>
> Is there a preference or option I can set, in either Scid or Rybka, to
>> instruct Scid to kill ALL Rybka threads and not just the first one?
>>
>
> I do not know such an option in Scid. However, I wonder if it's a bug in
> Rybka as Scid sends a proper quit signal to the engine
I believe such scripts work great, but sorry, I have no intentions to
become a programmer, nor do I have the time to learn scripting :)
For me, GUI-clicking is the only thing I manage. I really need simple,
fast and intuitive solutions, sorry.
Alexander Wagner wrote:
> In this case I admit tha
Dale Emery wrote:
Hi!
> When I Force Quit Scid (which I have to do now and then), one Rybka
> proces is killed, but the others keep running at 100% CPU speed. This
> turns my Mac Pro into a mighty, mighty furnace. I live in Sacramento,
> and have found that in August a furnace is not only unne
pso...@web.de wrote:
Hi!
> Yes, Benoit, that is a cunning workaround for a small Scidbase with 20
> games. Tagging 80 or more games by hand in a special header each might
> be harder, though.
Yes, the problem comes up once you exceed 20 games. (Ie. this afternoon ;)
In this case I admit that
Volker Pittlik wrote:
Hi!
>> A similar option is available in some UCI engines. There the
>> switch in question is called UCI_LimitStrength (this one has
>> to be set to "true") and UCI_Elo where you can set the
>> ELO-level the engine tries to simulate.
>>
>
> I know. But have you ever tried it
12 matches
Mail list logo
