Kelsenellenelvian

They are skipping a vital point. It includes a PE environment This is a "Live" version of windows and is technically a licensed ms product. As such they are distributing MS windows which is a huge no-no As for using ubcd and ubcd4win this is a OK process as you provide the windows software. I am sure (Giving the assurance you will drop the warez usage) someone will be able to help you. You also need to note that nLite is not for business or corporate uses....

Yeah don't use warez and illegal software. We cannot help you as the #1 rule of the forum here is against warez

"Corp xp" is a terminology almost always used by pirates and referring to warez. Based on your terminology and the laughing off of statements of others I made the assuption that you were just trying to lie to cover your a**. Please also remember that when you say you work for your dad that nLite is NOT for business or corp useage. It says so in the license that you agreed to when you (Or your friend) installed nLite.

Yeah sure... You mean to tell me your dad has a vlk and you have NO ACCESS to a clean source??

/q

Yes you are NUTS Afetr rereading your last post I have a question: IS the sp1 source unmodified? If so you are good to go then. just slip in sp3 and go from there.

#1 vmware tools normaly doesn't autoinstall. #2 I will do some testing tonight and see if i can replicate your issue. (I never run wpi from the source disk I keep mine on a usb key)

SURE ITS SUPER EASY [ sarcasm] Heres how to do it in 100 easy steps: Get a fresh source of the exact same as your original source (Remember there are several different versions of each type of XP) copy the files missing open the relevant source files and add the all to them for xp to rerecognize them. (Dosnet, txtsetup, sysoc so-on) open up and copy ALL of the relelvant reg files that acompany them (hivesft and so-on) find and remove all relevant nlite entries test redo all steps if you missed something. Honestly if it was super easy don't you think a guide would be out there? But then to think about it wouldn't you have a copy of the fresh source after being done anyways?

Things are pretty rough but I am managing.

Nope I use vmware when testing

got it

You are putting the sources folder too deep by dropping it into the $oem$ folder... It has already been made with several folders in it. You simple choose extract here and drop the created folder to the root of the disk.

Next version...

Your ORIGINAL disk INCLUDED A KEY?!?! Anyways grab your original disk and make a new upto date one with this pack here http://www.ryanvm.net/forum/viewtopic.php?t=6438

There are many ways just as there are MANY different types of app installers! It depends on the program m8.

Since my quote he has found more packages to remove via dism and will be adding a bit more removals to the toolkit.

LOL dumbax...

Works for me here I made it into a regfile

OK! Copy the following into notepad: Save it as "Whatever.reg" (Without the quotes) Then run it... by double clicking on it. You have to make the file.

Slightly of topic BUT: Remake your sp1 disk! I am reposting a link to full sp1 disks here: (The mods have not disallowed this link and it is straight from MS so I guess its legit) 1 = "Not well" as cluberti said 2 = Not without modifications and ALOT of extra work 3 = For making an a-i-o do the following: Materials required: Windows 7 x32 install media Windows 7 x64 install media Hex editor with search-and-replace, and support for unicode strings. WAIK 2.0 Optional materials: Windows 7 Enterprise x32 & x64 install media (only required if you wish to have these editions available) Stage 1: arranging files Okay, in this guide we shall be working on the D: drive, but any drive letter you have available shall do. In this stage we set up a directory structure to be used for the rest of the stages. Firstly, create the folders: D:\AIO\DVD and D:\AIO\WIMs Next, extract contents of the x86 DVD into D:\AIO\DVD Delete all .clg files from D:\AIO\DVD\sources delete ei.cfg from D:\AIO\DVD\sources Then move install.wim from D:\AIO\DVD\sources to D:\AIO\WIMs, and rename it ULTx86.wim Then extract install. wim from the x64 DVD to WIMs, and rename it ULTx64.wim And optionally, extract the install.wim from the x86 and x64 Enterprise DVDs, renaming them ENTx86.wim and ENTx64.wim respectively. Finally, extract the content of the sources directory (except install.wim and ei.cfg) from the x64 DVD to D:\AIO\DVD\sourc64, and copy the setup.exe from the x64 DVD to D:\AIO\DVD as setup64.exe Stage 2: Building the WIM Now we must build the install.wim (that's the file that contains the different versions of windows, if you didn't know), by exporting images from the .WIMS we have. Assuming you've done exactly as I've said, open the deployment tools command prompt (from WAIK), and enter these commands: You can skip the Enterprise ones if you chose not to include Enterprise. Well, you could skip any of them, but I reccommend including all you can, as it does not take up much additional room (I assume WIM automatically reuses files), and you never know when you might need to do a clean install for someone! Sage 3: Modifying the BCD Here we modify the DVD's BCD, so as to add an x64 recovery option. The recovery option is just that: it cannot install. To improve user transparency, the boot timeout shall be set to 3 sec, so as to be almost unnoticeable if not needed. Ok, open an administative command prompt. Navigate to D:\AIO\DVD Now make a copy of the default loader by executing: This command shall tell you the GUID of the copy made, make a note of it. Next set the new loader to load the 64 bit PE by executing: Replace {GUID} with the GUID you noted down) Finally, alter the boot timeout by executing: Stage 4: getting upgrade to work Now, the one problem left is upgrade installs on 64 bit. This involves hex editing files, and so breaks the digital signature, causing the ugly yellow UAC prompt. This is, I am almost ashamed to say, the first of two such cosmetic glitches. Now first open D:\AIO\DVD\setup64.exe in your hex editor. Search and replace all instances of the unicode string "sources\" with "sourc64\". Although this breaks the signature, it does not break the program, because both strings are the same length. Now, open D:\AIO\DVD\sourc64\autorun.dll, and replace all instances of the unicode string "sources\setup.exe" with "sourc64\lunch.cmd" (in case you were wondering, it was going to be launch.cmd, but I had to drop one letter...) Now, create a file in D:\AIO\DVD\sourc64 called lunch.cmd containing exactly this: NOTE: If you are using a SP1 slipstreamed image, lunch.cmd should instead contain exactly this: This is the cause of the second cosmetic glitch. A command prompt is briefly visible before setup is launched. Now, the autorun.inf must be modified so that it runs setup64 on x64 systems. Modify it so it contains: Now, finally, we're ready to master a DVD. Open up the deployment tools command prompt, and enter: Win7Toolkit over at wincert forums will do ALL of the above for you!

Updated...

OOOPS DESELECT the second option!

http://lmgtfy.com/?q=dism

If you relocated it and rebooted then you will not see it in there anymore.

Remove the packages via dism.