I tried to run a program using wine and it seemed to start up and then just stopped. Is there a file that wine writes to with all error messages?

it usually spews them onto the console.
what program ? and what version of wine ? and what error messages did you see ?

wine 20040213 is the version. I am trying to run taxact, and the problem is that it isn't spewing any error messages that is why I was wondering if there is a log file created by wine. It starts the program, a splash screen comes up and then it goes away, but the program seems to continue to run in the terminal.

Okay I figured out how to get debug messages to print to screen with debugmsg, but I can't get it to send it to a file. I tried:

wine --debugmsg trace+all taxact.exe > wine.txt

It prints to the screen, but not to the file.

Here is what is printed to the screen with trace+relay:

0009:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=40f31700
0009:Call kernel32.WaitForMultipleObjectsEx(00000001,4069eed8,00000000,00000000,00000000) ret=40f16e65
0009:Ret kernel32.WaitForMultipleObjectsEx() retval=00000102 ret=40f16e65
0009:Ret x11drv.MsgWaitForMultipleObjectsEx() retval=00000102 ret=409b4ae5
0009:Call kernel32._ConfirmSysLevel(409f1ba0) ret=4098e505
0009:Ret kernel32._ConfirmSysLevel() retval=00000000 ret=4098e505
0009:Call kernel32.GlobalLock16(000010ef) ret=40983cf2
0009:Ret kernel32.GlobalLock16() retval=40349238 ret=40983cf2
0009:Call kernel32.ReleaseThunkLock(4069f0f8) ret=409b4bc2
0009:Ret kernel32.ReleaseThunkLock() retval=00000000 ret=409b4bc2
0009:Call kernel32.ReleaseThunkLock(4069f160) ret=409b4e24
0009:Ret kernel32.ReleaseThunkLock() retval=00000000 ret=409b4e24
0009:Call x11drv.MsgWaitForMultipleObjectsEx(00000001,4034923c,ffffffff,00000000,00000000) ret=409b4e66
0009:Call ntdll.RtlEnterCriticalSection(40f58780) ret=40f31770
0009:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=40f31770
0009:Call ntdll.RtlLeaveCriticalSection(40f58780) ret=40f31700
0009:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=40f31700
0009:Call ntdll.RtlEnterCriticalSection(40f58780) ret=40f31770
0009:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=40f31770
0009:Call ntdll.RtlLeaveCriticalSection(40f58780) ret=40f31700
0009:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=40f31700
0009:Call kernel32.WaitForMultipleObjectsEx(00000002,4069ef28,00000000,ffffffff,00000000) ret=40f16e65
0009:Call kernel32.GetLastError() ret=004f342b
0009:Ret kernel32.GetLastError() retval=00000057 ret=004f342b
0009:Call kernel32.TlsGetValue(00000004) ret=004f3439
0009:Ret kernel32.TlsGetValue() retval=41a60f80 ret=004f3439
0009:Call kernel32.SetLastError(00000057) ret=004f3485
0009:Ret kernel32.SetLastError() retval=00000057 ret=004f3485
0009:Call kernel32.GetLastError() ret=004f342b
0009:Ret kernel32.GetLastError() retval=00000057 ret=004f342b
0009:Call kernel32.TlsGetValue(00000004) ret=004f3439
0009:Ret kernel32.TlsGetValue() retval=41a60f80 ret=004f3439
0009:Call kernel32.SetLastError(00000057) ret=004f3485
0009:Ret kernel32.SetLastError() retval=00000057 ret=004f3485
0009:Call kernel32.UnhandledExceptionFilter(4069e6ac) ret=004f6d5b

HERE IS WHAT PRINTS TO SCREEN WITH TRACE+WIN

trace:win:WINPROC_FreeProc freeing 0x40a347b4 (1)
trace:win:WIN_DestroyWindow 0x10028
trace:win:WIN_SetWindowLong 0x10028 -4 4096a8e0 2
trace:win:WINPROC_AllocWinProc (0x4096a8e0,2): returning 0x40a347b4
trace:win:WINPROC_SetProc (0x40a347d8,0x4096a8e0,2): res=0x40a347b4
trace:win:WINPROC_FreeProc freeing 0x40a347b4 (1)
trace:win:WINPROC_FreeProc freeing 0x40a347d8 (1)
trace:win:WIN_DestroyWindow 0x10029
trace:win:WIN_SetWindowLong 0x10029 -4 4096a8e0 2
trace:win:WINPROC_AllocWinProc (0x4096a8e0,2): returning 0x40a347d8
trace:win:WINPROC_SetProc (0x40a347fc,0x4096a8e0,2): res=0x40a347d8
trace:win:WINPROC_FreeProc freeing 0x40a347d8 (1)
trace:win:WINPROC_FreeProc freeing 0x40a347fc (1)
trace:win:WIN_SetWindowLong 0x10023 0 0 3
trace:win:WIN_SetWindowLong 0x10023 12 0 3
trace:win:WINPROC_FreeProc freeing 0x40a34700 (1)
trace:win:WIN_SetWindowLong 0x10023 -4 409688a0 2
trace:win:WINPROC_AllocWinProc (0x409688a0,2): returning 0x40a34700
trace:win:WINPROC_SetProc (0x40a346dc,0x409688a0,2): res=0x40a34700
trace:win:WIN_SetWindowLong 0x10023 -12 0 3
trace:win:WINPROC_FreeProc freeing 0x40a34700 (1)
trace:win:WINPROC_FreeProc freeing 0x40a346dc (1)
trace:win:SetForegroundWindow (nil)

NOT SURE WHERE TO GO FROM HERE. IF ANYBODY HAS ANY IDEAS PLEASE LET ME KNOW.

THANKS

Wine is by no means finished... it works great for some programs, and not at all for other.
however compatability is constantly getting better with every release of wine.

your version is almost a year old, why not try the latest stabe, and latest cvs versions ?

That was a good suggestion. I downloaded the latest version of wine. I am getting an error that it can't find c:\\windows and others. I looked in the config file and this is what I found. Does this look right? Should my Path have a c involved or should those "Windows" be equal to "fake_windows\\windows".

Any thoughts?


[Drive C]
"Path" = "%HOME%/.wine/fake_windows"
"Type" = "hd"
"Label" = "fake_windows"
"Filesystem" = "win95"


[wine]
"Windows" = "C:\\Windows"
"System" = "C:\\Windows\\System"
"Temp" = "C:\\Windows\\Temp"
"Path" = "C:\\Windows;C:\\Windows\\System;X:\\;Y:\\"
"Profile" = "c:\\windows\\Profiles\\Administrator"
"GraphicsDriver" = "x11drv"
;"ShowDirSymlinks" = "1"
;"ShowDotFiles" = "1"
"ShellLinker" = "wineshelllink"

Delete your ~/.wine directory and try again with the new version

Okay, thanks for the help, wine is back to running order, but I am also back to where my program starts and tehn ends without any fanfare (ie no error messages) When I run it in debug mode it just sits there. Is there any way to know what wine is doing when it breaks, or is the program not going to run?

thanks