Achieveressays.com is the one place where you find help for all types of assignments. We write high quality term papers, sample essays, research papers, dissertations, thesis papers, assignments, book reviews, speeches, book reports, custom web content and business papers. These drivers are 100% compatible with all USB 1.1 devices as well. Please read the included README file for the latest technical enhancements and limitations of these drivers. Supported operating systems: Adaptec's USB 2.0 drivers support Microsoft Windows® 98 Second Edition,Windows 2000, Windows Millennium Edition and Windows XP operating.
Administration - Office area with one or more desktop computers, LCD monitors, peripherals and office equipment. Back Office - 1-3 racks with servers, network hardware and telecommunications systems. ROADHUG SPRINGS & MACHINERY PTY LTD - Tel. No.: 03 -.8322 4/6 Fowler Road Dandenong South Vic 3175 BRAND NEW ESTER - Portable, Digital Hardness Tester Part No.: Q520 Code No.: 39 Part No.: Q520 Shipping weight & size: Description 50-520 - Portable, Digital Hardness Tester HRB, HRC, HRA, HV, HB, HS, HL Overview The 50-520 is an advanced Leeb type portable hardness tester with a wide. Oneprox™USB Office Admin KitIn addition to the enrollment capability, a PAC 512 Line Driver provides extended direct communications between the Host PC and the nearest convenient PAC 512 Two-Door Controller which can be located up to 1,000ft away, typically using 22-4 unshielded cable.
-->This topic is intended for OEMs who want to build a Windows 10 system with USB Type-C connector and want to leverage OS features that allow for faster charging, power delivery, dual role, alternate modes, and error notifications through Billboard devices.
A traditional USB connection uses a cable with a USB A and USB B connector on each end. The USB A connector always plugs in to the host side and the USB B connector connects the function side, which is a device (phone) or peripheral (mouse, keyboard). By using those connectors, you can only connect a host to a function; never a host to another host or a function to another function. The host is the power source provider and the function consumes power from the host.
The traditional configuration limits some scenarios. For example, if a mobile device wants to connect to a peripheral, the device must act as the host and deliver power to the connected device.
The USB Type-C connector, introduced by the USB-IF, defined in the USB 3.1 specification, addresses those limitations. Windows 10 introduces native support for those features.
Feature summary
- Allows for faster charging up to 100W with Power Delivery over USB Type-C.
- Single connector for both USB Hosts and USB Devices.
- Can switch USB roles to support a USB host or device.
- Can switch power roles between sourcing and sinking power.
- Supports other protocols like DisplayPort and Thunderbolt over USB Type-C.
- Introduces USB Billboard device class to provide error notifications for Alternate Modes.
Official specifications
Hardware design
USB Type-C connector is reversible and symmetric.
The main component are: the USB Type-C connector and its port or PD controller that manages the CC pin logic for the connector. Such systems typically have a dual-role controller that can swap the USB role from host to function. It has Display-Out module that allows video signal to be transmitted over USB. Optionally it can support BC1.2 charger detection.
Consider recommendations for the design and development of USB components, including minimum hardware requirements, Windows Hardware Compatibility Program requirements, and other recommendations that build on those requirements.Hardware component guidelines USB
Choose a driver model
Use this flow chart to determine a solution for your USB Type-C system.
| If your system... | Recommended solution... |
|---|---|
| Does not implement PD state machines | Write a client driver to the UcmTcpciCx class extension. Write a USB Type-C port controller driver |
| Implements PD state machines in hardware or firmware and support USB Type-C Connector System Software Interface (UCSI) over ACPI | Load the Microsoft provided in-box drivers, UcmUcsiCx.sys and UcmUcsiAcpiClient.sys. See UCSI driver. |
| Implements PD state machines in hardware or firmware, but either does not support UCSI, or support UCSI but requires a transport other than ACPI | Write a client driver for the UcmCx class extension. Write a USB Type-C connector driver Write a USB Type-C Policy Manager client driver |
| Implements UCSI but requires a transport other than ACPI | Write a client driver to the UcmUcsiCx class extension. Use this sample template and modify it based on a transport that your hardware uses. Write a UCSI client driver |
Bring up drivers
USB Function driver bring-up is only required if you support USB Function mode. If you previously implemented a USB Function driver for a USB micro-B connector, describe the appropriate connectors as USB Type-C in the ACPI tables for the USB Function driver to continue working.
For more information, see instructions about writing a USB Function driver.
USB Role-Switch driver bring-up is only required for devices that have a Dual Role controller that assumes both Host and Function roles. To bring-up the USB Role-Switch driver, you need to modify the ACPI tables to enable the Microsoft in-box USB role-switch driver.
For more information, see the guidance for bringing up the USB Role Switch Driver.
A USB Connector Manager Driver is required for Windows to manage the USB Type-C ports on a system. The bring-up tasks for a USB Connector Manager driver depend on the driver that you choose for the USB Type-C ports: The Microsoft in-box UCSI (UcmUcsiCx.sys and UcmUcsiAcpiClient.sys) driver, a UcmCx client driver, or a UcmTcpciCx client driver. For more information, see the links in the preceding section that describe how to choose the right solution for your USB Type-C system.
Test
Perform various functional and stress tests on systems and devices that expose a USB Type-C connector.
Test USB Type-C systems with USB Type-C ConnEx - Run USB tests included in the Windows Hardware Lab Kit (HLK) for Windows 10.
Run USB function HLK tests with a C-to-A cable (search for Windows USB Device in the HLK
Certification/ComplianceAttend Power Delivery and USB Type-C compliance workshops hosted by the standards bodies.
See also
-->This article provides a solution to an error that occurs when you insert a smart card in a reader.
Original product version: Windows 7 Service Pack 1, Windows Server 2012 R2
Original KB number: 976832
Symptoms
When you insert a smart card into a smart card reader, Windows tries to download and install the smart card minidrivers for the card through Plug and Play services. If the driver for the smart card is not available at any of the preconfigured locations, such as Windows Update, WSUS, or intranet paths, and a custom Crypto service provider is not already installed on the system, you receive the following error message in the notification area:
Device driver software was not successfully installed
Click here for details.
This error message disappears after several seconds.
Drivers Pac Usb Office Administration Kit Port Devices List
Additionally, in Device Manager, under Other devices, the Smart Card device has a status of DNF (Driver not found).
This frequently requires the user to obtain one of the following items from the smart card issuer to resolve this error:
- A Windows logged smart card minidriver.
- A custom cryptographic service provider (CSP) for the Smart card.
- A Windows non-logoed smart card minidriver.
- Other middleware such as an ActiveX control, PKCS#11 software, or other custom software.
However, if the user is provided with only item 3 or 4 from this list, the smart card continues to work on the system. However, the user will receive the error message that is mentioned in this section every time that they insert the smart card.
Drivers Pac Usb Office Administration Kit Port Devices Download
This issue affects all releases of Windows 7, Windows Server 2008 R2, and in later versions of both operating systems.
Cause
All smart cards require additional software to work in Windows unless there is an inbox driver that lets the user use the card without installing additional software. The Windows Smart Card Framework was improved in Windows 7 to enable the automatic downloading of smart card minidrivers from Windows Update or from other similar locations such as a WSUS server when the smart card is inserted into the reader. All smart cards that successfully pass the logo requirements, as published by the Windows Logo Program, benefit from this feature.
However, if the software that is required to use a smart card in Windows is not logoed or is of a type that differs from a minidriver, such as a PKCS#11 driver, a custom CSP, middleware, or an ActiveX control, the automatic download option fails because Microsoft certifies only smart card minidrivers. Therefore, if the user inserts a card for which a custom CSP is not already registered, the user receives an error message that states that the driver software is missing for the smart card device even though the user can use the smart card through additional software that was installed on the user's computer from a custom installation.
Resolution
Although the smart cards continue to work despite the error message that the user sees, a smart card issuer, vendor, or manufacturer can use one of the following methods to resolve this error.
Implement a smart card minidriver
We recommend that card issuers, vendors, and manufacturers implement smart card minidrivers and participate in the Windows Logo Program to benefit from the improvements that are introduced in the platform such as Smart Card Plug and Play, Device Stage for Smart Cards, and so on.
Implement a NULL driver for your smart card
If custom software such a PKCS#11 driver, an ActiveX control, or some other middleware is required to enable the use of smart card on Windows, and implementing a smart card minidriver or a custom CSP is not a practical option, we recommend that card issuers, vendors, or manufacturers consider submitting NULL drivers to Windows Update. The typical process for making sure that a NULL driver is available on Windows Update requires a successful unclassified device submission through Winqual. If in the future, there is a minidriver available for these cards, the new driver can be uploaded to Windows Update by participating in the Windows Logo Program. The NULL drivers can then be manually downloaded by the end users or can made available by using optional updates.
The following is a sample template for a NULL driver for a smart card.
To generate the hardware device ID that is referenced by the DEVICE_ID string in the sample, follow the instructions in the smart card minidriver's specification.
For detailed information about how to submit a NULL driver to Microsoft, please contact Microsoft Customer Support Services.
Disable Smart Card Plug and Play through Group Policy for managed computers
This option is recommended only for enterprise deployments where the computers are managed by administrators and all the necessary software to work with the smart cards that are being used in the enterprise is installed by using software management tools such as SMS.
This procedure is discouraged in the following environments because it will affect all the smart cards in your environment:
- Commercial deployments that target end-users, such as online banking.
- Environments that include both Plug and Play smart cards and non-Plug and Play smart cards that use Group Policy to disable Plug and Play for smart cards.
Smart Card Plug and Play can be disabled in enterprises where the end user's computer is managed by mechanisms such as Group Policy.
If your deployment uses only non-Plug and Play smart card solutions, Smart Card Plug and Play can be disabled by a local administrator on a client computer. Disabling Smart Card Plug and Play prevents smart card drivers, also known as smart card minidrivers, from downloading. It also prevents Smart Card Plug and Play prompts.
To disable Smart Card Plug and Play in local Group Policy, follow these steps:
Click Start, type gpedit.msc in the Search programs and files box, and then press ENTER.
In the console tree under Computer Configuration, click Administrative Templates.
In the details pane, double-click Windows Components, and then double-click Smart Card.
Right-click Turn on Smart Card Plug and Play service, and then click Edit.
Click Disabled, and then click OK.
Change the end user's system and disable Smart Card Plug and Play for specific cards
This is the least-recommended option. You should use this option only if the cards are legacy cards and there are no plans to implement smart card minidrivers in future. This option requires that the existing software that is already installed on the system notify Windows that there is a custom CSP installed on the system even though no such CSP exists on the end-user system. As soon as Windows determines that there is a custom CSP already installed on the system, Windows does not try to download and install a driver through Smart Card Plug and Play. No device node for the smart card device is created that is visible in Device Manager. This option results in the following changes to the system registry:
Subkey: HKEY_LOCAL_MACHINESOFTWAREMicrosoftCryptographyCalaisSmartCards<Smart card name>
Drivers Pac Usb Office Administration Kit Port Devices -
Subkey registry entries:
Drivers Pac Usb Office Administration Kit Port Devices Free
ATR=Hexadecimal DWORD: Comma delimited ATR of the smart card.
ATRMask= Hexadecimal DWORD: Comma delimited mask to apply to the ATR to mask out insignificant bytes in the ATR.
Crypto Provider=String value: Some string relevant to your smart card.
For example:
Subkey: HKEY_LOCAL_MACHINESOFTWAREMicrosoftCryptographyCalaisSmartCardsFabrikam ATM card
Subkey registry entries:
- ATR=Hexadecimal DWORD: 3b,dc,13,00,40,3a,49,54,47,5f,4d,53,43,53,50,5f,56,32
- ATRMask= Hexadecimal DWORD: ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff
- Crypto Provider=String value: Fabrikam ATM Dummy Provider
For x64-bit systems, identical changes must be made under the following subkey: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftCryptographyCalaisSmartCards
We recommend that, instead of directly changing the system registry, you use WinSCard APIs to introduce these changes to the system. Here is sample code example that detects smart card insertion and then disables Smart Card Plug and Play for the particular card by creating a registry entry that associates the card with a non-existing provider.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
References
For more information about troubleshooting smart card Plug and Play issues, see Smart Card Troubleshooting Guide.