Hi all, I am trying to run my last Windoze app (proprietary banking software) under Wine, and it is *almost* there... however some functions fail, the program will pop up error boxes saying 'Type mismatch' and/or 'Invalid property value'. Sometimes this is no problem because the program just continues as normal. However, in other situations I'm stuck. The errors that are given are all like this: err:int:INT_Int3dHandler int3d: unknown/not implemented parameters: int3d: AX 2efe, BX 6ee0, CX 1f7f, DX 0000, SI 01f9, DI 0c44, DS 01ef, ES 1f7f err:int:INT_Int3dHandler int3d: unknown/not implemented parameters: int3d: AX 014a, BX 6ee0, CX 1f7f, DX 0000, SI 01f9, DI 0c44, DS 01ef, ES 1f7f err:int:INT_Int3dHandler int3d: unknown/not implemented parameters: int3d: AX 0690, BX 689a, CX 205f, DX 0000, SI 1908, DI 0c44, DS 01ef, ES 01ef err:int:INT_Int3dHandler int3d: unknown/not implemented parameters: int3d: AX 06bd, BX 68ac, CX 205f, DX 0000, SI 1908, DI 0c44, DS 01ef, ES 01ef Other register values occur, but these are the most common. I'm running wine-20010824 by the way, with no Windows on the machine. I am also seeing a lot of FIXME:pthread_rwlock_unlock FIXME:pthread_rwlock_rdlock on startup, but that doesn't seem to cause a problem. The program starts fine. Anyone have any ideas? Thanks, Mark
On Tue, 2 Oct 2001 19:55:51 +0200, Mark Koek <mark@koek.net> wrote:>Hi all, > >I am trying to run my last Windoze app (proprietary banking software) under >Wine, and it is *almost* there... however some functions fail, the program >will pop up error boxes saying 'Type mismatch' and/or 'Invalid property >value'. Sometimes this is no problem because the program just continues as >normal. However, in other situations I'm stuck.<snip errors> These errors are probably not the reason for your problems. Often there is no error message in the console because error messages are output by Wine when the programmers have thought in advance of possible problems; however, programmers do not always think in advance of possible problems. It's only if the error messages on the console appear at the same time that the application displays an error message that you can guess there is a relation. If you want to try to fix Wine, the way to go is as follow : - run with -debugmsg +relay yourprog.exe &>yourtracefile.txt - make your problem appear (do the operation that triggers a problem) - end the app the difficult part is then to cut a part of the trace that can be reasonably posted to Usenet (200 lines) while holding information sufficient for a contributor to find and fix the problem. It is not always possible of course. The trick is to search the trace file for the error message. Often it will appear many times; cut 200 lines before the first occurence of it and post the result. It is quite frequent that this does not give any meaningful info and this must be repeated until the problem is found or someone (usually the initial poster) gives up. There are alternatives to Wine : - take another bank that do not rely on Windows software - use a solution like vmware HTH Gerard