[Nirmal Shyam Kumar]

Hi Ajay,

Would like to update, a follow up of our discussion over the call:

We did try installing LabVIEW in the clean PC and unexpectedly the SW did not work as it was in case with SW working on machines that has LabVIEW pre-installed

So we are confused again on the missing piece. Do you have any alternate suggestions?

Meanwhile, we are trying to compare the reports exported from Dependency Walker and shall share with you possibly tomorrow

Best Regards,
Nirmal Shyam Kumar.S

[Nirmal Shyam Kumar]

Hi Ajay,

Thanks for the suggestion and I would like to respond on behalf of Infant.

Our Typical execution steps are:

1. Run the LabVIEW Installer (Exe and Installer created per guidelines) in the Clean machine
2. Run the FTDI CDM Driver (the same one you mentioned in the link)
3. Run the Executable (as mentioned by Infant, we have verified the folder to carry FTD2XX.dll)

On skipping step 2, we get FTDI driver error and at times the device is not listed in the Windows Device manager

Strangely if a system has LabVIEW (nothing else related to FTDI driver), the Executable works fine when the above steps are followed.  If the system doesn’t have LabVIEW, then we observe the FTDI driver error as indicated by Infant.

It looks like something with DLL and FTDI Driver. But we are not sure about the root cause.

Best Regards,
Nirmal Shyam Kumar.S

[Author]

Posts