Remove Net Framework 4 from Onepiece XP Post-SP3 AIO Update

[centi50]

Please can anyone tell me how to remove Net framework 4 and the new windows search thing from Onepiece Update pack v3.9.0-100713. I am using Nlite for making my Xp updated CD.

Pleaese i'll appreciate much if given step by step Instruction

Thanking all of you in Advance

[nonno fabio]

Optional components added in your XP source by Onepiece's AIO UpdatePack can be easily:

• uninstalled (and reinstalled) in a running system
• disabled (not installed with XP but keeped in your source for future installations)
• totally removed from your source

LIVE UNINSTALL

you can easily uninstall some of them from Windows Components Wizard after windows setup (a clean XP SP3 source is needed). "Clean" in this case means "with neither AIO UpdatePack nor IE7-8 integrated".
Then you can use a Run window to totally delete the components from your live system, typing this command

Code: Select all

rundll32.exe advpack.dll,LaunchINFSection OPMWXPUP.inf,%Optional Components NAME%.CleanUp

Other supported switches are HIDE (removes the component from Windows Component Wizard list) and SHOW (shows the component in Windows Component Wizard list):
http://img202.imageshack.us/img202/1386/cattura3.png
http://img8.imageshack.us/img8/1720/cattura4.png
http://img44.imageshack.us/img44/5121/cattura5.png

DISABLING

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 (don't remove netfx2.0). List only those you want to disable.(updated 09-11-16):

Code: Select all

[Components]
WinRM = off
PowerShell = off
PowerShellISE = off
MicrosoftUpdate = off
Silverlight = off
DirectX = off
MDX = off
MSXML4 = off
WDSearch = off
IMAPI2 = off
ICCDSCD = off
WgaNotify = off
WRMC = off
BitLockerToGo = off
BrowserChoice = off
netfx11 = off
netfx30 = off
netfx35 = off
netfx40 = off

REMOVAL

Or, again, you can remove them from XP source after UpdatePack integration: simply run a new RVM-i integration session on your updated source and add one or more of the small RVM-only addons that you'll have previously extracted from this suite: (updated 2010-05-13):

Onepiece Remove Addons Pack
OnePiece_Remove_AddOn_For_WinXP_UP.cab
http://www.adrive.com/public/dfc4f2a905 ... d9e18.html
http://ifile.it/5vhrqby/OnePiece_Remove ... nXP_UP.cab
http://hotfile.com/dl/42600346/883b9ae/ ... P.cab.html
http://www.uploadjockey.com/download/59 ... nXP_UP.cab
http://www.klurk.com/files/0J9SUIVA/One ... nXP_UP.cab
Hash MD5 124CC161821584EB0E55F73DBDD8A0BC
Size: 15.4 KB (15837 byte

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.
***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.

[centi50]

Thank you Nonno Fabio for your reply.

What i understand from your reply is that there is only two way of removing components from the updated CD

1.Using live uninstall and
2.Using RVM-i with the removal addon

So there is no way to remove them using nlite during integration process

am i right?

[TheMAN]

correct
nlite does not have the ability to handle the "remove" entries in the script

if you must use nlite, then do all the stuff that you want with it first, then run the remove packs through rvm before burning

[centi50]

correct
nlite does not have the ability to handle the "remove" entries in the script

if you must use nlite, then do all the stuff that you want with it first, then run the remove packs through rvm before burning

Thank you TheMan for your reply,

But i think when using RVM at http://integrator.siginetsoftware.com/i ... nual&start it says under A few notes before you start:
-Do not do an integration over a previously-nLited installation source!

Right?

[Kelsenellenelvian]

That really only applies when you are doing component removal in nLite.

[TheMAN]

in otherwords, nothing to worry about as far as what you are trying to do