Jump to content

nLite 1.3 Final - Gas Powered Commander


nuhi
 Share

Recommended Posts

My ultimate Unattended Windows XP was terrible. I think this version 1.3 have some bugs. The instalation is so long and the startup take a lot of time to load when I login my session.

Here is happenning something.... :}

Edited by Masterwill21
Link to comment
Share on other sites


@carrido gallardo, I know exactly what you are talking about. Look in the i386 folder and tell me what is the filesize of DBGHELP.DLL... If its 1.92 megs its corrupt, just drag and drop the one from your unmodified CD overwriting the corrupt one

Link to comment
Share on other sites

@ricktendo64: the filesize of my DBGHELP.DLL is 650kb and it's the same of the unmodified one.

Looking at the log files in my Windows folder after the installation i've noticed some strange things in SETUPAPI.LOG... Look at this:

#W334 Failed to verify catalog when scanning file queue. Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\clusocm.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\multimed.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\accessor.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\wmp11ext.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\runtimes.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\sidebar.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\7zip.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\absolut.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\aveicon.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\ccleaner.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\cplbonus.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\dvddcrpt.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\dvdshrnk.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\exchamap.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\freegame.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\gadinst.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\uberpack.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\lrlclock.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\wmplyric.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\gencheck.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\neavgame.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\nirsoft.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\nlaom.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\nlite13f.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\note.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\reshack.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\sta3x.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\gamegads.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\sysinter.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\unixtrac.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\ussf.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\tasktips.inf" will be installed (Policy=Ignore). Error 1168: Element not found.
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "f:\windows\inf\wb51enh.inf" will be installed (Policy=Ignore). Error 1168: Element not found.

I've no idea of what's the cause of all of this, but now i wanna try to use nLite rc2 with the same source and the same preset. Maybe i could understand something more... Maybe... :wacko:

Thank you Rick for your interest! :hello:

EDIT:

Ok, same problems also with RC2...

Edited by Carillo Gallardo
Link to comment
Share on other sites

Unfortunately for me the RC2 works better than the Final.

When I use the 1.3 Final I get this error during the unattended install of PowerDVD:

nLite.jpg

When I run exactly the same .ini file through 1.3 RC2 I do not get his problem.

Both .ini's attached, I have no other issues so will just use RC2 for the time being.

Kind Regards

Plasma

Last_Session_RC2.ini

Last_Session_Final.ini

Link to comment
Share on other sites

I don't know if is a bug or not...

I integrated the Windows Power Shell (KB926140), no errors produced during integration, I'm used even a clean XP SP2 to test.

But after the installation of Windows XP, the powershell executable and files simply don't exist (%windir%\system32\powershell\). I noted also that the files are not copied during the text mode part of installation. I looked on txtsetup.sif and they're not here too.

If you can fix this, i will be grateful.

Thanks so much.

Link to comment
Share on other sites

I had a similar problem as Plasma had, using RC2 there wasn't problems. When I installed XP using the 1.3 final I got a box saying something about windows file protection that some files where replaced and need the OS CD to restore everytime I installed drivers in a new intallation (even if they were signed or not)

Can be solved this on the next 1.4 release? and the problem with the integration of WMP11 when created a limited account user.

:hello:

Link to comment
Share on other sites

Hi!

Nice tool.

I used nLite long time ago by making My WinXP SP2 CD, and it works perfect.

My "Regional and Language" settings was:

Windows XP + SP1: English,

All language settings & default keyboard layout: Croatian,

Location: Bosnia & Herzegovina.

Well, after I saw nLite 1.3 Final, and there is a while I wanna do some changes to my installation source, I downloaded it.

At this Moment I used Windows XP + SP2 with language settings & keyboard layout set to Bosnian (first time included on SP2).

After installation I tested nLite and at the beginning become a problem.

At the stage: "Locating the Windows installation", after identifying version and rest of stuff nLite hangs by CPU usage on 100%.

Tried to change all language settings to Croatian (Bosnia & Herzegovina) and became same result.

Probably same happens with Serbian (Bosnia & Herzegovina), and some other new added languages on SP2.

Before trying to change languages reinstalled all .net components, and tried with nLite runtime, reinstalled nLite (fresh copy) with same result.

After switching everything to Croatian (just Croatian) / like I had on Win XP + SP1 / everything works.

Idea to change language came from it that I had same problems by installing some hardware (mostly optical drives) on PC with Windows XP + SP2, but after Windows recognize it I switch back everything to Bosnian, and there are no more problems.

Well it must be on Microsoft, but maybe programing nLite with .net Framework 3 will solve the problem.

Sorry if there are any grammatical errors. I like to use BS ;).

Link to comment
Share on other sites

hi,

I found nlite quite powerfull,

but there some important bugs if you are using it with " windows server 2003 entreprise SP2"'.

Especially I get the BSOD when I disable these three services:

1- Application lookup service

2- Mount point

3- Partition manger

The fact , is that the two last mentionned service by nlite, appear NOWHERE in my service list when running the OS. Probably hidden critical stuff. Anyway , I think nlite should hide these 3 (just like it does for RPC).

The tweaking is also buggy. Problem is that XP an server 2003 have often different default options, so if you don't check a box,nlite will consider it's "already done", but it's not true for server 2003.

For instance in "server 2003" you have the classic view in explorer by default while in XP you can see the task panel by default. If you uncheck the option "classic view" in nlite then you still have the classic view in 2003. Same problem with "add administrative tools" etc .....

I tested nlite with Xp, and clearly it works better with this one.

I'll still have to do some tweaks after install, but the most important is done.

I would have liked the "place bar" for common dialogs to be more customisable (not just C,D,E, & neighborhood).

I do: Desktop, C, D, and my documents.

One default I've seen: quick launch bar is not enabled by default.

Also why the saved presets are language dependent ?

I speak french & english and sometimes I find better explanations in french or english.

Would have appreciated to switch easily from a langage to an other for the descriptions.

cheers

Link to comment
Share on other sites

Did 1.3 final remove some tweaks for some reason? I can't find "Disable driver update internet prompt" and "Disable web open with prompt" under the tweaks section anymore... what happened? Those are pretty useful tweaks... :D

I'm building a CD now without them. Is there a way to apply those later?

EDIT: D'oh!! I'm such a stupid! It wasn't until I began the build process that I realized I was using an RTM version, not SP2! Wow. Been a while since I had that problem. Carry on... that also explains why "TCP/IP patch" was "unsupported"! :P

Edited by Volatus
Link to comment
Share on other sites

I want to focus your attention to a big problem that some have (just see in the forum).

I've created a bootable Windows XP SP2 with all the hotfix released since September 2004 (and IE7 Added). I was trying to install the new version of Win but the installer seems to loop infinitely at the "Registering Components" phase. It says that setup will take 13 minutes - for nearly 3 hours long and counting!

I suppose it's a BUG of nlite with the new hotfix released by Microsoft in February or in march… Infact, I have a previous version of WIN XP made with nlite 1.3rc2 in january (with all the hotfix of MS at that time) and it works.

May anybody help me?

Thanks!

Edited by albsip
Link to comment
Share on other sites

hi,

the programm crash easily if you mistakenly indicate a wrong folder then a good one at the begin of the wizard.

If you want to nlite in multiple step for testing and avoiding problems you get a lot of "last_sessions.ini" files in the root. If there's a way to merge them in a single setting file it would be nice.

At least it would be nice if nlite store automatically all the these ini, in a single zip file when creating the iso.

I don't like the fact that, when attempting a re-nliting in order to redefine some options in "unattended mode"

that you can't reselect an embedded theme as a default theme.

Font to be removed should be selectable.

I don't agree that they are rarely used , for instance arial is suggested by default in dreamweaver styles.

It would be nice if you remove a language you also remove automatically the corresponding keyboard.

Would be nice if nlite was checking automatically dependencies. It makes no sense to remove a component and not the others that depend on it.

There should be a big warning for the ability of tweaking process.

I got nothing else than problems at trying to optimise process.

My firewall (look'n'stop) refused to block applications,

and what's weird is I don't have such problem when I tweak the process only after install.

I guess windows rely on some process during intall, and then it's induce problems to fix some settings in advance.

I also tried with server 2003 and I got nothing more than a BSOD.

I think that tweaking of process should be hiden by default on only accessible if the user insist.

Too much times lost in this.

Also there's no advices built in nlite for the process and it doesn't manage automatically dependencies.

If you have a process A that depends on a service B, it makes sense that if you disable B you also disable A.

There's should be a box to "prevent loss of performance" in compatibility options, as removing some components might make the booting slower.....

final suggestions:

would be nice if there was a rating of some components removed accorded to their popularity.

It will be given to users the ability to submit a last_sessions.ini file, and the collecting of all theses datas will

help to decide which setting is "popular" or not. This would help "not too experienced" people to decide wether or not it's a good idea to remove something.

Or why not maintaining a kind of wiki where user could post a comment for each settings.

Nlite would offer a link for each settings, and at any hesitation the user could click that link and see other posted comments ...

cheers

Link to comment
Share on other sites

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
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...