Kelsenellenelvian

I would think by now you would know that... Reshack & shell32.dll and the other file should be shell32.dll.mui Read this: http://www.askvg.com/list-of-windows-7-system-files-to-be-hacked-using-resource-hacker/

You do know hirens is illegal and considered warez on this forum don't you? To speak of such is HIGHLY against the rules and likely to get you banned...

Honestly? Stick with Ultimate or Home Premium... You will find that vLite for the MOST part only screws up windows 7 wim files. Go to the vLite section and there is a couple of LOOOOONG threads dedicated to slimming WIN7! Unless you somehow (Miraculously) have a enterprise MAK setup (Super highly improbable for a 11 year old) then you'll HAVE to stick with something affordable. Which also begs the question: How did you get a copy of Enterprise7?

The ONLY drawback you will have going from gold --> SP3 is you will not be able to skip the serial entry section. I would suggest going Gold --> SP2 --> SP3 then during installation you can skip the serial section and get a 30day "trial" installation. NOTE! This only works on rtm versions of XP.

Which app? There are HUNDREDS (OK thousands) of apps out there and my crystal ball is broken... There are several different types of installers and we need to know which one it is.

How are you calling WPI? Or WHEN? TONS of people use it daily from cmdlines.txt (T-13\T-12)

hfslip (Found on this forum) Siginets integrator (OR the ryanVM official integrator...) http://siginetsoftware.com/forum/index.php The first one will slipstream hotfixes or addons and upddate packs The second one will do hotfix packs and addons NOT hotfixes None can really remove features.

nLite is basically the same way... Think about it for a second. When you use hfslip or nLite the original files and entries are FULLY replaced with newer ones... The old files\entries DO NOT exist at all to windows. Therefore windows would have nothing to fall back on when you call the uninstaller.

HOLY COW!!! It should NEVER take that long. More than 1-2 minutes and somethings wrong.

DAMNIT!!! That is a clerical error. I will fixit when I get home...

HAHHAHHAHAH OMG! Thats friggin CLASSIC! Thanks for the laugh.

Jaclaz's google-fu is astounding! I thought my google-fu was good!

Please note: THOSE ARZE NOT FOR vLite! Right now there are NO update packs\addons for vLite.

Just because you are a non-profit organization doesn't mean you get to use nLite to deploy Windows to multiple pc's... Edit: After some thought I felt like there is more to say here. Does being a non-profit does that also allow you to ignore other Eula's like MS's Windows Eula? While nLite-ing is super and great for personal use deploying nlited installations is highly against MS's Windows Eula. nLite modifies MANY MANY core windows files and rather fully violates MS's Eula. While MS overlooks this for personal use (and some MS techs actually suggest it for slipstreaming Sp's) distributing nlited copies of Windows is VERY HIGHLY WRONG and defiantly un-ethical. The arrogance you show here by saying, rather simply "we are not business or corporation. We are a non-profit organisation." is very astounding. OK being a non-profit is very nice and really should afford you SOME special consideration but fully ignoring software agreements is very un-ethical. Most of what nLite does can be found and done other ways (most of them being on this forum) these other ways are mostly agree-able to being used in multiple-deployment environments. The use of nLite in a corporation (Or non-profit organization) is a sign of laziness IMO. You cannot in anyway fully support deployed installations that have been nlited. (Unless you know EXACTLY what nLite does, and if you actually do then why aren't you doing it yourself?) Lets see nLite's license: [b]LICENSE AGREEMENT: Your use of nLite is governed by the following conditions. Please read this information carefully before using nLite. By using it you are agreeing to the following conditions: 1. nLite is freeware and can be freely used for any personal non-commercial purposes, subject to the following restrictions. 2. nLite can only be distributed electronically through the official host www.nliteos.com. 3. nLite is supplied "as-is". The author assumes no liability for damages, direct or consequential, which may result from the use of nLite. 4. Import Restrictions. International users also check any import restrictions that your government may impose. Reread eula.txt in your Windows\System32 folder. 5. nLite is free for personal use only, you cannot use it for any company or business purposes at this time. 6. MCDBNET2.dll is registered on me (the nLite author) with the royalty-free license and can be distributed only bundled with nLite. 7. nLite is a copyrighted material of Dino Nuhagic aka nuhi. You may not decompile, disassemble or otherwise reverse engineer this product. You may not include the parts of nLite in your software without the author's permission. You may not alter or modify nLite in any way or create a new installer for it.[/b] Here it says read the EULA.txt in your windows folder. Which would then remind you that: YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE. IF YOU DO NOT AGREE, DO NOT INSTALL, COPY, OR USE THE SOFTWARE; YOU MAY RETURN IT TO YOUR PLACE OF PURCHASE FOR A FULL REFUND, IF APPLICABLE. Then leads to: 4. LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION, AND DISASSEMBLY. You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation. Back to the license: This section then reads that nLite is ONLY FOR PERSONAL USE...

This might be slightly wrong, BUT I am pretty sure from the tone of your post this needs to be reminded: nLite is NOT for business or corporation usage... It's in the nLite license, which you agreed to when you installed nLite.

Redownload WPI v7.8.0 WPI.exe was added as a later feature...

Options ===> Execute before....

I like the old sledge hammer method!!! BAM BAM BAM No more data!!! Mwahahahahaahahha

Yes it is actually that easy... This is slightly wrong. You need 2 files in $oem$ cmdlines.txt and RunWPI.exe or cmdlines.txt and RunWPI.inf The .exe one runs right BEFORE login and the .inf one runs right AFTER login (Then desktop is loaded then)

Can I ask a question? WHY WOULD WE HELP YOU WITH ILLEGAL COPIES OF WINDOWS????

I will ask mritter. AFAIK utf-8 support is already implemented. The ONLY issue I see with that is just HOW MUCH of config.js are you translating? If you are translating any of the defualt, internal stuff then you will surely have issues.

Why???

Someone slightly more knowledgable than me will have to answer what switches you need to add the hotfixes into a SFX package. (But yes they can ALL be added into a package to run silently) I am not sure why the inclusion of the hotfixes into the updates folder kills the unattended process.

@ hag672: Please have your aid carefully read the first post of the onepiece package... It has 2 different ways of disabling the items you do not want to include. My preferred way? [Components] WinRM = off PowerShell = off PowerShellISE = off MicrosoftUpdate = off Silverlight = off DirectX = off MDX = off MSXML4 = off WDSearch = off IMAPI2 = off ICCDSCD = off WgaNotify = off WRMC = off BitLockerToGo = off ALL of these (Or any) can go into the components section of your winnt.sif answer file to disable the undesired applications.

I think you may have found a flaw in MS's practices...