Onepiece XP Post-SP3 AIO Update Pack FINAL
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
Nice to hear this.
As you know you can use DX's Update Pack Creator for a fast and easy job.
If you do that way, please take note that Unicode language XP users (like ARA, CHS, CHT, ELL, HEB, JPN, KOR, RUS) should update manually the TimeZone Hotfix lines as DXUPAC is not able to to take out lines in local language so they are created in English. You need to extract latest TimeZone KB (you find them under [TZ_KBLAST.AddReg]) and update all lines from Argentina_Display=* to Yakutsk_Display in Strings section.
As you know you can use DX's Update Pack Creator for a fast and easy job.
If you do that way, please take note that Unicode language XP users (like ARA, CHS, CHT, ELL, HEB, JPN, KOR, RUS) should update manually the TimeZone Hotfix lines as DXUPAC is not able to to take out lines in local language so they are created in English. You need to extract latest TimeZone KB (you find them under [TZ_KBLAST.AddReg]) and update all lines from Argentina_Display=* to Yakutsk_Display in Strings section.
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
1) Yes but not only. For example, Onepiece's IE8 "official" addon uses "true" (native) mode to install but with DXUPAC you can also create a Svcpack or RunOnceEX install Addon, and it allows you to add your own IE tweaks; or you can use DXUPAC to integrate SP3 in XP Media Center Edition, and so on.Ultraform wrote:What really is "DX Universal UpdatePack/Addon Creator"
you make like " Onepiece XP Post-SP3 AIO Update Pack" and other addons but in other language ?
edit :
Do you replaced/removed Hotfix in the Changes/updates you made in the
"Onepiece XP Post-SP3 AIO Update Pack" :O ?
2) I'm not sure if I've understood clearly your question but I try to answer: when a new hotfix replaces another one, you can see it in Changelog file ("supersedes KB......) and the superseded hotfix description is deleted from Hotfixes List
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
Remember, this pack is intended to be used with a "clean" source that has only had SP3 added to it, not any other previous updates, and not on any existing live install. The resulting build is also intended to only be used to do a "clean" install, not any kind of repair or update install, so again no previous outdated and superseded hotfixes are involved in any way.Ultraform wrote:Do you replaced/removed Hotfix in the Changes/updates you made in the "Onepiece XP Post-SP3 AIO Update Pack" :O ?
Cheers and Regards
-
- Posts: 5
- Joined: Wed Feb 09, 2011 9:32 am
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
Wow, a real bug at last...
New update KB2813347 partially updates KB969094. This is a very rare (1 in 290 in pack+200 obsoleted) GDR-only hotfix and we missed it.
To fix it in a live system is rather easy:
- Download WindowsXP-KB2813347-x86-ENU.exe file and extract it (simple run it with -x command)
- Copy (change) these files:
New update KB2813347 partially updates KB969094. This is a very rare (1 in 290 in pack+200 obsoleted) GDR-only hotfix and we missed it.
To fix it in a live system is rather easy:
- Download WindowsXP-KB2813347-x86-ENU.exe file and extract it (simple run it with -x command)
- Copy (change) these files:
Code: Select all
"..\WindowsXP-KB2813347-x86-ENU\SP3GDR\aaclient.dll" "%SystemRoot%\System32\aaclient.dll"
"..\WindowsXP-KB2813347-x86-ENU\SP3GDR\mstsc.exe" "%SystemRoot%\System32\mstsc.exe"
"..\WindowsXP-KB2813347-x86-ENU\SP3GDR\mstscax.dll" "%SystemRoot%\System32\mstscax.dll"
"..\WindowsXP-KB2813347-x86-ENU\SP3GDR\tsgqec.dll" "%SystemRoot%\System32\tsgqec.dll"
"..\WindowsXP-KB2813347-x86-ENU\SP3GDR\wksprt.exe" "%SystemRoot%\System32\wksprt.exe"
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
nonno Fabio,
as a temp fix for my updatepack I realeased a version 20130514a.
I just replaced the QFE mstscax.dll with the GDR. no reg entry changes or it would break MU.
this is only temporary until MS releases a new Hotfix/Update to replace KB2813347.
surprised a fix was not updated for last patch Tuesday!
as a temp fix for my updatepack I realeased a version 20130514a.
I just replaced the QFE mstscax.dll with the GDR. no reg entry changes or it would break MU.
this is only temporary until MS releases a new Hotfix/Update to replace KB2813347.
surprised a fix was not updated for last patch Tuesday!
- OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
Hi user_hidden, Thank You
Update Pack v6.8.0 is Ok, the bug is in the Update Pack v6.7.0 (April 10 2013 Releases, Italian user who first discovered the BUG
http://www.eng2ita.net/forum/index.php/ ... l#msg61229 ), I do not think that will be released a new Update, is a case very unique\rare, microsoft seems that wrong with what hotfix, the point is that everything happens because it seems to put microsoft QFE update them by mistake, the hotfix basic is WindowsXP-KB969084-x86-ENU.exe (which the WindowsXP-KB2813347-x86-ENU.exe update partially) is only in GDR ehhhhh, in fact happens, if extract the WindowsXP-KB969084-x86-ENU.exe you will notice that we only inside the folder sp3gdr anything else (there are so hotfix but is really very very rare, say nearly one in 500, we just missed it, because if we remember the KB969084 we immediately noticed the error\mistake microsoft put them file QFE), in poor words is a error\mistake of microsoft, but also on our part there was a bit of oversight
how to say, however is really a very very rare case ehhhh
all this perhaps because the fate that it seems that microsoft decided by now that all the new official update will be fully oriented to QFE (if I'm not mistaken I've read in microsoft.com weks ago, but can not remember where now) however the fates that are the latest Update of Windows Server 2003 are now in QFE only, however for us, this does not create any kind of problem (is OK) Thanks RyanVM has always been decided\used in All Update Pack only the QFE, so for us does not change anything
Ciao.
Update Pack v6.8.0 is Ok, the bug is in the Update Pack v6.7.0 (April 10 2013 Releases, Italian user who first discovered the BUG


all this perhaps because the fate that it seems that microsoft decided by now that all the new official update will be fully oriented to QFE (if I'm not mistaken I've read in microsoft.com weks ago, but can not remember where now) however the fates that are the latest Update of Windows Server 2003 are now in QFE only, however for us, this does not create any kind of problem (is OK) Thanks RyanVM has always been decided\used in All Update Pack only the QFE, so for us does not change anything
Ciao.
Last edited by OnePiece Alb on Tue May 21, 2013 2:21 pm, edited 14 times in total.
-
- Posts: 5
- Joined: Wed Feb 09, 2011 9:32 am
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
wait, v6.8.0 pack (May, 15th) is already OK from the beginning.
The issue involves only v6.7.0 (April release) and it wasn't fixed as it has been first pointed out on May 3th in ITA community and fixed in a Onepiece's v6.7.0 DEU Updatepack (DXUPAC demo) but not in ENU one as May Patch Tuesday was only a few days after.
Verify your updatepack version, redownload and retry an integration on a clean XP CD: you'll got no issues.
The issue involves only v6.7.0 (April release) and it wasn't fixed as it has been first pointed out on May 3th in ITA community and fixed in a Onepiece's v6.7.0 DEU Updatepack (DXUPAC demo) but not in ENU one as May Patch Tuesday was only a few days after.
Verify your updatepack version, redownload and retry an integration on a clean XP CD: you'll got no issues.
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
-
- Posts: 5
- Joined: Wed Feb 09, 2011 9:32 am
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
the v6.7.0 fix change v6.7.0 files with v.6.8.0 one. If you run it on a v6.8.0 updated XP you'll get same files.
;;;; OPMWXPUP.inf in OnePiece Update Pack v6.8.0
.
;;;; OPMWXPUP.inf in OnePiece Update Pack v6.7.0
;;;; OPMWXPUP.inf in OnePiece Update Pack v6.8.0
[KB2813347.AddReg]
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347", "Description", %REG_SZ%, "%LOC_SECURITY_UPDATE% for %PRODUCT_NAME% (KB2813347)"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347", "InstalledBy", %REG_SZ%, "%NAME%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347", "InstalledDate", %REG_SZ%, "%VERSION%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347", "Type", %REG_SZ%, "Update"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\0", "FileName", %REG_SZ%, "aaclient.dll"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\0", "Version", %REG_SZ%, "6.1.7600.17233"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\0", "BuildDate", %REG_SZ%, "Wed Feb 27 07:31:23 2013"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\0", "BuildCheckSum", %REG_SZ%, "24999"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\0", "Location", %REG_SZ%, "%11%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\1", "FileName", %REG_SZ%, "mstsc.exe"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\1", "Version", %REG_SZ%, "6.1.7600.16722"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\1", "BuildDate", %REG_SZ%, "Wed Feb 27 02:21:54 2013"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\1", "BuildCheckSum", %REG_SZ%, "10a71b"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\1", "Location", %REG_SZ%, "%11%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\2", "FileName", %REG_SZ%, "mstscax.dll"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\2", "Version", %REG_SZ%, "6.1.7600.17233"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\2", "BuildDate", %REG_SZ%, "Wed Feb 27 07:31:23 2013"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\2", "BuildCheckSum", %REG_SZ%, "29e1a2"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\2", "Location", %REG_SZ%, "%11%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\3", "FileName", %REG_SZ%, "tsgqec.dll"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\3", "Version", %REG_SZ%, "6.1.7600.17233"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\3", "BuildDate", %REG_SZ%, "Wed Feb 27 07:31:23 2013"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\3", "BuildCheckSum", %REG_SZ%, "11787"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\3", "Location", %REG_SZ%, "%11%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\4", "FileName", %REG_SZ%, "wksprt.exe"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\4", "Version", %REG_SZ%, "6.1.7600.16385"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\4", "BuildDate", %REG_SZ%, "Wed Feb 27 02:21:55 2013"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\4", "BuildCheckSum", %REG_SZ%, "388ea"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\4", "Location", %REG_SZ%, "%11%"
HKLM, "%KEY_HOTFIX%\KB2813347", "Backup Dir", %REG_SZ%, ""
HKLM, "%KEY_HOTFIX%\KB2813347", "Comments", %REG_SZ%, "%LOC_SECURITY_UPDATE% for %PRODUCT_NAME% (KB2813347)"
HKLM, "%KEY_HOTFIX%\KB2813347", "Fix Description", %REG_SZ%, "%LOC_SECURITY_UPDATE% for %PRODUCT_NAME% (KB2813347)"
HKLM, "%KEY_HOTFIX%\KB2813347", "Installed", %REG_DWORD%, "1"
HKLM, "%KEY_HOTFIX%\KB2813347", "Installed By", %REG_SZ%, "%NAME%"
HKLM, "%KEY_HOTFIX%\KB2813347", "Installed On", %REG_SZ%, "%VERSION%"
HKLM, "%KEY_HOTFIX%\KB2813347", "Service Pack", %REG_DWORD%, %SERVICE_PACK_NUMBER%
HKLM, "%KEY_HOTFIX%\KB2813347", "Valid", %REG_DWORD%, "1"
HKLM, "%KEY_HOTFIX%\KB2813347\File 1", "Flags", %REG_SZ%, ""
HKLM, "%KEY_HOTFIX%\KB2813347\File 1", "New File", %REG_SZ%, ""
HKLM, "%KEY_HOTFIX%\KB2813347\File 1", "New Link Date", %REG_SZ%, ""
HKLM, "%KEY_HOTFIX%\KB2813347\File 1", "Old Link Date", %REG_SZ%, ""
WindowsXP-KB2813347-x86-ENU contains these files:..\OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_ENU\aaclient.dll HashMD5 - 7902E06337A9534BCBF418F01D6CE30A
..\OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_ENU\lhmstsc.exe HashMD5 - 2553AD01F1ED5CDD939F5D12303E9709
..\OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_ENU\lhmstscx.dll HashMD5 - C8605F6CD65D38512A526366F0761841
..\OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_ENU\tsgqec.dll HashMD5 - 8799E1D0AA33A333DCDEDA52040C02F0
..\OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_ENU\wksprt.exe HashMD5 - EE4E2F7757C9F5B2B7B8367E25C60237
.
.\WindowsXP-KB2813347-x86-ENU\SP3GDR\aaclient.dll HashMD5 - 7902E06337A9534BCBF418F01D6CE30A
..\WindowsXP-KB2813347-x86-ENU\SP3GDR\mstsc.exe HashMD5 - 2553AD01F1ED5CDD939F5D12303E9709
..\WindowsXP-KB2813347-x86-ENU\SP3GDR\mstscax.dll HashMD5 - C8605F6CD65D38512A526366F0761841
..\WindowsXP-KB2813347-x86-ENU\SP3GDR\tsgqec.dll HashMD5 - 8799E1D0AA33A333DCDEDA52040C02F0
..\WindowsXP-KB2813347-x86-ENU\SP3GDR\wksprt.exe HashMD5 - EE4E2F7757C9F5B2B7B8367E25C60237
..\WindowsXP-KB2813347-x86-ENU\SP3QFE\aaclient.dll HashMD5 - 90D5A075E2B37DC77074502C24154FB2
..\WindowsXP-KB2813347-x86-ENU\SP3QFE\mstsc.exe HashMD5 - 16E0EFDB794FE09EDCB2CD4C2D761BB1
..\WindowsXP-KB2813347-x86-ENU\SP3QFE\mstscax.dll HashMD5 - AD606293A87C97EBFCA21F5B77C8E1B1
..\WindowsXP-KB2813347-x86-ENU\SP3QFE\tsgqec.dll HashMD5 - 093BF5BBB4A1AFEEE0381AA720E35869
..\WindowsXP-KB2813347-x86-ENU\SP3QFE\wksprt.exe HashMD5 - 122FF221625EB0459B6FD3752B88007D
;;;; OPMWXPUP.inf in OnePiece Update Pack v6.7.0
See here: http://youtu.be/o_28F7EVj6s[KB2813347.AddReg]
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347", "Description", %REG_SZ%, "%LOC_SECURITY_UPDATE% for %PRODUCT_NAME% (KB2813347)"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347", "InstalledBy", %REG_SZ%, "%NAME%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347", "InstalledDate", %REG_SZ%, "%VERSION%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347", "Type", %REG_SZ%, "Update"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\0", "FileName", %REG_SZ%, "wksprt.exe"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\0", "Version", %REG_SZ%, "6.1.7600.21448"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\0", "BuildDate", %REG_SZ%, "Wed Feb 13 12:23:21 2013"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\0", "BuildCheckSum", %REG_SZ%, "44d29"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\0", "Location", %REG_SZ%, "%11%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\1", "FileName", %REG_SZ%, "tsgqec.dll"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\1", "Version", %REG_SZ%, "6.1.7600.21448"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\1", "BuildDate", %REG_SZ%, "Wed Feb 27 06:30:46 2013"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\1", "BuildCheckSum", %REG_SZ%, "12e1c"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\1", "Location", %REG_SZ%, "%11%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\2", "FileName", %REG_SZ%, "mstscax.dll"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\2", "Version", %REG_SZ%, "6.1.7600.21448"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\2", "BuildDate", %REG_SZ%, "Wed Feb 27 06:30:46 2013"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\2", "BuildCheckSum", %REG_SZ%, "2a3835"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\2", "Location", %REG_SZ%, "%11%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\3", "FileName", %REG_SZ%, "mstsc.exe"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\3", "Version", %REG_SZ%, "6.1.7600.21448"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\3", "BuildDate", %REG_SZ%, "Wed Feb 13 12:23:25 2013"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\3", "BuildCheckSum", %REG_SZ%, "100674"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\3", "Location", %REG_SZ%, "%11%"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\4", "FileName", %REG_SZ%, "aaclient.dll"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\4", "Version", %REG_SZ%, "6.1.7600.21448"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\4", "BuildDate", %REG_SZ%, "Wed Feb 27 06:30:46 2013"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\4", "BuildCheckSum", %REG_SZ%, "20743"
HKLM, "%UpdateRegKey%\%PRODUCT_NAME%\SP%SERVICE_PACK_NUMBER%\KB2813347\Filelist\4", "Location", %REG_SZ%, "%11%"
HKLM, "%KEY_HOTFIX%\KB2813347", "Backup Dir", %REG_SZ%, ""
HKLM, "%KEY_HOTFIX%\KB2813347", "Comments", %REG_SZ%, "%LOC_SECURITY_UPDATE% for %PRODUCT_NAME% (KB2813347)"
HKLM, "%KEY_HOTFIX%\KB2813347", "Fix Description", %REG_SZ%, "%LOC_SECURITY_UPDATE% for %PRODUCT_NAME% (KB2813347)"
HKLM, "%KEY_HOTFIX%\KB2813347", "Installed", %REG_DWORD%, "1"
HKLM, "%KEY_HOTFIX%\KB2813347", "Installed By", %REG_SZ%, "%NAME%"
HKLM, "%KEY_HOTFIX%\KB2813347", "Installed On", %REG_SZ%, "%VERSION%"
HKLM, "%KEY_HOTFIX%\KB2813347", "Service Pack", %REG_DWORD%, %SERVICE_PACK_NUMBER%
HKLM, "%KEY_HOTFIX%\KB2813347", "Valid", %REG_DWORD%, "1"
HKLM, "%KEY_HOTFIX%\KB2813347\File 1", "Flags", %REG_SZ%, ""
HKLM, "%KEY_HOTFIX%\KB2813347\File 1", "New File", %REG_SZ%, ""
HKLM, "%KEY_HOTFIX%\KB2813347\File 1", "New Link Date", %REG_SZ%, ""
HKLM, "%KEY_HOTFIX%\KB2813347\File 1", "Old Link Date", %REG_SZ%, ""
Last edited by nonno fabio on Fri Jun 14, 2013 6:32 pm, edited 1 time in total.
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
You can patch mstscax.dll 6.1.7600.21448 with a resource editor.
You need to update the MUI section with the one from the GDR dll file to fix this error. You can also use the MUI section from the previous QFE dll, KB2483614, they are identical.
This will break the digital signature so you need to patch system file protection to make it work.
You need to update the MUI section with the one from the GDR dll file to fix this error. You can also use the MUI section from the previous QFE dll, KB2483614, they are identical.
This will break the digital signature so you need to patch system file protection to make it work.
Last edited by Acheron on Tue Jul 16, 2013 12:48 pm, edited 1 time in total.
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
@Acheron
it would not be a good idea to pack a modified MS file in any of our update packs.
only untouched original files should be included.
as for this particular update KB2813347, it replaced some files from KB969084 which was itself
a GDR update so therefore the problem now with using the QFE files from KB2813347 cause the
RDP issue. the proper fix is to use the GDR branch files.
OnePiece Alb had already pointed the above out a few posts above this one.
it would not be a good idea to pack a modified MS file in any of our update packs.
only untouched original files should be included.
as for this particular update KB2813347, it replaced some files from KB969084 which was itself
a GDR update so therefore the problem now with using the QFE files from KB2813347 cause the
RDP issue. the proper fix is to use the GDR branch files.
OnePiece Alb had already pointed the above out a few posts above this one.
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
I'm sorry if I confused you. I don't want you to include modified system files when an alternative is available.
The patch I posted was to show what this error was about and how you can fix it on a running system.
BTW, you contradict your previous post. First you say the problem is caused by mixing GDR with QFE files.
Then after I posted why this is not an issue you say the exact opposite.
And don't bring MS to the discussion. I don't think they like these update packs to be distributed anyway.
The patch I posted was to show what this error was about and how you can fix it on a running system.
BTW, you contradict your previous post. First you say the problem is caused by mixing GDR with QFE files.
Then after I posted why this is not an issue you say the exact opposite.
And don't bring MS to the discussion. I don't think they like these update packs to be distributed anyway.
Instead of patching mstscax.dll another fix is updating mstscax.dll.mui to 6.1.7600.21103, included inside KB2648397.
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
about KB2813347:
http://www.ryanvm.net/forum/viewtopic.p ... 145#132145
http://www.ryanvm.net/forum/viewtopic.p ... 145#132145
nonno fabio wrote:v6.8.0 pack (May, 15th) is already OK from the beginning.
The issue involves v6.7.0 (April release) only ...
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
new release (see changelog)
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
- UtCollector
- Posts: 464
- Joined: Sun Apr 09, 2006 8:31 pm
- Contact:
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
A win7 updatepack has no sense as Microsoft has done its job, at last.
.msu and .cab updates integrates directly in true mode with DISM. And non .msu updates (DirectX, .net 4.0 x86, Silverlight, Flash Player ActiveX, MRT...) can be integrated using true-mode addons and DXWinNT6.x True Integrator. In Windows 7 there's no difference in integrating an AIO addon or separated single addons.
Thank you for your appreciation.
.msu and .cab updates integrates directly in true mode with DISM. And non .msu updates (DirectX, .net 4.0 x86, Silverlight, Flash Player ActiveX, MRT...) can be integrated using true-mode addons and DXWinNT6.x True Integrator. In Windows 7 there's no difference in integrating an AIO addon or separated single addons.
Thank you for your appreciation.
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
- OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
Hi..
A little confusing I know.sorry!.
OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_NLD_C59A1DCC93595567304B09C1EBEDD4E9
loading in Nlite Fail.
[general]
builddate=2013/30/05
description=OnePiece's Windows XP Post-SP3 Update Pack
forcelang=Dutch
language=Dutch
ServicePack=SP3
title=OnePiece's Windows XP Post-SP3 Update Pack
version=6.8.0
website=http://www.microsoft.com/technet/security/current.aspx
Windows=XP
Need to be for NLite:
[general]
forcelang=Nederlands
language=Nederlands
and when I change this option..Loading is fine in NLite.
But If I start to slipstream..This message show up..
Missing file:
OPMWXPUP.inf
The File is there but still this Error?.What can I do to Fix this?.
I download the File from SkyDrive.
Grt and Thx for bild all this stuff!!!...
A little confusing I know.sorry!.
OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_NLD_C59A1DCC93595567304B09C1EBEDD4E9
loading in Nlite Fail.
[general]
builddate=2013/30/05
description=OnePiece's Windows XP Post-SP3 Update Pack
forcelang=Dutch
language=Dutch
ServicePack=SP3
title=OnePiece's Windows XP Post-SP3 Update Pack
version=6.8.0
website=http://www.microsoft.com/technet/security/current.aspx
Windows=XP
Need to be for NLite:
[general]
forcelang=Nederlands
language=Nederlands
and when I change this option..Loading is fine in NLite.
But If I start to slipstream..This message show up..
Missing file:
OPMWXPUP.inf
The File is there but still this Error?.What can I do to Fix this?.
I download the File from SkyDrive.
Grt and Thx for bild all this stuff!!!...
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
All updatepacks are always tested with RVM Integrator to be 100% sure that everything is OK, so we have missed this. Maybe is a small Nlite bug as Microsoft itself specifies NLD localization as "dutch" as you can see in your PRODSPEC.ini file
Anyway, you should simply click on "No" when you are asked for:


About missing OPMWXPUP.inf file, please verify MD5 hash after download and if you see differences download it again from https://www.mixturecloud.com/album/1vih2Bva or http://voidseesaw.com/onepiece/). If MD5 hash is correct, probably Updatepack has been corrupted while archived or similar
Code: Select all
;
;Opmerking voor de gebruiker: VERANDER OF VERWIJDER DIT BESTAND NIET.
;
[SMS Inventory Identification]
Version=1.0
[Product Specification]
Product=Windows XP Professional
Version=5.0
Localization=Dutch
ServicePackNumber=0
BitVersion=40
[Version]
DriverVer=07/01/2001,5.1.2600.0


About missing OPMWXPUP.inf file, please verify MD5 hash after download and if you see differences download it again from https://www.mixturecloud.com/album/1vih2Bva or http://voidseesaw.com/onepiece/). If MD5 hash is correct, probably Updatepack has been corrupted while archived or similar
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
Hi...
My Setup in NLite:
OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_NLD
But Also 2 Addons from the:
OnePiece_Remove_AddOn_For_WinXP_UP_4BECBC567126B8AB06907C8A1245BAE3
1:OnePiece_Remove_BitLockerToGo_AddOn
2:OnePiece_Remove_BrowserChoice_AddOn
I think you know what I'll go to say.
Yep indeed,...I didn't correct the order of integration.
I just pick the files and start integration.
In NLite:
OnePiece_Remove_BitLockerToGo_AddOn
OnePiece_Remove_BrowserChoice_AddOn
OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_NLD
The first Call goes to BitLockerToGo_AddOn and then you get the missing OPMWXPUP.inf Error.
What I forgot was to move Windows_XP_Post-SP3_UpdatePack to the top.
Like this:
OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_NLD
OnePiece_Remove_BitLockerToGo_AddOn
OnePiece_Remove_BrowserChoice_AddOn
Now I didn't have the OPMWXPUP.inf Error!!!..
All works very nice....And a very compleet Pakket,..Cool^^
I did a successful install now with your UpDatePack.
Thank you very much again...
Grt ECLV
Thank you very much!!!!...yep it works like a charm^^nonno fabio wrote:Anyway, you should simply click on "No" when you are asked for:
I forgot to tell a part off the story. (my bad)nonno fabio wrote:About missing OPMWXPUP.inf file
My Setup in NLite:
OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_NLD
But Also 2 Addons from the:
OnePiece_Remove_AddOn_For_WinXP_UP_4BECBC567126B8AB06907C8A1245BAE3
1:OnePiece_Remove_BitLockerToGo_AddOn
2:OnePiece_Remove_BrowserChoice_AddOn
I think you know what I'll go to say.

Yep indeed,...I didn't correct the order of integration.
I just pick the files and start integration.
In NLite:
OnePiece_Remove_BitLockerToGo_AddOn
OnePiece_Remove_BrowserChoice_AddOn
OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_NLD
The first Call goes to BitLockerToGo_AddOn and then you get the missing OPMWXPUP.inf Error.
What I forgot was to move Windows_XP_Post-SP3_UpdatePack to the top.
Like this:
OnePiece_Windows_XP_Post-SP3_UpdatePack_v6.8.0_NLD
OnePiece_Remove_BitLockerToGo_AddOn
OnePiece_Remove_BrowserChoice_AddOn
Now I didn't have the OPMWXPUP.inf Error!!!..
All works very nice....And a very compleet Pakket,..Cool^^
I did a successful install now with your UpDatePack.
Thank you very much again...
Grt ECLV
Last edited by ECLV on Mon Jul 01, 2013 5:37 pm, edited 1 time in total.
- OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
Re: Onepiece XP Post-SP3 AIO Update Pack v6.9.0-20130612
Hi ECLV, nLite does not support Remove AddOn, Remove AddOn are valid only for RVMi
Ciao.nonno fabio wrote:[*]Or, again, you can remove them from XP source after UpdatePack integration. Simply extract one or more of the small RVM-only addons from this suite and run a single new RVM-i integration session for every one of them on your updated source : (updated 2010-05-13):
OnePiece Remove AddOn For WinXP UP
Update (13 May 2010)
Update (13 May 2010)
Update (13 May 2010)
Update (13 May 2010)
Update (13 May 2010)
Hash MD5 124CC161821584EB0E55F73DBDD8A0BC
Filesize: 15,4 KB (15837 byte)
NB
*"REMOVE" addons are RVMIntegrator-only!! the entries.ini removal values are not supported by Nlite.
**the file you download, OnePiece_Remove_AddOn_For_WinXP_UP*.cab, is the archived full suite of single addons: you must unpack it (or extract from it the addons you need) before use with RVMi.
*** Please note also that, due to a RVMi limitation, Removal Addons could break XP setup if integrated in the source at once in the same RVMi session: you must run your regular integration with Nlite or RVMi then, before making the .iso, one or more additional sessions of RVMi to finish off your source with the desired removal addon.
****OnePiece_Remove_Windows_Management_Framework_Core_AddOn.cab removes from setup CD all single WinMFC component (Powershell, PowershellISE & WinRM). So if you use it, you don't need to add these single component removers:
OnePiece_Remove_WinMFC(PowerShellv2)_AddOn.cab
OnePiece_Remove_WinMFC(PowerShellISE)_AddOn.cab
OnePiece_Remove_WinMFC(WinRM)_AddOn.cab
to your integration list
Let's recap! the right order is:
Run RVMi and integrate Update Pack - rerun RVMi and integrate first Removal addon - rerun RVMi and integrate second Removal addon - ... - rerun RVMi and integrate last Removal addon - rerun RVMi and integrate your preferred SW - make the .iso.[/list]
Aha Oke thank you for this Info.OnePiece Alb wrote:Hi ECLV, nLite does not support Remove AddOn, Remove AddOn are valid only for RVMi
Now you say,I did read it..But compleet forgot.
The test I run today was Only the Windows_XP_Post-SP3_UpdatePack...Very Compleet Pack..wow^^
So if I will remove some stuff I need to rollback to the RVMi..oke^^
I didn't use it about the Hardware popup by plugin a simple mouse..
Grt ECLV
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
After you've integrated UpdatePack, Remove Addons and all your remaining stuff using RVM Integrator, you can also run Nlite over your updated CD to apply its own tweaks and removals, but remember to use it only once and as the last thing to do before creating the .iso
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
new release (see changelog)
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead
- OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
perhaps not more than one case, after the http://voidseesaw.com/onepiece/ was closed today also One_Piece@outlook.com
said all this because as you already understand if the reason for the temporary closure of One_Piece@outlook.com were the AddOn then remains at RyanVM after reviewing\decide ect ect ect
Ciao a tutti.

I do not know, we hope that Outllook will give me more info about itYour account has been temporarily blocked
Someone may have used your account to send spam or perform other acts that violate the Microsoft Service Agreement
said all this because as you already understand if the reason for the temporary closure of One_Piece@outlook.com were the AddOn then remains at RyanVM after reviewing\decide ect ect ect
Ciao a tutti.
-
- Posts: 8
- Joined: Sat Mar 14, 2009 2:15 pm
-
- Posts: 8
- Joined: Sat Mar 14, 2009 2:15 pm
Here is the response I received:
Dear Sir/Madam,
Please see section 12 of the User Agreement:
"CPU Usage. User agrees that User shall not use excessive amounts of CPU processing on any of FatCow's servers. Any violation of this policy may result in corrective action by FatCow, including assessment of additional charges, disconnection or discontinuance of any and all Services, or termination of this Agreement, which actions may be taken in FatCow's sole and absolute discretion."
The large archive files in the "onepiece" directory of your account are creating too many requests to the server and utilizing heavy network/server resources, which are resulting in critical issues with the server pool. As a result, we were forced to suspend your site, in line with the user agreement described above, to protect services to our other customers.
In order to unsuspend it, you need to agree to take immediate action to reduce the CGI load resulting from your content. Typically, this would involve removing those files from the server, hosting them elsewhere, and embedding or linking to them from there in your account, as the resources required to support the download of extremely large files such as this are not compatible with our shared hosting environment.
If you are not able to do so, you should seek an alternative hosting provider, as it appears your site needs are no longer compatible with the service which we can provide. I am sorry for any resulting inconvenience.
Thank You,
Jim M.
Technical Support
- OnePiece Alb
- Posts: 525
- Joined: Sat Sep 01, 2007 7:01 pm
- Location: Albania
- Contact:
-
- Posts: 8
- Joined: Tue May 03, 2011 8:48 pm
- Location: Belfast
Hi
Hello People
I decided to make XP 64 my main OS again
Anyway if I integrate this pack with nlite or ryans integrator, I get an error at the start of GUI setup..
I am using WinsetupfromUSB excellent utility to install from USB. Could this be fixed or am I doing something wrong ? It works fine via cd.
nlite gives a GLOBALROOT error at the very start of GUI.
Jonny
I decided to make XP 64 my main OS again

Anyway if I integrate this pack with nlite or ryans integrator, I get an error at the start of GUI setup..
I am using WinsetupfromUSB excellent utility to install from USB. Could this be fixed or am I doing something wrong ? It works fine via cd.
nlite gives a GLOBALROOT error at the very start of GUI.
Jonny
I don't know if this has anything to do with your USB problem, but I would have thought you might should have used the XP x64 pack rather than this one, since you say you are using XP 64 now.
Cheers and Regards
Cheers and Regards
-
- Posts: 8
- Joined: Tue May 03, 2011 8:48 pm
- Location: Belfast
-
- Posts: 3
- Joined: Sat Jan 24, 2009 8:08 pm
Hi nonno fabio!
Now the http://voidseesaw.com/onepiece/ has suspended, where can I get the contents of Hotfix List and Changelog?
Now the http://voidseesaw.com/onepiece/ has suspended, where can I get the contents of Hotfix List and Changelog?
- nonno fabio
- Posts: 1627
- Joined: Mon Jun 06, 2005 10:36 am
- Location: Northern Italy
- Contact:
try here:
https://www.dropbox.com/s/p62imonplcrky ... gelog.html
https://www.dropbox.com/s/wl6186rivvvc7 ... xList.html
https://www.dropbox.com/s/p62imonplcrky ... gelog.html
https://www.dropbox.com/s/wl6186rivvvc7 ... xList.html
Don't ask for a different configuration of Onepiece's XP AIO Update Pack: use one of the existing vanilla XP UpdatePack with your preferred addons instead