Bob Jones

Uh oh. Two different answers (sort of) that essentially say to worry about chronological order (which is what I am concerned about in the first place) and not to worry about it as nLite will not overwrite newer files with older. I have a feeling that nLite will (provided I check the box) not overwrite newer with older files so I should be ok by simply selecting all the hot fixes I have and just letting it go. OR, applying some now and some later if I forget them. Which is what I am pretty much trying to confirm. It's all about "feeling good" about the process as well as getting an end result I don't have to worry about being incorrectly slipstreamed. Sounds like nLite can handle all at once or some now and some later though it's probably best to just do everything I have in one pass. BUT I think it's a good idea to periodically re-download hot fixes so that, if any did change for some reason, you have the latest and greatest for all of them to work with and, hopefully, not go wrong. Again, thank you for the clarifications. Bob

Thanks for the suggestion. Assuming I am using all the hot fixes as I originally downloaded them, this should pretty much take care of them all relative to each other. However, is it possible that, if I re-downloaded one for some reason, it might have a newer build date than it originally had and thus get mis-coordinated against all the other hot fixes? Perhaps the best thing to do would be to take my list of all hot fixes, critical, non-critical, etc. and just go re-download them all tonight and that should give all the hot fixes the latest date they could possibly have and then apply them all at the same time and not do some now and some later. It would be so nice if Microsoft would provide a foolproof way to know the absolute install order of all hot fixes since you can't go by KB number or even the date on the file as downloaded. I am not 100% sure that build date is foolproof either, but I guess if that Build Date is internal to the package, nLite should be able to handle it. I'll see what happens. Thanks for the help, Bob

Quick question I have about using nLite and I have not yet found a good answer. I have all my hot fixes and updates in folders corresponding to their criticality: Critical, Non-Critical, Install if needed, etc. The simple question is if I slipstream XP with all critical hot fixes and then later decide to slipstream the non-critical, is nLite sophisticated enough to know if a subsequent non-critical hot fix has files that are older than what was already applied and NOT apply them? In other words, can I incrementally slipstream like this or is it recommended to install all of them at the same time and nLite will take care of everything all at once? I don't want to slipstream and then find out I forgot something and apply a hot fix or update that's actually older than what I've already applied. Anyone have the simple answer? Thanks! Bob