Checking for USB Drivers...

[GlennP]

Hi All,
On my quest to ensure my software/hardware doesn't break anything but has the drivers it needs I am using a method that looks for the C:\Windows\system32\drivers\ftdibus.sys file. Two questions is this file the one I need to check for the version number is the same as was found using a previous program and device manager, and is the file at that location on all versions of Windows. I have test run it on Windows XP Pro, Windows7 Pro, but can the location vary? this is due to the fact that I am checking the above location (C:\Windows....) Also I have noticed some warnings about ftdibus.sys being used to disguise Trojans & Viruses, any ideas any one?

Glenn    

[Jan Axelson]

Not every Windows drive is C:.

And I believe users can specify a different name for Windows directory on installation though I don't know how common that is.

Jan

[GlennP]

Thanks for that , it did save me from trouble. I do the below
        LocationDrivers = Environment.SystemDirectory + "\\drivers\\ftdibus.sys";
 FileVersionInfo fsi = FileVersionInfo.GetVersionInfo(LocationDrivers);//@"C:\Windows\system32\drivers\ftdibus.sys");
Thing is now I have attacked every machine (I can) testing this darn thing, can I ask if the FTDI driver installs faster on some machines than others it just I have seen big differences in the speed that it installs, on similar machines, XP Pro, around 2 GHz (one  2.5, one 2.0).  Really I'm not bothered by the speed it just that appears odd and I'm trying for an application that will causes the least amount of trouble to the end user (and me!) down the line.
Any ideas, any one?....

[Jan Axelson]

It doesn't surprise me. I don't know the exact reason.

Jan

[GlennP]

Well, thats good I think! The thing is if USB is that irregular at install why does it work reliably (relatively) later?
Glenn

[Jan Axelson]

For what it's worth, having to a wait a little longer to install doesn't have much user impact compared to how well the device functions after installation. You could look at the setupapi logs to see if the system is flailing around looking for a driver. Or it may be something else entirely (CPU is busy with other tasks).

Jan