USB 2.0 für DOS: Zusammenfassung der im Beitrag von Brummelchen genannten USB 2.0 - DOS - Treiber Quellen und Downloads. Bitte die jeweiligen Lizenzbestimmungen beachten .
Inhaltsverzeichnis
A. Abkürzungen
:
A. Abkürzungen
K= Konfiguration Startdateien Q= Quelle CL= Change Log DL= Download
B. Changelog
:
B. Changelog
CL 00 - 01.09.2009 : USB 2.0 für DOS - Complete Refresh
C. Quellen - Übersicht
:
C. Quellen - Übersicht
Q 01 - Langa Newsletters : USB for DOS
Q 02 - 3D Chips Net
Q 03 - Information Week - USB-To-Whatever
Q 04 - Information Week : The Perfect Rescue Tool
Q 05 - Darkehorse - PC DOS Drivers USB
Q 06 - The Inquirer - Yes, there are USB drivers for DOS
Q 07 - USB-Drivers.com
Q 08 - Interesting DOS programs
Q 09 - Computing Net - USB Storage in DOS
Q 10 - USBMan - USB Downloads - Links - Tutorials
Q 11 - BootDisk.com - DOS USB Drivers
Q 12 - Uwe Sieber - Tools und Utilities für Windows und DOS
Q 13 - Avira - Kostenfreie Tools
Q 14 - Bret Johnson - DOS USB Drivers
Q 15 - Nnewdos Yginfo.net - USB Support for DOS
Q 16 - Windows OS Installation via AddOnics USB Drive
Links
Q 03 - Information Week - USB-To-Whatever
Q 04 - Information Week - The Perfect Rescue Tool, Parts I and II
Q 05 - Darkhorse - PC DOS Drivers USB
Q 06 - The Inquirer - Yes, there are USB drivers for DOS
Die Reihenfolge der USB-Treiber bewirkt, dass zuerst USB 1.0 neu, dann USB 1.0 alt und dann USB 2.0 durchprobiert wird... So ist eine größtmögliche Kompatiblität sichergestellt...
This boot diskette supposedly supports Firewire and USB Iomega ASPI devices. I have not tested this diskette so use at your own risk.
Diese Boot Diskette unterstützt vermutlich Firewire und USB Iomega ASPI Geräte. Diese Diskette wurde von mir nicht getestet - Verwendung auf eigene Gefahr.
Another USB CD ROM Driver. A visitor told me about this and said he was able to use Ghost and this driver to backup his hard drive to a CD-RW. Add a device reference to this driver (device=usbaspi.sys) in your config.sys and then run MSCDEX or SHSUCDX in autoexec.bat to bind the driver.
Ein alternativer USB CD ROM Treiber. Ein Besucher berichtete, daß es ihm gelungen sei, ein Backup seiner Festplatte unter Verwendung von Ghost und diesem Treiber auf CD-RW zu erstellen.
Fügen Sie in der Config.Sys eine Geräte Referenz zu diesem Treiber hinzu (device=usbaspi.sys) und starten dann MSCDEX oder SHSUCDX in der Autoexec.Bat.
Recently updated this disk to include DUSE 4.4!
A Windows 98 Bootdisk I made using the DUSE.EXE driver below. I created this diskette for those folks having troubles getting DUSE to work with their USB CDROM drives. Download and double click this program to create the diskette
Diese Windows 98 Bootdisk enthält den Duse 4.4 Treiber und ist für diejenigen Benutzer gedacht, die Schwierigkeiten haben ihre USB CD Rom Laufwerke mit dem DUSE Treiber anzusprechen.
Version 4.4 of DUSE.EXE now supports USB 2.0!; WOW! What a great find. This 'universal' device driver will work with USB Zip Drives, Hard Drives, CD-ROM drives, floppy drives and something called MO drives. I was actually able to read the contents of my USB CD-RW disk with this driver. Read the instructions included with the package.
Version 4.4 der DUSE.EXE unterstützt nun den USB 2.0Standard. USB Zip Laufwerke, Festplatten, CD ROM Laufwerke, Floppy Disk Laufwerke und MO Laufwerke arbeiten mit diesem "universellen" Treiber zusammen. Beachten Sie die im Download Paket enthaltenen Hinweise.
The driver switches you can use are:
device=(path)\USBASPI.SYS [/e] [/o] [/u] [/w] [/v] [/l[=n]] [/f] /r] [/slow] [/nocbc] [/norst] [/noprt]
The driver scans all three USB controller specs by default, but you can limit which controllers are enabled using these switches:
/e EHCI spec (USB 2.0)
/o OHCI spec (newer USB 1.x)
/u UHCI spec (older USB 1.x)
And so far I learned what these switches mean:
/w Wait, displays text message for attaching or swapping USB devices
/v Verbose, shows status messages - recommended
/l[=n] LUN, specifies highest LUN to be attached to device ID (default=0)
Example config.sys and autoexec.bat files on a DOS boot diskette with USB support for an usb cd-(rom/rw) and hard disk look like this:
[config.sys]
DOS=HIGH,UMB
lastdrive=Z
device=HIMEM.SYS
rem The following line loads Panasonic's universal USB- controller driver
devicehigh=USBASPI.SYS /v /w /e
rem the following is an aspi mass storage driver for usb- connected HDs and compactflash memory cards
devicehigh=DI1000DD.SYS
rem The following one loads CD-ROM driver
devicehigh=USBCD.SYS /d:USBCD001
[autoexec.bat]
@echo off
REM the following line adds a drive letter to the usb cd(rom/r/rw) mounted
LH MSCDEX /d:USBCD001
The Panasonic driver also seems to recognise some TI cardbus controllers, making it possible to use USB peripherals attached to USB (even 2.0!) Cardbus cards.
The USBASPI.SYS Panasonic(TM) USB to ASPI driver v2.06 Reference
Japanese files for a startup disk creation tool for their various USB optical drives on popular Japanese portables. USBASPI.SYS is extracted from the F2H subdirectory, and is tested compatible with English version DOS.
The USBASPI.SYS driver is also available from these links:
( These are Windows self-extracting file format for Panasonic driver files for different OEM drives )
UHCI/OHCI (USB 1.x) and EHCI (USB 2.0) Support
With a USB CD-ROM Driver, it allows USB optical drives (like DVD-ROM, CD-ROM drives, and (re)writers) to be used in DOS after MSCDEX extensions are loaded.
Here are the known valid switches identified so far with the Panasonic(TM) v2.06 USBASPI.SYS driver in CONFIG.SYS :
You can specify more than one controller type (e.g. /e /u).
This switch can also be used to force slower speed operation on high-speed USB controllers & devices.
The driver will scan for all types of USB controllers, so use these switches to specify which port types to enable.
This allows for faster USB scanning.
By specifying /u or /o and omitting /e, it forces Full-Speed mode on High-Speed devices.
But a Low-Speed (LS) or Full-Speed (FS) device cannot be made to run at High-Speed (HS).
/e
EHCI, for enabling only USB 2.0 controller
/o
OHCI, for enabling only add-on/onboard USB 1.1 controller
/u
UHCI, for enabling integrated USB 1.1 controller
In verbose mode :
USBASPI displays details on controller type and USB devices it detects.
It displays the vendor & product ID codes, the controller address range (memory map or I/O port map) of controllers, and the connection speed code for each device.
/v
Verbose, shows USB details - excellent troubleshooting tool
These switches modify driver actions
/w
Wait, displays prompt message to allow swapping/attaching of target USB device
/l#
Luns, to specify highest number of LUN assigned, default /L0
/slow
to enter SLOW down mode, gives longer delays when scanning USB devices
/nocbc
for NO Card Bus Controller, to disable detection of USB on CardBus slots
/norst
for NO ReSeT, this is useful when legacy USB devices (e.g. a USB keyboard or mouse) had been pre-initialized by the BIOS so by preventing a USB reset, these devices would still function after USBASPI.SYS has loaded.
This switch is typically used on portable systems with an external USB floppy drive connected to the single USB port for boot-up.
Used in conjunction with RAMFD.SYS so after the boot floppy is copied to a RAM drive, (and after the /W pause...) the USB floppy can be removed, and the target mass storage device can be attached and detected
/r
Resident, allows driver to stay resident in memory when USB floppy drive is detected.
There are a number of switches whose specific function is still unknown. Please post your discoveries in the USBMAN end-user forum, or the Computing.Net DOS forum.
/noprt
Have found that on some systems with USB on Intel chipset (1.1 or 2.0), if UHCI is normally I/O mapped, using this switch causes USBASPI.SYS to "hang" while detecting host controllers. Could it be to force I/O port addressing mode?
/f
/p=xxxx
As per F2H documentation, this sets the I/O port address, but have been unable to get this to work on standard desktops. Could it be for CardBus?
K 04 - Konfigurationen
K 04.1
Enable only the high-speed USB controller and the mass storage drive:
K 06 - 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
[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
K 06.1 - 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.
K 06.2 - 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.
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.
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).
DL 23 - Bret Johnson - Complete Set of USB Drivers
DOS USB Drivers enthalten einen kompletten Satz DOS USB Treiber für Keyboard, Tastatur, Maus, Drucker, Festplatten Laufwerke, Hubs und einige Test Programme.
Aktuell werden UHCI Treiber unterstützt -
Support für OHCI, EHCI, WHCI, XHCI Treiber und Geräte soll in den kommenden Versionen noch folgen.
DL 24 - Bret Johnson - DOS TSR Programs
DOS TSR (Terminate but Stay Resident) beinhalten alle weiteren DOS Tools von Bret Johnson - Download einzelner Tools ist jedoch auch möglich.
DL 25 - Nnewdos Yginfo.net - Downloads
Alle Original Downloads und Ergänzungen
Duse Drivers
DUSE is a half-universal yet full-featured USB Mass Storage driver for DOS, which support USB Hard Drives, USB Floppy Drives, USB CD Drives, USB ZIP Drives, and USB MO Drives.
Example:
DEVICE=<path>DUSE.EXE INT XFER=32 DRIVES=2 CDD=USB-CD
Duse Downloads
Duse - Version 4.2
Duse - Version 4.3
Duse - Version 4.4 --- siehe auch DL 18 - Q 11
Duse - Version 4.9 --- siehe auch DL 19 - Q 11
SCSI drivers
In order for SCSI/ASPI devices to work under DOS, the corresponding SCSI/ASPI drivers must be loaded. SCSI drivers consist of two parts: the specific driver for the SCSI controller and the universal driver for the SCSI device. As the matter of fact, the USBASPI or ASPI?HCI driver above is the former part of the SCSI drivers. Thus, once USBASPI or ASPI?HCI is loaded successfully, you need a universal SCSI driver for that device to really work. For USB/SCSI CD drives to work properly under DOS, MSCDEX must be loaded after the corresponding CD driver.
Drivers for SCSI Hard Drives - Download:
DI1000DD.SYS
ASPIDISK.SYS
Drivers for SCSI CD Drives - Download:
USBCD.SYS
ASPICD.SYS
More drivers - Download:
GUEST.EXE
RAMFD.EXE
USBASPI
USBASPI is a "universal" driver for many different USB Mass Storage drives with different chipsets, such as Intel, VIA, NVIDIA, Ali and SiS chipsets. Especially USB Flash drives should work fine with this driver. But note that this driver is actually a "converter", i.e. Convert USB devices to SCSI/ASPI devices, so you also need to load some universal SCSI/ASPI driver after USBASPI in order for the devices to work correctly.
Example:
DEVICE=<path>USBASPI.SYS /R /V
USBASPI - Downloads:
USBASPI V 1.07
USBASPI V 2.01
USBASPI V 2.06
USBASPI V 2.15
USB 2.0 für DOS : Zusammenfassung
Linear-Darstellung
