SAMSUNG Composite USB Driver v4 - 34 - ReleaseNotes
SAMSUNG Composite USB Driver v4 - 34 - ReleaseNotes
SAMSUNG Composite USB Driver v4 - 34 - ReleaseNotes
Phone +1-607-277-1029
Fax +1-607-277-6844
www.mcci.com
Copyright © 2005
All rights reserved
PROPRIETARY NOTICE AND DISCLAIMER
Unless noted otherwise, this document and the information herein disclosed are proprietary to
Moore Computer Consultants, Incorporated, 3520 Krums Corners Road, Ithaca, New York
14850 (“MCCI”). Any person or entity to whom this document is furnished or having
possession thereof, by acceptance, assumes custody thereof and agrees that the document is
given in confidence and will not be copied or reproduced in whole or in part, nor used or
revealed to any person in any manner except to meet the purposes for which it was delivered.
Additional rights and obligations regarding this document and its contents may be defined by a
separate written agreement with MCCI, and if so, such separate written agreement shall be
controlling.
The information in this document is subject to change without notice, and should not be
construed as a commitment by MCCI. Although MCCI will make every effort to inform users
of substantive errors, MCCI disclaims all liability for any loss or damage resulting from the use
of this manual or any software described herein, including without limitation contingent,
special, or incidental liability.
MCCI, TrueCard, TrueTask, MCCI Catena, and MCCI USB DataPump are registered
trademarks of Moore Computer Consultants, Inc.
MCCI Instant RS-232, MCCI Wombat and InstallRight Pro are trademarks of Moore Computer
Consultants, Inc.
All other trademarks and registered trademarks are owned by the respective holders of the
trademarks or registered trademarks.
TABLE OF CONTENTS
1. Introduction........................................................................................................................................ 1
1.1 Scope....................................................................................................................................... 1
- iii -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
3.2.12 Bug 1273: Hyperterm hangs if Set Line Control Fails ....................................... 12
3.2.13 Bug 1274: Driver sometimes set Xon/Xoff limits to zero ................................. 12
3.2.14 Bug 1292: Correctly synthesize modem status change bits.............................. 13
3.2.15 Bug 1355: Add support for QXDM to Qualcomm DM-port driver ................ 13
3.2.16 Add serial data buffer policy controls................................................................. 13
3.2.17 Error processing improvements........................................................................... 14
3.2.18 Bug 1380: Surprise Removal Handling ............................................................... 14
3.2.19 Suspend & Hibernation controls.......................................................................... 15
3.2.20 Support Prolific PL2303-HX ................................................................................. 15
3.2.21 Bug 1346: Spinlock management ......................................................................... 15
3.2.22 Bug 1359: Unknown devices appear when multiple identical devices
connected via hub ............................................................................................................... 15
3.2.23 Bug 1362: Start modem status loop only when needed by the protocol. ....... 16
3.2.24 Bug 1363: Handle STALL condition in Driver Rx loop .................................... 16
3.2.25 Bug 1365: Prevent an infinite wait in MCCIMODEM....................................... 16
3.2.26 Bug 1372: XONLimit & XOFFLimit settings ...................................................... 17
3.2.27 Bug 1375: connect to com port after suspend..................................................... 17
3.2.28 Bug 1395: Writefile never returns ........................................................................ 17
3.2.29 Bug 1390: Accept Suspend during active communications session................ 18
3.2.30 Bug 1407: CommClearError returns correct status ........................................... 18
3.2.31 Bug 1408: Fix bluescreen in return from hibernation........................................ 18
3.2.32 Bug 1409: load drivers on Win98 after the PC resumes from standby........... 19
3.2.33 Bug 1468: Avoid hang on second hibernation request. .................................... 19
3.2.34 Bug 1475: Avoid Application hang...................................................................... 19
3.2.35 Bug 1477: Blue screen on surprise remove with modem port open ............... 20
3.2.36 Bug 1490: Checked serial driver causes blue screen during first installation 20
3.2.37 Bug 1497: Bluescreen while running HCT Device Path Exerciser test ........... 20
- iv -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
4.2 xxxxUninstall....................................................................................................................... 24
4.2.1 Bug 1121: Uninstall removes driver & INF files if called with –quiet ............ 24
-v-
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
1. Introduction
1.1 Scope
These notes apply to MCCI V4.16 through V4.34 build 2703 USB driver sets, including:
• INFs
• executables
Note that in this revision, where applicable, detail has been added. In the case of feature
requests, the reasons may be cited. In the case of bugs, the problem description is included, and
in some cases the reproduction procedure is also included.
The “official” releases of V4.16-V4.34 include installation technology based on InstallRight Pro
V1.11 through V1.26. The Installation technology is built separately from the drivers, and has
an independent version number. That version number can be determined easily from the file.
Please consult your MCCI support contact for more information.
MCCI may release intermediate driver builds. The first build of each revision level is 2701;
4.34.2701 is the first driver release of this series. Note that not all intermediate builds are
released to customers, and not all intermediate builds have changes that are visible to
customers. Therefore, only builds that were released to customers with visible changes are
included in the following table.
This section summarizes the changes between builds, with reference to the note on each change.
Table 1. Release Matrix for V4.34.2705
1490 - - - √ √ Checked serial driver causes blue screen during first installation
-1-
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
-2-
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
A device from one manufacturer produces USB device/interface descriptors that are
non-standard, in that some interface numbers were omitted from the set of interfaces in
the configuration descriptor. This situation normally causes the Microsoft USB stack to
fail during driver startup. The bus driver was modified to work around the discovered
issues.
Effect on subordinate drivers: none – they still only receive the descriptors that belong
to their specific function of the device.
-3-
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Effect on devices: some devices that previously would not work as multi-function
devices under Windows now will work correctly. No effect for devices that were
previously working.
3.1.2 Bug 1115: WHQL Device Path Exerciser blue screen w/Driver Verifier
Problem Description: Running WHQL HCT11.2 Universal test DPE and DV, getting blue
screen and bug check errors.
Problem solutions:
Problem Description: V4.10 cannot support more than 4 identical devices simultaneously.
(V3.40 could support at least 8 identical devices simultaneously.)
This problem was introduced by an attempt to work-around issues with hot Plug and Play (bug
1049, which was fixed in 4.10). However, this inadvertently introduced a limitation in the
number of devices that can be supported.
Problem Solution:
2. correct some boundary conditions which caused blue-screen problems on hot removal.
Effect on applications: applications no longer need to be quite as careful about closing COM
ports immediately when an unplug event (WM_DEVICECHANGE) is reported by Windows.
-4-
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Problem Solution: Allow each function driver to specify its own Surprise Removal capabilities.
Effect on applications: Users will now be able to invoke the "Safely Remove Hardware" applet
prior to disconnecting their device from the system.
Problem Solution: Fix the generic driver so that it detects the error generated by attempts to
open non-existent pipes on interfaces without endpoints. When detected, it fails gracefully with
error indication.
3.1.6 Bug 1278: Attempt to open an interface without all pipes fails
Problem solution: The solution is to check for null pointers in the debug print.
Effect on devices: the checked drivers can now recover gracefully if a device USB
implementation is defective.
Feature Request: Allow the loading of multiple driver instances for each enumerated device
function in the event that a previous driver instance remains loaded.
2) driver cdcbus detects this key, and allows multiple instances if configured.
Effect on devices: separate drivers instances can be loaded for multiple devices.
-5-
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Feature implementation:
Problem description: after implementation of the Cable Emulation drivers, installation did not
work in Windows XP gold or in Windows XP SP1. (It worked fine in Windows 9x, any version
of Windows 2000, and in Windows XP SP2. This turns out to be a regression bug between
Windows 2000 and Windows XP, fixed in XP SP2.
Problem Description: When running the WHQL HCT12.0 NDIS test, Driver Verifier bug checks
with DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9).
Problem Solution: Implement a work-around which preserves the existing behavior when
running on all OS versions below WinXP.
3.1.11 Bug 1399: Blue Screen in Driver Verifier after resume from Standby
Problem Description: When running the WHQL HCT12.0 NDIS test, Driver Verifier bug checks
with DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5).
Problem Solution: Removed debug print code which was accessing the pIrp->IoStatus block
after having called PoCallDriver.
-6-
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
3.1.12 Bug 1465: Prevent BlueScreen while starting devices due to timelock mechanism.
Problem Description: If the current system time predates the driver build time, the driver
generates a bluescreen.
-7-
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Effect on devices: host response to interrupts may be less than that indicated by the device in
descriptors.
Problem Description: When doing WHQL 2m_P_hibernate test, Windows becomes stuck at
preparing to enter hibernation screen. The mouse will move but the keyboard does not
respond. This happens randomly during the 10 times scheduled hibernation of the test. System
recovery requires hardware reset or power-off.
3.2.1 Bug 1138: Blue Screen on unplug while Internet Access Wizard running.
Problem solution: Avoid de-referencing an invalid pointer. This change affects all drivers that
export a serial or modem-compatible interface.
-8-
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
3.2.2 Bug 1142: WHQL Device Path Exerciser works w/o blue screen
Problem Description: On Windows XP, the WHQL Device Path Exerciser crashes with v4.14rc1
serial/modem drivers. With free drivers, the stack backtrace includes a symbol of the form:
xxx-mdm!mccimdmd_klsi_immedchar_done
Problem solution: Correct a function result to match results returned by Microsoft in-build
serial drivers. This change affects all drivers that implement
IOCTL_SERIAL_IMMEDIATE_CHAR.
Effect on applications: The MCCI drivers more accurately model the behavior of real serial
ports.
As requested by a customer, support for two Vendor Specific IOCTLs was added. These in
turn support two applications supplied by that customer.
Note: These IOCTLs are enabled by a special entry in the INF file. Please contact MCCI for
more information if needed.
Effect on applications: If IOCTL support is not enabled in the registry, there is no effect. If
enabled, two new IOCTLs are available, but none of the existing IOCTLs are affected.
Problem Description: a customer device does not correctly handle the CDC 1.1
SET_BREAK_ON/OFF setup requests; the device does not perform the status phase. This
causes the original IRP's status to remain STATUS_PENDING until the request is cancelled by
the application.
Solutions:
1. For devices that report a CDC 1.1 compliant descriptor, but which do not handle the
CDC setup requests, simulate BREAK handling inside the driver without sending to the
device if the "EnableCR1147".(cdc protocol) registry key is set to a positive value.
-9-
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
2. For devices which report only a vendor-specific descriptor, but which support CDC 1.1
BREAK handling correctly, the DisableCR1147 registry key, if set to a positive value,
disables this BREAK simulation.
This change affects CDC ACM protocol drivers and the applicable manufacturer-specific
protocol drivers.
Effect on devices: devices that don’t implement CDC SET_BREAK requests correctly can now
be used. A registry setting is required to tell the driver that break doesn’t work.
3.2.5 Bug 1148: WHQL Device Path Exerciser works w/o blue screen
Problem Description: On Windows XP, the WHQL Device Path Exerciser crashes with v4.14rc1
drivers. The crash backtrace indicates that the crash is at:
xxx-serd!mccimdmd_diagnostic_sethandflow+0x72
Affected drivers: this bug only affected the “diagnostic port” drivers for CDMA handsets.
Problem Description: Under Windows 9X and ME the V4.16 and earlier driver releases would
not work correctly after having been manually removed through Device Manager and then re-
installed through the use of the Device Manager “refresh” function. The COM port assigned by
the system during the original installation is no longer able to be opened. When the device is
un-plugged and subsequently re-plugged in, another driver installation is performed resulting
in a new COM port assignment.
Problem Solution: Ensure that registry keys created during the initial installation process are
restored when processing CONFIG_ENUMERATE requests.
Effect on applications: Applications will now be able to re-open the original assigned COM
port after the manual driver removal and refresh procedure.
- 10 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
3.2.7 Bug 1180: Blue Screen if disconnect during DUN connection process
Problem Description: A "blue screen" would infrequently occur if a handset was disconnected
from the PC while Dial-Up Networking was in the process of establishing a connection.
Problem Solution: The Modem Filter Driver was modified to return appropriate status to
IOCTLs while in a Surprise Removal state.
Effect on Applications: TAPI applications should receive the appropriate status and abort the
connection attempt.
Problem Description: TX_EMPTY event notifications are sometimes lost depending on the way
applications use the Serial API.
Problem Solution: Implement a different mechanism for resetting the driver's notion of the
TX_EMPTY state.
Problem description: In Windows XP, running Dial Up Networking, on USB cell phone, the
connection is made and works, but the data traffic counters are not always updated. Similarly,
the ‘lights’ on the tray icon do not always blink with data traffic.
- 11 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Problem Solution: not yet known. The work around is to close the connection or unplug before
hibernating, which is inadequate.
• Updated init macros to _V12; the standard declaration macro now requires
<drvname>_FlushBuffers as a dispatch routine.
Problem Description: Some drivers do not implement all possible settings in VSP.
Unfortunately, they did not fail with error returns. Example: If an illegal setting is selected
using Hyperterm under Windows 2000 or XP, and an attempt is made to open the port,
Hyperterm locks up until manually terminated. This also happens with WCOM32. It doesn't
seem to happen with COMTEST2. However, if portmon is loaded, the problem is not
reproducible; you instead get a proper "can't open port" message.
Problem Solution: To affected drivers, add error returns for invalid VSP line settings when
working with Hyperterm and the Windows comm library. Also change SET_CHARS not to
change characters in the database until the device has commented on the command.
Effect on Applications: Applications that generate illegal settings but also implement error
recover will now recover gracefully.
Problem description: For Windows 98, if no Xon or Xoff Limit is specified, the driver may set
them both to zero. This causes logical errors in the firmware regarding flow control.
Problem solution: Add logic that detects this condition and adjusts.
- 12 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Problem Description: Trying to connect to a vendor’s modem implementation failed. The cause
was incorrect handling of modem status bits.
Problem Solution: Return the current status bits (as the W32 drivers actually work), not the
previous status as described in the DDK.
3.2.15 Bug 1355: Add support for QXDM to Qualcomm DM-port driver
Problem Description: PQualcomm's QXDM application requires special support in the DM-port
driver, to allow QXDM to operate correctly across surprise removals. Previous versions of the
MCCI DM driver did not include this support.
Problem solution: The support in the MCCI DM driver was upgraded to support the latest
versions of QXDM.
Effect on applications: QXDM will be able to detect surprise removal in its preferred way. This
uses a proprietary API, and so other applications are not effected.
This dword registry should be used only when necessary to support applications that require
the driver to track the last AmountIniInQueue to determine whether or not to ignore a
SERIAL_PURGE_RXCLEAR IOCTL_SERIAL_PURGE request.
Implementation:
2) add SuppressDevicePurge registry key; add logic to suppress purge requests to the
device based on that key.
- 13 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
This key is used to encourage legacy applications to relinquish any open handles to the driver
as quickly as possible.
Implementation:
1) When called during error processing, check for null URB pointers.
2) In surprise removal, drop the modem status lines and satisfy any pending
WAIT_ON_MASK IOCTLs.
These keys are used to encourage legacy applications to relinquish any open handles to the
driver as quickly as possible.
Implementation:
4) If surpise removal event detected, let the modem status loop die.
5) If the corresponding bits are set in EnableMdmStatusHeuristics are set, force the
DCD and/or DSR signals ON.
- 14 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Depending on the specific setting, this dword registry key can configure the driver to allow or
refuse a suspend/hibernate request.
Problem description: A local KIRQL variable was being used incorrectly. This can cause a blue
screen under specific error recovery code execution paths. This problem is localized to the
MCPC AT Command and WMC Device Management protocols of the serial/modem drivers.
3.2.22 Bug 1359: Unknown devices appear when multiple identical devices connected via hub
Problem Description: plug in two or more identical devices (e.g. phones) through a hub, and
run an application. After several rounds of test, some phones will start to show "unknown
device" during enumeration.
Problem Solution:
- 15 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
The key defines the number of milliseconds to delay. A 50 millisecond minimum delay
is enforced in order to comply with the implementation in cusbdasy.c.
MCCIMODEM_CLOSE_PROCESSING_HEURISTICS_NO_DEVICE_ACCESS
This bit definition instructs the driver not to send any requests to the device during
"close" processing.
3.2.23 Bug 1362: Start modem status loop only when needed by the protocol.
Problem description: The modem status loop is not necessary for protocols that utilize
notification endpoints to deliver modem status information such as CDC ACM, MCPC, and
WMC.
Problem solution: Move the "Start" and "Stop" of the modem status loop from the generic
open/close functions to the class-specific open/close functions of the protocols that actually
need it.
Problem description: If the RxIrp completes with an error, and the URB status indicates a
USBD_STATUS_STALL_PID error, the RxIrp should actually be resubmitted after resetting the
IN pipe. Otherwise, a STALL condition may lead to device errors/instability.
Problem solution: Detect whether the RxIrp error status is associated with an URB status of
USBD_STATUS_STALL_PID. If so, then set the RxNeedsReset flag and re-submit the RxIrp.
Problem description: It is possible for a thread to enter into an infinite wait state if it has tried to
terminate an IRP and if the RX pipe reset completes with an error.
- 16 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Problem solution: Detect the condition and ensure that this condition is handled correctly.
Problem description: When some applications try to set XOnLimit and XOffLimit larger than
the ReceiveQueueSize for flow control, the driver will return fail.
Problem solution: by customer request, the drivers will return success indication, whether or
not the limits exceed ReceiveQueueSize.
Effect on applications: applications that try to set these limits above ReceiveQueueSize will not
fail due to error returns from setting those high values.
Problem description: HCT is unable to connect com port after first time hibernation with
AllowSuspendWhileOpen registry key enabled.
Problems solution: the power management code now checks whether the Rx loop has been re-
started as a result of a failing RxIrp completion status or the result of a previous call to RxStop.
Problem Description: The serial/modem driver did not handle the case where a write
completion occurs just as the write total timer dpc has been scheduled to run, causing the
current IRP_MJ_WRITE request to remain pending forever.
Problem Solution: Detect the situation and ensure that the Irp is completed.
Effect on Applications: Applications which previously were susceptible to the problem now
work correctly.
- 17 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Problem Description: By design, our WMC drivers block suspend if there is an active
connection. Through HCT 11.x, this passed WHQL. By Microsoft decision, this fails in HCT
12.0. They granted a contingency #1137 to support migration.
Problem solution: for Windows XP and later, our WMC drivers will accept suspension if there is
an active connection. The implementation includes an AllowSuspendWhileOpen registry key,
that forces the previous policy.
Effect on Applications: Legacy applications which are not power management aware will be
adversely effected when running on Windows XP or later. In particular, forced suspension
(user closes the lid on a notebook; low power warnings) will cause the driver to accept
suspension. Connections will be lost.
Power management aware applications, like Windows’ DUN, will know to re-establish the
connection.
Problem Resolution: Implemented a registry key based approach to configure the VSP driver to
issue the VSP_bRequest_GET_COMM_STATUS bRequest to the device on a brand by brand
basis. The new dword registry key is named SendRequestForCommStatus.
Effect on Applications: VSP aware applications can now receive COMMSTATUS information
from a VSP device.
- 18 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
3.2.32 Bug 1409: load drivers on Win98 after the PC resumes from standby
Problem Description: After a PC resume from standby, modem and serial drivers were not
visible in device manager under the device types, but they were visible under "Universal Serial
Bus controllers" category.
Effect on Applications: Applications should not lose devices after suspend and resume.
Problem description: In Windows 2000 or XP, if a second suspend request is generated while a
first one is pending, the driver hangs.
Problem resolution: IRP queuing is disabled after processing the first suspend request has
started.
Problem Description: A phone test and management application uses device management
handles. When an attempt is made to terminate the application while the device is connected, it
does not surrender the DM handle, and stays active in the task manager. Further, if the
application is launched again, it cannot used the device, because the handle is still held by the
previous application instance.
Effect on Applications: Applications should not hold handles when terminated, but they may
be able to work if they do.
- 19 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
3.2.35 Bug 1477: Blue screen on surprise remove with modem port open
Problem Description: In Windows 2000 or XP, using Hyperterm application, with modem port
open (not a com port). On surprise removal there is a blue screen.
Effect on Applications: robust system behavior when modem ports are used.
3.2.36 Bug 1490: Checked serial driver causes blue screen during first installation
Problem Description: Using Windows XP and a 4-port serial adaptor, checked version serial
driver causing Windows blue screen when loaded. It tries to get tsp file object pointer which is
null for the serial drivers.
Problem Resolution: Add a test for the validity of the irpStack file object before attempting to
use it.
3.2.37 Bug 1497: Bluescreen while running HCT Device Path Exerciser test
Problem Description: Running HCT 12.1.01 device path exerciser, Windows fails after reboot.
Problem Resolution: free the receive input buffer if a failure occurs during "open" processing.
3.3.1 Bug 1216: V4.18 Cable Modem drivers fail HCT 12.0
Problem Description: The parameters passed in for certain IOCTLs are not validated.
Problem Solution: Ensure that parameters are validated for all IOCTLs.
Effect on Applications: Passing an illegal IOCTL parameter to the driver will cause a failure
status to be returned to the application.
- 20 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
None.
Most customer releases of MCCI USB drivers also include InstallRight Pro, which simplifies
installation and removal of the drivers.
V4.10 drivers included InstallRight V1.8; V4.18 and V4.20 included InstallRight Pro V1.11; V4.22
and V4.24 include InstallRight Pro V1.26.
Please be aware that version numbers for InstallRight Pro do not follow MCCI’s usual
numbering convention. In particular, V1.8 is prior to V1.11, because 8 is < 11 (even though 1.8 >
1.11). The numbering scheme will be changed in a future release.
Because InstallRight Pro is a separate product from the base drivers, it is often updated
independently. You may have a later version in your release. Please contact your MCCI
support office for updated information.
4.1 Setup
4.1.1 Prevent setup.exe from copying useless inf files on Windows 2000/XP
Problem Description: Windows 2000 and Windows XP generate Unsigned Driver warnings.
This can be reduced if some of the files are not necessary to install.
Solution: Setup.exe searches valid inf files in preparation for driver installation. Setup.exe
decides that an inf file is NOT valid if:
Problem Description: The common.addreg entries in the inf file are not installed for a customer
brand. This caused a driver workaround for a firmware bug to not be enabled.
- 21 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Effect on Devices: A driver workaround for a firmware bug is now installed and enabled.
Problem statement: USB devices with serial numbers result in multiple instances in the registry.
Therefore, in production test, it is preferable to ignore the serial numbers. Existing MCCI
drivers have an ‘-ignore_serialnum’ command line switch.driver that can be used for
manufacturing & testing. A customer requested additional support.
Problem solution (V1.12): setup (the installer) has been modified to detect the need to ignore the
serial number via new mechanisms. First, means have been added so that any command line
switch, including ‘-ignore_serialnum’, can be added to driver branding information. Second,
setup will check if any of the driver inf files that will be installed has "InstallOptions" string
value. In this case, if any of xxxxbus.inf, xxxxmdm2.inf or xxxxsdm2.inf has InstallOptions =
"IgnoreHWSerialNumber" string value on Win2K/XP, setup will act as directed by the ‘-
ignore_serialnum’ command line switch.
4.1.4 Bug 1188: Automatic post-installation fails on some Windows 98 family systems
4.1.5 Bug 1192: Setup.exe does not copy .cat files to a harddisk folder
Problem Statement: Setup did not copy the .cat (catalog) files. This generates unsigned driver
warnings on signed drivers.
- 22 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
Problem Solution (V1.16): Setup.exe was modified to copy .cat files if they exist and are declared
in CatalogFile= directives in inf files.
Problem Solution (V1.18): Setup upgraded to support Windows Server 2003 family.
4.1.7 Bug 1224: Setup.exe couldn’t find proper install path on Spanish Windows.
Problem Solution (V1.20): Setup will read the string value "ProgramFilesDir" from the registry
under HKLM\Software\Microsoft\Windows\CurrentVersion.
Problem Statement: Setup ignored handle CatalogFile.nt entries, which could result in unsigned
drivers warnings.
4.1.9 Bug 1268: Setup.exe uses CatalogFile entry in Version section on Win98
Problem Statement: Setup.exe did not handle CatalogFile entry in Version section on Windows
98. This would cause Windows 98/SE/ME to complain to that user looking for catalog files.
- 23 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
4.1.10 Bug 1271, Reduce end-user confusion from Bug 1268 fix
Problem Statement: The solution for Bug 1268 would work the first time, but it may cause
subsequent component installs to fail, or will cause the user to be prompted for the CD,
particularly if the user has installed from CABs on the hard disk.
Problem solution (V1.24): The change for Bug 1268 was removed. Setup will comment out
CatalogFile directives in all inf files during pre-installation.
Implementation:
1) User can append a command that prevents installation on specific Windows versions:
“NotInstallOnWin[98|98se|98vers|me|ver4|2k|xp|serv2003|ver5]” to McciOptions
string value(s) in the driver INF.
2) User can use a command line switch to prevent installation on specific Windows
version: “-ensure_win[98|98se|98vers|me|ver4|2k|xp|serv2003|ver5]”.
4.2 xxxxUninstall
4.2.1 Bug 1121: Uninstall removes driver & INF files if called with –quiet
Problem description: XXXXUninstall.exe didn’t remove driver files and inf files under the
Windows directory if called with the -quiet parameter.
- 24 -
MCCI V4.34.2705 USB Driver Release Notes
Engineering Report 950252 Rev.K
1362 √ √ √ √ √ √ √ Start
modem status loop only when
needed by the protocol
1466
- 25 -