USB Driver is missing

[rickford66]

I have an application that was written in LV7.0, back when XP was the machine of choice.  Back then, I could get away with putting a copy of my USB driver .dll file in the same folder with my app.  I've recently moved my app up to LV2010, and am now wanting to take advantage of the driver store.  The USB driver installs to the driver store.  Therefore, I don't want to keep a local copy of the .dll file, but instead, I want to use the one that is loaded from the store.  Problem is, when I deleted my .dll from my working folder, my vi's broke.  They don't seem to know how to find the .dll that is installed from the store.  Does anyone know how to fix this problem?  Thanks.

[billko]

I think you have to update at least one instance of your call library function properties to point to the new location...

[rickford66]

I get that, but now I have 2 questions.  1.  Where is the file?  I did a search and came up empty, even though I know it's installed.  2.  Will this location be the same for W7, Vista and XP?  Thanks.

[billko · Accepted solution]

---

@rickford66 wrote:

I get that, but now I have 2 questions.  1.  Where is the file?  I did a search and came up empty, even though I know it's installed.  2.  Will this location be the same for W7, Vista and XP?  Thanks.

---

Most likely it went into your windows/system32 folder - at least in XP.  I haven't actually looked at the directory structure for Windows7, but I imagine it to be the same/similar.  Maybe it gets a little more complicated with the 64-bit version, I don't know...

Sorry I can't be of more help...

[rickford66]

I found it.  I forgot to plug in the device so that the driver would be copied out of the store, that's why it wasn't there yet.  Duh.  After doing that, I just browsed to it when prompted (while opening the app source code) and it solved the problem.  Thanks.

[billko]

---

@rickford66 wrote:

I found it.  I forgot to plug in the device so that the driver would be copied out of the store, that's why it wasn't there yet.  Duh.  After doing that, I just browsed to it when prompted (while opening the app source code) and it solved the problem.  Thanks.

---

Glad you fixed it.  🙂