MrRaines

Thanks. As it happens I multi-boot and have an XP32 build on there I can use for making new builds.

Can you rephrase that? I don't understand what you are getting at. In any case I started from scratch under XP: Extracted the flat files from a VLK-SP0 ISO Integrated SP3 using MS command line method Used nLite to insert key and adjust other unattended options, and integrate latest RyanVM post-SP3 update pack Constructed a new ISO Just tested the resulting build in VMWare and it works! No key prompt....and the update pack seems to have worked too, less post-install updates in the list. I guess I just had a while in between builds and it didn't click that I'd switched to Vista as my main OS in between. Thanks all for your input.

Hmm that MS article doesn't seem to be exactly relevant, as it says that the VLK is not accepted, when my key is accepted with no problems (albeit after being typed in manually). However I'll try it under XP and see what happens. Thanks agian.

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.

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

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.

Pardon? I put it in the same place that worked for years using older versions of nLite.

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....

Eh? If the key was 'bad', that would become obvious once I put it in mannually, correct?

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.

Pmollica Did you ever test this? Regards MrRaines

Please let me know how you get on with this! I am very interested.

I also didn't remove anything in my nLite build - only added things (namely hotfix pack and RAID/SCSI adapter drivers). I did different builds to isolate the problem and found out that integrating hotfixes didn't give rise to the problem, but integrating drivers did - so this is the area of nLite that is causing the issue (if indeed it's an nLite issue).

Thanks for that. I tested it on my VMware build and indeed it seems to correct the problem. Strange that within days of my posting this query now two others have started threads on this exact problem. Are we SURE that there is indeed corruption in some files? If you do a Windows Backup of the system state, it verifies successfully. It's only Backup Exec that has a problem. We could do with a mod merging the three threads so we aren't all talking repeating ourselves in all the threads. I am interested in seeing whether this is a bug in nLite or whether it's just a Backup Exec problem. I need to be able to integrate drivers into the OS CD because these cheap crappy servers like HP ML110 etc don't come with a floppy drive and HP say that using a USB floppy drive (even a HP one) is not supported for installation. Some USB floppy drives do work but others don't.

Hi all I'd like some input on this if anyone has any ideas. I have been using nLite successfully for some time now to integrate drivers and hotfix packs into XP and win2003 OS disks. Recently, however, an issue has arisen when using Symantec Backup Exec 10d on servers built with nLited media. All system state backups fail with the following message: Error: e000fedf - A failure occurred reading an object. I should say that Windows Backup backups of the system state seem to verify ok - but Backup Exec isn't happy. I have narrowed the problem down by using two different builds, one with the drivers included, one with the hotfixes included. The hotfixed build was fine but the build with drivers only failed with the same error. Does anyone know what nLite does to integrate the drivers? I have checked and driver.cab on the CD grows so I know it's integrating and recompressing the CAB file. But is anything else done? I need to try and isolate the cause of this issue so a solution can be arrived at. Thanks for any ideas MrRaines