by H.G.Muller » 03 Sep 2009, 18:59
Yes, this was a bug. Options with an invalid syntax were not rejected by 4.4.0beta2, but accepted with undefined results. I already sent the patch for this to Arun after we discussed this yesterday (producing the error response that we now require in the protocol specs), but he did not upload it to the repository yet.
So the 4.4.0 we hope to release this weekend will ignore the option. (Not that this will help you much, of course...)
I equiped Fairy-Max with some option features (for setting a resign threshold, clearing the hash table, or setting an alternate game-definition file, plus some dummies), so that it now can act as a model native WB engine that implemets the protocol extensions. (It responded to the memory command aready for a long time.)