johnhc

bensam56, I am curious how you slipped SP1? Is it possible to do it with MS tools (DISM, ImageX, etc)? Thanks, John.

Tdunk18, you can run nLite under VMware. I am not familiar with some of the terms you are using (slp, aio). I hope you are not using nLite in a work environment. The nLite license only allows personal use. It is available in the nLite folder in the Program Files folder. Please give it a read. Assuming you are OK with the license, please do post more information. The more the better. We like to see screen shots of error messages (another advantage of testing under a VM). We will take at look at oemscan, but know nothing at this time, so we should attach other problems first. Enjoy, John.

Tdunk18, thanks for the Last Session.ini and the title change. First, I see you are running nLite under W7 (or Vista) to create an ISO for XP. This can be a problem especially if you are integrating a Service Pack. Your text said you were, but your Last Session did not. In general you should always start with a fresh copy of your CD files/folders and run nLite only once doing all your work. Running nLite multiple time can cause some really wild symptoms. I am curious what the .cab files are for updates. What are the media updates? - not WMP11? I think it best to narrow your problems down and look at one to start. Please try a run (under XP if possible) with just your updates and let us know the outcome (hope you are using a virtual system for testing). BTW, I usually encourage posters to use only nLite or only some other program to process their source. When multiple programs are used, I, for one, cannot be of much help because I have no experience with them other than nLite. Enjoy, John.

Tdunk18, we need to see your Last Session.ini not the U_.ini. Please attach your Last Session.ini. Also please edit your first post and change the title to something meaningful (AddOns failing, oemscan fails...etc? - whatever you like). I will have no help for you concerning placing all the versions of XP on one DVD. Perhaps someone else will. Please give us link(s) to the oemscan information. Enjoy, John.

kevin34, I do not know what the other values do in ShellState. That is why I suggested you modify your copy of the value. Google gets lots of hits on HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ShellState, so maybe there is some info there. I played a little with the icon size on my VM (RegShot) and could make little sense of it. Most of the times I saw no changes to the Registry and some time changes to keys that made no sense. I suspect the icon size is not kept in the Registry. Enjoy, John.

kevin34, you are welcome. I should point point out a concern with the size key. Please look at the LastEnum value and you will see that there is a GUID for each of your HDDs. When I had one (on my VM) my script worked fine. When there were several (on my HW), then my script failed. I never figured out how to determine which GUID went with which HDD. I assume it can be done and may get back to it some day. Enjoy, John.

patronu, I simply copy the Favorites folder from my old machine, then during installing W7, copy it into the new Favorites folder. Enjoy, John.

bbmak, I think RT7Lite will inject drivers into boot image. Please see thread above. Enjoy, John.

kevin34, please try this key/value. Your contents may vary, so look at yours and modify as needed. I think the first is with confirmation dialog enabled. If you do not see the key/value in your Registry, then change the check box/Apply, then look again. I deal with the GUID problem by using an AutoIt script to read the following key then use it to store my value. I do not modify the NukeOnDelete, but set my maximum recycle size. This GUID process works for me, but, of course, there are no guarantees from this end. Hope this information is useful. Enjoy, John.

kevin34, I find it here using RegShot on my W7 X64 Ultimate: Enjoy, John.

dukew74, thanks for your reply. I had no media in my optical drive. As noted above, mritter has made changes for Registry access and he sent me a test version. It is much faster - looking forward to its release. Enjoy, John.

MoXa, there are two things you might try. The Create Bootable ISO Task has an alternate ISO creator called Mkisofs. You could give that a try. In the Patches tab of the Options Task you can Disable SFC (System File Checker). You could also try it. The link Ponch gave speculated that SETUPREH.HIV might be modified by Dell. Where did your CD come from? Is it a retail or OEM and did it come with hardware? Perhaps installing from the original CD accommodates the modified SETUPREH.HIV. I would also like you to try ImgBurn, or your favorite ISO burner. BTW, running nLite under W7 to create a W2003 ISO can cause problems, especially if you are integrating a Service Pack. Enjoy, John.

eltonzoto, you can integrate many programs including AVs. Above is a forum on AddOns that may offer one for the AV you like. If not, you can run the installer from the RunOnce exit out of the Unattended Task in nLite or create you own AddOn. You will need to find the appropriate switches (silent, options, norestart, etc). Enjoy, John.

MoXa, what version of nLite are you using and where did it come from? What OS are you running nLite under? If you are testing on VM (a great idea, BTW), please post a screen shot of the error message. Is SETUPREH.HIV missing or not loadable, as in Ponch's link? I am curious why you are using nLite to only create an ISO? How big is your ISO? Perhaps you should try ImgBurn - what I use. Enjoy, John.

happygardener, probably the easiest way is to use an Update Pack. Please see the RyanVM forum for update packs. There are not hundreds of updates because you will only need post SP3 updates. There is also Windows Update Downloader - see forum below - but then you need to deal with the fact that nLite cannot integrate all MS updates. I use XP x64, so am not familiar with XP updates. Enjoy, John.

happygardener, use this one. Enjoy, John.

MoXa, we need to see your Last Session.ini. Please attach it as requested in BOLD RED letters above. It is not really possible to guess what the problem is, but you always need to start with a fresh copy of your CD files/folders and run nLite only one time doing all your work. Enjoy, John.

zeezam, the same program. It has two folders, one for 32 and one for 64 bit. This link is in Russian, but you can find English sites and the program supports English (and other languages). Enjoy, John.

kingweaver88, see my second EDIT above and Help and Support. Enjoy, John.

kingweaver88, does the second command run (oobe)? Are you sure that the .exe names are identical (in command and file name)? Please find NLITE.CM_ in your source folder (after running nLite), extract it and see if your RunOnce commands are in there and intact. BTW, I see you are running Vista (or W7) to run nLite to create an ISO for XP. This an be a problem especially if you are including a Service Pack. Enjoy, John. EDIT: Just saw your last reply. Sorry I cannot answer your question about poweruser - never used it. EDIT: According to Help and Support (START): Power Users can "Install programs that do not modify operating system files or install system services. "

marcusj0015, here is what I used on XP with WMP11 and it works on W7 (have not looked at the WMP version): Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\Preferences] "AcceptedEULA"=dword:00000001 "FirstTime"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsMediaPlayer] "GroupPrivacyAcceptance"=dword:00000001Enjoy, John.

kingweaver88, that looks like it should work - no quotes needed. Where did you place the $OEM$ folder? It should be in the root of the folder with the I386 folder, not in the I386 folder. Please attach (not paste) your Last Session.ini file. Enjoy, John.

zeezam, I used RegShot on my W7 x64 Ultimate to see if it would find the secret. The following key is involved: The first value for PnPCapabilities (0x118) unchecks "Allow the computer to turn off this device to save power" and the second value checks the box. You will need to run RegShot (or something similar) on your machine to identify the key since the name contains a GUID, which is probably different for your machine/NIC. I do not know if this value changes from install to install and you may need to search the Registry for the GUID to see where it is assigned to your NIC card. Good luck, John.

SEB100, you are running a really old copy of nLite. Please get up to the latest, 1.4.9.1. It also looks like you slipped SP2. You should slip SP3 - that is all you need no matter what your source contains. Enjoy, John.

Cheetah, you are welcome. Glad you are running and hope no problems arise. Enjoy, John.