MrJinje

Yes, it "should" work in a VM. Did you get a chance to find/correct any errors with WSIM ? Here is snap of WSIM, I'd look under Components > 1 windowsPE in the "Answer File" section. At least that's what I guess according to the error in your 1st post. Once you get used to the GUI, it is much easier to add/edit settings this way.

Here is how to find the typos in your XML. Step 1: Install WAIK for Windows 7 Step 2: Open WSIM - Windows System Image Manager Step 3: In lower left quadrant, select your (catalog) .clg file from inside the sources folder. Step 4: Import your XML file using the middle section. Step 5: In the lower right section, double click the (RED) error(s) and it will jump you to the correct section Step 6: Once at source of the error, fix them using the upper right corner section. Each setting is controlled from there. A) If there are multiple errors, repeat Steps 5 and 6. That is the easiest way I know how. If Step 4 causes an error, it will tell you which line number is the problem, open the XML in a numbered line capable text editor (search start menu for Powershell IDE if you don't have a better program) and fix any errors there. Good luck, it is much easier than it sounds.

nLite doesn't do that by itself AFAIK, attach your session.ini so we can be sure. Otherwise, if you don't want to waste time to have to re-nLite your disk, very easy to delete the account with one of your $OEM$ scripts. Just add this snippet. NET USER owner /DELETE

Thanks for the update list. Your English is better then most people's Chinese so no worries there. I tested in vLited Windows 7 x64 with all Asian languages removed. Apparently it defaults to a blank character.

Please post your replies in the original thread. Thank you. Can someone merge this and delete my post, here is the link mods.

OP is not crazy. After changing to a different ICON still get shell32.dll as the default. Can someone else confirm on a non-vLited install and a x86 version. Mine is heavily thinned x64 If anybody wants to do some trial and error, have a look at these registry settings. HKEY_CLASSES_ROOT\Directory\DefaultIcon HKEY_CLASSES_ROOT\Folder\DefaultIcon HKEY_CLASSES_ROOT\Folder\ShellNew\IconPath They are all set to %SystemRoot%\System32\shell32.dll,3 Have fun, I'm out, this sounds like more work than reward.

or could try wmlite. http://ksphere.free.fr/site/codecspackage.php

Driver Injection and Patch Integration can be done very easy, but every method you will find is limited in that you need to mount each image and update them one at a time. Lucky for you I already wrote a partial script that does this. AIO-DISM-Updater This is an update to include drivers, edit it to suit your needs. Place your Updates (MSU or CAB) into the x86 or x64 folder and place all your drivers into the x86-Drivers or x64-Drivers folder. Then just need put your install.wim in the same folder with this CMD and double click it. W7_Updater.cmd - both x86 + x64 scripts are included in the attachment. MD %~dp0MOUNT Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:1 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /image:%~dp0MOUNT /Add-Driver /Driver:"%~dp0x86-Drivers" /Recurse Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:2 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /image:%~dp0MOUNT /Add-Driver /Driver:"%~dp0x86-Drivers" /Recurse Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:3 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /image:%~dp0MOUNT /Add-Driver /Driver:"%~dp0x86-Drivers" /Recurse Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:4 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /image:%~dp0MOUNT /Add-Driver /Driver:"%~dp0x86-Drivers" /Recurse Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:5 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /image:%~dp0MOUNT /Add-Driver /Driver:"%~dp0x86-Drivers" /Recurse Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit EDIT: Don't worry about it integrating drivers or updates twice. It is safe to run multiple times as Windows 7 first checks if the update or driver has already been integrated. W7_Updater.7z

Easy way is to install them into a live OS, then use something like Driver Magician Lite to export them. Here is the link for the portable version. http://www.drivermagician.com/PortableDML.zip

Karate + nice-guy, we are talking about customizing not only the Windows 7 logon screens, but also editing the Windows PE portion during the DVD installation so that we don't see any Microsoft's images while installing. That is the key difference, the OEM registry method does not accomplish the full goal. (it only does applies after installation is completed). Since Vista/7 are based on boot.wim installations this is the method of creating custom boot.wim's for your DVD's. The OEM method does not alter the boot.wim and there-fore does not offer the same level of customization. (but it does work perfectly fine once the OS is fully installed). If anyone is satisfied with the blue image during the installation, then use the registry tweak, otherwise, if you need to trick out your boot.wim, this is the correct method.

The first line creates the non-propagated "create and append" setting, the second line creates the "Modify" control over the subfolders and files only. Not sure if you need to fully delete your existing permissions. Report back if it does not work. Jaclaz, you are not the internet police, I am, now respect my authoritah', let's stop acting like we are MVP's and actually try to answer a question once in a while. {RANT}If people wanted replies like that they could go to the social.answers.microsoft forums and let a Microsoft MVP tell them how stupid they are. I don't speak Italian, but Franco Leuzzi seems to have passed the buck like some of the lazy MVP are known to do. All he seems to say is that Microsoft does not approve of making this change, blah blah blah. Then to top it off, he gives the guy the ICACLS syntax page knowing full well that most programmers cannot comprehend how to control inheritance via command line, let alone a n00b. I'd wager Franco doesn't understand the concept himself and that is why he chose to avoid answering the question, all to maintain his air of superiority. Seriously the effort you make in showing everyone how many posts he made, was more than I exerted in helping him. Not that I approve of his crazy postings, but maybe answering his question will shut him up. (but I won't be fooled twice!!) Besides are we such a-holes at MSFN that we require people to understand complex syntax and relish the nuances of every scripting method. Or instead of claiming we are better than everybody, why don't we show our intelligence and just answer his damned questions. {/RANT} The next reader trying to deal with propagating inherited security / ACL permissions will find this thread and have a working sample to play with. Here are some quick links to resources for that future reader. http://ss64.com/nt/icacls.html http://support.microsoft.com/kb/243330 http://technet.microsoft.com/en-us/library...28WS.10%29.aspx

You need to take ownership of the file. Below is a common reg script for creating a right click entry so you can "right click" the file and take ownership of it very easily. Otherwise you need to look up the command line syntax and do the same thing manually. Take_Ownership_Multi_Lingual.reg Above is my multi-lingual version. Here is an english only version from the HowToGeek.com.

or maybe we hide it a different way. I don't see why he couldn't create a SFX file with the correct folder structure and make it extract to the root of the drive. Convert that SFX into a hotfix, integrate it with nlite, and it will extract during setup, but will not be visible to any casual observers. Maybe even throw in a clean up script to delete the extracted files afterwords. Would that work.

That usually entailed adding a $ to the end of a shared folder, similar to the administrative shares (C$,D$, etc) so that they do not appear when network browsing. (and it only applied to network browsing) I don't think that can help the OP, because the $OEM$ folder is accessed locally whenever the CD is in the drive. (bypassing the setting)

Read Closer. All the links are there.

不要告诉我你不知道如何使用谷歌翻译。 Don't tell me you can't understand how to use google translator. 始终提供英文翻译。 Always provide an english translation.

Can't hide it. Why would you want to, what are you trying to hide in your install that you don't want other people to know about ? I guess you could try setting the "hidden" folder property before creating your ISO. But anyone who can find the "show hidden files and folders" setting will be able to see it. Not very useful IMO.

Give it a week or two and they will be working again, already been discussed here. http://www.msfn.org/board/index.php?showtopic=141487

Sounds like a temporary thing, probably happens so often I just never caught it before.

Yes. It was down temporarily. But it is back online now. On a side note, they must've changed the URL processing, my old links do not work anymore. It still occurs after I deleted my cookie, is this a permanent change ? What about all the old-style links in everyones post's. Do they all re-direct to the home page now ? This was working yesterday, now redirects to main page. http://www.msfn.org/board/mr-jinje-dism-tool-t138804.html Today the new link is this. http://www.msfn.org/board/index.php?showtopic=138804

Or just forget everything in this thread, and use the easy 7 step sticky to turn your EXE into a proper hotfix that XP will recognize. http://www.msfn.org/board/index.php?showtopic=63596

Fine, the simplest way is to just use CMDLINES.TXT http://www.unattended.msfn.org/unattended.xp/view/web/14/ Place this file and the EXE in your $OEM$ folder. CMDLINES.TXT [COMMANDS] ".\O2K3_SP3.exe"

Try using the <CopyProfile>true</CopyProfile> setting during the specialize pass in your autounattend.xml.

OK Thread Locked.

Don't worry, very easy to disable notepad.exe, cmd.exe with a group policy. Follow the method described in the link. http://www.technipages.com/prevent-users-f...n-programs.html But instead of only following the prevent method, use a combination of both the prevent method, and the Run only Specified Windows applications, to lock down any random applications we haven't thought of. Read the documentation closely for the limitations of doing so, it is not as cut and dry as it sounds. Also note that Task Manager has it's own disable setting.