johnhc

milk, your Last Session (at the top) tells us that you have used W7 (as you stated in your reply) to create an ISO for XP. This is probably not going to work if you include an SP, which you have done. That may well be your problem, but I have a question about your source CD. You say "I purchased it at a computer with a keyboard". What does this mean? If you purchased a computer and this CD came with it, then it is a Recovery CD and the copy of Windows can be installed only on the computer it came with - please read the Windows EULA (License). .NET Framework should install just fine under XP. If you will post the error you are getting, perhaps we can help. Enjoy, John.

Patosan, I guess my problem here is the age of the thread and the intermittence of the replies. Sorry about that. Since the only thing in your Last Session is the hot fixes, I am going to suspect them or nLite. I have never caught wind of anyone having nLite problems with Japanese Windows before. So, a technique I learned from Kurt_Aust for determining what Windows updates are required: Run nLite against a fresh copy of your source adding only SP3 and doing an unattended install if you like, but do not apply any hot fixes. Install this on VPC and go to Windows Update and see what updates it wants to install. Copy a few of the oldest and try these on an nLite run (including SP3) and VPC. Let us know what you learn. Perhaps this has been asked before, but have you tried removing nLite, DLing (from the nLite site and checking the MD5) and installing a fresh copy? If you want to go over to a completely non-nLite unattended method, please try the Unattended Guide link above and the Unattended sub-forum. Good luck, John.

Patosan, the only thing I see readable in your 'gibberish' is "ms-ime2002". Google says this is some kind of Japanese language input system. Perhaps you don't have VPC set up properly to run your Japanese version of Windows. There is noting in your Last Session that looks suspicious. I run XP x64, so I do not know anything about your updates. Please post a screen shot of a Windows Explorer view of your CD. Is it a real OEM CD or a recovery CD? Enjoy, John

Patosan, sounds like you have run nLite more than once against the same source. You should always start with a fresh copy of your CD files/folders. OEM versions of Windows work just fine. I have used two (XP x64) with no problems. I hope you mean OEM and not Recovery CD. Some have reported problems with Recovery CDs. WMP11 Slipstreamer works just fine. After you attach your Last Session (as strel requested) we will take a look and maybe have some more suggestions. Enjoy, John.

xmf, I don't have a complete answer for you and no MCE CD to test. You get many hits on this subject here and via Google. Please do some searching. nLite may well have a Media Center removal item. I suggest you run nLite against your CD and look at the Remove Components Task and see if Media Center is there. Looking at Translation.txt in the nLite Lang folder leads me to think it is there. Some of the links I looked at indicated you will have something a little less than XP when you get done removing Media Center. One said you end up with a more capable XP Home that cannot join a domain. Others disagreed. I suggest, if you find that nLite will remove Media Center, that you the build an ISO and run it on a virtual system (VMware Server, VirtualPC and VIrtualBox are free) and see what you have left. Item 3 can be handled with the Unattended Task-Users tab. You can create an Account and assign a blank PW. Please let us know what you learn. Enjoy, John.

mihneafloid, please post a screen shot of the error message. I run XP x64 (OEM) and have no such problem. What is the source of your CD? - OEM, Retail, Recovery, etc? Please look in the file SETUPP.INI (use Notepad) on the CD and tell us what the Pid value is and also tell us what the CD label says (My Computer-Optical drive when CD is loaded) . Enjoy, John.

DzigiBau, I am not sure what you are running Dependency Walker against. I have not used it and know nothing about it. I DLed it and ran it against nLite.exe and found three DLLs missing (see attached). I also ran it against several other .exe files and they all reported the same three DLLs missing. Don't know what this means - perhaps never executed calls to DLLs. What is msvcm90.dll missing from? - nLite, others?? I do not have this DLL in my CD, but it is in the nLite folder although not called out by Dependency Walker. The AddOn that Kiki Burgh pointed to does contain this DLL. I doubt that adding SPs and updates to your system has produced this problem. I would point out that this is the first time I have seen this - many are running fine. I still suspect something is wrong with your CD and nLite is hanging instead of reporting that it cannot handle the problem. I guess it could be something wrong with your system - virus? - bad update? - ?? I don't know where to go from here. Have you researched others using Recovery CDs. Enjoy, John.

DzigiBau, did you take out all four folders are just the one? If just the one, try removing all four. I also suggested that you move the folders to another folder. If this every works, you could move the folders back in just before you create an ISO. Your install may well need some of the files. I have never used a Recovery CD but know some people have problems with them. You can do a search here to see what kind of problems, but I do not remember anyone having the problems your are having. Similar problems have occurred when the CD is copied to the root directory instead of an empty folder (nLite then searches the entire HDD). We have also seen something similar when .NET was hosed. Perhaps I should have told you at the get go that the owner/author, nuhi, is on hiatus and we have not heard from him in some time. Apparently he is very busy and may not ever be able to support nLite and vLite again. I look at most problems as needing a work around since a real live fix may never be available. Very few real nLite bugs have been identified and works around were developed by posters here. Please try removing all four folders mentioned, if you have not, and let us know. Sp0iLedBrAt suggested you consider an unattended install path. There is more than one way to get at this. There is an Unattended Guide link at the top of the page. I do not understand what you mean about checking your .dll integrity. Did you check your CD? How - what program? Enjoy, John.

mzik, please post a screen shot of a Windows Explorer view of your CD. Enjoy, John.

DzigiBau, thanks for all the information. Right now, the only thing I can suggest is to remove the cmpnents, VALUEADD, SUPPORT and DOCS folders and run nLite again. You can just drag and drop them into another folder so they are available later. Did you check the System Log after copying the CD? OK? Have you told us what version of Windows you are running. I am sorry if I missed it, but please let us know. Enjoy, John.

Jack_uk, some MS update do not integrate with nLite and I have seen several problems with XP updates. There are Update Packs that deal with all updates after SP3. I do not use one (running XP x64), but I think the RyanVM forum is the best place to find them. 5eraph makes IE8 AddOns (I use the x64 version) and I think he also makes an Update Pack. As long as you are not including an SP, I suspect W7 may be OK (use Compatibility Mode for nLite.exe). Enjoy, John.

dwalker59, I tried SFC on my nLited XP x64 on my VM and it would not run - getting a 6ba error (RPC Service not available (but it is)). I tried the fix, which is to install a certificate, but SFC continues to fail for the same reason. I tried it on my HW (with nLited XP x64) and it runs OK, but quickly asked for the CD (I did not insert it and canceled). I did find this article describing how to use SFC, including how to change the Registry to use a I386 file on your HDD. I am not sure from your post if you used the correct key. Please give it a try and let us know what you learn. I am not aware of any problems with running SFC on a nLited install. Enjoy, John. EDIT: I had SFC turned off (nLite Options) and that stopped SFC scan from working. When I enabled it in the Registry and did a SFC /scannow on my VM it ran and worked fine. You said "some weirdnesses happening", but did not explain. Often when strange things happen to nLited installs it is because nLite has been run multiple times against the same source. You should always start with a fresh copy of your CD files/folder and run nLite only once.

Jack_uk, please attach your Last Session as requested above. It makes it search-able and easier to deal with in general. Running nLite under W7 to create an XP ISO can be a problem, particularly if you add an SP. XP under a VM should eliminate this concern. You can also try running nLite.exe in XP Compatibility Mode. I would be concerned about your long list of hot fixes. I run XP x64, so am not familiar with XP updates but have seen several problems with them if not correct. If you continue to have problems, then I suggest you remove all hot fixes and try that. I assume you are testing under VM. You are using nLite privately and NOT in a business environment? Please let us hear. Enjoy, John.

DzigiBau, I don't think you are seeing an nLite problem. I suspect the problem lies with the source (OK, nLite could report better) or some yet unknown source. Here's some requests: Post a screen shot of your CD, as requested. Post a screen shot of the nLite page when hung. Manually copy the CD files/folders to a new folder, check System Log for errors then run nLite. Remove .NET, reinstall then go to Windows Update and add the latest updates. I don't think this precludes a possible .NET problem. Some more questions:Have you every nLited this CD before? Are any of your HDDs on a network? Have you checked the MD5 of your nLite DL? One other thing to try is to remove all the extraneous folders from your CD folder, then run nLite. We will suggest the folders when we see the screen shot of the CD. Let us hear. Enjoy, John.

dbueler, I went here and found all kinds of XP drivers. Am I doing something wrong? Enjoy, John.

mzik, like magic? Please read the RED message above and attach as requested. Enjoy, John.

csvaasan, most likely will not work. Please read the message in RED above and attach as requested. Enjoy, John.

masster, there have been some reports of security SW interfering with nLite. You should try running nLite with it all turned off. When I do this I unplug my modem to be sure there is no Internet traffic. Were you running Kaspersky when nLite would not exit? Please see the message in RED above? Enjoy, John.

DzigiBau, one other idea to consider. You might try running with your security SW turned off. When I do this I unplug my modem to be sure there is no Internet traffic. Please let us know how you make out. Enjoy, John.

DzigiBau, please post a screen shot of a Windows Explorer view of the CD and check the MD5 of your DL. The only other thing I can think of is your installation of .NET Framework. You could try removing and reinstalling it. You could also try starting with a new empty folder and do the copy of the Files/folders with a copy/paste operation. You need to make sure that Folder Options-View allow Hidden Files and Folders and System files and folders are not hidden. Good luck, John.

DzigiBau, you do not need any special SW to get a screen shot. Open My Computer, right click your optical drive with the Windows CD in it and click Explore. Then push Alt-Print Screen on your KB. This places the screen shot of the selected window on the clipboard. I then paste it into Paint and edit it of private information, if necessary. The MD5 is a hash code and will tell you if the DL went OK. If you look at the DL site you will see it. There are many free hash code calculators - I use HashTab. This almost absolutely assures you that the DL is good. If the posted MD5 and the computed one of your DLed file are different, you have a bad DL. Where did your CD come from? It looks like it may have some extra stuff in it. Is it OEM, Retail or is it a Recovery CD or something else? Are any of your files on a networked drive? Enjoy, John.

DzigiBau, again, please post a screen shot of a Windows Explorer view of the CD. Also please look in your System Log (right click My Computer-click Manage- Expand Event Viewer and select System) for 'Bad block on CDROM' messages at the time you were doing the copy. Where did you get your copy of nLite? Did you check the MD5 after DL? Have you tried removing/reinstalling nLite? Enjoy, John.

MEGAKILL, you need to read the guides at the nLite site. You don't deal with any of the files already on your system. You must copy all the files/folders that are on your Windows installation CD. Once you copy all these to a new, empty folder on your system, nLite will process them as needed. nLite will do the copying, just point it to your optical drive with the Windows CD. You use the method applicable to what you are doing. If you are going to test under a virtual system, then just do a Create Image. If you do not have an ISO and wish to install on HW, then a Direct burn is in order. Enjoy, John.

DzigiBau, you said that the CPU is running at 50%. Please open your Task Manager and tell us what process is taking half the processor. If you click the CPU column, it will be sorted by usage. Click CPU again and the highest will be at the top. I assume you are copying from the original CD. Is anything really copied? Please post a screen shot of a Windows Explorer view of the CD. Do you see the CD activity LED blinking? Enjoy, John.

gnarula, if you mean to run nLite again against the already nLited source, then no. This leads to bad results in almost all cases. You should always start with a fresh copy of your CD's files/folders and run nLite only once. You can use the Last Session from previous runs to get all your changes included. Enjoy, John.