johnhc

sublow, sometime Compatibility mode will help but in your case you are slipstreaming an SP and that will not work. It is possible that you can run nLite under Vista (or W7) as long as you don't slip the SP. I would suggest you continue running Compatibility Mode. Also, 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.

bobmiers, we do need to see your nLite file. You will not see or test your drivers on VM, because VM has its own virtual drives and drivers. NLite places the driver files in the Windows directory in folder NLDRV. You can find both the text mode and the normal drivers there. They will not have been installed since no real HW was detected. We also would like to see your BSOD code - perhaps a 07B. And perhaps you have not included the text mode drivers. 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.

majax79, these other guys may have steered you in the correct direction already, but have you looked at the Dell DL Center? Enjoy, John.

Fernando 1, I finally understand what is being said. In the case of the ISO created with any Unattended option other than Prompt repair, I must press F10 when the F6 prompt occurs. This will take me to the Recovery Console. I was thinking about "Repair Install" not trying to recover from some problem that rewriting the MBR (e.g.) will correct. I looked through all the Recovery Console commands available, and found none that would allow me to do a Repair Install. I conclude from all this that I cannot preform a Repair Install if I originally installed Windows from an ISO built with any Unattended option other than Prompt Repair. If I am wrong, please correct me! I understand that the Recovery Console can be useful (I have used it) to recover from some problems (perhaps viruses, etc), but I cannot do an install that will preserve my current machine state, replacing only Windows files. Thanks Fernando 1 and thanks all, John.

majax79, did you read my previous reply? Please do. Just point nLite (Drivers Task) to the inf files for the drivers you need. You can put more than one Text Mode drivers into nLite, just not more than one for a single device. If you are running a RAID on a SATA controller, then you will need two text mode drivers. Enjoy, John.

rbayne, nLite does not do sysprep, but if you did use nLite to build your ISO, 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. Otherwise, you are in the wrong forum. Enjoy, John.

-X-, I just tried it a couple more times with no luck. Sometimes my host (real machine) gets the F10 and opens the Control Panel. This is not really important to me, I was just hoping to test Fernando 1's suggestion. Perhaps VMware Server does not do a good F-key emulation at this time (Setup). Thanks, John. EDIT, OK, figured it out. I had my fancy KB in 'Enhanced F Keys' mode. Now all the F keys work as in the link -X- provided (thanks). F5 and F7 yield the same results in my VM.

-X-, thanks for your response and the link. Did you test under a VM and if so, which one? I hope to hear from Fernando 1 about the F10 post of his. It also seems like there was a key (F8??) during Setup that would product the Task Manager. I'll look some more. Thanks and enjoy, John.

Thanks, Kurt_Aust. I will PM 5eraph and ask him to look into fixing the IE8 problem (not 5eraph's) in his AddOn. Thanks, John.

cpuwhiz11, you did not comment on using F10 to get the repair option. Did you try that as Fernando 1 suggested? I tried it on my VMware VM and got no response at all. I have the Unattended Mode set to Fully Automatic. I may have missed something Fernando 1 said about using F10. I also tried F2, to get to Automatic Recovery, but that did not give any response either. @Fernando 1, have I missed something? Would you expect this to work under a VM? Would you expect to see the Repair option ever when the Unattended Mode is set to Fully Automatic? Thanks and enjoy, John.

majax79, the text mode drivers go into the Drivers section of nLite. 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.

SlipStreamer, sorry but the information you have provided does not help much. What is the BSOD code? Did you do each experiment starting with a fresh copy of your CD files/folders? 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.

I think this the original and real problem: Since nLite was run more than once, nhelper.exe is getting deleted too soon. If you will look at the posted nLite.inf, nhelper.exe is deleting itself third from the bottom. This means 'missing nhelper.exe' messages are probably being produced during install and some, if not most of the work scheduled, via RunOnce is not getting completed because there is no nhelper.exe. This is leading to varied and weird symptoms. Making decision about what is and is not getting done becomes moot because of the early deletion of nhelper.exe. Have fun, John.

JayDogg, I told you the file - nLite.inf. Enjoy, John.

kobe, the 7-Zip .msi file must be run by calling msiexec.exe. Here is the one from my batch (adjust the path). msiexec /I %Source%AddOns\7z465-x64.msi /Passive %Source%AddOns\dotnetfx35.exe /Passive /NoRestartDon't know what is wrong with your .NET (right name, file in right folder?), but I also stuck my call in the code area. You do need the /norestart or you will get a reboot. I suggest you remove the @Echo off, so you can see what is going on. Enjoy, John.

JayDogg, I still comment that you should not need the Registry tweaks, but you can add the necessary commands to the nLite.inf before you cut an ISO. I use Reg2Inf, found here, to convert the .reg to .inf format. Are you not willing to run an experiment, removing all your hot fixes? Enjoy, John.

I not sure whether it is thought this is all corrected. I hope someone will post when it is believed to be. I continue to get the 'Authorization mismatch' when I preview or add a reply and send a PM. Thanks, John.

JayDogg, sorry, I did not see where you attached your complete Last Session. Do you mean in another thread? You can run a .reg file from RunOnce in Unattended section. The code you showed is part of a .reg file and needs this in front: Windows Registry Editor Version 5.00Note blank line after this line and at the end of the file. However, you should not have to do this. I remove both Tour and Windows Messenger and have neither after install. That raises two questions in my mind: Where did your source come from and what are the AddOns and Update Packs doing to you. Assuming you are really starting with a really fresh, legal and valid copy of Windows, I suggest you strip out all that is in your hot fix section and let us know the results. Enjoy, John.

JayDogg, please don't chop up your Last Session and paste it in the forum. After you have attached (no pasted) your Last Session, we can take a look and possibly help. I suspect (site unseen) that you have run nLite multiple time against the same source and this often leads to unpredictable results. So, I will leave you with my standard advice: 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.

Henrique-S, your steps are way too labor intensive and are far too many. I hope I have advised you before in my standard inculcation - If you have a problem: 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. To start, simply create a new folder, insert your CD and open a Windows Explorer on it, highlight all (Ctrl-a) then copy all the folders/files to your new folder (NOT the root directory). Then run nLite exactly one time creating/writing your ISO in the last step. It is highly recommended that you use a virtual system for testing. VMware Server, VirtualPC and VirtualBox and all free. I use the first one (because I run XP x64) but it is huge compared to the others which are used by most here. Enjoy, John.

kobe, to change your forum password, click on My Controls in the line at the top of the forum that shows that you are 'Logged in as:'. The change PW is on the left toward the bottom. If general, you should get no errors when running nLite. If you are, I suggest you investigate and eliminate all of them. Please attach (not paste) your complete Last Session and tell us about the specific errors you are getting (screen shots, KB #s, etc). gamehead200 is correct on disabling SFC (WFP) to install a modified DLL. Please see the Options task of nLite. He is also correct in that you should run nLite only once against the same source. There is no real need for multiple runs and more than once is asking for future trouble. Enjoy, John. EDIT: You need to remove the Tweak "Lanzar ventanas de carpetas en un proceso separado". This exposes a Windows bug.

Hey guys, I have been telling people they cannot use Repair unless they install using 'Prompt Repair' mode under Unattended Mode of the General tab of the Unattended Section. The Help text for Unattended Mode seems to support this. If F10 really works when 'Fully Automatic' is chosen, that would be great and I will respond accordingly. One thing I do know is I learn something from Fernando 1 almost every day. @cpuwhiz11, please let us know if this solves your problem and tell us what Unattended Mode you used (could just attach (not paste) your Last Session.) Thanks and enjoy, John.

Slasher, I see nothing obvious with your Last Session that would yield your weird symptoms and suspect it is the multiple running of nLite. Please try starting with a fresh copy of your CD files/folders. Last weekend major changes were made to the forum and all of us have been having problems. Please see this thread. Seems to be better today and I don't think it is your browser, although I run IE. Please let us hear how things are going. Enjoy, John.

Henrique-S, look in the file SETUPP.INI on your various CDs. The Pid will tell you what kind of Windows it is. If the trailing characters are OEM, then it is OEM, otherwise I suggest you Google the Pid and it should tell you for sure. I should point out that an OEM copy of Windows can only be installed on one machine - not just one machine at a time as a Retail copy. So, the OEM CDs need to be installed on the machine they came with or the ones they were originally installed on. The last time I looked, NewEgg.com had OEM copies of XP Home for about USD 90 and XP Pro for about USD 130. I have stayed out of the SP question, and I do not know what you don't understand, but: On a running system, you must install SP1, then SP2, then SP3. If you are slipstreaming (what nLite does), you install only one SP, usually the latest, SP3, no matter what the CD contains. Enjoy, John.

A few minutes ago I was not able to login. The solution, after many trials, was to clear the browser cache and cookies. Clearing only cookies did not correct the problem. Enjoy, John.