Deployment and Imaging Group

Let’s face it, it is not that easy in some cases to locate the best matching driver for your HDD or NIC to use in WinPE as your PreOS.
Implementing one driver after the other in to your PreOS (WinPE) to test the driver then under that PreOS is a bit time consuming. Further the list of drivers in the library will explode and it will be hard a month later to remember which driver was the working one.
(Of course you could do such testing with a copy of your PreOS to avoid this problem)

Best and fastest way would be to test the driver directly under WinPE.
This require a bit of Preparation:
Create a bootable CD/DVD/USB put all drivers that you think will work on separate USB pen drive.
When you boot your machine exit the ghost GUI interface. In command line navigate to your USB pen drive with the drivers.

The test Procedure:
Step 1: Access the driver which are in F:\drivers\intel1 (on the USB pen drive). For this example.

X:\>f:
F:\>cd drivers
F:\drivers\cd intel1
F:\drivers\intel1>

Step 2:Load driver
F:\drivers\intel1>drvload driver.inf

Step 3:Assign a static IP address:
F:\drivers\intel1>netsh interface ipv4 set address "local area connection" static 10.0.0.2 255.255.255.0 10.0.0.1

Or you can assign a DHCP address:
F:\drivers\intel1>netsh interface ipv4 set address "local area connection" dhcp

Step 4: Verify results
with ipconfig /all
You can try to reconnect to the session using X:\Ghost32\ghost32.exe

This procedure is documented as well in the Symantec Knowledge Base:
TECH122799:How to try different network drivers in WinPE without using GhostBootWizard and with no need to reboot.
http://www.symantec.com/docs/TECH122799

I just wanted to use the option to highlight the procedure again to everybody.