Hello Ives,
I use multilanguage Windows98SE operating system. With Milady 1.72 version, if I write "Winboard" instead of "Arena" at the Milady.cfg file, when opening the Winboard interface, Milady crash and appear an error message. But if I write "Arena" instead of "Winboard", at the Milady.cfg file, Milady plays OK at Winboard ????.
If I use the Arena interface version 1.1, Milady 1.72 crash, but if I use the newer Arena version 1.99b2, Milady 1.72 play OK ???.
Here are the error messages and the winboard.debug file when Milady crash:
Error Message N?1
==============
"Application has generated an exception that could not be handled.
Process id=0xfff868c7 [-497465], Thread id=0xfffa7ad3 [-361773].
Click OK to terminate the application
Click CANCEL to debug the application"
Error Message N?2
==============
"Registered JIT debugger is not available. An attempt to launch a JIT debbuger with the following command resulted in an error code of 0x2 [2]. Please check computer settings.
cordbg.exe !a 0xfffa9b8b
Click on Retry to have the process wait while attaching a debugger manually.
Click on Cancel to abort the JIT debug request"
Winboard.debug
===========
"recognized 'normal' (-1) as variant normal
WinBoard 4.2.7 + Milady172
Reset(1, 0) from gameMode 0
recognized 'normal' (-1) as variant normal
GameEnds(0, (null), 2)
StartChildProcess (dir="c:\Wbrd\L-O\Milady") Milady172
720 >first : xboard
protover 2
770 <first : feature setboard=1 analyse=0 done=1
770 >first : accepted setboard
770 >first : rejected analyse
770 >first : accepted done
770 >first : new
random
770 >first : level 40 5 0
770 >first : post
770 >first : hard
770 >first : easy
GameEnds(0, (null), 2)
72180 >first : force
72180 >first : quit"
--------------------------------------
I hope above information help for your investigation.
Best regads,
Pablo
PS: For me is easier to comment Milady problems using the email instead of the Forum.
My email adress is:
indech@ctcinternet.cl