Jump to content

Search the Community

Showing results for tags 'updatepack'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • General Discussion
    • Introduction
  • WinCert Member Projects
    • Win Toolkit
    • HeiDoc.net Projects
    • Windows Post-Install Wizard (WPI)
    • WPI, nLite and RVM Addons
    • DX WinNT6.x True Integrator
    • Switchless installers
    • XP Theme Source Patcher
    • OS Transformation Packs
    • Installer Repacks
  • WinCert.net International
    • WinCert.net Turkish
    • WinCert.net Italian
    • WinCert.net French
    • WinCert.net Spanish
    • WinCert.net Dutch
    • WinCert.net German
  • Microsoft Operating Systems and Software
    • Microsoft Windows
    • Microsoft Windows Server Family
    • Microsoft Office
    • Tips and Tricks
  • News, Support, Discussion
  • The Design Art Forum
  • Miscellaneous

Categories

  • Win Toolkit
    • WinKit Addons
  • nLite/RVMi Addons
  • Citrix
  • Unattended Setup Files
  • Various
  • Repacks

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL ENU Update (22 June 2017) Update (22 June 2017) Update (22 June 2017) Hash MD5 7A2AC7C5DD72BB4BC0C18D677A8B8FB1 Filesize: 206.18 MB (216198876 bytes) This XP post-SP3 All-in-One QFE/LDR Update Pack differs from RyanVM's/user_hidden's one as it includes by default more stuff like IE8, DX updates, all .NETs and 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 and integrated in native "true" mode. Onepiece's XP Update Pack can be used along with Nlite from v1.4.9.1 or RVM Integrator from v1.6.1 b2.1 on a clean (untouched) XP SP3 ENU source. From v3.5.1 XP post-SP3 AIO UpdatePack can be integrated in a XP MCE 2005 SP3 source. Please don't ask for inclusions or exclusions: if you like a different configuration use one of the existing vanilla XP UpdatePacks with your preferred addons and you'll get your own XP disc without the need to remove anything. However if you don't like all the additional stuff included in OnePiece's XP Update Pack, you can easily uninstall some of them from Windows Components Wizard after windows setup. Then you can use a Run window to totally delete the components from your live system, typing this command: rundll32.exe advpack.dll,LaunchINFSection OPMWXPUP.inf,%OptionalComponentsNAME%.CleanUp Other supported switches are HIDE (removes the component from Windows Component Wizard list) and SHOW (shows the component in Windows Component Wizard list): Alternatively, you can also disable their installation listing the one you don't like to install (but not .net 2.0!) in a Winnt.sif file (see also here), under [components] section, with an "= off" by their side. For example, if you want to disable installation of Windows Desktop Search you will add this string: [Components]...WDSearch = off... All the Winnt.sif optional components codes are shown below. List only those you want to disable! BitLockerToGo = BitLocker To Go ReaderBrowserChoice = Browser ChoiceDirectX = DirectX Post-SP3 UpdateICCDSCD = Windows Feature Pack for StorageIMAPI2 = Image Mastering APIMDX = DirectX Managed CodeMSXML4 = MSXML 4.0 SP3 Parser (KB2721691)MU = Microsoft UpdateNETFX30 = Microsoft .NET Framework 3.0 Service Pack 2NETFX35 = Microsoft .NET Framework 3.5 SP1NETFX40 = Microsoft .NET Framework 4PowerShell = Windows PowerShellPowerShellISE = Windows PowerShell ISESilverlight = Microsoft SilverlightWDSearch = Windows Desktop SearchWgaNotify = Windows Genuine Advantage NotificationsWinRM = Windows Remote Management (WS-Management)WRMC = Windows Rights Management ClientXP_EOS = Microsoft Windows XP End of Service Notification 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: OnePiece Remove AddOn Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Update (8 April 2014) Hash MD5 07C39C13FEC9099B603BC00C3B209234 Filesize: 19.8 KB (20303 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. ***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 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. Integration 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 Onepiece Repair IE8 cosmetic problems addon which does nothing else than cleaning those false errors in your setuperr.log file. Please note that in some rare configurations the integration of this "repair" addon could cause issues, so we don't suggest to use it. OnePiece Repair IE8 Cosmetic Problems AddOn Updated (March 27-2009) Hash MD5 5C7AF8CA9F637C993F4AEEFFB63F39ED Filesize: 1.28 Kb There's an incompatibility of new msi installer official release KB981669 with a single app of Windows Live suite, Photogallery. Microsoft hasn't fixed it yet so if you need that specific app you must revert to very old KB967756 using this addon by 5eraph. If you don't want to loose the new version, there's also a temporary workaround for working systems that allows you to install Photogallery in an updated XP What's inside Onepiece's XP Update Pack: Hotfixes List What's new in latest release: Changelog To update the included Adobe Flash Player ActiveX use Create OnePiece Adobe Flash Player True AddOn and integrate the resulting OnePiece_Adobe_Flash_Player_v%Version%_True_AddOn.cab after UpdatePack. As an example this is v20.0.0.228 True AddOn just created with Create OnePiece Adobe Flash Player True AddOn OnePiece Adobe Flash Player v26.0.0.131 True AddOn Update (22 June 2017) Update (22 June 2017) Update (22 June 2017) Hash MD5 69F5516C9CCDF0DB62B11450925B7E5D Filesize: 9.04 MB (9483969 bytes) You can also extract both the UpdatePack and the OnePiece_Adobe_Flash_Player_v%Version%_True_AddOn.cab, delete entries_Flash.ini file, copy/move newer Adobe Flash Player AddOn files inside UpdatePack, overwriting the older one and then archive UpdatePack again. How to update the DotNet True AddOn Complete mirrors, including prerelease and legacy versions, are available here: Localized XP Updatepack final releases (main languages):Onepiece International XP Post-SP3 AIO Update Packs 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. All credits are in entries.ini file: however many, many thanks especially to RyanVM, Nuhi, Siginet and Xable.
  2. 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:
  3. DXUPAC Update (2016) Update (2016) Update (2016) Update (2016) Update (2016) Video tutorial: how to create your localized Onepiece's UpdatePack (and IE, WMP11 or Silverlight Addons) with DXUPAC This tool allows you to create a localized UpdatePack or Addon, simply following these steps: Place in a folder (source folder) the complete source already updated with the latest Service Pack and exactly all the hotfix installers and additional components listed in Onepiece's AIO UpdatePack topics (for XP and 2003 UpdatePacks) or the setup file and all the eventually needed hotfix installers (for Addons). UpdatePack INTL Files or UpdatePack INTL Files you can find the needed hotfixes updated lists for the 24 main XP localizations.. If you are creating UpdatePacks, you need add in source folder the following addons: netfx 3.5 gdr addon netfx 4.0 gdr addon Starting from June release you must also add this addon in source folder in place of install_flash_player_ax.exe file, because Flash installer doesn't support anymore 7-Zip. Run DXUPAC.exe with the needed settings and the path of source folder. When finished, you get your own localized addon/pack in 7z format, WU-compliant. The only thing missing will be your localized .net 3.5/4 language packs . You can add them too using Svcpack addons you can build with another easy tool available here . You need only to place in same directory dotnetfx35langpack_x86**.exe and dotNetFx40LP_Full_x86**.exe files you'll get from Microsoft and run. Only for Unicode language XP users (like ARA, CHS, CHT, ELL, HEB, JPN, KOR, RUS): you 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. Trust me: creating an Onepiece's localized AIO UpdatePack need only a few clicks. So please don't ask for ready-to-use UpdatePacks, you can do it by yourself, we really got no time to rebuild 24 different updatepacks every month. Thank you for your comprehension. Universal Creator can also integrate Service Pack 3 inside XP MCE 2005. Follow these steps (some screen are from italian XP but they are easily comprehensible): Or After slipstreaming of Service Pack 3 in MCE sources, integration of Onepiece's XP postSP3 AIO UpdatePack is strongly suggested. When done, you can also add the XPMediaCenter specific hotfixes (by integrating them at T-13: here you can find a step-by-step guide, in italian but with screenshots) Thanks to Yumeyao for his suggestions. Please be tolerant if something is not enough clearly stated. It's more easier to run than explain how it works
×
×
  • Create New...