Onepiece XP Post-SP3 AIO Update Pack FINAL

[nonno fabio]

new release (see changelog)

[santoptol]

Hi there, when i try to make an English AIO update pack, using the files from onepiece's box and the latest DXUPAC, the archive i build has some differences from the one you make. More specific:
Your archive has 3 more files: SCVPACK\muweb.cat, wuauclt1.exe, wuaueng1.dll
There are some differences in 12 files: entries.ini, IE.inf, LgtCkCtl.dll, msxml.msi, OPWMXPUP.inf, swflash.inf, sysmain.sdb, winsstra.exe, wmfsdk.inf, wmp.inf, WRMC.msi, WEMCBC.msi.

I am going to make an AIO update pack in my native language by using the files from onepiece's box and I am asking you if I am going to have any troubles because these little differences.

Thanks in advance.

[nonno fabio]

you can ignore SCVPACK\muweb.cat, wuauclt1.exe and wuaueng1.dll files as they are no more used. Recent MU versions (WindowsUpdateAgent30*.exe ) don't update those files since long time.
Instead entries.ini, IE.inf, LgtCkCtl.dll, msxml.msi, OPWMXPUP.inf, swflash.inf, sysmain.sdb, winsstra.exe, wmfsdk.inf, wmp.inf, WRMC.msi, WEMCBC.msi and others are different because they are localized. Generally they depend on localized hotfix version, not always the same of ENU one. For example, wgatray.exe & wgalogon.dll depend on WindowsXP-KB905474-%LANG%-x86.exe build. About LgtCkCtl.dll (LegitCheckControl.dll) simply add in directory LegitCheckControl.cab http://go.microsoft.com/fwlink/?linkid=39204

[cosy]

thank you for the update, any DEU release too?

[Ultraform]

First time i got My own Swe pack to work, i did the pack on a laptop this time

But i wounder about a message that happen under installation.

[nonno fabio]

@cosy
http://www.ryanvm.net/forum/viewtopic.p ... 110#134110
http://www.ryanvm.net/forum/viewtopic.p ... 749#135749

[Ultraform]

Is this message normal ?
I got this on both SWE and ENG
edit : On XP home. dont think it happen to XP PRO / PRO VL

[nonno fabio]

Please specify more details on your integration.
Remember that UpdatePack is not responsible of third party modifcations not supported by Microsoft or Windows Setup

[bitoolean]

You know if not for your advice regarding integrating the removal add-ons separately, one at a time, using the RVM Integrator, I would have never solved my issue with integrating several add-ons (in fact, a lot of add-ons) of yours and Kels' together, which took me a month to realize anyway, a month full of headaches.

Every time I tested the remastered Windows setup disc, a different add-on would cause the same error. I posted about it elsewhere, not sure now what it was, perhaps a message about some DLL, but something was missing or wrong in the sysoc.inf I think (or something like that).

I finally decided the last resort, when I was out of ideas, to integrate each separately just like with your removal add-ons, and hocus-pocus, all of the add-ons worked together. Until then, it never crossed my mind that just throwing them all together with either nLite or the Integrator was a bad idea. Or maybe it did, but it just didn't seem plausible having to integrate each one at a time (this happened more than a year ago). So a double thank you is in order.

[spider]

Gah! I need some help.

I've tried integrating this pack

*with other addons
*without other addons rvmi only
*without other addons nlite only
*using vanilla Xp sp3 pro n edition
*using vanilla Xp sp3 pro edition
*Redownloaded the pack with a different downloader (even though hashes were correct)


But i still get the grpconv & framdyn/srclient.dll error

The only thing i can think of causing it is that I'm using windows 8.1 x64 to do this on?

Code: Select all

2014-02-27_23.15.29
Log Startup @ 23:15:29 local time, on February 27, 2014.

Running OS: WIN_VISTA  X64
RVMIntegrator v1.6.1 beta2.1

"I:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" 

23:15:43  - English - Windows XP Professional x86 - Corporate SP3 Found
23:16:09  - English - Windows XP Professional x86 - Corporate SP3 Found
23:16:09  - 
23:16:09  - Source Location      = D:\x4
23:16:09  - Destination Path     = d:\XP1
23:16:09  - Destination Size     = 18.73 GB
23:16:09  - Working Directory    = d:\XP1\I386
23:16:09  - Temp Directory       = d:\XP1\I386\rvmtemp
23:16:09  - 
23:16:09  - Starting Integration
23:16:09  - 
23:16:09  - Copying Files To The Destination Directory.
23:16:09  -   Copying Working Directory...
23:16:14  - 6421  Files Copied in 4 Seconds
23:16:14  - 
23:16:14  - Checking Destination For OS Type.
23:16:14  - English - Windows XP Professional x86 - Corporate SP3 Found
23:16:14  - 
23:16:14  - Extracting OnePiece_Windows_XP_Post-SP3_UpdatePack_v7.7.0.7z
23:16:51  -     MD5 Hash = a48c1ed4b478ee213a5d56c40ec64d30
23:16:51  - Clearing any Read Only Attributes.
23:16:52  - 
23:16:52  - Gathering temp files
23:16:52  - Integrating Windows XP Professional Files.
23:16:52  - 20 Files Moved in 0 Seconds
23:16:52  - Expanding driver.cab
23:17:03  -     CabLite.dll::CabExtractAsync reports completion [code=00001136]
23:17:03  - Expanding SP3.cab
23:17:06  -     CabLite.dll::CabExtractAsync reports completion [code=00000170]
23:17:08  - Copying/Moving files to driver.cab
23:17:09  - Copying files for driver.cab repackaging. - drivercab_copy
23:17:09  - Moving files for driver.cab repackaging. - drivercab_move
23:17:09  - Compressing Files
23:19:31  - Processing new .CAT files found in SVCPACK
23:19:35  - 
23:19:35  - Shifting Stuff Around
23:20:42  - 1754 Files Moved in 67 Seconds
23:20:42  - Analyzing 1 Entry Files
23:20:42  - Processing OnePiece's Windows XP Post-SP3 Update Pack v7.7.0   Build Date: 2014/02/12
23:20:42  -     Gathering Sysoc Entries
23:20:42  -     Gathering Dosnet.inf [Files] Entries
23:20:43  -     Gathering Dosnet.inf [Files] Entries - XP Pro Only
23:20:43  -     Gathering Dosnet.inf [Files] Entries - XP Home Only
23:20:43  -     Gathering txtsetup.sif [SourceDisksFiles] and [WinntDirectories] Entries
23:20:44  -     Gathering txtsetup.sif [SourceDisksFiles] and [WinntDirectories] Entries - XP Pro Only
23:20:44  -     Gathering ExtraFileEdits Entries
23:20:45  - 
23:20:45  - Preparing System Files...
23:20:45  -   sysoc.inf
23:20:45  -   svcpack.inf
23:20:45  -   dosnet.inf
23:20:45  -   txtsetup.sif
23:20:48  - 
23:20:48  - Processing ExtraFileEdits
23:20:49  - Processing Sysoc.inf
23:20:49  -     Adding Components
23:20:49  - Processing svcpack.inf
23:20:49  - Processing dosnet.inf
23:20:49  -     Modifying any SP?.cab areas in dosnet.inf
23:20:49  -     Editing [Files]
23:21:01  -     Editing [Files] - XP Pro Only
23:21:16  - Processing txtsetup.sif
23:21:16  -     Editing [WinntDirectories]
23:21:18  -     Editing [SourceDisksFiles]
23:21:19  -     Editing [SourceDisksFiles] - XP Pro Only
23:21:19  -     Modifying any SP?.cab areas in txtsetup.sif
23:21:22  - 
23:21:22  -       Compressing Files ASMS...
23:21:24  - 
23:21:24  - Processing [EditFile]
23:21:25  - Entire .ini Processing Completed in 42 Seconds
23:21:25  - 
23:21:25  - Compressing and Moving Edited Files
23:21:25  - 
23:21:25  - Processing mmssetup.cab
23:21:25  - Expanding mmssetup.cab
23:21:25  -     CabLite.dll::CabExtract reports completion [code=0000000A]
23:21:25  - Processing mmssetupcab_move
23:21:25  - Found and Moved new files into mmssetup.cab
23:21:25  - Rebuilding mmssetup.cab
23:21:26  - Rebuilding mmssetup.cab complete; 10 files compressed.
23:21:26  - 
23:21:26  - 
23:21:26  - Rebuilding driver.cab
23:23:29  - Compressed 4784 files into driver.cab [code=12B00001]
23:23:29  - 
23:23:29  - Rebuilding drvindex.inf
23:23:29  - Rebuilding drvindex.inf Complete.
23:23:29  - 
23:23:29  - Moving Files
23:23:29  - Replacing driver.cab
23:23:30  - Cleaning Up.
23:23:30  - Integration Completed.
23:23:30  - Total Integration Time = 436 Seconds
23:23:30  - ==================================================================================
23:23:30  - 

Log Shutdown @ 2014-02-27 23:42:27 local time.

[bitoolean]

Spider, you reminded me, that was the name of the DLL, framedyn.dll I think. The one mentioned in the logs / error message right after logging into the installed OS for the first time. As mentioned previously, that error appeared due to some errors in the resulted sysoc.inf in the installation, caused by incompatible addons (I was integrating too many addons at once but there were too many incompatibilities to figure out which) - the error disappeared when I integrated the add-ons one at a time.

I've never used the RVM Integrator to integrate OnePiece's UpdatePack as far as I can remember, so I can't help you, but I've never had problems using nLite. On the RVM Integrator web page, the description says that it has a limit with addons / updatepacks when it has to process too many files (over 1000), even the beta version that you're using, according to some comments on this forum somewhere by notorious pack creators . Are you doing any other modifications to the source other than integrating the updatepack?

Maybe someone else has more useful information for you. I'm not using Windows 8, nor a 64-bit OS.

[PaulAuckNZ]

The only thing i can think of causing it is that I'm using windows 8.1 x64 to do this on?

You shouldnt slipstream XP which is 32 bit on a 64 bit system. Or you WILL have probs. It should be slipstreamed in XP

[5eraph]

But i still get the grpconv & framdyn/srclient.dll error

In XPx64, GrpConv errors have been known to be caused by a bad line in WinNT.sif. Do you use a custom WinNT.sif file? Does it contain the following line?

Code: Select all

NonDriverSigningPolicy = Ignore

[nonno fabio]

framedyn.dll//srclient.dll, the mother of all integration errors! I was really young... SP2 integration!!
http://www.ryanvm.net/msfn/faq.html

I get errors involving "framedyn.dll" after integrating your SP2 update pack.
This problem is caused by a failed integration of the Update Pack.

As all of us ol'guys knows, you get a framedyn/srclient.dll error mostly when an .inf file doesn't find a file in XP CD.
The cause is never the updatepack itself, but probably a corrupted XP source

If you want to know what's happened, real windows setup log files, for example C:\Windows\setuperr.log, or remove from WinNT.sif file the option

Code: Select all

    [Unattended]
    UnattendMode=FullUnattended

or change it in

Code: Select all

[Unattended]
    UnattendMode=DefaultHide

so windows setup can tell which file it isn't able to find

Regarding Windows N edition see here
http://www.wincert.net/forum/topic/5143 ... entry82946

[spider]

*Never had problems before with rvmi, but I had the same issue with nlite so it wasn't that.
*Yes I did have "NonDriverSigningPolicy = Ignore" I've removed it now will try that.
*Yeah i've tried only integrating the addon and nothing else in an unmodified xp source. Still had the error.
*I'll try integration on an xp os. Do you think it would be ok to do inside a virtual machine?

Thanks for you help. I'll get back after i try a few things.

[PaulAuckNZ]

Should be fine in a VM. I usually slipstream XP in XP mode. Never had any probs with the finished ISO

[cosy]

*Never had problems before with rvmi, but I had the same issue with nlite so it wasn't that.
*Yes I did have "NonDriverSigningPolicy = Ignore" I've removed it now will try that.
*Yeah i've tried only integrating the addon and nothing else in an unmodified xp source. Still had the error.
*I'll try integration on an xp os. Do you think it would be ok to do inside a virtual machine?

Thanks for you help. I'll get back after i try a few things.

I have done this time over time and I have never had any errors whatsoever...
can you explain what you are doing over there?

[bitoolean]

@cosy: What have you done "times over time"? Integrating the updatepack into a 32-bit source on a 64-bit OS?

[nonno fabio]

I remember that updatepack integration tests are made since a long time on windows NT6.x x64 systems

[cosy]

@cosy: What have you done "times over time"? Integrating the updatepack into a 32-bit source on a 64-bit OS?

on both, which one is giving you a headache?

[spider]

Here's what happens

Code: Select all

@Echo off

Echo "Welcome to the Xp SP4 Builder"
  

Echo "Set Apps Drive Letter:"
Set /P Apps=
  

Echo "Set Builder Working Drive Letter:"
Set /P Xpdrive=

Echo "Cleaning Directories"
Del /F /Q "%Xpdrive%:\Xp\*.*"
RD /S /Q "%Xpdrive%:\Xp"
Del /F /Q "%Xpdrive%:\XpTest\*.*"
RD /S /Q "%Xpdrive%:\XpTest"
Del /F /Q "%Apps%:\Windows Builder\Xp\Logs\*.*"
RD /S /Q "%Apps%:\Windows Builder\Xp\Logs"
MKDIR "%Apps%:\Windows Builder\Xp\Logs"
  

Echo "Extracting Windows..."
rem "%Apps%:\Apps\GetWaikTools\x64\7z.exe" x "%Apps%:\ISOs\Slim Os\Xp Sp3 Slim Dec 2011.7z" -o"%Xpdrive%:\Xp">"%Apps%:\Windows Builder\Xp\Logs\XpExtract.txt"
"%Apps%:\Apps\GetWaikTools\x64\7z.exe" x -y -o"%Xpdrive%:\Xp" "%Apps%:\ISOs\Os\en_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-73974.iso">"%Apps%:\Windows Builder\Xp\Logs\XpExtract.txt"
rem Xp Sp3 Slim Dec 2011  Xp Sp3 Slim July 2012


Echo "Deleting Unessecary Files..."
DEL "%Xpdrive%:\Xp\README.HTM"
DEL "%Xpdrive%:\Xp\SETUPXP.HTM"
DEL "%Xpdrive%:\Xp\WIN51"
DEL "%Xpdrive%:\Xp\WIN51IP.SP2"
DEL "%Xpdrive%:\Xp\Last Session_u.ini"
DEL "%Xpdrive%:\Xp\Last Session.ini"
Del /F /Q "%Xpdrive%:\Xp\i386\COMPDATA\*.*"
RD /S /Q "%Xpdrive%:\Xp\i386\COMPDATA"
Del /F /Q "%Xpdrive%:\Xp\i386\DRW\*.*"
RD /S /Q "%Xpdrive%:\Xp\i386\DRW"
Del /F /Q "%Xpdrive%:\Xp\i386\WIN9XMIG\*.*"
RD /S /Q "%Xpdrive%:\Xp\i386\WIN9XMIG"
Del /F /Q "%Xpdrive%:\Xp\i386\WIN9XUPG\*.*"
RD /S /Q "%Xpdrive%:\Xp\i386\WIN9XUPG"
Del /F /Q "%Xpdrive%:\Xp\i386\WINNTUPG\*.*"
RD /S /Q "%Xpdrive%:\Xp\i386\WINNTUPG"
Del /F /Q "%Xpdrive%:\Xp\CMPNENTS\*.*"
RD /S /Q "%Xpdrive%:\Xp\CMPNENTS"
Del /F /Q "%Xpdrive%:\Xp\Support\*.*"
RD /S /Q "%Xpdrive%:\Xp\Support"
  

Echo "Integrating Updates..."
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\Xp" /Destination:"%Xpdrive%:\XpTest" /UpdatePack:"%Apps%:\Windows Builder\Xp\Addons\00 Essential\OnePiece_Windows_XP_Post-SP3_UpdatePack_v7.7.0.7z" /Integrate

rem "%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\01 Basic\*" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\00 Essential\Kels_CPLBonus_v13.2_addon.rar" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\00 Essential\Kels_Uber_Addon_v16.6.rar" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\00 Essential\Ricks_CMenu2.6_AddOn.rar" /Integrate




Echo "Patching Cosmetics..."
rem "%Apps%:\Windows Builder\Xp\Addons\02 Cosmetics\XPtsp.v1.4.7.1.exe"
rem Pause
  

Echo "Patching Patches..."
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\5er_KB893056_SP3_Addon.7z" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\ENU_Addons_BVProSvcDescriptions_1.5.2.7z" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\ENU_AddOns_SpeedUp_1.5.zip" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\Motion_Scenes_Addon.7z" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\PatchAddon_HIVESYS-1920x1200.7z" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\PatchAddon_SFC_OS_v14.7z" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\PatchAddon_SYSSETUP_InfSkip_v14.7z" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\PatchAddon_TCPIP_250_v14d.7z" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\PatchAddon_UXTHEME_v14a.7z" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\PatchAddon_XPRAID5_v14.7z" /Integrate
"%Apps%:\Windows Builder\Xp\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\XpTest" /Addons:"%Apps%:\Windows Builder\Xp\Addons\03 Patchs\WinXP_Pro_Vista BootScreen Blue (5857)_addon.7z" /Integrate

Echo "Please Reduce Your Xp As Desired..."
rem"%Apps%:\Windows Builder\Xp\Tools\nLite\nlite.exe"
  

Pause
Echo "Deleting Unessecary Files..."
Del /F /Q "%Xpdrive%:\Xp\*.*"
RD /S /Q "%Xpdrive%:\Xp"
DEL "%Xpdrive%:\XpTest\README.HTM"
DEL "%Xpdrive%:\XpTest\SETUPXP.HTM"
DEL "%Xpdrive%:\XpTest\WIN51"
DEL "%Xpdrive%:\XpTest\WIN51IP.SP2"
DEL "%Xpdrive%:\XpTest\Last Session_u.ini"
DEL "%Xpdrive%:\XpTest\Last Session.ini"
Del /F /Q "%Xpdrive%:\XpTest\i386\COMPDATA\*.*"
RD /S /Q "%Xpdrive%:\XpTest\i386\COMPDATA"
Del /F /Q "%Xpdrive%:\XpTest\i386\DRW\*.*"
RD /S /Q "%Xpdrive%:\XpTest\i386\DRW"
Del /F /Q "%Xpdrive%:\XpTest\i386\WIN9XMIG\*.*"
RD /S /Q "%Xpdrive%:\XpTest\i386\WIN9XMIG"
Del /F /Q "%Xpdrive%:\XpTest\i386\WIN9XUPG\*.*"
RD /S /Q "%Xpdrive%:\XpTest\i386\WIN9XUPG"
Del /F /Q "%Xpdrive%:\XpTest\i386\WINNTUPG\*.*"
RD /S /Q "%Xpdrive%:\XpTest\i386\WINNTUPG"

however currently I'm trying to get just OnePiece_Windows_XP_Post-SP3_UpdatePack_v7.7.0.7z to integrate onto Xp vanilla by rvmi/nlite without removing anything or adding anything extra.

[cosy]

you seem to be doing so many operations at once. I prefer to first integrate "OnePiece_Windows_XP_Post-SP3_UpdatePack.." on a neat XP_source first and let it finish in the first one round. Thereafter try to do the addons(get them also to finish first) and the components removal.

[spider]

nope it's all sequential in serial not parallel.

[cosy]

can you try to do this manually, make a folder "XP_ENU" extract all contents of your xp source with winrar or any other tool in this folder. open up nlite and try to intergrate your "OnePiece_Windows_XP_Post-SP3_UpdatePack.." only and see if you get any errors or not. From here try to do your further integration using this Folder- all should be fine

[spider]

can you try to do this manually, make a folder "XP_ENU" extract all contents of your xp source with winrar or any other tool in this folder. open up nlite and try to intergrate your "OnePiece_Windows_XP_Post-SP3_UpdatePack.." only and see if you get any errors or not. From here try to do your further integration using this Folder- all should be fine

got errors quite a few times doing that but finally got it to build fine on one go.
Problem is if i try reduce it with nlite it breaks.
Also if i try reduce it prior to integrating it breaks

[bitoolean]

I repeat:
I use nLite to remove & disable some stuff and integrate the updatepack. This is the first step in my process.
Then add any add-ons one by one using RVM Integrator. It never fails in my case. I add DriverPacks after that. Manually deleting folders should be your final step, before building the ISO. I'm not sure why you would do that first in you batch file. I see that nLite is REMmed, but if you uncomment it, move it to an upper position - you don't want to run it after already integrating add-ons. RVMI can work with nLited installations, but the other way around, not so much (not as often). It's already written on the web. The right order is: nLite, RVMI, DriverPacks... If you nLite the source before integrating or removing anything, and it still breaks, then you are probably removing something that is needed by what you are trying to integrate.

[bphlpt]

... nLite to remove & disable some stuff and integrate the updatepack ... add any add-ons one by one using RVM Integrator ... I add DriverPacks after that. Manually deleting folders should be your final step, before building the ISO. ... you don't want to run it (nLite) after already integrating add-ons. RVMI can work with nLited installations, but the other way around, not so much ... The right order is: nLite, RVMI, DriverPacks... If you nLite the source before integrating or removing anything, and it still breaks, then you are probably removing something that is needed by what you are trying to integrate.

While I agree with most of what you say, I think some of it depends of what exactly you are trying to do with nLite and RVMi. (Full Disclosure - I have only done very limited things with either RVMi or nLite - Why change stuff that works? - so much of what I believe is from what I have read of other's experience. If I am wrong I hope someone will correct me.)

NOTE: With the possible exception of (1) below, nLite should only be used ONCE while building an install source, while RVMi can be used multiple times if desired.

Things I believe:

1) Integrating SPx should be first - Can be done with /integrate switch, or with nLite, or any other method you chose but must be done on an XP host. Using nLite to do this as a standalone step I think is the only exception to the "Only use nLite once" rule.

2) Integrate the updatepack of your choice.

3) Add any other MS addons you wish, such as .NET etc if they aren't already included in the updatepack. [Of course with nonno fabio's pack this step does not apply. ]

[At this point your install source "should" be at the point that it would be if MS had any brains and would release an updated install CD, plus whatever extras are included in your updatepack.]

4) Apply any removals and OS tweaks.

5) Add non-MS addons. (Unless you use another external means to do so such as WPI.)

6) DriverPacks and manually deleting folders should be last.

I have seen some folks have success doing 1-5 with nLite all in one go. I have seen others do each of the above steps separately, and as mentioned earlier, even go as far as to add the various addons in multiple passes. If nLite is being used only, or primarily, for removals and OS tweaks, then I think it can be used safely after RVMi.

Bottom line, I totally agree that when it come to doing any removals:

"If you nLite the source ..., and it still breaks, then you are probably removing something that is needed by what you are trying to integrate."

Cheers and Regards

[bitoolean]

Very good info, bphlpt. It pretty much covers every possible scenario.

I always get missing framedyn / srclient DLL errors, just like nonno fabio said, when integrating multiple "true add-ons" in a single session of either RVMI or nLite. I'm no expert either, I'm just sharing my experience. I'm not sure which INF directives make them incompatible. When integrating them one by one though, there is no issue, so it probably is a limitation of the integrators (by that I mean that if I can just select the add-ons one by one and press the Integrate button for each of them, then the program could do the same processing by itself).

To avoid integration problems, I guess it's just as with grammar - if you apply some common sense, and don't try to speak more than one word at a time, don't repeat words, don't add too many attributes, etc., you're good and sentences come out right Start simple, and build upon that. You could say that the XP source, the service packs and the update packs are the subject and predicate of the integration process, so you'd need to make sure those integrated fine before anything else.

[spider]

Ah yes i was playing round and testing things I think i may have found the problem being the system file patches.

I've just done an update with harkaz's Sp4 pack and have a functional slim XP now

Based off that and some testing

The following script should work but i'm still investigating further in reagrds to the file patches

Code: Select all

@Echo on

Echo "Welcome to the Xp SP4 Builder"
 
Echo "Set Apps Drive Letter:"
Set /P App=

Rem SET Apps=%App%:\Xp Builder
SET Apps=%App%:\Windows Builder\Xp Builder
  
Echo "Set Builder Working Drive Letter:"
Set /P Xpdrive=

Echo "Cleaning Directories"
Del /F /Q "%Xpdrive%:\Xp\XpTest\*.*"
RD /S /Q "%Xpdrive%:\Xp\XpTest"
Del /F /Q "%Xpdrive%:\Xp\*.*"
RD /S /Q "%Xpdrive%:\Xp"
Del /F /Q %Apps%\Logs\*.*
RD /S /Q %Apps%\Logs
MKDIR %Apps%\Logs

Echo "Extracting Windows..."
"%App%:\Apps\GetWaikTools\x64\7z.exe" x -y -o"%Xpdrive%:\Xp\XpTest" "%App%:\ISOs\Os\en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso" > "%Apps%\Logs\XpExtract.txt"

Rem "%Apps%\Addons\00 Essential\WindowsXP-UnofficialSP4-Alpha2-x86-ENU.exe" -x:"%Xpdrive%:\Xp\Sp4" /quiet /nobackup
rem "%Xpdrive%:\Xp\Sp4\i386\update\update.exe" -s:"%Xpdrive%:\Xp\XpTest" /quiet

Echo "Integrating Updates..."
"%Apps%\Tools\nLite\nlite.exe" /preset:"%Apps%\Tools\Backup\Presets\00_Essential" /path:"%Xpdrive%:\Xp\XpTest"

Echo "Integrating Addons..."
"%Apps%\Tools\nLite\nlite.exe" /preset:"%Apps%\Tools\Backup\Presets\01_Basic" /path:"%Xpdrive%:\Xp\XpTest"

Echo "Patching Patches..."
"%Apps%\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\Xp\XpTest" /Addons:"%Apps%\Addons\02 Patchs\5er_KB893056_SP3_Addon.7z" /Integrate
"%Apps%\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\Xp\XpTest" /Addons:"%Apps%\Addons\02 Patchs\Entries_BVProSvcDescriptions_1.5.3.7z" /Integrate
"%Apps%\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\Xp\XpTest" /Addons:"%Apps%\Addons\02 Patchs\ENU_AddOns_SpeedUp_1.5.zip" /Integrate
"%Apps%\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\Xp\XpTest" /Addons:"%Apps%\Addons\02 Patchs\PatchAddon_HIVESYS-1920x1200.7z" /Integrate
"%Apps%\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\Xp\XpTest" /Addons:"%Apps%\Addons\02 Patchs\PatchAddon_SFC_OS_v14.7z" /Integrate
"%Apps%\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\Xp\XpTest" /Addons:"%Apps%\Addons\02 Patchs\PatchAddon_SYSSETUP_InfSkip_v14.7z" /Integrate
"%Apps%\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\Xp\XpTest" /Addons:"%Apps%\Addons\02 Patchs\PatchAddon_TCPIP_250_v14d.7z" /Integrate
"%Apps%\Tools\Rvm\RVM_Integrator_1.6.1b2.1.exe" /Wipe /Source:"%Xpdrive%:\Xp\XpTest" /Addons:"%Apps%\Addons\02 Patchs\PatchAddon_XPRAID5_v14.7z" /Integrate

Echo "Patching Cosmetics..."
"%Apps%\Addons\03 Cosmetics\XPtsp.v1.4.7.1.exe"

Echo "Reducing Your Xp..."
"%Apps%\Tools\nLite\nlite.exe" /preset:"%Apps%\Tools\Backup\Presets\Xp_Slim_v1.3" /path:"%Xpdrive%:\Xp\XpTest"
 

Echo "Deleting Unessecary Files..."
Del /F /Q "%Xpdrive%:\Xp\*.*"
RD /S /Q "%Xpdrive%:\Xp"
DEL "%Xpdrive%:\Xp\XpTest\README.HTM"
DEL "%Xpdrive%:\Xp\XpTest\SETUPXP.HTM"
DEL "%Xpdrive%:\Xp\XpTest\Last Session_u.ini"
DEL "%Xpdrive%:\Xp\XpTest\Last Session.ini"
rem Del /F /Q "%Xpdrive%:\Xp\XpTest\i386\COMPDATA\*.*"
rem RD /S /Q "%Xpdrive%:\Xp\XpTest\i386\COMPDATA"
rem Del /F /Q "%Xpdrive%:\Xp\XpTest\i386\DRW\*.*"
rem RD /S /Q "%Xpdrive%:\Xp\XpTest\i386\DRW"
Del /F /Q "%Xpdrive%:\Xp\XpTest\i386\WIN9XMIG\*.*"
RD /S /Q "%Xpdrive%:\Xp\XpTest\i386\WIN9XMIG"
Del /F /Q "%Xpdrive%:\Xp\XpTest\i386\WIN9XUPG\*.*"
RD /S /Q "%Xpdrive%:\Xp\XpTest\i386\WIN9XUPG"
Del /F /Q "%Xpdrive%:\Xp\XpTest\i386\WINNTUPG\*.*"
RD /S /Q "%Xpdrive%:\Xp\XpTest\i386\WINNTUPG"
Del /F /Q "%Xpdrive%:\Xp\XpTest\i386\CMPNENTS\*.*"
RD /S /Q "%Xpdrive%:\Xp\XpTest\i386\CMPNENTS"
Del /F /Q "%Xpdrive%:\Xp\XpTest\i386\Support\*.*"
RD /S /Q "%Xpdrive%:\Xp\XpTest\i386\Support"
Del /F /Q "%Xpdrive%:\Xp\XpTest\i386\Lang\*.*"
RD /S /Q "%Xpdrive%:\Xp\XpTest\i386\Lang"  
Del /F /Q "%Xpdrive%:\Xp\XpTest\i386\[BOOT]\*.*"
RD /S /Q "%Xpdrive%:\Xp\XpTest\i386\[BOOT]"

Echo "Copying Folders..."
xcopy  /s /h /y /k /g /c "%Apps%\Backup\WINNT.SIF" "%Xpdrive%:\Xp\XpTest\i386\"
xcopy  /s /h /y /k /g /c "%Apps%\CD\*.*" "%Xpdrive%:\Xp\XpTest"

Echo "Building Iso..."
"%App%:\Apps\GetWaikTools\ImgBurn\ImgBurn.exe" /MODE BUILD /BUILDINPUTMODE ADVANCED /BUILDOUTPUTMODE IMAGEFILE /DEST "%Xpdrive%:\Xp\Xp Sp4 Slim v1.0" /VOLUMELABEL "Xp Sp4 Slim v1.0" /BOOTEMUTYPE 0 /BOOTIMAGE "%Apps%\Tools\Backup\Microsoft Corporation.ima" /BOOTLOADSEGMENT 07C0 /BOOTSECTORSTOLOAD 4 /BOOTDEVELOPERID "Huntakillaz" /PORTABLE /NOSAVESETTINGS /CLOSESUCCESS

Pause 
Rem Del /F /Q "%Xpdrive%:\Xp\*.*"
Rem RD /S /Q "%Xpdrive%:\Xp"
Rem Del /F /Q "%Xpdrive%:\Xp\XpTest\*.*"
Rem RD /S /Q "%Xpdrive%:\Xp\XpTest"
Del /F /Q "%Apps%\Logs\*.*"
RD /S /Q "%Apps%\Logs"

Echo "All Complete! :)"
Pause

[bitoolean]

The Del commands before the RD commands are not necessary, even with read-only files/directories. RD with S and Q switches deletes an entire directory, recursively (including the directory itself, any subdirectories, and their contents).
You should probably post in a more appropriate thread since you seem to no longer be using OnePiece's UpdatePack

[nonno fabio]

new release (see changelog)

A note about KB2934207 update (A notification about the end of Windows XP support): you can easily disable it from Windows Component Wizard menu



Furthermore Remove addon suite has been updated with OnePiece_Disable_XP_EOS_AddOn.cab & OnePiece_Remove_XP_EOS_AddOn.cab

[tjwasiak]

I would like to kindly ask about KB2933528 released in March. I could not find it in Changelog nor in HotfixList but I found it uploaded (at least to Polish) updates on box.com. Should this update be included in 7.8.0 or not?

[OnePiece Alb]

no, you do not need KB2933528, is finished them by mistake (already removed), thanks for reporting

Ciao.

[tjwasiak]

no, you do not need KB2933528, is finished them by mistake (already removed), thanks for reporting

Ciao.

Thank you for prompt answer. I am going to "cook" polish 7.8.0 right now

[pansophysr]

Probably a dumb question, but is there someplace where one can still get OnePiece_Windows_XP_Post-SP3_UpdatePack_v7.7.0_ENU.

Thanks,

P.

[tjwasiak]

Probably a dumb question, but is there someplace where one can still get OnePiece_Windows_XP_Post-SP3_UpdatePack_v7.7.0_ENU.

For example using Box mirror posted by One Piece / Nonno Fabio inside Archive folder.

[pansophysr]

Found it! Thanks for the prompt reply.

P

[nonno fabio]

in Onepiece's Mega archive you can find ALL updatepack releases (100 and more...)

[PaulAuckNZ]

Can you remove KB2934207 with an addon or something somehow? After you slipstream the updatepack?

Don't think I want to be reminded that support is ending after I slipstream it

[OnePiece Alb]

Can you remove KB2934207 with an addon or something somehow? After you slipstream the updatepack?

Don't think I want to be reminded that support is ending after I slipstream it

There are many ways to do that (Online or Offline)

new release (see changelog)

A note about KB2934207 update (A notification about the end of Windows XP support): you can easily disable it from Windows Component Wizard menu



Furthermore Remove addon suite has been updated with OnePiece_Disable_XP_EOS_AddOn.cab & OnePiece_Remove_XP_EOS_AddOn.cab

recommended the use of OnePiece_Disable_XP_EOS_AddOn.cab

Ciao.

[PaulAuckNZ]

Cool thats good enough for me ta Wheres the addon? There was an addon for MRT is it still available?? I dont need that either

[OnePiece Alb]

Cool thats good enough for me ta Wheres the addon? There was an addon for MRT is it still available?? I dont need that either

in first post

[*]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:

Code: Select all

[Components]
...
WDSearch = off
...

All the Winnt.sif optional components codes are shown below. List only those you want to disable!

Code: Select all

BitLockerToGo = BitLocker To Go Reader
BrowserChoice = Browser Choice
DirectX       = DirectX Post-SP3 Update
ICCDSCD       = Windows Feature Pack for Storage
IMAPI2        = Image Mastering API
MDX           = DirectX Managed Code
MSXML4        = MSXML 4.0 SP3 Parser (KB2721691)
MU            = Microsoft Update
NETFX30       = Microsoft .NET Framework 3.0 Service Pack 2
NETFX35       = Microsoft .NET Framework 3.5 SP1
NETFX40       = Microsoft .NET Framework 4
PowerShell    = Windows PowerShell
PowerShellISE = Windows PowerShell ISE
Silverlight   = Microsoft Silverlight
WDSearch      = Windows Desktop Search
WgaNotify     = Windows Genuine Advantage Notifications
WinRM         = Windows Remote Management (WS-Management)
WRMC          = Windows Rights Management Client
XP_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 (12 March 2014)
Update (12 March 2014)
Update (12 March 2014)
Update (12 March 2014)
Update (12 March 2014)
Update (12 March 2014)
Update (12 March 2014)
Update (12 March 2014)
Update (12 March 2014)
Hash MD5 3790B85508D3078A09DA6B6217386A4C
Filesize: 18.3 KB (18833 bytes)

NB
*"REMOVE" addons are RVMIntegrator-only!! the entries.ini removal values are not supported by Nlite.
**the file you download, OnePiece_Remove_AddOn_For_WinXP_UP*.cab, is the archived full suite of single addons: you must unpack it (or extract from it the addons you need) before use with RVMi.
*** 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.[/list]

Ciao.

[PaulAuckNZ]

Thanks

[viggen66]

So the next update is going to be the last one

[sodapopdima]

So the next update is going to be the last one

That's what I am wondering as well

[ahmerkhan]

Thanks for keep updating the XPSP3, I really appreciate your hard work

[nonno fabio]

first final XP release (see changelog).
note: November 2013 Root Certificates update has been readded in addition to latest March one, becase WindowsUpdate asks for it

[user_hidden]

first final XP release (see changelog).
note: November 2013 Root Certificates update has been readded in addition to latest March one, becase WindowsUpdate asks for it

great job through the years buddy. I have appreciated all that you have done.

btw, the UpdRoots must be another game by MS once again to the XP users.

[OnePiece Alb]

Hi user_hidden, it seems that the release of the November 2013 update\add\edit registry keys that does not make them in March 2014, perhaps there's some problems with the release in March 2014, perhaps is not complete maybe missing pieces or maybe a BUG hmmmmm, I think if it was not a serious thing, I do not think that MU insist so much

in general only need to use the

Code: Select all

HKLM,"Software\Microsoft\Active Setup\Installed Components\{EF289A85-8E57-408d-BE47-73B55609861A}","Version",,"40,0,2195,0"

and MU is Ok, but is not recommended is not safe, need to install "November 2013" for the reasons said above


here is the modified March 2014 (41,0,2195,0) rootsupd.exe (in November 2013 & March 2014) inside the UpdatePack

[Version]
Signature = "$Chicago$"
Provider = %Msft%
AdvancedINF = 2.0,%AdvPack%

[DefaultInstall]
RequiredEngine = setupapi.dll,%SetupAPI%
CheckAdminRights = 1
AddReg=AppCompatSetup.reg
RunPostSetupCommands = RunPostSetupCmds

[RunPostSetupCmds]
updroots.exe authroots_2013.sst
updroots.exe updroots_2013.sst
updroots.exe -l roots_2013.sst
updroots.exe -d delroots_2013.sst
updroots.exe authroots.sst
updroots.exe updroots.sst
updroots.exe -l roots.sst
updroots.exe -d delroots.sst

[AppCompatSetup.reg]
HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID%",,,"%COMPName%"
HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID%","IsInstalled",0x10001,01,00,00,00
HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID%","Version",,"%VERSION%"
HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID%","Locale",,"%LANG%"
HKLM,"Software\Microsoft\Active Setup\Installed Components\%GUID%","ComponentID",,"%COMPID%"


[Strings]
; !!!!!!!WARNING!!!!!!!!
; !!!!!!!WARNING!!!!!!!!
; !!!!!!!WARNING!!!!!!!!
; !!!!!!!WARNING!!!!!!!!
; >>>>> VERSION must be updated for each update roots package <<<<<
; "Ver" must also match the first field of VERSION.
VERSION="40,0,2195,0" ; "41,0,2195,0"
Ver="040" ; "041"

; Don't change this -- this is our unique GUID
GUID={EF289A85-8E57-408d-BE47-73B55609861A}


; Don't change these either
COMPID=Windows Roots Update
COMPName=RootsUpdate

; Same set of roots for all locales
LANG=*

;----------------------
; localizeable Strings
;----------------------
Msft = "Microsoft"
AdvPack = "The correct version of Advpack.dll was not found, update halted."
SetupAPI = "Required file: SetupAPI.dll, is missing from your system."

so install November 2013 and after March 2014 and after puts in registry "40,0,2195,0" (November 2013) to satisfy the MU

I think it better (for safety) to use https://mega.co.nz/#!0x80TahT!GKAdIg1SO ... QUtmYiCP_I or https://app.box.com/s/ecm6cf4fgfwa88u0vlw9 in your UpdatePack

Ciao.

[user_hidden]

gracie