<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Adding Mass Storage (and other) Drivers to a WinPE Image</title><link>http://blogs.msdn.com/archon_team/archive/2005/02/09/MassStorageDriversInWinPE.aspx</link><description>Working in the Windows Setup team means we have to support a massive amount of hardware, which can vary tremendously across the company. This includes brand new machines that don’t have in box drivers or beta hardware that might have custom drivers. We</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Adding Mass Storage (and other) Drivers to a WinPE Image</title><link>http://blogs.msdn.com/archon_team/archive/2005/02/09/MassStorageDriversInWinPE.aspx#370761</link><pubDate>Fri, 11 Feb 2005 04:46:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:370761</guid><dc:creator>ribond</dc:creator><description>As a sidenote: DRVINST.EXE is a handy tool for adding device driver support to WinPE images.  And make sure that you uncomment any sections you use in WINPEOEM.SIF... &lt;br&gt;&lt;br&gt;And if you ever wonder what that crazy TXTSETUP.OEM syntax _really_ means just open the txtsetup.oem from any Adaptec driver package.  They do good work. </description></item></channel></rss>