johnhc

arpharazon, I am pretty much at a lost, as I am sure you are. Did you check the size and MD5 of files you DLed? Kurt_Aust listed at least size and often MD5 for most of the files he listed. He also listed the total size and count of the final Hot Fix folder. Have you checked against this? If nothing pops up, I suggest you remove your calls to your batch files and all Hot Fixes and see if this will install. Sorry, this has been such a headache for you. Is your virtual system still in Add/Remove? Are any of its files in your Program Files (x86) folder? You may need to run the MSI Cleanup Utility from Microsoft - please be very careful with this one. I have never used it but looked into it once and it can get one into trouble. Please keep us informed. Thanks, John.

santhoshworld, in the process of trying to learn something about .INF (Information) files, I ran across the file QMGR.INF (extracted QMGR.IN_ in your I386 folder.) It looks like this is the INF that installs BITS. I am not knowledgeable enough to tell you how to use this information, but it looks like this file contains the files and keys needed to get BITS going. Hopefully someone else will comment and we will all learn something. If you do decide to pursue this, please be WARNED, that messing with this can cause real problems on your running system. I would recommend that you first install a copy of your OS (with missing BITS) on a Virtual System (VirtualPC, VirtualBox or VMware Server - all free.) You can then test without risk to your running system. Please let us know what you think and learn. Have fun, John.

WizardOfWoz, it should not. Windows Update should scan your machine, then DL only the parts of SP3 needed to update the components you have installed. Enjoy, John.

Molecule, nice avatar. You do the sequencing. NLite takes them in order presented. You should have the oldest at the top of the list. If you include IE7 and/or WMP11, then any updates should follow. RyanVM's site offers Update Packs with accumulated updates and you can get the proper order there. Here is my standard inculcation: 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.

Andyba, great! Thanks for reporting. I am not familiar with your chip set but possibly some others may comment. I have not read through Fernando 1's thread but assume you have and have searched these forums and Google for your chip set drivers. I would think, however, that nVidia's site would have the best drivers, unless your MB maker has issues with them. A technical note to the MB people may help. Hope you enjoy the Sunshine there. It has made its way here and I will enjoy soon. Have fun, John.

Another Person, 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.

Andyba, OK, please correct me if I am wrong. It looks like to me you are trying to install XP Pro on a Server. It also looks like you are using Server 2003 drivers. I am not sure this is a problem, but possibly so. I could find no XP drivers for your machine. If you know the chip set type (NF4, etc), you might go to the nVidia site and find your drivers there. A free program called CPU-Z will tell you lots about your MB and other stuff. BTW, you have to be careful about using F6 on an nLited install. Please see the Help (? in circle) next to the OEM Preinstall on the General tab of Unattended. This may seem like a long way around, but trust me (why not?), it will pay off in the long run. I suggest you install a virtual system for testing. Please consider VirtualPC, VirtualBox or VMware Server - all free. You can install from an ISO file and my XP x64 installs in less than 15 minutes on VMware Server. You create zero coasters. This will not test drivers but will see if you can get past the weird error and key validation issue. After that we can go after the driver problem. I think there is value in separating the problems and then killing them. Please let us know what you learn. Enjoy, John.

Thanks, meowing, for the Shock Wave DL. Where did you find this? I searched the Adobe site and could find a KB referring to it, but no DL. Their site is one of the worst for this type of thing. I will open one more nasty gram of a technical question for them. I did try the installer and it is not silent. It opens a window at the end for a Finish click. I will also complain about this. I found, via Google, several complaining about the last click. Thanks, John.

Andyba, in my first post I asked you to attach (not paste) your Last Session. Can you tell me why so many people with problems are so reluctant to honor my request? If you will attach it, perhaps someone here can help you. It would also be nice if you would answer my question. Enjoy, John.

Andyba, 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. EDIT: Should have said, to check out your CD, you can install it directly on the hardware. If it is OK, then the CD is probably OK. If it fails the same way, then run back to your shop and complain. I suggest you take as much information as possible. There are banned keys and MS would be glad to talk to you about that if you call them. I suspect they would like to hear about your shop. If it works, it is most likely a user problem because many, many people have used nLite with great success. Enjoy, John.

ahmad2080, drivers can be included in your ISO via nLite. See Integrate Drivers in the Task list. Also, please read the guide on the nLite Web Site. Basically you extract the drivers and point nLite to the .inf files. To elaborate a little on Kels post - please read the forum rules at the top. Discussion of illegal SW is not permitted here and is grounds for being banned. Enjoy, John.

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

santhoshworld, SOL - Sadly Outta Luck (polite form) - from acronymfinder. You have removed a lot of stuff. You do need to remove the Tweak "Explorer-Launch folder windows in a separate process". This exposes a Windows bug, but has nothing to do with your problem. Did you read nLite's warning (in red) about this service being needed for Network and Windows Update? I cannot help you get BITS back. You will have to wait to see if someone else has been down this road. I assume you have searched far and wide for an answer. In general, to restore a removed component requires a rebuild. Good luck, John.

kazanti, sorry the nLite license agreement permits personal use only. Please read the file in the nLite folder. Enjoy, John.

Birds, it is NOT a bug (or a but) in nLite. Please see my answer to your other thread and please post each problem only once. Enjoy, John.

ahmad2080, yes, MB is Main Board. Thanks for the links. I will take a look. Give your ISO a go and let us know what you learn. Enjoy, John.

Birds, I guess I don't understand the question. First, I would suggest trying F8 to get into Safe Mode and if you can, please record and report the stop error code. If you have an AMD CPU and slipped SP3, then you may need KB53356. By non nLite install, I assume you mean a CD. If so set your BIOS to boot from the CD and don't boot from the HDD with the bad copy of Windows. 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.

Birds, you are welcome to watch your movies in pieces, backward or forward. And you can run nLite multiple times against the same source. Doing so almost certainly will lead to myriad varied and often bizarre problems. But, of course, you are welcome to try it. If you do and end up posting a problem, please, please, report that you have UP FRONT, so we can respond appropriately. If you think this is a bug, that is your privilege, but it will not be fixed any time soon if ever. It has been discussed many times here including with nuhi (author/owner). He does not think it is a bug. Enjoy, John.

santhoshworld, I suspect you are SOL. Please attach (not paste) you Last Session. Enjoy, John.

watbox, quick note - thunderstorms in my area! I did not know this was you. Later. Enjoy, John.

watbox, thanks for the Last Session. I was not looking down on you, just prompting you to post the information I requested. I will look more deeply, but at first glance I see nothing to concern me. The command prompt I am getting is not associated with nLite. If you Google "windows script host version 5.6", it has something to do with Visual Basic. I suspect you are running nLite more than once against the same source and causing a problem in the nLite.inf. Under certain conditions of running multiple times, nhelper gets deleted prematurely, then is not present later when it is needed to, for instant, delete files. There was a long thread with lots of shouting and name calling about this subject. The OP was describing how to alter nLite.inf to get around the fact that nhelper was deleted early. Enjoy, John.

macfanboy and diablo1, I suspect you have violated one or more of my inculcations, so, 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.

watbox, I will run the test you suggest - actually had considered such a scenario. I still need to see your Last Session and I would also like to see the script you are running and answers to the questions I have been asking. Sometimes it seems like pulling teeth to get a request fulfilled here. Enjoy, John. EDIT: I just ran several tests, defining a new account, then doing a Switch User. The new account gets created and when the desktop comes up, I see the same Command Prompt I posted earlier and that is it. NLite.cmd does not try to run. When you post the information I have requested, we can proceed. John.

ahmad2080, I think these are your drivers, but I can't really tell since you have posted NONE of the information I have requested. See my previous post. Enjoy, John.

smsc, you should integrate only SP3. Without more information it is hard to speculate, so, 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.