				 README.TXT

              Release Notes for Microsoft (R) Visual Control Pack

				Version 1.00

		  (C) Copyright Microsoft Corporation, 1993

This document contains release notes for the Microsoft Visual Control Pack
version 1.0. Information in this document is more current than that in the
manuals or online Help.

     ********************************************************************
     Read Part 1 - Software Installation Information - before installing.
     ********************************************************************

========
Contents
========

Part    Description
----    -----------
 1      Software Installation Information

 2      Custom Controls

 3      Visual Basic Samples


Part 1: Software Installation Information
=========================================

Before installing the Visual Control Pack version 1.0, you should make
backup copies of all the distribution disks.

SETUP.EXE is a Windows application; that is, it is run from Windows
rather than from the MS-DOS prompt.  SETUP.EXE will only run in Windows
Standard or Enhanced mode.  It will not run in Real mode.  You can
determine how Windows is configured on your computer by choosing About
from the Help menu in the Program Manager.

To install the Visual Control Pack, use Program Manager or File
Manager to start SETUP.EXE as you would any other Windows-based
application.  For example, if you are installing from drive A:

	- From the Program Manager File menu, choose Run.

	- In the Run dialog box, type A:SETUP and choose OK.

	Or

	- From the File Manager, double-click on the SETUP.EXE file icon
	  on drive A.

Most of the files on these disks are compressed and must be expanded before
they can be used.  For the Visual Control Pack to work properly, you must
install the files using SETUP.EXE.  You cannot simply copy the files to
your hard disk.

During setup, the Visual Control Pack installs the custom controls into
your Windows system directory.  If you have custom controls with the same
name as the custom controls included with the Visual Control Pack, then
the Visual Control Pack installs the custom controls in your Visual Control
Pack directory.


Part 2: Custom Controls
=======================

Installing Custom Controls
--------------------------
The Visual Control Pack installs custom controls in the Windows system
directory.  If you previously installed the Visual Basic 1.0 Professional
Toolkit, you may have old versions of controls in the \VB\VBX directory.
You should remove any older versions of controls you may have on your
machine.

VB.LIC
------
Please make sure that the copy of VB.LIC in the \windows\system directory
is the only one on your computer.  Otherwise, you may encounter problems
loading the new custom controls.

If an older VB.LIC is being used, or you have a missing or incorrectly
installed VB.LIC file, the following message appears when you try to add
the custom control file to your project:

 "License file for custom control not found.  You do not have an
  appropriate license to use this custom control in the design
  environment."

Communications Control
----------------------
Page    Section
--------------------
116     Visual C++ Declaration for ComInput Function

	Declaration should be:
	int FAR PASCAL ComInput(HWND hWnd, LPSTR lpData, int cbData);

116     Visual C++ Declaration for ComOutput Function

	Declaration should be:
	int FAR PASCAL ComOuput(HWND hWnd, LPSTR lpData, int cbData);


Pen Controls (PENCNTRL.VBX) Update
----------------------------------------

The CPointerToVBType and VBTypeToCPointer functions are not necessary
in Visual C++.  You can simply typecast the memory address, which is
passed to the RcResult event, to a RCRESULT structure pointer.

Shipping PENWIN.DLL with Your Application
-----------------------------------------
PENWIN.DLL is a fully redistributable component of Windows for
Pen Computing.  Because applications will seek to leverage the
Pen API - Visual Basic controls in particular - PENWIN.DLL can
be shipped with your application.  There are some considerations
to keep in mind when shipping PENWIN.DLL with your application:

1.  PENWIN.DLL functions ONLY under Windows 3.1.  It WILL NOT
    WORK with Windows 3.0 because it functions only as an
    installable device driver (a feature not present in Windows
    3.0).

2.  As with other redistributable components (such as COMMDLG.DLL
    and the OLE libraries), it is the responsibility of the
    application vendor to determine whether PENWIN.DLL has
    already been installed (there is a GetSystemMetrics() call
    for this) and to ensure that the version of PENWIN.DLL with
    the latest version stamping is the one that is running. These
    issues are the same for all redistributable components, and
    further information is contained in the Windows SDK.

3.  Unlike some of the other redistributable components, if your
    application installs PENWIN.DLL for the first time, or
    replaces the current version with a later one, Windows will
    have to be restarted.  As an installable driver PENWIN.DLL
    can be loaded only at Windows boot time.  Restarting Windows
    can be accomplished via an ExitWindows() call or by simply
    prompting the user to do so.

    NOTE:  To install PENWIN.DLL on a Windows 3.1 system follow the
	   directions listed in the Pen Sample section below.

4.  PENWIN.DLL may be in either the \WINDOWS or the \WINDOWS\SYSTEM
    directory.  The default will be \WINDOWS, but since Windows for Pen
    Computing is an OEM product, Microsoft cannot completely control where
    PENWIN.DLL is located on a particular machine.

To get a good feel for the Pen Windows controls, you are encouraged to
use and experiment with the Pen sample application (PENSMPL.MAK).


Part 3: Visual Basic Samples
============================
Note:  These samples are only intended for Visual Basic 2.0.

Multimedia Sample
-----------------
This sample program illustrates the use of some of the device types
supported by the Media Control Interface (MCI).  The four device 
types used in this program are:

   Device Type     Description
   -----------     -----------
   MMMovie         Plays Multimedia movie files (*.mmm).
   CDAudio         Plays audio discs from the CD-ROM drive.
   Sequencer       Plays MIDI sequencer sound files (*.mid).
   WaveAudio       Plays digitized waveform sound files (*.wav).

HARDWARE REQUIREMENTS:
In order to access a CD-ROM drive or a sound card, the hardware,
along with any supporting device drivers, need to be installed
and configured for the machine.  The following table lists
the hardware required for the MCI device types used in this
program:

   Device Type     Hardware
   -----------     --------
   MMMovie         No extra hardware.  *See software requirements.
   CDAudio         CD-ROM drive.
   Sequencer       Sound card (e.g., Sound Blaster Pro)
   WaveAudio       Sound card.

SOFTWARE REQUIREMENTS:
In order to run the MCI application, Microsoft Windows with
Multimedia Extensions 1.0, or Windows with Multimedia must be 
installed.  The Multimedia Extensions include device drivers for
the different types of MCI devices.

To access a specific MCI device type, the corresponding MCI device
driver must be installed.  The following table list the device 
drivers required for the MCI device types used in this program:

   Device Type     Device Driver
   -----------     -------------
   MMMovie         MCIMMP.DRV    *See note below.
   CDAudio         MCICDA.DRV
   Sequencer       MCISEQ.DRV
   WaveAudio       MCIWAVE.DRV

The [mci] section of the SYSTEM.INI file contains a list of the
installed MCI device types.  This is what your file would look
like if all 4 of the above device types were installed:

[mci]
CDAudio=mcicda.drv
WaveAudio=mciwave.drv
Sequencer=mciseq.drv
MMMovie=mcimmp.drv

BACKGROUND:
The MCI control provides a high-level interface for using 
multimedia devices. Using the property settings of a control, you
can determine the settings and the actions of a device.

The MCI control is also smart enough to know what action are 
relevant for the current state of a device.  For example, if you 
click on a "Pause" button while playing a movie, the "Play" 
button is automatically re-enabled.

NOTE:
If you are unable to run an animation movie (*.mmm file), make 
sure the MCIMMP.DRV and MMP.DLL files are installed on your 
machine.  To install the animation driver from Windows 3.1, run 
the "Drivers" applet from the Control Panel, insert Disk 1 of the
Visual Control Pack (the files MCIMMP.DR_ and MMP.DL_ are also in
the C:\VCP subdirectory).  Select "Unlisted Driver", and accept
"A:\" as the directory.  You will then be ready to use the
animation features of the MCI control.

FILES:
   ABOUTBOX.FRM.......The dialog box for the "About Box".
   ANIMATE.FRM........Form for playing Multimedia Movie files.
   CD.FRM.............The form for playing compact disc audio.
   GLOBAL.BAS.........Global data types and declarations.
   MCITEST.BAS........Global Subs and Functions.
   MCITEST.FRM........The main form.
   MCITEST.MAK........The MAKE file for the project.
   MCITEST.MID........Sample MIDI sequencer file.
   MCITEST.MMM........Sample Multimedia Movie file.
   MCITEST.WAV........Sample waveform file.
   OPENDLG.FRM........Form for holding the Common Dialog control.
   WAVE.FRM...........Form for playing waveform and MIDI files.

TO RUN:
In the Visual Basic environment (VB.EXE), you can load the files
in this sample program by choosing Open Project from the File 
menu, and selecting the MCITEST.MAK file.
 
Two additional files appear in the Project Window:

   MCI.VBX............MCI control.
   CMDIALOG.VBX.......Common Dialog control.

PEN Sample
----------
Note:  To run this sample you must have Windows for Pen Computing, 
       or install the PENWIN.DLL file.  See below.

BRIEF DESCRIPTION of PEN SAMPLE PROGRAM:
This sample program illustrates many uses of the Pen controls:
  * the new On-Screen Keyboard control
  * inking and displaying bitmaps on the new InkOnBitmap control
  * handwriting recognition in both delayed and non-delayed mode
  * recognition of gestures
  * transfer of ink data between controls
  * manipulation of the Recognition Context data structure
and more.

The file PENAPI.TXT contains function and constant declarations
for the entire set of Windows for Pen Computing API.

FILES:
   DELAY.FRM.........Form for demonstrating Delayed Recognition.
   DELAY.FRX.........The binary for DELAY.FRM.
   EDITSUBF.FRM......Support Form for Gesture demonstration.
   GESTFRM.FRM.......Form for demonstrating Custom Gestures.
   INKFRM.FRM........Form for showing transfer of Ink data.
   IOBFRM.FRM........Form demonstrating the Ink On Bitmap control.
   IOBFRM.FRX........The binary for IOBFRM.FRM.
   KEYBRD.FRM........Form for the On-Screen Keyboard Button demo.
   KEYBRD.FRX........The binary for KEYBRD.FRM.
   PENAPI.TXT........Pen function declarations and constants.
   PENMAIN.FRM.......Main form.
   PENMAIN.FRX.......The binary for MAIN.FRM.
   PENSMPL.MAK.......The MAKE file for the project.
   RCFRM.FRM.........Form demonstrating the Recognition Context.
   GRAFPAPR.BMP......Bitmap for creating graph paper effect.
   RULEPAPR.BMP......Bitmap for creating ruled paper effect.
   SKBFACE.BMP.......Bitmap of default keyboard on SKB Button.
   TRANSFRM.FRM......Form for demonstrating transfer of ink data.

TO RUN:
After starting the Visual Basic environment (VB.EXE), you can load
files in this sample program by choosing Open Project from the File
menu and select the PENSMPL.MAK file.

Installing PENWIN.DLL:
This procedure will result in a system that will let you run
applications that contain Visual Basic BEdit, HEdit, InkOnBitmap,
and SKB Button controls and call the Windows for Pen Computing APIs.
You will not be able to perform handwriting recognition or draw ink
on the screen. Microsoft Windows 3.1 is required.

SYSTEM.INI Changes
The following items must be added or changed in your SYSTEM.INI
file so that the pen extensions will work.  NOTE: Back up your old
SYSTEM.INI file before proceeding.

1.  In the "[boot]" section:
      Add "penwindows" to the list of drivers after "drivers=".
      For example:
        drivers=mmsystem.dll penwindows

2.  In the "[drivers]" section:
      Add a new item "penwindows" and set it equal to the path to 
      PENWIN.DLL.
      For example:
        penwindows=C:\WINDOWS\PENWIN.DLL

3.  Restart Windows so the changes can take effect.

When Windows is restarted PENWIN.DLL will be loaded as an
installed driver and you will be able to run applications
containing Visual Basic BEdit, HEdit, InkOnBitmap, and SKB
Button controls and call the Windows for Pen Computing APIs.

PicClip Sample
--------------
Program example using the PICCLIP.VBX control.

BRIEF DESCRIPTION:
This sample program illustrates one of the many possible uses of
the Picture Clipping control.

BACKGROUND:
This sample application uses the PicClip control to spin a top.

FILES:
   INFOFORM.FRM......The information form.
   INFOFORM.FRX......The binary data for the information form.
   REDTOP.FRM........The main form.
   REDTOP.FRX........The binary data for the main form.
   REDTOP.MAK........The MAKE file for the project.

TO RUN:
After starting the Visual Basic environment (VB.EXE), you can 
load files in this sample program by choosing Open Project from
the File menu and select the REDTOP.MAK file.

Communications Sample
---------------------
Program example using MSCOMM.VBX in a terminal emulation program.

BRIEF DESCRIPTION:
This sample program illustrates how to use the communications
control with a serial port.

BACKGROUND:
MSCOMM.VBX allows you to open a serial port, change its settings, 
send and receive data through the port, and monitor and set many 
of the different data lines.  It's dual-method access allows for 
both polling and event driven communications.

FILES:
   CANSEND.FRM.......Dialog box used during file transfer.
   TERMSET.FRM.......Form used to change the serial port settings.
   TERMSET.FRX.......Binary data for TERMSET.FRM.
   VBTERM.FRM........The main form.
   VBTERM.FRX........Binary data for VBTERM.FRM.
   VBTERM.GLO........Global declarations.
   VBTERM.MAK........The MAKE file for the project.

TO RUN:
After starting the Visual Basic environment (VB.EXE), you can load
files in this sample program by choosing Open Project from the File
menu and select the VBTERM.MAK file.