USB ECD Class driver Introduction ============ The USBECD driver is a class driver that is intended to be a drop in replacement for Wim Brul's USBECD driver. This driver should be compatible with the original driver and any application that uses it. However, this driver is original code written completely from scratch and may have subtle behavior differences from the original driver. This driver has the following changes from the original: * Bug fixes * Protocol fixes * Fewer restrictions (no 64K alignment requirement) * 32 bit driver * Compatible with the modern ArcaOS USB stack * Does not emit beeps * Command parameters are not case sensitive * USB3 compatible * Resource Manager registration * Debugging capabilities * Supported by Arca Noae WARNING: Improper use of this driver can cause system-wide USB problems. Copyrights and Licensing ======================== Copyright (c) 2024 David Azarewicz All rights reserved. Copyright (C) 1992, 2000-2001 IBM Corporation. All rights reserved. Binary programs and documentation for the USB drivers are licensed to and distributed by Arca Noae, LLC. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement contained in the separate License.txt file, that you understand it, and that you agree to be bound by its terms. Installation ============ Add a DEVICE= statement to your CONFIG.SYS: DEVICE=c:\OS2\BOOT\USBECD.SYS where c: is your boot volume. You must reboot to active the driver. Then follow the directions as you would with the original USBECD driver. Uninstallation ============== Remove the DEVICE=c:\OS2\BOOT\USBECD.SYS (where c: is your boot volume) from your CONFIG.SYS. Getting Support and Reporting Problems ====================================== For more information and to report problems please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the USB support wiki at: https://www.arcanoae.com/wiki/usb/ Support from Arca Noae is limited to defects and potential enhancements in this driver only. Arca Noae cannot provide support for third party software even if used with this driver. Please consult the documentation you received with your software for instructions on getting support. Driver Command Line Options =========================== Option Description ------------------------------------------------------------------------------ /V Display informational messages during boot. /D::

: Specifies the usb device for this driver. is idVendor, the Vendor Identification.

is idProduct, the Product Identification. is bcdDevice, the Device Release Number. Must be specified with valid hexadecimal digits. The the wildcard character # may be specified in place of any digit. The default is ####:####:####. /N: Sets the name of the driver. Must be a valid device driver name that is unique. It must be different from all other driver names throughout your system. Must be between 1 and 8 characters. The default name is "$". /Q Ignored Additional debugging options useful with debug builds of the driver: /W Causes the debug buffer to wrap. The default is nowrap. /COM: Causes debug messages to be output to the specified serial port. 1=0x3f8, 2=0x2f8, 0xnnnn specifies the COM port base address. /BAUD: Sets the serial Port to the specified speed. Only valid if /COM is specified first. /CRD Changes a DosRead operation to return debug buffer data instead of device data. Example: DEVICE=C:\OS2\BOOT\USBECD.SYS /D:046D:0804:#### /N:$LTC250$ Additional Notes ================ You may use several instances of this device driver for various usb devices. All of these instances need to have a different device driver name specified. The driver will attach to the first device it sees that qualifies according to the specification provided by the /D parameter. The default for /D is ####:####:#### so if /D is not specified, the driver will attach to the first device it sees. This could be any device depending on the enumeration order. The enumeration order can vary from system to system and from boot to boot. You can determine which device is attached to this driver by examining the Resource Manager data with the rmview command. Try "rmview | grep ECD". The Hardware Manager can also be used, but beware that it does not always show the true status of connected devices. It is possible to attach to a device already being served by another driver. This may have undesired effects, including device malfunctions. If you specify the /CRD switch, you can use 'type ', where is the name specified by the /N: parameter, to see information about the attached device. All values are in hex. Examples: type $ type $LTC250$