Onepiece's EN-US Windows XP Post-SP3 All-in-One Update Pack

OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.9.0_ENU.7z
http://www.adrive.com/public/50db8b22f3b025b9d43c897d728d215cec8fb3c505d7397499f2fba3cdea3534.html
http://hotfile.com/dl/14886963/a6cd464/OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.9.0_ENU.7z.html
http://www.filefactory.com/file/a0hea4f/n/OnePiece_Windows_XP_Post-SP3_UpdatePack_v2_9_0_ENU_7z
http://www.simpleupload.net/download/469171/OnePiece-Windows-XP-Post-SP3-UpdatePack-v2.9.0-ENU.7z.html
http://www.turboupload.com/e7eanm86nh3s/OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.9.0_ENU.7z.html
http://speedshare.org/download.php?id=0FAC0F8F11
http://up-file.com/download/5269.59ada8a87d0fbc6f4487481595
Hash MD5 8139028A33F8D20ABE5904963CCD5AA2
Size: 112.8 MB (118278069 bytes)

This XP post-SP3 All-in-One Update Pack differs from Ryan's One, which is more customizable to your needs, as it includes by default more stuff like IE8, DX updates, .NET 1.1 or WMP11 for an easier integration, along with official and nearly all request-only hotfixes (RyanVM's Update Pack is more selective with request-only hotfixes, which is fine): all in a few MBs.

Onepiece's XP Update Pack can be used along with Nite 1.4.9.1 on a clean XP SP3 ENU source.
It can be used also with RVM Integrator 1.6.1 but you must run a second integration session on your updated source, before closing the .iso, adding this small compatibility addon which works around a RVM Integrator limitation when it handles big packs/addons at one time:
Repair_OP_XP_Post-SP3_UP_AddOn_ENU_RVMi_Only.7z
http://www.adrive.com/public/58f1fb09324bb...67e3628a72.html
http://www.uploadjockey.com/download/91822...NU.RVMi.Only.7z
Hash MD5 38DD9FD4750D67AEF20C703840B288F7
Size: 3.3 Kb (3411 bytes)

IE8 integration esthetic side effects (not UpdatePack bugs):
* setuperr.log will point out harmless error messages about some IE files like imgutil.dll, inetcpl.cpl, inseng.dll, mshtml.dll, msrating.dll, pngfilt.dll, occache.dll, webcheck.dll (caused by the patched Syssetup.dll used for integration and then restored with the original one). If you don't tolerate it you can integrate in addition this Onepiece Repair IE8 cosmetic problems addon
(Hash MD5 5C7AF8CA9F637C993F4AEEFFB63F39ED - Filesize: 1.28 Kb - updated 2008-03-27) which does nothing else than cleaning those false errors in your setuperr.log file.

You don't like any of the components included in OnePiece's XP Update Pack?
If you prefer a different configuration of Onepiece AIO Update Pack I suggest you to use RyanVM Update Pack with your preferred addons and you'll get your own XP disc without the need to remove anything.
However you can easily uninstall some of them from Windows Components Wizard after windows setup. Alternatively, you can also disable their installation adding them in a Winnt.sif file as follows:


Or, again, you can disable their integration inside XP source adding in your integration list after the Update Pack one or more of these small addons: (updated 2009-04-18):

Disable WGAN AddOn
http://www.adrive.com/public/f52daf48287a7...a92ef65162.html
http://ifile.it/v6t12l5
Hash MD5 7B3B9AA34FF297746F9F7278E31D7ADA
Filesize: 652 bytes

* **Remove NETFX1.1 SP1 & DMX AddOn
http://www.adrive.com/public/0f8ac250113b0...6790e8d59d.html
Hash MD5 A3CDE32829C240539459E0AE8F9F60A4
Size: 960Bytes (960 bytes)

*Remove Microsoft Update AddOn
http://www.adrive.com/public/712bd2ecb9caa...d88e80986d.html
http://ifile.it/8jqbem3
Hash MD5 323FF7479D4A5A3AA268DF28252F2446
Filesize: 770 bytes

*Remove MSXML4 AddOn
http://www.adrive.com/public/f30ae81168cf8...cb6f9d5e0f.html
http://ifile.it/yxniczu
Hash MD5 DB34908F78D498DB18F4883749D98979
Filesize: 785 byte

*Remove Silverlight AddOn
http://www.adrive.com/public/767453ca29139...27e01022a0.html
Hash MD5 8A6875D4577BD223076AAB8E67E3387A
Size: 1 Kb (1029 bytes)

*Remove Smart Card Driver AddOn
http://www.adrive.com/public/f2a32eb99baff...ad5a2d4ea7.html
http://ifile.it/r2mwpjv
Hash MD5 D9E59273ECFE07B45326201FF81EBFD0
Filesize: 781 bytes

*Remove Windows Search AddOn
http://www.adrive.com/public/891563185d4fb...9a1c4eb4dc.html
http://ifile.it/sg1bzwk
Hash MD5 C4F7230E11C73CD76E03AB79A60AABA2
Filesize: 1.08 Kb

*Remove DirectX Post-SP3 AddOn
http://www.adrive.com/public/7f9b4eebcde20...0672361fa4.html
http://ifile.it/7ow8sa0
Hash MD5 49622254E51E34D07D8D9D1E23508E76
Filesize: 1.01 Kb

*Remove PowerShell AddOn
http://www.adrive.com/public/143f4d51423a7...a7fe8b0865.html
Hash MD5 FB3CE8C137D5117375C659063112BD4A
Size: 1.1 Kb (1095 bytes)

* **Remove_PowerShell_MUI_Pack_CHS_CHT_ESN_FRA_GER_AddOn.7z
http://www.adrive.com/public/72de49bb92705...cd20408aee.html
Hash MD5 CC53D043E295E34AD2272F908A9353C0
Size: 1.2 Kb (1273 bytes)

* **Remove_PowerShell_MUI_Pack_ITA_JPN_KOR_PTB_RUS_AddOn.7z
http://www.adrive.com/public/f7c1c6aa3a842...834b1b72bcc.htm
Hash MD5 DC148C72FD7D2D65BC2A67258F54FC79
Size: 1.3 Kb (1290 bytes)

NB *"REMOVE" addons are RVMIntegrator-only!! the entries.ini removal values are not supported by Nlite.
** Please note also that, due to a RVMi limitation, .Net 1.1 and Powershell MUI 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.
Let's recap! If you want to use RVMi, the right order is:
Run RVMi and integrate Update Pack - rerun RVMi and integrate Compatibility Repair Addon - rerun RVMi and integrate first Removal addon - ... - rerun RVMi and integrate last Removal addon - rerun RVMi and integrate your preferred SW - make the .iso

All credits are in entries.ini file: however many, many thanks especially to RyanVM, Nuhi, Siginet and Xable.

Thank you for sharing you work on MSFN.

you're welcome!

updated

Thanks. Just integrated the last pack with no probs. Will get this for my next build.

new release

thanks for the new release....just a heads up, you may want to eliminate the original dead link

done, thanks

Is the latest build v2.6.0 or v2.6.1? I saw v2.6.1 on some other forums.

Just wanted to let you know that the link states "The file you are trying to access is no longer available publicly."

Link is fixed now. Sorry for the delay.

new release

new release

new release

Thanks for update.

I have a problem with this post sp3 update, I think. When I try to install Office 2003 the install process stop without any message. This error occur in VMWare environment. Any suggestions or solving tip?

you've tried the Office setup with default settings?

i have a question, i have xp pro sp2 oem and i slipstream with sp3 from microsoft. how can i know what hotfixes should i integrate with my xp till last update august 2009? if i use onepiece aio update pack 2.7.0 should it cover all update after sp3 till latest update from microsoft?

if i use onepiece aio update pack, should i add onepiece wm11 addon, one piece ie8 addon and directx add on?

i still dont understand what you said about adding winnt.sif

[Components]
WgaNotify=Off
MicrosoftUpdate=Off
Silverlight=Off
PowerShell=Off
DirectX=Off
MDX=Off
MSXML4=Off
WDSearch=Off
WRMC=Off
IMAPI2=Off
ICCDSCD=Off

can u explain more detail?

thanks a lot

@nonno fabio

Yes, I've tried with default settings and many other combinations. All with same result: stoppping install process.

1. If you run WindowsUpdate on a freshly installed XP SP3 system, it will tell you what hotfixes you need. If you have integrated Onepiece XP post SP3 UpdatePack on the XP SP3 source you've installed on your PC, you have nearly all the hotfixes (security, optional, request-only) released till updatepack build date. WU will show you nothing

2. No, No, No. They are already included.

3. XP setup won't install the desired optional component if you add a line in your Winnt.sif with =off after the component name under [Components] section. For explanation about usage of Winnt.sif file see MSFN Unattended Guide.

@mlu
please retry with v2.7.1. Msi installer has been reverted to previous build, maybe the cause is that

@nonno fabio

Problem solved. Seems that was the problem. Thanks, you are doing a great job!

will this work for x64 windows ?

No, but this one will.

i've problem when slipstream using n-lite. i'm using fresh source xp pro sp3. i'm test on virtual box.
my add on :


1. vista boot screen not working, even i use OnePiece_Vista_RTM_Boot_Screen_v5.1.2600.5845_AddOn_ENU.7z
any solution?

2. themes can't loaded, why?

3. when i start windows update, it always stop and can't continue, why?

4. when i install program with access database [mdb] there is an error not valid database!

5. IE and Outlook Express shortcut always show internet properties when i click.

6. Kels_CPLBonus_v9.5_addon.rar also not working ...

thanks a lot

it's a tipical failed integration: an addon has "broken" the .inf file. You should retry a new integration on a fresh XP SP3 source, integrating every single addon one by one to identify the culprit.
In other words, run Nlite, add updatepack, build the iso, test it on a VM; add 1st addon on updated source, build a new iso, test on a VM; add 2nd addon... and so on.

updated

Thanks for the quick release !!

Thanks for carrying the torch. A few questions...

I was able to associate each one except "WRMC", what is it? If I wish to leave some of these enabled, should I remove the line, or use =On? Are any of them dependent on others being enabled (ie: does MDX depend on DirectX)?

WRMC=Windows Rights Management Client. You can find the descriptions inside the pack in .inf file.

You can simply remove the line related to the component you want to enable. Remember that using the winnt.sif way you can install in your system in a second time the disabled components using Windows Component Wizard and your updated XP CD.

No, there isn't any dependance. DirectX is already inside the default XP CD ("DirectX" means DirectX updates). I guess you can disable DirectX updates and keep DirectX for Managed Code ("MDX") enabled without any consequence.

updated (see changelog.txt)

Can you please point me to a reference where the above components are listed?

I looked at the ref and deploy files from the SP3 CD, but the dates on those files are all 2001 and don't show a lot of the components that you listed. Where did you find out what names can be used?

Thanks

You need to place them in your Winnt.sif file only those you want "off"; they're on as default

I understand that, but you must have come up with these names from somewhere. Are these names only applicable to your update pack?

Also to understand better, how does setup make the connection to the name being used so that it knows what not install?

Ciao,

UpdatePack adds these references in Sysoc.inf, which is always executed during Xp Setup. So when Winnt.sif file is readed, Xp Setup knows what to do, even if those names are only applicable to this update pack

Thans for the explanation. Makes more sense to me now. I still have a question though that maybe someone can help me with. I have tried the off flag with two components and both seem to be ignored and still get installed anyway. MSN Explorer and Windows Messenger

[Components]
msnexplr=off
msmsgs=off

Is the off flag dependent on another setting in the answer file for it work?

I sure would like to know how. I did find both of these names in the sysoc.inf file.

Thanks

Although the components you've listed are not in Mr. fabio's list, I share your predicament with regard to flags appearing to be ignored.

When setting some of the components to "Off" (WDSearch, PowerShell, etc.), they seem to still be installed regardless.

Thanks for responses in advance.

In reponse to myself, I have found a solution to this problem.

By adding the following line to your cmdlines.txt in your OEM preinstallation package:



So that your cmdlines.txt looks like this:



...the Components section in WINNT.SIF will be executed properly!

Hi,

I am trying to integrate My Windows XP patched with SP3 with the Onepiece's EN-US Windows XP Post-SP3 All-in-One Update Pack. I get the following error in n-lite 1.4.9.1



I downloaded the file OnePiece_Windows_XP_Post-SP3_UpdatePack_v2.9.0_ENU.7z from different locations and the result is same. Also I selected only this addon while integrating with Windows-XP-SP3 installation media. but the error is same.

How to resolve this?

Regards
Shann