search for: tooltips_windowproc

...un a single board computer from Zworld called the Rabbit. The specific app name is dcrab619.exe. The gui comes up with no problem but when it tries to talk to the serial port I get these messages from wine: err:string:CompareStringA (s1=(null),s2=""...): Invalide NULL string err:tooltips:TOOLTIPS_WindowProc unknown msg c017 wp=00000000 lp=40fc0b3c fixme:comm:SetupComm insize 400 outsize 4096 unimplemented stub Every time I try to connect to the Rabbit the "fixme" line above repeats. Does anyone have a clew or better yet a patch for this problem Thanks for anyones help, Andrew

...:heap:HEAP_CreateSystemHeap system heap base address 0x80000000 not available fixme:font:load_VDMX No suitable ratio found fixme:mmtime:timeBeginPeriod Stub; we set our timer resolution at minimum fixme:font:load_VDMX No suitable ratio found fixme:font:load_VDMX No suitable ratio found err:tooltips:TOOLTIPS_WindowProc unknown msg 0500 wp=00000000 lp=00000000 err:x11drv:X11DRV_CreateWindow invalid window width -16 err:x11drv:X11DRV_CreateWindow invalid window height -16 The first time I start Wine after boot, I get warnings on the console: Warning: pid 650 used static ldt allocation (with wine's pid in th...

...00 lp=7fc6ac44 err:rebar:REBAR_WindowProc unknown msg 204e wp=00000000 lp=7fc696b0 err:rebar:REBAR_WindowProc unknown msg 204e wp=00000000 lp=7fc696b4 err:rebar:REBAR_WindowProc unknown msg 2210 wp=00000201 lp=004b00c9 err:rebar:REBAR_WindowProc unknown msg 204e wp=00000000 lp=7fc6e10c err:tooltips:TOOLTIPS_WindowProc unknown msg 204e wp=00010038 lp=7fc6e118 err:toolbar:ToolbarWindowProc unknown msg 204e wp=0000071b lp=7fc6d854 err:toolbar:ToolbarWindowProc unknown msg 204e wp=0000071b lp=7fc6d884 err:tooltips:TOOLTIPS_WindowProc unknown msg 204e wp=00010038 lp=7fc6e120 err:rebar:REBAR_WindowProc unknown msg 204...

Im trying to run this program called Thinkboxx and wen it tryes to comunicate over the comm port it hangs. Here are som output to read. earlier on i get: Call kernel32.VirtualAlloc(43050000,00001000,00001000,00000004) ret=0058557c Ret kernel32.VirtualAlloc() retval=43050000 ret=0058557c thats from vhere the com port gets an virtual memory space, i think. and in the end i have: Call