hoolie

Madboy, Now I have a different problem as the system I was testing on has all the drivers. I deleted the driver for the ethernet adapter and uninstalled it from device manager to test the new version, but it hangs and never completes. However, it does find the driver in the db, so that part seems to work. I think it has to do with the device status "This device is not configured correctly (Code 1)" since there may be information on the required driver somewhere in an inf file on the hard disk that I cannot find. When not running your program, and using windows to reinstall the driver (after I deleted it from the hd), in the found new hardware wizard it keeps asking for a driver location (since I deleted the driver) and all I can do is cancel out and that might be triggering the issue with your program where the device status is not correctly set in the registry. This happens with both .18 an .19 versions, so it has something to do with removing a driver that was working correctly in order to test the program. I'll have to try this again on a fresh install, but need to change hd's first. I'll try again tomorrow. Here's some logs and pictures for you. logs_ver19.zip

MadBoy, I'm having problems with the program locating drivers in the database. I am testing the program with a system that has 9 devices needing drivers, and I know 4 or 5 of them should get detected and installed with the program, but none of them are found. Errors are like this: Device => PCI\VEN_14E4&DEV_170C&SUBSYS_01AF1028&REV_02 Driver Path => NOT FOUND in DB I traced it to the issue of the "REV_xx" suffix, so there is no matching up being done with the db that is built. Looking at the inf file for that specific driver, there is no suffix like "REV_02" listed with the device name, so the db appears to be building correctly. However, I tried the same driver set with version 0.6.7.0 of the program, and it worked! There must be something different about how the 2 versions make a device match. I've attached the log, xml, and db since I know you will ask. logs.zip