johnhc

Cauptain, you should do it all in one nLite run. Boooogy's WMP11 Slipstreamer is built into nLite now, just install the latest WMP11 Slipstreamer and put WMP11 in the hot fix area and turn it loose. No multiple runs against the same source. Remember, 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.

Flaviss, I looked around for WGAPluginInstall.exe and found a DL here. I don't have any idea if this is the correct or latest one. The MS Download Center has WGA notification KB, but I don't know if that is what you are looking for either. I did a search here on it and got lots of hits, so it has been a popular subject. I suggest you look at these three sources and see what fits. Enjoy, John.

Cauptain, nLite does not deal with hardware. I can only speculate that your VM is not set up properly. You don't have the proper configuration or your VM system does not have the proper drivers for your virtual hardware. Have you asked the question and posted the screen shots on the VMware forum, or at least searched them for ideas? Does Windows run OK, except for the error you show us? Enjoy, John.

I have discovered that using Paint on SETUP_W.BM_, I can change the background color of the GUI setup screen, but only under the following conditions. I must set Black background to No and Classic to Yes in nLite Options. When I do, my HAL9000 GUI billboard (WINNTBBU.DL_) is gone and I get the Classic one instead. This is not what I want, so unless I hear from someone, my efforts are ended. No matter what I do, I do no not get my altered background on first boot after setup finishes. I would also like to hear from someone if this can be changed. Enjoy, John.

arpharazon, some installers will fail if you give them a bad switch, some will simply ignore it. There is a utility called Universal Silent Switch Finder (USSF), found in these forums, which will find many switches for you. The nLite working folder, source folder and Windows installation folder are the same thing. It is the folder you copy your original CD contents into and point to to start an nLite run. Enjoy, John.

arpharazon, did you name your batch file a .txt to attach it or is it really named that? If so, you must remove the .txt that Notepad adds. What is the line "Set Source=%1" in your file for? I don't see where %1 is defined. NLite defines %source before calling the RunOnce file. See the nLite.cmd file in your folder after nLite runs. It may be named .CM_ and need to be expanded to edit the contents. Did you place your .bat in the source folder and your installers in the AddOns folder, parallel to the AMD64 folder? It would probably have been better to start with the the Run1 bat, but you are OK. You certainly don't need the 120 second wait at the beginning. The real intent of Run2 was to be scheduled by Run1 to do some additional work after a reboot. I have never found a use for it. I use WPI. Some installers need /S and some /SILENT and some /Q and others /QUIET - it does matter. That is why I am glad to take the work that others have done and use it. Enjoy, John.

ss4sgoku, find the file deploy.cab in the SUPPORT folder of your CD and expand it. It contains two .chm (help) files. Look at them (Deploy.chm in particular) and you will find some option(s) for some kind of auto-format. Please let us know what you learn. Have fun, John.

fritzman, Welcome to the nLite forum. Well, what does it do? Normally, it takes a while for the SP to install, then it takes a while longer after the completion message before the Next button is available to click, then, you click Next and it goes to the following Task. Give us more information and we will try to figure out what is going on 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.

testerh, I certainly think so. Whenever a shortcut shows up on my DT after an install, and I don't want it, I just quickly stick it into the Recycle Bin - gone! Enjoy, John.

Sotcr, welcome to the nLite forum, but I think none of these are bugs. Certainly not in nLite. All but the first are discussed many times here. If you have specific problems, after searching here for answers, 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.

hellbringer616, there are many free resource editors. I use Explorer Suite (I use XP x64) and XN Restorator. There is a good tutorial in the nLite forum on doing this. It recommends using TuneUp Utilities 2009 so you do not have to touch the EXE, just select your image. You can use it on a 30 day trial, as I did, and it costs nothing. Enjoy, John.

arpharazon, I counted that you had 110 hot fixes in your first Last Session. My last look, Kurt_Aust only had 50 and had added a few since then. I don't think I said they were unnecessary, just looked like there were too many. You need to have VMware Tools64 installed in your VM to get cut/paste to work and it only works for text. You can install it via the Server Home Page, or via nLite (what I use.) Again Kurt_Aust has instructions for how to do this. If you want to pass files, you need to enable sharing over your LAN connection, use a USB stick, or the CD. I use the LAN. Enjoy, John.

I ran several more times with 100% success. I removed the restart feature I had put in via the Startup folder. I also quit deleting the WPI key, but did set the two keys to "no" as mritter had asked. I looked at the Registry after and they are set to "yes", which I did not do, so I assume WPI did. This is usable as far as I am concerned. Thanks, John.

testerh, is there some reason you don't want to delete it? Enjoy, John.

Flaviss, the Autologon option works fine for me. Something else may have caused it to not to work for you - perhaps the multiple runs of nLite. I see no need to give it up. I run XP x64 so your hot fix questions are totally foreign to me. I suggest you look into RyanVM's Update packs. They offer a single source for your updates and the site lists all the included updates. Good luck and let us hear. Enjoy, John.

arpharazon, I pointed you to Kurt_Aust's thread. Please look at his RUN1_XP-64.BAT - can even DL it. Strip out what you don't want and you are done. Also include his code into the nLite RunOnce area. I asked earlier about using a virtual system. Have you considered VirtualBox or VMware Server - both free? It saves time and burning DVDs. I can do an install in less than 15 minutes on VMware Server. Enjoy, John.

pmgant, your link does not work for me either. If Ponce did not clear up your questions, please post a screen shot and, 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.

Flaviss, Sorry, I got confused concerning which disk you were being denied access to and thought it was the D:. Your Last Session looks OK to me, except you need to remove the Tweak "Explorer-Launch folder windows in a separate process". I don't think this has anything to do with your problem, but it exposes a Windows bug. You can turn it off in a running machine by going to Folder Options (Control Panel). I see you are defining an Autologon user. Do you place it into the Administrator group? My reference to a fresh copy of your source, simply means to start with a fresh copy of your CD files/folders. When I started using nLite, I copied my CD to a folder which I don't use except to copy all the files/folders into my Working folder before I start nLite. Reusing a source that has had nLite run against it usually leads to bizarre results. The Last Session will save all your options/tweaks/etc. What I do is save a copy of my Last Session in a separate folder with a meaningful name (I am running two different configurations). As 5eraph pointed out, all your previous Last Sessions are in the Preset folder with time stamps. Remember to copy both the .ini and the _U.ini and if you change the name, make sure the first part is exactly the same for both. I don't think you need to repartition or delete your partition to start with. I use VMware Server and just do a quick format of the partition I am going to install to. If you are comfortable (as I am) that you have a good disk, this should work fine for you. I don't have an idea why you are getting the access denied unless it has to do with reusing your source - could be. Please be sure to let us know when you figure it out. Enjoy, John.

arpharazon, yes DirectX goes in RunOnce, see how Kurt_Aust does it in his batch file. Please attach you Last Session. Are you going to try to narrow down the bad driver? Enjoy, John.

TerryFox, great! Glad to help. Have fun, John.

Flaviss, did you format your D: partition before the install? If not format it now, before you take down your Windows installation. Setup will not format any partition but the one you are using for the Windows install. As 5eraph said, attach your Last Session and, 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.

arpharazon, exactly. Please see his last post and go back and you will see his post concerning changes to the first page. Enjoy, John.

hellbringer616, you are welcome. Please let us know how you make out. Have fun, John.

Steve_stewart, to emphasize cluberti's point, please open SETUPP.INI, probably in your I386 folder of your CD, and post the value of the Pid. One of the really nice features of nLite is to allow your to install text mode drivers for your machine without using F6 or a floppy. You need to find the proper text mode driver for your machine and DL it. When you have extracted it, open the folder and you should see (among others) an .inf file and and a txtsetup.oem files. Point nLite (Driver section) to the .inf and you're good to go. Now, 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.

docmorris-17, I suspect you are going to get very tired of waiting for nuhi to tell you what is wrong. I told you before that changing to Automatic processor type would not correct the problem. Did you do any of the things I asked you to do? Did you remove nLite and DL a new copy? Did you check the MD5 of the new copy? After you do this, install and run nLite, look at your nLite.inf (mine is 23,000 lines or so). If your nLite.inf has only 280 lines, please let us know. You may have to remove and reinstall .NET Framework. Enjoy, John.