I'm not sure what is causing mini-setup to prompt you for the driver. But I can't see how this is anything to do InjectMsd...
In principle, what's happening is simple enough. Mini-setup is searching the folders enumerated in the DevicePath registry key, looking for inf files that match devices present in the system. At some point during this process, it finds an inf that matches your virtual adapter, but some of the driver files that the inf file refers to aren't there. So it prompts you for them.
There is indeed no reason to specify an OemPnpDriversPath if you use ldprep.
Thanks for the reply. InjectMSD is what im using to inject the drivers found with the captureMSD tool... I dont think it's missing any drivers because if I type c:\drivers\msd in the path when promoted it works fine?
I'm running InjectMSD after LDprep runs... So that means my DevicePath Key does not have the Drivers/MSD folder.. Could that be the issue?
I followed this order.
REMEXEC374=h:\tools\ldprep /c /reg=Software1 /path=c:\drivers\pnp
REMEXEC375=reg unload HKLM\Software1
I did not dive into the auto it code but perhaps injectMSD just appends the Drivers/MSD to the end of the Devicepath key.. If that's the case then I guess that is not my issue...
InjectMsd doesn't do anything with the DevicePath key... Whether you run ldprep before or after injectmsd can't make a difference.
The way you have things set up, c:\drivers\msd indeed won't be listed in DevicePath. Why that would be a problem is not clear to me (doesn't cause me any pain). But it's worth trying if including c:\drivers\msd in DevicePath makes a difference (change the path parameter of ldprep to c:\drivers).
Another thing you could try is delete the inf file from c:\drivers\msd. InjectMsd doesn't need it and the machine will bott without it. You then may or may not want to have a copy of the inf & sys files under c:\drivers\pnp.
Deleting the INF file caused the computer to blue screen after reboot. I also added Drivers\msd to the Devicepath key in the registry and that did no help either.
Since I was only having this issue with the VMware machine, I decided to just add a line at the end of my OSD Script which copies the the MSD folder into the sysprep\I386 folder and that fixed the issue. Not sure why it happend though?
Thanks anyways for your help.