Application Development - Matrox 4Sight User Manual

54 Chapter 4: Developing an application for Matrox 4Sight under Windows NT Embedded

Application development

To achieve the very small space requirements demanded by the
DiskOnChip, much of the familiar shell of the full Windows NT
operating system has not been included in the version of
Windows NT Embedded shipped with the Matrox 4Sight unit.
The lack of a familiar shell means that you might find Windows
NT Embedded slightly awkward initially. This chapter explains
how to develop an application for Matrox 4Sight from a remote
development computer. The following is a broad outline of the
necessary steps:
1. Code and compile your application on the development
computer.
2. Optionally, debug the application on your development
computer if you have the necessary hardware in place to do
so.
3. Copy your application to the Matrox 4Sight unit.
4. Run the application on the Matrox 4Sight unit.
5. Remotely debug your application, if still necessary.
6. Remove unnecessary files from the Matrox 4Sight unit.
Note that to code and compile a MIL/MIL-Lite application, it is
necessary to first purchase and install a MIL/MIL-Lite package
on your development computer. Ensure that it has the same
version and build numbers as the redistribution version on the
Matrox 4Sight CD. Refer to the readme file on the Matrox
4Sight CD for details.
To do preliminary debugging on your development computer
(optional step), ensure that you have the necessary hardware
in place to do so (for example, a Matrox Meteor-II frame
grabber). If the application is a MIL application, you must also
attach the MIL hardware key to the parallel port of the machine
running the application. If possible, use the same version
(service pack) of Windows NT as the version from which
Windows NT Embedded was created.