🚀 go-pugleaf

Denville Longhurst wrote:

>The problem is that the diagnostic message which my app displays (and logs)
>prior to closing is lost as soon as it closes.  What I am trying to
>replicate is a scheme where I can copy the essential message(s) back to the
>DOS console so that an observer can still reas them in the DOS box even
>after my app has closed and the contingency app has run up.

You could write messages to a text file, and have the batch then type
the text file. (delete it on startup)

>I do not agree that GUI processes do not use STDOUT.  If I place a

The Command Interpreter (CI)  doesn't _normally_ set up stdout for gui
apps.

> However, if I call the app with something like MYAPP >MYFILE the stdout is 

Yes, because the CI is setting up a pipe prior to CreateProcess().

>  I am tempted to write a MORE - like utility to achieve what I want but this seem overkill if there
>is a simpler way.

That should be a very short & easy program.

>So, the basic question is: How, from within a GUI applicatiuon running in a
>DOS box, can I write text to that DOS box.

If you reliably know the name of the Command Console, you could get
it's hWnd, then maybe use WM_PASTE
Hmm... There's a TITLE function that would set the name reliably....

Then again, I don't think there's anything stopping you from creating
a "console app" (runs in the "DOS box") that then creates threads that
run the gui portion.  
You'd replace WinMain with main(), but the code inside WinMain should
be pretty much the same. CreateWindow, message pump, etc.