Bleser

Original post edited with requested files.

I actually did load a "Last Session", and maybe something got screwy in the process - I'll have to wait until the experts dissect my Last Session.ini file after I post it.

Forgot I would need that to help diagnose the problem. I'll post it in a few hours.

So last night I loaded a new copy of XP that I had slipstreamed my RAID drivers and SP2 into. I also spent a lot of time tweaking in the "Tweaks-More Tweaks" page. The problem is that Windows was WAY too lite! Things like IE couldn't be found... not even the default windows volume control was installed. Not Outlook Express, not much whatsoever. Do you have to make a decision about EVERY one of the options on this page, and if you don't then nLite just yanks it? I skipped the "Component Removal" step so I don't see why so much was missing from my build. I didn't even have the resources to make another nLite build, so I stayed up all night doing a bloated build. Edit: I've updated this post with two Las Session.ini files, both of which were on the CD that nLite created for me. Thoughts?

I think the source of my problem was the failure for me to select "Disable" for the System File Checker (SFC) while setting up my first nLite build. I did another nLite build last night and peformed my install and not once did I get the error message in question. Thanks for everyone's help!

nlite 1.3 beta is fine too, but I would advise 1.2.1 only because it is not beta, and because User account creating doesnt work in 1.3 beta so theres other problems too.. I advise to import the last session.ini because that way we have the same setup between the 2 versions of nlite, however if you want to do a clean setup, that is fine too. Hmmmm... this could be the culprit. What would be "wrong" with not having sfc enabled? How do I go about disabling it (just turn it off in Windows services?)? You can turn off SFC, and that will solve the problem temporarily, but SFC shouldnt be popping up unless one of the files is truely modified, as in hacked in some way. I cant remember exactly how to turn it off myself, in a running copy of windows, just google for "turn off windows file protection".. If you want to turn it off during and after install tho (have nlite do it) there is an option in 1.2.1 that will do it. Theres nothing "wrong" with turning it off, but some people prefer the "protection" that it provides, ie if a virus overwrites one of those files, then WFP (as it is known now) restores it, and if your drive starts crashing, then wfp may kick in on a regular basis to restore files that got corrupted, which will say theres something wrong here and maybe i should look into buying a new drive. Thanks for all of your valuable information. I'll give 1.2.1 a whirl tonight and hope for the best. Thanks again! No, this build was pre-IE7.

Would I need to import my last session.ini, or can I just create a new nLite build using the version you specified? Would nLite 1.3 Beta be OK? Thanks for your help. Hmmmm... this could be the culprit. What would be "wrong" with not having sfc enabled? How do I go about disabling it (just turn it off in Windows services?)?

I've edited my original post with both the Last Session.ini and Last Session_u.ini files. I hope this helps!

Hello all, I used my first nLite-enabled Windows XP Pro installation (SP2 slipstreamed in along with some RAID drivers) and everything worked fine and dandy but Windows has an odd behavior that I haven't seen before. Each time I install a driver or an application that potentially overwrites Windows system files, it tells me something like "Some Windows files have been replaced by newer versions. Insert the Windows CD to restore these files to their original copies. OK/Skip/Cancel". Does this have something to do with the way SP2 was slipstreamed in? Did I skip an option in the nLite setup? Any help is appreciated to make me understand why it is prompting me and what I can do to prevent/fix the situation. Besides this problem, Windows is working great.