A few questions about what nLite does

[J.C.]

Hi, for the last week i've been deep into trying to understand the proccess nLite uses to apply tweaks mostly i've started this because i've run into the 'Advanced INF install' error on logon with a few configurations but also to better my understanding of how this wonderfull tool works (thanks nuhi ).

(nLite 1.2RC was used)

here are my questions/issues i want to clarify:

1. since nLite incorporates tweaks into the registry hives files on the cd, is there a reason for the run once entrie/s in the default user profile ? (runing the reapply section?)

2. in nLite.inf there is a line 'BitReg = B', but there isn't a section ?

3. nLite seems to parse and footprint all the registry hive even when it dosen't affect meaningfull changes to some of them (e.g. only remove empty lines /comments / indentetions then footprint the file) ?

4. some tweaks don't seem to stick like displaying the control panel in classic mode or disabling ie and oe link creation is this a bug or could something specific to my configuration ? (last try i had nLite doing tweaks and the tcp patch only).

5. about the unattended settings, should the FullName setting realy be attached to the administrator full name in nLite when it isn't neccessary ?

6. i'm just about ready to create my cd and i was considering using nLite wpi and the ryanvm updates any words of caution/wisdom about the order i use these on the source ?

hope you find the time / strength to answer my questions

[anonymous_user]

#4 - not all tweaks work. i dont know of a list though.

#6 - for me i run nlite once to integrate a update pack, then run nlite again for everything else (component removal, unattended, etc)

[mazin]

Q1. since nLite incorporates tweaks into the registry hives files on the cd, is there a reason for the run once entrie/s in the default user profile ? (runing the reapply section?)

A1. Yes, there is a reason. Whenever you create a new user, anytime in the future, the entries are run again to ensure the newly created user has got the same tweaks the first user had.

Q2. in nLite.inf there is a line 'BitReg = B', but there isn't a section ?

A2. It's safe to delete it. Leaving it there causes no harm, either.

Q5. about the unattended settings, should the FullName setting realy be attached to the administrator full name in nLite when it isn't neccessary ?

A5. Providing a Full Name will make the Full Name displayed everywhere instead of displaying the user name.

For example, if a user name (user account) is "MAX" and the full name for the same account is "Jhon Doe", then "Jhon Doe" will be displayed on the top of your Start Menu instead of "MAX".

This is why I don't add a full name. But this is my own preference!

Edited October 11, 2006 by mazin

[anonymous_user]

For example, if a user name (user account) is "MAX" and the full name for the same account is "Jhon Doe", then "Jhon Doe" will be displayed on the top of your Start Menu instead of "MAX".

This is why I don't add a full name. But this is my own preference!

not to get off topic, but if u dont provide a full name wont Windows then prompt you and thus it wont be an unattended setup anymore?

[J.C.]

thats the full name setting i was reffering to anoymous_person, and the answer is yes windows will prompt you.

this setting affects the name dispalyed on system/'my computer' properties.

it realy have nothing to do with the administrator full name setting but nLite will set it in winnt.sif to whatever you put as the full name for the administrator.

mazin - if the settings are in the hive and were incorporated into the default user profile why would you need to 'make sure'?

Edited October 12, 2006 by J.C.

[ricktendo]

The full name thing is why I went back to 1.01

[J.C.]

really? personaly i just use my own winnt.sif, the main reason for that is my personalized regional settings but i also rather use the [optional components] section for the stuff it can do.

its my prefference to keep the cd as intact as possible i rather not remove software components that might possibly be needed later,

on the other hand i just might remove some of the old drivers and hardware support, it seems to speed the setup proccess.

[r3incarnat0r]

1. since nLite incorporates tweaks into the registry hives files on the cd, is there a reason for the run once entrie/s in the default user profile ? (runing the reapply section?)

2. in nLite.inf there is a line 'BitReg = B', but there isn't a section ?

3. nLite seems to parse and footprint all the registry hive even when it dosen't affect meaningfull changes to some of them (e.g. only remove empty lines /comments / indentetions then footprint the file) ?

4. some tweaks don't seem to stick like displaying the control panel in classic mode or disabling ie and oe link creation is this a bug or could something specific to my configuration ? (last try i had nLite doing tweaks and the tcp patch only).

1. Windows rewrites some registry settings after installation, so it must be "fixed" using RunOnce.
   
2. If no BitReg tweak is used, section is simply not created. "BitReg = B" is harmless.
   
3. Yup!
   
4. Classic Control Panel will be fixed in next release. Links creation tweaks will be checked.
   

[J.C.]

Thanks for replying r3incarnat0r,

pehapse you could expand abit on the registry bits i can understand how the installation proccess can modify the registry after the hives have been imported but that could be corrected by a non-sticky runonce entry.

nLite makes it sticky by readding it as part of the proccess and putting a runonce entry in the default user profile.

it seems a bit couter productive is it realy neccessary to do it to apply the tweaks to new accounts or or is a safeguard in case someone edited the default user profile ?

if its only a safeguard should there be an option to disable it ?