Hi,
some guys told me that a program of mine is not able to work correct on Windows 10.
It uses a virtual com port driver from FTDI.
Has someone a similar problem and maybe a solution?
I have no access to a Windows 10 PC to test something.
Bernd
PB 5.31 x86 and Windows 10
-
RichAlgeni
- Addict
- Posts: 935
- Joined: Wed Sep 22, 2010 1:50 am
- Location: Bradenton, FL
Re: PB 5.31 x86 and Windows 10
Bernd,
If the com port was working ok, even a virtual com port, it should show up in device manager. If so, they should be able to connect to it using shareware terminal emulation software, that can connect to a com port. If it does connect, type ^Q, do you see any data coming in then?
Rich
If the com port was working ok, even a virtual com port, it should show up in device manager. If so, they should be able to connect to it using shareware terminal emulation software, that can connect to a com port. If it does connect, type ^Q, do you see any data coming in then?
Rich
Re: PB 5.31 x86 and Windows 10
On my W10 I have not had any problems with FTDI devices.
I did not have to install any drivers, Windows provided a driver "provided by DTC"
Under device manager it appears as "USB Serial Port"
My PB application is happy with that.
Could he have been caught with a fake FTDI chip?
FTDI drivers were getting nasty with the fake chips.
The only problem I have found (so far) is with a Microchip PIC32 device which does a few strange things.
Jim
I did not have to install any drivers, Windows provided a driver "provided by DTC"
Under device manager it appears as "USB Serial Port"
My PB application is happy with that.
Could he have been caught with a fake FTDI chip?
FTDI drivers were getting nasty with the fake chips.
The only problem I have found (so far) is with a Microchip PIC32 device which does a few strange things.
Jim
-
Fangbeast
- PureBasic Protozoa
- Posts: 4790
- Joined: Fri Apr 25, 2003 3:08 pm
- Location: Not Sydney!!! (Bad water, no goats)
Re: PB 5.31 x86 and Windows 10
I'm programming my amateur gear (3 radios) using fake prolific chips that create virtual com ports and initially they failed as windows would upgrade to their latest prolific driver and the support for the fake prolific chips ended with the new genenration.
I grabbed a driver set that was made in 2012 that matched the prolific chips I had, installed and set them to be used in control panel (Which is still available) and then it worked.
Also must remember to blacklist the MS driver in windows update so it keeps the prolific ones between reboots.
The point of all this was that FTDI had similar problems and I read that you could solve it the same way that I did for prolific.
I:E. 1. Find the old FTDI drivers that did work, install them.
2. Blacklist the new drivers from being updated.
3. Point the hardware to the old drivers in control panel.
I grabbed a driver set that was made in 2012 that matched the prolific chips I had, installed and set them to be used in control panel (Which is still available) and then it worked.
Also must remember to blacklist the MS driver in windows update so it keeps the prolific ones between reboots.
The point of all this was that FTDI had similar problems and I read that you could solve it the same way that I did for prolific.
I:E. 1. Find the old FTDI drivers that did work, install them.
2. Blacklist the new drivers from being updated.
3. Point the hardware to the old drivers in control panel.
Amateur Radio/VK3HAF, (D-STAR/DMR and more), Arduino, ESP32, Coding, Crochet
Re: PB 5.31 x86 and Windows 10
I bit the bullet and upgraded my W7Pro PC today.
I have tested 3 different FTDI devices and they all have FTDI supplied drives including the one that ended up with DTC drivers on the other PC
The main difference between the two PC's is W7 PRO Vs W8.1 Home and the Pro has had a lot more FTDI devices installed before upgrading.
I run PB 5.31 x86 here and can probably find a matching FTDI chipset if you need some testing.
Jim
I have tested 3 different FTDI devices and they all have FTDI supplied drives including the one that ended up with DTC drivers on the other PC
The main difference between the two PC's is W7 PRO Vs W8.1 Home and the Pro has had a lot more FTDI devices installed before upgrading.
I run PB 5.31 x86 here and can probably find a matching FTDI chipset if you need some testing.
Jim