Sign in to follow this  
Followers 0
jcai@precisionsupply.com

DPInst.exe doesn't work.

6 posts in this topic

I use most updated version of DPInst.exe (version 2.1) to install 2 usb driver (ftdibus.inf and ftdiport.inf). They are all unsigned. So I make legacyMode on, which allow DPInst.exe install unsigned driver. It tells me installation is successful after I run the DPInst. But It still prompt up "Find new hardware" when I plug the device to my desktop. The DPInst.xml file is good. I just don't know why it happens like this. Please help!!!

0

Share this post


Link to post
Share on other sites
I use most updated version of DPInst.exe (version 2.1) to install 2 usb driver (ftdibus.inf and ftdiport.inf). They are all unsigned. So I make legacyMode on, which allow DPInst.exe install unsigned driver. It tells me installation is successful after I run the DPInst. But It still prompt up "Find new hardware" when I plug the device to my desktop. The DPInst.xml file is good. I just don't know why it happens like this. Please help!!!

Hello,

so someone has the same problem...

Let`s hope one of the gurus has a look at this, too!

BTW... For me, the "normal installation" does work, but the quiet installation does not.

Regards,

Pelle.

Edited by Pelle1911
0

Share this post


Link to post
Share on other sites

Hi there,

I am also finding the same problem.

I am not able to install driver if I use DPInst exe in legacy mode.

Error coming as No matching devices found in INF on the Machine.

Can anyone help me in this? I do not have cat file for driver and there is no entry in INF file also.

Please reply.

0

Share this post


Link to post
Share on other sites

Hello again,

after having users install the driver in legacy-mode, it seems users typically quit installation when prompted to install an unsigned driver. This is causing serious problems, since if the driver is not installed, our system won't work (obviously).

Any suggestions how to suppress the warning-message? This is important!

Regards,

Pelle.

0

Share this post


Link to post
Share on other sites

I am getting exactly the same thing and was hoping somebody had a solution. Apparently a windows hotfix is responsible for this and unfortunately it has no uninstall functionality. I will get back to you if I manage to pinpoint the hotfix that is the culprit.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.