I've used in the past RequestDeviceNotifications to create a Device
Notification queue to "listen to" all the devices that get plugged/
removed from the machine, it's working great for USB printers, USB /
PCMCIA storage devices, PCMCIA network cards.
Recently I've added support for USB network devices (USB RNDIS) and
although this new network interface is working perfectly fine, I never
receive any notification in my listening queue.
I wonder if there is something at the USB level that bypasses the
usual notifications system when creating the network interface. Is
there a reason / way around that?
Fix for SuSE multiple hotplug network interfaces race condition? ... all USB and PCMCIA network interface hotplug events are ... even an attempt to serialize PCMCIA network interface hotplug events.... Why are SuSE's hotplug scripts written this way? ... (comp.os.linux.networking)
Fix for SuSE multiple hotplug network interfaces race condition? ... all USB and PCMCIA network interface hotplug events are ... even an attempt to serialize PCMCIA network interface hotplug events.... Why are SuSE's hotplug scripts written this way? ... (alt.os.linux.suse)
Re: Network Interfaces ... I have never used usb but I do use a wireless pcmcia card in my laptop. ...iface lo inet loopback ...iface eth0 inet dhcp... (Debian-User)
RE: USB Device Interface ... I also need other's help on this because i dont have all kinds of USB flash... 1> monitor for registry changes under the registry key: ... or ur service app will have DBT_DEVICEARRIVAL notification.... to produce the drive letter assignment.... (microsoft.public.development.device.drivers)
Re: USB Device Interface ... is absolutely no reason to play with the registry.... I also need other's help on this because i dont have all kinds of USB flash storage device to test my service application. ... or ur service app will have DBT_DEVICEARRIVAL notification.... to produce the drive letter assignment.... (microsoft.public.development.device.drivers)
