Soooo did that work?

or are there other ideas somewhere else I need to read about :-)

hmm... :-)

I did use kickarse hwid tool to build sysprep MassStorage list :-)  btw what a very nice tool it saved me hours(days, Weeks) of work :-) 

The errors are triggered by sysprep in the setupapi.log file I found

#E245 The device installation digital signature failure policy has been elevated from Ignore to Warn due to a proposed replacement of a protected system file.

there must be a way to override this elevation setting so we can start SYSPREP and walkaway. :-)

7.  If you want to include the MassStorage DriverPack into the Mass Storage section of your sysprep.inf, I recommend using FindHWIDs, found here, using the SysPrep option, as it will export the MassStorage format that you need for your sysprep.inf file.  If you don't plan on including the MassStorage DriverPack, skip this step.

this is the problem step..... I understand why and how to use the rest of the steps but when it comes to the integrating MassStorage drivers I get too many prompts for "the software you are installing for Driver xyz hasnt passed windows logo testing" 

I have disabled the the driver signing in windows and in the sysprep.inf but it still asks for "Continue Anyway" or "Stop Installing"

is there a way to determine which drivers arent signed?
or
a way the gets around this prompt

Got the below method from http://www.mydigitallife.info/2007/12/0 … indows-xp/

but this doesnt seem to work for me i have double confirmed the settings and during sysprep it will not install the drivers
is there another way to integrate to driverpacks into a SYSPREP build.

***Start
It’s pretty annoying to see the warning dialog prompted every now and then, and some more it delays the completion of device driver installation, in some cases wasting time when users forget to monitor the progress and leave the installation to run on its way, stopping at unsigned driver dialog indefinitely waiting for user input.

Here’s the trick to suppress the unsigned uncertified driver warning and force installation to continue automatically.
Right click on My Computer then select Properties to open System Properties.
In “System Properties† dialog box, select the Hardware tab.
Click on Driver Signing button.


In the “Driver Signing Options† dialog box, under “What actions you want Windows to take?† section, three levels of actions on digital signature verification is provided, with default as Warn - Prompt me each time to choose an action. Default will generate the Hardware Installation or Software Installation dialog box as shown earlier whenever an unsigned driver is detected.



To suppress and skip the warning dialog and install unsigned driver automatically, select the radio button for Ignore - Install the software anyway and don’t ask for my approval.

You can also select Block - Never install unsigned driver software to NOT INSTALL any uncertified driver - no question asked, and no way to change during installation - so it’s not recommended.
In “Administrator option† section, tick the check box for Make this action the system default.
Click on OK button twice to exit.

Above methods works for both Windows XP Professional and Windows XP Home edition. For XP Professional, users can use group policy to enforce the no warning dialog rule too.
Click on Start button, then click on Run.
In the Run box, type gpedit.msc, then press Enter.
Expand User Configuration.
Expand Administrative Templates.
Select System folder in the tree.
Right click on Code signing for device drivers, and then select Properties.
In the “Settings† tab, you should see “Enable† as the default action. Select Ignore from the drop down list to silently allow all unsigned drivers to install.

Users can also select Disable to stop all unsigned drivers installation, which cannot be overrode during installation process.

Once you have decided which method is best for you
Click on OK button.

Reboot PC so new settings take effect

Now you don’t have to worry about clicking on Continue Anyway when installing a new device (or old device) to let Windows use the unsigned driver.
***END