23-04-2019, 07:33 AM
How very 1990's of you.
A genuine OS Bigot. I was sure they were all in museums now.
Do you really think that a driver for an OS can reflash a chip on a third party device? The issue you mention relates to Prolific USB chipsets. Newer Windows drivers from Prolific recognise fake chipsets and simply do not work with them. It is not Microsoft being a big bad spooky overlord, it is Prolific simply protecting their IP.
Now, I doubt Yaesu are using fake Prolific chipsets on board and as other machines are having the same issues on that radio, I don't think it is a driver issue.
However, what driver brand does Device Manager or it's equivalent say it is using?
If it has a Prolific chipset on board and you think it may be the Prolific issue, do a web search for the older drivers and temporarily install those and see if it springs back to life.
A genuine OS Bigot. I was sure they were all in museums now.
Do you really think that a driver for an OS can reflash a chip on a third party device? The issue you mention relates to Prolific USB chipsets. Newer Windows drivers from Prolific recognise fake chipsets and simply do not work with them. It is not Microsoft being a big bad spooky overlord, it is Prolific simply protecting their IP.
Now, I doubt Yaesu are using fake Prolific chipsets on board and as other machines are having the same issues on that radio, I don't think it is a driver issue.
However, what driver brand does Device Manager or it's equivalent say it is using?
If it has a Prolific chipset on board and you think it may be the Prolific issue, do a web search for the older drivers and temporarily install those and see if it springs back to life.
Colin
Barossa Valley, SAP. PF95ln
(aka VK5CSW)
Barossa Valley, SAP. PF95ln
(aka VK5CSW)