johnhc

Alintoro, I see nothing obvious in your Last Session, but do have some questions. I see you have specified a theme. Usually these are unsigned and you need the SFX Option to get the theme included. If you use this option, you need to use the Disable SFC Option. In this Last Session, you did not do that. Have you run nLite more than once against the same source? If so, that is your problem. If not, please let us know what file SFC is complaining about. It looks like you have gotten away with a potential problem with your text mode drivers. You have included many and in text mode only the last is used. You should really determine which driver(s) you need and include it and no others. If you are still having this problem, then I would suggest that you remove all your AddOns and see if the problem goes away. One may need the SFC Option. You can look at your source for all your AddOns or just use trial and error to determine which one if it is one. I'll leave you with, 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.

gianalf, still not sure what you are saying. Are you talking about the attached AutoStart menu? You need to boot your machine from the CD. This means to start your machine and press Delete key, which will get you into the BIOS, and set the CD as the first boot device and restart your machine after updating the CMOS. On some machines you can press the Esc key during booting and get a menu to select the boot device. In this case, select the CD and continue. If we are having a language problem, go ahead and post in Italian and I will try to translate using Google. For example I do not know what you mean by "(installation a.s.o.) ". Enjoy, John.

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

Arguy, don't have a clue, 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.

gianalf, what do you mean by not bootable? Does Windows Setup boot up? What do you see after you try to boot the CD? You say you have two OEM licenses (keys). What kind of copy of Windows do you have? Is it also OEM (must be)? Please post the value for pid in the file setupp.ini in your original CD folder. Also, 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.

Jorpho, thanks for replying. I think we have all learned something. The error log is huge! - what a mess. Enjoy, John.

Jorpho, I don't have an answer for your questions, only the strong suspicions that the Setup error messages are telling you that that you have many missing files. I get NO errors at all during install. Do you not have a SATA or RAID device you are installing on? Are you using F6 to install a text mode driver? How did you burn the CD? I would expect you to get CD read errors if that went awry. I would try your version of 'start over' and let us know what you learn. Enjoy, John.

Jorpho, here is a link to an investigation of the "Explorer-Launch folder windows in a separate process". You are correct, it is easily undone once running. Just a caution to prevent people form posting finding an nLite problem and avoiding the situation. We would like to see what errors you are getting during install. I have never done an install on a machine with multiple optical drives but I would not expect a problem. I did a ton of testing on VMware Server and when I did my first install on my new HW, all went well and I have had no unexpected problems. I just completed my number n (big number) install on this machine also with no problems. I am testing various RAID installations, so each time I want to change it I have to reinstall my OS. This is the power of nLite for me. I would say, yes, it is unusual for a HW install to behave badly when it works fine on VM. Did you prepare your HW CD differently from the VM ISO? I noticed no drivers in your Last Session. What did you do about those? When you run nLite, if you don't Disable OEM Preinstall, then you cannot use F6 to install drivers during Setup. Drivers are the main difference between a VM and HW install. The VM cannot test your driver installation, but it does not sound like to have driver problems. Are you sure you did not run nLite more than once? Are you sure of the hot fix list and order? Enjoy, John.

Jorpho, thanks much for the Last Session. Often when there are many strange errors it is because nLite was run more than once against the same source. So, your starting over idea is a good one. The option "Explorer-Launch folder windows in a separate process" needs to be removed. It has nothing to do with your problems, but exposes a Windows problem. I run XP x64, so your hot fixes are not familiar to me. Are you sure of them and the order? What is the Server 2003 update? Here is my standard: 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. Please report when you have a solution, so others can benefit. Enjoy, John.

swiftangelus, I would sure think not. When MS installs updates/SPs, a System Restore point is created before the changes. So, please give it a try and if anything is not as you like it, then use the Restore point to change the system back. Please let us know what you learn. Enjoy, John.

Darkforce1, nhelper.exe is a utility nLite uses to do much of its work during install. The last thing it does is delete itself. I suspect what you have done is run nLite multiple time against the same source. In this case code gets added after the code that has deleted nhelper and therefore anything scheduled to be done is not completed and your install is not complete. You can look at nLite.inf (compressed to nLite.IN_) to see this - start at bottom and go up. My suggestion is to start over. And, 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.

satyendra, going along with cdob's post, please see this post. It is the opposite problem that you may be having. Apparently nLite has a problem integrating text mode drivers with the additional USB support. My solution was to remove the additional code, but you will need to add them to txtsetup.oem and use F6 to load them. That means that you cannot use the OEM Preinstall as cdob pointed out. Good luck, John.

g-force, are you talking about the floppy driver? I tried it on on R51294.exe and got the same thing. Have you tried it? Enjoy, John.

Birds, don't know, 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.

Sp0iLedBrAt, I too have encountered these type files. If the Command Prompt trick and 7-Zip both fail, I don't have a suggestion. In this case, go ahead and run the file and copy the files from the floppy. If you have a VM installed, then use a virtual floppy. I think it is best to wait for the OP to let us know what he needs, before we give any more wasted effort. Enjoy, John.

Sp0iLedBrAt, interestingly, I DLed that one and ran it in a Command Prompt when I first found the drivers. It will not accept any switches and only wants to write to a floppy. I do not have a floppy on this machine but plan on powering up my old machine later. If no one has created the floppy by then, I will do it. If you have a floppy, then go ahead and run the thing and post the compressed folder and I'll take a look. Are you sure this is the one he needs? Enjoy, John.

satyendra, if your Windows was processed by nLite, and you did not Disable OEM Preinstall in the Unattended Task, then you cannot use F6 - PERIOD! You either must Disable OEM Preinstall or integrate your text mode drivers with nLite. Assuming you are using a valid, legal copy of Windows (Please verify to us that your are!), 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.

Sp0iLedBrAt, tell me which one you are talking about and I'll give it a try. Some drivers will self extract. Put them in a Command Prompt with a /? switch and see it they will tell you the switch to use to extract. Enjoy, John.

enescrv, please see Dell's site, here. There are several for RAID and non-RAID. You will need to select the one that applies to your machine and DL it. If you have trouble extracting it and/or determining which files to use, post the compressed folder here and we'll take a look. If it is too large to post, then tell us exactly which one you need. Enjoy, John.

vinifera, then I would suggest that you get rid of all the updates and the WMFDist11.exe. I hope you are testing on a virtual machine. If so, you can take smaller steps - for example, just remove WMFDist11.exe. Please let us know what you learn. Good luck, John.

vinifera, I don't see anything obviously out of whack. I use XP x64, so can't tell about your updates and since you stripped most of the name, I can't tell some basic information. What is the WMFDist11.exe and where did you get it? Does it contain WMP11 updates? Are any of your included updates for WMP11? If so they need to go after the WMFDist11.exe. Are you sure of the update order? Have you considered using an Update Pack? Why not use the WMP11 Slipstreamer by booogy? If all else fails, you will need to remove some stuff and use trial and error to get at the problem. I would start with the WMFDist11.exe, then get rid of all the updates and see what happens. Have you run nLite more than once on the same folder? Are the files in the error messages really in your System32 folder? Good luck, John.

joe sixpack, always use the latest version of nLite (1.4.9.1). How did you do your clean install of XP? Is it up to date (SP3, etc)? If you used nLite to create it, 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. Please post a link of where you got .NET and a screen shot of one error message. Enjoy, John. EDIT: Where did you get your copy of Windows XP? Is it retail, OEM or what? Many, perhaps 1000s of people run nLite without .NET problems, so something is suspicious in your setup. Please do some searching here for the few that have had .NET problems.

vinifera, I would say it is critical. How did you include IE? What IE are you using? Is IE working on your install? I Googled all the file names in the error messages and they all seem to be related to IE. So attach your T-13 batch file and 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.

After completing the text mode file copying, setup gave the error that no hard drives could be found. I had included the 3Ware text mode driver (Version 9.5.2) DLed from the the 3Ware site and included it in my nLite run. Fernando 1 came to my rescue, once again, by finding a fix via Google. The page, here, is in German, but essentially says to delete the lines at the end of the txtsetup.oem file that allow use of a USB floppy to load the text mode drivers. This is not needed - really cannot be used since F6 cannot be used. After deleting these lines, my install went fine. Thanks again to Fernando 1 for his help. Enjoy, John.

tchjgangel, here is some Language Group information I copied from the ref.chm file. There is a link to MS with more information on Language Groups. The file is found in the deploy.cab in the Tools folder of the Support folder on your install CD. You can look in this file and deploy.chm after you extract the deploy.cab file. For your latest question, I recommend you do some experimenting. Check nothing on the Compatibility page, then go into the Remove Components and take some screen shots of the various sections. Click Back (or Cancel to start over) and come back into the Capability page and check one (such as Cameras and Camcorders) and then continue into the Remove Components and compare the various sections to the screen shots you took. You should see some components missing now. These are being protected from being removed. Enjoy, John.