Jump to content

Recommended Posts

Posted

I would like to have the ability to easily add registry settings. Say by just pointing nLite to the folder with the relevant .reg files.


Posted

actually I have to agree with ZcWorld a way to setup user accounts would be a killer feature. One large inconvenience I have to go though on almost every setup is:

autologon:Administrator

I want to create Limited User accounts, however I must create a second Administrator first?!

Then I can create the Limited User accounts.

I cannot delete the second admin account I had to create, so I have to use a reg tweak to hide it from the logon screen.

Anyone know a better way? :)

Posted

1. Can we have a resizable window, please?

Will make things much easier when writing nLite components removal HowTo and including screenshots.

2. Also can nLite remove folders like these:

C:\Windows

addins

Config

Connection Wizard

Cursors

Media

PeerNet

C:\ProgramFiles
ComPlus Applications
or we need them for some reason?

3. Remove more components please!

:hello:

Posted (edited)

* A separate version for XP pro would be nice :D cause they don't all exactly have the same services, files, .reg entries and settings (I think this is one of the reasons why there are "things" that don't work as supposed to on all NT based OS-es supported by nLite)

Edited by larisa
Posted (edited)

The ability to run nLite unattended with a command argument.

nlite.exe /preset:<filename.ini> /option

Possible options:

/qb to run unattended but visible

/qn to run unattended and silent, kind of like .msi

Edited by RogueSpear
Posted

More speedup oriented tweaks (of different kinds - not only registry).

Detailed description of services (maybe with presets ready to use).

Posted (edited)

Posibility to clear desktop icons and include customised start menus (icons).

I usually do it in a batch file but it is not perfect :)

my two cents

Edited by mad_mattx
Posted

My request isn't so simple, and could prove quite complicated and possible rewrite of a majority of the code.

Make nLite modular. Have a base engine that loads modules. Module for removal, one for cosmetics, and what have you. Along with this, the ability for others to write their own modules (say to include something you never would have though of). I understand you don't want to make nLite opensource, and so the modular idea with allowing users to write their own modules (granted the programming ones) and then could take some of the burden off you for different "components" of nLite.

Posted (edited)

Make nLite an open source project, I don't see any disadvantages. :blushing:

Edit: I just noticed that Alanoll said almost the same thing :P

Edited by Kamil

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...