Software

Ask something
Question Locked

FTDI DLL Hell

0 helpful
3 replies

by txpomeroy

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am trying to rename the FTDI drivers for their FT232R chip, with their blessing but no support, to support a medical device we're developing. We need to ensure that the driver stack we test doesn't get overwritten whenever some other device gets loaded. I have the driver package working but am still getting "cross talk" between drivers that use the standard driver stack and the renamed one. In other words, our application, a C# VS 2008 app, sees devices from both stacks. Even worse, when we check the driver version in our app, we get a value but are not sure which driver stack provided it.

If anyone has any experience renaming the FTDI driver package files, and not just the INF files, please respond.

Thanks

3 replies

by robo_dev

What OS is this app running on?

My guess is this is Windows mobile?

My further guess is that the problem is related to the file/directory structure of these devices....there is no relative path because mobile devices have no 'current' directory.

There are only absolute paths, and most device drivers are expected to be in \windows directory.

http://www.c-sharpcorner.com/Forums/ShowMessages.aspx?ThreadID=25756

by txpomeroy

OS is WinXP 32 or 64 and Vista 32 or 64.

Driver files are being loaded to Windows/system32 and Windows/system32/drivers and the correct chain of files is reported in the device manager but I still am getting this "cross talk" to other devices based on FTDI chips.

This discussion is closed to new replies.