Dos program won't exit using CMD.EXE and System.Diagnostics.Process Class

Question

4.00/5 (1 vote)

See more:

The following code is used to start a Dos program.

C#

System.Diagnostics.Process process1;
            process1 = new System.Diagnostics.Process();
            process1.StartInfo.FileName = "cmd";
            process1.StartInfo.Arguments = "/c voc2wav.exe "+Convert.ToString(shortPathVocLoc) +
                " " + Convert.ToString(shortPathWavLoc);
            process1.StartInfo.UseShellExecute = false;
            process1.StartInfo.CreateNoWindow = false;
            process1.StartInfo.WorkingDirectory = Convert.ToString(shortPathVoc2Wav);
            process1.Start();
            process1.WaitForExit();
            MessageBox.Show("exited");

When I run it, the process starts and performs its task but it doesn't terminate. When I use the Command Prompt window and run the exact same thing manually, the program runs and terminates.

Anyone have any idea what is causing this. Windows XP Sp3.

Thanks.

Posted 28-Feb-10 11:09am

Greg1947

Updated 28-Feb-10 15:34pm

DaveyM69

v2

Add a Solution

5 solutions

Solution 5

Thanks for the advice. It seems the that DOS program itself is quirky. It works when the files are in the working directory but has problems when they are in other directories making it look like it is a cmd.exe problem.

Posted 1-Mar-10 5:15am

Greg1947

Solution 2

The same thing happens when I call voc2wav.exe directly rather than thru CMD.ExE. Another curious thing is that when a condition exists where a file exists that voc2wav is trying to write to and it asks whether to continue y/n. If you answer n, it terminates and the process terminates. When you answer y, it continues, does its work correctly but the process (Cmd.exe) never terminates. None of this funny result occurs when you exectue voc2wav using the command prompt window.

Posted 28-Feb-10 14:21pm

Greg1947

Solution 3

I've made progress on this. It appears that the length of the command line agruments (all the path/file specs) exceeded some limit and they were being truncated. Is there a way to expand that limit?

Posted 1-Mar-10 3:38am

Greg1947

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jimmanuel · Accepted Answer · 2010-02-28T11:38:00

Solution 1

My guess would be that voc2wav is exiting, but cmd is not and that's what process1 is waiting for. Instead of calling cmd.exe and passing it /c voc2wav ... for the arguments what happens if you call voc2wav directly?

Posted 28-Feb-10 11:38am

Jimmanuel

Kristian Sixhøj · Accepted Answer · 2010-03-01T04:00:00

Hi,

I recall another case where someone had to pass arguments containing spaces to the command prompt, which caused problems. The solution was to wrap the arguments in quotation marks:

MIDL

process1.StartInfo.Arguments = "\"/c voc2wav.exe "+Convert.ToString(shortPathVocLoc) + " " + Convert.ToString(shortPathWavLoc) + "\"";

I'm not sure if it helps in your case, but give it a try.

:)

Dos program won't exit using CMD.EXE and System.Diagnostics.Process Class

5 solutions

Solution 1

Solution 4

Solution 5

Solution 2

Solution 3

Add your solution here

Preview 0

Existing Members

...or Join us