triggering a batch file from within inf - ordering

NTDEV
1

Hi all,

I am able to trigger a batch file from within an inf file.
But the ordering seems to be off.
My intention is to first complete installing the driver (sys file) AND THEN trigger the batch file.
The driver is for a network adapter and the batch file is a simple script that automates the setting of the just installed network interface.
But what is really happening is that the batch file gets triggered first and blocks the completion of the driver installation.
How can i achieve what i am trying to do?
Do i need an autorun.inf or some such thing that serializes the driver installation and batch file triggering?

Thanks in advance.

2

Don’t use a batch file, use a coinstaller if you really want this.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

wrote in message news:xxxxx@ntdev…
> Hi all,
>
> I am able to trigger a batch file from within an inf file.
> But the ordering seems to be off.
> My intention is to first complete installing the driver (sys file) AND
> THEN trigger the batch file.
> The driver is for a network adapter and the batch file is a simple script
> that automates the setting of the just installed network interface.
> But what is really happening is that the batch file gets triggered first
> and blocks the completion of the driver installation.
> How can i achieve what i am trying to do?
> Do i need an autorun.inf or some such thing that serializes the driver
> installation and batch file triggering?
>
> Thanks in advance.
>
>
>

3

Dear Don,
OK. I will look into coinstaller. Can you give me a big picture of how this would work in a line or two? Is a coinstaller a sys file or dll file or an exe file that’s auto-launched? Where should i start digging on coinstallers (DDK as always would be a good start i guess)? Thanks.

4

It is a DLL, there are samples in the WDK. The co-installer will be called
for multiple events in the install process, including the driver having
been successfully installed.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

wrote in message news:xxxxx@ntdev…
> Dear Don,
> OK. I will look into coinstaller. Can you give me a big picture of how
> this would work in a line or two? Is a coinstaller a sys file or dll file
> or an exe file that’s auto-launched? Where should i start digging on
> coinstallers (DDK as always would be a good start i guess)? Thanks.
>
>