Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

nuhi is back, post your suggestions here

- - - - -

  • This topic is locked This topic is locked
270 replies to this topic

#51
Ponch

Ponch

    MSFN Junkie

  • Patrons
  • 3,260 posts
  • OS:none specified
  • Country: Country Flag

Hello,

I can give you an annoying scenario.

You sart nLite on XP SP2 (or less),

you tell nlite to

-add SP3

-remove all languages (beside some you use)

This is all fine. But in a next run, if you try tu use the saved presets, nLite will read that preset file, state that some languages are not present (because they are not added yet by the Service Pack that is included after nLite reads the preset file?) and those languages will appear unticked when they do stand in the preset file as "to be removed").

I think there was also a bug with the unattended preset. nLite can't handle modified or added users from the saved presets.

 

We've had people finding their entire desktop copied to the iso because they had put a driver on the "Desktop" (to be integrated by nLite).

 

You need to make the "MAKE ISO" button bigger and flashing red or place it where the "Next" button is now or replace "Next" by "Finish without making ISO". Some people miss it, click Next and come here saying there is no ISO created.

 

Few options you need to rephrase (numerous threads,if you want, just search on "disable enable", and my name).
-SFC; let chose between "SFC enabled (default) and "SFC disabled". (Now it's "disable SFC:" "Enable (default)/Disable", which is confusing to some).
-"Press Any Key"; from your comment down the screen, it is totally a guess if "Enable" means enable the option or enable the message. Even more when you check the two next options ("Remove Duplicate File"s and "Remove Old Bios information")
I once suggested you replace the right part by "keep(default)/remove" instead of "enable(default)/disable"

An other SFC cosmetic bug; when SFC is removed (thus on a modified source), the greyed out dropdown says "Enabled" instead of "Disabled".

 

When using Unattended settings on XP Home, nLite forces you to create a user but still XP creates "owner", so there is no need for that additional user. Someone found a workaround here. And it was discussed here as well.

 

Cheers.


Edited by Ponch, 26 August 2013 - 02:31 AM.



How to remove advertisement from MSFN

#52
Maxfutur

Maxfutur

    Member

  • Member
  • PipPip
  • 232 posts
  • OS:none specified
  • Country: Country Flag

 

There is confusion with presets, as you start piling up last sessions, they would need to be merged

The first times that has really been a nightmare, also because I didn't expect such behaviour (after the first image I was like: "my nLite settings..wtf!?").
Luckly, now I don't need to change much configs. :sneaky:
A nLite auto-merge feature or a global setting or, at least, some warning.. would be nice.

My main complaint is that it modifies a lot of setup files to remove comments and white space on every run. This makes it harder to compare the differences when using version control to check what changes are made.

I would like to have a detailed info tab in nLite which describes exactly what files are modified and why it is necessary to make those changes. It should also explain what nhelper.exe is doing and why it is added.

I totally agree with this!!
That would be useful also when you need to add manual tweaks.

 



I disagree somewhat with you guys.
 

Piling up last session preset is not a big deal once you understand its behavior.

 

You can use names or numbers or a combination of them.

 

There are 2 preset files, both have the same name with the difference in "_u", wich is used by the unnattended settings, any preset that you have with whatever name you have changed, it is going to be recognized by nLite. For me has been very easy to find 6 presets after try&error, i started by renaming with names.

 

The difference between one or the other i have found with 'beyond compare' (trialware), not a big deal.

 

I prefer to keep off too many details because it would be too much work and it will take too much room in the screen, i like the last nLite behavior (v1.4.9.1).

 

 

Suggestion:

 

I think that it is very easy to add, and is related to last session presets, add rename last session on preset selection after its first time of nLite use.

 

Additional to it, option to add/edit a description in the preset in the same section, useful when using more than one OS or nLiting the same OS in a different way.

One more, pre-set a name to a new "last session file that is going to be created with nlite" instead of leave it by default.

 

 

 

Has been a long time that i haven't used nLite, my last updated source is somewhat outdated, maybe a year but i used HFSLIP for slipstream and nLite for component removal, tweaks and unnattended source.


Mozilla Firefox http://www.getfirefox.com the best web browser i've used.

#53
nuhi

nuhi

    nLite & vLite human.dll

  • Developer
  • 4,348 posts
  • OS:none specified
  • Country: Country Flag

jaclaz, I always had one preset to manage, as far as I have experienced multiple presets happen during the learning process when a person is testing something, unsure what to do.
Merge option in the preset page would be nice. What I like similar to that is incrementally adding to the last session, maybe asking the user to insert save data into the tagged preset or create a new one.

 

Acheron, the setup files as they are by default are a mess, nlite formats it all to be more consistent, the RVM Integrator does similarly as noted in this topic earlier. Now that could be a separate option, true. nLite's options grew faster than people could report multi-session issues, if I was here for the last 5 years, many if not all of those quirks would be gone, so let's not jump to conclusion that nLite as it is, is my final word. But now with future and all :), it might never become what it could have been.

 

phaolo, first thing I saw when going to DriverPacks forum was a big no to using nLite with their product. It is either a poor handling of competition or I missed those bug reports. So please explain the steps to me how to reproduce the errors with that combo, or simply link me the existing bug reports. For example am I supposed to support their pack integration, or just to integrate drivers with nLite after their tool was used and what driver do you use for getting the error?

 

Ponch, that languages-not-removed bug seems familiar to me, it was something about some langs being actually detected over a text entry which doesn't get removed unless something else happens, can't remember now, but it is an exception, not a rule... no other component should do that, and if it does let me know. I'll check those langs with a fresh perspective.

Driver integration copies the folder the driver is in, it is mentioned in the UI, and to put it bluntly - people who extract files raw into a folder with other files deserve what they get.

Now you could say that I should parse the INF and draw only relevant files for those lost souls, but it is a low priority at this point, even though I would like that very much and it is doable. Driver installation during install works on a PnP basis, so all infs and their files that get integrated are relevant, it is not junk data.

Similar to that I would get reports that ISO is too large, and to my surprise they would put ISO files to a drive root directly. I added routines to warn when selecting a drive root as the source.

Was I supposed to parse txtsetup/dosnet and recreate windows setup as well... just venting a little.

Thx for the UI suggestions, I will go over them in detail.

Home edition admin, interesting, will look at that as well, thanks.

 

Maxfutur, preset renaming and description, adding to the list of consideration.


So the next version will be mainly bug fixes around the direct integration, all of the other suggestions I will look into for the version after the fixes are stabilized.


http://www.nliteos.com | http://www.vlite.net
Remove components and customize Windows

#54
Ffin

Ffin
  • Member
  • 8 posts
  • OS:XP Pro x64
  • Country: Country Flag

Well, hi :)

 

So I am back, in other words free to work on nLite again. I am willing to consider updating it if you guys have some serious requests, be it fixes or missing functionality over the years.
For now there is no plan to update vLite, I am working on something else which will cover that area. The release date is not yet known, it is safe to say it can be counted in months, not years.

 

Fire away, if there is anyone left :)

 

Oh wow, Christmas came early this year :w00t:



#55
Ponch

Ponch

    MSFN Junkie

  • Patrons
  • 3,260 posts
  • OS:none specified
  • Country: Country Flag

Ponch, that languages-not-removed bug seems familiar to me, it was something about some langs being actually detected over a text entry which doesn't get removed unless something else happens, can't remember now, but it is an exception, not a rule... no other component should do that, and if it does let me know.

The problem is not that the component is not rremoved, it's the box being unticked by nLite. When manually reticked (which defeats the concept of presets), component are removed.I think other components do that as well.

Same scenario; take XP SP1, run nLte, integrate SP2, remove "Nachi &Blaster removal tool" (or whatever it was called), which is a component aded by SP2, the setting will be saved in lastsession.ini.

But do it again, load XP SP1 and your presets, integrate SP2, the box is now unticked (!).

This is because obviously, nLite needs to read the preset file to show that "you did integrate a Service Pack last time", but it also processes the whole file and doesn't find that component at the time in the source and so decides that it technically can't be removed.

Maybe there's a way to recheck the "remove components" part of the presets after packs have been added?



#56
nuhi

nuhi

    nLite & vLite human.dll

  • Developer
  • 4,348 posts
  • OS:none specified
  • Country: Country Flag

Ponch, first let me say, just in case it needs to be said, nLite detects components by reading the source, not from presets.

Seems to me what you are suggesting is to bind preset to a specific source?

 

If you select something to remove on source 1, create last session, load source 2, it will be checked there for removal.

And also you are introducing Service Pack integration into the mix, when that happens it is a question if the preset is saved or not before it, and reloaded after, that is a minor issue regardless as the whole source changed after slipstream.

 

If you are suggesting that component selection for same component which was there before slipstream is lost during slipstream, that is a bug report, seems to me it is far from proving that the whole concept is wrong :)


http://www.nliteos.com | http://www.vlite.net
Remove components and customize Windows

#57
phaolo

phaolo

    Member

  • Member
  • PipPip
  • 189 posts

Ponch: annoying scenario[...] you start nLite on XP SP2 [...] add SP3 [...] remove some languages

[...]"MAKE ISO" button bigger and flashing red or place it where the "Next" button is now or replace "Next" by "Finish without making ISO

Uh lol, that's my scenario, because I have a WindowsXp SP2 cd. I recall some weird behaviour too, so I always avoided restarting nLite and preferred a full single session.

I agree with the "Make iso" button issue, I often missed that the first times (also, only "Mkisoft ISO engine" worked for me).

 

nuhi: DriverPacks forum was a big no to using nLite with their product [...]am I supposed to support their pack integration, or just to integrate drivers with nLite after their tool

 

In the linked FAQ they say:

How to install DriverPacks with nLite? It does not work well. - Please don't.

Please use nLite and make all of your changes first. Then run DriverPacks BASE to add your drivers.

[...]You can leave nLite open at the create ISO page while you run DriverPacks BASE.

I guess it's just some incompatibility. The best ideal scenario would be if you could find with them any nice compatible solution. Is it possible?


Edited by phaolo, 26 August 2013 - 05:29 AM.


#58
Ponch

Ponch

    MSFN Junkie

  • Patrons
  • 3,260 posts
  • OS:none specified
  • Country: Country Flag

I'll try again to be clearer. This goes over the same source. The twist is the SP, which changes the source. Same scenario, explained more precisely;

You have XP SP1, you start nLite, at that point probably it checks a default list of components (remember, 99% things you know, I don't). You load no preset because this is your 1st time. You tell nLite to use "integrate SP" and "Remove Components". AFTER nLite has integrated the selected SP, it shows you the list of components, "Blaster Removal Tool" is present, you can tick it and finish. In the saved ini file, "Blaster Removal tool" will appear (meaning it has been ticked for removal).

Now you restart the same thing except you load "Last Session". nLite will show you that you have SP1, that you choosed to "integrate a SP" and to "Remove components", I suspect AT THAT POINT, it has already "detecte/reads/decided" that the components listed for removal in the ini files are "present or not" and thus "to be removed for real or ignored". ...but Blaster Removal Tool is NOT present yet. This results in the fact that AFTER you integrated the Service Pack, you are presented with the list of components to be removed, but "Blaster removal tool", altough being listed (like your 1st time), is now still unticked. So Same source, same actions, different results. Same for few languages.

That's why I say that the presets should (if possible) be rechecked after the SP (or any pack) is integrated, just before presenting the list of components to be removed.



#59
Acheron

Acheron

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 988 posts
  • OS:XP Pro x86
  • Country: Country Flag

nuhi, despite these quirks nLite is still a great tool which has helped me get into the world of customizing Windows setups and slipstreaming updates. Recently I have worked on removing a lot of legacy stuff from Windows XP and nLite has helped me to get rid of most.

 

However some component removal could be divided into subcomponents to remove more, without breaking functionality.

 

Some things I would like to remove with nLite:

 

OOBE mouse tutorial (You can remove OOBE, but not this subcompent)

Windows Media Player 9 tour

Animated screen characters Courtney and Earl

 

The following files can be removed safely with no effect on any functionality:

 

Windows Help directory:

sniffpol.dll
sstub.dll

 

Search Assistant directory:

msgr3en.dll
nls302en.lex

 

System32

pentnt.exe (floating point divide error report utility)

write.exe (redirect to wordpad.exe)

routemon.exe

dvdupgrd.exe

 

Another minor grief is that when you have removed all this stuff, you still get a lot of empty folders created on each install. To prevent creation of these folders you can comment out the corresponding lines in the [WinntDirectories] section of txtsetup.sif.

 

Hopefully all of this gets implemented in next release.


Say no to bloatware. Download Nero Lite!

#60
Maxfutur

Maxfutur

    Member

  • Member
  • PipPip
  • 232 posts
  • OS:none specified
  • Country: Country Flag

Now you restart the same thing except you load "Last Session". nLite will show you that you have SP1, that you choosed to "integrate a SP" and to "Remove components", I suspect AT THAT POINT, it has already "detecte/reads/decided" that the components listed for removal in the ini files are "present or not" and thus "to be removed for real or ignored". ...but Blaster Removal Tool is NOT present yet. This results in the fact that AFTER you integrated the Service Pack, you are presented with the list of components to be removed, but "Blaster removal tool", altough being listed (like your 1st time), is now still unticked. So Same source, same actions, different results. Same for few languages.
That's why I say that the presets should (if possible) be rechecked after the SP (or any pack) is integrated, just before presenting the list of components to be removed.


May i ask you if you have a localized setup of nLite?

It can be a "normal" behavior in nLite in the case of, when you use a localized nLite (translated to your language), nLite only Save to your "Last session.ini" what is translated, if an option is not translated or its ID is not integrated in the translation file, is not going to be added to the "Last session.ini" file and there is when you get "the unticked" option.


Mozilla Firefox http://www.getfirefox.com the best web browser i've used.

#61
Ponch

Ponch

    MSFN Junkie

  • Patrons
  • 3,260 posts
  • OS:none specified
  • Country: Country Flag

I don't think I ever used the translation while running the program. I also PM'd Spoiled Brat who encountered the problem I describe. He even adds "Security Center" to the list of components who will be "ignored for removal" by nLite if not present at start. Unfortunately, the forum's "make over" ate his ini file.

One more here, with ini file and more components.


Edited by Ponch, 27 August 2013 - 03:28 AM.


#62
Maxfutur

Maxfutur

    Member

  • Member
  • PipPip
  • 232 posts
  • OS:none specified
  • Country: Country Flag

If you work with nLite in english, is weird, but if nLite is running in other language than english, then you are using a translation file.


Mozilla Firefox http://www.getfirefox.com the best web browser i've used.

#63
jmbattle

jmbattle

    Member

  • Member
  • PipPip
  • 169 posts

First off, wow, great to see nuhi back!  I haven't visited this forum in years, but had to log-in just to offer my warm greetings.

 

Second, my current 'main' XP installation is still going strong five years or so after being prepared by nLite - I believe this is testament to the quality of nuhi's superb programme.

 

Anyway, I recently upgraded my internet connection, with the new provided utilising PPPoE.  Unfortunately, my current XP setup had stripped the components required for this functionality away.  So I spent a little while working with VirtualBox and nLite, creating a new XP installation that was as light as possible but retained PPPoE support.  I re-nLited the same distribution over and over, gradually removing components until I was left with just 'Dial Up Networking' and 'Kerberos Authentication'. While repetitive, the trial-and-error detective work felt rather nostalgic, and reminded me of similar processes I had been through five or so years ago in preparing my - then - 'ultimate' lightweight XP setup.

 

In the end, rather than reinstall XP keeping the required components, I decided to just pick-up an inexpensive router and use this for handling PPPoE connectivity.  However, following nuhi's return, I'm planning to prepare a 'new' up-to-date XP installation in the new future (just need to find an up-to-date alternative to RyanVM's post SP3 update pack), and will of course update my signature accordingly!

 

I'm of course also looking forward to nuhi's future projects - especially if they allow Windows 7/8 to be stripped-down in a similarly intuitive manner as nLite.

 

So, once again welcome back nuhi, however I'm sure I'm not the only person who is rather curious as to where you've been for the past few years!

 

Cheers,

James

x


Edited by jmbattle, 27 August 2013 - 05:56 PM.

Notebook PC: nLite 1.4.1 reduced WinXP with SP2 / RyanVM / FlyakiteOSX / Drivers integrated.

#64
wk357mag

wk357mag

    Newbie

  • Member
  • 17 posts

You have been missed. :)

Welcome back, you have been missed! Looking foward to beta testing future releases.

 

Im choosing to stick with XP/W2K3, so your tool is my best friend!



#65
dadaniel

dadaniel

    Newbie

  • Member
  • 11 posts

Hi nuhi,

 

great to see you back :)

 

 

These are my requests:

 

--> Even if you only select driver integration and ISO creation... there are always some helper files that have no relation to driver integration added and other files modified.

--> When a driver has been added, there is a huge delay on the first hardware install after Windows setup has been finished. It seems like some internal driver database is rebuilding. This is easily reproduceable, just plug in a USB thumbdrive after setup. It needs minutes to show up.

 

Maybe you could have a look at this...

 

 

Thank you very much for your great work!


Edited by dadaniel, 28 August 2013 - 01:58 AM.


#66
Oisin

Oisin

    Newbie

  • Member
  • 16 posts

Really great you are back! :)



#67
Ultraform

Ultraform

    Newbie

  • Member
  • 28 posts

Awesome to see this, Love nLite and vLite<3

 

Maybe already someone told this, but if you choose Remove, Components
Then Remove "Languages"
"Western Europe and United States"
Are still There next time you start nLite =).



#68
boooggy

boooggy

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,334 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag

Awesome to see this, Love nLite and vLite<3

 

Maybe already someone told this, but if you choose Remove, Components
Then Remove "Languages"
"Western Europe and United States"
Are still There next time you start nLite =).

please post your last session here.

thank you


Edited by boooggy, 28 August 2013 - 05:24 AM.


#69
buggie

buggie

    Newbie

  • Member
  • 12 posts
  • OS:none specified
  • Country: Country Flag
Hi, when i use nlite it doesnt want to remove keyboard files and language bar disappears. Is it a bug or not?
Also about vlite, can you tell me what i need to keep for tts reader to work (when i remove narrator and speech support it doesnt work. Can you make in next version separate options for removing speech recognition and tts reader)?

#70
buggie

buggie

    Newbie

  • Member
  • 12 posts
  • OS:none specified
  • Country: Country Flag
Hi, when i use nlite it doesnt want to remove keyboard files and language bar disappears. Is it a bug or not?
Also about vlite, can you tell me what i need to keep for tts reader to work (when i remove narrator and speech support it doesnt work. Can you make in next version separate options for removing speech recognition and tts reader)?

#71
robertcollier4

robertcollier4

    Newbie

  • Member
  • 10 posts
  • OS:XP Pro x86
  • Country: Country Flag
Here is a potential thing to add to nLite for Windows XP. "Fix svchost.exe 'memory could not be read' error on shutdown".

There is a common error related to svchost.exe that occurs on stripped versions of Windows XP in which services have been tweaked/disabled. The error on shutdown (only appears sometimes) is:
svchost.exe - Application Error
The instruction at "0x7c92dd29" referenced memory at "0x00000008". The memory could not be "read".
OR
svchost.exe - Application Error
The instruction at "0x7c92c288" referenced memory at "0x00000008". The memory could not be "read".
The problem is that Windows has used an update pack that included a non-official "QFE" branch of KB971657 which updates wkssvc.dll to a buggy QFE edition. The fix is to downgrade wkssvc.dll back to the stable GDR version.

Attention! Updating information.
Issued 11.08.2009 Security Update KB971657, when installed on the QFE branch, causes an error when you restart the svchost.exe. GDR branch of the hotfix, the test results are not affected by the problem. For those who are in the tank - hot fixes for XP, as a rule, contain two versions of one and the same file.

If you have after installing KB971657 discussed error occurred, check the full version of the file wkssvc.dll in System32, as described in this post, and if it turns 5.1 .2600.5826 (xpsp_sp3_ qfe .090609-1445), replacements , and those files GDR option

 
The fix first found found by os-zone here1 and here2 and full thread and ru-board here but translated and simplified by Sergey Kireev here. Just need to extract WindowsXP-KB971657-x86-ENU.exe with the "/x" switch and then replace wkssvc.dll with the file from the SP3 GDR branch:
_http://social.msdn.microsoft.com/Forums/en-US/d427ca47-869c-4c6b-b151-7ad60482c68d/svchost-error-at-shutdown

1. Download the KB971657 hotfix:
_http://www.microsoft.com/downloads/details.aspx?familyid=9c0e5bff-c248-4e87-a83b-82ba52f5299d&displaylang=en

2. Extract the content of the WindowsXP-KB971657-x86-ENU.exe to the temp folder:
WindowsXP-KB971657-x86-ENU.exe /x

This hotfix includes 4 versions of the same file 
 http://support.microsoft.com/default.aspx/kb/971657
For all supported x86-based versions of Windows XP
File version File size Date Time Platform SP requirement Service branch 
Wkssvc.dll 5.1.2600.3584 132,096 10-Jun-2009 06:32 x86 SP2 SP2GDR 
Wkssvc.dll 5.1.2600.3584 134,144 10-Jun-2009 06:26 x86 SP2 SP2QFE 
Wkssvc.dll 5.1.2600.5826 132,096 10-Jun-2009 06:14 x86 SP3 SP3GDR 
Wkssvc.dll 5.1.2600.5826 134,144 10-Jun-2009 06:17 x86 SP3 SP3QFE 

3. Replace your buggy QFE edition of C:\windows\system32\wkssvc.dll with the stable file from GDR subfolder
For example:
C:\WindowsXP-KB971657-x86-ENU\SP3GDR\wkssvc.dll for SP3 image
NOTE: You can check which version of the file you have as shown in the following images. The QFE version is buggy. The GDR version is good.
qr5.gifzuk.gif

Edited by robertcollier4, 30 August 2013 - 04:19 AM.


#72
MrJinje

MrJinje

    Tool™ Developer

  • Developer
  • 1,038 posts
  • OS:none specified
  • Country: Country Flag

Hey Nuhi, keep up the hard works.  Got any details on your v-78 product yet ?


Edited by MrJinje, 31 August 2013 - 11:44 PM.


#73
LeakHunter

LeakHunter

    Nigga

  • Member
  • 20 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag

So good to see you back nuhi! Windows 7 and 8 was terrible without you, cannot wait to do a customized Windows 8.1 installation image file, without all the bloatware.


What is better than a Nigga? more...


#74
vinifera

vinifera

    <°)))><

  • Member
  • PipPipPipPipPip
  • 961 posts
  • OS:Windows 7 x86
  • Country: Country Flag

there are plenty of tools that customize win7 so don't talk BS


If you want true Windows user experience
try Longhorn builds: 3718, 4029, 4066

#75
LeakHunter

LeakHunter

    Nigga

  • Member
  • 20 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag

there are plenty of tools that customize win7 so don't talk BS

 

If so, maybe those did not existed in Win 7 time.


What is better than a Nigga? more...





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN