nonno fabio

entries.ini commands supported by DXIntegrator [sysPrepOC] Component_Name=advpack.dll,LaunchINFSection,INF_FileName,SectionName ;or Component_Name=setupapi.dll,InstallHinfSection,INF_FileName,SectionName ;;;example [SysPrepOC] Unlocker=advpack.dll,LaunchINFSection,Unlocker.inf,Unlocker Silverlight=setupapi.dll,InstallHinfSection,MSSlight.inf,Silverlight [General] ;;;example [General] BuildDate=2010-10-27T11:05:11Z Description="Freeware tool which overcomes a Windows bug" Language=English Title=Unlocker Version=1.9.0 WebSite=http://ccollomb.free.fr/unlocker/ processorArchitecture=x86 ; --> Warning: this key is used to force addon integration only in a certain system architecture; if present OS architecture is not the one defined in this key, DXIntegrator skips the AddOn ForceLang=Italiano ; --> Warning: this key is used to force addon integration only in a certain system language; if present OS language is not the one defined in this key, DXIntegrator skips the AddOn ReleaseType=True AddOn Customizedby=OnePiece Copyright=CEDRICK 'NITCH' COLLOMB Company=CEDRICK 'NITCH' COLLOMB InstallPackageName=Unlocker.inf LastUpdateTime=2010-10-27T11:05:11Z about Dirids: http://msdn.microsoft.com/en-us/library/ff553598%28v=VS.85%29.aspx about Security Descriptor Definition Language to be used in [securityRegistry*Integration] and in [securityFiles*Integration]: http://msdn.microsoft.com/en-us/library/aa379567%28v=VS.85%29.aspx http://msdn.microsoft.com/en-us/magazine/cc982153.aspx http://blogs.technet.com/b/askds/archive/2008/04/18/the-security-descriptor-definition-language-of-love-part-1.aspx http://technet.microsoft.com/en-us/library/cc512610.aspx [securityRegistryBeforeIntegration] ;;;example [SecurityRegistryBeforeIntegration] "MACHINE\%KEY_SOFTWARE%\ProgramName",0,"D:P(A;CIOI;GR;;;BU)(A;CIOI;GA;;;BA)(A;CIOI;GA;;;SY)(A;CIOI;GA;;;CO)" [securityRegistryAfterIntegration] ;;;example [SecurityRegistryAfterIntegration] "MACHINE\%KEY_SOFTWARE%\ProgramName",,"D:P(A;CIOI;GR;;;BU)(A;CIOI;GR;;;BA)(A;CIOI;GA;;;SY)(A;CIOI;GA;;;CO)" DXIntegrator loads this HIVES as default, so like previous example if want to add reglines in HKLM\Software, you need to use MACHINE\%KEY_SOFTWARE%, if you want to add or delete reglines in HKLM\System instead, you need MACHINE\%KEY_SYSTEM% "%MountDir%\Windows\System32\config\SOFTWARE" = %KEY_SOFTWARE% "%MountDir%\Windows\System32\config\SYSTEM" = %KEY_SYSTEM% "%MountDir%\Windows\System32\config\SECURITY" = %KEY_SECURITY% "%MountDir%\Windows\System32\config\SAM" = %KEY_SAM% "%MountDir%\Windows\System32\config\COMPONENTS" = %KEY_COMPONENTS% "%MountDir%\Windows\System32\config\DEFAULT" = %KEY_DEFAULT% "%MountDir%\Users\default\ntuser.dat" = %KEY_NTUSER% "%MountDir%\Windows\system32\smi\store\Machine\schema.dat" = %KEY_SCHEMA% "%MountDir%\WINDOWS\system32\config\systemprofile\NTUSER.DAT" = %KEY_NTUSER_SP% "%MountDir%\WINDOWS\system32\config\systemprofile\AppData\Local\Microsoft\Windows\UsrClass.dat" = %KEY_USRCLASS_SP% "%MountDir%\Windows\ServiceProfiles\LocalService\NTUSER.DAT" = %KEY_NTUSER_LS% "%MountDir%\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\Windows\UsrClass.dat" = %KEY_USRCLASS_LS% "%MountDir%\Windows\ServiceProfiles\NetworkService\NTUSER.DAT" = %KEY_NTUSER_NS% "%MountDir%\Windows\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\UsrClass.dat" = %KEY_USRCLASS_NS% "%MountDir%\Users\Administrator\NTUSER.DAT" = %KEY_NTUSER_ADMIN% "%MountDir%\Users\Administrator\AppData\Local\Microsoft\Windows\UsrClass.dat" = %KEY_USRCLASS_ADMIN% [securityFilesBeforeIntegration] ;;;example [SecurityFilesBeforeIntegration] %11%\FileName.exe,0,"D:P(A;;GA;;;BA)(A;;GR;;;SY)(A;;GR;;;BU)" %PROGRAMDATA%,0,"D:PAI(A;;0x1200a9;;;SY)(A;OICIIO;GXGR;;;SY)(A;;FA;;;BA)(A;OICIIO;GA;;;BA)(A;;0x1200a9;;;BU)(A;OICIIO;GXGR;;;BU)" %10%\regedit.exe,0,"D:P(A;CI;GR;;;LS)(A;CI;GR;;;BU)(A;CI;GR;;;PU)(A;CI;GA;;;BA)(A;CI;GA;;;SY)(A;CI;GA;;;CO)" [securityFilesAfterIntegration] ;;;example [SecurityFilesAfterIntegration] %11%\FileName.exe,0,"D:P(A;;GR;;;BA)(A;;GR;;;SY)(A;;GR;;;BU)" %ALLUSERSPROFILE%,0,"D:P(A;CI;GR;;;BU)(A;CI;GA;;;BA)(A;CI;GA;;;SY)(A;CI;GA;;;CO)" %16422%,0,"D:P(A;CI;GR;;;BU)(A;CI;GA;;;BA)(A;CI;GA;;;SY)(A;CI;GA;;;CO)" [TweaksAddReg] ;;;example [TweaksAddReg] HKLM, "%KEY_SOFTWARE%\ProgramName", "Test", %REG_SZ%, "Test....." HKLM, "Test\Test2", "Test2", %REG_SZ%, "Test2....." [color=green];;;see example in [ProcessesToRun*Integration] where RegHive has been loaded in HKLM\Test[/color] [TweaksDelReg] ;;;example [TweaksDelReg] HKLM, "%KEY_SOFTWARE%\ProgramName" SourceFiles = Directory where the addon has been extracted MountDir = Directory where the image has been mounted Warning: %MountDir% is an optional variable, there's no need for it as MountDir is always DIRID 24 (Root directory of the system disk), so %24%\ is always mount directory destination [ProcessesToRunBeforeIntegration] ;;;example [ProcessesToRunBeforeIntegration] reg load HKLM\Test "%Mountdir%\Windows\System32\config\RegHive" "%SourceFiles%\ResHacker.exe" -delete "%16422%\Internet Explorer\iexplore.exe", "%16422%\Internet Explorer\iexplore.exe", Icon,, "%SourceFiles%\ResHacker.exe" -addoverwrite "%16422%\Internet Explorer\iexplore.exe", "%16422%\Internet Explorer\iexplore.exe", "%SourceFiles%\Icon.res",,, "%SourceFiles%\ResHacker.exe" -delete "%MountDir%\Program Files\Internet Explorer\iexplore.exe", "%MountDir%\Program Files\Internet Explorer\iexplore.exe", Bitmap,, "%SourceFiles%\ResHacker.exe" -addoverwrite "%MountDir%\Program Files\Internet Explorer\iexplore.exe", "%MountDir%\Program Files\Internet Explorer\iexplore.exe", "%SourceFiles%\Bitmap.res",,, [ProcessesToRunAfterIntegration] ;;;example [ProcessesToRunAfterIntegration] reg unload HKLM\Test "%SourceFiles%\ResHacker.exe" -delete "%MountDir%\windows\system32\FileName.exe", "%MountDir%\windows\system32\FileName.exe", Bitmap,, "%SourceFiles%\ResHacker.exe" -addoverwrite "%MountDir%\windows\system32\FileName.exe", "%MountDir%\windows\system32\FileName.exe", "%SourceFiles%\Bitmap.res",,, "%SourceFiles%\ResHacker.exe" -delete "%11%\FileName.exe", "%11%\FileName.exe", Icon,, "%SourceFiles%\ResHacker.exe" -addoverwrite "%11%\FileName.exe", "%11%\FileName.exe", "%SourceFiles%\Icon.res",,, Warning, these sections do same job of [securityFiles*Integration] sections but in different ways; they've been added for they who find hard to understand microsoft guides about "Security Descriptor Definition Language", so you can use these too; anyway it is suggested to use [securityFiles*Integration] section, safer e also faster 1 = gives Admin permissions for a file or a directory 2 = when destination is a directory, gives Admin permission for all files and subdirectories of specified directory 3 = when destination is a directory, if it doesn't exist will be automatically created [FilePermissionsBeforeIntegration] ;;;example [b][FilePermissionsBeforeIntegration][/b] %10%\regedit.exe,1 %COMMONPROGRAMFILES%,1 %16426%\Filename.exe,1 [FilePermissionsAfterIntegration] ;;;example [FilePermissionsAfterIntegration] %10%\test.exe,1 %PROGRAMFILES(X86)%,1 %16428%\Test,3 [AddProgram] ;;;example [AddProgram] Filerefox.exe [color=Green];or[/color] install_flash_player.exe -install -force "SetUp XXX.exe" /S [string] ;;;example [Strings] LANGNAME = "English" LANGUAGE = "ENU" MuiCultureDirectory = "en-US" LangIdHex = "409" Lang = "EN" LCID = "0409" UnlockerTip = "Freeware tool to overcome a Windows bug" ;or use multi local about International INF Files http://msdn.microsoft.com/en-us/library/ff540208%28v=VS.85%29.aspx [Strings.0409] LANGNAME = "English" LANGUAGE = "ENU" MuiCultureDirectory = "en-US" LangIdHex = "409" Lang = "EN" LCID = "0409" UnlockerTip = "Freeware tool to overcome a Windows bug" [Strings.0410] LANGNAME = "Italiano" LANGUAGE = "ITA" MuiCultureDirectory = "it-IT" LangIdHex = "410" Lang = "IT" LCID = "0410" UnlockerTip = "Strumento freeware per superare un bug di Windows" DXIntegrator adds as default these keys in Strings section REG_SZ = 0x00000000 REG_EXPAND_SZ = 0x00020000 REG_DWORD = 0x00010001 REG_QWORD = 0x000B0001 REG_BINARY = 0x00000001 REG_MULTI_SZ = 0x00010000 REG_NONE = 0x00020001 REG_KEYONLY = 0x00000010 REG_KEYONLY_COMMON = 0x00002000 REG_UNKNOWN = 0x00030001 REG_NOCLOBBER = 0x00000002 REG_DELVAL = 0x00000004 REG_OVERWRITEONLY = 0x00000020 REG_APPEND = 0x00000008 ;Append a given value to that of an existing named value entry. This flag is valid only if FLG_ADDREG_TYPE_MULTI_SZ is also set. The specified string value is not appended if it already exists. REG_64BITKEY = 0x00001000 REG_32BITKEY = 0x00004000 REG_SZ_64BITKEY = 0x00001000 REG_SZ_32BITKEY = 0x00004000 REG_SZ_NOCLOBBER = 0x00000002 REG_SZ_NOCLOBBER_64BITKEY = 0x00001002 REG_SZ_NOCLOBBER_32BITKEY = 0x00004002 REG_SZ_DELVAL = 0x00000004 REG_SZ_DELVAL_64BITKEY = 0x00001004 REG_SZ_DELVAL_32BITKEY = 0x00004004 REG_SZ_OVERWRITEONLY = 0x00000020 REG_SZ_OVERWRITEONLY_64BITKEY = 0x00001020 REG_SZ_OVERWRITEONLY_32BITKEY = 0x00004020 REG_EXPAND_SZ_64BITKEY = 0x00021000 REG_EXPAND_SZ_32BITKEY = 0x00024000 REG_EXPAND_SZ_NOCLOBBER = 0x00020002 REG_EXPAND_SZ_NOCLOBBER_64BITKEY = 0x00021002 REG_EXPAND_SZ_NOCLOBBER_32BITKEY = 0x00024002 REG_EXPAND_SZ_DELVAL = 0x00020004 REG_EXPAND_SZ_DELVAL_64BITKEY = 0x00021004 REG_EXPAND_SZ_DELVAL_32BITKEY = 0x00024004 REG_EXPAND_SZ_OVERWRITEONLY = 0x00020020 REG_EXPAND_SZ_OVERWRITEONLY_64BITKEY = 0x00021020 REG_EXPAND_SZ_OVERWRITEONLY_32BITKEY = 0x00024020 REG_DWORD_64BITKEY = 0x00011001 REG_DWORD_32BITKEY = 0x00014001 REG_DWORD_NOCLOBBER = 0x00010003 REG_DWORD_NOCLOBBER_64BITKEY = 0x00011003 REG_DWORD_NOCLOBBER_32BITKEY = 0x00014003 REG_DWORD_DELVAL = 0x00010005 REG_DWORD_DELVAL_64BITKEY = 0x00011005 REG_DWORD_DELVAL_32BITKEY = 0x00014005 REG_DWORD_OVERWRITEONLY = 0x00010021 REG_DWORD_OVERWRITEONLY_64BITKEY = 0x00011021 REG_DWORD_OVERWRITEONLY_32BITKEY = 0x00014021 REG_QWORD_64BITKEY = 0x000B1001 REG_QWORD_32BITKEY = 0x000B4001 REG_QWORD_NOCLOBBER = 0x000B0003 REG_QWORD_NOCLOBBER_64BITKEY = 0x000B1003 REG_QWORD_NOCLOBBER_32BITKEY = 0x000B4003 REG_QWORD_DELVAL = 0x000B0005 REG_QWORD_DELVAL_64BITKEY = 0x000B1005 REG_QWORD_DELVAL_32BITKEY = 0x000B4005 REG_QWORD_OVERWRITEONLY = 0x000B0021 REG_QWORD_OVERWRITEONLY_64BITKEY = 0x000B1021 REG_QWORD_OVERWRITEONLY_32BITKEY = 0x000B4021 REG_BINARY_64BITKEY = 0x00001001 REG_BINARY_32BITKEY = 0x00004001 REG_BINARY_NOCLOBBER = 0x00000003 REG_BINARY_NOCLOBBER_64BITKEY = 0x00001003 REG_BINARY_NOCLOBBER_32BITKEY = 0x00004003 REG_BINARY_DELVAL = 0x00000005 REG_BINARY_DELVAL_64BITKEY = 0x00001005 REG_BINARY_DELVAL_32BITKEY = 0x00004005 REG_BINARY_OVERWRITEONLY = 0x00000021 REG_BINARY_OVERWRITEONLY_64BITKEY = 0x00001021 REG_BINARY_OVERWRITEONLY_32BITKEY = 0x00004021 REG_MULTI_SZ_64BITKEY = 0x00011000 REG_MULTI_SZ_32BITKEY = 0x00014000 REG_MULTI_SZ_APPEND = 0x00010008 REG_MULTI_SZ_APPEND_64BITKEY = 0x00011008 REG_MULTI_SZ_APPEND_32BITKEY = 0x00014008 REG_MULTI_SZ_NOCLOBBER = 0x00010002 REG_MULTI_SZ_NOCLOBBER_64BITKEY = 0x00011002 REG_MULTI_SZ_NOCLOBBER_32BITKEY = 0x00014002 REG_MULTI_SZ_DELVAL = 0x00010004 REG_MULTI_SZ_DELVAL_64BITKEY = 0x00011004 REG_MULTI_SZ_DELVAL_32BITKEY = 0x00014004 REG_MULTI_SZ_OVERWRITEONLY = 0x00010020 REG_MULTI_SZ_OVERWRITEONLY_64BITKEY = 0x00011020 REG_MULTI_SZ_OVERWRITEONLY_32BITKEY = 0x00014020 REG_NONE_64BITKEY = 0x00021001 REG_NONE_32BITKEY = 0x00022001 REG_NONE_NOCLOBBER = 0x00020003 REG_NONE_NOCLOBBER_64BITKEY = 0x00021003 REG_NONE_NOCLOBBER_32BITKEY = 0x00024003 REG_NONE_DELVAL = 0x00020005 REG_NONE_DELVAL_64BITKEY = 0x00021005 REG_NONE_DELVAL_32BITKEY = 0x00024005 REG_NONE_OVERWRITEONLY = 0x00020021 REG_NONE_OVERWRITEONLY_64BITKEY = 0x00021021 REG_NONE_OVERWRITEONLY_32BITKEY = 0x00024021 REG_KEYONLY_64BITKEY = 0x00001010 REG_KEYONLY_32BITKEY = 0x00004010 REG_KEYONLY_NOCLOBBER = 0x00000012 REG_KEYONLY_NOCLOBBER_64BITKEY = 0x00001012 REG_KEYONLY_NOCLOBBER_32BITKEY = 0x00004012 REG_KEYONLY_DELVAL = 0x00000015 REG_KEYONLY_DELVAL_64BITKEY = 0x00001015 REG_KEYONLY_DELVAL_32BITKEY = 0x00004015 REG_KEYONLY_OVERWRITEONLY = 0x00000030 REG_KEYONLY_OVERWRITEONLY_64BITKEY = 0x00001030 REG_KEYONLY_OVERWRITEONLY_32BITKEY = 0x00004030 REG_KEYONLY_COMMON_64BITKEY = 0x00003000 REG_KEYONLY_COMMON_32BITKEY = 0x00006000 REG_KEYONLY_COMMON_NOCLOBBER = 0x00002002 REG_KEYONLY_COMMON_NOCLOBBER_64BITKEY = 0x00003002 REG_KEYONLY_COMMON_NOCLOBBER_32BITKEY = 0x00006002 REG_KEYONLY_COMMON_DELVAL = 0x00002005 REG_KEYONLY_COMMON_DELVAL_64BITKEY = 0x00003005 REG_KEYONLY_COMMON_DELVAL_32BITKEY = 0x00006005 REG_KEYONLY_COMMON_OVERWRITEONLY = 0x00002020 REG_KEYONLY_COMMON_OVERWRITEONLY_64BITKEY = 0x00003020 REG_KEYONLY_COMMON_OVERWRITEONLY_32BITKEY = 0x00006020 REG_UNKNOWN_64BITKEY = 0x00031001 REG_UNKNOWN_32BITKEY = 0x00032001 REG_UNKNOWN_NOCLOBBER = 0x00030003 REG_UNKNOWN_NOCLOBBER_64BITKEY = 0x00031003 REG_UNKNOWN_NOCLOBBER_32BITKEY = 0x00034003 REG_UNKNOWN_DELVAL = 0x00030005 REG_UNKNOWN_DELVAL_64BITKEY = 0x00031005 REG_UNKNOWN_DELVAL_32BITKEY = 0x00034005 REG_UNKNOWN_OVERWRITEONLY = 0x00030021 REG_UNKNOWN_OVERWRITEONLY_64BITKEY = 0x00031021 REG_UNKNOWN_OVERWRITEONLY_32BITKEY = 0x00034021 ; ServiceType values SERVICE_KERNEL_DRIVER = 0x00000001 SERVICE_FILE_SYSTEM_DRIVER = 0x00000002 SERVICE_ADAPTER = 0x00000004 SERVICE_RECOGNIZER_DRIVER = 0x00000008 SERVICE_WIN32_OWN_PROCESS = 0x00000010 SERVICE_WIN32_SHARE_PROCESS = 0x00000020 SERVICE_INTERACTIVE_PROCESS = 0x00000100 SERVICE_INTERACTIVE_SHARE_PROCESS = 0x00000120 ; StartType values SERVICE_BOOT_START = 0x00000000 SERVICE_SYSTEM_START = 0x00000001 SERVICE_AUTO_START = 0x00000002 SERVICE_DEMAND_START = 0x00000003 SERVICE_DISABLED = 0x00000004 ; ErrorControl values SERVICE_ERROR_IGNORE = 0x00000000 SERVICE_ERROR_NORMAL = 0x00000001 SERVICE_ERROR_SEVERE = 0x00000002 SERVICE_ERROR_CRITICAL = 0x00000003 SPSVCINST_TAGTOFRONT = 0x00000001 SPSVCINST_ASSOCSERVICE = 0x00000002 SPSVCINST_DELETEEVENTLOGENTRY = 0x00000004 SPSVCINST_NOCLOBBER_DISPLAYNAME = 0x00000008 SPSVCINST_NOCLOBBER_STARTTYPE = 0x00000010 SPSVCINST_NOCLOBBER_ERRORCONTROL = 0x00000020 SPSVCINST_NOCLOBBER_LOADORDERGROUP = 0x00000040 SPSVCINST_NOCLOBBER_DEPENDENCIES = 0x00000080 SPSVCINST_NOCLOBBER_DESCRIPTION = 0x00000100 COPYFLG_WARN_IF_SKIP = 0x00000001 COPYFLG_NOSKIP = 0x00000002 COPYFLG_NOVERSIONCHECK = 0x00000004 COPYFLG_FORCE_FILE_IN_USE = 0x00000008 COPYFLG_NO_OVERWRITE = 0x00000010 COPYFLG_NO_VERSION_DIALOG = 0x00000020 COPYFLG_OVERWRITE_OLDER_ONLY = 0x00000040 COPYFLG_REPLACEONLY = 0x00000400 COPYFLG_REPLACE_BOOT_FILE = 0x00001000 COPYFLG_NOPRUNE = 0x00002000 this is the integration process executed by DXIntegrator 1 [FilePermissionsBeforeIntegration] 2 [securityFilesBeforeIntegration] 3 [ProcessesToRunBeforeIntegration] 4 [securityRegistryBeforeIntegration] 5 Offline Install Execution (installs addon AddOn) 6 [TweaksAddReg] 7 [TweaksDelReg] 8 [securityRegistryAfterIntegration] 9 [ProcessesToRunAfterIntegration] 10 [securityFilesBeforeIntegration] 11 [FilePermissionsAfterIntegration]

updated

updated to fit latest Onepiece's XP/2k3 UpdatePacks

updated

updated

http://www.wincert.net/forum/index.php?/forum/196-winnt6x-true-integrator-addons/

updated (improved x64 true addons integration)

updated with latest public hotfixes. Now .Net 4.0 addon can be integrated in Windows 7 32 bit too, using DX Integrator!

updated with latest public hotfixes

Updated. Now it is compatible with XP addons (I don't know if it works with Switchless installers). The limitations are: You can use only .cab addons (recompress them with CabTool); You must add a section in True Addons entries.ini file (not needed fo Svcpack addons)

Onepiece's DX WinNT6.x True Integrator is a DISM (Deployment Image Servicing and Management) GUI, based on Microsoft command-line Dism.exe, default in Windows 7 (see here for info http://technet.microsoft.com/en-us/library/dd744566(WS.10).aspx) DX WinNT6.x True Integrator is full international: your system language is selected on start by default but if you have different languages you can force to start with needed one by adding the "language display name" in a /%LANG% switch, ie, if your Windows 7 has english and german langpacks add "/German" (without quotes) for german (switches list) Once started, you must choose wim image path, mount directory and kind of image you want to modify, then press "Mount". DX Integrator can work also on a previously mounted image and automatically remount it only if needed. Now DX WinNT6.x True Integrator can process all Windows editions (starter, home, pro, ultimate,...) in single WIM files. The edition to be mounted is the one highlighted in blue with your mouse. If you need to process other editions, then add a check in correspondant checkbox (in the example, #2 will be mounted and modified. When finished, automatically #1 and #3 will be processed at the same way) Important! you must click on "next" if you want to process all editions you've checked. If you click on "apply", only the edition higlighted in blue will be processed. NB. For time/space saving reason Windows PE x64 is used in this video tutorial. Next step you can enable and disable Windows features. Please be careful here, because if you choose to enable or disable unsupported features, your image will be damaged and become unusable, so you must unmount the image and mount it again. When done, press Apply to immediately apply the modifications to the image or Next to apply them at the end. Then you can add packages like hotfixes and langpack. Both *.cab and *.msu are supported but it's better to use .cab files extracted from *.msu packages, because DISM.exe handles them more directly. You can also uninstall from image an existing hotfix (listed in the upper packages list) by clicking on "state" column. DX Integrator is also able to recognize file version and silently uninstall older hotfixes or deny obsolete ones installation. The order of hotfixes integration can be changed and everything is checked when you press "apply". You can also check the correct integration of every single hotfix in image by switching "IGNORE-CHECK" (default) in "CHECK-STATE" but remember that this requires additional 20-40 seconds per hotfixes and now there are about 300 w7 official-unofficial hotfixes... Now you can add drivers. The upper window lists existing third-party drivers which you can also choose to uninstall, in lower window you can add new drivers in your image (force unsigned driver to install option is activated by default) ... to be continued...(?)

Second answer WU will update .net framework with new hotfixes in the same way, either you've integrated it in your source using this addon or you've installed it in running system using default installer. Obviously, when new hotfixes will come out, an updated build of this addon will be released for your future integrations

An all-in-one addon composed by 1.1+3.5full+4.0 is useless because you don't save any space and anyway each dotnet framework must wait the setup end of previous one before it can start its one, as in 3 separate addon like now.

During Windows setup you can always press Ctrl+F11 to see what's happening. OnePiece_Remove Addons only removes Windows optional components added by pack itself. Once ago, there was some interesting remove addons from keytotime http://www.ryanvm.net/forum/viewtopic.php?p=20343#20343 but the links are dead now. Unfortunately OnePiece has connection problem due to Albanian ISPs and it's not so easy for him uploading his work everywhere

@wallled: Simply use RVMi to integrate first the updatepack then to add every Onepiece's Remove Addon you like. Now you can use Nlite on your source if you want to add or remove something more (but be careful with the removal. @medozzz0: if you are sure that your source is untouched, use RVM integrator and retry to integrate updatepack only (verify if pack MD5 hash is correct) and test the iso on a VM.

Just tried now and created this: OnePiece IE8 WinXPSP3 True AddOn_FRA Update (August 16-2010) Hash MD5 D1A29786F205D65A1B0370B8C7816686 Filesize: 11.2 MB (11784772 byte) It works like a charm on French XP SP3 MSDN. You can use this or rebuild it by yourself from scratch, using the latest tool. You can also upload somewhere the defective addon, we can have a look at it

Updated: switched .Net updates from QFE to GDR branch to improve WU/MU compatibility. This because in dotnet updates MicrosoftUpdate forces GDR over QFE branch, which always has an higher build, so this could cause MU/WU to fail with repeated and annoying attempts. Anyway for the braves who despite that still want a full QFE branch updated .net true integration there's also an additional addon to overwrite GDR updated files added by Onepiece's 3.5 SP1 GDR true addon with QFE ones.

New releases. Now updates GDR branch is used. This because in dotnet updates MicrosoftUpdate forces GDR over QFE branch, which always has an higher build, so this could cause MU/WU to fail with repeated and annoying attempts. Anyway for the braves who despite that still want a full QFE branch updated .net true integration there's also an additional addon to overwrite GDR updated files added by Onepiece's 3.5 SP1 GDR true addon with QFE ones

updated to fit latest Onepiece's XP/2k3 UpdatePacks

Maybe you've integrated IE8 2 times in that CD. Retry with an untouched one or see if your txtsetup.sif there are doubled lines like these: ie4uinit.mui = 100,,,,,,,2,0,0,ie4uinit.exe.mui iedkcs32.mui = 100,,,,,,,2,0,0,iedkcs32.dll.mui ieframe.mui = 100,,,,,,,2,0,0,ieframe.dll.mui mshta.mui = 100,,,,,,,2,0,0,mshta.exe.mui msrating.mui = 100,,,,,,,2,0,0,msrating.dll.mui sqmapi.dll = 100,,,,,,,,3,3 ie4uinit.mui = 100,,,,,,,2,0,0,ie4uinit.exe.mui iedkcs32.mui = 100,,,,,,,2,0,0,iedkcs32.dll.mui ieframe.mui = 100,,,,,,,2,0,0,ieframe.dll.mui mshta.mui = 100,,,,,,,2,0,0,mshta.exe.mui msrating.mui = 100,,,,,,,2,0,0,msrating.dll.mui sqmapi.dll = 100,,,,,,,,3,3 in this case leave only these: ie4uinit.mui = 100,,,,,,,2,0,0,ie4uinit.exe.mui iedkcs32.mui = 100,,,,,,,2,0,0,iedkcs32.dll.mui ieframe.mui = 100,,,,,,,2,0,0,ieframe.dll.mui mshta.mui = 100,,,,,,,2,0,0,mshta.exe.mui msrating.mui = 100,,,,,,,2,0,0,msrating.dll.mui sqmapi.dll = 100,,,,,,,,3,3 However as some reglines are changed in new IE8 update, it is better to rebuilt a new addon using Onepiece's tool and rebuild a new CD from a clean source.

KB954459 is not present in this pack. It has been superseded by public MS update KB973687. Anyway the problem is not related to the pack but to Service Pack 3: SQL 2005 uses a very old setup file which is not able to see that MSXML6 is already resident in memory (it starts with windows, default from SP3), so it tries to install it and obviously fails. You should ask in Microsoft Social Network for a workaround

new release (see changelog)

Updated: improved setup with low-end PCs

Updated. 1.1: improved compatibility with XP MCE 2005 2.0-3.0-3.5: added NDP20SP2-KB983583-x86