Re: usbser.sys and registry entry
- From: "Alexander Grigoriev" <alegr@xxxxxxxxxxxxx>
- Date: Mon, 6 Jun 2005 06:31:16 -0700
It is very possible that USBSER was not designed properly. Judging by how
long it took to clean it, starting from Windows 98, its quality is likely
quite low.
A properly designed driver should clean all its synbolic links, disable
interfaces (which are symbolic links, too) and clean all corresponding
registry information not only in REMOVE_DEVICE, but also in STOP_DEVICE and
SURPRISE_REMOVAL (taking care about NOT deleting those twice, because at
REMOVE_DEVICE time, another device object may already own those). Those
links should be created in START_DEVICE, not in AddDevice.
<macmohan@xxxxxxxxx> wrote in message
news:1118039475.813357.176280@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hello All,
>
> I am using the usbser.sys for the CDC ACM device to emulate a Virtual
> COM port on Windows. The USB device is getting enumerated and in the
> device manager, ports, an entry is made and properties shows "device is
> working properly". In the registry in
> My Computer\HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM an entry
> by the name \Device\USBSER000 is formed with data value set to COM port
> no. (say COM3).
> When the USB cable is removed, this entry also gets deleted
> automatically.
> I am able to open any application on that Virtual com port and use it
> like a normal serial port.
> But sometimes, when the application tries to open the Virtual COM port,
> it gets a error: "System file not specified". When I remove the USB
> cable at this point, the entry \Device\USBSER000 still remains.
> To start the application, I have to connect the device to other USB
> port.
>
> Is this the problem with usbser.sys of not removing the registry entry
> sometimes on surprise removal?
>
> Thanks for your time..
>
> Regards,
> Mohan.
>
.
- References:
- usbser.sys and registry entry
- From: macmohan
- usbser.sys and registry entry
- Prev by Date: Re: USB Bus or Device Reset?
- Next by Date: RE: Print Monitor, error in LoadLibrary
- Previous by thread: usbser.sys and registry entry
- Next by thread: Miss the Hardware interrupt using NTDDK USBCAMD
- Index(es):
Relevant Pages
|