DOSBox is intended for games. It is missing some features that many applications require that no games need.

The dosbox.conf has a line labelled [autoexec]. Add your DOS batch jobs there. In your last DOS batch file, add the line: exit; this should allow dosbox to exit. Create a batch file on the host which runs dosbox.exe; this will run the jobs in dosbox.conf.

The host command line would include 32/64-bit commands which output data to a host directory; this directory should be shared with dosbox and the DOS batch jobs. Perhaps add a semi-colon after that part of the script, then have it start the dosbox batch file within that same command line. Given dosbox is operating upon a host directory, has run its jobs, and then has exited; then that output should be available to the host. Add another semi-colon and then add the next 32/64-bit command. A for loop can have this routine work over a set of files or lines of a file.

I have not tested this yet, but this is the way I would try first.

There is a kludgy, unofficial patch that allows DOSBox to interact with the Windows clipboard. That is likely as close as you are going to get.
Re: Printing & clipboard-exchange - kludgy workaround for DOSBox under Windows

Jorpho wrote:

There is a kludgy, unofficial patch that allows DOSBox to interact with the Windows clipboard. That is likely as close as you are going to get.
Re: Printing & clipboard-exchange - kludgy workaround for DOSBox under Windows

Using that kludgy workaround, the way to pipe output to the Windows clipboard is to do something like:

1echo "This is for the Windows clipboard" > p:\clipout.tmp

It's ugly and inefficient, but it at least it should work.

Here's another almost equally complicated method:
1) create an empty directory;
2) register a change notification from within Windows for that directory;
3) mount a drive pointing to that empty directory;
4) redirect the output to a file in that directory.

The change notification will trigger when the file appears or is changed.
You can read the contents and then delete the file again.
However, it's really not the best idea.