fac007 Posted December 3, 2004 Posted December 3, 2004 HI folks any ideas on this. during the install after the 2nd restart during runonce.cmd i get 5 or 6 Hardware device pop ups saying the driver is not certified. If I press continue it carries on fine. The drivers are Audio codec, Video Codec and a few other I cant remeber. I thought it might be DriverSigningPolicy=Ignore but without that it gets a blue screen and refuses to boot into windows. If I put it back in I get the 5 or 6 pop ups which I have top click continue.Any ideas (its a SP2 slipstreamed version using nlite, with SP1 it was fine)here is my winnt [Data] MsDosInitiated = 0 UnattendedInstall = Yes[unattended] UnattendMode = FullUnattended UnattendSwitch = Yes OemPreinstall = Yes OemSkipEula = Yes FileSystem = * WaitForReboot = No DriverSigningPolicy=Ignore TargetPath = "\Windows" Hibernation = No KeyboardLayout="United Kingdom"[setupParams] SkipMissingFiles = Yes[GuiUnattended] EncryptedAdminPassword = No AdminPassword = "123456" TimeZone = 85 OEMSkipRegional = 1 OemSkipWelcome = 1[userData] ProductKey = "" FullName="user" OrgName="unknown" ComputerName=*[RegionalSettings] Language = 0809[TapiLocation] CountryCode=44 Dialing=Tone [Networking] InstallDefaultComponents=Yes [identification] JoinWorkgroup=WORKGROUP
benners Posted December 4, 2004 Posted December 4, 2004 try adding Nondriversigningpolicy = Ignore under unattended
fac007 Posted December 5, 2004 Author Posted December 5, 2004 yep thanks for that I tried it but now when ive installed windows with it I get unnasinged driver warnings for every driver I install. Is there some registry setting which can turn this off or to ignore when in windows?
benners Posted December 5, 2004 Posted December 5, 2004 I have this code in my tweaks reg file ;## When Windows Detects A Driver File Without A Digital Signature, Ignore ####[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Driver Signing]"BehaviorOnFailedVerify"=dword:00000000 more info here
Tsunami Posted December 5, 2004 Posted December 5, 2004 try adding Nondriversigningpolicy = Ignore under unattendedIt's DriverSigningPolicy = IgnoreI have this code in my tweaks reg file ;## When Windows Detects A Driver File Without A Digital Signature, Ignore ####[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Driver Signing]"BehaviorOnFailedVerify"=dword:00000000 more info hereNote that that tweak probably only works on 2000. The following tweak should work for XP:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing]"Policy"=hex:00
benners Posted December 5, 2004 Posted December 5, 2004 @TsunamiNote that that tweak probably only works on 2000. The following tweak should work for XP: this is the reg key set when using the group policy editor in XP ProBoth the driver entries are valid, I picked the Nondriversigningpolicy up from this board, think it was a link to a page on gosh's website
fac007 Posted December 6, 2004 Author Posted December 6, 2004 Hi I tried Benners method and although in system properties trhe option to ingnore unnasigned drivers is set. I get a unasihned driver warning for all harware on the system even the hardwrae thats definatly ok, which is a pain im going to try Tsunamis method.
fac007 Posted December 6, 2004 Author Posted December 6, 2004 I’ve tried both methods now (sorry my spelling deserted me in my last post)I’ve tried both methods now and every piece of hardware gets an unassigned driver warning. It starts with audio drivers then hardware then when windows is installed every hardware I add gets an unassigned driver warning.What’s changed from SP1 to SP2 all I’ve done is used nlite to slipstream SP2 and now I’ve got unassigned driver warnings.With DriverSigningPolicy=Ignore off windows fails to install so I have to put it in Without DriverSigningPolicy=Ignore I get unassigned driver warnings, Nondriversigningpolicy = Ignore doesn’t seem to do anything I get the same issues.Surely everyone else out there has managed to get SP2 slipstreamed without this issue. Shall I not use nlite?Please help
fac007 Posted December 7, 2004 Author Posted December 7, 2004 fixed this issue quite simply didnt use nlite to slipstream used the dos prompt integrate methos and now works finethanks for all suggestions and help
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now