I've been trying to create an unattended install, but it just won't work. I think it's not reading my winnt.sif at all—I've tried it about a jillion different ways, but it won't listen to me. The file I'm using now looks like this: [Data] MsDosInitiated=No [unattended] OemPreinstall=Yes DriverSigningPolicy=Ignore NonDriverSigningPolicy=Ignore That's the really basic version I've been trying to troubleshoot with. What I really want to use is: [Data] AutomaticUpdates=1 AutoPartition=0 UnattendedInstall=Yes MsDosInitiated=0 [unattended] DriverSigningPolicy=Ignore NonDriverSigningPolicy=Ignore OemPreinstall=Yes OemSkipEula=Yes TargetPath=\WINDOWS UnattendMode=DefaultHide WaitForReboot=No [GuiUnattended] AdminPassword=e52cac67419a9a224a3b108f3fa6cb6d8846f7eaee8fb117ad06bdd830b7586c EncryptedAdminPassword=Yes OEMSkipRegional=1 OEMSkipWelcome=1 TimeZone=35 [userData] ComputerName=XP_PC [TapiLocation] CountryCode=1 Dialing=Tone AreaCode=860 LongDistanceAccess="9" [RegionalSettings] LanguageGroup=13,17,3,2,5,16,4,12,15,7,8,10,11,9,6,14,1 Language=00000409 [branding] BrandIEUsingUnattended=Yes Home_Page=http://www.google.com Search_Page=http://www.google.com [Proxy] Proxy_Enable=0 Use_Same_Proxy=1 [identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes The path to it from the CD is \i386\winnt.sif. It's definitely not winnt.sif.txt. I could even deal with it skipping the unattended part, but it won't even copy files from my \$OEM$\$1 folder It definitely recognizes that $OEM$, at least, is there, because it executes cmdlines.txt. My RunOnceEx works, except for that none of the files it refers to exist (besides the driverpacks finisher, but that's because it's copied differently. But, because it's not reading the DriverSigningPolicy in winnt.sif, it gives me a zillion warnings about the drivers). So I end up getting "this file does not exist" messages for each RunOnceEx item except for importing registry edits—for them, there's no warning, but I know it's not importing them because the file containing them isn't on the hard drive. I've even tried restarting the whole process from multiple CDs, to no avail. I just can't figure out why XP hates me so much. Is it possible that one of the updates I'm slipstreaming (all from Microsoft and with nlite, though, except for the driver packs) is somehow breaking it? I plan to see if it works from an untouched (besides adding the $OEM$ folder and winnt.sif) CD to try to narrow down the cause—but until I do that, does anyone have any suggestions? Or maybe there's something crazy in txtsetup that's messed up and causing problems, but I don't get I feel like there's probably a simple solution to this that I'm missing.