I can't even think how to search winehq for this one. I have been running Wine successfully one one machine for ages. without problems. I am setting up a fresh machine. On that machine when I run the same application it leaves a whole load of copies of wine processes running when the application shuts down. I can't see any obvious differences in the config. Does anyone have any suggestion as to where to look for the cause; I don't like having to use kill each time I run the application. Bill
Bill Medland <medbi01@accpac.com> wrote in article <01c11ba6$0a12a640$6f0c10ac@medbi01>...> I can't even think how to search winehq for this one. > > I have been running Wine successfully one one machine for ages. without > problems. > > I am setting up a fresh machine. On that machine when I run the same > application it leaves a whole load of copies of wine processes runningwhen> the application shuts down. > > I can't see any obvious differences in the config. > > Does anyone have any suggestion as to where to look for the cause; Idon't> like having to use kill each time I run the application. > > Bill >OK. It is the winedbg process sitting around that is keeping everything alive. Turn off the automatic invocation of the debugger. (See WIne Developer's Guide 2.5 - Configuration). Bill