by H.G.Muller » 26 Dec 2012, 23:18
/xreuse is normally an option that is intendes for a sepcific engine. (Which is why there is /xreuse and /xreuse2.) So WB resets it before each new pairing, to prevent that one engine that does not need it would 'inherit' it from an engine that used it the previous pairing.
So the proper use is to specify the option with the installed engine, so that each time the engine is loaded, it is set to the desired value. The best way to do this is after you have installed the engine in the usual way, use the Edit Engine List menu to append " /xreuse" to the engine line. After that the engine will always run in this mode when you load it. This way you can limit this setting only to engines that need it.
I did not include a checkbox for /xreuse in the Load Engine dialog, because /xreuse should be considered a work-around option. In WB protocol engines that need /xreuse should specify it themselves by sending "feature reuse=0" to the GUI at startup. I guess the use of /xreuse as a WB command-line option is a legacy from the time of WB protocol v1, from before the 'feature' commands were invented.