Onepiece's EN-US Windows XP Post-SP3 All-in-One Update Pack
OnePiece_Windows_XP_Post-SP3_UpdatePack_v3.0.0_ENU.7z
http://www.adrive.com/public/689e338987cf5...a886ca9a28.html
http://www.gazup.com/KmK4C-onepiece_window...wnload-mirrors/
Hash MD5 93E3DA9AC3A64FE094C8531366407C85
Size: 114.7MB (120284739 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 and RVM Integrator 1.6.1 on a clean XP SP3 ENU source.

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 listing the one you don't like installed in a Winnt.sif file (see also here), under [components] section, with an "= off" by their side. Here's an example of a Winnt.sif [components] section disabling ALL the optional components of Onepiece's AIO Pack. List only those you want to disable.(updated 09-11-16):


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-11-16):

* ***OnePiece_Remove_Windows_Management_Framework_Core_AddOn.cab
http://www.adrive.com/public/01e635cad922d...35960b657c.html
http://www.gazup.com/jpA2m-onepiece_remove...ownload-mirrors
Hash MD5 F23FC9C1E6FA4D1DC9A771983F28BA19
Filesize: 1.30 KB (1340 bytes)

***OnePiece_Remove_WinMFC(PowerShellv2)_AddOn.cab
http://www.adrive.com/public/f9edf9f9af5d4...de5c8dcc4f.html
http://www.gazup.com/jPjoU-onepiece_remove...ownload-mirrors
Hash MD5 329771E9729818401CA43CFD11391B84
Filesize: 1.07 KB (1104 bytes)

***OnePiece_Remove_WinMFC(PowerShellISE)_AddOn.cab
http://www.adrive.com/public/ff3a5627ab434...402cc58a12.html
http://www.gazup.com/B6CRT-onepiece_remove...ownload-mirrors
Hash MD5 851E7AADD6A2FE9B9002A3E08B62DBBC
Filesize: 757 Bytes (757 bytes)

***OnePiece_Remove_WinMFC(WinRM)_AddOn.cab
http://www.adrive.com/public/3ea673bd0d5d9...0fd3c84154.html
http://www.gazup.com/UOIlk-onepiece_remove...ownload-mirrors
Hash MD5 0B37989D379A54B982D267B84C827431
Filesize: 859 Bytes (859 bytes)

OnePiece_Remove_Windows_Search_AddOn.cab
http://www.adrive.com/public/0a2f6647295d8...a482367658.html
http://www.gazup.com/FTTCj-onepiece_remove...ownload-mirrors
Hash MD5 0435817738577CE445D4AB33DDF7C8EB
Filesize: 1.08 KB (1106 bytes)

OnePiece_Disable_WGAN_AddOn.cab
http://www.adrive.com/public/cfc64366eadbf...a2a2b802f7.html
http://www.gazup.com/a1Q6I-onepiece_disabl...ownload-mirrors
Hash MD5 4F1A1A367AFDDD6B8248FFC7BC27D4A3
Filesize: 650 bytes (650 Bytes)

OnePiece_Remove_BitLockerToGo_AddOn.cab
http://www.adrive.com/public/831844d5b7ddb...f9e5378bb0.html
http://www.gazup.com/wTlgz-onepiece_remove...ownload-mirrors
Hash MD5 E28E395E27C70A5DCECF57E383AE213E
Filesize: 875 Bytes (875 bytes)

OnePiece_Remove_DirectX_Post-SP3_AddOn.cab
http://www.adrive.com/public/e304a7645fce2...3d326f3b58.html
http://www.gazup.com/cmoQS-onepiece_remove...ownload-mirrors
Hash MD5 71553EF8AD793B400AA57213789A6E31
Filesize: 1.23 KB (1262 bytes)

OnePiece_Remove_IMAPI2_AddOn.cab
http://www.adrive.com/public/bb08cd2d97793...79b2811339.html
http://www.gazup.com/0R3Bv-onepiece_remove...ownload-mirrors
Hash MD5 7B23FEAE6E1A6DA2A62AA55F7AFDB8E5
Filesize: 747 Bytes (747 bytes)

OnePiece_Remove_MDX_AddOn.cab
http://www.adrive.com/public/4dc3b8b04bc7e...443a5c8a4c.html
http://www.gazup.com/UDowJ-onepiece_remove...ownload-mirrors
Hash MD5 504C56EB45A05C277C359BDE021DB430
Filesize: 812 Bytes (812 bytes)

OnePiece_Remove_Microsoft_Update_AddOn.cab
http://www.adrive.com/public/556c4f05c9171...3c10d8d622.html
http://www.gazup.com/I0xAE-onepiece_remove...ownload-mirrors
Hash MD5 CC4C980CDCAF8BA82134471311A2F15C
Filesize: 766 Bytes (766 bytes)

OnePiece_Remove_MSXML4_AddOn.cab
http://www.adrive.com/public/39947495953e8...79e224f1a3.html
http://www.gazup.com/Vioqb-onepiece_remove...ownload-mirrors
Hash MD5 B8D70DADA65C50CBCC1B07B7009445B7
Filesize: 769 Bytes (769 bytes)

OnePiece_Remove_NETFX1.1SP1_AddOn.cab
http://www.adrive.com/public/15c9395abae0e...4d4a24a4a7.html
http://www.gazup.com/4HO7i-onepiece_remove...ownload-mirrors
Hash MD5 F466118ACA84A251EC532D555B7CB8BE
Filesize: 690 Bytes (690 bytes)

OnePiece_Remove_Silverlight_AddOn.cab
http://www.adrive.com/public/e815af35f5bcc...0bd2d0e9ca.html
http://www.gazup.com/auUN5-onepiece_remove...ownload-mirrors
Hash MD5 6937B2F4133D8CB8B831F0245795CD01
Filesize: 929 Bytes (929 bytes)

OnePiece_Remove_Smart_Card_Driver_AddOn.cab
http://www.adrive.com/public/216e22a8dd394...8b6cf420b7.html
http://www.gazup.com/qW3HX-onepiece_remove...ownload-mirrors
Hash MD5 B9E48CE9EA246938D8C79B55DA728D30
Filesize: 771 Bytes (771 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, 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 first Removal addon - ... - rerun RVMi and integrate last Removal addon - rerun RVMi and integrate your preferred SW - make the .iso.
***OnePiece_Remove_Windows_Management_Framework_Core_AddOn.cab removes all single WinMFC components. So if you use it, you don't need to add:
OnePiece_Remove_WinMFC(PowerShellv2)_AddOn.cab
OnePiece_Remove_WinMFC(PowerShellISE)_AddOn.cab
OnePiece_Remove_WinMFC(WinRM)_AddOn.cab
to your integration list

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

@massoo: check the MD5 hash, seems as a corrupted download

Hi,

the md5 checksum of both the downloaded files matches that is "8139028A33F8D20ABE5904963CCD5AA2"

cadlib is in Nlite code: I don't think it's a Nlite issue because many people use it successfully.
Unfortunately we can't reproduce such an error. Have you already tried to reinstall Nlite?

Thanks for the info. The re-installation of nlite took out the error of cadlibs. However, I am encountering 3 more errors in the process of integrating the update pack

The first being error

on pressing yes, the second error comes up.

on pressing yes, the third error comes up.

To shed more light on this, I am using Windows XP SP3 and I have patched the installation media with the latest Driver Packs.

Is this reason for the above errors?

The problem is that the [GuiUnattended] section and also the [Components] are ignored with UnattendMode=ProvideDefault. If you use UnattendMode=FullUnattended the problem does not exist.

That's not quite true, click-click. The [GuiUnattended] section is not ignored. The answers it specifies are provided to the end user to change, if desired. Ref.chm does not specify that the [Components] section will be ignored, so I'm doubtful that it is though I haven't tried it.

Besides, FullUnattended presents its own problems:


I prefer DefaultHide. When all the answers are provided it's completely silent and unattended. And there are no potential problems with unsigned drivers.

Well, I tested this and these were my findings. I did forget to add an entry in the winnt.sif running fullunattended and yes - you get an error message, but setup then prompts you for the missing information. In my case it was the Admin password under the GuiUnattended section.

I could not get

[GuiUnattended]
TimeZone=110

[Components]
msnexplr=off
msmsgs=off

to work with some of the other UnattendMode= parameters. Although, I must say that I did not try DefaultHide which as you say might be a better choice. I will test this and post my findings.

Thanks

new release, finally.

A really good news for RVMi users: there's no more need for RVMi Compatibility addon, because pack .inf files are now shorter.

KB975591 has not been included in the pack because Microsoft has removed related KBs. However if somebody needs it, here is the addon:
OnePiece_KB975791_True_AddOn.cab
http://www.adrive.com/public/39d1a29b7996e...e977d95407.html
http://www.gazup.com/apflw-onepiece_kb9757...ownload-mirrors
Hash MD5 1251FC73BC94939B460D325B8F081622
Size:36.4K (37226 bytes)

Correct - both DefaultHide and FullUnattended will not ignore the [GuiUnattended] and [Components] sections. The interactive options such as ProvideDefault will.

Sorry for the OT