BikinDutchman

This appears to be solved for my WinNT32 installation (tweak, simple drivers, Xable, IE7, Boooggy, and a number of simple add-ons). Great job Nuhi Other posters in this topic: Please report your experience so that we can, hopefully, conclude that this nasty problem has been solved, and this post can sink to the bottom of this forum.

Yes he does keep it up the date on monthly basis, also WGAN and MSUpdate. And it works terrific. I belive he has been more regular tha Ryan's forum

It is well possible that there are more errors, not logged because at some point the installer drops the ball and moves on to the next stage. -Ignore the "was not deleted" and "could not be copied into the DLL cache" errors.

Did you have this problem with WinXP SP2?

I have my settings fully unattended and the first thing I have to do is entering the Administrator password I also see the white flying logo and I do not remember I ever saw it with SP3. The Windows Update problem may be related to it being set in WinNT.sif. There are many things in the official MS unattended method that do not work.

Oops, stupid me . I did not even realize that booting the OS from USB was already that well developed. I followed Dietmar's attempts but lost track.

I believe not. The USETUP versions do not differ much, see earlier posts in this topic by aittersu. I am paying so much attention to making my WinXP_SP3 source up-to-date and always the same, to help figuring out what the problem is. I have still the same problems with nLite 1.4.6, WinNT32 and can fix it by editing TXTSETUP.sif. I still need to do a comparison with a CD install and after that report back. I am now getting also concerned about possible differences between (partition to partition) and (network to partition) installs.

Talking to my own topic again : I wrapped up some comments and added them.

Edit: I missed the point of the topic, thought it was about installing from USB, sorry. Anyway here is the method for installing from USB: You can do a WinNT32 install from a USB stick that boots into WinPE 2. Copy your i386 or AMD64 folder to the usb stick. Also copy unattend files to the USB. Boot from the USB, use Diskpart to fix drive letters, and to format the install drive. Assuming the USB is drive D:, and you want to install on drive C:, execute a command like: D:\i386\winnt32 /MakeLocalSource /noreboot /s:D:\i386 /syspart:C /tempdrive:C /udf:MyComputer,D:\Unattend.udb /unattend:D:\Unattend.txt I tried it, spent 30' on it, works like a charm. Google is your friend here

I thought that too but for that purpose ref.chm gives the option: FileSystem = ConvertNTFS LeaveAlone I saw barely any problems with the file, so just guessing

Microsoft provided a new Deploy.cab for for Windows XP SP3. This might imply that there are some changes in the WinNT.sif structure. I looked at your file and found a couple of things I could not find in the most recent ref.chm: [unattended] FileSystem=* NoWaitAfterTextMode=1 NoWaitAfterGUIMode=1 NonDriverSigningPolicy=Ignore I have seen the No* before, but I am more surprised about the Filesystem=* The Networking and related sections are largely different from the setupmgr settings. A lot of params sections missing. Indeed if setup finds something wrong it tends to ignore the rest of the WinNT.sif

For simple integrations these modifications of TXTSETUP.sif and WBEMOC.inf are just cosmetic. nLite removes comments and useless white space. (Always amazed how MS can deliver such crappy layouts). Personally I prefer to slipstream SP3 first, before nLite. That gives me a constant start for new integrations. On a different note: I read in the MS info that WinNT32 installations across a network slightly differ from installations partition to partion. That may give an additional source of confusion.

That is because some integrations go a lot deeper than just replacing a couple of files and setting. Example: IE7 integration.

nLite > Unattended > Skip OOBE In Unattend file (WinNT.sif): [unattended] UnattendSwitch=Yes

Octopuss, I do not know all contents of retail CDs but I guess they do noy have the small glitches that we see with slipstreamed CDs. I hope that my guide leads to something very close to the eventual retail CD SP3.

All, it is important to distinguish between RTM, SP1, SP2 CDs as they are sold (retail), AND CDs that are made by slipstreaming the content of previous CDs That leads to a number of interesting combinations, depending on what retail CD you have. My guide is for: -Retail CD RTM -> SP3 Which means that I start with the contents of a retail CD RTM (the first official release) copy that to a folder, and then slipstream SP3. Other combinations are, assuming you have one retail CD : -Retail CD SP1 -> SP3 -Retail CD SP2 -> SP3 If you lost the retail CD you may come across: -Retail CD RTM -> SP1 -> SP3 -Retail CD RTM -> SP2 -> SP3 -Retail CD RTM -> SP1 -> SP2 -> SP3 -Retail CD SP1 -> SP2 -> SP3 I believe I have them all now Believe me. I did not try them all but if you follow the guide you will likely end up with the same result.

sittingduck, here we go: Read-only: some (less important files do not get overwritten) -Delete i386\GUITRN_A.DL_ etc: This is the old Remote Desktop Client, no need to keep it. -Delete i386\USETUP.exe: this version is not updated, causes problems with WinNT and WinNT32 installs -Deploy.cab: needed to prepare unattended/sysprep install, is not automatically updated by service packs -Support Tools: see README.html, is not automatically updated by service packs Not all that important but if you do it once why not do it right?

Added: need to remove Read-only attribute from source files,

I believe there is a signing/certification process, just as with drivers.

Do not worry about those errors, they are normal. It looks like the WBEM adjustments in the recent nLite versions are causing the trouble.

Helllo all, This is slightly off topic but since there has been so much discussion about this I thought it good to summarize; explanation is between (). This is what I do for a regular Windows XP SP3 Professional integration starting from an RTM source (in folder WinXP_SP3): -After copying the root contents of a WinXP CD into WinXP_SP3, remove the Read-only attributes from all files in that folder. -Download "Windows XP Service Pack 3", extract (in folder SP3) and slipstream by executing: SP3/i386/update/update.exe /Integrate:WinXP_SP3. -In the slipstreamed folder: --Delete cmpnents\TABLETPC, and move *.htm moved into DOCS. (I did not look into tablet installations). --Delete i386\GUITRN_A.DL_, MIGISM_A.DL_, MIGWIZ_A.EX_, MMC.CH_, MSRDP.CA_,MSTSC.CH_, MSTSC.EX_, MSTSCAX.DL_, RDSKTPW.CH_, SCRIPT_A.DL_,SYSMOD_A.DL_, TSCUPGRD.EX_, XPTHT41W.HT_ (the old RDP client). ---remove the msrdp.cab line in DOSNET.inf (to avoid an error message during install). --Delete i386\USETUP.exe; copy i386\System32\SMSS.exe one level up, and rename it to USETUP.exe (to have an up to date GUI steup for all types of install: CD, WinNT, WinNT32). -Download "Windows XP Service Pack 3 Deployment Tools" to update WinXP_SP3\SUPPORT\TOOLS\Deploy.cab (used to make SP3 unattended and sysprep installations). -Download "Windows XP Service Pack 2 Support Tools", and extract them in WinXP_SP3\SUPPORT\TOOLS, updating all other tools (less and less usefull utilities but for the sake of completeness...). The steps of removing read-onlly and slip-streaming can be carried out with nLite . In case you do not have an RTM CD, you may encounter interesting combinations, discussed here. -You can delete the WIN51IP.SP1 and/or WIN51IP.SP2 files in the root. Google is your friend for the downloads. I am not sure what can be/has been incorporated in the nLite slipstreaming. Comments welcome as always; I will update the above as needed.

Hi Fernando, I am planning to integrate Intel AHCI drivers for IHC6R and ICH9DO chipsets. -But I could not find a single Intel driver package with support for both. So now I am thinking of integrating an old Intel driver package for IHC6R and a new driver package for ICH9DO -However I looked a little into how nLite integrates these packages and I am not sure whether this work. -One problem might be that all these driver names are the same. Do you have a suggestion?

Just replace i386\HOSTS in the windows installation source

If two driver sets are present for the same Device Instant ID, the most recent signed driver takes precedence. However, it is probably better to remove that redundancy

Yes they are mostly for special hard drives/configurations (SCSI, AHCI, RAID). Integrating just one of those is fine. Do not worry for your laptop.