Chapter 13. Known problems

Generally problems and bugs can be expected. If it crashes, don't panic. Please try to reproduce the problem and report the bug to me.

Text scrolling in the various IGS output windows is strange on Windows 98. To fix this, I included a special Windows 98 compatible resource file. Replace C:\Program Files\glGo\share\resource.xrs with resource.xrs_win98 found in the same directory. This changes all textareas to be more Win98-friendly. Maybe the installer should do this automatically, but as I lack a proper Windows 98 test system I am currently unsure about this. Also try changing the "Force scrolling" option in the IGS preferences.

When opening a board on Windows, sometimes there are display artifacts. Once the window got a bit resized or moved, the artifacts are gone. Another good idea is to enable "Autohide starter" in the preferences, this seems to solve the issue as well. This does not happen on Linux. I don't know the reason for this.

If you run a GNU Go score estimation and kill the gnugo process via task manager or killall, glGo will crash.

The captures algorithm has trouble with Kos. When loading SGF files this could produce some weird results. With observed IGS games it should be ok as then glGo won't calculate captures itself but instead use the provided list sent from IGS.

On Linux, toggling the toolbar creates some artifacts; resize the window manually a little to fix this. I don't know why this happens, it's ok on Windows.

Automatch does not display a dialog. glGo will automatically select nmatch if available, which is far superior to automatch.

The localhost server mechanism on Windows is a potential security risk if you run Windows without firewall. However, if you do such, you have much more serious things to worry about than someone hacking your Go client.

Mac note: The new SGF parser on Mac has a tendency to crash on big files like Kogo. So on Mac the old SGF parser is the default setting. You can change it in the preferences dialog. On normal files (Kogo just isn't normal) the new parser works fine.


If you encounter trouble, please don't hesitate to tell me about it. What I don't know I cannot solve.