Ok, since I build now functional CMD with 1 extra free tool [subtopic_level3] -> Data. I think it's time to modify this original post a bit. Took me a lot of hours total to reach the bottom and identify every single possible entry at any architecture MS Driver INF file and currently working on last set of data, but I think I am getting there. I think in few days I get something solid going on.
---
Here is test example of 1 singular extremely hard to parse INF file from 'Promise Technology' which is simply incorrectly built against MS Driver INF guidelines and I am still wondering how this kind of Driver INF could ever possibly register to Windows XP correctly. However, I am going to use it as extremely hard example of parsing through.
Note that Architecture and OS versioning is supported, so, basically this kinda scenario would be capable of parsing through inf database which would for example include any OS versions of the INF and collect that data to future file renaming or copying to install the actual driver. Also AddReg, Delreg entries are located by where they come from which means "HKR" at Subtopic_level3 DATA can be parsed correctly to include manufacturer specified "Relative" registry entry base. Because you will know what actually executed the AddReg/DelReg entry topics.
EXAMPLE ONLY:
http://www64.zippyshare.com/v/32895619/file.html
MD5: 5bc055552e067d704938d75b75108f0d
Disclaimer:
I assume everyone even looking this topic or the file above understands that launching any kind of executable/script/batch file from anywhere at web has always risk. No one is perfect there can be some sort of unforseen system specific error or other unforseen execution taking place or simply error by me which are still user fault not mine as you are the one executing it not me.
So, just saying use this with caution.
Usage:
1. Extract to drive:\somedir
2. Leave the ULSATA2.inf to folder. (This file is used in this example CMD as base of information it will work against other INF files too, but this is v0 as in not generally functional example.)
3. inf_parser.cmd will build core topic and subtopic_level 1 -->> subtopic_level 3 .DAT files (these are topics only) .RAW (these are data only)
I am working on v0.01 of this parser now. I think I can map every single possible entry these is on any INF with few days put to it.