INF install failure

[fusetubor]

I get this error when installing nlite XP iso on virtual box:

"INF install failure. Reason. The configuration registry key is invalid."

Found an earlier post about similar problem:

http://www.msfn.org/board/index.php?showtopic=109127

But I cannot work out what to do to solve the problem.

If you need to see last session ini can you tell me how/where I find that.

[johnhc]

fusetubor, please attach (not paste) your Last Session.ini (found in your source folder after nLite runs, NOT the _u.ini). Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Enjoy, John.

EDIT: Also, please attach the .inf it is complaining about. Thanks, John.

Edited January 21, 2009 by johnhc

[fusetubor]

Attached is the last session ini file.

The error is almost the same as reported in the earlier post:

http://www.msfn.org/board/index.php?showtopic=109127

An error dialog box appears near the end of XP installation that reads:

"INF install failure. Reason. The configuration registry key is invalid."

Click OK on the error dialog box and the XP installation continues. But the installation hangs just before the login should appear. I was trying to install in virtual box to test the iso.

I have not attached the inf as I do not know which it is. How do I find that out?

LAST_SESSION__205501.20_16.49.38_.INI

[fusetubor]

Problem sorted. The error appears to be caused by the default option in OEM Preinstall (which is set to enabled) and this created a file cmdlines.txt in folder $OEM$ in the Source folder.

Unattended page > General Tab > OEM Preinstall.

Default option is OEM Preinstall enabled. This created the cmdlines.txt file which caused INF install failure error.

With OEM Preinstall option disabled no cmdlines.txt file is created and no INF error occurs.

The cmdlines.txt file reads:

[Commands]

"rundll32 advpack.dll,LaunchINFSection nLite.inf,U"

Attached is a copy of the cmdlines.txt file

cmdlines.txt

[johnhc]

fusetubor, I am curious what happened. The nLite.inf file contains many changes to the Registry and is run via the OEM Preinstall. Please look in your nLited source and search for nlite.in*. You should find NLITE.IN_. This is a compressed version of nLite.inf. I use 7-Zip to extract it so I can browse it with notepad. Mine has 23,000 lines in it. Perhaps since you specified Tweaks section to run, but no tweaks were selected, nLite got confused. Try selecting at least one tweak. I don't know how this file gets run when you turn off OEM Preinstall - perhaps it does not. Did your component removals take effect? Please let us know what is in your nLite.inf. Enjoy, John.

[fusetubor]

johnhc.

Thanks for that information. I looked in the NLITE.IN_ file, which has a list of registry entires, but I do not know how these will shed any further light on the problem.

The error no longer occurred when I changed the OEM Preinstall to disabled. The default setting is enabled. I did not install any OEM files.

I assumed this was the cause of the error, but I could be wrong. All component removal appears to be OK.

Edited January 23, 2009 by fusetubor

[johnhc]

fusetubor, I suspect the nLite.inf is where the bad registry update key is located. You can take a look and see if you can find it, or zip it up and attach it so we can look at it. I am glad you are running, but there is more to be learned here. Enjoy and thanks, John.