Re: [Mono-dev] Mono - CreateProcess error

2006-09-28 Thread Hubert FONGARNAND
Le mardi 26 septembre 2006 20:03 +0200, Robert Jordan a crit: Honey, Steve wrote: A search of google says this was a bug which was supposed to be corrected in 1.1.16. I was running 1.1.13 so I upgraded to 1.1.17 but still have the problem. I also tried adding Process.Dispose() to the

Re: [Mono-dev] Mono - CreateProcess error

2006-09-26 Thread Brian Crowell
Honey, Steve wrote: Help! Hey, Steve. I've been watching this one, too. For months. The latest bug is filed as: http://bugzilla.ximian.com/show_bug.cgi?id=79286 The only workaround I know of at this point (other than, say, rebooting every now and then) is to periodically empty the

[Mono-dev] Mono - CreateProcess error

2006-09-26 Thread Honey, Steve
Help! Ive been using Mono/C# (on Linux) to develop an algorithm to process real time radar data. So far, so good. Development has gone smooth and I love the Mono environment (first time using C# as well). However, Im running into a problem now that I want to run this in real time.

Re: [Mono-dev] Mono - CreateProcess error

2006-09-26 Thread Brian Crowell
Brian Crowell wrote: At least, I *think* that works. It's such a finicky problem, I can never be sure of a real fix. Check that. We just received reports in this morning from our application. This doesn't clear or disable WAPI at all. Looks like the next alternative would be to shut down

Re: [Mono-dev] Mono - CreateProcess error

2006-09-26 Thread Miguel de Icaza
Hello, A search of google says this was a bug which was supposed to be corrected in 1.1.16. I was running 1.1.13 so I upgraded to 1.1.17 but still have the problem. I also tried adding Process.Dispose() to the code but that hasn’t help either (don’t know if it should have, but I’m

Re: [Mono-dev] Mono - CreateProcess error

2006-09-26 Thread Robert Jordan
Honey, Steve wrote: A search of google says this was a bug which was supposed to be corrected in 1.1.16. I was running 1.1.13 so I upgraded to 1.1.17 but still have the problem. I also tried adding Process.Dispose() to the code but that hasn't help either (don't know if it should have, but