Umm you are aware that every device communicates over a USB cable differently right? Hence the existence of drivers. I see no scenario where accessing the raw USB data is useful, unless you are trying to communicate with a device you wrote yourself. And, if you have the expertise to create a hardware device using the USB interface, why can't you just write a device driver? Also, why would mIRC need this? How does communicating with a USB device relate to chatting? I can't even see an indirect link such as with sockets (!weather scripts for example). I can't see why this would be useful to anyone. Oh and by the way, the system would have to be MUCH more complex than /usbwrite and /usbread. For example, how do you know which USB port to write to? How do you determine whether to use USB 1.0, 1.1, or 2.0 to communicate? How do you handle if there is a USB hub connected? What about daisy chained USB devices?
Thats why device drivers are needed. If you want to communicate with a particular device, learn C.
