[Eagle710]

Is there anyway to make it seem(pretend) like a USB key has been unplugged from the system?

[Sponsor]

[Tripredacus]

As of PE v2.0, it seems to be pretty fast in the PnP of UFDs.

[Eagle710]

Is there anyway to pretend that I have unplugged it thought via command line?

[iamtheky]

http://quick.mixnmoj...sb-disk-ejector

how to use the command line

http://www.howtogeek...ific-usb-drive/

This post has been edited by iamtheky: 23 October 2009 - 08:09 AM

[Eagle710]

I install a driver when WinPE is loaded using DRVLOAD however the drivers does not kick in until the USB key is physically unplugged. I noticied that once the key is remove the registry detects the PCI device which was the driver I installed.
Any ideas?

[Tripredacus]

Why not inject the driver into your WIM? That way you wouldn't have to worry about Drvload

[Eagle710]

I tried injecting the driver however the driver doesn't take affect until I plug in and remove a USB key.

[Noise]

I've found in PE you have to inject the drivers using peimg (or dism), then edit the startnet.cmd file and drvload them also.

You could use a Diskpart script and the "rescan" command.

[Eagle710]

Noise, on Oct 28 2009, 03:26 PM, said:

I've found in PE you have to inject the drivers using peimg (or dism), then edit the startnet.cmd file and drvload them also.

You could use a Diskpart script and the "rescan" command.

Noise,

I have injected the drivers on the offline WinPE image and then you recommend that I edit the startnet.cmd to drvload them again?

[Eagle710]

It seems like when I remove the USB the drvinst.exe process runs and once completed the driver is enabled and setup.... any ideas?

Once removed the driver actually takes effect on the system.

This post has been edited by Eagle710: 02 November 2009 - 03:34 PM

[Noise]

Add this to your startnet.cmd in WinPE:

FOR /F %%i in ('DIR /B /ON "%SystemRoot%\inf\oem*.inf"') do (
	@ECHO	   Installing %%~ni
	DRVLOAD "%SystemRoot%\inf\%%~i" > NUL
)

Custom driver are injected in WinPE and their INF files are re-named to start with OEM. This little scriptlet loads all drivers at startup.

[Eagle710]

I actually tried this:
If the name of the driver is net4.inf should i change the oem*.inf ?

This didn't work when I tried to use it both within the startnet.cmd and just running via command line it still requires me to remove the USB key in order for the PCI device to obtain an device ID.

This post has been edited by Eagle710: 04 November 2009 - 10:29 AM

[Eagle710]

After having injected the driver into the offline WinPE image and checking which drivers are running on the system using DriverView it seems as though the driver is not running. Only when I remove the USB key does the driver appear as installed/activiated in WinPE. Any ideas?

[Eagle710]

So I have not determined what cause the driver to kick in after I unplug the USB key. However, I have found this little MS tool called Devcon.exe which is similar to Device Manager but using command line. I simply added the following command line into my winpeshl.ini to run at start and this allowed for the driver to activate.

Devcon.exe, /rescan