Yzöwl

Please bear in mind, whilst you're making these lists, that the vast majority of the components you are asking to be 'Off' are already Off by Default, and are simply wasting space. You should only be using this section of your file to change the Windows default settings. i.e. if its off by default, and you want it on by default, set it to =On if its on by default, and you want it off by default, set it to =Off For a list of 'Official Components' read the Ref.chm, this will tell you the default states, so that you can either remove them or comment out the appropriate entries

In a reg file, if you were wanting to use the REG_EXPAND_SZ method, your reg would start to look something like this: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup] "Installation Sources"=hex(7):43,00,3a,00,5c,00,49,00,33,00,38,00,36,00,00,00,\ 00,00;REG_MULTI_SZ (C:\I386) "SourcePath"=hex(2):25,53,79,73,74,65,6d,44,72,69,76,65,25,00;REG_EXPAND_SZ (%SystemDrive%) "ServicePackSourcePath"=hex(2):25,53,79,73,74,65,6d,44,72,69,76,65,25,00;REG_EXPAND_SZ (%SystemDrive%) i.e you would need your variables in hex format....

If using a runonceex.cmd, mine would probably look something like this: REG ADD %KEY%\075 /VE /D "Applying Security Template" /f REG ADD %KEY%\075 /V 1 /D "%SystemRoot%\system32\cmd /c copy \"\"%SystemRoot%\security\Database\secedit.sdb\"\" \"\"%SystemRoot%\security\Database\WinXPPro.sdb\"\"" /f REG ADD %KEY%\075 /V 2 /D "%SystemRoot%\system32\cmd /c copy \"\"%SystemDrive%\install\Security\WinXPPro.inf\"\" \"\"%SystemRoot%\security\templates\\"\"" /f REG ADD %KEY%\075 /V 3 /D "%SystemRoot%\system32\secedit /configure /db \"\"%SystemRoot%\security\Database\WinXPPro.sdb\"\" /cfg \"\"%SystemRoot%\security\templates\WinXPPro.inf\"\" /overwrite /log \"\"%SystemRoot%\Temp\securcfg.log\"\" /quiet" /f As you can see, it's very messy, it's only supposed to be on four lines, and very easy to get wrong due to all the quotation marks. My method would be to copy the existing secedit.sdb file to a new WinXPPro.sdb, then copy my own WinXPPro.inf, then run the SECEDIT over the two. Hope this helps you out.

You can achieve what you are after in a couple of ways: Add this to your .cmd file (as Bâshrat the Sneaky stated): REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" /v "Installation Sources" /t REG_MULTI_SZ /d "%SystemDrive%\I386" /f REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" /v SourcePath /t REG_SZ /d "%SystemDrive%" /f REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" /v ServicePackSourcePath /t REG_SZ /d "%SystemDrive%" /f REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v SourcePath /t REG_SZ /d "%SystemDrive%\I386" /f Alternatively, (contrary to what Bâshrat the Sneaky said), use an inf: [Version] Signature=$CHICAGO$ [DefaultInstall] AddReg = Reg.Settings [Reg.Settings] HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Setup,"Installation Sources",0x10000,"%24%\I386" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Setup,SourcePath,,"%24%" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Setup,ServicePackSourcePath,,"%24%" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion,SourcePath,,"%24%\I386" I suppose for the Installation Sources key, you could forget about the "%SysyemDrive%\I386" bit, and because it's a MULTI_SZ value, put something like this in instead "C:\I386,D:\I386,E:\I386,F:\I386,G:\I386,H:\I386", you would then cover your hard disk and optical drives too!

Your first page on the thread when I posted had a direct link to CODECS22.rar file when it was running at 2.3 thats all I meant. It also suggested therefore that the new msi version was therefore also at 2.2, which was obviously not the case. You appear to have changed the reference now, and all is okay.

@ msfn11 Another way would be to download the Policy Setting Reference Spreadsheet for XP SP2 . All the settings have their registry locations listed within it. Also from the link you should get links to information on Administrative Template (.adm) files.

Also check that the file you've posted is named runonceex.cmd not RunOne.exe

What method are you using to deploy the template? Without more information I think it's going to be difficult for anyonr to come up with a reason.

When a user logs on, Windows XP checks the list of user profiles in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList to determine if a local profile exists and its %USERPROFILE% path. If an entry exists, the OS loads the hive file Ntuser.dat found in %USERPROFILE% into the subkey HKEY_USERS\<security ID> and then links HKEY_CURRENT_USER to it. If on the other hand the OS does not find a matching user profile, it copies the Ntuser.dat from <ProfilesDir>\Default User into the new <ProfilesDir>\%USERNAME% and loads it into a new subkey HKEY_USERS\<security ID> and then links HKEY_CURRENT_USER to it.

If the %1 is already stored, which it must be in order for the inf to run using it, then just creating a label="""%~n1""" string and changing the first %here% in each of the two keys may do it then! I would have suggested this in my last post, but thought that the ~n expanded the filename, which of course we don't have cos we're right clicking a folder. Whereas ~p gave the path and ~d the drive letter etc. [EDIT] Tested it as above, it gives %~N1 as the LABEL [/EDIT]

This web page should give you enough to go on

Added ankap! Thanks for your work ! Just thought I should highlight that both the above should be referenced at ver 2.3 in your front page not 2.2

@Tsunami I think that's what I was trying to get around to. It would of course be a lot simpler if it was possible to expand out %1 somehow

Well in that case would it not be %CD:~3% i.e. no length just offset 3? Anyhow, would the above only be effective if you CD to the directory first, and would the right click command only work on files located 1 level below root.

@ msfn11 I think you should have created another thread for this. You could always Save your Policy Settings in a Template from the MMC and apply the template during the installation.

Since you are editing the DAT file, be careful, if you get something wrong ..... It may be wiser to suggest a copy rename in your cmd first, if you want others to go down this road. Good tip though non-the-less

no problem, just a pedantic method of making my point...consider it gone I actually hoped it would've triggered a response from the author, as it's not just people, without wordpad, but most users of firefox etc. will pick up a txt file in their browser by default, unless they remember to right click on it first.

I don't have Wordpad, the file extension is .txt for use with a text editor, not a word processor. Here it is again for those of us using a text editor, or reading directly in their browser. [EDIT] Removed [/EDIT]

It doesn't look like a txt file to me, what format is it supposed to be?

Google search criteria was "find target" context

When you've got a definitive list, how about a thread full of UA switches for them; for those of us who do not use pirated software. Here's one of my favourites Paint: Pixia

So we're playing cryptic games then! You said you made a batch, but didn't work, but wouldn't post it I took a guess, no response except for a single word. If you want to delete things which are protected by WFP, your gonna have to do something about the protection first.

Have you tried %CommonProgramFiles% [EDIT]**** got there just before me[/EDIT]

What does your batch look like, something like this: RD /S /Q "%programfiles%\ComPlus Applications" RD /S /Q "%programfiles%\microsoft frontpage" RD /S /Q "%programfiles%\movie maker" RD /S /Q "%programfiles%\msn gaming zone" RD /S /Q %programfiles%\netmeeting RD /S /Q "%programfiles%\Online Services" RD /S /Q "%programfiles%\Outlook Express" RD /S /Q %programfiles%\xerox

@ durex No you are thinking of REG_MULTI_SZ Also on an unmodified PC they are stored as REG_EXPAND_SZ as shown below. Favorites - %USERPROFILE%\Favorites My Music - %USERPROFILE%\My Documents\My Music My Pictures - %USERPROFILE%\My Documents\My Pictures Personal (My Documents) - %USERPROFILE%\My Documents Your specific example didn't need changing, but; The REG_EXPAND_SZ is used primarily because those keys usually, and in the case of my examples contain a variable (%USERNAME%). This is of course helpful in a multiuser environment so that each user has all their redirected folders placed under their own User Name or Profile, as they are by default in Windows XP (%USERPROFILE%). The expand bit basically refers to the fact that the OS will expand the variable when required to provide the true path location for the currently logged in user. Hope this better explains it!