johnhc

Patosan, I am not sure what you have there in your CD, but it is not an OEM CD that I am used to seeing. The VALUEADD, BOOTFONT and DOTNETFX folders are not present in my OEM CD files/folders. There are a couple more files I have you do not have and vice versa. I bought mine Online at newegg.com and they are Microsoft official OEM for system builders. Yours looks more to me like a recovery CD - one that ships with a new computer used to recover the OS in case of a bad crash. If the BOOTFONT folder is not too large, please compress it (Zip or 7-Zip) and attach it. You should look at the folders I mentioned and see what if anything you can learn. I could be mistaken about this, and hopefully someone else with more knowledge than I will comment. Some people here have been successful running nLite against a recovery disk and some not. If it is truly a recovery CD, then the shop should not have sold it to you. In any case, at this time, I am now very suspicious of your source. Please try posting some or all of BOOTFONT and VALUEADD folders (compressed) for us to peruse. According to Google, VRMHOEM_JA, at least the English version (_ENU) is XP Home Edition with SP2. One more thought: please search for a WINNT.SIF file and if you find it please attach it. Before you attach it, please open it (I use notepad) and see if it contains a product key and/or account id/passwords. If so, please obscure these. Enjoy, John. EDIT: Here's an idea for information on the Unattended section of nLite - or any section. Open nLite and go to the Unattended section. Select each tab and the each Help item on the tab - click the ? in a circle. Enjoy.

Patosan, I am still a little suspicious of your source. Please post a screen shot of a Windows Explorer view of the CD. You did not answer my question about the source being altered previously or what SP it came with. Thanks, John.

Patosan, OEM is fine, that is what I use (XP x64) with no problems. Just wanted to make sure that something suspicious was not going on with the source. So, does the Japanese version of Windows install in VPC, no errors, with the XML hot fix NOT there? Enjoy, John.

Orgyx, here is one I found and another. There are probably lots more. You can also use .bat files to update the Registry. It depends on what you like and know how to use. Enjoy, John.

Patosan, I recognize only one character (origin, root) in your error message. Could you please provide more detail? Have you tried it without the one update? If not, please do. One of the powers of nLite coupled with a virtual system is being able to run quick tests. Be sure to start with a fresh source copy of your CD file/folders. The next area I would like to explore is the source of your Japanese Windows CD. Is it OEM, Retail or something else? Has it been altered by anyone using any program before? Did it come with an SP and if so, which one? Please look in file SETUPP.INI (probably in your I386 folder) and post what the value for the Pid is. I know any number of people have successfully used nLite against a Japanese version of Windows. Thanks and enjoy, John.

Orgyx, what do you mean? If you mean you specified the Tweak and it is not working, then perhaps you have run nLite more than once, 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. There are several ways to include Registry entries. I think about the easiest is to use the RunOnce exit in the Unattended section. You can run a .reg file here or use a batch (.bat) file. There are plenty of examples in the forum of these. Enjoy, John.

Patosan, well, I hope you don't give up. Thanks for the attached Last Session. The one update you include, KB954459, is for Microsoft XML Core Services (MSXML). I am not familiar with this. Is it automatically installed? If it is not there, no telling what the update is doing. You might try removing it and see what happens. I think this is the SP3 you need - can't read (or even see most of) the text on my system. I need to give you my 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. Please report when you have a solution, so others can benefit. Enjoy, John.

DMahalko, I have two suggestions. First, please see the Unattended Guide. It shows how to include text mode drivers in the CD image and, of course, has no license restrictions. Second, see this thread. It shows a txtsetup.oem file file containing code to allow a USB floppy to load F6 drivers. I had to remove the code to get nLite to accept the driver. Perhaps you could include the code. Here is another thread on this. I also agree with Sp0iLedBrAt on the bootability. I started using ImgBurn to build my ISOs and DVDs and have had no problems since. It is freeware and I think does not have the restrictions nLite does. Please let us know what you learn. Enjoy, John.

jackXattack, you are welcome and thanks for the update. Enjoy, John.

Comage, most SPs and MS updates can be directly integrated (slipstreamed). If you run SP3, for example, in a Command Prompt with a switch of /?, a list of valid switches will be displayed. One is the /i:path switch. The path is specified as the folder containing your Windows source files/folders. The SP will then be slipped directly into the source. This is how nLite does it for you. I still would like to know how SP3 was integrated. Did you run nLite and just integrate SP3, then save this folder for future use? It is OK to do this, but it is not OK to run nLite multiple times doing other functions without possibly causing problems. It may cause real problems to use some other program to integrate SP3, then use nLite on the source. I guess I have missed that you were successful using the non-RAID drivers. Did you start with the same source folder with SP3? Any other differences? I do not understand why the non-RAID drivers work, but the RAID do not. I assume you have copied the txtsetup.oem file into the Win32 folder and pointed nLite to the Win32 folder - true? I assume you have used the Adaptec process to define a RAID and format it (if needed)? Is it possible to run nLite under XP (32 bit)? The drivers that Fernando 1 (driver expert here) pointed to are the 3.00.00.63 version. If you think your current effort is at a standstill, then try these. Please let us know. Enjoy, John.

Comage, I don't understand the driver version you are using. Please gives us a link to your DL. I DLed the drivers from the above link, and I get version v3.00.00.63, not 1.02.xxx. Am I completely off base? Did you slipstream SP3 by running it with an /I switch? If you used some other method, that may be the problem. In any case, can you try to use your original CD contents and add your SCSI driver and see if that will work? Please let us know. Enjoy, John.

T3KN0F0B1A, I suspect you are wrong about SP3. You never posted your Last Session, as requested, but perhaps it would show the problem. Did you use Vista to slip SP3? If so, that is the problem. No telling what other problems you would have encountered if you were able to continue. Many, many people have slipped SP3 and not observed your problem. Enjoy, John.

T3KN0F0B1A, I don't have an floppy either, but I do have a floppy controller and you probably do also. What is your Windows XP source? Is the fdc.sys file in the original folders/files? 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.

pedrocamarero48, after you run nLite, a file named Last Session.ini is created and stored in your source folder. The information in it is very useful for helping you, but please attach (not paste). There is also a Last Session_u.ini that contains private information and normally should not be posted. Enjoy, John.

Comage, I think most of your issues have been dealt with by all the others, but I have one concern. How did you slip SP3? I see you are using Vista (or W7) to run nLite to create an ISO for XP. This may well not work. Is it possible for you to run nLite under XP (32 bit)? Enjoy, John. EDIT: You might consider rewritable media. I use DVD+R/W for my HW testing. Saves lots of coasters.

jackXattack, I see two major concerns. First, you are running a down level version of nLite. Please DL the latest (1.4.9.1) from the nLite site and start again. Second, you are running nLite under XP to create an ISO for XP x64. If you have added an SP this is not going to work. If you have not added an SP, then you will probably be OK. I know nothing about the applications you are talking about, so if you want help on them specifically, then provide links to them. But first, get the latest nLite and let us know if your problems are gone. Also you need to remove the Tweak "Explorer-Launch folder windows in a separate process." It has nothing to do with your problem but exposes a Windows bug. 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.

Alintoro, not being a heavy user of AddOns, I may not be the best to recommend. But, I suspect it is not the 7-Zip, IE8 (either), or .NET. I would be less suspicious of Unlocker and Reader Lite. You don't need to test one-by-one. For example, take out all but the ones I mentioned, and test. Still get the error, then take out half of them, if no error, put in half the ones you took out. This is kind of a binary search and you should be able to find the bad one in a few iterations (3 or 4). Since it does not happen on VM, it may be an AddOn that has a driver in it. Since your VM does not the have the requisite HW, the driver is not loaded and the error not detected. This idea guided my choice of AddOns. You might look at where you got the ones you think contain drivers and see it they recommend disabling SFC. Please let us know what you learn. Enjoy, John.

Comage, plenty of people, including me, have included SATA/RAID drivers (Setup calls them SCSI or Mass Storage), but I do not know if anyone has included real live SCSI drivers. I see no reason why it will not work, though. If you are using nLite, then unless you have disabled OEM Preinstall in the Unattended section, you cannot use F6 to include any drivers. Obviously, Setup finding no drives sounds like a driver problem. I had a problem recently with 3Ware RAID drivers with the same message. It turned out to be an over anxious txtsetup.oem file allowing USB drives to be used to include the drivers. Please give us more detail, 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. Also attach you txtsetup.oem file for the SCSI driver. Enjoy, John.

pedrocamarero48, what first post? 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: I get many, many hits when I Google nvrd32.sys. Many people are missing this file. Are you trying to install from a USB stick? If so, see the forum here on USB stick install. You cannot just copy the CD files to the stick and expect it to work.

Sp0iLedBrAt, I sent an e-mail to Dmitry. I then tried TCP-Z. It reports my upped limit to 200 correctly. Enjoy, John.

arunice, nLite will do this for you but not in an .exe. Perhaps I do not really understand what you are asking. I suggest you start by reading a few of the posts here and spend some time at the nLite site reading the guides and FAQs. I certainly do not understand what you mean by Windows installs the drivers it needs to support the hardware it detects. If you don't want a driver installed for a certain piece of HW, simply do not include one. Enjoy, John.

Sp0iLedBrAt, just for grins I DLed and ran the Half-open limit fix 4.1. I got an error message saying I have an unsupported version of tcpip.sys. Perhaps this is because I have used nLite to patch the limit already? Enjoy, John.

gianalf, I run WMP11 Slipstreamer from within nLite when I do my one nLite run. You can run the Slipstreamer first on the source, then run nLite. This works fine. I would not have recommended that you install WMP11 after Windows install. I think Nero can be made to work correctly (think I did it once some time ago), but I agree that IngBurn is a much better choice. Glad you are running. Enjoy, John.

Alintoro, I played with SFC some time ago and I am beginning to think my memory is not serving me well. I thought there was a statement somewhere that said if you used the uxtheme Option, you needed to use the SFC disable to get rid of the message you are getting. I could not find it. Since nLite alters a dll to implement uxtheme options it does make sense to me. I also seem to remember that there was a way to see the file that SFC was complaining about. I was also mistaken about not finding the DoUxTheme (I called it SFX, for some unknown reason - Of all the things I have lost, I miss my mind the most, Unknown author) Patch but it is there. I hope you are testing under a virtual system (VirtualBox, VirtualPC and VMware Server are all free), so you can try some things. I would suggest that you try not setting the uxtheme option and see if that corrects it, then do the AddOn suggestion I gave earlier. Enjoy, John.

Sp0iLedBrAt, I found this via Google. I don't think it will not do what you asked for, but should correct your problem. Enjoy, John.