Device Compatibility Issues with Digi USB Ports USB-Based Parallel Ports Drivers which bypass the operating system's parallel port software interface (and insist on directly accessing chips on the motherboard) will not work with our USB parallel ports. Unfortunately, this is fairly common on Windows 95 and 98, which limits our compatibility with devices like ZIP drives, scanners, and some printers with enhanced software support. Tested Parallel Port-Based Devices The following devices have been tested with the parallel port on the AccelePort USB 2: Cannon BJC-240 Works fine; communicates bidirectionally HP LaserJet 6L PCL Works fine; communicates bidirectionally HP LaserJet IIP Works fine; standard Centronics Epson LQ/LX Dot Works fine; standard Centronics Matrix Epson Color Stylus Not compatible; driver requires chip level and Stylus Photo access HP 7xx/8xx Ink Jet Not compatible; driver requires chip level access Scanners Not compatible; drivers require chip level access ZIP Driver Not compatible; drivers require chip level access Notes: All tests have been on Windows 98 using the drivers on the Windows 98 CD. Windows 98 does not query our LPT port for Plug and Play printers, so the 1284 Compatible printers are not auto detected. USB-Based Serial Ports As with parallel devices, any software or driver which bypasses the operating system's native programming interface will fail with anything except the chips on the motherboard. This is fairly unusual for most programs that access serial ports, especially current versions of them. Overall, interoperability and compatibility with our USB-based serial ports should be very good to excellent. Unsupported Driver Features There are three features that not all of our USB devices support: DTR/DSR/DCD flow control (only AccelePort USB 2 supports it) RTS "toggle" (only AccelePort USB 2 supports it) TxContinueOnXoff (none of our devices support it) Below is a bit more information on each of these. DTR/DSR/DCD flow control This is basically using these signals INSTEAD of the RTS/CTS pair for hardware flow control. It's rarely, if ever, used today, and when "DTR flow control" needs to be supported by printers, it's typically done by using RTS/CTS flow control and simply routing the printer's DTR signal to our CTS instead of using the printer's RTS signal (not used in this DTR flow control mode). In other words, by using a different cabling method. Simple. RTS "toggle" This is useful for those rare occasions where people are using devices such as HAM radio modems, where they have to make sure that RTS is asserted precisely before a data block transmission, and then immediately (in hardware) deasserted after the last byte is transmitted. In the HAM radio modem example, RTS is used to "key the microphone", which is why it is needed there. One can manually toggle RTS just fine, but the internal COM ports support a mode where this is done automatically; Digi USB serial ports don't. TxContinueOnXoff This one should have no effect on you. If this is set to TRUE, transmission is allowed to continue even when the input buffer is full and has told the remote device to stop transmitting (XOFF sent). If set to FALSE, then transmission can not continue until input is ALSO allowed to continue (after the input buffer empties some). Basically, there is no reason why transmission should have to stop just because your input buffer is full, at least with our products anyway, so we operate as if this were set to TRUE, and don't support setting it to FALSE (or ignore it if it is set to FALSE). Doing a Complete Uninstall of the Digi USB Driver Disconnect all of our units from the bus and do the following procedure to clean the system, reboot, and re-install the drivers. To clean up the registry: Open HKEY_LOCAL_MACHINE\Enum Delete DIGIBUS (if it's there). Open USB Delete all subkeys starting with VID_05C5. Open HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class Open Ports, go through all subkeys, delete each one with PortDriver being dgusb0.vxd. Open USB, go through all subkeys, delete each one with ProviderName equal to "Digi International". Start Windows Explorer, open \Windows\Inf\Other (actually should be %WINDIR%\inf\other, depending on what windows directory is), delete all files beginning with "Digi InternationalDGUSB". Then also go into the \Windows\System directory and remove all files that begin with dgusb (dgusb*.*). Reboot the machine. Plug the USB module in, and start over. Windows 95 Issues If you are using Windows 95 OSR2.1 with our products, it is strongly recommended that you use version 4.03.1214 or later of the Microsoft USBD.SYS file (in the system directory). To find out which version you currently have installed, right click on the file, select "Properties..." from the pop-up menu, and then select the "Version" tag. If the version indicated is 4.03.1214, you have the latest version as of this writing. Version 4.03.1212 was buggy and should be avoided.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.