<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[DriverPacks.net Forum - all drivers on drive... not by KTD]]></title>
		<link>http://forum.driverpacks.net/viewtopic.php?id=2289</link>
		<description><![CDATA[The most recent posts in all drivers on drive... not by KTD.]]></description>
		<lastBuildDate>Tue, 22 Jan 2008 15:22:39 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: all drivers on drive... not by KTD]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=17157#p17157</link>
			<description><![CDATA[<p>delete the folder </p><p>the default location is windows\driverpacks or more specifically %SystemRoot%\DriverPacks</p><p>don&#039;t you have HAL issues when you use this technique?</p>]]></description>
			<author><![CDATA[null@example.com (OverFlow)]]></author>
			<pubDate>Tue, 22 Jan 2008 15:22:39 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=17157#p17157</guid>
		</item>
		<item>
			<title><![CDATA[Re: all drivers on drive... not by KTD]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=17156#p17156</link>
			<description><![CDATA[<p>Right now I use KTD in my installs into VMware for imaging and restoration most PCs.&nbsp; Note I am not using sysprep only the &#039;Standard IDE&#039; driver trick to facilitate booting on most PCs<br />.&nbsp; The problem is the 1.2GB of drivers stays on the new destination PC.&nbsp; How can I facilitate a KTD removal from the newly imaged PC after driver detection is over?</p><p>Thanks,<br />-felipe</p>]]></description>
			<author><![CDATA[null@example.com (felipegeek)]]></author>
			<pubDate>Tue, 22 Jan 2008 15:13:34 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=17156#p17156</guid>
		</item>
		<item>
			<title><![CDATA[Re: all drivers on drive... not by KTD]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=16889#p16889</link>
			<description><![CDATA[<p>if drivers are installed during setup then they are cached locally on the machine, without KTD.</p><p> (windows\system32\drivers\) and (Windows\inf) <br />and most notably (WINDOWS\system32\ReinstallBackups)</p><p>you may use KTD to keep only the packs you wish, however i don&#039;t think you need it if you are aware of <br />&nbsp; &nbsp; &nbsp; WINDOWS\system32\ReinstallBackups</p>]]></description>
			<author><![CDATA[null@example.com (OverFlow)]]></author>
			<pubDate>Sun, 13 Jan 2008 22:15:35 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=16889#p16889</guid>
		</item>
		<item>
			<title><![CDATA[Re: all drivers on drive... not by KTD]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=16866#p16866</link>
			<description><![CDATA[<p>In South Arkansas we have a problem with &quot;I got this from my XXX&quot;. Where is the disk that came with it? HUH? What disk?<br />So I like to keep the LAN and modem packs on the drive. As long as those two are working, I can get any others I may need.</p>]]></description>
			<author><![CDATA[null@example.com (jhsands)]]></author>
			<pubDate>Sat, 12 Jan 2008 21:47:24 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=16866#p16866</guid>
		</item>
		<item>
			<title><![CDATA[Re: all drivers on drive... not by KTD]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=16845#p16845</link>
			<description><![CDATA[<div class="quotebox"><cite>jhsands wrote:</cite><blockquote><p>If DPbase extracts all the 7z files to the hard drive, is there not a way to leave them there?</p></blockquote></div><p>Yes. The way to just leave them there after we are done is called KTD (Keep The Driver)</p><br /><br /><div class="quotebox"><cite>jhsands wrote:</cite><blockquote><p>Why go through all that extracting, just to install all DP through KTD when you can just leave them on there?</p><p>TIA<br />JHS</p></blockquote></div><p>DriverPacks does not install drivers through KTD...</p><p>In fact KTD is not recomended by me personaly. it is only good for what i call a Test Bed computer. like a technicians machine on his work bench to use for testing customers cards. (quickly identifying if an issue is hardware or software releated.)</p><p>In any other environment; <br />if you are adding hardware you are physically going to be at the machine and have it open anyway. might as well take the latest greatest driver?&nbsp; </p><p>I assume if it is new it won&#039;t need hardware added soon. why burn 1.5gig of HDD space on out dated drivers? </p><p>Turn KTD off unless you plan on rotating hardware on the machine regularly (like a test machine)<br />if you are running KTD on a test machine it is likely that you will be reloading it often, and would then be a good DriverPacks tester and have the latest packs all the time.</p>]]></description>
			<author><![CDATA[null@example.com (OverFlow)]]></author>
			<pubDate>Fri, 11 Jan 2008 01:25:00 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=16845#p16845</guid>
		</item>
		<item>
			<title><![CDATA[all drivers on drive... not by KTD]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=16833#p16833</link>
			<description><![CDATA[<p>If DPbase extracts all the 7z files to the hard drive, is there not a way to leave them there?<br />Why go through all that extracting, just to install all DP through KTD when you can just leave them on there?</p><p>TIA<br />JHS</p>]]></description>
			<author><![CDATA[null@example.com (jhsands)]]></author>
			<pubDate>Thu, 10 Jan 2008 05:52:27 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=16833#p16833</guid>
		</item>
	</channel>
</rss>
