- Longway Modems Driver Download For Windows 10
- Longway Modems Driver Download For Windows 7
- Longway Modems Driver Download For Windows
This download contains the Intel® Ethernet network drivers and software for Windows 8.1. Which file should you download? Note: 10-Gb adapters are only supported by x64-bit drivers. PROWin32.zip for 32-bit (x86) editions of Windows. PROWinx64.zip for 64-bit (x64) editions of Windows; How to use this download. Download Bluetooth Driver Installer 1.0.0.128 for Windows for free, without any viruses, from Uptodown. Try the latest version of Bluetooth Driver Installer 2020 for Windows.
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.
Longway Modems Driver Download For Windows 10
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.
That entry can be added in one of two ways:
Longway Modems Driver Download For Windows 7
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:
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
| ||||||||
Home • Troubleshooting • Windows XP | ||||||||
ALSO SEE: Checking Modem InstallXP Driver SigningXP TipsDisconnections |
Windows XP (Updated 26-Apr-03)
Windows XP & Modems:Windows XP comes with a variety of 'generic' modem drivers - including modems based upon all the popular chipsets. In many cases, adding, changing, or removing a modem is simple: plug and play. But, it doesn't always work that way.
If you haven't yet installed or upgraded to Windows XP - please read this whole page first! If it's installed, check Control Panel -> System -> Hardware Tab -> Device Manager to see if the modem is listed (see this page for sample); if the Query Modem produces responses, you probably don't have a modem problem - check your Connectoids.
MODEM INSTALLATION IN XP:
If you are upgrading a system with an older version of Windows to XP: you are much more likely to have a modem problem. I recommend remove the modem from the system before you upgrade. (Remove it in Control Panel's Add/Remove Programs if it is listed there, as well as physically.) Then, after XP is installed, put the modem back in the machine. XP should find new hardware and automatically install support.
Clean Install - installing XP 'clean' (not attempting to upgrade existing system/OS) shouldn't be a problem - as long as XP has a driver for your modem.
If XP doesn't find a driver for your modem: Search the WindowsUpdate driver list for a driver; or, find a XP or Win2k-compatible driver from your modem vendor.
If you've already upgraded the system with the modem installed, subsequent removal may result in automatic installation of the same non-working driver. You may be able to resolve the problem by installing a new driver using the Update Driver... selection in Device Manager (see below).
ALSO SEE: Checking Modem InstallXP Driver SigningXP TipsDisconnections
Longway Modems Driver Download For Windows
Check System: Click START -> CONTROL PANEL. (Then, the easiest way for me is to Switch to Classic View, and double-click the SYSTEM icon. There are other ways of bring up System as well.) Then, click on the Hardware tab, and then Device Manager. (See this page.) Expand the Modems tab by clicking on the +, and your modem should be listed. If it is not, look for Unknown devices / Error indications. You can also use the Update Driver... and use the don't search / Have Disk option to point XP to a compatible driver you've downloaded. You can also try Uninstall and then try the Add New Hardware wizard - use the don't search / Have disk option to point to a compatible driver. If the modem is listed without error indication in device manager, continue to Properties by right-clicking the modem as shown. |
A Premium Access Subscription is required to view the remainder of this page - which includes more graphics, and XP modem installation and troubleshooting.
Home | Links | Send Feedback | Privacy Policy | Report Broken Link Legal Page | Author's Web Sites | Log In |
Modemsite.com ©1998-2020 v.Richard Gamberg. All rights reserved. |