Last Session Questions

[oao]

I need some clarifications on last session settings:

I am running nlite from my hard disk with everything else on a USB hard drive. I want to do the whole process in several steps and I want the info input in each step to be saved for the next until the CD is ready, then save the whole thing for when and if I may need to create the CD again.

1. My understanding was that the INI files are created where the Windows source (target) resides. But when I put earlier copies

there, they don't come up for loading when I run nLite. It appears only in the Presets directory they are recognized. Is this how it's supposed to work?

2. If I do certain parts but then I get out, the new input is not being saved to be available when I continue. Thus, if I use a saved previous INI, when I exist the program, the INI remains unchanged and I lose the new input.

How do I insure that new changes are added to the old changes?

Thanks.

[johnhc]

oao, what you are doing is not safe, at least that is what I say. You need to heed: Please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. The Last Session.ini is always saved into the Presets folder in the nLite folder in Program Files with a date/time stamp. It is also saved, as Last Session.ini into the source folder unless you select the Option to not save it. If you really want to use earlier copies of Last Session, you can import it on the Presets screen of nLite. After I get an ISO that I think a lot of, I copy the Last Session from the source folder into a folder I save. I renamed it to something meaningful, then import it when I need it again. One must be sure to name the front part of the .ini and the _u.ini exactly the same or a mess ensues. In my opinion, there is never a need to run nLite more than once against the same source. To do so is inviting grief. You, of course, can do as you wish and I only ask that you inform us that you are running nLite multiple times against the same source. Hope this answers your questions and then some. Enjoy, John.

[Ponch]

1) That's what the "Import" button is for. It doesn't show up, you go and get it. But normally, considering nLite is for personal use only, the file should be in your preset folder as well.

2) The new ini file is created as a whole only when the process is run on the install files, not every time you tick/untick an option.

3) As stated byJohnhc, it is risky to restart from a set of files which location contains an ini file which probably means it has already been processed by nLite. nLite is meant to be run on original files or with only Service Pack integrated.

Note that there is a bug with AM/PM sorting of the ini files.

[oao]

I am not sure I was understood correctly.

I don't want to APPLY the changes in several steps. I want to SPECIFY THE CHANGES in several steps, So not starting with a clean source is not an issue.

For example, let's say I start with a clean source and specify the hot fixes only, then without processing get out; next day I want to specify the drivers and get out, without processing; so I want to start with the hotfixes already specified. And so on, until I specified everything and THEN APPLY the changes.

The reason is that specifying all the changes at once takes too much time and is tedious. There should be a way to have the new specs each time I exit, until such time as all the specs are in and I apply the changes to the file. IOW,

the INI files should be created cumulatively and the changes applied only when I choose to do so. Isn't that how it actually works?

In fact, I've seen instructions somewhare (Aust?) to apply SP2 in one session, get out, install and apply hotfixes to WMP11 with WMP11 Slipstreamer, then go back and apply the hotfixes, drivers and tweaks. If so, then the second session starts with a source to which SP2 and WMPII were already applied, which you say should not be done. Are those instructions wrong?

[oao]

So there are 2 issues here:

1. Let's suppose I created a CD earlier and since then there have been some new hotfixes/packs and the drivers were updated. I would start with a set of clean install files from the MS CD, but I don't want to respecify EVERYTHING I specified last time, but rather alter the previous INI files to reflect just the new changes, then reapply the whole shabang to the the original install.

2. I want to keep modifying an INI file until such time as I am ready to apply it to the install files.

[Sp0iLedBrAt]

Go to Program Files/nLite/Presets and you will find all the .ini files.

[johnhc]

oao, instead of two consecutive posts, it is best to just edit the first and add to it. Please do some testing. I suspect that nLite will not save an .ini if you do not click yes on the "Do you want to start the processing?" question. Test and see. This sounds like a getting started problem. I suggest you just grit your teeth and do it all at once. The .ini files will be saved. You may make a mistake or 40, so what. After testing (in a virtual system), start anew with a fresh copy of your source, using your saved .ini files and go forward - adding/deleting hot fixes, drivers, components, options, etc. Now test again. I think you are hung up on the details too soon. In the final analysis Kurt_Aust is almost always correct and he is this time. You can run nLite and add an SP, then quit. There is no reason to save the .ini file - you will never add an SP to this folder again. Then you can run WMP11 Slipstreamer (with or without nLite) and be done with that. Now you start with this as your 'fresh' source. I do not do such. I always start with a copy of my CD, then in one nLite run apply SP2, include WMP11 in my hot fixes and do all the rest. It takes me a little longer, but I always know where I am. I have done both the SP and WMP11 up front and that works, but then I have a folder full of my CD plus - perhaps 700 MB. Do it as you wish. I tend to tell people that it is not necessary to run nLite more than once as a safety measure. People tend to do things that get them into trouble here. Please do some testing/playing. I have attached my Last Session.ini for your reading pleasure. Enjoy, John.

[oao]

There is no need to test, yes, the INI file is generated at the end of specs, which means that I cannot add to or change specs before I integrate. More than once it happened that I started specifying and I reached a point where I could not continue without further research. So I needed to put the operation on hold, figure things out, then continue, sometimes later or the next day, etc. One cannot do this -- one must lose all specs and start from scratch. Since the full specs process is long and rather tedious, repeating it more than once can drive one nuts. Hence the need for partial saves/alterations.

Regarding Aust, yes, there is no need to save the INI file after a SP run -- that's trivial, because then the process is short and simple. I was responding to the argument that one should ALWAYS start with a clean source -- in that case one starts with a source which was already modified with SP and WMP11 Slipstreamer.

As far as I know the WMP fixes must be set in RunOnce mode and one must learn how to do that, which I don't care for. So Aust's way is much easier for me.

I reiterate: I don't want or need to APPLY integration in stages; I want to SPECIFY the integration in stages. If the INI files were created during the specs and not at integration time, it would make life easier for reasons I specified above.

What I am saying is a future improvement.

[johnhc]

oao, well, I do not understand what you are saying. I will say that the hope of getting changes to nLite are slim at best. We have not seen nuhi (author/owner) in some time and we are adjusting to getting along with work arounds for any things found (almost none).

As far as I know the WMP fixes must be set in RunOnce mode and one must learn how to do that, which I don't care for. So Aust's way is much easier for me.

I use Kurt_Aust's method for many things but not WMP11. If you will look at my Last Session, you will see that I have simply included WMP11 installer and updates into the nLite Hot Fix section. I have WMP11 Slipstreamer installed on my system and nLite calls it to process WMP11 and its updates. Enjoy, John.

[johnhc]

oao, in most Tasks in nLite, at the bottom, is a pull down called Presets. They allow you to save the Last Session and give it a name. It can be loaded again later. I had forgotten about this feature because I do not use it. Hope this suits your needs. Enjoy, John.

[oao]

oao, well, I do not understand what you are saying. I will say that the hope of getting changes to nLite are slim at best. We have not seen nuhi (author/owner) in some time and we are adjusting to getting along with work arounds for any things found (almost none).

Ah, well, that's life. Too bad.

What I am talking about is:

1. The ability to specify the ini file in multiple sessions rather than in one, and process only after it's all specified.

2. Producing a new XP64 CD after enough new changes have occurred without respecifying everything from scratch. Thus if I ever need to reinstall XP I don't gave to install from an old nlited CD and apply post-CD changes manually: i specify only the changes and nlite produces a revised ini file.

Since the ini file is produced by nlite in one session and after the full specification, neither is possible via nlite. If so, the only way is to first fully specify an ini file and apply it in one session so as to produce a full ini file, then each subsequent time edit the ini file manually to reflect changes, import it and process.

What I wanted to do but can't is avoid (a) the first full specification IN ONE STAGE (b) subsequent MANUAL edits to the ini file, which are riskier.

I use Kurt_Aust's method for many things but not WMP11. If you will look at my Last Session, you will see that I have simply included WMP11 installer and updates into the nLite Hot Fix section. I have WMP11 Slipstreamer installed on my system and nLite calls it to process WMP11 and its updates. Enjoy, John.

afaicr I have not seen any reference that says wmp11 slipstreamer itself can be input into nlite, but if you say you do it i'll take your word for it. i suggest a note should be added to aust's guide where appropriate to let people know it's possible to do it that way too (and how).

thanks and best regards,

FP

[johnhc]

oao, I think you can do exactly what you want. Please see my last reply. Enjoy, John.

[oao]

oao, I think you can do exactly what you want. Please see my last reply. Enjoy, John.

You mean within nLite, or manually as I described in my last message?

[johnhc]

oao, please do some playing with nLite as I suggested before. Although I have not used the feature, it looks like at each Task of nLite you can save the Last Session (you select the name), then you can quit (no nLite processing), then start later and use the previously saved Last Session. Again I urge you to play and see how this works. Enjoy, John.

[oao]

oao, please do some playing with nLite as I suggested before. Although I have not used the feature, it looks like at each Task of nLite you can save the Last Session (you select the name), then you can quit (no nLite processing), then start later and use the previously saved Last Session. Again I urge you to play and see how this works. Enjoy, John.

I did. I don't see any prompt to save. I see only Back/Continue/Cancel, neither of which prompts me to give a name and save.

Can you be more specific?

I now see there was some confusion on my part regarding WMP11: I confused wmp with .net frame. According to your ini, WMP11 and its hotfixes go into Hotfix section, without the wmp11 slipstreamer.

It is the .net frame which require RunOnce and special coding. Is there XP64 code available to use in nLite to integrate . net by nLite?

I see some stuff on x86 but not x64.

Edited January 14, 2010 by oao