Summary
PyFtdi aims at providing a user-space driver for popular FTDI devices, implemented in pure Python language. Suported FTDI devices include: UART and GPIO bridges. FT232R (single port, 3Mbps) FT230X/FT231X/FT234X (single port, 3Mbps) UART and multi-serial protocols (SPI, I 2 C, JTAG) bridges. FT2232C/D (dual port, clock up to 6 MHz). A library of over 250,000 device drivers, firmware, BIOS and utilities for Windows. Latest Drivers Downloads. Synaptics PS/2 Port TouchPad Driver 19.0.11.1 64. In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see. Right-click the name of the device you connected, and then select Update Driver Software. In the Hardware Update wizard, select Browse my computer for driver software and click Next.
Point and Print reduces administrative overhead, and simplifies and automates printing. Point and Print functionality was introduced in Microsoft Windows 95, Windows 98, and Windows 98 Second Edition (as a client), and Microsoft Windows NT 3.5 and later.
When you connect to a printer on a print server, the connecting client looks for the appropriate drivers on the print server. If the drivers are installed on the server, the drivers are automatically downloaded and configured for the client. However, if the drivers are not present, you are prompted to select and install the drivers.
More Information
This article describes the results of improperly configured or incompatible Point and Print situations, and provides solutions to those situations.
When you attempt to connect a Windows-based network client to a print server, you may receive the following error message:
The server on which the device name printer resides does not have the correct printer driver installed. If you want to install the driver on your local computer, click OK.
This error message can be displayed in any of the following situations:
When server message block (SMB) is connected to the print server.
When a Windows 95, Windows 98, or Winodws 98 Second Edition-based computer is running File and Print Sharing.
When an Alpha-based computer running Windows NT 4.0 Server connects to an x86-based client without an Alpha print driver.
When you connect to a printer using the new Internet Printing Protocol (IPP) and an appropriate driver is not installed on the Internet print server.
If you receive the error message in one of the situations described above, use the appropriate workaround.
SMB-connected print server
SMB print boxes let workstations on the network send print jobs directly to a print server without going through an intermediate personal computer or print server. This type of configuration does not support Point and Print.
Workaround
To work around this behavior, install the print driver locally and create a connection to the SMB print share:
Click Start, point to Settings, and then click Printers.
Double-click Add Printer, and then click Next.
Click Local Printer, and then click Next.
Click Create a new port.
In the Type box, click Local Port, and then click Next.
Type the SMB share name. For example:
PrintServerSharename
Continue the Wizard and install the appropriate driver for the device.
Computer running Windows 95, Windows 98, or Windows 98 Second Edition
You can share out print devices to other computers on the network in Windows 95, Windows 98, and Windows 98 Second Edition. These versions of Windows do not support alternate drivers like Windows NT does, so only these clients can connect in this Point and Print scenario.
Workaround
To work around this behavior, install the print driver locally and create a connection to the Windows 95, Windows 98, or Windows 98 Second Edition print share:
Click Start, point to Settings, and then click Printers.
Double-click Add Printer, and then click Next.
Click Local Printer, and then click Next.
Click Create a new port.
In the Type box, click Local Port, and then click Next.
Type the SMB share name. For example:
PrintServerSharename
Continue the wizard and install the appropriate driver for the device.
Windows NT 4.0 (non-x86 server, x86 client)
If your network contains a mixture of Windows 95, Windows 98, or Windows 98 Second Edition-based, Alpha-based, and x86-based computers, you can install printer drivers for each one on each print server. Doing this ensures that documents originating from Windows NT or Windows 95, Windows 98, or Windows 98 Second Edition clients running on any of the hardware types can use all print devices. During Point and Print, Windows NT clients call the application programming interface (API) GetPrinterDriver, and obtain information about the drivers that are installed on the server. If a suitable driver cannot be found, the error message is passed to the client.
Workaround
To work around this behavior, use the appropriate method.
Method 1 (administrators only): Configure non-x86-based servers for non-native drivers to accommodate all clients on the network. Use the following steps to install client drivers on a computer running Windows NT Server:
From a x86-based client, browse the print server.
Click the print folder, and then double-click Add Printer Wizard.
Click the appropriate port, and either click the printer from the Model/Manufacturing list, or click Have Disk and type the path to an updated driver.
After you finish the wizard, x86-based clients can download the driver automatically upon connection.
Method 2: Install the appropriate drivers on the client computer. If the driver is not available on the server, you can install the driver locally on your computer and redirect the output to the print server.
Click Start, point to Settings, and then click Printers.
Double-click Add Printer, and then click Next.
Click Local Printer, and then click Next.
Click Create a new port.
In the Type box, click Local Port, and then click Next.
Type the share name. For example:
PrintServerSharename
Continue the wizard and install the appropriate driver for the device.
Internet Printing Protocol (IPP)
You can use IPP to print directly to a Uniform Resource Locator (URL) over an intranet or the Internet. In addition, you can install a printer from the Internet or intranet using Microsoft Internet Explorer. The error message can occur when the IPP print server does not have a suitable driver installed.
Workaround
To work around this behavior, use the appropriate method.
Method 1 (administrators only): Install a compatible driver on the server.
Click Start, point to Settings, click Print Folder.
Double-click Add Printer, and then click Next.
Click Local Printer, and then click Next.
Click Create a new port.
In the Type box, click Local Port, and then click Next.
Type the share name. For example:
PrintServerSharename
Continue the wizard and install the appropriate driver for the device.
Method 2: Install a suitable driver on the client computer and redirect the printer to the appropriate IPP URL.
Click Start, point to Settings, click Printers.
Double-click Add Printer, and then click Next.
Click Local Printer, and then click Next.
Click Create a new port.
In the Type box, click Standard Port Monitor, and then click Next.
Type the Internet Protocol (IP) address of the IPP print server.
Continue the Add Printer wizard and install the appropriate driver.
Incompatible print driver
Some third-party drivers that are written for Windows NT 4.0 do not work properly in Windows 2000. If you attempt to install an incompatible driver, the error message is displayed during Point and Print.
Workarounds
To work around this behavior, use the appropriate method.
Method 1 (administrators only): Obtain an updated driver from the manufacturer's Web site.
Download and install the updated driver.
If the driver has an uninstallation tool, run the tool before continuing these steps.
Click Start, point to Settings, and then click Printers.
Double-click Add Printer, and then click Next.
Click Local Printer, and then click Next.
Click the same port you used for the previous driver.
Click Have Disk and type the installation folder for your updated driver.
Continue with Setup and share out the driver for down-level clients.
Method 2 (administrators only): Install a Windows 2000 driver on the print server.
If the original driver has an uninstallation tool, run the tool before continuing these steps.
Click Start, point to Settings, and then click Printers.
Double-click Add Printer, and then click Next.
Click Local Printer, and then click Next.
Click the same port you used for the previous Original Equipment Manufacturer (OEM) driver.
Click the appropriate model in the Model/Manufacturer list.
Finish Setup and share out the printer for network use.
Method 3: Install a compatible driver on the client and redirect the output to the server.
Click Start, point to Settings, and the click Printers.
Double-click Add Printer, and then click Next.
Click Local Printer, and then click Next.
Click Create a new port.
In the Type box, click Local Port, and then click Next.
Type the share name. For example:
PrintServerSharename
Continue the wizard and install the appropriate driver for the device.
Versions supported
- Windows 10
- Windows 8.1
Applies to
- Device manufacturers of CDC Control devices
Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.
In Windows 10, the driver has been rewritten by using the Kernel-Mode Driver Framework that improves the overall stability of the driver.
- Improved PnP and power management by the driver (such as, handling surprise removal).
- Added power management features such as USB Selective Suspend.
In addition, UWP applications can now use the APIs provided by the new Windows.Devices.SerialCommunication namespace that allow apps to talk to these devices.
Usbser.sys installation
Load the Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.
Note
If you trying to install a USB device class driver included in Windows, you do not need to download the driver. They are installed automatically. If they are not installed automatically, contact the device manufacturer. For the list of USB device class driver included in Windows, see USB device class drivers included in Windows.
Windows 10
In Windows 10, a new INF, Usbser.inf, has been added to %Systemroot%Inf that loads Usbser.sys as the function device object (FDO) in the device stack. If your device belongs to the Communications and CDC Control device class, Usbser.sys is loaded automatically.You do not need to write your own INF to reference the driver. The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows.
USBClass_02
USBClass_02&SubClass_02
- If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor. For more information, see USB communications device class. With this approach, you are not required to distribute INF files for your device because the system uses Usbser.inf.
- If your device specifies class code 02 but a subclass code value other than 02, Usbser.sys does not load automatically. Pnp Manager tries to find a driver. If a suitable driver is not found, the device might not have a driver loaded. In this case, you might have to load your own driver or write an INF that references another in-box driver.
- If your device specifies class and subclass codes to 02, and you want to load another driver instead of Usbser.sys, you have to write an INF that specifies the hardware ID of the device and the driver to install. For examples, look through the INF files included with sample drivers and find devices similar to your device. For information about INF sections, see Overview of INF Files.
Note
Microsoft encourages you to use in-box drivers whenever possible. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Unlike desktop editions, it is not possible to load a driver through an external driver package. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device.
Windows 8.1 and earlier versions
In Windows 8.1 and earlier versions of the operating system, Usbser.sys is not automatically loaded when a USB-to-serial device is attached to a computer. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) by using the Include directive. The directive is required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications require to find the device and talk to it. That INF specifies 'Usbser' as a lower filter driver in a device stack.
The INF also needs to specify the device setup class as Modem to use mdmcpq.inf. Under the [Version] section of the INF, specify the Modem and the device class GUID. for details, see System-Supplied Device Setup Classes.
For more information, see this KB article.
Configure selective suspend for Usbser.sys
Starting in Windows 10, Usbser.sys supports USB Selective Suspend. It allows the attached USB-to-serial device to enter a low power state when not in use, while the system remains in the S0 state. When communication with the device resumes, the device can leave the Suspend state and resume Working state. The feature is disabled by default and can be enabled and configured by setting the IdleUsbSelectiveSuspendPolicy entry under this registry key:
To configure power management features of Usbser.sys, you can set IdleUsbSelectiveSuspendPolicy to:
'0x00000001': Enters selective suspend when idle, that is, when there are no active data transfers to or from the device.
'0x00000000': Enters selective suspend only when there are no open handles to the device.
Download Woehler Port Devices Driver
That entry can be added in one of two ways:
Write an INF that references the install INF and add the registry entry in the HW.AddReg section.
Describe the registry entry in an extended properties OS feature descriptor. Add a custom property section that sets the bPropertyName field to a Unicode string, 'IdleUsbSelectiveSuspendPolicy' and wPropertyNameLength to 62 bytes. Set the bPropertyData field to '0x00000001' or '0x00000000'. The property values are stored as little-endian 32-bit integers.
For more information, see Microsoft OS Descriptors.
Develop Windows applications for a USB CDC device
If you install Usbser.sys for the USB CDC device, here are the application programming model options:
Download Woehler Port Devices Drivers
Starting in Windows 10, a Windows app can send requests to Usbser.sys by using the Windows.Devices.SerialCommunication namespace. It defines Windows Runtime classes that can use to communicate with a USB CDC device through a serial port or some abstraction of a serial port. The classes provide functionality to discover such serial device, read and write data, and control serial-specific properties for flow control, such as setting baud rate, signal states.
In Windows 8.1 and earlier versions, you can write a Windows desktop application that opens a virtual COM port and communicates with the device. For more information, see:
Win32 programming model:
.NET framework programming model:
Related topics