johnhc

Sorry, jaclaz, I addressed the wrong person. LDouglasLJr, I think what I meant is do you have a txtsetup.oem in the folder with the .inf file? Have you considered nLiteing your source and only the text mode driver? Good luck, John.

Good luck, GrofLuigi. I'm running an AMD CPU, so your stuff looks strange to me. John.

Tlee, I see no problem in your .ini, but you did not answer the other questions in my post. Enjoy, John.

jaclaz, I am pretty much out of ideas. Please attach your aac.inf file, so we can take a look. The only other things I can think of is to nLite under W2K or perhaps try an integration with only the text mode driver. Sorry I can't get a grip. John.

adiabolist, Not even a wild guess. How about attaching (not pasting) your LastSession.ini? Enjoy, John.

atolica, What is: ?John.

Tlee, There is not enough information to guess what your problem might be. What source are you starting with? What OS are you running nLite under? I have never heard of HFSLIP. Why are you not using nLite to direct integrate WMP11 with WMP11 Slipstreamer? Do you nLite your source more than once? You should always start with a fresh copy of the source CD files/folders. Please attach (not post) your LastSession.ini. Perhaps spending some time looking at posts in this forum (if you have not) will aid understanding what others are doing and experiencing. Enjoy, John.

GoodGuy98, I think nLiteing the same source more than once is a common mistake and I agree with you that the documentation is lacking. I guess that is one price we pay for free SW. Here is a post about a walkthrough. I have not spent any time there but it has many screen shots. Basically you should do every thing in one nLite session using a fresh source. Enjoy, John.

GrofLuigi, I don't have much help. Perhaps nuhi is the only one who can help. I looked at your cpu.inf files and at my CPU.IN_ (used 7-Zip to decompress). Mine has no changes (at least no nLite note at the bottom) and I did not remove any CPU drivers. What version of nLite are you running? Have you nLited the same source more than once? What OS are you nLiteing under? Please attach (not paste) your LastSession.ini. My only suggestion is trying an nLite run with no CPU drivers removed. Good luck, John.

GoodGuy98, You basically start over to update a driver. You should never run nLite on a source that has been nLited before. If you are only updating a couple of drivers on a running system, then remove them through Add/Remove, reboot and install the new ones. You might want to run Driver Cleaner (Google) also. I have Automatic Updates set to 'Notify before download' and have seen no problems. My LastSession.ini has 'AutoUpdates = 3' in it - check yours. Enjoy, John.

higina, You should go ahead and upgrade to nLite 1.4.9.1. I don't think this will help, but it will eliminate one factor. Information in the error message all point to .NET Framework. Do you have all the latest updates? I remember when I updated .NET 2.0 some time ago, it was compiling routines for several boots after the update. Perhaps it is not through with that. If all else fails you might try the latest .NET (MD5 D481CDA2625D9DD2731A00F482484D86) after removing your current one. Be sure to check the MD5 hashes for both nLite and .NET. Hopefully someone will respond who has seen this error. Good luck, John.

LDouglasLJr, I see nothing in your LastSession that looks suspicious to me. To try in Compatibility Mode: Open your Program Files folder-right click nLite.exe-select Properties-select Compatibility tab-check 'Run this program in compatibility mode for:' and in the pull down list select Windows 2000. Be sure to start fresh. Please let us know if this helps. Enjoy, John.

Here is a rather extensive discussion on this subject. I suggest the WPI route. Enjoy, John.

LDouglasLJr, I am on shaky ground here, because I know almost nothing about W2K. What Window's version did you run nLite under? If XP, did you use W2K Compatibility mode? Did you install W2K drivers including the text mode driver for the array controller? Did you nLite the same source more than once? Always use a fresh copy of your CD source files/folders. Please attach (not paste) your LastSession.ini. Good luck, John.

net775, Windows Update Downloader is jcarle's program and I suggest you post in his forum: Post here Perhaps you can find some help with a search. He will probably want to see a copy (screen shot) of the error message and what version of WUD you are running. Be sure to say what Windows you are running. I assume you have looked in Add/Remove to see if .NET Framework is installed. Enjoy, John.

Eyael, Can you use a computer that has XP on it? I seem to remember several posts indicating it was not possible to nLite a WMC source and I do not know if this extends to making XP ISOs. Please do a search on WMC here and see what you find. You might also look at the WMC system and see if it has a XP SP2 Compatibility Mode. Good luck, John.

higina, Hard to say since I can't read the error message. What version of nLite are you using? Do you at least get to the first screen from nLite? Do you have .NET Framework at least version 2.0 installed? Did you check the MD5 of the download? Have you tried it with your security software turned off (I unplug my modem when I do this to block Internet bad guys)? Any other information would be helpful. Enjoy, John.

jace5869, You right click My Computer and select Properties. I know of no way to remove this and am curious why you want it removed. You may be able to nLite a XP 32 bit source on a Vista machine by using Compatibility mode (right click nLite.exe-select Properties-Compatibility tab-select XP SP2 Compatibility Mode). Enjoy, John.

crazyjust, I see nothing unusual in your LastSession.ini that I think might explain your problem. Therefore, I assume it has something to do with the changes you have made to the boot and setup files. I would suggest you try making an ISO (I hope you are using a virtual system such as VirtualBox or VirtualPC) with just your nLited source with the original boot and setup files and create/burn with nLite. Let us know how it turns out. I am sure more than one of us are interested in why and what you are changing in the boot/setup areas. Enjoy, John.

TranceEnergy, Thanks. I was mainly just curious what the thinking was. Thanks, John.

crazyjust, There is not much information to go on here. What are you using to burn the DVD? Did you add the boot sector? If you are not using nLite, perhaps you should try that and see what happens. I use nLite to burn all my CDs and DVDs. If it is rewritable, be sure to erase it first. I would assume that the setup.exe is associated with the install and not the boot, but perhaps you could share with us what is modified here. Please attach (not paste) your LastSession.ini. Did you alter the ntldr or any of the boot files? Enjoy, John.

Kurt, I am curious why you offer C++ 2005 instead of 2008? I do not use it, but when I finish my installs, I see that I have C++ 2005 in Add/Remove. On my real machine I have C++ 2008 SP1 (as well as 2005). I don't know how they got there. I suspect that VMware Server installed it, but I did not explicitly. I just tried to install VMware Server on my VM guest but it would not let me. I suspected as much, but was curious if it would install C++ 2008 - it did not. Thanks, John.

kujaff, The Program Files path is on the General tab of the Unattended section. Enjoy, John.

crazyjust and Lodoss, I tried this and it does indeed work but had unintended consequences. When my install was complete, I had my file on C:\Documents and Settings\account-name\Desktop, but the files for my account were all of the form C:\Documents and Settings\account-name.computer-name. This was not what I intended. I assume Windows install saw the account-name level in the Documents and Settings directory and created a new name. I am afraid the same thing will happen to the All User account also. I tried placing a file in the All User Desktop folder and it does not show up on my DT. Here is a link explaining the $OEM$ folder: MSFN $OEM$ Discussion You can create the folder if it does not exist or add your directories to it if it does. There is no special instruction to nLite. NLite will create the folder if you don't. I have not tried the Runonce exit but I am also afraid it will have the same bad effect - hope someone will try, however. I do place files in the Windows and System32 folders using the $OEM$ folder but will stick to WPI for copying files and folders to my DT. Enjoy, John.

HowdyDoody, You are welcome - glad to help. I assume there would be a registry tweak to fix it at install time. If you are interested to pursue, then a new thread with this subject may find someone who knows. Enjoy, John.