==============================================================================
                             SOFTWARE DISKETTE FOR
                 WINDOWS PROGRAMMING POWER WITH CUSTOM CONTROLS
                      BY PAUL S. CILWA AND JEFF DUNTEMANN
==============================================================================

READ THIS NOTE IN FULL BEFORE YOU BEGIN!  PUH-LEEEEZ!


There are actually two steps to installing the software:

1. Install the diskette as though it were a Windows application, by running the SETUP.EXE program on the diskette.  YOU MUST DO THIS!  Until you do, the files on the diskette will have their final characters shown as underscores.
The install utility changes the underscores back to what those final characters "really" are.

SETUP.EXE by default creates a subdirectory called WINPOWR.

Now, the SETUP.EXE program does not perform the complete install.  What it does is install the custom control VBX and HLP files into your WINDOWS\SYSTEM subdirectory, along with a little demo program that demonstrates the use of most of the controls described in the book.  This demo program is installed behind an icon in your Visual Basic subdirectory if you have one.  When you double click on the icon, the demo program will run.

The demo program does *not* demonstrate two of the controls.  The Panel control is for use with SDK-style development, and is incompatible with the demo program, which was written in Visual Basic.  If you know enough about SDK-style Windows development in C or C++, you already know enough to load and use custom controls like Panel.

The other control that the simple demo does not demonstrate is the IniData control.  There is a separate demo program for IniData, but the SETUP.EXE program DOES NOT INSTALL IT.  That's what the second part of the install process is for:

2. Install the source code subdirectories.  There is a bit of a trick to this.  It's not difficult, but it's easy to do incorrectly.  Here's how it works.  Change the default directory to one directory level *above* the WINPOWR subdirectory.  This is typically the root directory.  From that directory, execute the self-extracting archive program SOURCE.EXE with the /D switch, like so:

C:\WINPOWR>CD..
C:\>WINPOWR\SOURCE /D

You can execute SOURCE.EXE from the WINPOWR subdirectory.  However, if you do, SOURCE.EXE will create a *second* (extraneous) WINPOWR subdirectory beneath the original WINPOWR subdirectory.  This won't break any code, but it places a completely unnecessary directory layer between you and the custom control source code files.

SOURCE.EXE creates a subdirectory INIDATA for the IniData control.  Beneath the INIDATA subdirectory is the INIEDIT subdirectory, which contains a simple utility for editing INI files, incorporating the INIDATA control.  This utility is INIEDIT.EXE, and you can either run it from FILE|RUN, or else create a program item for it in one of your groups.


