Edit

Introduction to Microsoft STI

  • Article

Microsoft STI is made up of the following primary components:

  • A Still Image Event Monitor, which monitors all installed still image devices and receives notification when Still Image Device Events occur. An event typically indicates that a device is ready to transmit image data. The event monitor also keeps track of all registered applications and can start an application when an event is detected.

  • A set of vendor-supplied, User-Mode Still Image Minidrivers that can detect device activity and notify the still image event monitor of that activity through still image device events. These minidrivers also pass image data from kernel-mode drivers to upper level software.

  • A Scanners and Cameras Control Panel, which allows users to assign specific still image device events to specific applications. In this way, the event monitor will know which application to start when it detects an event. Control Panel also lets users test still image devices.

An Imaging Application can register itself as push-model aware, meaning it can be activated by the Event Monitor when a still image device is ready to transmit an image.

Imaging applications typically read image data streams by calling a high-level Image Acquisition API, such as TWAIN. Device-specific subcomponents of the image acquisition API, such as TWAIN data sources, use an interface into the user-mode still image minidrivers to perform I/O operations.

Microsoft STI defines several Still Image COM Interfaces that allow STI components to communicate with each other.

The next section provides more information about these and other Microsoft STI Components.