johnhc

b-man, I noticed that you said that you did it in one session. I suggest you should always do it in one session and start with a fresh source. Your last posted Last Session has no hot fixes. Is this true? Since you are running a VM, I suggest you start making test runs with some stuff left in the ISO. E.G., perhaps remove no services and see if it works. I got a bad copy of my CD one time and started making bad ISO with really strange symptoms. Looking in my System Log, I found messages like "Bad block on CDROM". It would be good to check your log for such. Good luck, John.

b-man, the latest version of Windows Update Agent 3.0 can be found in this KB. I suggest you install it and see if it fixes the problem. Is your wuaueng.dll version 7.4.7600.226? I suspect the agent will not correct your problem and I do not know what is going on yet. When you go to WU, it will ask to update the agent if it is not up to date. You said it used to work. Has it worked in your VM or just on the HW? What has changed since then? I also run VMware Server (XP x64) and have no problem with updates (latest agent installed during Windows install). Enjoy, John. EDIT: Please try DLing one of the updates directly from Windows DL Center and see if it will install by running it directly. Thanks. EDIT Again: I would suggest you start SENS (System Event Notification Service). Please look in your event log and see if COM is complaining about SENS not running.

b-man, did you start with a fresh copy of your CD files/folders? I notice that you have a number of services set to 4 (disabled). Did you change any of these? What says "install failed". Please post a screen shot. Have you tried with your security SW off? Have you changed FW/AV lately? I just went over to CIS (Comodo) v4 and it is sandboxing all kinds of things. BTW, I notice you set up a bunch of NICs. The way I read the nLite Unattended page, you must specify a MAC address for these to work. Did these definitions work for you? Enjoy, John.

djwyldeone, I stand by what I said and will also say you are violating the Forum Rules by instructing the OP to DL warez from some other site and violate the MS EULA. John.

Cptmaximum, simple, you can't! Any such attempts are a violation of the MS license (EULA). We certainly do not help people do such here! I suggest you either contact HP and hope they will give you one, or you buy a copy of Windows. Enjoy, John.

ghaliloo, the Dell drivers are found at the Dell Driver Site, but I found no text mode drivers. Good luck, John.

BrandonMills, wow, looks like you are in a pickle. I suggest you look for a new way to manage your PCs. I think the author/owner of nLite does not license commercial use for this among many reasons. I probably should not even go this far, but I disable SFC to do my install, then re-enable it afterwords by copying the original sfc_os.dll file back and altering the Registry entry, in that order. I don't use McAfee, but have seen no problems. I think it is not good to run without SFC anyway. Other nLite users should also take warning that leaving SFC disabled could lead to trouble. For that we are thankful for your report. Good luck, John.

The Day Walker!, great!. I felt that was the answer when I saw the code in the txtsetup.oem file last night. Thanks for hanging in there and also reporting. Enjoy, John.

I do reuse this folder but I have written a small batch fie that deletes files/folders and gets a fresh copy from a copy of my CD that I keep on my HDD. The location of the original folder is kept in the nlite.ini file in the nLite folder of Program Files. Alter all of this talk, I suggest you rerun your build with a fresh copy and see if your problems are gone. Please let us know. Enjoy, John.

Re515tance, I always do. I use a saved Last Session, but start with a fresh copy of my CD files/folders. As with many things you can get away with some changes to an existing nLite modified source, I cannot tell what you can and cannot do. Perhaps nuhi (author/owner) can, but he has not been seen here for quite some time. What do you mean by "WinXP-SP3 image"? Of course you can start with a CD that has SP3 integrated. And it also true that you can integrate SP3 and save that and go from there. I don't even do that since integrating SP2 (XP x64 - no SP3) goes so fast. Enjoy, John.

Re515tance, thanks for the Last Session. Have you run nLite more than once against the same source? You should always start with a fresh copy of your CD files/folders and run nLite only once. I cannot answer your questions about the AddOns. I suggest you go to the thread that provided the AddOn and ask him/her. I install Adobe Reader via the GUIRunOnce exit from the Unattended Task and it ask me no questions and I get no tool bars. I'm using the switches "/sPB /rs /msiEULA_ACCEPT=YES" as per Kurt_Aust. There are several problems with running nLite under W7 (and Vista) to create an ISO for XP. Usually when you add an SP the key will not be accepted but I don't think we have heard of all your problems. Again, are you running nLite more than once? You should be able to run nLite under the virtual system in W7 Professional and Ultimate. Please remember to install .Net Franmework. Enjoy, John.

The Day Walker!, unless you really know what you are doing, don't remove anything from the txtsetup.oem except the USB code I posted. When nLite integrates the driver it will ask if you want the x86 or x64 driver. Enjoy, John.

The Day Walker!, I think I have found the problem. Please see my post and Fernando 1's response (he is the driver expert here) above. Then, please remove the following lines from your txtsetup.oem file. Let us hear. I am almost sure this is the problem. I had the same problem with the same code in my 3Ware-LSI RAID controller except it could not find any drives at all. Enjoy, John.

w1zard, as you said, you have a working system, but I too was surprised that a manual slipstream worked under W7. I think nLite uses the same /integrate switch - certainly looks the same. Interesting. Enjoy, John.

Fernando 1, I took a look at the txtsetup.oem file and found this This looks like the same code that kept my 3Ware-LSI text mode drivers from working. Do you think if The Day Walker! removes these lines he will be good-to-go? Thanks for looking in, John.

w1zard, please see this MS article. Enjoy, John

w1zard, did you really remove nothing? If not, how did you know that was not the problem? I wish the RED message would not place that restriction and simply say if you have a Last Session, to attach it. I know of no way to get around the problem on W7 except the one I mentioned - do not integrate an SP and hope that works. Enjoy, John.

w1zard, one of the know problems with running nLite under W7 to create an ISO for XP is that the key will not be accepted. Sometime you can get away with it if you do not integrate an SP. Since you did not attached your Last Session, as requested above in bold RED, we cannot tell if you added an SP. You can run nLite in a system running XP, under a virtual system (VMware Server, VirtualPC and VirtualBox are free) or the virtual system in W7 if your system is Professional or Ultimate. Enjoy, John.

The Day Walker!, is your controller set to AHCI in the BIOS? John.

The Day Walker!, I think you have the correct driver now, so there is something else going on. Make sure your BIOS is setup properly for your RAID and it is set to AHCI mode. Are you doing a full format? If not, please do. You may need to run Recovery Console and do a chkdsk.exe. When you burned the ISO to CD, did you do a verify? If not, please do. You could try any of several HDD configurations, including the individual drives to see if you can get past this error. Please let us know. Good luck, John.

Signore, you are welcome. I do not know what file type is acceptable. Google may help, or give it a try and see what you learn. I hope you are using a virtual system for testing - VMware Server, VirtualPC and VirtualBox are free. Enjoy, John. EDIT: In your CD there is a folder called SUPPORT, it contains a folder called TOOLS. In the TOOLS folder is file DEPLOY.CAB. If you will extract this file, two .chm files will come out with the other files. Deploy.chm and ref.chm are very helpful to answer the types of questions you have. For example see below.

Signore, using nLite and enabling OEM Information in the Options Task will product the form of the General tab in my attached screen shot. The nLite logo is in file oemlogo.bmp (OEMLOGO.BM_) and the text information is in oeminfo.ini (OEMINFO.IN_). These files are in my AMD64 folder and I assume in the I386 folder for XP. I have no idea how to prevent the user from changing these files. Have fun, John.

DadCat, thanks for reporting and glad you are running. The nLite site is up now. Enjoy, John.

DadCat, have not seen this error before, but others have and these can be found with a search. Did you install .NET Framework 2.0 or above on your VM? Aren't you running W7 Ultimate? It has a built in virtual system. You could have used that instead on installing VPC. Enjoy, John. EDIT: A link I found on Google points to the nLite Site, but It does not come up! EDIT, AGAIN: W7 Ultimate and Pro have the capability of running the "built in" virtual system, but it must be DLed and installed.

The Day Walker!, DL and extract the attached file. Include this driver and nothing else in your Driver section of nLite and see if your install goes OK. I got it from the link I provided above. Let us know. Enjoy, John.