View Single Post
  #11  
Old 02-27-2018, 05:52
bongos_man bongos_man is offline
Friend
 
Join Date: Aug 2016
Posts: 25
Rept. Given: 0
Rept. Rcvd 4 Times in 3 Posts
Thanks Given: 4
Thanks Rcvd at 25 Times in 14 Posts
bongos_man Reputation: 4
Quote:
Originally Posted by Kerlingen View Post
The driver is for a RAID controller and, like I wrote, driver.sys is signed both by the vendor and by Microsoft.
thank you for the clarification. distribution via windows update also, if i recall correctly, requires whql, so i figured the driver had gone through that process. i apologize for my tone; i should not have assumed that you might have not known about this detail (microsoft hardly documents it themselves).

Quote:
I can't install Windows if it doesn't detect any harddisk which could be used for installation.
If I install it with the default Microsoft driver and install the vendor driver on the running system, Windows will unload its own driver, which leads to an instant BSOD since the boot device becomes inaccessible.
I can only load the vendor driver during Windows setup, since WinPE is running from a RAM drive and losing access to the harddisk will not crash it.
is it mandatory that the windows in-box driver for your PCI\001 be working right now? in other words, can you add the vendor driver via the procedure outlined here for adding boot-critical drivers to winPE, install to a drive on the now-visible PCI\002, then use this installation to begin with the process i outlined?
Reply With Quote