none
CM_PROB_NO_SOFTCONFIG RRS feed

  • Question

  • I have written a driver that uses a certain I/O space - corresponding to a hardwired peripheral on my target hw. When I set the ConfigPriority=DESIRED in the inf file, driver loads and executes fine. When I set the ConfigPrriority=HARDWIRED, the driver loads but will not start. In setupapi.log I see the error CM_PROB_NO_SOFTCONFIG.

    Because the peripheral is hardwired I must use that I/O space, I assumed I should therefore use HARDWIRED? Is this not true? What is the source of this error? Will DESIRED suit my needs?

    Wednesday, October 10, 2012 7:26 PM

Answers

  • Desired should work fine for your situation.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Wednesday, October 10, 2012 7:33 PM