This preset is probably automated with GAME code generted by the Play-Test Applet. (I.e. the code in the betza.txt include.) This code indeed uses the 'onboard' test in several places, mostly for parsing the user's input move.
But the error message appears for me on invoking the preset from the link in the article, which should bring me to the start position. Only the Pre-Game GAME code should be executed at that point, and this would not do any onboard tests.
It seems to me that Game Courier acts here as if the user has entered a move, and then crashes on what it thinks the user entered. (Which would not be surprising if it pulled some garbage string out of nothing.)
I have not changed anything in the betza.txt include file since Aurelean reported the timeout of the mate test, and I cannot imagine that I introduced an error at that time that would not have been discovered in the mean time.
This preset is probably automated with GAME code generted by the Play-Test Applet. (I.e. the code in the betza.txt include.) This code indeed uses the 'onboard' test in several places, mostly for parsing the user's input move.
But the error message appears for me on invoking the preset from the link in the article, which should bring me to the start position. Only the Pre-Game GAME code should be executed at that point, and this would not do any onboard tests.
It seems to me that Game Courier acts here as if the user has entered a move, and then crashes on what it thinks the user entered. (Which would not be surprising if it pulled some garbage string out of nothing.)
I have not changed anything in the betza.txt include file since Aurelean reported the timeout of the mate test, and I cannot imagine that I introduced an error at that time that would not have been discovered in the mean time.