How to add entries in the Critical Device Database?

Hi,

How should I add entries inside CDDB given an .inf file?

Is there any tool/utility out there which accomplish this or all that is required is few changes in .inf? If yes what those changes should be?

Thanks.

Well, I think looking at web I am the first one who is actually building such tool.

(Sure as hell, if someone knows something that can get these informations out of INF lemme know I'll stop working immidiedly and use that commercial or not.)

.INF is microsoft badly generated information file what nobody likes, lol. It only has 1 subtopic "tree" following all rest of the "tree's" and to locate information at INF by any 3rd party tool it would need to set of strings, go through entire tree to get the full information needed for the included driver(s). Structure is so damn bad that it's just horrible to parse.

To answer the question itself, well, I think in your case (unless you need to boot it from NIC_3,4,5,6,6,7,78,8,8,8,9 and so on) easiest solution would be to boot the OS with NIC_2 in same system architecture and simply export the critical devices or include critical devices from INF DEVICE_IDs to correct class to the HOST system and export service and .reg to removal of entries which (your link on previous few posts stated how the host system Windows is built). That would reguire 1 .reg file and the driver .sys file.

Edited by genetix, 02 September 2013 - 02:23 PM.

To answer the question itself, well, I think in your case (unless you need to boot it from NIC_3,4,5,6,6,7,78,8,8,8,9 and so on) easiest solution would be to boot the OS with NIC_2 in same system architecture and simply export the critical devices or include critical devices from INF DEVICE_IDs to correct class to the HOST system and export service and .reg to removal of entries which (your link on previous few posts stated how the host system Windows is built). That would reguire 1 .reg file and the driver .sys file.

I just looked into .inf file and saw many device-ids listed over there. So I just created subkeys with the name (PCI#<device-id>) having values that are usually associated with keys in the CDDB such as Service, ClassGUID, DriverPackageId.

I hope that is what you meant. 

Needed:

* Service

* Registry for NIC functionality (Not sure, if this is optional or not because NICs has a lot of their functionalities stored in registry)

* CDDB

CDDB tells windows what device is, if not known, asks Service what to do where service answers that it should start a driver and how to start a driver.

You should add those to registry and copy files (including INF to tell windows the displaynames).

OR

You could try easy way out and try usage of 'devcon install driver.inf DEVICE\ID' style of dummy install or if you already have booted the hardware and host does actually have somekind of ghost device in system from NIC_2 might be possible to update that ghost device with actual inv through device manager.

Edited by genetix, 04 September 2013 - 01:37 PM.

Hello,

I too am looking for a way to forcibly install nic drivers for devices that have not been present before.

I've read your other threads ntdeveloper31 in other forums, both you and I are trying to accomplish the same thing. What have you found out so far? Is it possible to prevent LWF from binding upon nic install?

What is the exact problem anyway technically that causes the 0x7b?

What is the exact problem anyway technically that causes the 0x7b?

A STOP 0x0000007B error occurs when Microsoft Windows NT (and its descendants) are unable to mount the boot-volume. That means it's missing, which could be due to a missing device or a missing driver.

It's of relating to this, that's where I found ntdeveloper31's  topic here.

http://www.osronline...cfm?link=246000

It's of relating to this, that's where I found ntdeveloper31's  topic here.
 
http://www.osronline...cfm?link=246000

I've gone thr' following links while searching for the solution: http://www.etherboot...t_winnt_sanboot

Also, http://reboot.pro/to...rivers-directly / suggests that this problem might go away by adding reg entry for this new NIC inside "Critical Device Database". However doing some research on net suggests that it does not hold true when it comes to NIC.