Customizing Driver Shutdown
The shutdown sequence of a Nimbus IVI-COM driver proceeds in an orderly fashion to ensure that driver resources, such as repeated capability pointers or I/O session pointers, are properly released. If the driver developer customized the intialization sequence of the driver, then it may very well be the case that resources were acquired by this custom initialization logic. Those resources would need to be freed during the shutdown sequence of the driver. Alternatively, other cusotm logic might need to be performed at some point after the end user code invokes the driver's Close method.
The topics in this section first explain the initialization sequence and then discuss each of the functions that can be used to intercept driver initialization and inject custom logic.
Download a complete CHM version of this documentation here.