[Info-vax] FTDI driver for windows

Simon Clubley clubley at remove_me.eisner.decus.org-Earth.UFP
Sat Jul 13 00:30:05 EDT 2019


On 2019-06-19, VAXman-  @SendSpamHere.ORG <VAXman- at SendSpamHere.ORG> wrote:
> In article <qeds2n$4qd$2 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>>On 2019-06-19, VAXman-  @SendSpamHere.ORG <VAXman- at SendSpamHere.ORG> wrote:
>>>
>>> Well, the email I received from the manufacturer/designer of the altimeter
>>> says that the FTDI chip is legit.  Where does that leave me with WEENDOZE
>>> refusing to connect to it???
>>>
>>
>>I think you said you tried it under Itanium. If so, did it show up
>>as a usable serial port, or did it just show up as a generic unknown
>>device ? (I'm not talking about what the device description string says.
>>I'm talking about what USB driver VMS loaded.)
>
> It shows up as a terminal device.  I've packed the rocket with this particular
> altimeter for a large weekend launch.  I can verify it next week.
>

I wonder who wrote the FTDI driver for VMS and what they used as the
reference driver. (The FTDI chips are not standard USB CDC communications
devices and require special drivers).

>
>
>>I think the next thing for you to try would be to download the Windows
>>driver from the FTDI website and try that. IIRC, they come in two
>>flavours, a virtual com port driver and a more low-level driver.
>>
>>Do you know which one you need ?
>
> All I know is that when it was inserted, WEENDOZE when and found a drive and
> did whatever it does to install it.
>
> The software wants me to enter the COMM# number when the device is connected.
> However, due to the connect/disconnect nature of this driver, that number is
> never the same twice.
>

It sounds like you need the VCP version of the drivers then.

Looking around, this appears to be the download location for the drivers:

https://www.ftdichip.com/Drivers/VCP.htm

If you are sure it's a genuine FTDI device, I would try the drivers
from this location as your next step. As John says, Windows may have
installed a driver which doesn't work with your FTDI device.

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world



More information about the Info-vax mailing list