Reloading ini files

[Litlsystems]

Dear all,

I've occasionally used Nlite for many years now and recently got 1.4.9.1 It seems to have a fundamental change in that you can't reload settings using a cd image that you have already used. I use it specifically for shrunk XP installs and usually, because of an error on my part, take a few goes to get things exactly right. I used to be able to go back and edit the options as much as necessary...don't ask me what version as I unfortunately lost it. Now it seems that once I have made the iso, that's it!!

Can someone please advise if I am doing something wrong, or is there a workaround to this? I found references in the forum and tried using another xp disc for the initial load and sure enough up came the mods. If I go back to the original they won't load. To me this seems incredibly dumb that you can't tweak an install to get it exactly right.

Regards,

Litl

(Edited immediately 1.4.9 to 1.4.9.1....oops, sorry)

Edited March 14, 2012 by Litlsystems

[Ponch]

Now it seems that once I have made the iso, that's it!!

Don't know exactly what you mean. The "Back" button is still there. The iso is created aside the source and you can still restart nLite using that source. Indeed, there have always been things you can (like adding a driver) and things you can't do (removing something) on an already modified source. Well technically you could, but even if you avoid potential immediate errors, its still not advised.

The ini file is like the road from A to B. If you try to take the same turns starting from anywhere else, it won't get you to where you think it does.

Also minor bug is the fact that your ini file doesn't take the Service Pack modifications from within the very nLite session in account. I mean you're better off applying ServicePacks then restarting nLite and reloading ini file. Looks confusing ? I'l try to explain better:

You load XP fresh, components 1, 2 or 3 are addded by SP3, you remove component 2 with nLite and save your work and ini file as is. Next time you want to do "exactly the same", you reload XP fresh and your ini file, nLite will see component #2 is not included in XP, and will not list it for removal, even if it will prompt you for SP3 and include that component, so at the end, component is not removed.

Edited March 14, 2012 by Ponch

[Litlsystems]

Thanks for the prompt reply, Ponch.

I am working up a scenario to better illustrate my situation, but it might be a few days away as the issue isn't a big priority for me at present in the scheme of things.

So, thanks, and keep an eye out for when I can get to it.

Regards,

Litl