****************************************** * NOTICE TO CUSTOMERS: * * * * IBM SYSTEM PROGRAMS LICENSE AGREEMENT * ****************************************** BEFORE OPENING THIS PACKAGE OR USING YOUR SYSTEM, YOU SHOULD READ THE LICENSE.TXT FOR THE TERMS AND CONDITIONS. OPENING THIS PACKAGE OR INITIAL USE OF THE SYSTEM PROGRAMS INDICATES YOUR ACCEPTANCE OF THESE TERMS AND CONDITIONS. ***************************************************** * Various fixes/solutions: * * * * Last Update: 02/08/99 - Add readme.txt and * * license.txt files. * * * * 01/03/01 - Add updated 4777 DOS * * Serial driver IBM4777.SYS * * * * 06/08/01 - Add updated 4777 Windows * * DLL's: * * - WNT77MAG.DLL * * - WNTA7MAG.DLL * ***************************************************** LICENSE TXT ** LICENSE AGREEMENT XBDA SYS ** DOS driver to supply missing Extended BIOS functions ** on some non-ibm clones and Aptivas. ** Add this driver with a device= statment to the top ** of config.sys before any DOS FIO drivers are loaded. ** IBM4777 SYS ** Updated 4777 DOS Serial Driver that fixes errors ** seen during IPL on the following PC's: ** PC300(2169-xxx) ** NetVista A10(2169-xxx) ** ************************************************************************ * 06-08-01 Update: * * WNT77MAG.DLL AND WNTA7MAG.DLL updated to fix a 4777 Async API problem * being seen by a customer in Switzerland. * * Errors (1541 - Device armed) were being received from a MagReadDataAysnc * that was preceeded by a MagReadDataAsync/MagAbort sequence. * * The problem was that the MagReadDataAsync API was returning before * the device was physically armed. If a MagAbort was then issued, * the potential existed for the MagAbort to simply return because the * device was still not armed. A short time later, the device would * eventually become Armed and any subsequent MagReadDataAsync API's would * fail with a 1541 because the device was still armed. * * The fix was to provide private API's between the two DLL's to allow * WNTA7MAG.DLL the ability to know when the device was physically armed * at which time it was safe to return to the application. * * Note: The same problem could occur for a MagEncodeDataAsync and is * fixed in the new DLL's. * **************************************************************************** WNT77MAG DLL ** 4777 Windows DLL. ** Updated on 06-08-01 to fix a problem being seen when ** using the Async API's in WNTA7MAG.DLL as described above. ** WNTA7MAG DLL ** 4777 Windows DLL. ** Updated on 06-08-01 to fix a problem being seen when ** using the Async API's in WNTA7MAG.DLL as described above. **