Missing files when parsing inf file

Hello everyone,

I wrote some code more than 6 years ago that does inf file parsing and
collects the files that are referenced from an inf file and creates a
"driver package" for the client management product that we sell. Now I
suddenly received a driver that a customer of ours failed to package
properly because my inf parsing code seems to ignore a couple of files
and at runtime the installation prompts for them. The files that are
missing are all under the "lang\hdmi" subdirectory of the directory
where the inf file resides and under this subdirectory there are
subdirectories like ara, chs, cht, csy ... which obviously contain
language specific DLLs. However, I can't for the life of me find out,
how these files in this "lang\hdmi" subdirectory are referenced from
the inf file, so I dunno why my code fails to find these files from
parsing the inf file.

Is there anything new in the inf file specification like a "lang"
subdirectory that always and automatically has to be considered part of
the driver files? Could it be that the CoInstaller in this driver
somehow determines the system's locale, adds those files in the
subdirectory dynamically and now prompts for the associated files? Is
something like that possible at all? If that were the case, I do
understand why my parsing routines don't detect that these files belong
to the driver files, but would that be good practice, to dynamically add
files from coinstaller code?

Any help appreciated,

--
Stefan Kuhr

Stefan Kuhr wrote:
> However, I can't for the life of me find out, how these files in this
> "lang\hdmi" subdirectory are referenced from the inf file, so I dunno
> why my code fails to find these files from parsing the inf file.

Two possibilities come to mind:


(a) Your customer selects these files (or directories) with a
language-dependent string section:

http://msdn.microsoft.com/en-us/library/ms790204.aspx


(b) Your customer uses a custom co-installer that installs/copies the
files, and thus they are not referenced in the INF.

http://www.osronline.com/ddkx/install/coinst_5p0n.htm


In either case your tool probably needs an option to include additional
custom files.

Hello Hagen

Hagen Patzke wrote:
> Stefan Kuhr wrote:
>> However, I can't for the life of me find out, how these files in this
>> "lang\hdmi" subdirectory are referenced from the inf file, so I dunno
>> why my code fails to find these files from parsing the inf file.
>
> Two possibilities come to mind:
>
>
> (a) Your customer selects these files (or directories) with a
> language-dependent string section:
>


My code covers this situation, because I parse the inf file several
times with different thread locales set. There is no indication in this
particular inf file from the strings section to the files in the
"lang\hdmi" subdirectory. Another strange thing is also that there is
only one strings section for English, no other strings sections in
dot-langid notation.


>
> (b) Your customer uses a custom co-installer that installs/copies the
> files, and thus they are not referenced in the INF.
>
> http://www.osronline.com/ddkx/install/coinst_5p0n.htm
>

That's what I suspect as well.


Thanks for giving an answer to my question.

--
Stefan Kuhr