A note about CPU support:

Moby Dam uses the Intel/AMD 64-bit instruction set, including the POPCNT
instruction, supported since Intel first generation "Nehalem" (Core i) and
AMD "Barcelona" (K10) processors, dating from about 2008.
Moby Dam will not work on older generation CPUs.


A note about memory handling:

Moby Dam tries to use the Windows Large Page Support for the transposition
table memory to improve performance. For this to work, the program must be run
as administrator, and the user's account must previously have been granted the
"Lock Pages in Memory" privilege in the Group Policy Editor.
If these conditions are met, it improves speed by about 10-20%, and a line in
the engine log file will say "tt allocated with large pages."
If these conditions are not met, regular memory pages are allocated for the
transposition table.

The Linux version of Moby Dam uses the Transparent Hugepage Support of the
kernel; no special preparations are necessary. Its use is not noted in the
engine log file.


A note about "hub" mode:

While Moby Dam continues to support the DamExchange (DXP) protocol, it now
also supports the hub protocol as an alternative. It can be operated for
example with the graphical Hub 2.1 GUI that Fabien Letouzey created for his
Scan program, see https://hjetten.home.xs4all.nl/scan/scan.html .

To use the Hub GUI with Moby Dam in Windows, modify the two files
hub.ini and engine.ini in the hub_21 folder.
In this example, the mobydam folder is located inside the hub_21 folder,
and the endgame database files are in C:\Damend.

hub.ini:
change the engine-dir and engine-command settings, and if desired
the game-ponder setting

engine-dir = mobydam
engine-command = mobydam\mobydam.exe -e C:\Damend -b book\book.opn hub

game-ponder = true

engine.ini:
set the desired Moby Dam parameters, for example

book = true
ponder = true
threads = 4
tt-size = 26
bb-size = 6
