johnhc

Thanks, mritter. I am aware of the option, but I do not want to uncheck it and again take the chance that I start an installation on the system I am using to setup WPI for a future install. I guess what you two are saying is that I cannot have my cake and eat it also. I suspect you cannot tell the difference between a USB stick and a true HDD. Thanks for your reply. Enjoy, John.

Kelsenellenelvian, I am talking about the message after the timer expires: This is the protection put in to prevent me from accidentally starting installation on the system I am setting up WPI. Thanks, John.

I did an install of W7 x64 from a USB drive and had no trouble finding the path, but WPI paused and asked me if it was OK to Start Installation. I assume it does not think this is a CDROM (it is not, obviously). How do I avoid this interruption without losing the protection of the check when I am running from my HDD. I am running WPI version 7.7.0. Thanks, John.

I restarted with a fresh copy of my DVD, added updates and drivers using dism and then installed it on a new partition on my machine. All went well, so I really don't know what the problem was. I did remove one driver from AMD and stuck with only the drivers supplied my my MB vendor, DFI. Thanks for all the comments. For this install I used a USB stick. The install seemed to go about as fast or a little faster than from a DVD, but writing my files/folders to the stick took 1 hour 20 minutes. I must have the slowest USB stick in existence! I would be glad to hear suggestions for a faster 8 GB USB stick. Newegg has some Patrist sticks in the mid $20s which is rather expensive for the capacity but plenty worth it if they are really faster. Thanks for any suggestions. Enjoy, John.

clivebuckwheat, not sure if that is availabe, but I use this in my AutoUnattend.xml file: My batch file is placed here "E:\W7\sources\$OEM$\$1\Run1" Enjoy, John.

grabben, I am not familiar with the /apply-unattended switch and could find no information on it. My problem was looking for unattended, the switch is /Apply-Unattend. If you used the one with the ed, then try again. MS TechNET seems to have a good discussion of the switch. Good luck, John.

unisev, I'm not sure you can do a .reg file. One way to accomplish the same thing is to convert the .reg file into a .inf file (see RyanVM forum for utility Reg2Inf) and then add it to the nLite.inf (compressed into NLITE.IN_) or even easier is to then convert it into an AddOn. Enjoy, John.

MagicAndre1981, In my first post I said the 07B came before I started trying to install on HW and was fixed by removing a driver. I do know what an 07B stop is - seen many on the nLite forum. I cannot see the Stop Code on my HW install because it happens so fast - thus the title to this thread. Thanks, John.

Tripredacus, as I stated, I am using ATI(AMD) Catalyst 10.4 drivers. I prepared them basically the same way I did for nLite for my XP x64 system. In this case I DLed the W7 version, executed the installer in my VM running W7. Even though I do not have access to the real video card, the drivers get extracted into a folder in the root directory. I saved this folder and used dism to inject them. There is one problem that arose. The dism process could not extract the files in one folder, so I had to extract all of them using 7-Zip (version 9.13 Beta, current released version will not extract them). HDMI audio driver comes out also. I install Catalyst Control Center as a switch-less installer out of my <FirstLogonCommands>. Enjoy, John.

grabben, thanks, perhaps I should have given more details. I have included all the drivers I think I will need in my system. The video (Catalyst 10.4, plus HDMI audio), NIC, AHCI, printer and RAID drivers are all injected. The KB and audio drivers are installed out of the <FirstLogonCommands> exit via a batch file which installs other things like JAVA, 7-Zip etc. I also run WPI to install other programs and tweaks. Right now I can only suspect a driver, but don't know what to try next. Thanks, John.

Tripredacus, thanks for your reply. As I said, I am doing a dual boot. I have set the display to the same same settings I am using right now on my XP x64 system (same HW). Thanks, John.

I have been trying my first HW install of my W7 Ultimate x64 image. It has been tested under VMware Player and seems to install and work fine. When I first tried installing on VMware I had a BSOD (07B) that I chased down to a driver (South Bridge) which I removed and the install proceeded. I posted my Autounattend.xml in the 7UA thread (I used 7UA to build my original .xml) and maxXPsoft commented that I should remove the <RefreshRate>60</RefreshRate> as he had some trouble with it (or maybe his video card). Since my VM installs worked, I left the RefreshRate in and tried on HW. I cannot see the Stop code,so am not sure what the problem is but am willing to try removing the RefreshRate if it is possibly the problem. The process takes so long on HW and I hoping to avoid as many false starts as possible. Since I am doing a dual boot install, I am able to look at the partition created in the install for my XP x64 system. I have found in the Windows\Panther\Setupact.log the following message: Perhaps this is trying to tell me something. Now some questions. What is Panther? Is there any other logs/files I can look at to define the problem? Is there a setting to make the BSOD stay put and not cause an immediate restart? If so, can I do it now with access to the W7 partition and/or via the .xml for the next install? I attach my Autounattend.xml. Thanks for any help to be offered. Enjoy, John.EDIT: I failed to remove my personal data, so will re-attach .XML shortly. EDIT: I have re-attached my .XML - hope clean this time.

mainpage, sorry, but like I said before, I am no theme expert. I DLed my lone theme and stuck it into a folder and pointed nLite to it and it worked. If you cannot find better information searching, then start a new topic asking for help on integrating your themes. There are lots of knowledgeable people here and surely some theme experts. Enjoy, John.

Sp0iLedBrAt, you need the UxTheme only if you have unsigned themes. mainpage probably has unsigned ones, so it is probably needed and is included in the Last Session file. The SFC disable is also needed to allow the altered UxTheme.dll get through Setup. Problems with leaving one or both out will not show up till further than the OP is getting. Enjoy, John.

mainpage, I am no theme expert, but have attached what works for me. It is a complete theme with icons, wallpaper and all. You will see that the top folder contains the .theme file and a folder. This folder contains the .msstyles file, wallpaper file, icons folders and a shell folder. It has been a while since I messed with this, but I think the .theme files contains instructions defining how the other files/folders are used. Hopefully you can find some better detail and/or help here from someone better informed that I. I also attached my .theme file (had to change the name to .txt, so forum would attach). You can open it with notepad. Good luck, John.

mainpage, I think Sp0iLedBrAt is correct, you should talk to your supplier about your CD. Barring that, please post a screen shot of a Windows Explorer view of the CD contents. If it contains a Last Session file, please attach that. See if there is an NLITE.IN_ file in the I386 folder and if so, attach it also. If nLite has been run against the CD before, then you have a potential major problem. Again, I think you should talk to the vendor. On the themes, I only integrate one, so I have it in a folder alone. I suggest you try placing just two themes in separate folders and try that. The fact that it is complaining about hb, says perhaps it needs them in a folder alone. My theme has a .theme file plus a folder containing the wallpaper, icon etc. Good luck, John.

mainpage, the possible big problem I see is that your are running nLite under Vista (or W7) to create an ISO for XP. This can be a problem, especially if you are integrating an SP. I do not see your doing that, unless you have done it in another run. I suspect that the basic problem is that in some of the many theme folders you point nLite to, are themes with the same name (example hb). You should get no error messages from nLite or during install. If you do, then something is wrong. Enjoy, John.

Caelcorp, have you looked at this key to see if there is anything obvious? Enjoy, John.EDIT: Please attach your Last Session.ini and NLITE.IN_ files. The first is found at the root of your nLited CD and the latter is found in you I386 (or AMD64) folder.

A method to create your own Registry tweaks is to use a program like RegShot. I use the one here, but there may be more. I have used it on my XP x64 and my W7 x64 systems. I simply open RegShot, take Shot One, then make a change, then take Shot Two. The program compares the two and displays the changes necessary. Sometime I use it just to lead me to the appropriate key, then I export it and use in my next install. Enjoy, John.

stephaniei, I cannot help with your problems, but have you run Windows System Image Manager (WSIM, part of WAIK) against your .xml files? I found it to be very useful in making changes and verifying the .xml. Good luck, John. EDIT: I looked some more at your .xml and wonder about a couple of things: My .xml has this code and I do not get asked about the image: I also see you have the EN-US code (0409) in several places. Perhaps it should be 0809 - please see here. In the unattend.chm is this code for joining a domain. I do not use this, so don't know if it is relavent, but please look at the unattend.chm for help. Hope some of this helps. Oops, looks like the forum quote mechanism has messed up the formatting - sorry about that.

jordanwb, please read the guide in the stickies above. I hope you have read the guides on the nLite web site. You can point nLite to your original CD (never an ISO file) and it will copy it into a folder for you or you can copy all the files/folders into an empty folder yourself. I simply copy all (Ctrl-A, then copy/paste) into an empty folder. I then copy from this folder into my working folder to run nLite against since nLite should only be run against a fresh copy of the files/folder (and only once). Some are afraid that if you don't have all files/folders visible they may all not be copied. Letting nLite do it avoids this. Running nLite under Vista to create an XP ISO can lead to problems, especially if you are integrating a Service Pack. Best to run under XP. Enjoy, John.

mainpage, then you are in good shape and should not be getting messages that the themes are already added. If you still are, then please attach your Last Session. Enjoy, John.

Sp0iLedBrAt, I don't think you can slipstream vcredist, I do not. I install them out of the RunOnce exit, as shown in Kurt_Aust's great guide. This is a 64 bit guide, but has many great insights/ideas and the principles apply to 32 bit OSs. firsak, If you did slipstream vcredist, then you probably need to start over (fresh copy of your CD files/folders). You cannot slipstream .Net either, but I can't tell if you did. Please attach your Last Session, as requested in the bold RED letters above. My Windows folder is 3.3 GB and the .Net folder is over 300 MB. The System32 folder is 800-900 MB, so you are not too far out of alignment. Most of your program installs are going into the Program Files folders which is not in the Windows folder (in Root). Enjoy, John.

mainpage, I explained to synthro what his problem was. Nuking his HDD is not going to deal with missing drivers. Enjoy, John.

mainpage, you should never run nLite more than once against the same source. So, start over with a fresh copy of your CD files/folders or suffer many problems/much grief. Enjoy, John.