8.12
S
CAN
D
EINIT
()
Prototype:
SCAN_RESULT ScanDeinit();
Purpose:
Performs final clean-up in the DLL pending shutdown.
Arguments:
None.
Notes:
ScanDeinit() is typically called during the shutdown/cleanup phase of the client application. Any
scanning devices that are open will be closed by the ScanDeinit() function.
Returns:
SR_SUCCESS
The operation completed successfully.
SR_NOT_INITIALIZED
A successful call to ScanInit() must be made first.
SR_DEVICE_FAILURE
May occur as a result of calling ScanInit() on Windows NT systems only. An internal error occurred
while communicating with the scanning device (perhaps the device was removed during the
function call.) The client application will probably need to be re-started, and possibly the Win32
Desktop system reset (after first removing the scanning device from the host.)
On Windows NT systems, a scanning device MUST be present in the system BEFORE calling
ScanInit(). Additionally, the scanning device MUST NOT BE REMOVED from the system while the
ScanAPI is in use. Since the API does not support hot-swapping for this platform, no device
removal or insertions messages are generated. If a card is removed and re-inserted while a
scanning session is in progress, the COM port associated with the PC Card will not be configured
properly, and ScanAPI errors will result.
Under Windows NT, all PC Card devices must be present at boot-time, and can never be safely
removed without re-booting. The exception is if you have added third-party Card and Socket
Services to your NT system. In this case, the scanning device must be present before the ScanInit()
call, but can be safely removed AFTER ScanDeinit() is called.
April 8, 2010
Page 37
Document#: 6410-00147 K
Revision 2.28
