Jump to content

Change nLite Options - to a preset approach?


Recommended Posts

Posted (edited)

Hi nuhi,

First -thanx for a very useful program. I started using it again after a long absence [work..doh!] and now it have a question, or rather - a suggestion.

Which I hope is not already covered elsewhere. :blushing:

Part A)

Can you not have an option for nLite to have a prefixed folder structure? Or some "main" folders at least?

E.g. [1]Windows orig source, [2]SP2, [3]SP3, [4] nLite Windows source folder - maybe also Driverpacks, etc..-but mainly [1], [2] [3] and [4] folders.

Unfortunately i don't have a web URL to link to a picture, so i added a attachment pic - but here is a representation [hope it helps]:

F drive - nLite

|--_Info & Links

|--CD_XP_Prof_English_Keyless_SP2 [1]

|--CD_XP_SP2 [2]

|--CD_XP_SP3 [3]

|--DriverPacks

|--ISO

|--nLite

|--nLite_XP_Source [4]

|--02_2Burn here

|--03_PEbuilder

|--04_WPI

That way each ISO or DVD i make can be redone without manually having to copy over a new/fresh windows copy. Because nLite already "complains"/"insists" about a FRESH Windows source before each new build - thus it can automatically "delete" the current "nLite Win Source" folder, automatically copy the files from the preset [1] over to the blank /erased [4] folder

This way it is not a tedious manual process with possible "oops's" in it

Only thing to remember - when "auto" deleting the nLite windows source [4] is to KEEP the $OEM$ files - i keep apps and software there for loading onto the DVD/ into windows folders.

Part B )

Can the "ini" configuration file not have a NOTES section please?

That way i can put all my comments in as well.

E.g i am currently writing a AHCI10 textmode install DVD. BUT the first attempt had the wrong driver - i need another one - so where do i note that error and "info" to carry on another day?

or

e.g. the 2nd attempt was great- but i needed to add "addons" of which one was not "nice" - so i had to recompile all to omit the culprit.

Each time means manually deleting the nlite "Win source Folder" [4] and copying [1] over to [4]. And then where to note the "problems" on each ini file - or just the "flavour and contents"?

Thanks - just a suggestion - dunno if anyone else would also find this helpful. If you do think so too, brilliant - just remember the auto delete of [4] must please "leave" the $OEM$ section [only textmode inside it can be deleted or over-written [the folder always has the same directories so relatively easy]

Thanks in advance,

Jan

post-185513-1219137826_thumb.jpg

Edited by Jan_F5

Posted
Because nLite already "complains"/"insists" about a FRESH Windows source before each new build - thus it can automatically "delete" the current "nLite Win Source" folder, automatically copy the files from the preset [1] over to the blank /erased [4] folder

I must have missed that screen a hundred times. :huh:

That idea would suppress the ability to further slim down an install.

I'm all for the "notes" section in the ini files. I posted about it already.

Posted
must have missed that screen a hundred times. :huh:

That idea would suppress the ability to further slim down an install.

Hi Ponch, agreed on the "notes" [in ini file] then - kewl. :)

I may be missing your point when u say above quoted - maybe nLite could then rather have a normal and also a preset option?

I mean i slim my Windows CD down using nLite and some addons as well - but i mostly use a "virgin" [lol] source. Or the "same" source for many 'trials'.

So then you could place whatever you'd like in the main [1] windows folder that get's "auto" copied to [4] the nLite OS source.

That way any trimmed version or the version you placed there - it is thus ALWAYS used [instead of the manual delete and copy each time one starts nLite.

And "usually" one uses a "same" version a few times before actually changing the windows that radically, and if so, then "that radical version [trimmed] becomes the new default source[1].

My own usage is mainly for AHCI [ack :realmad: !!!] drivers for XP to enable full SATA2/hot plug without legacy/compatibility or having to force XP by adding the driver post an install fudge.

Doing this means umpteen attempts to get the right "CD/ISO" for version 8 ...then 9....then lately 10. Then each gets trimmed and addons galore, tested on a PC, back to tweaking...so i do manual "delete-n-source copy" UMPTEEN times a day PER each ISO.

Then i have nForce 6 and 7 PC's as well - that's another two ISO's with multiple trials each..

Anyhoo - i am sure you get my point here, so maybe a normal / preset option with INI notes si the best solution for all?

Or am i missing something? lol :unsure:

ciao

Jan

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...