Release Notes MCCI Usbwin32 Release V2.52b September 15, 1998 V2.52b - Reported Problems addressed in this release ----------------------------------------------------------------------------- 1. V2.52a drivers do not install under Win95 OSR2. Changes ---------------------------------------------------------------------------- SYNOPSIS - The system call IoOpenDeviceRegistryKey() cannot be be called by name. NATURE OF CHANGE V2.52a changes added a call to IoOpenDeviceRegistryKey() for the purpose of retreiving "AltModemStatus" from the registry. This call is a system call. When the driver is built, a Microsoft-supplied library completes the binding by adding loader information to the driver image that tells the loader what the call name is and what Windows module to find it in. The problem stems from the fact that the location of this routine is different between 98 and 95. The result of this move is that a driver that makes this call by name cannot be used in both versions of Windows. The driver will load in one version, but not in another. To work around this issue, the secondary drivers MCCICM95.SYS and MCCICMNT.SYS have been modified to return the address of this system call. MCCICMNT is built to reference the call by name and return it's address. MCCICM95 is built to locate the function using other Windows-only system calls. MCCIMDM.SYS has been modified to call the secondary driver to get the call address rather than calling it by name. IMPACT ON OEMs OEMS must replace all drivers as a set. IMPACT ON DOCUMENTATION No documention changes requrired. V2.25a - Reported Problems addressed in this release ----------------------------------------------------------------------------- 1. Dial-Up-Networking connections are dropped randomly during ftp downloads. 2. Connection with Procomm32 must be restarted after receiving a ZMODEM transfer. Changes ---------------------------------------------------------------------------- SYNOPSIS - AltModemStatus value added to AddReg section of WDM INF file. NATURE OF CHANGE The drivers have moved from a heuristic approach to detemining the modem status return value bit ordering to a Registry-based method. This change was neccessary because some target modems do not support the bit order as detailed in MCCI ER950056. IMPACT ON OEMs OEMs must either replace their WDM Inf file with the version in this release or update their version to add the new Registry value. IMPACT ON DOCUMENTAION MCCI should add an appendix to ER950056 to detail bit ordering expected when AltModemStatus is enabled. Lucent OEM documentation may also need to be updated. SYNOPSIS - Heuristic-based AltModemStatus mapping removed from MCCICOMM.VXD NATURE OF CHANGE Previous versions of MCCICOMM.VXD contains a heuristic that attempted to detect and correct modem status bit orders different from the standard order as described in MCCI ER950056. The alternate ordering assumed by this heuristic was incorrect. Since the heuristic was in a VxD, it also had no effect for NT installations. IMPACT ON OEMs OEMS must replace all drivers as a set. IMPACT ON DOCUMENTATION No documention changes requrired. SYNOPSIS - MCCIMDM.SYS now performs AltModemStatus mapping. NATURE OF CHANGE MCCIMDM.SYS performs mapping from the alternate bit order to the standard bit order based on the setting of AltModemStatus in the device's driver registry entry. This mapping is table-based. The driver now consults the Registry at device-initialization time and sets a context value accordingly. Whenever the driver is called to retreive the current modem status, it sends the request to the driver and then maps the returned status via the mapping table if the saved context value indicates that mapping should be done. IMPACT ON OEMs OEMS must replace all drivers as a set. IMPACT ON DOCUMENTATION No documention changes requrired. SYNOPSIS - Setup request error checking changes in MCCICOMM.VXD NATURE OF CHANGE Procomm32 attempts to set the current Comm state to an invalid state on ZMODEM receive completion if the device is a modem. The application contains a structure that is used to recored the device initial state. This structure is initialized if the device is a serial port, but is left untouched if the device is a modem. When a ZMODEM receive completes, the application uses this structure to set the device state, regardless of the device type. The end result is that an uninitialized structure is passed to the device as part of the setstate call. The previous version of this driver performed error checking on this structure, but not before stopping the read loop. The result of this was that the connection had to be broken and reestablished before additional transfers could occur. The error checking logic has been reworked so that the readloop is only stopped if the request is valid. The readloop is restarted on setstate completion. IMPACT ON OEMs OEMS must replace all drivers as a set. IMPACT ON DOCUMENTATION No documention changes requrired. SYNOPSIS - IOCtl status return problem fixed in MCCICM95.SYS NATURE OF CHANGE A splinter window existed in the IOCtl handler in MCCICM95.SYS that could allow the handler to return invalid status values. In some cases, the driver attempted to retrieve status from memory that had just been released back to the system. This logic has been reworked so that the status value is saved locally before the memory is released. The return status then comes from this saved local cell. IMPACT ON OEMs OEMS must replace all drivers as a set. IMPACT ON DOCUMENTATION No documention changes requrired. [end]Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.