Passing or Piping commands into a dos window

[bizygha]

Is it possible in windows to interact with a previously open DOS session, and pass commands into that session?

I have a dos program running in that session, and don't have the source code to that program, so I can't modify it. It runs in a dos session, and sits there waiting for commands, that can be typed in by hand. I want to send commands to that program and read its output in an automated way.


Is something like this possible?

 

[EagleKeeper]

To pipe to an output file the command Window uses >> output.txt

Try creating an input file of commands.
In the command windows when you type in the application name follow it with << input.txt

That may work

 

[nickbits]

For a bit more control, it's easy to do via programming in .NET/C#. Create a Process object and tap into StandardOutput and StandardInput.
Might be possible to do something with powershell but I haven't played around with that.

 

[QuietDad]

What OS? What language? Here's a good starting point in your research: http://tclap.sourceforge.net/manual.html

 

[EagleKeeper]

The problem is, the OP already has an application that has to be used.

don't have the source code to that program

 

[takeru]

are you passing arguments to it at execution, or are you passing commands to it while the program is running already? i would assume running already since you said it sits there waiting for commands? you can try what eagle said to capture the output, and use autoit to grab focus of the dos window and feed it commands, then read/parse the output.txt for the response.

 

[bizygha]

To pipe to an output file the command Window uses >> output.txt

Try creating an input file of commands.
In the command windows when you type in the application name follow it with << input.txt

That may work

Thanks, I tried this, and i get a '<< was unexpected at this time' message. I tried with a single '<' but that seemed to fail. I can get the >> output.txt to work though. I'm not sure I can use a static file like anyway that because I want to interact with the program at its command prompt. Goes something like this--

C:\> Analyzer.exe

Analyzer> (I type a command here)

(I get message with output status)

(and then back to program's prompt.)

(at this point I read an output file that is produced, and based on the results come up with a new command.)

Analyzer> ( I type that new command here. and the cycle repeats)

 

[EagleKeeper]

There is no way to send data to the program because it is designed for direct user input via stdin.

You can trick it to think stdin is a data file, but that is it.

The OS sets up input when app starts. After that, the app is on autopilot based on the input data.

 

[EagleKeeper]

Without source, you are SOL.
Write a replacement application is about the only solution.

Some may try to break open the applican, but that is very iffy.

Best to create specs based on what the app is doing and then write an app that has the enhancements you need.

 

[Fallen Kell]

Thanks, I tried this, and i get a '<< was unexpected at this time' message. I tried with a single '<' but that seemed to fail. I can get the >> output.txt to work though. I'm not sure I can use a static file like anyway that because I want to interact with the program at its command prompt. Goes something like this--

C:\> Analyzer.exe

Analyzer> (I type a command here)

(I get message with output status)

(and then back to program's prompt.)

(at this point I read an output file that is produced, and based on the results come up with a new command.)

Analyzer> ( I type that new command here. and the cycle repeats)

You need something like "expect" for windows.... Do not know if it exists or not. You might be able to simply install Cygwin and run your application that way and gain expect.

 

[Ken g6]

It sounds like you want an "automation" tool. There are various ways of doing this. It generally helps if you can get data sent over TCP, such as by opening a TELNET terminal connection to your own system.

If that's not possible in this case - and I suspect it's not - there are direct Windows automation tools. This Python recipe looks interesting if your application has a command prompt - meaning it doesn't use CURSES to draw nice graphics. Even in that case you might be able to do something.

 

[takeru]

There is no way to send data to the program because it is designed for direct user input via stdin.

You can trick it to think stdin is a data file, but that is it.

The OS sets up input when app starts. After that, the app is on autopilot based on the input data.

you can, with autoit using send key commands. he can try what i wrote above. autoit is built to handle automating manual processes. typing in cmd is easy with it, and parse the output txt file with autoit, and depending on what result you expect, refocus to the cmd again and feed it more commands.

 

[bizygha]

expect.

According to the Cygwin website, I would be suprised if this would work. Do you still think this may work?

Best to create specs based on what the app is doing and then write an app that has the enhancements you need.

This Python recipe looks interesting if your application has a command prompt - meaning it doesn't use CURSES to draw nice graphics. Even in that case you might be able to do something.

you can, with autoit using send key commands. he can try what i wrote above. autoit is built to handle automating manual processes. typing in cmd is easy with it, and parse the output txt file with autoit, and depending on what result you expect, refocus to the cmd again and feed it more commands.

Thanks for the suggestions. Initially I didn't realize there wouldn't be 'standard' method embedded into the OS, (Windows), to do it, (unlike linux), although I had an inkling. I contacted the app vendor since remaking this app would probably take me years, anyway they decline to provide this functionality. I am not familiar with Python or AutoIt, I will start looking into them.

 

[EagleKeeper]

you can, with autoit using send key commands. he can try what i wrote above. autoit is built to handle automating manual processes. typing in cmd is easy with it, and parse the output txt file with autoit, and depending on what result you expect, refocus to the cmd again and feed it more commands.

AutoIt may not work as you think.
My concern is the OP is not using a Windows program. It is a "DOS" type program that is being run in a Command Window.

From the AutoIt site

AutoIt v3 is a freeware BASIC-like scripting language designed for automating the Windows GUI and general scripting. It uses a combination of simulated keystrokes, mouse movement and window/control manipulation in order to automate tasks in a way not possible or reliable with other languages (e.g. VBScript and SendKeys).

 

[takeru]

AutoIt may not work as you think.
My concern is the OP is not using a Windows program. It is a "DOS" type program that is being run in a Command Window.

From the AutoIt site

yes i know. another poster from here awhile back wanted to target a cmd window also:
http://forums.anandtech.com/showthread.php?t=2318462

it is possible to target the window by title and start messing with it.

example of changing cygwin window titles:
http://heath.hrsoftworks.net/archives/000139.html

 

[BoberFett]

SendKeys

http://msdn.microsoft.com/en-us/library/system.windows.forms.sendkeys(v=vs.110).aspx

I used to use it all the time for simulating user input. I don't know the syntax nowadays, but this should get you started. Just set focus to the window you want and SendKeys to your hearts content.

 

[BoberFett]

AutoIt may not work as you think.
My concern is the OP is not using a Windows program. It is a "DOS" type program that is being run in a Command Window.

From the AutoIt site

It doesn't matter whether it's a command window or a DOS program running in a window, that window still has a handle and given focus and interacted with like any other window.

 

[serpretetsky]

slightly off-topic. I've seen people here more than once refer to DOS programs or going into DOS to run commands. Seeing as how this is 2013, I'm assuming everyone is referring to the command prompt, and command line programs, correct?

 

[takeru]

SendKeys

http://msdn.microsoft.com/en-us/library/system.windows.forms.sendkeys(v=vs.110).aspx

I used to use it all the time for simulating user input. I don't know the syntax nowadays, but this should get you started. Just set focus to the window you want and SendKeys to your hearts content.

yup, exactly, autoit has a similar function as well.
http://www.autoitscript.com/autoit3/docs/functions/Send.htm

 

[EagleKeeper]

It doesn't matter whether it's a command window or a DOS program running in a window, that window still has a handle and given focus and interacted with like any other window.

With a regular window, you can send a WM_CHAR event message that gets picked up and if designed for, handled.

You are stating that the CMD window will take a WM_CHAR event message and pass it to stdin?




As to the OP problem; he still seems to be having to have the human in the loop making decisions about what information he wants to feed the program based on outs.

Unless he can define a table of output->input options that is consistent; automating should not help him.

 

[bizygha]

Sorry, I may have given the wrong impression. Outside of the initial setup, there is no human interaction necessary. The 'analyzer' is wrapped in an optimizing function. Every action taken by the 'optimizer' depends on the results of the analyzer--(what is meant by it not being static).