BikinDutchman

I would not combine NR_IE7en_Addon_1.0.6b_alt.7z and the IE7 hotfix. just get rid of that hotfix and let Windows Update handle it. Or integrate the ORIGINAL MS IE7 installer and the recent hotfixes with nLite 1.4.1. Sorry I missed that you did the Boooggy . But I recommend you do the Boooggy with ALL WMP11 hotfixes AFTER nLite integration. Has always worked for me. BTW: It is good that you look at Setuperr.log .

The sfcfiles.dll error is normal the others not. Combining NR_IE7en_Addon_1.0.6b_alt.7z and IE7-WindowsXP-KB942615-x86-ENU.exe is suspicious. -You can integrate the MS IE7 installer and a few hotfixes (IE7 KB938127, IE7 KB939653 and newer) directly. The WMP11 hotfixes do not make sense if you have no WMP11 integrated -My two cents is that this causes the error messages. I recommend: use the Boooggy's WMP11 integrater with installer and hotfixes.

Question about Wmp.inf line Hi Boogy, I looked into the Wmp.inf as modified by your slipstreamer. It has the following two lines: HKCU,"Software\Classes\Software\Microsoft\MediaPlayer\Preferences","AcceptedPrivacyStatement",0x00010001,0 HKCU, "Software\Microsoft\MediaPlayer\Preferences", "AcceptedPrivacyStatement",0x00010001,0 I removed the first one (with Software\Classes\Software) and that had no effect on the results. -I think it can be removed, not urgent, but maybe for the next revision .

The whole plugin.ocx issue seems to be resolved with nLite 1.4.1. I am still with WinXP SP2 but no longer tweak addons, SFCfiles.dll and the error message does not show up in Setuperr.log. The updates for v1.4 somehow resolved this issue as well .

You can edit your unattended batch file or i386\WinNT.sif to add: [Components] TSWebClient = On And pray that it works (it does not work for every component)

Next time search the forum: here

It looks like you remove/tweak something that causes this problem But I also do not see what that might be I can only suggest to start from minimal nlite, and add groups of settings step by step That would take a virtual PC, rewriteable CD, or a WinNT32 installation BTW: did you check Windows\Setuperr.log ?

Looks allright; are you sure that otherwise your network is working? -Look at driver, Client for MS Networks, F&P Sharing for MS Networks, TCP/IP, -Under TCP/IP > Properties > Advanced: is TCP/IP over NetBIOS enabled You may have removed something that causes this: -Does this problem occur if you create work with a clean WinXP SP2 with minimal nLite (no removals etc)?

You might want to look in your i386\WinNT.sif

Please attach directly. Do not let us click through that ...

You can edit the default theme in the windows installation folder. For instance in WinXP extract Luna.th_ to Luna.theme, edit the wall paper info, compress again to Luna.th_

On the Bink forum I found there is a MS white paper here. It gives at least some information from headquarters about what is included, no .Net, WMP11 and IE7 as far as I can see.

The WMP11_Tweaked.cab may well be an older addon made by Boooggy. Not all eleven! hotfixes that Boooggy recommends on his site show up under MU.

There have been many posts about this. Integrate only the one HDD driver that you really need as textmode and select the correct SATA/RAID mode. For instance ICH6...9 SATA non RAID: -insert iastor.inf and then select your controller txtsetup.oem needs to be present in the same driver folder

Normally nLite does all these things for you. Assuming you have a Windows XP install folder (mine is called WinXP) with at least an I386 (or AMD64) subfolder: -you can just enter WinXP on the second page of nLite, select Bootable ISO on the fourth page, and create the image The ISO image should have all you need (nLite uses %ProgramFiles(x86)%\nLite\boot.bin) After you burn the image (using a real image burning mode) it should work Did you test this with: -A Vanilla WinXP CD? -An ISO made with nLite from a vanilla WinXP installation set (WinXP\I386 etc)?

If your BIOS settings are still as they were a month ago, you probably need the SATA (non-RAID) busdriver. Of course, you can alway try a standard windows CD and see where you end up without even installing something. -If, in that case, you reach the point where you get a question to delete the previous Windows, you are probably in emulated IDE mode (SATA behaves as the familiar old IDE HDD interface).

Yes, just those 4 *.cats and 4 *.infs (8 files) in one folder (call it your system driver folder). If you integrate just that one folder you pick one *.inf at random and nLite integrates them all (to verify: look under Windows\NLDRV, you will find it back as 001, or 002 etc, depending on the order of integrating. The order of integration does not matter: if windows detects a device it scans all inf files for a match (and carries out the instructions in the matching *.inf). Do not rename anything, nLite does the naming (001, 002, etc) If you have more than one driver sub-folder in a driver folder, you can use Kel's method, to save you some time.

I think you came a long way. I would put the ICH4core.cat, ICH4ide.cat, ICH4usb.cat, and 845g.cat, and 845G.INF, ICH4CORE.INF, ICH4IDE.INF, ICH4USB.INF in one folder (not the oem0.inf). Then integrate the contents of that folder with nLite > drivers, just pick 845G.INF, nLite will copy the rest. I am a bit surprised you had this trouble after integration. The above drivers are not really essential. Would it be an idea to try SP2 RTM first?

It CAN be done, the old Dell package has 845g.cat, ich4core.cat, ich4ide.cat, and ich4usb.cat (signature) files, so the related inf files must be somewhere in the package, and can be found under windows after installation if they get installed at all (likely as windows\Inf\oem??.inf). But if you are going SP3 don't even think about digging into that legacy package. You will be covered.

I put you on the wrong foot! The Dell Dimension 2350 has a 845G chipset and an ICH4 I/O controller. I expected .inf files for those components in the Intel package (845G.inf, ich4xxx.inf and likewise *.cat). -Intel frequently updates the chipset package to include the newest motherboards and fixes but keeps the old ones in for a while. -Too bad 845 and ICH4 are no longer in the Intel chipset packages . Your Dell package has them embedded and you have to run it, and find the right 4 *.cat and *.inf files under your windows folder. However, as far as I can see 845G and ICH4 are well supported by Windows XP SP2 so if you have that the best option may be: do nothing at all, do not integrate any chipset drivers.

It has been a while ago so please confirm below information -You have a Windows XP SP2 installation (32 bits, the most common). -Your PC/motherboard is an ASUS M2N-E type -You have your system drive connected to one of the nVidia SATA ports (from your BIOS screen shots) Assuming all this is the case: to integrate the correct drivers: -go to support.asus.com, and select download..., followed by 1. Motherboard, 2. Socket AMD2, 3. M2N-E, and Search. -open the RAID link and download WinXP > Make NVIDIA 32bit SATA RAID Driver for Windows 2000/XP/2003. -extract the package (with WinRAR or WinZIP 11) your drivers are in 32bit\IDE\WinXP\sataraid -perform a driver integration with nLite, and select only the NVIDIA nForce storage controller (required) (ignore the other "required" we do not want RAID; we take a risk here but want to figure out first what this does) -make an ISO image, burn a CD, shutdown your PC, disconnect all other hard drives (to avoid accidential overwrites) -start the CD install and see how far it gets --if something is wrong you get a processor halt screen pretty soon; after that you can probably start your computer again as usual and report -if the installation proceeds, carefully select the right partition, delete it, format and let the installation proceed -if you get up and running with the new windows, you can make a more complete slipstream based on what you observe Disclaimer: The above info is as is, no warranty. I have incomplete information, nVidia SATA/RAID integration is tricky, I do not know your system in much detail. The risks and rewards are all yours.

Download here, extract and integrate with nLite.

You can try a Diskpart script, see here. However I do not recommend you do this during WinXP install. Why not create the partitions once and forever and leave them as they are? Related: it is quite common to run diskpart in a WinPE session before OS installation.

Boooggy, I tried version 0.96i on a clean WinXP x64 installation but the problem with "Play All" is still there. Not sure if you had time to look at it but I just wanted to let you know.

Could you delete it without tweaking sfcfiles.dll?