johnhc

malcolmx, If you have nLited the same source more than once, then that could be the problem. Always use a fresh copy of the source CD files/Folders. HowdyDoody, Right click the DeskTop, then Properties-Appearance-Advanced-pull down Item list to Icon and set the size to your desire. Don't know how to do this in nLite. Enjoy, John.

crazyjust, Sure there is. Probably the easiest is to use WPI (see forum a couple below nLite). First create an account using nLite Unattended section and set it to autologon. The account will be logged on in the final reboot of the install. WPI will then run and you can copy what ever you like to the desktop or any other place. I do this on each install. There are other methods that may have an inherent problem with the path structure not being create yet due to the account initialization not being complete. If you are using a virtual system (e.g. VirtualBox, VirtualPC) then you could do some experiments and let us all know what works and what doesn't. RunOnce (Unattended again) may work. You can place you file on the CD during the Bootable ISO section (see Explore at bottom). You can create a structure like this in your source root: $OEM$\$DOCS\account-name\DeskTop\file-name. You would replace account-name and file-name with what you want. If this works, then the file will be on the desktop when the install is complete. It would be nice if you could let us know what works. Enjoy, John.

hp7166, We have no idea what you are seeing. Please post your error messages (screen shots)? Did you check the MD5 on the nLite DL (what version?)? Do you have .Net Framework 2.0 or higher installed? Enjoy, John.

bombo, Hard to say what your problem might be, with so little information. Please attach (not paste) your LastSession.ini. Did you run nLite under your Vista OS? Did you use XP SP2 Compatibility mode? If not, you might try rebuilding your disk under XP. It should work in Safe Mode. You could also rebuild under XP leaving out some or all the drivers and see if it works, to narrow the problem down some. Good luck, John.

dav532000, I don't know what you are trying to do but perhaps you are trying to save a blank configuration. Why in the world do you want to do that? I did the same thing and got the same error as you did. Obviously you need to specify a configuration before you do a save. John.

dav532000, I have never used MakeISO and have no idea if it works or how to use it. You need to ask Kelsenellenelvian about it. I always have used nLite to create ISOs and Disks - no problems. Why are you trying to use some other utility? I have also not used ZoSTers and have no idea what it does. I do know you are asking for trouble nLiteing the same source more than once. It is OK to run nLite and check only Bootable ISO to make an ISO or burn a disk. I ran an experiment opening WPI with no config.js file and see the same Configuration you posted when you were trying to add your first application, CCleaner. The DLed WPI comes with no config.js, so there is no path shown. If you go ahead and save the configuration, it will create the file and the path will show the next time you open configuration. Enjoy, John.

dav532000, I only meant to kill your Internet connection if you turn off your security SW. I do this to prevent bad guys from getting to my unprotected computer. I see several LastSession files in your XPcd-2 folder. This tells me you have nLited the same source more than once. This almost always leads to numerous and strange errors. I keep a HDD copy of all my CD files/folders and make a copy when I start an nLite session. It appears that most of your questions are concerning nLite. I suggest you switch over to the nLite forum and ask new questions there. You can point to this thread. I also suggest you spend some time reading the posts there and see what kind of problems/solutions others are seeing. Enjoy, John.

dav532000, Does your folder structure look like the one here? We probably need a screen shot of your WPI folder, so we can see the path information. Are you executing the WPI.hta file inside the WPI folder? If you are using a shortcut, try going into the WPI folder and double clicking the WPI.hta file. Have you deleted or renamed the config.js file in your WPIScripts folder? We also need a screen shot of the nLite error. Have you tried with your security SW turned off? I always disconnect my modem to kill the Internet. There was another topic here about USSF being a virus. The response was that it is not. Please search this forum for that post. Enjoy, John.

malcolmx, Other posters here have stated explicitly that on a running computer you need to have SP1 before you can install SP3. If you are using nLite, you integrate only SP3. Please search the forum if you seek more information. Enjoy, John.

dav532000, Please give us a screen shot! Thanks, John.

Veena_Rajamani, We need much more information. Exactly what OS are you trying to nLite (retail, OEM, recovery, 32/64 bit) and what OS are you using to run nLite? Who is giving the error message and when? Enjoy, John.

mah.riah, The only thing that immediately comes to mind is security SW. You might try turning it all off and trying again. When I need to do this, I disconnect my modem to break my Internet connection. To get a better idea we need more information. What OS are you running under? What OS are you trying to nLite? What kind of CD do you have - retail, OEM, recovery, etc? A screen shot would also be useful. Enjoy, John.

Thanks you two for your response, but I don't understand. I tried the and it does not change what is filled in when I click on the folder icon in the Tools tab Execute After. I have a work around now, if I don't save a new Option which wipes out the double quotes I use.Thanks, John.

I tried to use Options-Tools-Execute After and when I clicked the folder icon on the right and selected CleanUp.exe, then Open, the field was filled with the fully qualified name, not %wpipath%. It also did not have double quotes around it. I went to the useroptions.js file, changed to %wpipath% and placed the double quotes around it and it worked. If I go back into Options, there are no double quotes around the name. If I do a save, the the quotes are removed from the entry in the useroptions.js. I can also place the double quotes around it in Options. They are stored in useroptions.js, but are not there the next time I open Options. Please let me know if this is working correctly and if so, how I should code it to get it to work without editing useroptions.js. Thanks, John.

pthoma, You only need SP3. In general you should never nLite the same source more than once. Good luck, John.

I don't know what the problems are for either of you. But, there are multiple topics about using Recovery disks as input to nLite and there are also several topics about nLiteing ISOs for the EEE. I suggest you take a look at these if you are still having problems. Enjoy, John.

dav532000, I hope you don't mean: It is the $OEM$ folder. I need a screen shot of the WPI screen with the bottom missing from the Configuration function. I also don't know what you mean by my app does not show up. The installer for CCleaner should be placed in the Install folder in the WPI folder. When you open the Configuration function, you should click on the folder icon on the right of the command line and use it to point to your application in the Install folder. Do you see a scroll button on the right of the Configuration window? Anyway, the main thing is please include some screen shots. Are you running WPI version 7.1.1? Thanks, John.

jaclaz, They re-appear, see my post above. I am looking at scffiles.dll in a resource editor right now and have not made sense of it yet. My reason for opening this topic was to try to determine if I had done all the things I needed to do to restore SFC(WFP) to full function. Enjoy, John.

dav532000, I do not understand your second question - perhaps Kels will respond. As to the first: It sounds like you added the WPI and $OEM$ after you ran nLite and created an ISO. Apparently you tried to get nLite to make an ISO out of an ISO. You should add the WPI and $OEM$ into the folder before you create an ISO. In other words take your CD source files (fresh copy), add the two files for WPI then run nLite to make your changes and create the ISO. Enjoy, John.

All responders, thanks for your responses. I just looked at the hashes for the sfcfiles.dll in my nLite processed files (SCF Disabled) and the copy in my System32 folder on my host. They are both the same, so changing this file is not the method nLite uses as I said before. If you will look at my previous posts you will see that the sfc_os.dll file is altered. Enjoy, John.

hkclbb, Have you tried nLiteing the source without IE7? Does that work? Is your nLite a Chinese version? Perhaps there is a problem there. Good luck, John.

mgdejong, There is not enough information. Please attach (not paste) your LastSession.ini, your source CD info, nLiteing system OS, etc. Have you included drivers and if so are you sure they are the correct ones? Have you nLited the same source more than once? Google gets lot of hits on Stop 21a - have you looked at these? Enjoy, John.

robotnik, You don't provide much information about what you are trying to with what. Have you looked at the Unattended section? I use 'Fully Unattended' and specify my accounts and passwords here. There is no stopping during install. Let us know more about what you are doing and what kind of source CD you are nLiting if you are still having problems. Enjoy, John.

LeCoop, This option has been discussed in this forum. As I remember the problem is that during install, the machine will keep booting from the CD unless you yank the CD or go into the BIOS on the first reboot and change the boot order. Have you nLited your source more than once? You should always start with a fresh copy of the original CD's files/folders. Enjoy, John.

jaclaz, thanks for your reply. I will spend some time looking at the links. EDIT: I have looked at your links and I don't believe that nLite is using the 'empty dll trick'. I think you will see why I believe this below. TranceEnergy, thanks. By Googling, I was able to find how to disable SFC for XP (hex edit sfc_os.dll, change key). I then assumed that nLite probably did it the same way. I compared hashes between sfc_os.dll in an nLited ISO (SFC disabled) with the ones in my host machine (XP x64, SP2). The 64 bit one was different (exact same length), but I was surprised to see that the 32 bit one (SysWoW64) was the same. The keys for both (see my first post) were both altered. After restoring the 64 bit sfc_os.dll and both keys, both 32 and 64 bit functions seem to work. If I rename or replace a dll (shell32 for instances), in a few seconds a new one appears having the hash of the original. The 32 bit will yield a dialog if the needed dll is not available (insert CD). If this is canceled, then the 32 bit dll can be changed. Thanks for the comments. Enjoy, John.