Writing to and reading from the USB port directly. The USB device creates no virtual serial port, is not HID compliant (hence the HIDd api code I created worked with other devices but not this specific device), and only accepts code to/from it. The device driver from the manufacturer does not provide api access either so it is up to me to communicate directly with it. It's been a learning process to be sure! I got excited at one point when I got the HIDd api to work only to find out that this specific device is not HID. Then I tested using the mscomm control fine with another device which created a virtual serial port, but not this device - it does no such thing. Such is the way we learn.... :o)





>>Thank you Carlos, yes it helps alot. I cannot believe you found that link at MSFT - I swear I searched all of MSFT (and even sent emails to MSFT Employees) looking for more examples of enumerating devices using the setupapi.dll (in any language) and never found that MSFT link.
>>
>>Thanks again!
>>Tracy
>>
>
>You are welcomed! Glad it helped. I don't know how I find those things! You are not the first person to tell me that. I remember that years ago I could not find anything, and I mean nothing, in MSDN.
>
>Now its like I managed to get get hang of it. I guess its like if you moved to China, I am shure that after 10 years you'll end up understanding chinese!
>
>Just out of curiosity, what are you trying to do?
>
>Carlos