SzG wrote:Matthias Gemuh wrote:
Look into debug file and tell us how many threads GUI is telling Hiarcs to use.
Best,
Matthias.
Here is an excerpt from the debug file.
================ SendFirstCommands(HIARCS 12 2CPU), nProtocol = 1, EngineCodeHex = 20000120 ====
SendFirstCommands UCI
SendToEng1Time 0000000062293710 : Eng1 (HIARCS 12 2CPU) -> uci
.
Scheduling StartEngineTimerEvent() for HIARCS 12 2CPU at 0000000062293710.
Waiting for HIARCS 12 2CPU.
Eng1 (HIARCS 12 2CPU) <- HIARCS by Mark John Uniacke
Eng1 (HIARCS 12 2CPU) <- Copyright (c) 1992-2008 Mark Uniacke, Applied Computer Concepts Ltd. All rights reserved.
Eng1 (HIARCS 12 2CPU) <- id name HIARCS 12 MP
Eng1 (HIARCS 12 2CPU) <- id author Mark John Uniacke
Eng1 (HIARCS 12 2CPU) <- option name Ponder type check default true
Eng1 (HIARCS 12 2CPU) <- option name Licensed To type combo default Gabor Szots var Gabor Szots
Eng1 (HIARCS 12 2CPU) <- option name Core Threads type spin min 1 max 4 default 4
Eng1 (HIARCS 12 2CPU) <- option name OwnBook type check default true
It looks that the engine is sent the command to use 4 CPU's and its own book. At the same time, the engine ChsGUI.uci looks like this:
option name Ponder type check default false
option name Licensed To type combo default var Gabor Szots
option name Core Threads type spin default 2 min 1 max 4
option name OwnBook type check default false
Now it looks that the engine is set to 2 CPU's and no own book.
