<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[DriverPacks.net Forum - OPEN: change OemPnPDriversPath to use a FTP server]]></title>
		<link>http://forum.driverpacks.net/viewtopic.php?id=211</link>
		<description><![CDATA[The most recent posts in OPEN: change OemPnPDriversPath to use a FTP server.]]></description>
		<lastBuildDate>Mon, 26 Jun 2006 13:15:17 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: OPEN: change OemPnPDriversPath to use a FTP server]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=1026#p1026</link>
			<description><![CDATA[<p>Thxs for the fast reply.</p><p>Do you have a copy of your Cmdlines.txt? <br />I like to reduce my network bandwith and do not want to copy drivers that the pc doesn&#039;t need.<br />So the network card is setup in a late stadium. If i copy only the network card drivers and set de OEMpnpDriversPath to a networkshare.</p><p>Will Windows detect these drivers at first login ?</p>]]></description>
			<author><![CDATA[null@example.com (mdriessen)]]></author>
			<pubDate>Mon, 26 Jun 2006 13:15:17 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=1026#p1026</guid>
		</item>
		<item>
			<title><![CDATA[Re: OPEN: change OemPnPDriversPath to use a FTP server]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=1025#p1025</link>
			<description><![CDATA[<p>OemPnPDriversPath is utilized at T-39 (the very beginning) of the GUI portion of setup.&nbsp; At this point your NIC has not been installed yet, therefor it cannot access the network to get the drivers.&nbsp; The &quot;best&quot; way to do drivers w/ RIS is to use Method 2 and just copy down all of the DriverPacks to the system drive.&nbsp; Method 1 will work just fine, but now you&#039;re doing a copy operation on an additional 5,000 or so files.&nbsp; Much faster to copy a dozen larger files than thousands of tiny ones.</p><p>To back tack a little here - During the PnP enumeration of devices you probably notice near the progress bar that it says Installing Devices (or something similar).&nbsp; The very next thing after that is &quot;Configuring Network&quot;.&nbsp; It&#039;s not until that is finished that you have network access.&nbsp; Cmdlines.txt has full blown Internet access for instance.&nbsp; I know this for sure as I download files to the target computer during cmdlines.</p>]]></description>
			<author><![CDATA[null@example.com (RogueSpear)]]></author>
			<pubDate>Mon, 26 Jun 2006 12:28:30 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=1025#p1025</guid>
		</item>
		<item>
			<title><![CDATA[OPEN: change OemPnPDriversPath to use a FTP server]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=1023#p1023</link>
			<description><![CDATA[<p>I&#039;ve a question?<br />I&#039;m using RIS 2003 in a network and wanna setup a unattended XP installation with all kind of drivers.<br />So i was reading the forum, and there are some usefull idea&#039;s.<br />But there is one thing that&#039;s not clear to me and i think i forget something.</p><p>Why would you copy the drivers to the local machine by putting it in the folder $oem$\$1<br />Why not set the OemPnPDriverspath to a network share so that it only copy the drivers that de pc needs.</p><p>And if that&#039;s possible, can i set the OemPnPDriversPath to a ftp server so there is one database.</p>]]></description>
			<author><![CDATA[null@example.com (mdriessen)]]></author>
			<pubDate>Mon, 26 Jun 2006 11:29:19 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=1023#p1023</guid>
		</item>
	</channel>
</rss>
