Jump to content

Recommended Posts

Posted

I am using WinPE 3.0 to update and secure erase my OCZ SSD. I injected the SSD and NIC drivers into WinPE.wim (x86, as boot.wim) and booted it from a USB stick. With diskpart I can see my SSD W7 installation. To do an update I use a tool called OCZToolBox. The latest version (3.02.06) cannot see my SSD but the older one does. However, if instead of injecting the driver I use drvload to install the same driver files, I can see the SSD with the latest. What is the difference in injecting the driver and using drvload? Here is a link to the thread on the OCZ forum. It contains lots of extraneous information but possibly some useful to those here. Thanks for any help/suggestions. Enjoy, John.


Posted

Thanks, Tripredacus. I guess I will be using drvload for the SSD driver unless OCZ can explain. The injected NIC driver seems to work fine. Thanks and enjoy, John.

Posted

Its probably how the INF is written. For example, an INF can be written to require a restart in order to have complete installation. This is one example of a type of driver that obviously does not work with drvload. It would be interesting to know whether that OCZ driver works if injected into a Windows 7 image... but it just might since WinPE and Win7 handles drivers a little bit differently.

Posted

Thanks, for your reply Tripredacus. I have had this SSD for about six months now and have always injected the driver into W7 Ultimate x64 with no problems. Most of the users on the OCZ forum use the 'Load Driver' button on the "Where do you want to install Windows" screen. I assume, perhaps erroneously, that Setup (WinPE version) is using drvload to install the driver. Thanks and enjoy, John.

Posted

Its likely possible to even prove that by editing the winpeshl.ini to no automatically run Setup.exe. Then you would have a chance to run ProcMon and profile Setup.exe when clicking that button. :angel

Posted

Tripredacus, thanks but you are way beyond me and my curiosity about the way Setup loads drivers. Enjoy, John.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...