CWUSBD.SYS: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 5: | Line 5: | ||
* /V - Verbose, show some information while booting. | * /V - Verbose, show some information while booting. | ||
* /I13 - Could be used to delay USB host overtaking by USB driver stack until other device driver finishes required initialization operations and then send request to USBD driver to start USB service. It could be used to boot from USB floppy drive. | * /I13 - Could be used to delay USB host overtaking by USB driver stack until other device driver finishes required initialization operations and then send request to USBD driver to start USB service. It could be used to boot from USB floppy drive. | ||
* /REQ - This parameter | * /REQ - This parameter controls USBD driver initialization: driver at initialization time checks for listed host controller drivers and fails to install if none of listed drivers is loaded. Current version of USB stack supports the following parameter codings: | ||
**/REQ:USBUHCD$ | **/REQ:USBUHCD$ | ||
**/REQ:CWUSBUHC$ USBD driver is loaded only if UHCI compliant host driver is loaded | **/REQ:CWUSBUHC$ USBD driver is loaded only if UHCI compliant host driver is loaded | ||
**/REQ:USBOHCD$ | **/REQ:USBOHCD$ | ||
**/REQ:CWUSBOHC$ USBD driver is loaded only if OHCI compliant host driver is loaded | **/REQ:CWUSBOHC$ USBD driver is loaded only if OHCI compliant host driver is loaded | ||
**/REQ:USBUHCD$,USBOHCD$,CWUSBOHC$,CWUSBUHC$ - USBD driver is loaded only if one of OHCI/UHCI compliant host drivers is loaded. This most general form of parameter and must be used in | **/REQ:USBUHCD$,USBOHCD$,CWUSBOHC$,CWUSBUHC$ - USBD driver is loaded only if one of OHCI/UHCI compliant host drivers is loaded. This most general form of parameter and must be used in most cases. | ||
most cases. | |||
{{ProdS |V30=C|V31=C|V40=C|V45=C}} | {{ProdS |V30=C|V31=C|V40=C|V45=C}} | ||
[[Category:BASEDEV Statements]] | [[Category:BASEDEV Statements]] | ||
Latest revision as of 02:32, 23 September 2022
Basic USB driver by Chris Wohlgemuth, based on the sources available on the DDK site. It does not have the feature set of the latest IBM driver downloadable with software choice. If you already have a (maybe better) working driver from there feel free to use that one.
BASEDEV=CWUSBD.SYS
Parameter
- /V - Verbose, show some information while booting.
- /I13 - Could be used to delay USB host overtaking by USB driver stack until other device driver finishes required initialization operations and then send request to USBD driver to start USB service. It could be used to boot from USB floppy drive.
- /REQ - This parameter controls USBD driver initialization: driver at initialization time checks for listed host controller drivers and fails to install if none of listed drivers is loaded. Current version of USB stack supports the following parameter codings:
- /REQ:USBUHCD$
- /REQ:CWUSBUHC$ USBD driver is loaded only if UHCI compliant host driver is loaded
- /REQ:USBOHCD$
- /REQ:CWUSBOHC$ USBD driver is loaded only if OHCI compliant host driver is loaded
- /REQ:USBUHCD$,USBOHCD$,CWUSBOHC$,CWUSBUHC$ - USBD driver is loaded only if one of OHCI/UHCI compliant host drivers is loaded. This most general form of parameter and must be used in most cases.
| Product Support | |
|---|---|
| OS/2 1.3 | |
| OS/2 2.0 | |
| OS/2 2.1 | |
| OS/2 2.11 SMP | |
| OS/2 Warp 3 | C |
| OS/2 Warp Connect | C |
| OS/2 Warp 4 | C |
| OS/2 Warp Server for e-Business | C |