**************************************************************************
*******             Sample Eroiica DDE application                 *******
***************************************************** ********************

To compile this sample application you will need ANSI C compatible
compiler. Unless you use Microsoft's Visual C environment, you may need
to customize the supplied make/project files to suit you compiler
requirements.

The files required to compile the sample application are as follows:
 
CALLBACK.C
TESTCASE.C
DDE_TEST.C
UTDDE.C
UTDLG.C
UTFILE.C
DDE_TEST.DLG
TESTCASE.H
DDE_TEST.H
UTDDE.H
UTDLG.H
UTFILE.H
DDE_TEST.ICO
DDE_TEST.INI    ... should be completed, see note!
DDE_TEST.RC

For Microsoft Windows 3.1x compilation you will need
   DDE_W31.MAK and
   DDE_TEST.DEF.

For Microsoft Windows 95/NT compilation you will need
   DDE_W95.MAK.

Note: You must run EROICA.EXE before you run the DDE_TEST.EXE to establish
correct DDE connection between EROICA.EXE and the DDE sample application!

Note: If you will compile and run your DDE_TEST.EXE please complete the
image filenames as found in DDE_TEST.INI to allow find the files on your
disk. The image files reside in the IMAGE subdirectory of the directory
where Eroiica was installed.

**************************************************************************
To compile the DDE_TEST.EXE under Microsoft Windows 95 using Microsoft
Visual C/C++ ver. 4.2 developer studio:
--------------------------------------------------------------------------
1. Run MSVC developer studio. 
2. Choose Open Workspace from the File menu.
In the Open Project Workspace dialog box:
3. Set type of files to Project (*.MAK) in the Files of type list box.
4. From the subdirectory DDE_TEST (located where EROICA.EXE was originally
   installed), select DDE_W95.MAK to open the project DDE_W95. 
5. Choose Build DDE_TEST.EXE from the Build menu to generate the sample
   DDE application DDE_TEST.EXE.

**************************************************************************
To compile the DDE_TEST.EXE under Microsoft Windows 95 using Microsoft
Visual C/C++ ver. 4.2 command line compiler:
--------------------------------------------------------------------------
1. Set environment variables (PATH, INCLUDE, LIB, OBJ) as required by the
   command line compiler and linker. See following example of system sets
   produced by the SET command:
      ...
PATH=C:\WINDOWS;C:\WINDOWS\SYSTEM;C:\DOS;C:\MSDEV\BIN
INCLUDE=.;c:\msdev\INCLUDE
LIB=.;c:\msdev\LIB
OBJ=.;c:\msdev\LIB
     ...
2. Open a DOS window and at the DOS prompt, execute the following command
   to compile and link the sample DDE application and generate the
   DDE_TEST.EXE.:

      nmake dde_w95.mak

**************************************************************************
To compile the DDE_TEST.EXE under Microsoft Windows 3.1x using Microsoft
Visual C/C++ ver. 1.5x:
--------------------------------------------------------------------------

1. Run Microsoft Visual C++. 
2. Choose Open from the Project menu.
In the Open Project dialog box:
3. Set type of files to Project (*.MAK) in the List Files of Type list box
   and check the box Use as External Makefile.
4. From the subdirectory DDE_TEST (located where EROICA.EXE was originally
   installed), select DDE_W31.MAK to open the project DDE_W31. 
5. Choose Project from the Options menu.
In the External Project Options dialog box:
6. Make sure that Debug Build is set to 
	 NMAKE /f DDE_W31.MAK DEBUG="1"
   and Release Build to 
     NMAKE /f DDE_W31.MAK DEBUG="0". 
7. Choose Build DDE_TEST.EXE from the Build menu to generate the sample
   DDE application DDE_TEST.EXE.

**************************************************************************
To compile the DDE_TEST.EXE under Microsoft Windows 3.1x using Microsoft
Visual C/C++ ver. 1.5x command line compiler:
--------------------------------------------------------------------------
1. Set environment variables (PATH, INCLUDE, LIB, OBJ) as required by the
   command line compiler and linker. See following example of system sets
   produced by the SET command:
      ...
PATH=C:\WINDOWS;C:\WINDOWS\SYSTEM;C:\DOS;C:\MSDEV\BIN
INCLUDE=.;c:\msdev\INCLUDE
LIB=.;c:\msdev\LIB
OBJ=.;c:\msdev\LIB
     ...
2. In the DDE_TEST directory, create directory DEBUG and/or directory
   RELEASE depending on which type of compilation you will provide.
3. At the DOS prompt, in the DDE_TEST directory, execute the following
   command to compile and link the sample DDE application and generate
   the DDE_TEST.EXE.:
 
	nmake /f dde_w31.mak DEBUG="1"  /*  for Debug version  */

	nmake /f dde_w31.mak DEBUG="0"  /* for Release version */

All files for Debug version are generated into DEBUG directory and for
Release version into RELEASE directory. The DDE_TEST.EXE file is copied
into the project directory if link is finished successfully.