Jump to content
nonno fabio

Onepiece XP Post-SP3 AIO Update Pack En-US FINAL

Recommended Posts

This link isn't good for you?

http://voidseesaw.com/onepiece/OnePiece_Windows_XP_Post-SP3_UpdatePack_v4.7.0_ENU_21DB19AA0B4F1E7F7F3ECE07DF0106EE.7z

Most of the users should download from one of faster links in first topic. Voidseesaw repository is intended for users with very slow connections which break frequently.

Unfortunately Onepiece is one of them and he can't upload in remote mode on Mediafire and Megaupload as he does with the other upload sites.

If anyone with a Mediafire/Megaupload premium account would like to upload UpdatePack there and then share the link, he is welcome

Share this post


Link to post
Share on other sites

i have already download the latest windows xp sp3 update.. but i have one problem.. when i add this add on to my retail version of WinXP Pro sp3 and try it to virtual machine... there is an error pop-up by adminstrator.. then after installing my desktop became windows classic theme and some services are limited by admininstator?.. what seems to be the problem?.. I'm such a newbie.. Help me please..

I'm Using Nlite to make my unattended or integrated Windows XP OS

I'm using Oracle VM Virtualbox Manager as my virtual machine..

My copy of Windows XP Professional Edition SP3 is a Retail version

Edited by DaRkSe7eN

Share this post


Link to post
Share on other sites

i have already download the latest windows xp sp3 update.. but i have one problem.. when i add this add on to my retail version of WinXP Pro sp3 and try it to virtual machine... there is an error pop-up by adminstrator.. then after installing my desktop became windows classic theme and some services are limited by admininstator?.. what seems to be the problem?.. I'm such a newbie.. Help me please..

I'm Using Nlite to make my unattended or integrated Windows XP OS

I'm using Oracle VM Virtualbox Manager as my virtual machine..

My copy of Windows XP Professional Edition SP3 is a Retail version

Some settings in Nlite could have "damaged" your XP source during integration.

Retry with RVM Integrator 1.6.1 b2.1 instead and a clean XP CD and test the result in Virtualbox again

Edited by nonno fabio

Share this post


Link to post
Share on other sites

Some settings in Nlite could have "damaged" your XP source during integration.

Retry with RVM Integrator 1.6.1 b2.1 instead and a clean XP CD and test the result in Virtualbox again

The problem still occurs..

the error is all about grpconv.exe.. "the error states windows cannot access specified device, path, or file, you may not appropriate permisions to access the item"..

Share this post


Link to post
Share on other sites

grpconv.exe is not touched by XP UpdatePack so the latter can't be the cause of your issue.

Make sure that the XP CD you're using as a source is positively untouched. If needed, redownload SP3 and slipstream directly in your original CD. Then integrate UpdatePack and test in a VM.

Share this post


Link to post
Share on other sites

grpconv.exe is not touched by XP UpdatePack so the latter can't be the cause of your issue.

Make sure that the XP CD you're using as a source is positively untouched. If needed, redownload SP3 and slipstream directly in your original CD. Then integrate UpdatePack and test in a VM.

my windows xp pro sp3 is untouched 2007 retail version.. .. i have already tested it w/o addons and it works fine..

Share this post


Link to post
Share on other sites

hmm.. Where can I download update KB970159 User-Mode Driver Framework version 1.9 update for Czech Windows XP? I can't find it on micrsoft pages...

Edited by ArMinO

Share this post


Link to post
Share on other sites

hmm.. Where can I download update KB970159 User-Mode Driver Framework version 1.9 update for Czech Windows XP? I can't find it on micrsoft pages...

Here you go:

http://www.ryanvm.net/forum/viewtopic.php?p=115445#115445 

Share this post


Link to post
Share on other sites

I'm having problem with the latest update (4.8.0).. please see below..

0:33:41 - CabLite.dll::CabFile reports failure

20:34:16 - CabLite.dll::CabFileAsync reports failure [code=00000004]

20:34:28 - CabLite.dll::CabFile reports failure [code=00000004]

20:34:29 - CabLite.dll::CabFile reports failure [code=00000004]

20:34:31 - CabLite.dll::CabFile reports failure [code=00000004]

20:34:44 - CabLite.dll::CabFileAsync reports failure [code=00000004]

20:35:12 - CabLite.dll::CabFileAsync reports failure [code=00000004]

20:35:58 - CabLite.dll::CabFileAsync reports failure [code=00000004]

20:36:25 - CabLite.dll::CabFile reports failure [code=00000004]

20:36:28 - CabLite.dll::CabFile reports failure [code=00000004]

20:36:46 - CabLite.dll::CabFileAsync reports failure [code=00000004]

20:36:59 - CabLite.dll::CabFile reports failure [code=00000004]

20:38:16 - CabLite.dll::CabFile reports failure [code=00000004]

20:38:24 - CabLite.dll::CabFile reports failure [code=00000004]

20:38:42 - CabLite.dll::CabFile reports failure [code=00000004]

20:39:13 - CabLite.dll::CabFile reports failure [code=00000004]

20:39:42 - CabLite.dll::CabFile reports failure [code=00000004]

20:39:48 - CabLite.dll::CabFile reports failure [code=00000004]

20:39:53 - CabLite.dll::CabFileAsync reports failure [code=00000004]

20:41:36 - Processing new .CAT files found in SVCPACK

20:41:52 - CabLite.dll::CabFile reports failure [code=00000004]

20:42:00 -

20:42:00 - Shifting Stuff Around

20:42:46 - CabLite.dll::CabFile reports failure [code=00000004]

20:42:59 - CabLite.dll::CabFile reports failure [code=00000004]

20:44:45 - CabLite.dll::CabFile reports failure [code=00000004]

20:45:04 - CabLite.dll::CabFileAsync reports failure [code=00000004]

20:45:26 - CabLite.dll::CabFile reports failure [code=00000004]

20:45:43 - CabLite.dll::CabFile reports failure [code=00000004]

Share this post


Link to post
Share on other sites

Hi there,

When I edit the [Components] section of winnt.sif, the dot NET packages still install!

Mine looks like this:

....

[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

....

But when I check my fresh installation using asoft.be's dot net checker, I am still showing 1.1, 2.0, 3.0 3.5 and 4.0 as installed!

Any clue as to why they are not installing as expected?

The reason I want to exclude the dot NET packages is because all my CD's customized using OnePiece's update packs REFUSE to install any new dot NET updates through Microsoft Update. It only works if I uninstall 3.5 and then re-install it. However, by then, my fresh install already feels like it's been around for 6 months and not wisely handled.

Any and all help will be appreciated!

Thanks!

Share this post


Link to post
Share on other sites

The reason I want to exclude the dot NET packages is because all my CD's customized using OnePiece's update packs REFUSE to install any new dot NET updates through Microsoft Update. It only works if I uninstall 3.5 and then re-install it

Not True.

dotnet True AddOn have never had problems, I would say that true addon is more Secure than the original setup, about the problems that can give after installation or during repair or during remove

dotnet True AddOn does not need to remove them and reinstall them?, and success only one time when we used the QFE update mod, through no fault of the addon but because of the dotnet update themselves, which are install problems

more than once, which everyone knows already, after the release of dotnet4, the system now has two services CLR, only v4... and activated, during installation of the update to dotnet35 came out of problems, since the update called the CLR v2... Microsoft to put us almost 2-3 months to repair that thing (now also dotnet2, use files v4...), so dotnet True AddOn not centered with this story

and last time with v4.8.0 update packs that was not really a bug but a accident during the update of netfx20.inf, and problem and solved immediately, no need to reinstall dotnet hmmmmm

however, sometimes brings out dotnet setup problems, for this reason, Microsoft itself released guides on how to remove them and reinstall them, this gives us to understand clearly dotnet can be damaged very easily, but in this case the dotnet True AddOn due to True Mod structure they are more Safer/Secure during update or remove them or repair them

sorry for my English, however when Nonno Fabio will enter online (for 10 days, will be occupancy, so it will not be online) and answer them in English more clear

Ciao.

Edited by OnePiece

Share this post


Link to post
Share on other sites

Got a question but I don't know if anyone can answer it......how can i remove adobe flash player from update pack 4.9.0? I noticed that flash player comes out with new version quite often and I want to add my own ini file for new version. Just can't figure out how to remove the old version in update pack. Any help and I would be greatful. Thanks

Edited by Cerberus

Share this post


Link to post
Share on other sites

could not be removed (only update), because it is a default component of Windows XP CD

however Update Pack always includes the latest flash player

Update Flash Player

need to copy these files

%SystemRoot%\System32\Macromed\Flash\Flash%Version%.ocx

%SystemRoot%\System32\Macromed\Flash\FlashUtil%Version%_ActiveX.exe

%SystemRoot%\System32\Macromed\Flash\FlashUtil%Version%_ActiveX.dll

%SystemRoot%\System32\FlashPlayerCPLApp.cpl

rename them

Flash%Version%.ocx in flash.ocx

FlashUtil%Version%_ActiveX.exe in FlashUAX.exe

FlashUtil%Version%_ActiveX.dll in FlashUAX.dll

FlashPlayerCPLApp.cpl in FlashUAX.cpl

Cabtool http://www.wincert.n...ic/7702-dxtool/

replace the files on CD

flash.oc_

FlashUAX.ex_

FlashUAX.dl_

FlashUAX.cp_

extract with the cabtool swflash.in_

Replace inside swflash.inf, every %Old Version% with %Version% (example every 10t with 10v)

in [strings]

Replace VersionNumber = "Old verison" with New version

replace on CD swflash.in_ with new swflash.in_ (created with cabtool)

sorry for my English

Ciao.

Edited by OnePiece

Share this post


Link to post
Share on other sites

Hi. Again, firstly, thanks for the great work.

I have a few questions regarding the removal/omitting of three pieces of software:

I wish it would be possible to leave out the Malicious Software Removal Tool as it is about 50 MiB in size. Would repackaging the archive without that executable break integration or interrupt installation ?

I would also like to know whether version 2 of the .NET Framework can be removed and how, or why if not (is it part of the netfx3/3.5 and gets automatically removed along with it?).

Finally, how much overhead do you estimate Silverlight 4 adds to the windows setup source ? I mean how much less will the size of the windows installation source be after removal of Silverlight ? Your stand-alone Silverlight 4 add-on cab is only 7 MiB.

Don't spend too much time if it's too much trouble, it's nothing pressing. Thanks

Edited by brunetu

Share this post


Link to post
Share on other sites

I mean how much less will the size of the windows installation source be after removal of Silverlight ?

hi

is you problem to make an Installations CD which fits on a normal 700MB CD?

If so ,then ask and we can help you to show you how you can make one with most of these features included.

Share this post


Link to post
Share on other sites

I have a few questions regarding the removal/omitting of three pieces of software:

I wish it would be possible to leave out the Malicious Software Removal Tool as it is about 50 MiB in size. Would repackaging the archive without that executable break integration or interrupt installation ?

I would also like to know whether version 2 of the .NET Framework can be removed and how, or why if not (is it part of the netfx3/3.5 and gets automatically removed along with it?).

...

about first question, you can remove mrt.exe from the pack and and its references from entries.ini file then remove KB890830.AddReg from OPMWXPUP.inf file.

If you have experience with addon creation you can alternatively put together a specific remove addon with an entries.ini file like this:

Entries_RMRT.ini

 ;by OnePiece
;#######################################################################################################
;This section contains version information to nLite & RyanVM Integrator Entries_RMRT.ini
;# a huge thanks to all Italian guys (in particular and special thanks to Nonno Fabio)
;# Huge thanks to all guys of WinCert Forum and Eng2ITA Forum and RyanVM Forum
;# This file contains a list of all necessary entries to add in the various installation
;# files of Windows for the integration of OnePiece Windows_XP Post-SP3 UpdatePack AddOn.
;#######################################################################################################

;This section contains version info for nLite & RVM_Integrator
[general]
builddate=2010/12/24
description=OnePiece Windows XP Post-SP3 UpdatePack
language=ALL
title=OnePiece Windows XP Post-SP3 UpdatePack
version=1.0
website=http://voidseesaw.com/onepiece/
Windows=XP

;This section allows you to edit things that normally would not be possible to edit.
[ExtraFileEdits]
OPMWXPUP.inf|[KB890830.AddReg]|[KB890830.AddReg.Disable]|1

;Removes files from i386 which are no longer necessary
[obsolete_files]
[b]MRT[/b].exe

.net 2.0 is part of net 3.0/3.5. .net 2.0 doesn't require 3.0 or 3.5 to work but 3.5 requires 3.0 and 2.0 and 3.0 requires 2.0. And Onepiece's XP Update Pack itself requires .net 2.0.

So you can remove from OPUP .net 3.5 (or .net 3.5 and .net 3.0) but not .net 2.0

Edited by nonno fabio

Share this post


Link to post
Share on other sites

Hi!

I'm looking for file WINNT.SIF, but i can't find it - its not in the file... I want to disable installation some of the components.

BTW: nice pack!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By nonno fabio
      Onepiece's Windows XP Post-SP3 All-in-One QFE/LDR International Update Packs
      Start from here: Onepiece XP Post-SP3 AIO En-US Update Pack FINAL
      Made with DXUPAC! only DotNet LangPacks are not included (as they're useless) but if you want them too, integrate OnePiece_NetFxLangPack_SvcPack_AddOn_%Lang%.cab (download it from one of Onepiece's Files Repositories) after UpdatePack.
      How to: update the included Adobe Flash Player ActiveX





       
       
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL ARA - (Arabic)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 E9A0DE9CD1651C8EECF38AAF83721F3D
      Filesize: 201.55 MB (211337537 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL CHS - (Chinese Simplified)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 C507D6C2DC13EF6B60C6E9232C3C07D0
      Filesize: 207.08 MB (217138569 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL CHT - (Chinese Traditional)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 E2F2120C5F7B37A58AAEDB960800DC5C
      Filesize: 206.78 MB (216824677 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL CSY - (Czech)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 483859A994C117FFE1DE0D21B6867875
      Filesize: 207.18 MB (217247600 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL DAN - (Danish)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 9BB0241FB362EDA233E6E651FAF566DB
      Filesize: 206.66 MB (216696247 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL DEU - (German)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 8C4CB679F6BF9DEC8B957B6946D1F8E8
      Filesize: 207.44 MB (217518497 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL ELL - (Greek)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 68FA0EDF3EB5CCC81D2AA04ACEC48740
      Filesize: 207.09 MB (217153266 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL ENU - (English)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 7A2AC7C5DD72BB4BC0C18D677A8B8FB1
      Filesize: 206.18 MB (216198876 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL ESN - (Spanish)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 2E18AC3368D981EDEFE4F5A23A513501
      Filesize: 207.38 MB (217449516 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL FIN - (Finnish)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 2842D2C0D147AB7298A3FE19250766FA
      Filesize: 206.57 MB (216606818 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL FRA - (French)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 0782DE5A7D8F35FF21B5D21E23E59883
      Filesize: 207.48 MB (217559512 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL HEB - (Hebrew)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 1AAD9BD36A7DE743F0BE28AA256CE645
      Filesize: 201.14 MB (210914146 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL HUN - (Hungarian)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 E5CE1E19943730A0571DE21D477B3312
      Filesize: 207.19 MB (217254814 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL ITA - (Italiano)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 1065BBC91E197A83BB1182D6707CDDB5
      Filesize: 207.07 MB (217133052 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL JPN - (Japanese)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 AB07349C6226432744BAB6D8CCEE1228
      Filesize: 207.92 MB (218019895 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL KOR - (Korean)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 717B45BB67C883C3CC40AB696656CF6B
      Filesize: 207.46 MB (217540564 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL NLD - (Dutch)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 AFE345F0944970DAE4A2002C775896A5
      Filesize: 207.05 MB (217111160 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL NOR - (Norwegian)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 846060F0CFFE251EE6390FC69A40906C
      Filesize: 206.61 MB (216641910 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL PLK - (Polish)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 86D0924381CEAFCBE79E2830A13A071F
      Filesize: 207.24 MB (217311638 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL PTB - (Brazilian)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 40E5130FF80C77FF559563ADF22DEE78
      Filesize: 207.29 MB (217360212 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL PTG - (Portuguese)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 563C6F2B29397C59E04F6A457EF0E6C3
      Filesize: 207.12 MB (217186283 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL RUS - (Russian)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 237F2879AC6D6920495915F5EA62938D
      Filesize: 207.59 MB (217670355 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL SVE - (Swedish)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 4B76CD47C6F8561D255AE763E0A40258
      Filesize: 206.94 MB (216994255 bytes)  
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL TRK - (Turkish)
      Update (22 June 2017)
      Update (22 June 2017)
      Hash MD5 3ECFE702D78183F8AFFF90723C28D644
      Filesize: 207.06 MB (217113805 bytes)
       
       
    • By OnePiece
      OnePiece Windows XP Post-SP3 Update Pack è una raccolta di aggiornamenti integrabili direttamente sul cd di Windows XP SP3. A differenza di AutoPatcher che esegue gli aggiornamenti su un sistema già installato, questo pack serve a creare un CD di Windows XP SP4 completo, che non contiene però nessun tipo di tweak o miglioramento. Il vantaggio principale rispetto ad AutoPatcher è che se viene installato Windows da un CD che abbia il OnePiece Pack integrato dopo non è necessaria l'esecuzione di AP, perché i file che si vanno ad aggiornare con le patch sono già aggiornati.
      Cosa contiene - Hotfix List
      Attenzione: non applicare su precedenti Update Pack o AddOn, Ragazzi sia per quelli che usino nLite sia per quelli che usino RVMi, metterlo il pack da solo integrarlo, e dopo integrare o fare altri operazioni in quello cd, metterlo il pack inseme ai altri cose ce il rischio di sforzare tropo le applicazione come nLite e RVMi, e dopo che il rischio che forse anche sbagliano in qualche cosa, cosi il consiglio e sempre essere prudenti e metterli le cose in cd uno a uno, cosi siete sicuri 1000% che tutto andrà ok
      OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL ITA
      Aggiornato (22 Giugno 2017)
      Aggiornato (22 Giugno 2017)
      Aggiornato (22 Giugno 2017)
      Hash MD5 1065BBC91E197A83BB1182D6707CDDB5
      Filesize: 207.07 MB (217133052 bytes)  
      Ragazzi e tutto ok 10000% usare sia nLite sia RVMi per integrare Update Pack, io preferisco raccomandare sempre RVMi, perché RVMi non tocca mai nessun altro file in cd, cosi Integrazione non fallisce (o non fa uscire mai problemi ect ect) mai ect ect, cosi mi tocca rispondere piu meno ai segnalazioni che fanno tutti utenti al riguardo, come detto nLite e ok 10000%, milioni e milioni di utenti lo hanno usato per anni e anni e la usano ancora oggi ehhhhh (nLite va come un treno ), ma nLite a abitudine toccare a volte anche altri file che non hanno che fare con il Update Pack o il AddOn che stai integrando di più a moltissime opzioni, cosi utenti che non hanno molta esperienza al riguardo (eseguendo molte cose in nLite, oppure usando il nLite in extremis, oppure usando nLite in modo sbagliato) potranno danneggiare Windows XP Setup Files (che sono dentro il CD), e dopo non risecano capire dove hanno sbagliato ect ect dopo segnalano come problematico Update Pack o il AddOn ect ect, appunto per evitare questo io consiglio che e meglio usare RVMi per integrare Update Pack, testare se e tutto ok ect ect, e dopo chi vole fare altro andare avanti con nLite ect ect
      Ragazzi un ringrazio speciale va a forum http://thehotfixshare.net da dove o presso tutti questi hotfix, davvero direi straordinario il lavoro di quelli ragazzi li.
      Changelog
      Qui potete trovare tutto, anche le release precedenti:

×
×
  • Create New...