oao, on Jan 14 2010, 07:51 PM, said:
1. Multiple INF files for one driver in the same directory e.g. Intel® Matrix Storage Manager Driver: it has IASTOR.INF and IAHCI.INF in the same directory, both of which I think are needed. If I specify One Driver to Insert I must choose one of them and then I DK if the other will be installed; if I try to select the other one too, nLite does not accept it from the same directory. So should I specify Multiple Drivers to insure both will be included?
No, they will be both included anyway. nLite will always copy the whole content (= all files) of the driver folder into the CD image.
By the way: An INF file is just a text file and not a driver. You can open each INF file with the Editor and read it. The INF files only contain the informations for the OS about how to get the driver proper installed.
2. One driver with multiple files in different directories e.g. nVidia graphics driver: it has the INF of the core driver in one directory and an INF for a HDMI driver in ahanother directory. Here my guess is that I need to specify each directory as one driver and insert them separately, as I doubt the graphics driver will also include the HDMI.
The NVIDIA Display (=graphics) driver and the HDMI Audio driver are different drivers. So they have to be integrated separately. nLite will do that for you, if you choose the multiple driver folder option.
3. Multiple INFs for multiple drivers in the same directory e.g. Intel Mobile Chipset. Here there is a double problem: there are multiple INF files for the same chipset family all of which must be installed and multiple INF files for other chipset families none of which must be installed. The thing is I cannot tell from the names of the files which should be in and which out. So if I specify One-Driver to Insert, I don't know which INFs to select. But if I specify Multiple Drivers, all of them will be selected and I dk is that's correct -- would they all be installed?
All INF files will be integrated into the OS CD, no matter
a ) which INF file you checked and
b ) if you choose the single or the multiple driver option.
As I have written above, an INF file is not a driver.
By the way: The Intel chipset "drivers" (= "INF Update Ultility") don't contain any real driver. Real drivers are the files with the extension ."SYS".