<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[DriverPacks.net Forum - DriverPacks & nLite - in what order?]]></title>
	<link rel="self" href="http://forum.driverpacks.net/extern.php?action=feed&amp;tid=1988&amp;type=atom"/>
	<updated>2007-10-22T01:00:07Z</updated>
	<generator>PunBB</generator>
	<id>http://forum.driverpacks.net/viewtopic.php?id=1988</id>
		<entry>
			<title type="html"><![CDATA[Re: DriverPacks & nLite - in what order?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=15142#p15142"/>
			<content type="html"><![CDATA[<p>I have noticed that sometimes it is the end of line characters that screws up the winnt.sif file.&nbsp; Here&#039;s my exact winnt.sif file, minus a couple entries for legal reasons.&nbsp; It is a perfectly valid file, verified to have started OOBE.&nbsp; It also has the modification from DriverPacks, so if you want to use it on a non-driverpacks CD you have to delete the very last two lines yourself.</p><p><a href="http://www.sendspace.com/file/gfvdaw">http://www.sendspace.com/file/gfvdaw</a></p><br /><br /><p>If you can&#039;t get OOBE with this winnt.sif file, then double check to make sure you didn&#039;t remove OOBE in the components of nLite (if you choose to slim down your install disk, OOBE is among the first things to go).</p>]]></content>
			<author>
				<name><![CDATA[TigerC10]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2350</uri>
			</author>
			<updated>2007-10-22T01:00:07Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=15142#p15142</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: DriverPacks & nLite - in what order?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=15140#p15140"/>
			<content type="html"><![CDATA[<p>Sorry for the late post but I&#039;ve been trying many alternate ways. As of now I&#039;m desperate asking this:</p><p>Could you (or another feel like doing it) do the same procedure as i have? I guess if you follow the same procedure as me, there&#039;s at least one chance you&#039;d experience the same problem.</p><p>I also didn&#039;t recieve any relevant answer to my problem in MSFN, also it&#039;s hard to find anyone with the same problem: Their search isn&#039;t really the best one.</p>]]></content>
			<author>
				<name><![CDATA[ohem]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2713</uri>
			</author>
			<updated>2007-10-21T13:14:10Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=15140#p15140</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: DriverPacks & nLite - in what order?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=14255#p14255"/>
			<content type="html"><![CDATA[<p>The official IE7 installer doesn&#039;t integrate via standard methods properly (I think there is a lack of appropriate icons for some things).&nbsp; Same with Windows Media Player 11.&nbsp; However the issues with IE7 don&#039;t affect the install of the OS - but rather the actual install of the product.&nbsp; The reason is that they depend on Windows Installer 3.</p><p>You need to use an IE7 Addon from the RyanVM.net forums.&nbsp; I like to use the alternative pack, but that&#039;s just my personal preference.</p><br /><br /><br /><p>Well, winnt.sif gets used by CD based installs, unattend.txt gets used by remote installs.&nbsp; The reader for this file is <strong>very</strong> limited.&nbsp; In some cases, it doesn&#039;t matter what you put in the line - as long as it&#039;s not the default it will do the other thing.&nbsp; Be sure you change both winnt.sif and unattend.txt just in case (they should be identical).</p><p>Also be sure you&#039;ve got the order right.&nbsp; I&#039;ve noticed you&#039;ve got the UnattendSwitch and OemPreinstall flip flopped.&nbsp; I don&#039;t think that this could cause a problem, but with such limited parsing of the file it is possible that getting them out of order could pose a problem.&nbsp; See the link I posted to get the correct order of things.&nbsp; I think there&#039;s a program out that will generate this file for you properly, but I can&#039;t seem to locate it.&nbsp; If I find it again I&#039;ll post it for you.</p><br /><br /><p>However, you&#039;ve got the order of the tools right.&nbsp; It&#039;s just this OOBE problem.&nbsp; I recommend posting at the MSDN forums, they&#039;re probably more familiar with the OOBE problem (it&#039;s very fragile - breaks easily on windows install disks).</p>]]></content>
			<author>
				<name><![CDATA[TigerC10]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2350</uri>
			</author>
			<updated>2007-09-10T02:49:14Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=14255#p14255</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: DriverPacks & nLite - in what order?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=14252#p14252"/>
			<content type="html"><![CDATA[<div class="quotebox"><cite>TigerC10 wrote:</cite><blockquote><p>You&#039;re loosing OOBE because of nLite.</p><p>Open your winnt.sif and/or your UNATTEND.TXT files inside the i386 directory on your CD.&nbsp; This should be at the top:<br /></p><div class="codebox"><pre><code>[Data]
    AutoPartition=1
    MsDosInitiated=&quot;0&quot;
    UnattendedInstall=&quot;Yes&quot;

[Unattended]
    UnattendMode=ProvideDefault
    OemPreinstall=Yes
    UnattendSwitch=No
    TargetPath=\WINDOWS

[GuiUnattended]
    OemSkipWelcome=0
    OEMSkipRegional=0
    EncryptedAdminPassword=NO</code></pre></div><p>The important parts here are UnattendedInstall, UnattendedMode, OemSkipWelcome, and OEMSkipRegional.</p><p>If you change the unattendmode value to something like FullUnattended then you lose OOBE.&nbsp; You might also loose OOBE if you use DefaultHide and ReadOnly as well).&nbsp; Likewise if you change OemSkipWelcome to 1, you will skip OOBE.&nbsp; If you make OemPreinstall no, then your $OEM$ folders won&#039;t be copied.</p><p><a href="http://www.microsoft.com/technet/prodtechnol/Windows2000Pro/deploy/unattend/sp1ch01.mspx">http://www.microsoft.com/technet/prodte … 1ch01.mspx</a></p><br /><br /><br /><p>Good luck.</p></blockquote></div><p>Hi!</p><p>Though i set everything as good i could, i still get passed OOBE. These are my settings:</p><div class="quotebox"><cite>WINNT.SIF wrote:</cite><blockquote><p>; Generated by nLite 1.3.5</p><p>[Data]<br />Autopartition=0<br />UnattendedInstall=&quot;Yes&quot;<br />MsDosInitiated=No</p><p>[Unattended]<br />UnattendMode=ProvideDefault<br />UnattendSwitch=&quot;No&quot;<br />OemPreinstall=&quot;Yes&quot;<br />OemSkipEula=&quot;Yes&quot;<br />FileSystem=*<br />WaitForReboot=&quot;No&quot;<br />NoWaitAfterTextMode=1<br />NoWaitAfterGUIMode=1<br />DriverSigningPolicy=Ignore<br />NonDriverSigningPolicy=Ignore</p><p>[SystemRestore]</p><p>[GuiUnattended]<br />OemSkipWelcome=0<br />OEMSkipRegional=0</p><p>[Components]</p><p>[UserData]<br />ProductKey=&quot;censoredkey&quot;</p><p>[RegionalSettings]<br />Language= &quot;041d&quot;</p><p>[Networking]<br />InstallDefaultComponents=&quot;Yes&quot;</p><p>[GUIRunOnce]<br />command9=&quot;%SystemDrive%\DPsFnshr.exe&quot;<br />&quot;%systemroot%\Temp\install.cmd&quot;</p></blockquote></div><p>To add, does integration with IE7 and it&#039;s updates matter? I had an issue months earlier where the IE7 couldn&#039;t integrate well with nLite (if it&#039;s related that is) until 1-2 monhts ago, it got soemwhat fixed. But i wouldn&#039;t doubt there could be conflict somewhere nowadays.</p><p>I also tried replace &quot;DefaultHide&quot; with &quot;ProvideDefault&quot; but it got somehow reversed, i don&#039;tk now any other settings well suited.</p><p>Edit:</p><p>Wait a minute: My settings are even changed, how that happened i dunno. Ignore this post while i check around.</p><p>Edit2: Alright here&#039;s my settings, but still got passed OOBE.</p>]]></content>
			<author>
				<name><![CDATA[ohem]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2713</uri>
			</author>
			<updated>2007-09-09T22:36:13Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=14252#p14252</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: DriverPacks & nLite - in what order?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=14248#p14248"/>
			<content type="html"><![CDATA[<p>You&#039;re loosing OOBE because of nLite.</p><p>Open your winnt.sif and/or your UNATTEND.TXT files inside the i386 directory on your CD.&nbsp; This should be at the top:<br /></p><div class="codebox"><pre><code>[Data]
    AutoPartition=1
    MsDosInitiated=&quot;0&quot;
    UnattendedInstall=&quot;Yes&quot;

[Unattended]
    UnattendMode=ProvideDefault
    OemPreinstall=Yes
    UnattendSwitch=No
    TargetPath=\WINDOWS

[GuiUnattended]
    OemSkipWelcome=0
    OEMSkipRegional=0
    EncryptedAdminPassword=NO</code></pre></div><p>The important parts here are UnattendedInstall, UnattendedMode, OemSkipWelcome, and OEMSkipRegional.</p><p>If you change the unattendmode value to something like FullUnattended then you lose OOBE.&nbsp; You might also loose OOBE if you use DefaultHide and ReadOnly as well).&nbsp; Likewise if you change OemSkipWelcome to 1, you will skip OOBE.&nbsp; If you make OemPreinstall no, then your $OEM$ folders won&#039;t be copied.</p><p><a href="http://www.microsoft.com/technet/prodtechnol/Windows2000Pro/deploy/unattend/sp1ch01.mspx">http://www.microsoft.com/technet/prodte … 1ch01.mspx</a></p><br /><br /><br /><p>Good luck.</p>]]></content>
			<author>
				<name><![CDATA[TigerC10]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2350</uri>
			</author>
			<updated>2007-09-09T20:11:56Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=14248#p14248</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[DriverPacks & nLite - in what order?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=14247#p14247"/>
			<content type="html"><![CDATA[<p>I&#039;m trying to make a well updated XP of mine, I&#039;ve an XP version right after SP2 was released, so all the updates after the released have been downloaded by &quot;Windows Updates Downloader&quot;. I also have custom install with several applications through &quot;$OEM$&quot; directory in the source.</p><p>But everytime I&#039;ve combined DriverPacks Masstorage drivers and updates intergration with nLite i always loose the &quot;OOBE&quot; (Out Of Box Experience) and automatically logon as admin with no network connection and Windows classic theme, but this is only with both software.</p><p>I&#039;ve tested these steps and still have no clue what i should do to get around it and I&#039;m not gonna play in the registry to automatically create my account.</p><p>-------------------------------<br />Downloads all the necessary updates from &quot;Windows Updates Downloader&quot;.<br />Integrate all the updates through nLite.<br />Automatic Installation with only key integration (nothing else is touched).<br />Settings/Options (I&#039;m using the swedish version so bear with me, it&#039;s the field ritght below automatic) with patched TCP/IP, UxTheme, USB Hertz (1000) and disabled file protection (it&#039;s annoying).<br />Integrate Masstorage drivers with DriversBASE and set the drivers with text mode support.<br />Creates a bootable ISO.<br />Testing it with VMware.<br />-------------------------------</p><p>Now everything is up-to-date, both with DriverBASE (7.0.5.2) and masstorage (7.09) as well nLite 1.3.5</p>]]></content>
			<author>
				<name><![CDATA[ohem]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=2713</uri>
			</author>
			<updated>2007-09-09T19:43:36Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=14247#p14247</id>
		</entry>
</feed>
