James Hawkins wrote:
Internally, there will be three main install functions: install_init,
which will open the INF, make sure it's legit, and other
initializations, spapi_install, which will call setupapi to install
the base INF commands, and adv_install, which will parse the install
section and
"James Hawkins" <[EMAIL PROTECTED]> writes:
> Internally, there will be three main install functions: install_init,
> which will open the INF, make sure it's legit, and other
> initializations, spapi_install, which will call setupapi to install
> the base INF commands, and adv_install, which will
On 3/31/06, Dimi Paun <[EMAIL PROTECTED]> wrote:
>
> Or maybe simpler, instead of storing just the function pointer as
> the value for the map, store a structure that has 2 fields:
> -- priority
> -- function
>
> So than you just call things as:
> for (i=0; i < MAX_PRIO; i++)
> run_adv_
On Thu, 2006-03-30 at 23:12 -0600, James Hawkins wrote:
> there will probably be three or four maps, the functions in the maps
> grouped according to the order in which the commands should be run.
Or maybe simpler, instead of storing just the function pointer as
the value for the map, store a st
Hey,
As you've probably noticed, I've been working on implementing advpack
for a couple months now; a lot of progress has been made, and I'm glad
to say that the end is in sight. The rest of this email details the
game plan for finishing advpack.
advpack has five main install functions: DoInfIns
