I think that I know the answer to this, but I'd rather ask and look like an id*** instead of assuming I'm right (and remove all doubt)

I would like to take an XP source CD, remove keyboard and language, then integrate SP3, Xable's SP3 Update Pack, and drivers, then do NOTHING else.

If I were to make an ISO with these changes, would it be suitable as source material for more complex nLite runs? Or do I have to start with fresh source material every time?

Option 2, each and every time, i.e. fresh source (if you want to expect a solid and stable result).

I don't think you take a high risk.

Only integrate SP3 and burn ISO, nothing more.

You can manually remove any root-folder exept "I386".

That will be accepted as "fresh source" for further steps with nLite.

I tried to integrate Updatepacks and drivers and use this as source

for further operations with nLite, even to integrate more updates

and other drivers. I ran into some unexpected errors.

If you use your favorite "Last Session.ini" the whole process

is not as time-consumpting as to eliminate unexpected errors.

Using nLite since 2004 I prefer it like this.

--> Only integrate SP3 and burn ISO, nothing more.

Thank you, that is what I will do.

As far as the other folders go, my past habits is to put useful things in VALUE_ADD folder and kill the rest.

Microsoft and I have differing ideas regarding "Value".

I'm sorry but i disagree.

To explain in a simple matter, at least this is my intention : If you know that the changes you will do in the future iso builds, will not be affected by the changes you have made to the vanilla windows cd/dvd thus far, there is nothing to stop you from further making changes besides only integrating a service pack.

One such thing is f.example to remove the ability to do updated windows installs.

I would never, EVER, do a update install, but clean installs every time.

So i removed that ability of the windows install setup.

There are no limits if you know how to do it right.

edit : and i have used the same iso build for a myriad of different nlite runs.

Having said that. Be careful. It needs to be without flaws. Test each version of the build.

Start from scratch with new service packs etc.

Edited November 5, 200916 yr by TranceEnergy

Of cource it is possible to modify your "fresh source" - but what is the goal?

I tried to integrate Updatepacks and drivers and use this as source

for further operations with nLite, even to integrate more updates

and other drivers. I ran into some unexpected errors.

You only higher the risk of getting errors, there`s no reason to do so

if you are running your favorite "Last Session.ini" again.

there`s no reason to do so if you are running your favorite "Last Session.ini" again

I fully agree with that. Risk is high gain is almost non existant.

@TranceEnergy, technically, you make sense, but problem is, people (1st poster in this case) come for a clear answer, so "if you know what you're doing..." is not really what they are looking for and might even prove counterproductive.