Jump to content
nonno fabio

[Tool] DX's Universal UpdatePack/Addon Creator

Recommended Posts

updated to fit latest XP/2k3 Onepiece's UpdatePacks.

When WindowsUpdate will be offline for XP, DXUPAC won't need to be updated anymore to adjust OPMWXPUP.inf (XP UpdatePack inf Setup) and OPW2K3UP.inf (2k3 UpdatePack inf Setup) to WU/MU requirements.

Share this post


Link to post
Share on other sites
 
 

I downloaded INTL, DEU and Embedded DEU, put all files in one folder and started DXUPAC. It works like many times before, but when it is compressing at last, it`s done after a few seconds and the result is an UDP at about 14mb. What am i doing wrong?

 

Upate-List:

directx_Jun2010_redist.exeEUupdate.EXEIE8-WindowsXP-KB2598845-x86-DEU.exeIE8-WindowsXP-KB2632503-x86-DEU.exeIE8-WindowsXP-KB2909210-x86-DEU.exeIE8-WindowsXP-KB2936068-x86-DEU.exeIE8-WindowsXP-KB2964358-x86-custom-DEU.exeIE8-WindowsXP-KB2976627-x86-embedded-DEU.exeIE8-WindowsXP-x86-DEU.exeIMAPI_XP_SRV2003_x86_DEU.exeKB961184.exeKB961742-v3-DEU.exeKB970401-x86-DEU.exeKB983234.cablangpack_de.exeLegitCheckControl.cabMSXML2SP6-KB887606-x86-DEU.exemsxml4-KB2758694-deu.exeMuCatalogWebControl.cabmucltui.cabmucltui_de.cabmuweb.cabOnePiece_Adobe_Flash_Player_v14.0.0.176_True_AddOn.cabOnePiece_Microsoft.NET_Framework_v1.1.4322.2503_True_AddOn.cabOnePiece_Microsoft.NET_Framework_v2.0.50727.3659_True_AddOn.cabOnePiece_Microsoft.NET_Framework_v3.2.30729.4058.3_True_AddOn.cabOnePiece_Microsoft.NET_Framework_v3.5.30729.4056.3_True_AddOn.cabOnePiece_Microsoft.NET_Framework_v3.5.30729.7056.3_QFE_Update_AddOn.7zOnePiece_Microsoft.NET_Framework_v4.0.30319.1023_True_AddOn.cabOnePiece_NetFxLangPack_SvcPack_AddOn_DEU.cabrootsupd.exervkroots.exeSilverlight.exeSmartCard_XP_x86_DEU.exeWindows-de-DE-KB974266.exeWindows-KB890830-V5.15.exeWindows-KB909520-v1.000-x86-DEU.exeWindowsMedia11-KB974905-x86-INTL.exeWindowsRightsManagementServicesSP2-KB979099-Client-x86-GER.exeWindowsSearch-KB940157-XP-x86-deu.exeWindowsServer2003.WindowsXP-KB963093-x86.exeWindowsUpdateAgent30-x86.exeWindowsXP-KB2115168-x86-DEU.exeWindowsXP-KB2124261-x86-DEU.exeWindowsXP-KB2229593-x86-DEU.exeWindowsXP-KB2264107-x86-DEU.exeWindowsXP-KB2270406-x86-DEU.exeWindowsXP-KB2290570-x86-DEU.exeWindowsXP-KB2296011-x86-DEU.exeWindowsXP-KB2345886-x86-DEU.exeWindowsXP-KB2347290-x86-DEU.exeWindowsXP-KB2387149-x86-DEU.exeWindowsXP-KB2393802-x86-DEU.exeWindowsXP-KB2419632-x86-DEU.exeWindowsXP-KB2423089-x86-DEU.exeWindowsXP-KB2443105-x86-DEU.exeWindowsXP-KB2454533-v2-x86-DEU.exeWindowsXP-KB2467659-x86-DEU.exeWindowsXP-KB2478960-x86-DEU.exeWindowsXP-KB2478971-x86-DEU.exeWindowsXP-KB2479943-x86-DEU.exeWindowsXP-KB2483185-x86-DEU.exeWindowsXP-KB2485663-x86-DEU.exeWindowsXP-KB2491683-x86-DEU.exeWindowsXP-KB2492386-x86-DEU.exeWindowsXP-KB2498072-x86-DEU.exeWindowsXP-KB2508429-x86-DEU.exeWindowsXP-KB2509553-x86-DEU.exeWindowsXP-KB2535512-x86-DEU.exeWindowsXP-KB2536276-v2-x86-DEU.exeWindowsXP-KB2544893-v2-x86-DEU.exeWindowsXP-KB2564958-X86-DEU.exeWindowsXP-KB2566454-x86-DEU.exeWindowsXP-KB2570947-x86-DEU.exeWindowsXP-KB2584146-x86-DEU.exeWindowsXP-KB2584577-x86-DEU.exeWindowsXP-KB2585542-x86-DEU.exeWindowsXP-KB2592799-x86-DEU.exeWindowsXP-KB2598479-x86-DEU.exeWindowsXP-KB2603381-x86-DEU.exeWindowsXP-KB2619339-x86-DEU.exeWindowsXP-KB2620712-x86-DEU.exeWindowsXP-KB2629462-x86-DEU.exeWindowsXP-KB2631813-x86-DEU.exeWindowsXP-KB2661637-x86-DEU.exeWindowsXP-KB2686509-x86-DEU.exeWindowsXP-KB2691442-x86-DEU.exeWindowsXP-KB2698365-x86-DEU.exeWindowsXP-KB2705219-v2-x86-DEU.exeWindowsXP-KB2712808-x86-DEU.exeWindowsXP-KB2723135-v2-x86-DEU.exeWindowsXP-KB2727528-x86-DEU.exeWindowsXP-KB2749655-x86-DEU.exeWindowsXP-KB2757638-x86-DEU.exeWindowsXP-KB2770660-x86-DEU.exeWindowsXP-KB2780091-x86-DEU.exeWindowsXP-KB2802968-x86-DEU.exeWindowsXP-KB2807986-x86-DEU.exeWindowsXP-KB2808679-x86-DEU.exeWindowsXP-KB2813347-v2-x86-DEU.exeWindowsXP-KB2820917-x86-DEU.exeWindowsXP-KB2828030-x86-DEU.exeWindowsXP-KB2832214-x86-DEU.exeWindowsXP-KB2834886-x86-DEU.exeWindowsXP-KB2836198-x86-DEU.exeWindowsXP-KB2847311-x86-DEU.exeWindowsXP-KB2850869-x86-DEU.exeWindowsXP-KB2859537-x86-DEU.exeWindowsXP-KB2862152-x86-DEU.exeWindowsXP-KB2862330-x86-DEU.exeWindowsXP-KB2862335-x86-DEU.exeWindowsXP-KB2864063-x86-DEU.exeWindowsXP-KB2868038-x86-DEU.exeWindowsXP-KB2868626-x86-DEU.exeWindowsXP-KB2876217-x86-DEU.exeWindowsXP-KB2876331-x86-DEU.exeWindowsXP-KB2878379-v2-x86-DEU.exeWindowsXP-KB2884256-x86-DEU.exeWindowsXP-KB2892075-x86-DEU.exeWindowsXP-KB2892734-x86-DEU.exeWindowsXP-KB2893294-x86-DEU.exeWindowsXP-KB2898715-x86-DEU.exeWindowsXP-KB2900986-x86-DEU.exeWindowsXP-KB2914368-x86-DEU.exeWindowsXP-KB2916036-x86-DEU.exeWindowsXP-KB2918614-x86-embedded-DEU.exeWindowsXP-KB2922229-x86-DEU.exeWindowsXP-KB2926765-x86-embedded-DEU.exeWindowsXP-KB2929729-x86-DEU.exeWindowsXP-KB2929961-x86-DEU.exeWindowsXP-KB2930275-x86-DEU.exeWindowsXP-KB2934207-x86-DEU.cabWindowsXP-KB2935092-x86-DEU.exeWindowsXP-KB2939576-x86-embedded-DEU.exeWindowsXP-KB2957503-x86-embedded-DEU.exeWindowsXP-KB2957509-x86-embedded-DEU.exeWindowsXP-KB2961072-x86-embedded-DEU.exeWindowsXP-KB2981580-x86-embedded-DEU.exeWindowsXP-KB2993651-x86-embedded-DEU.exeWindowsXP-KB817688-x86-DEU.exeWindowsXP-KB897571-x86-DEU.exeWindowsXP-KB898461-x86-DEU.exeWindowsXP-KB905474-DEU-x86.exeWindowsXP-KB915800-v4-x86.exeWindowsXP-KB916157-v6-x86-DEU.exeWindowsXP-KB922120-v6-x86-DEU.exeWindowsXP-KB927436-v2-x86-DEU.exeWindowsXP-KB932716-v2-x86-DEU.exeWindowsXP-KB934401-x86-DEU.exeWindowsXP-KB942288-v3-x86.exeWindowsXP-KB943232-v2-x86-DEU.exeWindowsXP-KB944043-v3-x86-DEU.exeWindowsXP-KB945060-v3-x86-DEU.exeWindowsXP-KB945184-x86-DEU.exeWindowsXP-KB946648-x86-DEU.exeWindowsXP-KB947460-v3-x86-DEU.exeWindowsXP-KB948101-v3-x86-DEU.exeWindowsXP-KB948277-x86-DEU.exeWindowsXP-KB948698-x86-DEU.exeWindowsXP-KB948720-x86-DEU.exeWindowsXP-KB948877-v2-x86.exeWindowsXP-KB949127-v2-x86-DEU.exeWindowsXP-KB949900-x86-DEU.exeWindowsXP-KB950305-v2-x86-DEU.exeWindowsXP-KB950616-x86-DEU.exeWindowsXP-KB950820-x86-DEU.exeWindowsXP-KB950974-x86-DEU.exeWindowsXP-KB950982-x86-DEU.exeWindowsXP-KB951159-x86-DEU.exeWindowsXP-KB951163-x86-DEU.exeWindowsXP-KB951347-x86-DEU.exeWindowsXP-KB951376-v2-x86-DEU.exeWindowsXP-KB951531-v2-x86-DEU.exeWindowsXP-KB951618-v2-x86-DEU.exeWindowsXP-KB951624-x86-DEU.exeWindowsXP-KB951709-x86-DEU.exeWindowsXP-KB951822-v2-x86-DEU.exeWindowsXP-KB951978-x86-DEU.exeWindowsXP-KB952004-x86-DEU.exeWindowsXP-KB952117-v2-x86-DEU.exeWindowsXP-KB952595-v3-x86-DEU.exeWindowsXP-KB952954-x86-DEU.exeWindowsXP-KB953024-x86-DEU.exeWindowsXP-KB953028-x86-DEU.exeWindowsXP-KB953155-x86-DEU.exeWindowsXP-KB953761-x86-DEU.exeWindowsXP-KB953930-x86-DEU.exeWindowsXP-KB954193-x86-DEU.exeWindowsXP-KB954232-x86-DEU.exeWindowsXP-KB954434-x86-DEU.exeWindowsXP-KB954708-x86-DEU.exeWindowsXP-KB954920-v2-x86-DEU.exeWindowsXP-KB955109-x86-DEU.exeWindowsXP-KB955356-x86-DEU.exeWindowsXP-KB955417-x86-DEU.exeWindowsXP-KB955567-x86-DEU.exeWindowsXP-KB955576-x86-DEU.exeWindowsXP-KB955704-x86-DEU.exeWindowsXP-KB955830-v2-x86-DEU.exeWindowsXP-KB955988-x86-DEU.exeWindowsXP-KB956048-x86-DEU.exeWindowsXP-KB956572-x86-DEU.exeWindowsXP-KB956844-x86-DEU.exeWindowsXP-KB957218-x86-DEU.exeWindowsXP-KB957495-x86-DEU.exeWindowsXP-KB957502-x86-DEU.exeWindowsXP-KB957931-x86-DEU.exeWindowsXP-KB958071-x86-DEU.exeWindowsXP-KB958149-x86-DEU.exeWindowsXP-KB958244-x86-DEU.exeWindowsXP-KB958817-x86-DEU.exeWindowsXP-KB958910-x86-DEU.exeWindowsXP-KB959267-x86-DEU.exeWindowsXP-KB959334-x86-DEU.exeWindowsXP-KB959465-x86-DEU.exeWindowsXP-KB959682-x86-DEU.exeWindowsXP-KB959765-x86-DEU.exeWindowsXP-KB959873-x86-DEU.exeWindowsXP-KB960071-v2-x86-DEU.exeWindowsXP-KB960519-x86-DEU.exeWindowsXP-KB960655-x86-DEU.exeWindowsXP-KB960680-v2-x86-DEU.exeWindowsXP-KB960859-x86-DEU.exeWindowsXP-KB960921-x86-DEU.exeWindowsXP-KB960970-x86-DEU.exeWindowsXP-KB961067-x86-DEU.exeWindowsXP-KB961118-x86-DEU.exeWindowsXP-KB961187-v2-x86-DEU.exeWindowsXP-KB961451-v2-x86-DEU.exeWindowsXP-KB961503-x86-DEU.exeWindowsXP-KB961605-x86-DEU.exeWindowsXP-KB961853-v2-x86-DEU.exeWindowsXP-KB963038-x86-DEU.exeWindowsXP-KB965220-x86-DEU.exeWindowsXP-KB967048-v2-x86-DEU.exeWindowsXP-KB967705-v2-x86-DEU.exeWindowsXP-KB968389-x86-DEU.exeWindowsXP-KB968930-x86-DEU.exeWindowsXP-KB969059-x86-DEU.exeWindowsXP-KB969084-x86-deu.exeWindowsXP-KB969262-x86-DEU.exeWindowsXP-KB969632-x86-DEU.exeWindowsXP-KB970048-x86-DEU.exeWindowsXP-KB970063-x86-DEU.exeWindowsXP-KB970254-x86-DEU.exeWindowsXP-KB970326-x86-DEU.exeWindowsXP-KB970413-x86-DEU.exeWindowsXP-KB970430-x86-DEU.exeWindowsXP-KB970483-x86-DEU.exeWindowsXP-KB970553-x86-DEU.exeWindowsXP-KB970685-x86-DEU.exeWindowsXP-KB971029-x86-DEU.exeWindowsXP-KB971165-x86-DEU.exeWindowsXP-KB971234-v2-x86-DEU.exeWindowsXP-KB971276-v3-x86.exeWindowsXP-KB971314-x86-DEU.exeWindowsXP-KB971345-x86-DEU.exeWindowsXP-KB971455-x86-DEU.exeWindowsXP-KB971657-x86-DEU.exeWindowsXP-KB972270-x86-DEU.exeWindowsXP-KB972422-x86-DEU.exeWindowsXP-KB972435-x86-DEU.exeWindowsXP-KB972878-x86-DEU.exeWindowsXP-KB973502-x86-DEU.exeWindowsXP-KB973507-x86-DEU.exeWindowsXP-KB973624-x86-DEU.exeWindowsXP-KB973815-x86-DEU.exeWindowsXP-KB973869-x86-DEU.exeWindowsXP-KB973904-x86-DEU.exeWindowsXP-KB974112-x86-DEU.exeWindowsXP-KB974318-x86-DEU.exeWindowsXP-KB974571-x86-DEU.exeWindowsXP-KB975025-x86-DEU.exeWindowsXP-KB975467-x86-DEU.exeWindowsXP-KB975560-x86-DEU.exeWindowsXP-KB975713-x86-DEU.exeWindowsXP-KB976002-v5-x86.exeWindowsXP-KB976323-x86-DEU.exeWindowsXP-KB977816-x86-DEU.exeWindowsXP-KB977914-x86-DEU.exeWindowsXP-KB978338-x86-DEU.exeWindowsXP-KB978542-x86-DEU.exeWindowsXP-KB978706-x86-DEU.exeWindowsXP-KB978835-x86-DEU.exeWindowsXP-KB979309-x86-DEU.exeWindowsXP-KB979482-x86-DEU.exeWindowsXP-KB979687-x86-DEU.exeWindowsXP-KB981073-v3-x86-DEU.exeWindowsXP-KB981669-x86.exeWindowsXP-KB981997-x86-DEU.exeWindowsXP-KB982132-x86-DEU.exeWindowsXP-KB982316-x86-DEU.exeWindowsXP-KB982665-x86-DEU.exeWindowsXP-WindowsMedia-KB2378111-x86-DEU.exeWindowsXP-WindowsMedia-KB2834904-v2-x86-DEU.exeWindowsXP-WindowsMedia-KB954155-x86-DEU.exeWindowsXP-WindowsMedia-KB973540-x86-DEU.exeWindowsXP-WindowsMedia-KB975558-x86-DEU.exeWindowsXP-WindowsMedia-KB978695-x86-DEU.exewmp11-windowsxp-x86-DE-DE.exeWUDF_UPDATE_XP-SRV03-X86.exewuweb.cab

 

Share this post


Link to post
Share on other sites

Hi Gunnar Schröter, you do not need the OnePiece_Microsoft.NET_Framework_v2.0.50727.3659_True_AddOn.cab & OnePiece_Microsoft.NET_Framework_v3.2.30729.4058.3_True_AddOn.cab if you have the OnePiece_Microsoft.NET_Framework_v3.5.30729.4056.3_True_AddOn.cab, the OnePiece_Microsoft.NET_Framework_v3.5.30729.4056.3_True_AddOn.cab already includes the OnePiece_Microsoft.NET_Framework_v2.0.50727.3659_True_AddOn.cab & OnePiece_Microsoft.NET_Framework_v3.2.30729.4058.3_True_AddOn.cab, 7z.exe depends on the system is not easy to achive 667 MB 7z.exe use\takes\requires a lot of RAM and CPU, however if you find problems archive manually OnePiece_WinXP_Post-SP3_UpdatePack_DEU

 

however already tested here by me and all seems OK

 

OnePiece Windows XP Post-SP3 UpdatePack v1.0.3 FINAL DEU


tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
tabdownload.png Update (1 September 2014)
Hash MD5 3D4CC00A44A9B49E857AB5F5151D412D
Filesize: 233.01 MB (244324930 bytes)

 

Ciao.

Edited by OnePiece

Share this post


Link to post
Share on other sites
 
 

Hi OnePiece, thx for your fast reply. I deleleted NET 2.0 and NET 3.2 and started DXUPAC from scratch - same result: DXUPAC is working on the files and in final stage (compression) it ends after a few seconds and is builing a UDP at about 14mb. I also tried to include only the INTL-files: same result. I builded my own UDP 2 month ago and everything worked like a charm, so i`m not a newbie to your exellent tool. But this time i don`t know what`s going wrong.

BTW: When i choose "Language = German" in DXUPAC, the "entries.ini" looks like this:

[general]BuildDate=2014/07/24Description=OnePiece's Windows XP Post-SP3 Update PackForceLang=GermanLanguage=GermanServicePack=SP3Title=OnePiece's Windows XP Post-SP3 Update PackVersion=1.0.3WebSite=http://www.microsoft.com/technet/security/current.aspxWindows=XP

"German is wrong - it`s got be "Deutsch" - i changed the code like this example:

[general]builddate=2014/07/05description=g-force_WinXP_Post-SP3_UpdatePack_DEU_2014.07.05forcelang=Deutschlanguage=DeutschServicePack=SP3title=g-force_WinXP_Post-SP3_UpdatePackversion=2014.07.05website=http://www.win-lite.deWindows=XP

Share this post


Link to post
Share on other sites

Hi Gunnar Schröter, thanks for reporting, i have no idea why it will happen, here I have just tested and all is OK, maybe problems with antivirus hmmmm, as mentioned above archive manually the folder OnePiece_WinXP_Post-SP3_UpdatePack_DEU

7z.exe depends on the system is not easy to achive 667 MB 7z.exe use\takes\requires a lot of RAM and CPU, however if you find problems archive manually OnePiece_WinXP_Post-SP3_UpdatePack_DEU

No, is not Deutsch, but officially is German (microsoft knows so, for this reason is written German)

de_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-73985.iso

2ir9gr9.jpg

Nonno Fabio wrote http://www.ryanvm.net/forum/viewtopic.php?p=132785&highlight=prodspec#132785

Ciao.

Edited by OnePiece

Share this post


Link to post
Share on other sites
 
 

THX for your immidiate reply. By integration with nLite there`s a notification that this addon is not for "Deutsch" because it`s for "German" - maybe a bug within nLite.

 

After running DXUPAC there are 2 folders inside my sourcefolder: "Archive files" and "OnePiece_WinXP_Post-SP3_UpdatePack_DEU". Second folder only contais:

AddOnRes.dllentries.iniNETFX11.cabNETFX11.in_NETFX20.IN_NETFX30.IN_NETFX35.IN_NETFX40.IN_OPMWXPUP.infqfecheck.exe

I`ve been running DXUPAC several times, changed workingfolder (due to lenght of path), deleted several updates (due to save RAM/CPU), de/installed 7z again. I´m wondering cause i created my own UDP a few weeks ago with no trouble - same PC, same OS, no changes.

Share this post


Link to post
Share on other sites

Video tutorial: how to create your localized Onepiece's UpdatePack (and IE, WMP11 or Silverlight Addons) with DXUPAC

 

and "OnePiece_WinXP_Post-SP3_UpdatePack_DEU". Second folder only contais:

AddOnRes.dllentries.iniNETFX11.cabNETFX11.in_NETFX20.IN_NETFX30.IN_NETFX35.IN_NETFX40.IN_OPMWXPUP.infqfecheck.exe
that will have to happen only when the DXUPAC not find any hotfix\file in the diretory ???, however those are the defualt file

There 's no need for it, DXUPAC is enough if someone wants to use XP Embedded updates

in MEGA & BOX UpdatePack\Windows XP Embedded folder is already available.

Open DXUPAC and add to source only XP Embedded Updates, then get files from OnePiece_WinXP_Post-SP3_UpdatePack_%Local% folder; as default DXUPAC copies always

AddOnRes.dllentries.iniNETFX20.IN_NETFX30.IN_NETFX35.IN_NETFX40.IN_OPMWXPUP.infqfecheck.exe
so all remaining files in OnePiece_WinXP_Post-SP3_UpdatePack_%Local% folder are the XP Embedded updates; in other words, you need only to copy/move/change all files from OnePiece_WinXP_Post-SP3_UpdatePack_%Local% to UpdatePack, or ignore (Default) files and using only files which remain inside OnePiece_WinXP_Post-SP3_UpdatePack_%Local%

or, again, delete entries.ini file from OnePiece_WinXP_Post-SP3_UpdatePack_%Local% and rename OnePiece_WinXP_Post-SP3_UpdatePack_%Local% in OnePiece_WinXP_Post-SP3_EOL_AddOn, then open NotePad e copy this text

[general]builddate=2014/05/18description=OnePiece's Windows XP Post-SP3 EOL Update PackServicePack=SP3title=OnePiece's Windows XP Post-SP3 EOL Update Packversion=2014website=http://www.microsoft.com/technet/security/current.aspxWindows=XP
save as OnePiece_WinXP_Post-SP3_EOL_AddOn\entries_EOL.ini, archive OnePiece_WinXP_Post-SP3_EOL_AddOn with CabTool or 7-Zip and integrate the AddOn after UpdatePack using nLite\RVMi

 

Ciao.

Edited by OnePiece

Share this post


Link to post
Share on other sites
 
 

1. I downloaded all sources again (INTL, German, Embedded German) to avoid mistakes (in fact there was no difference to the sources i used before).

2. I copied all files from the three unpacked archives into one folder (there are no subfolders in it).

3. I ran DXUPAC on this folder, after this is what happens:

 

A UDP is created at size of 14 mb.

A subfolder "OnePiece_WinXP_Post-SP3_UpdatePack_DEU" at 20 mb in my sourcefolder is created like i posted before.

Another subfolder "Archive Files" at 1,76 GB is created, it contains 286 subfolder named exactly like the integrated updates.

 

What am i doing wrong? I`m sure i worked the same procedure when i created my last UDP with DXUPAC.

 

BTW: Your UDP-DEU works like charm (exept that little bug with nLite), but i really want to create my own UDP.

Share this post


Link to post
Share on other sites

Hi Gunnar Schröter, thanks for reporting, I do not know how to help you, if I can not reproduce the problem here by me
 
All in DXUPAC.exe is very simple, is a GUI in AutoIt, after all it does a CMD file, I mean there's nothing special there, is only a cmd file nothing else, and the cmd file was written years and years and years ago, now we can write the script directly in AutoIt in a very profession mod, but as long as it works it is not worth wasting time to rewrite them
 
So try one more time, install in the Virtual Machine WinXPSP3 clean, after copy in destop the DXUPAC.exe, after create a folder "C:\Update" and copy all files inside, open DXUPAC.exe and in ComboBox Choose language choose German, after indicates the "C:\Update", click Start, and see if everything is OK
 
remember if you choose German and the file in directory is "Name File ENU.xxx" the DXUPAC ignore it, DXUPAC check only "Name File.xxx" or "Name File DEU.xxx" or "Name File DE.xxx" or "Name File DE-DE.xxx" or "Name File DE_DE.xxx"

Important, the DXUPAC.exe will not have to be in the same folder where are the updates

 

BTW: Your UDP-DEU works like charm (exept that little bug with nLite)

you should simply click on "No" when you are asked for: Wrong Pack language

Ciao.

Edited by OnePiece

Share this post


Link to post
Share on other sites
 
 

 

So try one more time, install in the Virtual Machine WinXPSP3 clean, after copy in destop the DXUPAC.exe, after create a folder "C:\Update" and copy all files inside, open DXUPAC.exe and in ComboBox Choose language choose German, after indicates the "C:\Update", click Start, and see if everything is OK

I gave it one (or 2 or 4 :-) ) more tries, it all ends with the same result. I was looking into the updatesfolder while DXUPAC was working - it seems like DXUPAC is working on all of the files, but won`t copy them to folder "OnePiece_WinXP_Post-SP3_UpdatePack_DEU" (ends up at 22 MB before compressing), only the folder "Achive Files" is growing up to about 1,61 GB. So no wonder 7z is working so fast - it has just 22mb to compress.

There is no wrong (ENU) updates in my source, only INTL or DEU, but it seems like DXUPAC ignores all the files. I looked into my TEMP-Folder and had a closer look at the .bat-files, but they are too complex for me to analys any faults.

Edited by Gunnar Schröter

Share this post


Link to post
Share on other sites

Hi Gunnar Schröter, Thanks again for the reports, at this point i'm really sorry but for me it is impossible to do anything if i can not reproduce the problem here by me, is a problem that i would not have ever seen since the creation of DXUPAC.exe years and years ago, what happens them to you is very strange I do not think the problem them is DXUPAC.exe and i really can not imagine any kind of scenario that could do that, in poor words what happens to them you seems like a thing that does not make sense (is how to say, in my browser I write wincert.com, and opens the microsoft.com ehhhh) because it is impossible that in VM in Window XP SP3 clean, tested a thousand times by me is all OKKKK and them to you is not OK hmmmmmmmmmmmmmm

I told you to try it in VM with a Windows XPSP3 clean and to use "C:\Update", to exclude problems with Antivirus (because sometimes some Antivirus give false positives to AutoIt, because of the UPX), and to exclude the possibility that maybe your Username who could use some character that the CMD file does not accept, so to exclude any kind of possible scenario that exist or could happen

what I see is only this

I do not know what else to say

Ciao.

Edited by OnePiece

Share this post


Link to post
Share on other sites

1. I set up a brandnew VM (VMWare-Player, XPPro with your UDP-DEU, 512mb RAM) - host was my installed XPPro (wich didn`t made the thing). No Anti_Virus was installed in the VM.

2. I set all things as you suggested (workfolder: "C:\Updates" , DXUPAC on desktop). I integrated INTL, DEU and Embedded-DEU. I did that in an older VM too.

3. DPUPAC worked on the files and copied everything correctly to "OnePiece_WinXP_Post-SP3_UpdatePack_DEU" !

4. The compression process ran for over 3 hours, even the host-system slowed down. I copied "OnePiece_WinXP_Post-SP3_UpdatePack_DEU" to my host system and closed the VM.

5. I made little changes to "entries.ini" (due to that nLite-bug) and compressed manually with 7z.

 

Now everything is working like i wanted - and nobody knows what happened before.

OnePiece, i thank for your patience and help! If i ever find out reasons for that strange behaviour of my host XP I`ll let you know. :dancing:

Edited by Gunnar Schröter

Share this post


Link to post
Share on other sites

Is there a difference between an "update pack" and an "addon pack"?  If yes, what is it?  I am new to this tool btw.  

Share this post


Link to post
Share on other sites

Hi All, since the creation DXUPAC was created with the purpose to make a tool that does not need to update it more, I want to say I have them updated always things that most concern the aesthetics, I mean you can put in the source also old\obsolete hotfix, DXUPAC will ignore their files if in the source there is another most recent hotfix, for example if tomorrow come out new updates, need only to copy all them into the source, and then create the new AddOn, obvious is better (and recommended) to clean the source removing the old\obsolete hotfix, but I mean even if they can be there, they do will not end in the AddOn, the only thing that ends is the file KB * .cat, which DXUPAC copy always in SvcPack, but that's is not a problem

in v1.2.3.4 or put in place permanently timezone update, now you can always put the latest updates without problem, attention to TimeZone update unicode ARA (Arabic) - CHS (Chinese Simplified) - CHT (Chinese Traditional) - ELL (Greek) - HEB (Hebrew) - JPN (Japanese) - KOR (Korean) - RUS (Russian)  not for the fault of the DXUPAC but it seems that in Windows XP English is impossible properly to extract the hotfix unicode the line update.inf hmmmm example JPN

    Argentina_Display="(GMT-03:00) ƒuƒGƒmƒXƒAƒCƒŒƒX"
    Argentina_Dlt="ƒAƒ‹ƒ[ƒ“ƒ`ƒ“‰ÄŽžŠÔ"
    Argentina_Std="ƒAƒ‹ƒ[ƒ“ƒ`ƒ“•W€Žž"
    Armenian_Dlt="ƒAƒ‹ƒƒjƒA‰ÄŽžŠÔ"
    Armenian_Std="ƒAƒ‹ƒƒjƒA•W€Žž"

so if users ARA-RUS etc etc also find problems in their systems, is recommended to use the Hotfix ENU (Remember that the Tzchange.exe is always the same in every language) removing ENU from the name of the hotfix and put it in the source

Sorry again for my english

Ciao a tutti.

Share this post


Link to post
Share on other sites

Hi MAXtoriX, Unfortunately I did not find free time to finish it but it creates already 70% of true addon

Dxtool.exe /MTI file_path ;Msi2Inf Tool 

Ciao.

Share this post


Link to post
Share on other sites
On 30.3.2016 at 10:37 AM, OnePiece said:

Hi MAXtoriX, Unfortunately I did not find free time to finish it but it creates already 70% of true addon


Dxtool.exe /MTI file_path ;Msi2Inf Tool 

Ciao.

What I need to do next? Is there a guide or tutorial or something...

Share this post


Link to post
Share on other sites

After MSItoinf, extract with 7-zip the setup.msi, and take the files, example extract SkypeSetup.msi, and take from them the Product.cab, and add in SkypeSetup.inf 

[SourceDisksNames]
   1="Skype Setup Files","Product.cab",,"i386" 

or extract 7z1514-x64.msi and add in 7z1514-x64.inf 

[SourceDisksNames]
   1="7-Zip Files","WIN51",,"i386" 


so you've almost done the true addon

Ciao.

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 nonno fabio
      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.
       
       
    • 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...