<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[DriverPacks.net Forum - Injecting all of driverpacks to computer before image with DriverForge]]></title>
	<link rel="self" href="http://forum.driverpacks.net/extern.php?action=feed&amp;tid=3577&amp;type=atom"/>
	<updated>2009-03-17T00:55:10Z</updated>
	<generator>PunBB</generator>
	<id>http://forum.driverpacks.net/viewtopic.php?id=3577</id>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=30072#p30072"/>
			<content type="html"><![CDATA[<p>let&#039;s hope &quot;if newer&quot; is real smart and weighs from the sub-sub-sys down because version and date were (in oem drivers) not always trustworthy and they oft had common generic.</p><p>the driver update site at MSFT is getting much better too.<br />NON-critical drivers and those made obsolete or never in your &quot;vanilla&quot; are most likely picked up by an online msft driver search.<br />This takes one user setting for driver install. &#039;always allow online driver search&quot; (I have to translate what I see.. it is one tick in a gui.)</p>]]></content>
			<author>
				<name><![CDATA[Jaak]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=327</uri>
			</author>
			<updated>2009-03-17T00:55:10Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=30072#p30072</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=30067#p30067"/>
			<content type="html"><![CDATA[<p>There&#039;s a option in dpinst.exe that allows you to override &quot;if newer&quot;. I just don&#039;t remember what it is.</p>]]></content>
			<author>
				<name><![CDATA[stamandster]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2760</uri>
			</author>
			<updated>2009-03-16T11:43:34Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=30067#p30067</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=29657#p29657"/>
			<content type="html"><![CDATA[<p>I have made an image using OSP and injecting all the drivers. So far all hardware that i have imaged to works great.<br />I still have one little issue though that it prompts me on just a few drivers saying that i have newer ones in the image then the ones i am trying to use. I have a topic started over at barts forums about it if anyone has any input <img src="http://forum.driverpacks.net/img/smilies/smile.png" width="15" height="15" alt="smile" /><br /><a href="http://www.911cd.net/forums//index.php?showtopic=22662">http://www.911cd.net/forums//index.php?showtopic=22662</a></p>]]></content>
			<author>
				<name><![CDATA[JustusIV]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=6008</uri>
			</author>
			<updated>2009-02-28T15:17:04Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=29657#p29657</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=29633#p29633"/>
			<content type="html"><![CDATA[<p>Yes i believe i am already doing this via your method through OSP. Fantastic tool btw <img src="http://forum.driverpacks.net/img/smilies/smile.png" width="15" height="15" alt="smile" /><br />I dont have any issue booting any of our hardware. And any that BSOD in the past was made short work of with OSP/BartPE/DriverPacks.<br />Thank you all!</p><p>*EDIT*<br />added more credit to all the tools <img src="http://forum.driverpacks.net/img/smilies/smile.png" width="15" height="15" alt="smile" /></p>]]></content>
			<author>
				<name><![CDATA[JustusIV]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=6008</uri>
			</author>
			<updated>2009-02-27T14:05:19Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=29633#p29633</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=29601#p29601"/>
			<content type="html"><![CDATA[<p>Your absolutely right. You&#039;ll have to add the appropriate drivers manually in the sysprep.inf. I assumed he was doing this already.</p>]]></content>
			<author>
				<name><![CDATA[stamandster]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2760</uri>
			</author>
			<updated>2009-02-26T23:07:16Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=29601#p29601</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=29597#p29597"/>
			<content type="html"><![CDATA[<p>SPDrvScn won&#039;t work for mass storage drivers. It just updates the &#039;DevicePath&#039; key in registry, but doesn&#039;t enter &#039;CriticalDeviceDatabase&#039; or corresponding service entries. As such, on new hardware you will not survive first boot.</p><p>Regards,<br />Galapo.</p>]]></content>
			<author>
				<name><![CDATA[Galapo]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2906</uri>
			</author>
			<updated>2009-02-26T22:17:56Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=29597#p29597</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=29594#p29594"/>
			<content type="html"><![CDATA[<p>No it&#039;s not that bad. It&#039;s only going to install what it needs to install.</p>]]></content>
			<author>
				<name><![CDATA[stamandster]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2760</uri>
			</author>
			<updated>2009-02-26T19:55:27Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=29594#p29594</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=29593#p29593"/>
			<content type="html"><![CDATA[<p>Currently i am using Offlinesysprep which looks to useing SPDrvScn on the back end of things.&nbsp; Is it a bad idea to use SPDrvScn for all the driver packs? I see it says it can take a long time to go through the drivers but speed is the least of my concerns.</p>]]></content>
			<author>
				<name><![CDATA[JustusIV]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=6008</uri>
			</author>
			<updated>2009-02-26T19:54:38Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=29593#p29593</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=29592#p29592"/>
			<content type="html"><![CDATA[<p>Yes exactly... </p><p>You can use vernalex&#039;s sysprep driver importer to create a list of drivers and install post sysprep</p><p>You&#039;ll want to have the exe in the same folder as this batch script</p><div class="codebox"><pre><code>@ECHO OFF
ECHO Setting Driver Signing Policy to OFF
START WatchDriverSigningPolicy.exe
ECHO Importing Drivers to Registry
START /WAIT spdrvscn /p c:\D /e inf /d %windir%\inf /a /s /q
ECHO Starting Driver Manager
START devmgmt.msc
ECHO Starting Install of Hardware
START /WAIT RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers
taskkill /f /im WatchDriverSigningPolicy.exe
taskkill /f /im mmc.exe</code></pre></div>]]></content>
			<author>
				<name><![CDATA[stamandster]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2760</uri>
			</author>
			<updated>2009-02-26T19:37:53Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=29592#p29592</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=29591#p29591"/>
			<content type="html"><![CDATA[<p>Ok maybe i miss understood what DriverForge was doing. I thought it was prepping all the drivers so that it would have them for plug n play. What your telling me is it only install the drivers of the hardware you have?</p>]]></content>
			<author>
				<name><![CDATA[JustusIV]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=6008</uri>
			</author>
			<updated>2009-02-26T19:35:08Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=29591#p29591</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=29590#p29590"/>
			<content type="html"><![CDATA[<p>Driverforge wasn&#039;t designed to inject drivers into the registry beforehand. Driverforge was designed to be a post sysprep tool.</p><p>However, I will be adding that functionality at some point soon to FindHWIDs. You could always use Vernalex&#039;s Sysprep Driver scanner, which is exactly what my addition would be doing.</p>]]></content>
			<author>
				<name><![CDATA[stamandster]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2760</uri>
			</author>
			<updated>2009-02-26T19:20:08Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=29590#p29590</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Injecting all of driverpacks to computer before image with DriverForge]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=29589#p29589"/>
			<content type="html"><![CDATA[<p>Does anyone see any reason why it would be a bad idea to inject all of the driver packs using DriverForge before i image a machine and ghost it and roll it out to new hardware? Currently i inject the correct drivers via syspreping. It works but i would like to not have to do that step and if i inject all the drivers before hand windows should have them all correct?<br />Any thoughts are welcome<br />Thanks<br />JustusIV</p>]]></content>
			<author>
				<name><![CDATA[JustusIV]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=6008</uri>
			</author>
			<updated>2009-02-26T19:14:23Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=29589#p29589</id>
		</entry>
</feed>
