I am a happy nLite user, integrated Xable, Boooggy a few things more, and a lot of simple drivers.

With SP2 everything worked out perfect, and for several reasons I preferred to use WinNT32 installs.
-They are a little different, more sensitive to tweaks than CD installs, but yet everything looked good.

Under SP3 I tried to do more or less the same, and CD installs are perfect as before with IE7 integration, Boooggy, Xable, etc

However when I use the same nLited WinXP SP3 with WinNT32 installation, hell breaks loose.
-Lots of files missing, disfunctionality, signing errors, and no Calc.exe to name one of the most visible!
-I also tried a WinNT32 installation with Vanilla WinXP SP3 and no problems there!

Just for the sake of testing, I applied only one tweak with nLite: the WMP privacy statement. This resulted similar trouble and the error log as uploaded.

I looked into the differences between the installations before and after nLite and found changes to the following files:
-DEFLTWK,IN_, HIVEDEF.INF, HIVESFT.INF, SYSOC.IN_. The first two shrank by 10%, and all that for one simple tweak.

I understand well we are in the transition from SP2 to SP3, that things are difficult, so maybe I miss something:
-Does someone have a similar experience? Even tested this? Do I need to upload all nLited files?

I will greatly appreciate some insight into this problem.

Did you do your slipstreaming in Vista or 2008? That would be your issue if so.

Kel, no I did it under WinXP SP3, if I make a CD and do a CD install in Virtual PC it works fine
-the problems come with WinNT32 install on a real PC.

I slipstreamed WinXP RTM -> WinXP SP3, followed by nLite
-I will try WinXP RTM > WinXP SP2 > WinXP SP3 > nLite tonight

I need to clarify that my WinNT32 install is started from a partition, there is no CD involved. But that causes only one small part of the problems.

As mentioned, I applied just one tweak with nLite (WMP privacy) and that was causing quite some files edited and a disastrous installation. I found the causes:
-For this case nLite does not add nLite.inf to DOSNET.inf and TXTSETUP.sif so that (without) CD, nLite.inf cannot be found during installation. This causes a crash when sysocmgr tries to execute nLite.inf (and cannot find it).
-The DEFLTWK.IN_, HIVEDEF.INF, HIVESFT.INF files are just cleaned up by nLite. Comments, empty lines, etc. Good .

The above nLite.inf problem does not occur for more comprehensive installations but in that case another problem occurs (note WinNT32 only):
-Copying of files stops if certain WBEM files cannot be copied: napprov.mof, napschem.mof, rsop.mof, wscenter.mof, and rsop.mfl.
-This can be detected by searching for "could not be copied to" in Windows\Setuplog.txt. Without fatal copying errors "setup has completed copying" should be found.
-I do not know what the problem is, it looks like the WBEM files are actually copied (earlier?) and the error may just be an overwrite problem.
-I fixed this by taking the above file names out of TXTSETUP.sif.
-Looking at other posts, I believe that WBEM copy errors might be causing several other problems. I may be worth to keep tracking this.

i too have the same setup - integrated sp3 image and use no cd (i use manual installation option within the nlited xpsp3 real installation) to install from one partition to another( i dont use daemon tools or ms virtual cd or any iso.... i just run the setup from the folder which nlite modifies). i face same problems.... start menu shortcuts are missing e.g. no wmp no ie no calc on the start menu, drivers are not integrated properly, unattend file doesnt work so on...

also when i run manual setup with an answer file then why do i need to enter cd key etc?

i hope there is a solution to this soon!! i hope nuhi is reading this !!

Pallavsuri: Nuhi is working on this.

There is a solution: look into setuplog.txt and find the copy error. After that edit TXTSETUP.sif to remove the name of the file that is causing the copy error.

For more details see my own answer to my post.

I noticed the visible reduction in affected files as well, and my installation breaks, but since it is confirmed that IE7/WMP integration works fine with nlite I reckoned it was the human factor - me

Did you try with latest nlite?
I am trying out tonight to see if it breaks again.

All: I worked with nLite 1.4.5.b2

This is a work in progress. At this point I can only recommend to delete (comment out) the following files in TXTSETUP.sif:
-napprov.mof, napschem.mof, rsop.mof, wscenter.mof, and rsop.mfl

There may be more but for me it solved the problem, and it does not affect the CD installs

I still experience the same problems as posted here:

- Copying problems of the following files
napprov.mof, napschem.mof, rsop.mof, wscenter.mof, and rsop.mfl

- Missing IE icons on Desktop and Start menu

- Display settings from unattend are ignored

Has anyone got a solution for me?

aittersu, how do you manage that? Do you use nLite just to add addons or something? Any other programs involved?
There was a fix about when nLite is used only for integration, then this thing could happen. But if you remove at least one component or use options then it is a mystery how you got that issue, please explain.

Well.

I got a fresh Windows XP SP2 cd. I copied the complete content to a network drive.
I am still using my original $OEM$ directory in the I386 directory.

I then slipstreamed the SP3 using Nlite.

After that i try a reinstall from a DOS PXE boot environment (winnt.exe).

Copying files is ok, but during the GUI fase some files cannot be copied, including napclientprov.mof.

And when the setup is complete, the screen resolution is not taken over from the unattend.txt. also, the icons for IE are missing and the windows Firewall is not working.

aittersu, did you remove read-only from all files after copying the CD? Just checking .

What you report is remarkeably similar to what I experienced. Using SP2 is not a problem.

Did you modify TXTSETUP.sif as I indicated?

But doesn't it harm the installation if i comment out these five files?

I am going to try one now with those files commented out...

Oh winnt.exe...I never test that. Gonna give it a shot one day. Thx.

Well...

I commented out the five files you mentioned.

Still it came with a popup for napclientprov.mof during the GUI phase.

So i also edited wbemoc.inf with these entries:
[general]
builddate=06/May/2007
description=NR's WBEM Fix AddOn for Windows XP SP3
language=MultiLanguage
ServicePack=SP3
title=NR WBEM Fix AddOn
version=1.0
website=http://www.ryanvm.net/forum/viewtopic.php?t=6290
Windows=XP

[ExtraFileEdits]
wbemoc.inf|napclientprov.mof|napclientprov.mof,napprov.mof|1
wbemoc.inf|napclientschema.mof|napclientschema.mof,napschem.mof|1


Still nothing helps.

I get the feeling that i might need to switch to a 32 bits PXE environment for installing XP now.

Am I the only one on this forum who still uses Winnt.exe?

aittersu, I never got a popup during GUI, just a crash, did you look into your Setuplog.txt?

I would not touch wbemoc.inf, do you have the nlite-modified version?

If you want me to look, please upload your:
-DOSNET.inf, TXTSETUP.sif, Setuplog.txt, Setuperr.log, and wbemoc.inf
-Give me a day to look at it, remove all personal data (probably nothing at all but you never know)

Regarding: WINTT.exe: you may be one of the few, and discover new aspects of this wonderful installation process.

I like the PXE setup but eventually switched to WinPE 2.0 sessions to start WinNT32.exe. I start my WinPE sessions from a usb stick.

BikinDutchman,

It would be nice if you could take a look at my setupfiles.

I uploaded them in a zip-file called "setupfiles.zip".


Good luck with the files. I did not touch dosnet.inf. In txtsetup.sif, I only commented out the five files you already mentioned.

And I did:
-DOSNET.inf looks fine
-TXTSETUP.sif looks allright and patched as I did. But I do not believe that patch makes sense for this type of installation
-Setuperr.log indicates a major installation crash: if you get that many errors: format and start all over again.
-Setuplog.txt is a mess as usual; I do not see where napprov etc are copied, and a lot more is not copied (calc.exe for example). It seems to go wrong (without error msg) at wmimgmt.msc (suspicious because specified in wbemoc.inf).
-HOWEVER: the wbemoc.inf is weird, something with "NR's WBEM Fix AddOn for Windows XP SP3". I would get rid of that first and use the orginal that came with SP3, or the one obtained after nLite 1.4.5.

On a different note: MS in its/her infinite wisdom has decided to keep the old version of I386\USETUP.exe and updated I386\System32\SMSS.exe.
-According to some nitpickers these two should be the same, and it is not sure which is used by which installation type. I am still looking into that but do not believe it is major.

Hi BikinDutchman,

In wbemoc.inf, i added the stuff about "NR's WBEM Fix AddOn for Windows XP SP3" later because i found a topic on the msfn forum, suggesting that this addition would fix the problem.

This was not the case, so I think I will remove those entries again.

I give it maybe another day, after that i'm going to focus on WIN PE I think

Every new idea is welcome....

I have the same problems using winnt32.exe under BartPE...
Missing IE, Media Player calc...

BartPE should be no issue; it is a very nice build, based on the WinPE 1.0 scenario. But still our familiar windows 32 bit core.

You can have a look at your Setuplog.txt and Setuperr.log to detect any fatal errors. Ignore the hundreds of less important errors in setuplog.txt.

I noticed a difference between usetup.exe in the I386 folder and SMSS.exe in I386\System32.

SMSS.exe was patches by SP3, Usetup.exe not.

So i started an clientinstall and stopped the installation after the files were copied. When i look into the directory c:\$win_bt$.~bt\system32, i noticed that smss.exe that can be found there is NOT patched....

So now i replaced usetup.exe from the I386 folder with SMSS.exe from I386\System32.
I started a new install, and now c:\$win_bt$.~bt\system32\SMSS.exe is indeed the patched one.

Still, the effect is that napclientprov.mof is not copied, but isn't this strange?

I found a solution!!

First I replaced usetup.exe in the I386 with SMSS.exe from I386\System32. Thanks to BikingDutchman for the tip!!

This already solved the problem that the correct screen resolution was not taken over from the unattend.txt.

Secondly I edited I386\$oem$\$1\$$rename.txt

I added the following entries:

[\WINDOWS\System32\WBEM]
evtgprov.dll = "CmdEvTgProv.dll"
evtgprov.mof = "CmdEvTgProv.mof"
Napprov.mof = "NapClientProv.mof"
NapSchem.mof = "napclientschema.mof"


After this the setup runs normally without quitting at the T-28 pount during the GUI Phase. Also, Security center etc works again.

I still have one error in c:\windows\setuperr.log after installation:

[i]
Error:
Setup could not register the OLE Control C:\WINDOWS\system32\msjetoledb40.dll because of the following error:
LoadLibrary returned error 126 (the specified module could not be found).

***
[i/]

I am working on this one, but so far it looks like the problem is solved.

try rename msjetol1.dll to msjetoledb40.dll

ExamDiff tells the files are identical.


EDIT!!!!

Tested now, result:

Clean setuperr.log using aittersu's method, using the following $$rename.txt



IE, WMP tested and working, installation done using BartPE and winnt32 /unattend:.\winnt.sif /SYSPART:c:

magemaster: it looks like you did a WinNT32, which is different from WinNT. Please comment.

aittersu: do you agree that the WinNT installation problem is completely solved by using your and magemaster's fix?

I believe the $$rename.txt method is much better that tweaking TXTSETUP.sif

Yes, I did a winnt32 installation, but the errors was the same using winnt32.exe under BartPE and winnt.exe before using aiteru's method(NO IE, NO WMP, NO CALC and some others stuff that I didn't checked.

G'day,

Just a note of encouragement.
I am impatiently waiting for a winnt32.exe fix for nlite 1.4.5 having used an enlighted version of WinXPSP2 for many months now. I wouldn't want to miss the SP3 version of it. My personal complaint is that an added user does not automatically log on but generates an error message during autologon. But I am sure that past that point there are other problems. So pls pls let me know how it's going. I have spend the best part of a weekend on this so far and can't do it by myself. I don't have any useful tips as yet. Just following the discussion...

cheers

Hello all.

My problem with the winnt.exe installation after SP3 integration is completely fixed with the following additions to $$rename.txt:
I did not modify txtsetup.sif.


[\WINDOWS\System32\WBEM]
evtgprov.dll = "CmdEvTgProv.dll"
evtgprov.mof = "CmdEvTgProv.mof"
Napprov.mof = "NapClientProv.mof"
NapSchem.mof = "napclientschema.mof"

[\WINDOWS\System32\]
msjetol1.dll = "msjetoledb40.dll"
class_ss.dll = "shellstyle.dll"

[\WINDOWS\Resources\Themes\Luna\]
Luna.mst = "luna.msstyles"

[\windows\Resources\Themes\Luna\Shell\Metallic\]
metal_ss.dll = "shellstyle.dll"

[\windows\Resources\Themes\Luna\Shell\Homestead\]
home_ss.dll = "shellstyle.dll"

[\windows\Resources\Themes\Luna\Shell\NormalColor\]
blue_ss.dll = "shellstyle.dll"

[\windows\Media]
XPBalln.wav = "Windows XP Balloon.wav"
XPBatCrt.wav = "Windows XP Battery Critical.wav"
XPBatLow.wav = "Windows XP Battery Low.wav"
XPCrtStp.wav = "Windows XP Critical Stop.wav"
XPDef.wav = "Windows XP Default.wav"
XPDing.wav = "Windows XP Ding.wav"
XPError.wav = "Windows XP Error.wav"
XPExcl.wav = "Windows XP Exclamation.wav"
XPHdFail.wav = "Windows XP Hardware Fail.wav"
XPHdInst.wav = "Windows XP Hardware Insert.wav"
XPHdRem.wav = "Windows XP Hardware Remove.wav"
XPInfBar.wav = "Windows XP Information Bar.wav"
XPLogoff.wav = "Windows XP Logoff Sound.wav"
XPLogon.wav = "Windows XP Logon Sound.wav"
XPMenu.wav = "Windows XP Menu Command.wav"
XPMin.wav = "Windows XP Minimize.wav"
XPNotify.wav = "Windows XP Notify.wav"
XPBlkPop.wav = "Windows XP Pop-up Blocked.wav"
XPPrint.wav = "Windows XP Print complete.wav"
XPRecycl.wav = "Windows XP Recycle.wav"
XPRestor.wav = "Windows XP Restore.wav"
XPRingin.wav = "Windows XP Ringin.wav"
XPRngout.wav = "Windows XP Ringout.wav"
XPShutdn.wav = "Windows XP Shutdown.wav"
XPStart.wav = "Windows XP Start.wav"
XPStartU.wav = "Windows XP Startup.wav"

Thanks for everyone's efforts with this problem so far.

I've got the same issue with SP3. I'm using XP VLK and have tried slipstreaming an SP2 disk with SP3 and using a Microsoft SP3 ISO from Technet.

I use WinPE 2.0 and WinNT32.exe and boot and install from an external USB hard drive. If I add as little as 1 driver using nLite then the installation seems to miss all the files mentioned previously.

Any help anyone can offer would be greatly appreciated.

Hi everyone,

I have tried to follow the above thead and have modified usetup.exe and created a
$$rename.txt.
However no luck whatsoever.
Let me ask this questions:
I do not have a $1 directory within $OEM$! Where is $$rename.txt
supposed to be? I suppose I didn't use some nlite function to get the $$rename.txt

My main problem is that a new user that is supposed to be created does not
seem to exist for autologon. So Autologon says it can not log me on with the
user name I have specified.
If I log on as Admin instead it first has some problem relating to WMP11
and when finally showing the desktop does not show IE or OE etc and who knows
what else
NOT HAPPY!!!

Here is my Setuperr.log:
================================================

Error:
Setup could not register the OLE Control C:\WINDOWS\system32\userenv.dll because of the following error:
DllInstall returned error 2147746132 (80040154).


***

Error:
Setup could not register the OLE Control C:\WINDOWS\system32\eventcls.dll because of the following error:
DllInstall returned error 2147549183 (8000ffff).


***

Error:
Setup could not register the OLE Control C:\WINDOWS\system32\swprv.dll because of the following error:
DllInstall returned error 2147549183 (8000ffff).


***

=========== End Setuperr.log ==============================

I could not find too much on Google on thse errors.
Any thoughts out there?

I must follow the folder Hierarchy
$oem$\$1\$$rename.txt
$oem$ folder on winnt32.exe goes outside I386 folder, but I think with winnt.exe goes inside, maybe doesn't hurt put in both.

hgiertler

For CD installs you need to have:
-CDRoot\$oem$
-CDRoot\i386

For WinNT32 installs the $oem$ is a sub-folder of i386:
-InstallLocRoot\i386\$oem$

I do not know what is needed for WinNT installs. aittersu?

Your setuperr.log indicates the all too familiar installation crash.

Hi,

For winnt.exe, the $OEM$ need to be a subfolder of I386.

Hi, sorry to dig up an old post. But did the OP ever get this issue resolved?
Ive tried all versions of Nlite up to the final and also all kinds of methods and SP3 with Winnt.exe still continues to install a crippled system after Nliting.
COM+ and WMI are not installed among other things, tons of errors in the setup logs, and 3 main dll errors in the setuperr.log which have been mentioned on another thread on this forum. Basically XP is crippled. Ive tried a couple versions of XP too and also others are having the same problem using Winnt.exe and SP3 Nlited.

SP2 works perfectly, and SP3 works fine with a CD method.
Im using Winnt.exe for USB though.

Anyone have any ideas, should I start a new thread?
I have all the setup logs, even trimmed them down a bit.
I made a version identical to test in Vbox so i get the same errors in there as its the same Winnt.exe method.
Like mentioned works great with SP2, just not SP3 (slipstreamed manually or using Nlite to integrate it).

EDIT: Whoops I didnt see Page 2!! Will check out the info and see if it works for my install.
BTW I get the same errors as hgiertler. Just testing now with the usetup.exe changed. Checked the files and the names seem to be long file names and exist on the PC after installation.

Thanks.

Well problem somewhat solved.
I manually integrated SP3 into my clean untouched XP SP2 Installation source and didnt use Nlite and that setup was fine, no errors at all, but rather large!

BTW changing usetup.exe makes no difference as it is like that with the manual integration also.

I am having a similar problem while installing XP VLM thru Winnt32 if IE7 is integrated as a addon.

I have tried the solution mentioned and created $oem$\$1\$$rename.txt but it still does not resolve the problem. I am still having the IE icons and lots of other services missing.

Can someone give me the specific steps on what exactly to be done?

OK. I ran in to this problem and had no luck whatsoever with any of the fixes listed above; I just signed up to look at some attachments to try to resolve this problem. Nonetheless, I appreciate everyone's willingness to help.

The main problem that I was having was the LPDSVC (LPR/LPD Printing Service) was failing to install from the unattend.txt file. This led to other realizations such as calc.exe missing, DLLInstall errors in %windir%\setuperr.log, setuplog.txt being absolutely full of errors, and the video resolution settings from unattend.txt not being applied, etc.. It looks like nLite 1.4.5.3 just doesn't work for me at all.

After hours and hours of trial and error, running diffs on all of the inf files in the i386 folder, and all of my XP SP3 vanilla tests succeeding without any problem I came across a solution: back off to the previous version of nLite.

I manually slipstreamed XP SP3 into SP2 source and then used nLite 1.4.1 to add drivers (both PnP and Textmode) and now everything is working perfectly for me. The only issue that I'm seeing so far is something about system32\sfcfiles.dll not being signed properly in setuperr.txt. Setuplog.txt has a bunch of errors about not being able to delete files because they do not exist. Obviously you cannot use this tool to customize new settings in SP3, but I can do this in a later phase of my unattended install.

I've been using nLite for the past year to slipstream updates and add drivers and I am very pleased about how it performs overall. I am disappointed in the latest offerings, but I'm confident that the very skilled developers will take care of it.

Thanks for a great tool.

Do not worry about those errors, they are normal. It looks like the WBEM adjustments in the recent nLite versions are causing the trouble.

Any working solutions? Nothing has worked for me so far, arhhhhhhhhh!!!

Fixed in v1.4.6.

great work nuhi

sorry nuhi, nlite 1.4.6 hasn't solved the problem. same errors and files missing

Yep, same here, v1.4.6 unfortunately hasn't helped.  I use the winnt.exe method for installs and haven't had any trouble whatsoever prior to SP3.  With SP3 slipstreamed into a clean SP2 source I've been having the same issues that others have been having, like missing services.

Additionally, several system tweaks I selected have been ignored, like System Restore not being turned off, none of the My Computer right-click context menu entries I selected showed up, none of the 'show in My Computer' additions I selected showed up, and WordPad has gone AWOL.

Can't complain too much because of how much effort Nuhi has put into nLite, but it's still disappointing.  Not to be taken personally of course.

True, Nuhi has put alot of effort into nLite but this is all Micro$oft's fault. They should fix it or even tell us how to! Though this is probably one of their ways to make us move to vista, hmm

You gotta understand two things:
- No one uses winnt.exe, it works fine on CD boot
- Tried one of your presets which was failing and it worked with 1.4.6 with the winnt32.

Anyway it is just a question of how much lines to remove from the wbemoc, they did something weird there, easy to break.

So post your presets that didn't work, just saying it does not help.

edit: tried it now again with just languages removed, meaning normal components are left, and there is no problem with winnt32 as stated in the changelog. If someones winnt32 fails and boot from the same ISO works then please post your preset.

Here's a preset that doesn't work using winnt.exe with nLite v1.4.6.

Why is using winnt.exe so uncommon? It's quicker to install from a separate partition on an HDD than it is from a CD.
And with a CD, if you find that you left something out of your configuration/preset, you have to toss it and start over again. Just seems rather inefficient and wasteful.

Be careful with Winnt.exe: long file names may appear in \I386\ after integrating some updates or drivers (i.e. KB892130, ATI Catalist).

Just integrating the SP3 on a original SP2 source through nLite makes the winnt32.exe install fail. Nothing removed, nothing tweaked, nothing else... just plain integration. This is on a Norwegian XP source. I haven't tried with an English source.

Integrating by using Microsofts methods will make the winnt32.exe install work, but once I use nLite to change ANYTHING after the integration, it fails again. Normal installation through CD works, but not winnt32.exe.

I don't understand why nLite changes anything at all in the Windows source files when simply slipstreaming a service pack. Why can't it just run the Service Pack's /integrate switch? Does it need to make modifications to inf files or sif files at all? What is the purpose of this behavior?

That is because some integrations go a lot deeper than just replacing a couple of files and setting. Example: IE7 integration.