OK, so, don’t do that. Instead of having a massive extension driver that goes
to all systems, have a bunch of tiny extension drivers, each of which only goes
to the right system.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Vincent Wang <vincent0wang@xxxxxxxxxxx>
Sent: Tuesday, May 7, 2019 8:48:35 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: DCH INF and Cab file auto extraction
Hi Mathew,
"This should have only one thing in it – the data file specific."
Yes, we are doing this base + ext. The only difference is that our data file in
the ext is the Cab file per specific model.
That's why the auto expand of the cab is needed at Ext INF level.
Best REgards
Vincent
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Matthew van Eerde <dmarc-noreply@xxxxxxxxxxxxx>
Sent: Tuesday, May 7, 2019 11:09 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: DCH INF and Cab file auto extraction
As I understand it, the recommended approach is to have a base driver package
which is the single thing that READS the data – the .dll or the service or the
driver, whatever it is. This should use broad targeting without CHIDs.
Then if you want to have specific settings for different kinds of machine make
and models, create an extension driver for each make and model. This should
have only one thing in it – the data file specific to that make and model. This
would be targeted to the particular makes and models of machines with those
specific settings.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Vincent Wang <vincent0wang@xxxxxxxxxxx>
Sent: Tuesday, May 7, 2019 6:51:50 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: DCH INF and Cab file auto extraction
Hi Matthew,
To support larger number for devices, we would need .cab file to contain data
specific to that model.
Otherwise, we'll have a very long INF and large number of files to keep track
in code. Not something easy to maintain in long run, and keep up with the twice
a year RS cadence...
Best Regards
Vincent
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Matthew van Eerde <dmarc-noreply@xxxxxxxxxxxxx>
Sent: Tuesday, May 7, 2019 9:28 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: DCH INF and Cab file auto extraction
Why do you want to do that? The driver is already a .zip file.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Vincent Wang <vincent0wang@xxxxxxxxxxx>
Sent: Tuesday, May 7, 2019 6:15:40 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] DCH INF and Cab file auto extraction
Hi all,
I'd like to use a .cab file as a container of a larger number of files in a DCH
INF driver package.
I can create the INF and copy the .cab file into a folder under system32.
however I didn't find any documentation on how to set the .cab auto extract
after installation.
Can this be done within the INF syntax or I need to create other tool for this
to happen?
Thanks
Best REgards
Vincent
