Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cs.yale.edu!spolsky-joel
From: spolsky-joel@cs.yale.edu (Joel Spolsky)
Newsgroups: comp.windows.ms
Subject: Re: DOS app <-> Windows app communication
Message-ID: <27266@cs.yale.edu>
Date: 14 Nov 90 05:56:38 GMT
References: <1990Nov13.210047.984@vax5.cit.cornell.edu>
Sender: news@cs.yale.edu
Distribution: comp
Organization: Yale University Computer Science Dept., New Haven, CT 06520-2158
Lines: 29
Nntp-Posting-Host: zoo-gw.cs.yale.edu
Originator: spolsky@suned.CS.Yale.Edu

In article <1990Nov13.210047.984@vax5.cit.cornell.edu> u2zj@vax5.cit.cornell.edu (Stanton Loh) writes:
>Microsoft Windows 3.0
>---------------------
>
>What I need to be able to do is run a DOS program in a DOS
>window that communicates with my Windows program.  Data needs to
>flow both ways.  


Hi, 

There is a Microsoft document calls "Old Application DDE Interface." I
know that it came with the 2.0 SDK. If this document is not in the 3.0
SDK, you should be able to call microsoft and ask for it. Quoting from
the introduction:

	"The WinOldAp Dynamic Data Exchange (DDE) allows a Microsoft
	Windows application ... to manipulate an old DOS program in 
	the same manner as a user would under Windows."

It is designed to make it easy to write windows shells with menus and
stuff for old DOS applications.

There are also functions that old applications (DOS applications) use
the clipboard; they are accessed through interrupt 0x2F. This is also
well documented in the 2.0 SDK.

Joel Spolsky
spolsky@cs.yale.edu                                     Silence = Death