No I was wrong, the WM_KILLFOCUS message was only passed due to me clicking another window, hiding the messagebox. It occurs after the error so is not the problem here.
The first SendMessage called is WM_SETICON which returns a 0, but even recoding to make it return a 1 didn't help, the line is quite a ways from the messagebox call anyways.
The next SendMessage called is WM_NOTIFYFORMAT which returns a 1
The SendMessage before the error is WM_IME_CONTROL (283) with wparam=IMC_CLOSESTATUSWINDOW(21)
WARN--Unless you know what you're doing(unlike me), I suggest you not try the following as it may lockup your desktop!!! <- extra exclamations for emphasis !!!
[In Progess--editing]
Noting the function locations in the code of the functions called during this error:
case WM_IME_CONTROL:
ret = callback( hwnd, msg, wParam, lParam, result, arg );
if(wParam==0x21)
{
*result = 0; /* FIXME: Hack for IMC_CLOSESTATUSWINDOW of WM_IME_CONTROL */
}
break;
no messagebox error, but program closes suddenly. In winedbg mode I can open menus, but the program gets to a point where it won't respond and locks up my ubuntu windows temporarily.
The program will now create SSF.ini, but fails to create Settings.ini.