Hello, I have managed to sort out my problem; for anyone else with a similar one: I found a company that provides a USB CDC driver compatible with Windows 7: I modified the provided INF to include only what was utilized in that provided by Atmel, changed the hardware ID to match that of my device and after installing using the legacy hardware option it is working. I won't post my modified INF as I don't have permission from Recursion and I don't know how theyd take to that but the process is fairly simple for anyone else who needs it. Hi Thomas77, Thanks for your reply. I have been using XP Mode so far and it connects OK but its a little difficult to develop the application to drive the device via the virtual serial port and then have the device connect to, what might as well be, a completely different computer. Not to mention that USB was being touted as the solution for embedded developers to the dropping of serial ports by manufacturers, now its just started being taken up and it suddenly becomes useless again with an upgrade to 7 without extra hardware or expensive licensed third party drivers?
![]()
There are third party virtual serial drivers available (generic drivers that are compatible with any CDC implementation) but the licenses run at about 3000euro from some companies. Is there a way to work out what the problem Windows has with that INF is when I try and add it via the legacy hardware method?
Faking an RS232 Serial Port. Ask Question Asked 10 years, 1 month ago. I was able to use com0com and the Com Port Serial Emulator on Windows 7 64-bit without issue, worked great. Some Windows systems checking digitally signed driver will not work with its virtual serial port. Just want people know. Virtual Serial Ports Emulator (sometimes referred to as VSPE) was added by renArD in Feb 2015 and the latest update was made in Jan 2017. The list of alternatives was updated Apr 2018. It's possible to update the information on Virtual Serial Ports Emulator or report it as discontinued, duplicated or spam.
Am I correct in assuming that Windows no longer utilizes INF files, if so, would it be possible to create a replacement using the Windows Driver Development Kit without acctually having to code a new driver? Thanks again, SJF. Hello, I have managed to sort out my problem; for anyone else with a similar one: I found a company that provides a USB CDC driver compatible with Windows 7: I modified the provided INF to include only what was utilized in that provided by Atmel, changed the hardware ID to match that of my device and after installing using the legacy hardware option it is working.
I won't post my modified INF as I don't have permission from Recursion and I don't know how theyd take to that but the process is fairly simple for anyone else who needs it.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |