johnhc

Takino, exactly when are you getting the error - nLite step? Please post a screen shot. Use only the latest version of nLite (1.4.9.1) , run nLite under XP, always start with a fresh copy of your CD (ISO) files/folders and run nLite only once. You also might try the copy of SP3 from the MS DL Center. Is the school's ISO modified in any way - any other program run against it? Enjoy, John.

throbert, be sure you are Editing your first post and click the 'Use Full Editor' button. Enjoy, John.

throbert, thanks for a real .ini, now please change your title. It is hard to comment on your .ini as to what to remove and not. I attach mine for you to look at what I did. I am quite happy but I am sure it is not what you want. As far as the services go, please go to the Black Viper site. He has a great list of services settings and various recommendations. Be very careful about removing components especially services. If you find that you need them later, they are very difficult or impossible to restore without starting over with nLite. Please remember to always start with a fresh copy of your CD files/folders and run nLite only once doing all your work. I strongly recommend that you get a virtual system to test under. VMware Player (I use) and VirtualBox are both free and easy to use. Since you are running nLite under W7, it is especially important to test before going to HW. The weakness in VMs is that drivers are not tested. I noticed your are setting Unattended Mode to Provide Defaults - suggest Fully Automatic. The tweak 'Boot and Shutdown-Ctrl-Alt-Del at logon-Disabled' can present a problem if you forget your PW. All those network adapters you have specified will have no effect unless you specify a MAC address. I suggest you get started (using a VM) and them ask specific questions as they pop up. Please remember to change your title (full edit first post). Enjoy, John

throbert, please don't repeat your posts and see your original post for my reply. The reference .ini is just confusing, please post a real one. Enjoy, John.

throbert, as a start, please change your title (edit your first post) to something meaningful (see forum rules). Your reference .ini obviously confused Sp0iLedBrAt and did little to help anybody. Please post an up to date Last Session.ini for your system. Running nLite under W7 to create an ISO for XP is problematical, especially if you are adding a Service Pack. I suggest you take another look at Kurt_Aust's post. It is a great source of information. It tells exactly how to integrate .NET and DirectX. It is a little much at first but is a great reference and I use it often. I suggest you do not need any hot fixes from MediaFire. Please go to the forum where 5eraph presents his update pack , IE8 etc for answers to questions concerning them. Enjoy, John.

cluberti, I injected the four updates for IE9 that you pointed out to me - thanks much. An install on a VM (VMware Player) went quickly this time. Completing Installation took only about 3 minutes, so the missing updates must have been the problem. You are the best! Thanks, John.

esiu, it is real difficult to get at problems with so little information. Usually we can ask for a Last Session.ini and not ask 64 questions. First you said you ran nLite on a XP Pro x86 (assume 32 bit). This will present a problem if you try to integrate a Service Pack. Kurt_Aust has a work around here. It is also a great guide for XP x64 (updates, etc). The main concern I have is the version of nLite you are using. It should be 1.4.9.1 and DLed from the nLite site only. Perhaps you have an old version. I also run XP x64 and don't remember seeing the 2003. Some programs do think my OS is Server 2003 because XP x64 is based on it and has the same version number (5.2.3790). Also try running with all your security SW turned off. I disconnect my modem when I do this to prevent bad guys from getting into my system. Enjoy, John.

esiu, welcome, I have not seen this error before. It is occurring when nLite is scanning your source. You say the source is XP Pro x64 but the message says XP x64 2003. Sounds like Server 2003 64 bit to me - nLite should work OK. How did you copy the source CD? What machine are you running on (Windows version?) Please look in your System Log for CDPROM bad block messages. Try using nLite to do the copy - just browse to the CD. I had a copy problem once but it did not cause nLite to fail, but the install gave all kinds of strange errors. I cleaned the CD and copied again (getting no errors in System Log). Enjoy, John.

srihariram, sorry I cannot answer your questions. I use 'SetupComplete.cmd' to run a command after first login (file structure is in place) in a flat install (from HDD). I do not use WinPE and am not familiar with it. I would suggest running some experiments in a virtual machine. I use VMware Player. It is free and easy to use. Enjoy, John.

srihariram, yes, please see 'SetupComplete.cmd' in the waik.chm help file. Enjoy, John.

werigp, I do not use MDT (just DISM), so my observations may be off base. It surprises me that the install is complaining about a NIC driver. Did you inject the driver into the install.wim as well as the boot.wim? I went to the Intel DL site and found version 15.7 and DLed it. It has drivers for several architectures and 32/64 bit. There are about 50 .inf files and more than 30 with 64 in the name. Are you sure you are including the correct driver for your System (W7, I assume) and 64 bit? There are at least 3 .inf files with your DEV and SUBSYS codes. Enjoy, John.

stevieg330, I went to the Adaptec site and DLed several of their drivers. It looks like to me that you used aar1210sa_win2k-xp-2k3_drv_b45a, which has a warning not to use it except to supplement the original (Caution: Use this driver to update an existing driver rather than for a full operating system installation.). I would suggest you use the aar1210sa_w2k-xp-2k3_drv_bld10 driver. You should place the txtsetup.oem file inside the W2000 folder then point nLite to it as a multiple driver. Make sure to specify that it is text mode driver. I am not sure how you use the update file except after installation. Please let us know how you make out. Enjoy, john.

stevieg330, welcome. Without your Last Session.ini we could only offer wild guesses. In LARGE BOLD RED LETTERS above is a request for your Last Session.ini. Please attach it. Enjoy, John.

Same hashes. Enjoy, John.

Thanks, urie, I thought that might be it. Enjoy, John.

djonur007, here is another thread of where I started with this. I could find no way to do this without my interaction, so I wrote the AutoIt script. It is fully automatic. AutoIt is a free scripting language (search for it) and fairly easy to use. What I show above is a complete program to install the two theme packs. If you are not familiar with scripting, then you may need to seek some other means to do this or take maxXPsoft's method that requires you to hit enter. You need to also look at the waik.chm file for how to use the AutoUnattend.xml and the <FirstLogonCommands>. If you want to try my method, then you need to DL AutoIt, compile the code I gave you (changing the theme packs to one(s) you want) and run it from your AutoUnattend.xml. It is possible to run a command file at the end of installation. Please see the SetupComplete.cmd description in the waik.chm file. Enjoy, John.

maxXPsoft, I can't find your .cmd file on MDL. Do you use a different UserID there? How about a link to your post? I am not sure what you mean about removing other languages. I followed the instructions in the MDL thread (searching for en-us, etc) and installed SP1 with no problems. It looks like to me that I have removed all languages other than neutral and en-us. Enjoy, John.

djonur007, yes, that is where you place the <FirstLogonCommands>. Please see my other post here. Enjoy, John.

loki9, yes. In the .xml used for the installation, include the command <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <Order>1</Order> <Description>Start my batch file.</Description> <CommandLine>CMD /R %systemdrive%\Run1\Run1-W7.bat</CommandLine> </SynchronousCommand> </FirstLogonCommands>My batch file goes into W:\sources\$OEM$\$1\Run1 and has this command first to find the install source (CDROM): For %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\sources\install.wim set CDROM=%%i:Place your files/folders in a folder at the root of your install source. I call mine Install. Enjoy, John.

djonur007, I am not sure what you are trying to do, but I wanted to install a couple of theme packs, so I wrote a little AutoIt Script: Run(@ComSpec & " /c " &@ScriptDir&"\Gears3.themepack", "", @SW_HIDE) WinWaitActive ("Personalization") Sleep (3000) Send("!{F4}") WinWaitNotActive ("Personalization") Run(@ComSpec & " /c " &@ScriptDir&"\NASASpacescapes.themepack", "", @SW_HIDE) WinWaitActive ("Personalization") Sleep (3000) Send("!{F4}") and ran it out of a Command file at <FirstLogonCommands>. I placed the Gears3 and NASASpacescapes theme packs in a folder along with the script. The active theme is the last one I installed (NASA) when my DeskTop comes up. Both theme packs were DLed from the MS site "get more themes online" from the Personalization screen. Enjoy, John.

-X-, you are absolutely correct! I misread the 'pre' as 'post'. will edit it if I can get the forum to respond. Thanks for correcting me. Enjoy, John.

ravisunny2, Don't have a clue what the audio patch is. Yes. No. Point to each .inf file you need and include it. Please read the guides on the nLite web site and the guide in the Sticky area above. Enjoy, John.

I got a reply from AMD and the SW needed to support C'nQ is maintained by MS via Windows Update.

BigDaddy, in my XP x64 system I DLed and installed a "driver" from AMD for C'nQ. I never used it. You are telling me, correctly, that W7 has this support in natively. I suspect it still comes from AMD and there may well be a later version available. I would not think you would ever need third part SW, buggy or otherwise. I tried to find W7 support for C'nQ on the AMD site but failed. I sent them an e-mail request to get their site working again and will let you know what, if anything, I learn. Please post the BSOD stop code if the error occurs again. I do think you are on to something and it probably makes sense that a C'nQ problem would more likely lead to your crash than a memory problem. Enjoy, John.

BigDaddy, does your main board offer a monitor utility? If so, how are the temperatures and voltages? I have never run Cool'n Quiet, but would agree with you, that all else sounding good, is a good candidate. Enjoy, John. EDIT: If you got your Cool'n Quiet from your MB vendor, you might consider getting the latest from AMD. That is, if you want to continue to run it.