Getting DOS session to automatically close

Adjusted points to 100

Hi Jackie,

That's an interesting solution. However, I keep getting this error:

    Specified COMMAND search directory bad

The path (to a batch file in this case) is ok, so this is somewhat perplexing. Meanwhile, how will things fare in the NT environment, seeing as it doesn't have a command.com?

RJV

Can you post up your commands and batch file contents?
Do you give the full path in commands?
What is your DOS path? ( You can get it by typing "set" in DOS session )

This works but doesn't close:

  ShellExecute(NULL,NULL,prog,flnm+" "+cmds,wrkPath,show);

Where:

      prog = "c:\project\temp\batch.bat"
      flnm = blank
      cmds = blank
      workPath = blank
      show = (can be normal, minimzed or hide)

This gets the error without even opening the batch file itself (seen after removing the /c):

     prog = "command.com /c c:\project\temp\batch.bat"

Note that command.com is in the path (see below) and I've tried the above giving the specific path and even at the DOS prompt itself, with the same error. Here's the applicable parts of the evironment:

    winbootdir=C:\WINDOWS
    COMSPEC=C:\COMMAND.COM
    PATH=C:\WINDOWS;C:\WINDOWS\COMMAND

Though it never opens the batch file itself, here are its contents, which work without command.com:

   Arj a c:\work\add\test.arj c:\work\test.txt
   Arj a c:\work\add\test.arj c:\work\test1.txt

Hopes this helps! Also thanks for the extra help. I plan to increase the points as it's nice to be able to make up for extra help given for those that do make the effort.

Regards,
RJV

Try to run "command.com /kc:\project\temp\batch.bat"
If it succeed, then turn it to "command.com /cc:\project\temp\batch.bat"

Jackie, have you tried the command.com solution under VC++? I didn't get back earlier as today I decided to go after this and, no matter what I did, no luck. Everything works fine, but without closing the DOS session, as long as run on its own. It appears as if shelling puts you under command.com and then it doesn't like the extra command.com.

The main problem is to get the DOS session to close automatically under Win95 which stubbornly won't collaborate so far.

Regards,
Roger

You should run the "command.com /cc:\project\temp\batch.bat" under Win95 [Start] --> [Run].
If you run it under DOS session, it will need exit twice.
Because DOS session is another command.com, you know.

I use the command.com solution under VC++ exactly.
But I am using the CreateProcess() instead of ShellExecute().
I don't know what is the difference about running command.com

Now we're getting a bit closer in coding. I was actually using CreateProcess() plus ShellExecute(). I use the former to wait for an app to finish. Exactly how do you set up CreateProcess? I'll do the same here so we may nail this down.

As to two DOS sessions, I only tried it with a command line to try and find the problem. However, I believe when you launch a DOS program you automatically launch a DOS session, so maybe by using command.com you may indeed get two of them. I could be wrong on that one, though.

RJV

Jackie,

Just to note that I got CreateProcess() to work, finally. The problem is that command.com did not recognize the path given (why I don't know, as it seems to take itself back to PC or MS/DOS version 1). I made our application change to the correct path/folder and then run the batch file and all was ok.

Now I just need to find out if the operating system is Win95 or NT to switch command.com and cmd.exe accordingly. Any tips would be greatly appreciated! As indicated, I've increased the points for your extra effort, which was vital for the solution of my problem.

RJV