johnhc

supersheep, I know almost nothing about W2k3, but I have a couple of things to try. I see you are running nLite under XP. Can you try it under W2k3? I also see that your driver folder has two .inf files. Try selecting 'Multiple driver folder' under Insert of the Driver section and let it use both, if appropriate. When installing XP, it asks to hit F6 to install mass storage drivers. If that is what the 'press s' is about, don't press it. Just wait for setup to time out and continue. 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.

fissionman1, I see no such problems with a properly constructed CD. Did you slipstream SP3 on top of a slipstreamed SP2? If so, that will not work. In fact, running nLite more than once against the same source usually results in strange symptoms, such as you report. 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. Enjoy, John.

TyantA, you probably will need to start over. You could try to install the component from a complete CD, if you can find one. Insert it in the optical drive and when it auto starts, select Install optional Windows Components. Good luck, John.

fmkhan100, works that way for me too. I assume that is just how Windows works. It does not mean the contents of the folder are Read Only. What problems to you think this causes? Enjoy, John.

cynik606 ,since you have SP3, you should use IE7-WindowsXP-KB938127-v2-x86-PLK.exe. Enjoy, John.

paul_f, 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. Enjoy, John.

ouiouioui, did you try 133 Undo, not 155? This is what Geej recommended. If this does not work, you may have larger problems. 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. Enjoy, John.

cynik606, do you have this version (v2), IE7-WindowsXP-KB938127-v2-x86-ENU.exe? 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. Enjoy, John.

tictoc, see this post. There are many posts about nhelper missing. This happens because you have run nLite more than once against the same source. You don't need this guy's fix, just don't run nLite multiple times on the same source. You should start a new thread with a new topic. This question does not belong in this thread. Please 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.

albator, I think you need to set the Unattended Mode to Fully Automatic. Please let us know if that works. Enjoy, John.

albator, don't have a clue without your Last Session.ini. Enjoy, John.

felix1432, I've not heard of this before and don't have an answer. I suspect, when strange symptoms are seen, that nLite has been run more than once against the same source. In the future, 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. Enjoy, John.

albator, I don't understand your question. What screen are you talking about? 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. Enjoy, John.

ltsnow, I don't know why Ternion does not use packs but I refrain because of loss of control. I must accept when and what someone else decides to put in a pack and trust that the pack has no errors. Enjoy, John. Ternion, glad you are running. I specify my screen resolution and it works fine. If you are using a virtual system, sometimes the screen size and resolution gets screwed up, but it should work fine on install on real HW. What Unattended mode are you using - does not show in .ini? Try Fully Automated. I also don't understand why it is asking for a user (since you are using XP Pro). Are you specifying anything on the Users tab of Unattended? We can't see them since the info is in _u.ini and should not be posted for privacy reasons. Enjoy, John.

Jackson0, please attach (not paste) your WPIxxx.log. The xxx will be a date/time stamp and the file will be in your root (usually C:\) directory. Enjoy, John.

Thanks, Ryudo. Enjoy, John.

gordon@med.unc.edu, if you are doing all this in multiple runs of nLite, that is probably your problem. 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. BTW, looks like your user name is your e-mail address. That is asking to get spammed aplenty. Enjoy, John. EDIT: It would probably be prudent to make a much simpler run for your first try, such as just SP3. John.

INTI, I am not a user of driver packs, but that sounds OK to me. Perhaps a user of driver packs will confirm this. This is why I suggest a virtual system, to test these things quickly and without coasters. Enjoy, John.

INTI, something is wrong with your link and I cannot see it. But, nLite should do all that is necessary for an unattended install. It does create all the needed entries in WINNT.SIF. You should consider a virtual system such as VirtualBox, VirtualPC or VMware Server - all free - for testing (prevents coasters). If you have problems, 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. Enjoy, John.

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.

Ryudo, I don't have the answer, but perhaps you can help us understand this dilemma many find themselves in. Please insert your original Windows CD and when it autostarts (double click CD if needed), select "Install optional Windows components." Find and install the needed languages. AND, please let us know what you learn. Thanks, John.

Ternion, please try with no updates, just SP3. If you want to use WUD, just DL it and install it. Then run it and it will create a folder with the update DLs included. Please attach your latest Last Session.ini. Did you notice that the update list in the WUD list was in reverse order? Please try the SP3 first, just to be sure you have a base to work from. Here is another hot fix list that you might use. Enjoy, John.

Ternion, the update pack may be a good way to go. I have not used them, but I think you can just place it in the hot fix list. I looked at my updates (XP x64) and they are not in order. I use a list that Kurt_Aust maintains for x64. There is a program called Windows Update Downloader. You have some updates already DLed, so maybe you can use the list to determine the order. There are almost 50 updates in the list which seems about right to me. DL the list and extract it (I use 7-Zip), then open with notepad. The updates are in reverse order from top to bottom. Please let us know how this works out. Why don't you try the experiment I suggested to make sure you are on the right track. Walk before you run. Enjoy, John.

hellbringer616, your side bar says Windows 7. If you are running that, then you are in the wrong forum. Try the vLite forum. If not, 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. Also, please attach your imagehlp.dll, so we can take a look at it. Enjoy, John.

Ternion, it looks like your updates are not in order. I am running XP x64, so I don't recognize most, but the hot fix that installs IE7 should be followed by updates to IE7. The same is true for the rest. Just to get a baseline, try removing all hot fixes and installing only SP3 and see if that works. Then check out the hot fix order and put, perhaps half, back in and see if that runs. The best way to do this type of testing (and prevent many coasters) is to use a virtual system such as VirtualBox, VirtualPC or VMware Server - all free. Enjoy, John.