-->
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.
USB 2.0 Easy IDE Driver. Topics usb, ide, driver. Driver for some USB 2.0 to IDE adapter. Addeddate 2017-08-18 06:31:49 Identifier 405REasyIDE Scanner Internet Archive HTML5 Uploader 1.6.3. Plus-circle Add Review. Reviews There are no reviews yet. Be the first one to write a review. » e manage 2 usb device driver download » usb driver exe usb driver » usb driver qualcomm usb driver » acer usb charge manage 下载 » acer usb charge manage » driver hp connectio manage » tablet driver with macrokey manage » one safe driver manage » baixa o driver da motorola manage 2.4.5 » onesafe driver manage. Jan 15, 2016 Greddy E Manage Ultimate Usb Driver Downloads. Show: 1 2 Freeware; 1. ADC Instruments USB Driver 2.4 (adcmt.com) Installing and Uninstalling the ADC Instruments USB Driver. This Software is a device driver that is used to control test and measurement instruments, which are made by ADC Corp., from a PC through a USB interface.
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
E-manage2 Usb Device Driver
Certification/ComplianceAttend Power Delivery and USB Type-C compliance workshops hosted by the standards bodies.
See also
DOS USB Drivers
There are several ways folks are getting their USB CDroms, Hard Drives, and other drives to work in DOS. One is using what's known as DUSE driver system. The second method is using what looks somewhat like standard CDrom driver files and a USB driver. Both methods appear to require loading an usbaspiX.sys file first in config.sys in most cases. The third method is a bootdisk from a USB vendor. Method 4 is getting good reviews also.
METHOD 1 - The DUSE System
Example 1 Using DUSE
[config.sys]
device=a:himem.sys
devicehigh=a:emm386.exe
device=a:usbaspi.sys
dos=high,umb
Note: You can find a usbspi.sys on the internet or use on of the five different versions I've found in the Download Files section at the bottom of the page
[autoexec.bat]
@echo off
duseldr a:duse.exe
MSCDEX /D:USBCDROM /S /M:15 /V
Example 2 Using DUSE
[config.sys]
device=a:himem.sys
DEVICE=a:duse.exe
[autoexec.bat]
MSCDEX /D:USBCDROM /S /M:15 /V
METHOD 2 - The usbaspi.sys/usbcd.sys System - Example 1
As noted, this method seems just like loading IDE drivers, with the added entry of the usbaspiX file. The following are the relevant portions taken from a modified config.sys and autoexec.bat file which was designed to work with a Windows 98 OEM Bootdisk with the ramdrive.
The complete config.sys and autoexec.bat replacement files are available for download below, and you might want to start first with just copying them to your OEM bootdisk along with the relevant drivers and then experiment later with getting them to work on your Customized disk.
[config.sys - example 1]
device=himem.sys /testmem:off
device=usbaspiX.sys
device=usbcdX.sys /D:mscd001
Emanage 2 Usb Device Driver Failed To Install
[config.sys example 2 - USB Floppy in only port, 'sometimes' allows switching to CDrom after boot]
device=himem.sys /testmem:off
device=ramfd.sys
device=usbaspiX.sys /W
device=usbcdX.sys /D:mscd001
[autoexec.bat]
LH %ramd%:MSCDEX.EXE /D:mscd001 /L:%CDROM%
METHOD 2 - The usbaspi.sys/usbcd.sys System - Example 2
'I finally got my Belkin external drive enclosure with a WD 120gb drive to work in DOS, and then perform a GHOST image', wrote don b. 'Here's the files and config.sys that worked.'
[config.sys]
device=himem.sys /testmem:off
devicehigh=usbaspi1.sys
devicehigh=di1000dd.sys
devicehigh=usbcd2.sys /d:USBCD001
LASTDRIVE = Z
[autoexec.bat]
don b. noted that either the standard Ghost or Win98X autoexec.bat worked as is.
METHOD 2 - The usbaspi.sys/usbcd.sys System - Example 3
Herbert H. writes: 'I Just solved my problem by using the files from the 'virtual' DOS drive ghost03 makes when you run interactive mode. It uses IOmega USB drivers and Guest.exe. It alowed me to use my Western Digital external USB HD in DOS.
[config.sys]
LASTDRIVE=Z
DEVICE = usbaspi4.sys /int /all
DEVICE = usbaspi5.sys /int /all
DEVICE = usbaspi5.sys /int /all /D1
DEVICE = usbcdX.sys /D:cd2
DEVICE = OAKCDROM.SYS /D:cd1 [For his IDE CDrom]
METHOD 3 - The datoptic System
A USB 4 DOS bootdisk has been posted here called dat.exe
The key driver files in dat.exe include:
usbaspi.sys 37,090 bytes
nj32disk.sys 15,808
sbp2aspi.sys 28,836
datoptic.com recommends the following config.sys for it's USB/1394 products. It's been reported tho that their drivers also work for other brands as well.
[menu]
menuitem=USB,USB Boot
menuitem=1394,1394 Boot
menudefault=USB,30
menucolor=7,0
[USB]
DEVICE = USBASPI.SYS
[1394]
DEVICE = SBP2ASPI.SYS
[COMMON]
DEVICE = NJ32DISK.SYS /R
LASTDRIVE=Z
METHOD 4 - The Iomega Way
Ben B. wrote:
I built a boot disk to access a USB external hard drive from DOS using drivers included with Norton Ghost. 2003. Since Ghost can write to the external drive in DOS, I figured I could copy its drivers. Turns out they are from Iomega. I wanted to access the external drive to run a disk wiping program. Autoexec.bat and Config.sys can be much improved, but this is the bare bones of the boot disk. Note that the Iomega drivers will work with any USB external hard disk and are not proprietary to Iomega drives (mine is a Western Digital).
Config.sys:
DEVICE=aspiehci.sys /int /all
LASTDRIVE=Z
Autoexec.bat:
@echo off
GUEST.EXE
Contents of my boot disk:
aspiehci.sys [Iomega USB 2.0 driver]
Autoexec.bat
Command.com
Config.sys
guest.exe [Another Iomega program required to access the USB drive]
Io.sys
Msdos.sys
Thanks Ben. Your letter has enough information tho to put folks on the right track to find the drivers themselves. If folks want to save some time tho they can get the drivers here.
+++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++
DOWNLOAD FILES:
DUSE 4.4DUSE 4.9 With Excellent Docs
Dell Usb Device Driver
The USBdrivers collection includes 5 different usbaspi.sys and 2 usbcd.sys files, the iomega drivers, the ramfd.sys driver, and the modified Win98 OEM config.sys and autoexec.bat files. You will have to experiment to see which one works for you.
The key driver files I've put together for you in the [USBdriver] collection include:
ramfd.sys 22,012 bytes
usbaspi1.sys 39,093
usbaspi2.sys 43,528
usbaspi3.sys 37,090
usbaspi4.sys 49,242
usbaspi5.sys 50,606
E Manage 2 Usb Device Driver Updater
usbcd1.sys 5,509
usbcd2.sys 35,456
di1000dd.sys 16,368
Iomega:
aspiehci.sys 52,106
aspiehcj.sys 49,772 [renamed - older version of aspiehci.sys]
aspiohci.sys 42,242
aspinhci.sys 50,606
guest.exe 8.5 32,396
Please keep in mind that DOS USB CDrom/HDD/zip/etc. drivers is a brand new and developing area so there is no one single method that is guaranteed to work on every PC. If you try a few methods and have no luck, keep at it and dont worry as I'm confident there is enough information here to get at least 99% of the USB drives to work in dos.
A related article from theinquirer.net
Note that the files referred to in the article are included in my usb driver file download.
+++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++
Note that the files posted here are pretty much the most complete collection of USB drivers around. Oddly enough, if you have a USB floppy drive connected to your PC some of these cdrom/hard/zip drive drivers will fail to load or the above bootdisk will fail to work.
In fact, I'd remove ANY USB device you dont need [eg cams, mice, printers, etc.] when using the above files to get DOS access to your Drives.
Note that after you get your business done in DOS with the USB drivers that they really should be remmed out when you've done what you needed to and now want Windows to use the drive correctly using Windows drivers.
Also note that windows really doesn't like being installed from a usb device so if you only have a usb cdrom drive and need to install windows its best to copy the install files to a folder on your hard drive first and do the install from there. For example, if you are using win9X then make a folder on your hard drive called win98 and copy the files from the win98 folder on the cd to c:win98 then run setup from there.
Emanage 2 Usb Device Driver Download
If using XP then make a folder on your hard drive called i386 and copy the files from the i386 folder on the cd to c:i386 and run winnt.exe from there.
Please keep in mind that this is a new/developing area and I'm doing the best that I can in providing you with the info as it comes in so you are going to have to do some tweaking in the meantime.
+++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++
TESTIMONIALS
From jorj:
I unpacked the zipped file usbdrive.zip on my desktop. Then I looked in it and noticed there are [5] usbaspi.sys and 2 usbcd.sys files. Randomly I took usbaspi1.sys and usbcd1.sys and placed them into win98 startup cd, together with the autoexec.bat and config.sys files, which repalced the original bat/sys files on the startup disk. Then I ran the startup disk and watched the screen. It worked right from the start.
From obiwan
I use your bootdisk site often and your resources have bailed me out on several occasions. I recently set up USB support on some ghost boot disks that we use here and was excited to say the least. It worked on both the Plextor USB CD-ROMS and a Pioneer CD-ROM I have in an ADS USB enclosure. Thanks for the great site and keep up the great work.
From B. K.
Thanks for your excellent website - I just figured out how to read a USB CD drive from DOS solely because of your excellent advice.
From Daniel, Ottawa
I just purchaced a USB 2.0 Drive Kit at COSCO. I placed an IDE hard drive in it with all the images of PCs that I GHOST on a regular basis. Thanks to all the info provided on your website, I can now boot in DOS with USB support. I then run my GHOST floppy, and choose the correct image from the 'USB Hard Drive'. I no longer need multiple CDs... I no longer have to change CDs every 5 minutes for a full hour... I no longer have to burn tons of CDs... Thank you for your great website!
From Angelos
USB to Dos drivers, finally work. After many hours and attempts, I have managed to mount my SuperTalent External HD using the DUSE 4.9 driver found on this excellent site. The Ghost 2003 and DUSE 4.9 fit on a floppy so now I can image my HD my friends HD and so on. Thank you bootdisk you are the greatest.
E Manage 2 Usb Device Driver Download
From Carmen (Spain)
I just want to say thanks to ben b. for sharing his experience. I was able to find the files I needed on the Internet and got my usb hard drive to work which did not come with dos drivers.
From A Gorman (UK)
This site is excellent. Downloaded dos usb drivers and it works great.
From Wim (Holland)
Thanks to [this page] I got my Xterasys - USB 2.0 casing with a WD 80 gig HD, to boot from a DOS bootable floppy disk. Instead of loading the DEVICE=aspiehci.sys /int /all from config.sys [ie the Iomega driver Ben B. used], I loaded DEVICE=ASPIOHCI.SYS /int /all, also a Iomega driver. It works GREAT!!!!