----------------------------------------------
                             README for
      		ID TECH OPOS RS-232 and USB/RS-232
                        Driver v1.700.004
                            March 2004
             ----------------------------------------------
 
(c) Copyright ID Technologies, Inc. 2004. All rights reserved.
 
This document provides information for the execution and use of 
the ID TECH OPOS RS-232 and USB/RS-232 Driver. You may also 
view the ID TECH website at http://www.idt-net.com for information.
 
------------------------
HOW TO USE THIS DOCUMENT
------------------------
 
To view the Internet Explorer Readme.txt on-screen in Notepad, 
maximize the Notepad window.
 
To print Readme.txt, open it in Notepad or another word 
processor, and then, on the File menu, click Print.
 
===================
SYSTEM REQUIREMENTS
===================
 
This OPOS driver is for Windows 2000 and XP only. It does not support 
Windows 98 or me. 
 
========
TO USE
========
 
To install the driver, simply execute the program and follow the instructions 
on the screen.
 
OPOS (Object Linking and Embedding Point of Sale) is an open system standard
for interconnectivity between POS devices developed by Microsoft, NCR, Epson, 
PSI, and others, and administered by the Association for Retail Standards (ARTS). 
Windows based, it defines a set of POS device interfaces to support a range
of POS solutions. An OPOS driver, such as the ID TECH OPOS Driver, interfaces 
a device (such as an ID TECH reader) with a host computer running application 
software. 
 
This OPOS driver is for selected ID TECH RS-232 and USB/RS-232 interface
readers. When using it in conjunction with a USB/RS-232 reader, the ID TECH 
USB serial driver is also necessary. It can be downloaded from the ID TECH
website at http://www.idt-net.com.  
 
Many ID TECH readers have extensive data formatting and editing capabilities
designed into them in order to make them compatible with a wide range of 
application programs. OPOS, however, is specific to its own Point of Sale 
standard, making the variant formatting and editing of output data unnecessary.
Be sure, therefore, to return to reader to its default settings before operating
in the OPOS environment. Please see the user's guide for your specific reader
for details.   
 
======================================================= 
HOW TO ACCESS THE OPOS COMPONENT OF MINIMAG IN VB or VC
=======================================================
In VB or VC, import the OPOSMSR.ocx into the project, and you will see all the
methods and properties you can access. 

To access MiniMag, call "Open" method with the device name "IDTechMiniMag".

The following code extracted from a VC application is an illustration 
that shows how to access the MiniMag:

	//Here m_Msr represent the MiniMag control object.	
	m_Msr.Open("IDTechMiniMag"); 

	//Check whether the device is succeed to open, or not
	if( m_Msr.GetResultCode() != OPOS_SUCCESS ) 
	    MessageBox("This device has not been registered, or cannot be used.");

        //Get the exclusive control right for the opened device.
        //Then the device is disabled for other application.
        //(Notice: When using an old CO, use the Claim.)
	m_Msr.ClaimDevice( 1000 );

       	if( m_Msr.GetResultCode() != OPOS_SUCCESS ) 
            MessageBox("Fails to get the exclusive right for the device.");

        //Enable the device.
	m_Msr.SetDeviceEnabled( TRUE );
        m_Msr.SetDataEventEnabled( TRUE );
       	m_Msr.SetParseDecodeData( TRUE );

NOTE: When don't want to access the MiniMag or before exiting the application, 
	call the codes as follows:

	//Cancel the device
	m_Msr.SetDeviceEnabled( FALSE );

	//Release the device exclusive control right.
	//(Notice:When using an old CO, pls use the function Release().)
	m_Msr.ReleaseDevice();

	//Finish using the device.
	m_Msr.Close();


=====================
ISSUES AND LIMITATION
=====================
Following is a list of properties and methods not support by this release of 
OPOS driver. They are either due to not applicable to the device such as the JIS 
and track 4 data, not supported by the device or have issues in this release.

CapPowerReporting
PowerNotify
PowerState
CheckHealthText
CapJISOne
CapJISTwo
Track4Data
DirectIO (Now it is supported incompletely)
StatusUpdateEvent