Usbser.sys CDC Virtual COM Port

I have some issue regarding the use of the usbser.sys built in windows driver. I have implemented a USB CDC driver in some hardware that I am developing hoping not to have to change Win32 applicatins that currently talk to the device using an RS-232 COM Port. I have generated a .inf file for Windows XP and it installs the usbser.sys driver properly and it works. The Win32 apps can send and receive data over USB from the device as if it was connected to an RS-232 Com Port. The problem is that the device will not remain in the device manager when disconnected. It is of course very reasonable that when you unplug a USB device it is removed from the device manager, however, RS-232 ports are always available! This causes problems in the Win32 apps that are using the port as they have to be re-started (or they at least have to re-connect to the port) each time the device is reconnected to the PC.

Does anyone have any solutions?

I dont think there is anyway to change this. The Com1 and Com2 can also disappear by removal, especially on a laptop because they are in hw dock, or by disabling them in device manager.

Thank you for letting me know about it. I guess that I will have to implement Usb properly.

It has been a while since you posted last here.. But I still hope to see your reply!

We are also developing virtual COM port driver. (For the purpose : We have a legacy application that outputs only to COM port and a usb hardware device). We are using usbser.sys as virtual COM port driver. We are able to install the driver successfully.

But when we use Serial COM APIs like CreateFile etc., they fail with GetLastError reporting 2(system can not find specified path). Also if i see device manager -> Ports (COM & LPT) section, the virtual COM driver is listed with an exclaimation mark with below error,-

"Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)"

Do you have any inputs here ? Thanks in advance!

Vijay

Hi All,

Just a note here that I had this problem. I got around it by scanning all available com ports a few times a second on a timer until the port I wanted came up and then opened it. Use the code below (VB sorry):-

Sub GetSerialPortNames()
' Show all available COM ports.
For Each sp As String In My.Computer.Ports.SerialPortNames
ListBox1.Items.Add(sp)
Next
End Sub

Regards