jlindy

The presetup.cmd I'm using invokes WatchDriverSigningPolicy.exe. Here's and excerpt from setuplog setuplog 11:10:09,d:\srvrtm\base\ntsetup\syssetup\log.c,981,,SETUP: oem driver not logged: d:\drivers\005_storage\symmpi.sys -> C:\WINDOWS\system32\DRIVERS\symmpi.sys. 04/04/2005 11:10:09,d:\srvrtm\base\ntsetup\syssetup\log.c,316,,d:\drivers\005_storage\symmpi.sys was copied to C:\WINDOWS\system32\DRIVERS\symmpi.sys. 04/04/2005 11:10:09,d:\srvrtm\base\ntsetup\syssetup\syspnp.c,5325,,SETUP: SetupDiCallClassInstaller(DIF_REGISTER_COINSTALLERS) succeeded. Device = LSI Adapter, SAS 3000 series, 4-port (w/1064)(ScsiPort) 04/04/2005 11:10:09,d:\srvrtm\base\ntsetup\syssetup\syspnp.c,5337,,SETUP: SetupDiCallClassInstaller(DIF_INSTALLINTERFACES) succeeded. Device = LSI Adapter, SAS 3000 series, 4-port (w/1064)(ScsiPort) 04/04/2005 11:10:10,d:\srvrtm\base\ntsetup\syssetup\syspnp.c,5377,,SETUP: SetupDiCallClassInstaller(DIF_INSTALLDEVICE) suceeded. Device = LSI Adapter, SAS 3000 series, 4-port (w/1064)(ScsiPort) 04/04/2005 11:10:10,d:\srvrtm\base\ntsetup\syssetup\syspnp.c,3154,,SETUP: Device successfully installed. 04/04/2005 12:37:19,d:\srvrtm\base\ntsetup\syssetup\log.c,316,,Setup detected that the system file named [c:\windows\system32\drivers\symmpi.sys] is not signed properly by Microsoft. This file has been restored to the correct Microsoft version to maintain system stability.

I've followed the directions in the forum for installing mass storage from CD with the replacement setup.exe, presetup.cmd, .... I have it working. The problem is the driver I'm installing is a newer version of a inbox driver and the newer version is unsigned. WFP (SFC) keeps replacing the newer version with the signed version and during the real O/S boot, the system panics with inaccessable boot device. I need help on getting around this. One ugly workaround (and time consuming), is to boot from CD again, select repair and copy the newer driver to ...system32\drivers directory - this seems to work. Thanks