FTDI invalid handle on some computers

[rolfk]

---

@dkim2 wrote:

Yes.

This is the real problem! FT_Close is defined as:

FT_STATUS FT_Close(FT_HANDLE ftHandle);

NOT

FT_STATUS FT_Close(FT_HANDLE *ftHandle); // WRONG

Change that Pass: Pointer to Value to Pass: Value, et voila! It works! And yes, for the FT_Open() it needs to remain as Pass: Pointer to Value.

When I install the driver, the file in syswow64 is the ftd2xx.dll not ftd2xx64.dll, although I am using the call library function on the ftd2xx64.dll from LabVIEW. Could this be an issue?

---

SysWOW64, despite its name, contains binary files for 32-bit applications! The 64-bit binaries are located in System32! And I have no idea what you are talking about with ftd2xx64.dll. They are both called ftd2xx.dll.

[Andrey_Dmitriev]

---

@rolfk wrote: I have no idea what you are talking about with ftd2xx64.dll. They are both called ftd2xx.dll.

---

Hmmm, on my PC the officially deployed from FTDI and signed library is also called ftd2xx64:

ftd2xx.dll is not exists in %WINDIR%\system32, at least not on my PC.

[rolfk]

---

@Andrey_Dmitriev wrote:

---

@rolfk wrote: I have no idea what you are talking about with ftd2xx64.dll. They are both called ftd2xx.dll.

---

Hmmm, on my PC the officially deployed from FTDI and signed library is also called ftd2xx64:

ftd2xx.dll is not exists in %WINDIR%\system32, at least not on my PC.

---

As the image shows in the other message for the device properties, it seems to have installed ftd2xx.dll in both SysWOW64 and System32. It's what I have observed in some systems too, but I'm not currently using any FTDI hardware.

The latest driver 2.12.36.4 from FTDI seems to indeed install the ftd2xx64.dll in system32. Go figure.

[dkim2]

Thank you so much, this solved the issue.