johnhc

bargy, here is something to try: Find the following files and put them in a folder along with the .inf you posted. All should be extracted. Then right click the .inf and click Install and restart your machine. After the restart hopefully your component will be restored. I should point out that I have not tried this process, so I suggest you create a System Restore point before you start. Please let us know what your results are. Enjoy, John. mstask.dll mstinit.exe schedsvc.dll desktop.ini,mstask.ini Maintenance-Scandisk.job

bargy, tough one. I suspect you will need to start over. You can see this thread and see how we were able to solve one such problem. The key is to find the .inf that is used during Windows install. It will tell you which files and Registry keys are needed. Try finding a likely candidate .inf file in your original source and attach it here so we can take a look. Some have had luck restoring KBs and/or languages also. Please search for these threads. Enjoy, John.

Sp0iLedBrAt, I really see nothing that I would be suspicious of in your .ini. In the _U.ini I see differences in your Nevermind user account creation from mine. I assigned a PW and a full name and description. I don't have your problem but don't think the differences should cause your problem. We are curious what is the cause and would like to know what you find. Enjoy, John.

Sp0iLedBrAt, I have seen something similar. My fix was to open the Windows Security Center, go to the exceptions tab of the Windows Firewall and add the offending program. You may be having an nLite problem to do with removing something. If adding the program to the Exceptions list does not correct the problem, please attach your Last Session and we will see if anything looks suspicious. Good luck, John.

Aser, welcome. Thanks for the Last Session. It always helps to have it up front. You have run nLite under W7 to create an ISO for XP. This is probably not going to work. Please start over and run nLite under XP. Also remember, 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.

examinedliving, you should get no errors while running nLite or during install. I run x64 and have done many installs on VMware Server and get no errors. I do recommend you consider a virtual system for testing. VMware Server and VirtualBox are free and both support x64 (I have not tried VirtualBox). I looked at WSOCK32.DLL on my install source folder and here are the particulars: Version: 5.2.3790.1830 Size: 25,088 Bytes MD5: 67C6DE277D8E7991D74FA51502D85E98 You should look at your installed one and at the one on your source. To help you further, we need more information. 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.

CalvinNoob, welcome to the forum. Please edit (Full) your post and change the title to agree with the forum rules (see link at the top). It needs to describe your problem not just ask for help. It looks like you are using an upgrade CD to do an install on a computer that does not presently have Windows installed. What is the nature of your source CD? Is it an upgrade, not a complete version of Windows? In your source find a file called SETUPP.INI. Open it with Notepad and please post the Pid value. 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.

Sp0iLedBrAt, thanks much. RegMon has been replaced by Process Monitor and it is from Sysinternals. It creates tons of output quickly, so I am trying to get it to quiet down so I can see what nLite is doing. Thanks, John.

Sp0iLedBrAt and Kurt_Aust, thanks for your replies. I am amazed that I experienced the problem and as I commented in my last reply, I would really like to understand what is going on. I suspected that it was the Abort that was causing the problem and that is why I tried reinstalling nLite. I wonder if nLite keeps some information in the the Registry that does not get removed on an uninstall. I have searched my Registry to no avail. The problem persisted through many ISO creations. Reducing the source size fixed it. The cure was to use ImgBurn - now no problems. If anyone has an idea please let us know. Thanks, John.

To create a log file of the running of the batch file I altered the RunOnce to look like: CMD /R %Source%Run1_XP-64.bat >"%SystemDrive%\Run1.log" 2>&1This logs the commands and the error messages, if any, into the log file. There is no output to the monitor, but the output from the installers and other running programs continue. Enjoy, John.

sacharja, mine opens a new tab in the same IE8 window. I am running XP x64 and IE8, up to date, under VM. I also have 'A new tab in the current Window' checked under Tabbed Browsing Settings in Internet Explorer Options. Enjoy, John.

Today, for the first time in quite a while I am being logged off fairly often. Anyone else? Enjoy, John.

farkus, running nLite against a source that has had nLite run against it before is asking for trouble and often leads to the kind of problems you have. Also it is unnecessary to apply SP3 and SP2. You should only apply SP3 and doing otherwise may lead to problems. So you need to start over with a fresh source. You can use your original Preset. 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.

Grake, thanks for your reply. 5eraph, thanks also. I DLed and installed ImgBurn and managed to get an ISO that auto starts on my VM and boots into Setup. EDIT: I could not figure out what was meant by 'Boot Image', so I guessed it meant boot sector and I pointed to the boot.bin in the nLite folder. g-force, thanks for the welcome back. It is good to be back to my own machine. I am very surprised by my problem. It was totally unexpected and took me a while to determine what was going on because I would never think there was a size limit. The fact remains, my ISO is missing many files when I create it with nLite but is fine when I reduce the size of it or use ImgBurn with my large source (2.4 GB). I would like to know what is really going on. Enjoy and thanks much! John

0d14r3, thanks for your rely. I got that, and all, hot fixes from Kurt_Aust's thread for x64. I have built many an ISO with that KB with no problems. I think I have identified the problem. I removed the WPI folder (about 1 GB) from my source folder and created an ISO using nLite. It works and contains all my files and folders. I guess I am just trying to create an ISO that is too large for nLite. I am now trying to find a free program to create a bootable ISO. I tried CD Burner XP but the ISO I created just contains all the files in the original folder. I have not been able to determine how to create a bootable ISO with it. Any suggestions gladly and graciously accepted. Thanks, John.

I made an nLite run with some changes to Unattended and added hot fixes. The first time I tried to create an ISO I realized I had not updated a file used by WPI, so I clicked Abort on the create task. After updating the file, I again created an ISO. When I connect this ISO to my VM (VMware Server), it does not auto start and there are no files at the highest level (see attached screen shot). All of the files are in the source folder. I have rebooted, removed and reinstalled nLite and rebuilt my source folder from a fresh copy of my CD and rerun nLite. I have a number of programs and etc that I install via RunOnce and WPI so my source is large - 2.43 GB. I will continue to try to determine what is going on, but I would really appreciate it if someone can give me some help. Thanks much, John. EDIT: Just extracted the ISO and the files are not there. About 200-300 MB of files are missing.

.ry, your symptoms sound like you have run nLite more than once on the same source. strel is correct and further, 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.

Kurt_Aust, thanks much. I have a question. You have KB973346 in the /Hotfix and in the the Run1_XP-64.bat. I have always run it in the Hotfix section of nLite. Which place should it be? Thanks, John.

bingelman, searching will give you lots of help. Basically you copy the CD contents to a folder, then examine the files for driver files (indicated by a .inf extension, text mode by txtsetup.oem). You will most likely need to extract the .exe files there and look at what pops out. Point nLite to the .inf files. Please do some searching first. Enjoy, John.

mrfunk, I don't see it either in nLite for my XP x64 source. What OS are you running nLite under? If it is Vista, then that could be a problem although not this one. I have noticed that my component removal options for XP x64 are not the same as XP, so W2003 may be different also. Enjoy, John.

sacharja, the only positive way to correct this is to start over and not remove IE at all. But we can take a look, 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.

madpenguin, a great suggestion from -X-. I use VMware Server - really large (~500 MB), but needed it at the time for my XP x64. In order for nLite to be able to handle the WMP11 installer in the hot fix section, WMP11 Slipstreamer must be installed on your system and I suspect the WMP11 installer must have its original MS name. Please let us know how you make out. Enjoy, John.

Sp0iLedBrAt, thanks, it is good to be back to my own machine. Enjoy, John.

madpenguin, you, of course, can run nLite as you wish. You can run it multiple times, although it is not recommended by me and others. In my opinion, you are asking for trouble (have seen MANY). And, it is not necessary. The later versions of nLite will call WMP11 Slipstreamer, so all you need to do is include WMP11 installer and its updates in the nLite hot fix section. If you wish to use some of WMP11 Slipstreamer options, then you can run it separately, before running nLite, as long as you start with a fresh copy of your CD. I use IE8 and have none of your reported problems. I find it faster and more functional. It also has a recovery feature that restores sessions when there is a problem. Again, your choice. I am really not trying to convince you, just countering the negative report on IE8. Enjoy, John.

madpenguin, not nearly enough information. How did you include IE8? 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.