You should try to get a stack backtrace of the programs when they are hung: - start a program and wait until it hangs - on a different console type "winedbg" - if even winedbg hangs then you have a problem. If not then type "info process" - find the process id of the process that is hanging and attach the debugger to it: "attach 0x<num>" (the ids in "info process" are in hex so that's why the 0x is needed. This is a different thing than the Linux pids) - type "info thread" to check how many threads have the program - type "bt 0x<tid>" for each thread of the hanged program (where tid is the thread id you have found with info thread) Such a backtrace could give some more details what's happening. Mikołaj Zalewski _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
