johnhc

scottp, I have not reread all your thread, but have some questions. I see you included no drivers, so, how did you install them? Have you run nLite more than once against the same source? You should always start with a fresh copy of your files/folders and run nLite only once doing all your work. Running nLite more than once can lead to many strange symptoms but I have never heard of performance problems. What video card do you have and what driver are you using? I run XP x64, so don't know much about 32 bit updates, but I am concerned about yours, including ones converted into .cab files. You might want to consider going to an Update Pack and dropping the media player updates and see if your performance problems decline. Enjoy, John.

Longshanks, you obviously have an Internet connection somewhere since you are responding here. So use that machine to DL CPU-Z (as I suggested before - Search for it) and find out all you can about your HW. You can write the program on a flash drive or CD and load it into your XP system. There are two versions of CPU-Z, one that installs and one that is simply a .exe file you run. I suggest you use the .exe file. You can do the same with the NIC driver once you identify which one to DL. Do look in the Device Manager (Right click My Computer - Manage - Device Manger) and tell us all the items that have a yellow Bang (! in yellow triangle) on them so we can suggest what next. Enjoy, John. EDIT: Please edit your first post and change the title to reflect your 07B.

Longshanks, I have arrived late to this thread but have some comments. I was going to suggest your try Fernando 1's drivers which you have found. If you have problems, then you might consider posting in his thread. He is the driver expert here and can surely help you. I don't know about the other drivers you may need, but knowing your Main Board type could make it possible for you to find drivers at the MB Vendor's site. CPU-Z will tell you this and much more about your machine. Also, I would ask that you edit you first post and change the Stop code to 07B in the title and elsewhere to prevent others in the future from being misled. Thanks and enjoy, John.

Fuzzy, welcome. Between the nLite web site and the Reference Guide in the Stickies above, you should be good-to-go. I suggest you integrate SP3 (don't need SP2 at all) and your drivers. As long the CD is intended for just one machine, no reason not to include the drivers. If your HDD is SATA, then you will need the SATA text mode driver to get the install to work and integrating it is much better than using F6 during install. It is good to lurk a forum for a while - much to learn. What, I think, you have seen is: always start with a fresh copy of your CD files/folders and run nLite only once doing all your work. You should not run nLite against a source folder (simply a copy of your CD) that has been nLited before. During processing, nLite modifies files and creates new files and revisiting these does not always go correctly and avoiding it is the best strategy. Please attach (not paste) your Last Session.ini (not _U.ini) if you have a problem. It is found in the source folder after running nLite. Enjoy, John.

vinifera, the batch file is using the %1 as a parameter. Use %%1. You can test this simply by running the batch file in a command prompt. Enjoy, John.

Great find, cluberti! That appears to have corrected the problem. Thanks, John.

vinifera, looks like you do not need the quotes around the %1. Help and Support (W7) shows this assoc .pl=PerlScript ftype PerlScript=perl.exe %1 %* The %* gets the parameters. Enjoy, John.

chrisbraines, you are welcome. Glad to hear you found a good solution. Enjoy, John.

maxXPsoft, thanks for your reply. I observe this on HW and VM. I install on HW from a flat (HDD) and an ISO image as a virtual CD on VM. I do have my USB printer plugged into my HW so I could unplug it when installing on HW, but no USB devices attached to my VM. I also format the partition I am installing on on both HW and VM. When installing on HW, I start it from my XP x64 system and have an active Internet connection. On VM, I am not sure if there is an Internet connection. Perhaps Setup is doing something on the Internet or waiting for a timeout. Thanks, John.

Tripredacus, my W7 system is up to date including IE9 updates. I just DLed another copy of IE9 Beta from MS and it has the same hashes. The interesting thing is that IE9 looks amazingly like Chrome. I guess this is what Google gets for making Chrome open source. Thanks for your reply. Enjoy, John.

I am installing Windows 7 Ultimate x64 unattended in both HW and VMware Player. When either gets to the Completing Installation step, it seems to stall there for a long time (> 15 minutes). If I let it go on the HW, the monitor goes black due to the time out. When doing an install on my VM, I can see the CPU activity and it is minimal. On either type, the HDD activity is very minimal. Eventually it starts up and completes the install. I hope some will comment on their experience and what may be causing this delay. Thanks, John.

skybox, thanks for the Last Session. Yours is very simple and I see nothing that could cause your BSOD. I do agree with Sp0iLedBrAt that you should try Fernando 1's driver. He is the driver expert here. Using all those various versions of the driver is asking for trouble. If all the driver files (xxx.sys) have the same name, then only the last one is used. If it is not the corrected one then your install (on HW) will not work. These driver issues are not your VB problem, however, since VB will use it own virtual drivers. Did you run nLite more than once against the same source? You should always start with a fresh copy of your CD files/folder and run nLite only once doing all your work. I am curious why you did not integrate SP3? Where did your source come from and what type is it - OEM, Retail, Recovery or ...? You might try removing all your drivers (starting with a fresh source copy) and installing on VB. Please let us know what your learn. Enjoy, John.

skybox, without your Last Session.ini, as requested in BOLD RED letters above, we have little chance of guessing. IF VB is anything like VMware Player (that I use) it does not use your drivers but has its own set of virtual drivers. Enjoy, John.

chrisbraines, here is the link to the Unattended $OEM$ structure for XP. I could not find one for W7. I think you can get the right idea here. I suspect you will have trouble using the $OEM$ folder with the User path because the users have not been created when the $OEM$ folder contents are copied. Enjoy, John.

Tripredacus, thanks for your reply. I would think a heads up would be appreciated here. Don't know what IPS is. So, enjoy, John.

scottp, I suggest you need a base to work from. After installing a virtual system to test your ISOs, please create one with nLite having no updates or AddOns. Install it on your VM and see if there is a problem. Also consider an Update Pack for all your post SP3 updates. Add in the updates and test. Then add all your AddOns and test. Narrow down the problem if it crops up. The free virtual systems I am aware of are VMware Player, VirtualBox and VirtualPC. Be sure to always start with a fresh copy of your CD files/folders and run nLite only once doing all your work. Enjoy, John.

I would really like a response to this problem. Is there any support for W7 and/or IE9? Thanks, John.

The X, you are welcome and your English is just fine. Enjoy, John.

pistonbroke, you should always start with a fresh copy of your CD files/folders and run nLite only once doing all your work. I too have had CD copy errors. These led to strange errors as you are seeing. Please look at your System Log (right click My Computer-Manage-Event Viewer-System Log) around the time you copied your CD. If you see CDPROM errors (Bad block on CDPROM), then the copy is bad. For some reason Windows does not see fit to report these errors. I would suggest you clean your CD and optical drive (I use a cleaning CD), and do the copy until you get no errors. If you continue to have errors and the CD looks good, then try another machine /drive. After you get a clean copy then run nLite again as I stated at the start of this. Enjoy, John.

nihonko, you are including a bunch of drivers that are basically the same but different versions. If some have the same diver file name (xxx.sys) then only the last one is used. If this is not the correct one you get a 07B Stop code. So, please do as Sp0iLedBrAt says - include only the drivers you need. Enjoy, John.

Bendfella, you don't need a batch file. Simply place the Office2003.exe file in your source folder root and use the RunOnce tab in the Unattended task of nLite to execute the file. Enjoy, John.

The X, here is the Registry key I use to set the page file. I assume you can alter it to suit your needs. Reg Add "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" /V PagingFiles /T REG_MULTI_SZ /D "%SystemDrive%\PageFile.sys 2048 2048" /F I am curios, why would you not want to have your page file on the SSD? I set my file size to a fixed size, so the system does not change the size and fragment it across my HDD. Enjoy, John.

RightBrain, I don't know what kind of RAID you have, but if you will post a link to the driver, we will take a look. Please look in your nLite processed folder for folder NLDRV, probably in your I386 folder. Your driver should be in there. Since you had only one driver, there should be a folder named 001 with your driver files. Let us know what you find. Enjoy, John.

scottp, you also need to remove IE8 updates since you did not install IE8. There is no automatic notify when a post is replied to here. I have never looked but you may be able to enable some such function. If you have further trouble with your install, then remove all updates and see how it goes. Also, always start with a fresh copy of your CD files/folders and run nLite only one time doing all your work. Enjoy, John.

RickSteele, thanks, again. I will keep an eye on it. Enjoy, John.