johnhc

Chosen1985, it is not clear what you are actually doing. You say you "tried to reinstall XP" in you Vista machine. Has XP been installed before? Is Vista still installed? Have you found XP drivers for your setup? Have you used nLite? I know of no reasons you would have to use an nLite program to do your install. The 07B error you are getting is saying it cannot find your HDD to install Windows. The first message sounds like your text mode drivers did not get in properly. How did you attempt to install them - F6? Assuming you did use nLite, 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.

Hackez, please tell us how you created your XP install without ANY modifications. If you used nLite, please attach your Last Session. Also tell us more about your source. How was the SP(s) added? Please post a screen shot of a Windows Explorer view of the source folder. Are you quickly multi clicking as -X- is doing? If so, I don't think it is a surprise that a file is busy. I would like you to respond to my suggestions of running Process Explorer (link in my previous reply) and tell us what program has a handle to the file. Enjoy, John.

mshta.exe is the program that executes .hta files by default. Enjoy, John.

Hackez, did you try searching for nusrmgr.cpl? There are lots of hits on AVs. Are you running an AV? I assume yes, have you tried turning it and other security SW off and trying? When I do this, I unplug my modem to protect me from the Internet bad guys. Have you tried Process Explorer to see what SW has the file, nusrmgr.cpl? If nothing shows up, then the first thing I suggest you try is a single run of nLite to do all your work. I really already gave you my standard in the other thread, so here it is again, 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.

Hackez, I think it is trying to says that file C:\WINDOWS\system32\nusrmgr.cpl/nusrmgr.hta is in use. It might be useful to know what program is using the file. I use Process Explorer to determine this. Have you run nLite more than once against the same source? I see nothing obvious with your Last Session, but you have made many removals tweaks including many changes to services and I know nothing about your Update pack. Are you able to test under a virtual system? You may need to do some trial and error testing. There are lots of hits on nusrmgr.hta in Google and one here. They seem to be concerned with an AV going off on the file. Please take at look at these. Enjoy, John.

Hackez, eh? 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.

leozack, glad you are running well. Change the /Passive to /Quiet for no output at all. You can usually get the switches for these kind of things by running them in a command prompt with /? or /help switch. Enjoy, John.

Tralbry, I think the easiest way is to put all your files into the same folder, nLite-Files2Copy, into the directory where your CD files have been copied. Then place this command into the RunOnce field of the Unattended task: Xcopy "%Source%nLite-Files2Copy" "%UserProfile%\DeskTop\nLite-Files2Copy" /Q /S /E /H /K /C /YThis assumes you have defined a user and set it to AutoLogon. You cannot use the $OEM$ folder to place files into a specific user account because the account will not have been created when the $OEM$ folder is processed. You can certainly use the $OEM$ folder to place your nLite-Files2Copy folder into the root directory or other system folders. See this for details of the $OEM$ use. If you want to find out more about the RunOnceEx (not directly available via nLite), see the Unattended Guide link at the top of the formum. Enjoy, John.

Fernando 1, the reason I deleted the files is simply to allow me to attach the 7z file to the forum (limit is 200 kB), not for someone to use. They would have to DL the file from ECS. You may well be correct, I will not be able to test it either, but if you look in the txtsetup.oem, you will see a number of references to Sata1. I assume this means it supports SATA - could be wrong. The reason I think this must be the drivers for both is that it looks like the only text mode driver on the ECS site for the board. Enjoy, John.

I agree strongly with Fernando 1's Side note:. This got me off to a lack of understanding from the get go. This subject has caused me to run some experiments on my XP x64 running under VMware Server. With a running windows, I booted the original CD (this was a bad idea - very very slow compared to an ISO), and selected R for Repair on the second menu presented. I selected Continue on the first not R for Recovery Console. R is for Really bad use of the letter R. The Repair Install began and at T-34, I got a message that AmdLLD64.sys was missing and was asked to specify the directory to find it. I clicked Cancel. At T-29, I got a request to insert my SP2 CD and since I had no such thing or clue what it was, I clicked Cancel. Shortly I got a different message asking for my SP2 CD - Cancel. It was taking so long and even seemed hung, I power down my VM using the Troubleshoot option on the VMware pull down. Today I intended to do a fresh install from my nLited ISO but could not get VMware to boot from my ISO. I kept getting the message that Setup would continue, so after several tries, I allowed the Repair Install to continue (from my nLited ISO). I continued to get various messages concerning files it could not copy and the SP2 CD requests. It did finish and my auto login user desktop came up and I had a running system. It was not a pretty thing, in fact it was behind ugly! The DT wallpaper was mine but the theme was about a third mine and two thirds something else again. I assume some of this strangeness was due to doing half the Repair Install with the original CD and half with my nLited ISO. My hacked boot screen was there, but my Login screen and altered Log Off and Turn Off Computer were not. I then reinstalled (with format) from my ISO. Then I built an ISO exactly the same as the last one except I changed the Unattended Mode to Prompt Repair (even nuhi does not say Repair Install). I preceded to do a Repair Install from this ISO. I got very few prompts during the install (License Agree and maybe one more, no key request), and no errors. Windows came up on my AutoLogged user and looked normal. My Log Off and Turn Off Computer graphic changes were missing, but otherwise looks OK. I was surprised to see the Unattended RunOnce got executed, so I would suggest to anyone interested in making a Repair Install ISO/CD to remove the RunOnce stuff, unless you want it to run again. This is what I know at tis time and hope it helps some along the way. Have fun, John. EDIT: There seems to be a problem with updates. The utility qfecheck does not show most of my updates and WUD is offering one I had originally installed.

I noticed that Automatically Restart is disabled in My Computer-Properties-Advanced-Startup and Recovery-Settings. There is an nLite Tweak under Boot and Shutdown, but I don't have it checked. The Registry change is in nLite.inf to set AutoReboot to zero. I don't understand how it got there. I am running XP x64 and attach my Last Session.ini. Any ideas? Thanks, John.

leozack, I assume you got some of your information from Kurt_Aust's thread. I hope I pointed out to you that it was for XP x64. I meant for you to use the process, but substitute the appropriate XP items as needed. Here is the link for the XP version of KB969897. MS uses the same KB number, just personalizes them for the platform, language, etc. Some of the MS hot fixes will not integrate with nLite. If you will do a search on the forum, you can find if your KBs are in this category. KB951847 gets lots of hits in a forum search. So, maybe you can figure that out there. Sometime MS replaces an update and removes the original. I am not familiar with the warnings you are getting. Have you seen these on other systems you have the SW installed on? Have you clicked on the link provided in the warnings to see what they offer? You might also try Google to see what is available. Hope this helps. Enjoy, John.

chris.b, thanks for explaining why I am seeing two same size but different PIDGEN.DLL files. And they are, indeed, in the ip and ic directories. Thanks, John.

Fernando 1, if you will DL and look at the text mode driver, I think you will see that the ECS driver is mixed SATARAID. Only one .inf file, so I guess you get both whether you need the RAID or not. I attach the file so you can look at it. I have deleted the DLLs and the SYS file so it will fit. Enjoy, John.

bobmiers, great, I am glad you got it working! I recommend you use the drivers I pointed to in my last reply. I finished DLing the driver and extracted it (7-Zip) and it has 10 .inf files but one is a RAID tool I suspect you do not need and it is inside a .cab file. Did you remove the clock.avi from the Components [DeleteBox]? Enjoy, John.

bobmiers, I think I have been working on the wrong problem. It now sounds like you have an AFTER install problem not an install problem. Your text mode drivers must be working fine. You get the BSOD after you reboot after you install normal drivers by executing the .exe driver file you DLed from ECS. We really need to see the BSOD code now. The next time you get Windows to install, before you do anything else, please use the procedure above to disable automatically restart. So, are you telling us you have a running installed Windows until you install the drivers? Here is the ECS Driver DL page. I would suggest you DL the NVIDIA MCP73 IDE Driver dated 2007/11/08, extract them and point nLite to the .inf files. I am DLing them now to take a look - Europe seems to be the fastest, although it is verrrrrrry slow! I'll edit my post if I discover anything new. Enjoy, John.

sublow, you will always have the option to not slip SP3 - just install it after you install Windows. We think that should work. You can also barrow an SP machine, install a virtual system under W7, or use the virtual thingy you were telling us about. Please let us know if that works - sounds like a real possibility to me. To ask again, which version of PIDGEN.DLL did you use? Enjoy, John.

raina, I am really not trying to give you a hard time, but I assume you are preparing your install for you personal home computer. The nLite license does not permit business/commercial use. The only thing I see in your Last Session that looks strange is the Standard PC for Computer Type in Unattended section. I, and most, use Automatic. Please read the help text next to the Computer Type pull down (? in circle). Please post a screen shot of your Users tab of Unattended task with the Raina user selected in the Users Account window. I would suggest you try Computer Type of Automatic and be sure you have checked the Blank Password box. It also does not look like to me that you have set a PW for the Administrator. Enjoy, John.

bobmiers, I am going to PM Fernando 1 and see if he will take a look since you are using his drivers. I don't understand what you mean by I also don't understand why the folders are numbered 015-021 (only 7, BTW) either. I think what nLite does is, using the .inf file you point to, copies all the referenced files so that when the .inf is executed by Windows, the files will be available. For me, I would like to see the link to the driver DL site of the main board you are using. I would also like to see the information on SATA to PATA adapter you are using and the link to the driver DL site, if there is one. NLite has the clock.avi in the [Delete Box] of the Advanced-Components Task. I do not know why it is there but it has never given me a problem but some seem to need it. You need to remove the clock.avi from the [Delete Box]. Are you sure you can install an OS on the SATA attached PATA drives? Enjoy, John.

raina, certainly not a feature. Is the copy of Windows legal and you have a legal key to go with it? What SP does it have in it and how did it get there? If you don't know how the SP was included, please post a screen shot of a Windows Explorer view of the DVD. And finally, 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. Since you have PW problems, also attach your Last Session_U.ini file after you xxxx out all your personal data such as key, PWs, etc. Enjoy, John.

picard, we will be looking forward to getting more information. I think your experiences are not an nLite failure/bug. I am running XP x64 and do many many installs on my VMware VM for testing. It is completely unattended, although I do include text mode drivers, a VM environment does not test drivers. In general more information is better than less, so please give us a screen shot of any errors you are getting (if possible), and the BSOD error code - perhaps 07B (probably text mode driver problem). Enjoy, John.

picard, if you would like to continue here, please post the error you are getting (screen shot, if possible) 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.

sublow, I am curious what version of PIDGEN.DLL you used. I extracted an ENU version of SP3 (using 7-Zip) and found two copies, version 5.1.2600.5512. The really strange thing is that they are the same size but the hashes are different. In a while I will try extracting SP3 with its own process and see what I can find. Perhaps one of these SP3 PIDGEN.DLL's will work on g-force's fix. Enjoy, John. EDIT:I got the same two PIDGEN.DLL files when I extracted using the built in extractor.

bobmiers, this is a tough one. I have never done a multiple OS install, much less on a SATA attached PATA drive. I see no problem with your Last Session and I would expect you to see 8 folders in the NLDRV directory. I do not understand why you only see one. We really need to see the BSOD. I guess your machine reboots quickly, so try hitting F8 and see if you can get into Safe Mode. If you can, go to the Properties of My Computer and disable Automatically Restart (Advanced Tab-Startup and Recovery-Settings) and then reboot. If possible, please consider a virtual system (VMware Server, Virtual PC and Virtual Box are free - I use the first but it is huge compared to the others). Please post a link to the drivers you are using so we can take a look. Do you get any errors during install? The NLDRV folder is in your I386 folder after running nLite. Please take a look and see if it is OK there. Enjoy, John.

sublow, don't know. Please give it a try and let us know. Enjoy, John.