OEMHLP2.SYS: Difference between revisions
Appearance
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
=== | {{ProdS |V30=S|V31=S|V40=S|V45=S}} | ||
PCI search functions driver used by OS/2 CardBus Enabler client. | PCI search functions driver used by OS/2 CardBus Enabler client. | ||
==Syntax== | |||
BASEDEV=OEMHLP2.SYS | BASEDEV=OEMHLP2.SYS | ||
==Remarks== | ==Remarks== | ||
Line 21: | Line 10: | ||
Additionally, this driver adds a write protection filter to a socket where an USB card is inserted. | Additionally, this driver adds a write protection filter to a socket where an USB card is inserted. | ||
==Links== | |||
* {{FileLink|CBEnable_2005-07-13.zip}} - (2005-07-13) | |||
[[Category:BASEDEV Statements]] | [[Category:BASEDEV Statements]] |
Latest revision as of 03:50, 8 August 2025
Product Support | |
---|---|
OS/2 1.3 | |
OS/2 2.0 | |
OS/2 2.1 | |
OS/2 2.11 SMP | |
OS/2 Warp 3 | S |
OS/2 Warp Connect | S |
OS/2 Warp 4 | S |
OS/2 Warp Server for e-Business | S |
PCI search functions driver used by OS/2 CardBus Enabler client.
Syntax
BASEDEV=OEMHLP2.SYS
Remarks
Some System BIOS do not scan on CardBus bus, if they are asked to look for a PCI device. Imagine that there would be a common PCI Chipset with drivers and no special CardBus client. if the device is present at boot time and the PCI driver uses the OEMHLP$ driver (included in OS2KRNL), chaning OEMHLP$ to OEMH2$ would let the PCI driver find the CardBus device. Of course you must make sure that the card is in the socket all the time.
Additionally, this driver adds a write protection filter to a socket where an USB card is inserted.
Links
- CBEnable_2005-07-13.zip - (2005-07-13)