Terra is only compiled for windows systems. I have used it in Win95,98,NT and 2000 without problems. Oh well...
I have used IBM & DELL hardware only.
If you find any problems in some hardware-windows combination - please let me know.
Terra itself doesn't use much memory but in order to use hash tables and EGTB's more memory is needed. Don't allocate more hash space than your system can handle otherwise Windows will start swapping memory to disk and that will severely slow down Terra. Listen to the disk and if the swapping take place during Terra's thinking, lower the hash table settings .
The faster processor you have, the stronger Terra will play. Typically it will search one ply deeper with 3-4 times faster processor. Some measurements shows that doubling he speed will earn about 70 rating points (ELO). I'm not sure if this applies to Terra but it should be something like that.
I've developed Terra on a PII 300 MHz and that seems to be way below what is standard today. One of these days I will upgrade my system....
It will be interesting to hear from users with faster computers and their results. Maybe it is possible to better optimize the compilation parameters for faster computers than mine.
If you are running other programs in parallel with Terra on the same PC, the speed of Terra will slow down and make things worse.
The opening book is residing on the disk. The more space the bigger opening book is possible. On most
systems this is no big issue
anymore and of course it is not necessary to use a book at all or just a small one.
EGTB's it's another issue. They need disk space!
Full 3, 4 and 5 men tables requires 7.5 GigaBytes. When we come to 6-men tables we are talking about
Terabytes or was it Terrabytes
This program is not prepared for multiprocessor systems. I will not care about that before I have such a system myself.
Please give your comments in WinBoard Forum or email me. This document was updated 2004-08-02.