MrRaines Posted May 5, 2009 Share Posted May 5, 2009 (edited) For some reason, I can no longer get nLite to successfully integrate a VLK key into the unattended settings when I make a new build which includes SP3.On using the resulting build to install XP Pro, I am always prompted for a key.Has anyone else had this, or knows what the problem might be? I downloaded a couple of previous versions of nLite but the result was the same. Edited May 5, 2009 by MrRaines Link to comment Share on other sites More sharing options...
g-force Posted May 6, 2009 Share Posted May 6, 2009 Did you thought about that Key itself?Have you asked Microsoft about your VLK-Key? Link to comment Share on other sites More sharing options...
MrRaines Posted May 6, 2009 Author Share Posted May 6, 2009 (edited) Eh? If the key was 'bad', that would become obvious once I put it in mannually, correct? Edited May 6, 2009 by MrRaines Link to comment Share on other sites More sharing options...
g-force Posted May 6, 2009 Share Posted May 6, 2009 I think so, yes. Try to enter it manually in a XP-SP3-Installation. Link to comment Share on other sites More sharing options...
MrRaines Posted May 7, 2009 Author Share Posted May 7, 2009 I already have, many times.....I was being semi-sarcastic!The key is fine, I always knew it was....been using it a LONG time....hence my question.... Link to comment Share on other sites More sharing options...
b-man Posted May 7, 2009 Share Posted May 7, 2009 have you checked its right where u entered it for the unattended setting Link to comment Share on other sites More sharing options...
MrRaines Posted May 7, 2009 Author Share Posted May 7, 2009 Pardon?I put it in the same place that worked for years using older versions of nLite. Link to comment Share on other sites More sharing options...
b-man Posted May 7, 2009 Share Posted May 7, 2009 did u enter the correct key where u were supposed toFor some reason, I can no longer get nLite to successfully integrate a VLK key into the unattended settings when I make a new build which includes SP3.On using the resulting build to install XP Pro, I am always prompted for a key.Has anyone else had this, or knows what the problem might be? I downloaded a couple of previous versions of nLite but the result was the same.u say it didnt work in a few previous versions but now ur saying it did? Link to comment Share on other sites More sharing options...
johnhc Posted May 7, 2009 Share Posted May 7, 2009 MrRaines, please attach (not paste) your Last Session.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. Please report when you have a solution, so others can benefit. Enjoy, John. Link to comment Share on other sites More sharing options...
MrRaines Posted May 7, 2009 Author Share Posted May 7, 2009 did u enter the correct key where u were supposed toFor some reason, I can no longer get nLite to successfully integrate a VLK key into the unattended settings when I make a new build which includes SP3.On using the resulting build to install XP Pro, I am always prompted for a key.Has anyone else had this, or knows what the problem might be? I downloaded a couple of previous versions of nLite but the result was the same.u say it didnt work in a few previous versions but now ur saying it did?Sorry - perhaps I should restate that.I had nLite successfully integrating unattended settings (including insertion of VLK key) correctly for years. Then at some point, this stopped working. All recent versions of nLite that I have tried no longer work to integrate the key. I am unsure if this relates to SP3 or something has changed in nLite.In all cases, the same key that I am trying to integrate works fine when manually typed into setup. Link to comment Share on other sites More sharing options...
MrRaines Posted May 7, 2009 Author Share Posted May 7, 2009 (edited) MrRaines, please attach (not paste) your Last Session.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. Please report when you have a solution, so others can benefit. Enjoy, John.Ok thanks.I always do all of the above things that you recommended.Another comment - I have tried this process both with and without the integration of a RyanVM update pack - with the same results - so eliminating the update pack as the cause of the issue. Also, I usually integrate SP3 into my build using the microsoft command line procedure - so effectively I've had nLite do NOTHING except integrate a key, and it didn't work.Very frustrating!Last_Session.ini Edited May 7, 2009 by MrRaines Link to comment Share on other sites More sharing options...
Guest Posted May 7, 2009 Share Posted May 7, 2009 (edited) Does your key exist in WinNT.sif (in I386) after nLite finishes? If not, the problem is with nLite. If so, one of two things could be your problem:You slipstreamed SP3 into your source under Windows Vista. Try slipstreaming SP3 into your source from within another OS.Your key is bad. Contact Microsoft to obtain a new key. Edited May 7, 2009 by 5eraph Link to comment Share on other sites More sharing options...
johnhc Posted May 7, 2009 Share Posted May 7, 2009 5eraph, your number 1 is exactly right! Please see the top of his Last Session (Windows NT 6.0.6002 Service Pack 2, v.286.) This is Vista.MrRaines, you cannot run nLite under Vista to create an XP ISO. Under certain circumstances this may work but not slipstreaming an SP. Your Last Session does not show integrating an SP. This increases my suspicion that you have run nLite more than once. Other than that, your Last Session looks fine. Enjoy, John. Link to comment Share on other sites More sharing options...
MrRaines Posted May 7, 2009 Author Share Posted May 7, 2009 Does your key exist in WinNT.sif (in I386) after nLite finishes? If not, the problem is with nLite. If so, one of two things could be your problem:You slipstreamed SP3 into your source under Windows Vista. Try slipstreaming SP3 into your source from within another OS.Your key is bad. Contact Microsoft to obtain a new key.5eraph, your number 1 is exactly right! Please see the top of his Last Session (Windows NT 6.0.6002 Service Pack 2, v.286.) This is Vista.MrRaines, you cannot run nLite under Vista to create an XP ISO. Under certain circumstances this may work but not slipstreaming an SP. Your Last Session does not show integrating an SP. This increases my suspicion that you have run nLite more than once. Other than that, your Last Session looks fine. Enjoy, John.As I said, my key is not bad. It works when I put it in manually, and when I download an update that requires OS key validation it all goes through ok (which I would expect of a valid VLK key). The key does appear in winnt.sif after nLite processing.I should reiterate that SP3 is already integrated by the MS command line method (albeit under Vista) before nLite is ever run. Could it still be because I'm running nLite under Vista, even though the only thing nLite is doing is integrating a key?Thanks for the input. Link to comment Share on other sites More sharing options...
g-force Posted May 7, 2009 Share Posted May 7, 2009 (edited) The problem with this key results from a bug by working with Vista as hostsystem.This is documented by Microsoft, too: http://support.microsoft.com/kb/950722This means, that this is no nLite-Bug, it occurs even when you slipstream SP3 manually.Use XP as hostsystem, slipstream SP3 with nLite, do all your preferred settings,and you`ll see - everything will work fine. Edited May 7, 2009 by g-force Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now