Welcome to Windows XP Service Pack 4

Forum to discuss Update Packs created by community members for the various Windows operating systems.
Post Reply
ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Wed Oct 23, 2013 5:04 pm

XP Pro w/SP3 > AutoStreamer v1.0.33 > Windows share: \Windows XP Pro #1 with SP3 CD > Service Pack file: \WindowsXP-SP4-M2-ENU-x86.exe - got error message: Build: Share is already updated! > Next > Skip Slipstreaming? You haven't selected a valid Service Pack file! If you wnat to skip this, and just create a CD image, click 'Yes". Otherwise, click 'No' to return and specify a valid Service Pack file.

XP Pro w/SP3 > RVM Integrator 1.6.1b2.1 > File > Slipstream Service Pack > Browse For Folder: Select the Root directory holding the I386 folder you wish to slipstream > Selected CD copy: \Windows XP Pro #1 with SP3 CD > Browse To The ServicePack file to be Slipstreamed > Selected: WindowsXP-SP4-M2-ENU-x86.exe > Open > Extraction started and slipstreaming completed.

2013-10-23_13.26.12
Log Startup @ 13:26:12 local time, on October 23, 2013.

Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.6.1 beta2.1

"G:\RyanVM\RVM_Integrator_1.6.1b2.1.exe"

13:26:13 - English - Windows XP Professional x86 - Retail SP3 Found
13:26:20 -
13:26:20 - Starting user-requested service pack slipstream.
13:28:51 - Asking user for service pack network install file...
13:30:05 - Slipstreaming service pack: WindowsXP-SP4-M2-ENU-x86.exe

Log Shutdown @ 2013-10-23 13:31:20 local time.


Opened Explorer and found that the process had created new folders: cmpnents, docs, support, and valueadd. The cmpnents folder had two subfolders: netfx and TABLETPC, each of these had an i386 subfolder. The netfx\i386 had netfx cab subfolder which was full of files. The TABLETPC\i386 subfolder was also full of files.

The docs folder was empty.

The support folder had a tools subfolder - which was empty.

The valueadd folder had a subfolder structure: \msft\usmt\ansi - all of which were empty.

Question: Are these newly created folders\subfolders necessary? For what purpose? Please explain.

Noticed that after slipstream completion the I386 folder size went from 420.13Mb to 422.14Mb - does that seem correct based on your testing?

Looks like success has been achieved - good work. Next test, today or tomorrow will include Update Pack, Addons, etc. - interesting to see the results.

User avatar
Kelsenellenelvian
Moderator
Posts: 4383
Joined: Tue Nov 30, 2004 8:32 pm
Location: Pocatello, ID
Contact:

Post by Kelsenellenelvian » Thu Oct 24, 2013 12:27 am

Is there a list of all this is included as to date?

Also I have a official royale theme that is not JUST royale but the full standard 3 color xp theme with royal as a sub color choice. All official no need for uxtheme patching.

I sent you some files via email.

Here is a screen of the theme:

Image

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Thu Oct 24, 2013 5:45 pm

@ChiefZeke: "420.13Mb to 422.14Mb": This is not the appropriate change in size. You should expect a 30 MB change of size. Try integrating by running the SP4 installer with the /integrate:<path_towindows_share> switch. This is the official (and recommended) method to slipstream service packs. Make sure you're executing the command on a x86 system, with administratative priviliges.

@ Kelsenellenelvian: I got your mail. Thanks for the sfxcab.exe file and the windows theme files. They will be added in XP SP4 M3.

List of changes in XP SP4 M2 since XP SP3 RTM:

Code: Select all

-Removed Windows Messenger 4.7
-Updated to MSN Explorer 10.5 in CD-ROM installations.
-Internet Explorer 8 integrated in SP4
-Windows Update Agent 7.6.7600.256-257 is integrated in SP4
-Uninstallation not possible if following the RTM->SP2->SP4, RTM->SP1->SP4, etc. update paths (on live installations).
-You cannot change default uninstall directory
-No Microsoft files have been patched, except for the main installer file, update.exe. SFC won't complain about anything at all.

I have just finished MSI45 integration and moving on with IMAPIv2 and WMP11. You know, the most irritating part of SP4 is keeping existing update.ver entries up-to-date :p, but that's essential for live installations.
I will keep you updated.[/code]
Last edited by harkaz on Thu Oct 24, 2013 5:51 pm, edited 2 times in total.

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Thu Oct 24, 2013 5:47 pm

The following is a copy of notes I wrote to myself as I became familier with the RyanVM Integrator - I beleive most, if not all, of the information applies here as well:

Looking at an XP Home CD \DOCS, \DOTNETFX, \SUPPORT, and \VALUEADD and an XP Pro CD \CMPNENTS, \DOCS, \SUPPORT, and \VALUEADD do not have to be included as a part of the source when using the RyanVM Integrator because no files/programs in these folders are updated when the Integrator is run and they simply consume space that could be used by other Addons included in the Integrator as part of its operation. (The user could alwasy return to the source CD in the future if it was determined something here was required.)

Also, in \I386, the folders \LANG, \WIN9XMIG, \WIN9XUPG, and \WINNTUPG were also not effected by the Integrator and, depending on the end use of the final CD, one, two, three, or all of them could also be eliminated form the source as the Integrator was being used; thereby providing more space for additional Addons to be integrated. (Statement in () above also applies here.) Also delete \LANG if English only is to be used.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Thu Oct 24, 2013 6:00 pm

That's right, ChiefZeke, but take note that in future SP4 builds the cmpnents folder miht be necessary because SP4 won't fit on a single 650 MB CD-ROM

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Thu Oct 24, 2013 6:41 pm

My mistake, the i386 folder before slipstreaming: 409.19Mb and after: 422.14Mb

The total size went from: 410.56Mb to: 449.25Mb which includes the size of the new folders that were created during the SP4 M2 integration. (cmpnents size is 25.74Mb of this total)

As mentioned above, integration done in XP Pro w/SP3 (an x86 system).

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Thu Oct 24, 2013 6:49 pm

harkaz wrote:That's right, ChiefZeke, but take note that in future SP4 builds the cmpnents folder miht be necessary because SP4 won't fit on a single 650 MB CD-ROM
@harkaz

Must be missing something - why would the cmpnents folder be necessary in this situation?

Also, I would suspect most people have the ability to burn DVDs, thereby not being limited to 650Mb and/or burn to bootable flash drives, many of which come in sizes exceeding 650Mb.

User avatar
bphlpt
Posts: 1351
Joined: Sat Apr 19, 2008 1:11 am

Post by bphlpt » Fri Oct 25, 2013 1:02 am

I'm going to agree with Chief here and say I also do not understand why all the folders he specified 4 posts above this one need to be included for any reason. I don't see why any of them would possibly need to be touched in any way, or included in the final build. (With the possible exception of \LANG for non-English installs.) If any of those folders have any files in them that would still be relevant and useful for an SP4 install I would really like to understand which files and why.

Cheers and Regards

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Fri Oct 25, 2013 4:12 am

OK, let me explain why I think cmpnents folder will be necessary in future SP4 builds.

The cmpnents folder includes setup files for MCE and Tablet PC.

Why Microsoft chose to use the cmpnents folder? The main reason for this is the fact that MCE and Tablet PC files won't fit on a single 650 MB CD-ROM together with the files in I386 and other folders. (This is the standard CD-ROM size, as CD-R disks may be 700, 800 or even 900 MB in size). In MCE and Tablet PC distributions, the cmpnents folder is in the second installation disk.

The layout.inf,txtsetup.sif,dosnet.inf files are always found on the first installation disk and include references for all Setup files. Even if you don't have MCE, they reference the cmpnents folder, as the second installation disk and define the files from there.

Windows XP SP4 will include some components like .NET Frameworks which obviously don't fit on a signle 650 MB CD-ROM. They should be found in a second installation CD-ROM. Since, Windows XP CD-ROM #2 is already defined using the name \cmpnents (the cmpnents folder), we will continue using this folder for these files. That's why I think it will be essential for future SP4 builds.

As for other folders, I don't plan to remove them from the SP4 build. Windows XP SP4 should include these special files, like all previous SPs did. The only directory that may be removed is the \dotnetfx directory, because .NET Framework will be part of XP SP4.

User avatar
bphlpt
Posts: 1351
Joined: Sat Apr 19, 2008 1:11 am

Post by bphlpt » Fri Oct 25, 2013 5:50 am

Thank you for your explanation.

For the need for \CMPNENTS for MCE, you might want to check this out - http://www.wincert.net/forum/topic/4652 ... y-24-2012/ - as an alternative approach that has worked well for years. There is a similar method for Tablet PC, which can be used with or without MCE, that we could probably dig up for you as well. I'm not saying that you shouldn't also try to make your solution work for the regular releases of MCE and Table PC, but this is something else to consider.

As to the other folders, and \CMPNENTS too, I don't have a problem with you not planning to remove them, some people like to include them, even though I truly believe they will be totally non-functional for a SP4 build, except for \LANG. (If I am wrong about this I hope someone will show me the error of my ways. :) ) But I also feel very strongly that anything you do should not add anything at all to them or require their presence, not even create a warning message in a log if they are missing. If they are there, fine, they will be copied over and included. If they are missing, fine, you really shouldn't care.

I also agree with Chief that I don't see the need to require that your solution fit on, or utilize, only 650 MB CD-ROMs, though I also agree with you that it might be an elegant solution and be most like the original release if it did. But with everything that you have added, or plan to add, is there really a problem if the result requires a DVD or USB flash drive? People who want to add all that material should realize that it takes up extra space so should not be upset by that, I would think.

Cheers and Regards

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Fri Oct 25, 2013 6:55 am

Windows XP SP4 will not add special requirements for these files. It will only add new files in cmpnents folder. If you want to burn SP4 to DVD or USB, you have to copy the cmpnents folder with these added files (not the MEDIACTR,NETFX,TABLETPC subfolders). You won't get any messages during Setup. If you have to use CD-ROMs (for installation on old hardware, for example) copy the cmpnents folder to a second non-bootable disk and use that disk as "Windows XP Service Pack 4 CD-ROM #2".

Thanks for the MCE2005 link, it helps me A LOT.

I'm integrating the IMAPI2 right now and I'm rebuilding the SP3.CAB with the updated disk.sys driver. I've changed the compression algorithm of all new files to LZX:21, which is what Microsoft uses in Service Packs. This enhances compression ratio.

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Fri Oct 25, 2013 11:18 pm

Testing time to see how SP4M2 appears to other RyanVM Integrator procedures, WMP11 SlipStreamer and DriverPacks installer, etc - not good :

#1 test: RVMIntegrator v1.6.1 beta2.1 + \Windows XP Pro #1 with SP4M2 Test + Latest Update Pack - XPSP3_QFE_UpdatePack_20131008.7z + Many Addons (see log files) + WMP11 Slipstreamer + Driver Packs = Latest XP with updates/addons/etc + Make ISO.


2013-10-25_15.03.07
Log Startup @ 15:03:07 local time, on October 25, 2013.

Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.6.1 beta2.1

"G:\RyanVM\RVM_Integrator_1.6.1b2.1.exe"

15:12:26 - English - Windows XP Professional x86 - Retail SP4 Found
15:12:26 -
15:12:26 - Source Location = F:\Windows XP Pro #1 with SP4M2 Test
15:12:26 - Destination Path = W:\XPPro#1Integrated
15:12:26 - Destination Size = 461.11 GB
15:12:26 - Working Directory = W:\XPPro#1Integrated\I386
15:12:26 - Temp Directory = W:\XPPro#1Integrated\I386\rvmtemp
15:12:26 -
15:12:26 - Starting Integration
15:12:26 -
15:12:26 - Copying Files To The Destination Directory.
15:12:26 - Copying Working Directory...
15:13:32 - 6789 Files Copied in 65 Seconds
15:13:32 - Copying \CMPNENTS\ Directory...
15:13:33 - 91 Files Copied in 1 Seconds
15:13:33 -
15:13:33 - Checking Destination For OS Type.
15:13:33 - English - Windows XP Professional x86 - Retail SP4 Found
15:13:33 -
15:13:33 - Extracting XPSP3_QFE_UpdatePack_20131008.7z
15:13:43 - MD5 Hash = c2982e583fb8d63c622baca564759fb0
15:13:43 - Extracting YumeYao_WIC_Update_Addon_1_2_0.cab
15:13:43 - CabLite.dll::CabExtract reports completion

Code: Select all

15:13:43  -     MD5 Hash = e07332f9934b85b6b1270a3e57fd1feb
15:13:43  - Extracting 5er_KB893056_SP3_Addon.7z
15:13:43  -     MD5 Hash = 90af4dd8ca273ab002032cec940b350d
15:13:44  - Extracting DirectXRuntimes-201006-Addon-32.cab
15:13:44  -     CabLite.dll::CabExtractAsync reports completion [code=00000002]
15:13:44  -     MD5 Hash = 9f2496fa18c36b6f7b7a319519ebde0d
15:13:44  - Extracting Doug_Accessibility_AddOn_v13.rar
15:13:44  -     MD5 Hash = 04366ea5dcce36e60dcb610dcb22b941
15:13:44  - Extracting ENU_Addons_BVProSvcDescriptions_1.5.2.7z
15:13:44  -     MD5 Hash = 122a556425dfb31b7f9eb708f07381e2
15:13:44  - Extracting Jondar_RegeditCPL_Addon_v1.0.cab
15:13:44  -     CabLite.dll::CabExtract reports completion [code=00000003]
15:13:44  -     MD5 Hash = 8d55f16e1335a4d44bcb1138fd2c5394
15:13:44  - Extracting Kels_DirectX_CPL_addon_v90c.cab
15:13:44  -     CabLite.dll::CabExtract reports completion [code=00000002]
15:13:44  -     MD5 Hash = 515e7bfb1b2cc55c93f98ee71c5309ec
15:13:44  - Extracting Kels_MS_MSICleaner_addon_v44.cab
15:13:44  -     CabLite.dll::CabExtract reports completion [code=00000005]
15:13:44  -     MD5 Hash = 466ffed34f5eea8c6195154e4509309c
15:13:44  - Extracting Kels_MSConfig_addon_v11.cab
15:13:44  -     CabLite.dll::CabExtract reports completion [code=00000004]
15:13:44  -     MD5 Hash = 2b8842dc7961f6f86eca96d803a51644
15:13:44  - Extracting Kels_RegUnReg_addon_v11.cab
15:13:44  -     CabLite.dll::CabExtract reports completion [code=00000003]
15:13:44  -     MD5 Hash = 976f78adefa3b2c1c259b531dbb57d43
15:13:44  - Extracting Kels_Runtimes_addon_v8.6.2.7z
15:13:45  -     MD5 Hash = c9b6383414932a679f130163a2251a63
15:13:45  - Extracting Kels_Unicode2008_v1.626.6002.16489_addon.rar
15:13:46  -     MD5 Hash = 50701765e95cb422e0a2cfec281bf1d8
15:13:46  - Extracting Microsoft_Silverlight_5.1.20513.0_Addon.7z
15:13:47  -     MD5 Hash = 407b603e45ae5e8d27b81b0c7db056de
15:13:47  - Extracting Microsoft_UPHC-Service_1.6g_Addon.cab
15:13:47  -     CabLite.dll::CabExtract reports completion [code=00000002]
15:13:47  -     MD5 Hash = ba63a9a238f8eaea02bd72b80c8e1528
15:13:47  - Extracting MrsP_Cabinet_Tools_SDK_Combo_Addon_v121.cab
15:13:47  -     CabLite.dll::CabExtract reports completion [code=00000003]
15:13:47  -     MD5 Hash = 65d15485ae32b0592d2fc33f8e92387b
15:13:47  - Extracting MrsP_Disable_WinPicFax_Addon_v13-070825.cab
15:13:47  -     CabLite.dll::CabExtract reports completion [code=00000002]
15:13:47  -     MD5 Hash = 53ef4e535beb62643d32cc994cfedd64
15:13:47  - Extracting OnePiece_IE8_WinXPSP3_v4.5.0_AddOn_ENU.7z
15:13:49  -     MD5 Hash = d5dca91ec873afac54aa40b614fcd993
15:13:49  - Extracting OnePiece_Microsoft.NET_Framework_v1.1.4322.2503_True_AddOn_ENU.cab
15:13:49  -     CabLite.dll::CabExtractAsync reports completion [code=00000007]
15:13:49  -     MD5 Hash = 18a2c471618924589568631e4f7bb4eb
15:13:49  - Extracting OnePiece_Microsoft.NET_Framework_v3.5.30729.4056_True_AddOn_ENU.cab
15:13:50  -     CabLite.dll::CabExtractAsync reports completion [code=00000007]
15:13:50  -     MD5 Hash = 2fdd94e2f80022aecf1655f7ee15e3ca
15:13:50  - Extracting OnePiece_Microsoft.NET_Framework_v3.5.30729.7056_QFE_Update_AddOn.7z
15:13:53  -     MD5 Hash = 537dfe5608145b7f8c098fdc303f4b28
15:13:53  - Extracting OnePiece_Microsoft.NET_Framework_v4.0.30319.1016_True_AddOn_ENU.cab
15:13:54  -     CabLite.dll::CabExtractAsync reports completion [code=00000003]
15:13:54  -     MD5 Hash = 9ec75fa303a1a643ab31dd0d4d984e21
15:13:54  - Extracting PatchAddon_HIVESYS-1680x1050.7z
15:13:54  -     MD5 Hash = 0f979f29cd2b91d7b2e53b94dc8a0e63
15:13:54  - Copying RedDXManagedCode_Addon_1.1.0.exe
15:13:54  -     MD5 Hash = b3b44aaca531ecc745eae0643b1fba42
15:13:54  - Extracting Ricks_RecycleBin_SMD_AddOn_v0.6.rar
15:13:54  -     MD5 Hash = 9dc8d6bcfa9dbd00b7949829ba34217d
15:13:54  - Extracting RogueSpearAddonsInstallShieldScript.zip
15:13:55  -     MD5 Hash = d072331455b02c1928a2a203ab1aacc8
15:13:55  - Extracting RogueSpearAddonsUpdateLiteXPSP3_3.5.5.7z
15:13:57  -     MD5 Hash = 1d33e752e7b50ff3b7b2a11a48c31d83
15:13:57  - Extracting RVMAddons_2.0.0_UH.7z
15:13:57  -     MD5 Hash = c965b0ac0218ebfc50b3bd1efd3c3c35
15:13:57  - Copying Visual_Basic_C++_F#_J#_Redistributable_AIO_x86_x64.exe
15:13:58  -     MD5 Hash = 5f0ca9f592fe0d34557e1f97f307ea13
15:13:58  - Extracting WScript57-100-Addon.7z
15:13:58  -     MD5 Hash = 6264ba1c5655f1878bb8215ee801ad0c
15:13:58  - Extracting xable_WGAN-v1.4_addon.cab
15:13:58  -     CabLite.dll::CabExtract reports completion [code=00000006]
15:13:58  -     MD5 Hash = b243c0ef34d790903b7b7b8f6ddd3fd6
15:13:58  - Clearing any Read Only Attributes.
15:13:59  - 
15:13:59  - ERROR: Service pack level of destination is too high for chosen update pack.  <------  stopped here
15:13:59  - Notifying user and terminating program with exit code 1...

Service Pack error: The service pack level of the source is too high for the update pack you are attempting to integrate. Integration failed.

Log Shutdown @ 2013-10-25 15:15:38 local time.


#2 Test - Without update pack but same addons as above:

2013-10-25_15.17.23
Log Startup @ 15:17:23 local time, on October 25, 2013.

Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.6.1 beta2.1

"G:\RyanVM\RVM_Integrator_1.6.1b2.1.exe" 

15:17:23  - English - Windows XP Professional x86 - Retail SP4 Found
15:18:20  - English - Windows XP Professional x86 - Retail SP4 Found
15:18:20  - 
15:18:20  - Source Location      = F:\Windows XP Pro #1 with SP4M2 Test
15:18:20  - Destination Path     = W:\XPPro#1Integrated
15:18:20  - Destination Size     = 460.18 GB
15:18:20  - Working Directory    = W:\XPPro#1Integrated\I386
15:18:20  - Temp Directory       = W:\XPPro#1Integrated\I386\rvmtemp
15:18:20  - 
15:18:20  - Starting Integration
15:18:20  - 
15:18:20  - Copying Files To The Destination Directory.
15:18:20  -   Copying Working Directory...
15:18:27  - 6789  Files Copied in 6 Seconds
15:18:27  -   Copying \CMPNENTS\ Directory...
15:18:27  - 91  Files Copied in 0 Seconds
15:18:27  - 
15:18:27  - Checking Destination For OS Type.
15:18:27  - English - Windows XP Professional x86 - Retail SP4 Found
15:18:27  - <--------  stopped here        

AutoIt Error: Line -1: Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded. OK > Exited from RyanVMi.


#3 Test - WMP11 Slipstreamer 1.4.3.0 - successful - log files not created by the WMP11 Slipstreamer.

#4 Test - DriverPacks BASE 11.09.012 - successful - log files rather large (can be provided if needed):

#5 Test - Started RVM Integrator 1.6.1b2.1 to make ISO - successful - log file below:

2013-10-25_15.47.16
Log Startup @ 15:47:16 local time, on October 25, 2013.

Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.6.1 beta2.1

"G:\RyanVM\RVM_Integrator_1.6.1b2.1.exe" 

15:47:16  - English - Windows XP Professional x86 - Retail SP4 Found
15:47:49  - 
15:47:49  - Creating ISO
15:47:49  - Command Line = D:\Windows\Take Command\TCC.exe /c D:\WINDOWS\System32\rvmisofs.exe -joliet-long -iso-level 2 -N -d -relaxed-filenames -duplicates-once -D -boot-load-seg 0x7C0 -boot-load-size 4 -o "W:\XPPro#1ISO\XPPro#1wSP4WMP11DPav.iso" -b rvmintegrator.img -hide rvmintegrator.img -hide boot.catalog -J -hide-joliet xpboot.img -hide-joliet boot.catalog -no-emul-boot -volid "XPProwSP4WMP11Integ" -sysid "Win32" "G:\Windows XP Pro #1 with SP4M2 Test"
15:47:49  - Using Internal mkisofs 2.01-bootcd.ru (i686-pc-mingw32)
15:48:13  - Total translation table size: 2048
15:48:13  - ISO Complete

Log Shutdown @ 2013-10-25 15:48:29 local time.

XPPro#1wSP4WMP11DPav.iso created at size: 1,210,175,488

User avatar
5eraph
Site Admin
Posts: 4618
Joined: Tue Jul 05, 2005 9:38 pm
Location: Riverview, MI USA

Post by 5eraph » Sat Oct 26, 2013 1:25 am

I'd be interested in seeing integrator.ini and trying to reproduce the problem here.

User avatar
Kelsenellenelvian
Moderator
Posts: 4383
Joined: Tue Nov 30, 2004 8:32 pm
Location: Pocatello, ID
Contact:

Post by Kelsenellenelvian » Sat Oct 26, 2013 2:57 am

Service Pack error: The service pack level of the source is too high for the update pack you are attempting to integrate. Integration failed.


The above one is caused by a part of the entries files the specifies that the addon is for sp3

User avatar
bphlpt
Posts: 1351
Joined: Sat Apr 19, 2008 1:11 am

Post by bphlpt » Sat Oct 26, 2013 5:33 am

So rather than require all addons to be rewritten to allow installation on SP4, it looks like SP4 needs to identify itself as SP3?

Cheers and Regards

User avatar
5eraph
Site Admin
Posts: 4618
Joined: Tue Jul 05, 2005 9:38 pm
Location: Riverview, MI USA

Post by 5eraph » Sat Oct 26, 2013 6:38 am

Most addons do not specify a required service pack level. No rewriting should be necessary, bphlpt. Update packs should always specify SP level because the file updates contained therein should match that level.
Last edited by 5eraph on Sat Oct 26, 2013 6:38 am, edited 1 time in total.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Sat Oct 26, 2013 6:38 am

I had tried it, but it wouldn't slipstream on top of SP3 disk.
I will re-try it today.

Note: Royale theme, IMAPI2, MSI45 fully integrated

UPDATE: It works using the integrate switch, I will retry with nLite. If there are no problems, I will update the SP version in every dosnet.inf file.

UPDATE #2: It works with nLite,too, so the only thing we need to discuss is the necessity of this change.

(I won't change the disk label in setup files: it will be "Service Pack 4").

Because SP4 won't need any update packs, we can discuss keeping the SP number to 4.0 as a way to prevent integrating update packs to it.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Sat Oct 26, 2013 7:25 am

Just one note: A simple way to overcome the SP version issue in nLite is to temporarily rename the WIN51*.SP4 (for example WIN51IP.SP4 in XP PRO media) file to WIN51*.SP3 while integrating and then rename it back to WIN51*.SP4. Also change to ServicePack number from 4.0 to 3.0 in dosnet.inf -temporarily. I won't change the SP version in M3, but you can try using this workaround. If it doesn't work, please let me know.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Sat Oct 26, 2013 2:11 pm

I started integrating WMP11 and I was wondering where I could find all official WMP11 decoders.

P.S. I noticed that QFECheck is not available at Microsoft Download Center

User avatar
5eraph
Site Admin
Posts: 4618
Joined: Tue Jul 05, 2005 9:38 pm
Location: Riverview, MI USA

Post by 5eraph » Sat Oct 26, 2013 4:01 pm

The latest known version of QFECheck (v6.2.29.0) was from the Microsoft Product Support Reporting Tool. It seems all versions have been retired from the download center. The x86 binary can be found in any of the current update packs from OnePiece (XPx86,2k3x86) and user_hidden (XPx86), and in Xable's addon. My pack (XPx64) has the x64 binary.

tomasz86
Posts: 491
Joined: Tue Aug 09, 2011 12:12 pm
Location: windowsarchives.com
Contact:

Post by tomasz86 » Sat Oct 26, 2013 10:40 pm

5eraph wrote:The latest known version of QFECheck (v6.2.29.0) was from the Microsoft Product Support Reporting Tool. It seems all versions have been retired from the download center. The x86 binary can be found in any of the current update packs from OnePiece (XPx86,2k3x86) and user_hidden (XPx86), and in Xable's addon. My pack (XPx64) has the x64 binary.
https://web.archive.org/web/20070222195 ... PT_PFE.EXE

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Sun Oct 27, 2013 1:11 am

Would it really be difficult for the Update Pack creator(s) to edit the entries.ini so that there are no compatibility issues with this user created SP4?

Seems to me that would be the easier solution to the problem I encountered. I assume that once SP4 goes final it is not going to be updated every month to coincide with patch Tuesday but will depend on Update Packs being created every month, as happens now.

Or did I miss something in all of the above discussions about SP4 itself??

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Sun Oct 27, 2013 1:16 am

5eraph wrote:I'd be interested in seeing integrator.ini and trying to reproduce the problem here.
@5eraph

I'm assuming the other postings here satisfied your interest about my integrator.ini - but you did ask about other .ini files here: http://www.ryanvm.net/forum/viewtopic.php?t=10352 which I did post.

User avatar
mf3imp
Posts: 77
Joined: Sun Nov 11, 2007 3:15 pm

Post by mf3imp » Sun Oct 27, 2013 3:17 am

ChiefZeke wrote:I assume that once SP4 goes final it is not going to be updated every month to coincide with patch Tuesday but will depend on Update Packs being created every month, as happens now.
Or did I miss something in all of the above discussions about SP4 itself??
By april of next year there will be no more patch for xp, so sp4 will become definitive version very soon, and will certainly include all post-sp3 patch released, so I do not see the need to adapt current update pack to sp4. Basically, when there was the simultaneous presence of sp2 and sp3, Ryan himself mantain two different update packs, as it should be, each specific to the version that was intended for.

tomasz86
Posts: 491
Joined: Tue Aug 09, 2011 12:12 pm
Location: windowsarchives.com
Contact:

Post by tomasz86 » Sun Oct 27, 2013 7:15 am

mf3imp wrote: By april of next year there will be no more patch for xp.
I don't think so. Last official updates for Windows 2000 were released just a few months ago, 3 years after the official support ended.

There will certainly be at least several more updates prepared for XP too, released either semi-officially (through the monthly ISO packages) or leaked from companies paying for the extended support.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Sun Oct 27, 2013 3:33 pm

Thanks for the link, tomasz86. I'll take a look at it very soon.

Right now, I'm working intensively on WMP11 integration. There are about 150 files to update, and there needs to be careful integration of User-mode Driver Framework 1.9 - a WMP11 prerequisite - or you'll end up with BSODs. I have just finished referencing the files update.inf, and I'm moving on with registry and processes to run.

I may also include third-party codecs (only after testing them in VM) but this will be done in a second pass.

User avatar
5eraph
Site Admin
Posts: 4618
Joined: Tue Jul 05, 2005 9:38 pm
Location: Riverview, MI USA

Post by 5eraph » Sun Oct 27, 2013 6:49 pm

Good find, tomasz86. :)
ChiefZeke wrote:I'm assuming the other postings here satisfied your interest about my integrator.ini - but you did ask about other .ini files here: http://www.ryanvm.net/forum/viewtopic.php?t=10352 which I did post.
Just replied to that post, where I needed to verify your "Make ISO" settings in RVMi under XPx64 for comparison to my own. Relating to x86 SP4, having your INI would allow me to more accurately duplicate your integration process to find the problem. Information I need to recreate your INI is not provided in a log file.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Mon Oct 28, 2013 4:15 am

@ tomasz86: Have you ever manged to place a composite operator inside another composite operator in update.inf? I want to check whether Media pack is present in N versions of XP.
This is the original XP SP3 text:

Code: Select all

[N.Condition.Section] ;Checks whether this is version N without Media pack.
    OrOp=Non.WMP.Restore.Condition.Section ;Returns true if no SP2 media pack is installed
    ;Try to use a composite operator inside another composite operator
    AndOp=N.FileOp.Condition.Section

[N.FileOp.Condition.Section]
    PresentOp=CheckReg, HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\WindowsFeatures, "N", 0x10001
    NotPresentOp = CheckReg, HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\WindowsFeatures, "Windows Messenger", 0x10001


[Non.WMP.Restore.Condition.Section]
;===These conditionals require updating in order to take the new media pack update number into account.

    NotPresentOp=CheckReg, HKLM, SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB886540, "Installed", 0x10001
    NotEqualOp=CheckReg, HKLM, SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB886540, "Installed", 0x10001,"!=",1
and I want to do this change:

I want to create a composite operator which will return true if the [Non.WMP.Restore.Condition.Section] is true OR if a custom defined section named [Non.WMP.Restore.Condition.SP3.Section] is true.

This will be the code for [Non.WMP.Restore.Condition.SP3.Section]:

Code: Select all

 ;This is the SP3 Media Pack check.
NotPresentOp=CheckReg, HKLM, SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB943604, "Installed", 0x10001
    NotEqualOp=CheckReg, HKLM, SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB943604, "Installed", 0x10001,"!=",1
I don't know how to perform the link. Can you help me?
Thanks in advance.

UPDATE: I tried this code, is it the appropriate?

Code: Select all

[Non.WMP.Restore.Condition.Section]
;===Updated in order to take the SP3 media pack update number (KB943604) into account.
    OrOp=N.SP2MedPack.Condition.Section
    OrOp=N.SP3MedPack.Condition.Section

[N.SP2MedPack.Condition.Section] ;Return true if SP2 media pack is not present
    NotPresentOp=CheckReg, HKLM, SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB886540, "Installed", 0x10001
    NotEqualOp=CheckReg, HKLM, SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB886540, "Installed", 0x10001,"!=",1

[N.SP3MedPack.Condition.Section] ;Return true if SP3 media pack is not present
    NotPresentOp=CheckReg, HKLM, SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB943604, "Installed", 0x10001
    NotEqualOp=CheckReg, HKLM, SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB943604, "Installed", 0x10001,"!=",1

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Tue Oct 29, 2013 7:34 am

UPDATE: It's not working. svcpack.log shows this error:
"Unknown instruction OrOp in section Non.WMP.Restore.Condition.Section".

Any ideas to solve this problem?

UPDATE#2 : Probably I'll manage this with a custom app or dll.

NEWS: Tested WMP11 on XP SP3 PRO live installation/uninstallation. A few flaws were found. Most important, in order to use WMP11 you have to log off and then log back on after completing SP4 installation.

I'll fix this flaw plus a few others and then will post back.

UPDATE#3: These flaws have been fixed (and some other bugs from M2 release seem to be gone too). The only thing I still need to take care of is the SP3 N Media Pack. I will also start working on CD-ROM installations.

I haven't yet decided whether I should release an XP SP4 M3 now, or after integrating MCE2005 UR2 + .NET1.1 SP1 RTM.

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Tue Oct 29, 2013 5:01 pm

5eraph wrote:I'd be interested in seeing integrator.ini and trying to reproduce the problem here.
Here: [Settings]
CMPNENTS=F:\Windows XP Pro #1 with SP4M2 Test\CMPNENTS
Source=F:\Windows XP Pro #1 with SP4M2 Test
Destination=W:\XPPro#2Integrated
UpdatePack=G:\RyanVM\XPSP3_QFE_UpdatePack_20131008.7z
ExternalRun=G:\WMP11 Slipstreamer\WMP11Slipstreamer.exe
ParametersRun=
IsoFile=W:\XPPro#2ISO\XPPro#2wSP4WMP11DPav.iso
IsoVolume=XPPro#2wSP4WMP11DPInteg
IsoExtTool=
IsoExtCmd=
IsoIntExt=Internal
IsoCmdLine=mkisofs

[Switches]
Optimize=1
SaveSettingsOnExit=4
AudibleAlert=1
IKnowWhatImDoing=1
Cached=4
ExitBeforeINT=4
ExternalCMD=4
ProgramOnExit=1
ProgramOnExitHot=1
AdvancedDB=4

[AddonPacks]
YumeYao_WIC_Update_Addon_1_2_0.cab=G:\RyanVM\Addons - Pro
5er_KB893056_SP3_Addon.7z=G:\RyanVM\Addons - Pro
DirectXRuntimes-201006-Addon-32.cab=G:\RyanVM\Addons - Pro
Doug_Accessibility_AddOn_v13.rar=G:\RyanVM\Addons - Pro
ENU_Addons_BVProSvcDescriptions_1.5.2.7z=G:\RyanVM\Addons - Pro
Jondar_RegeditCPL_Addon_v1.0.cab=G:\RyanVM\Addons - Pro
Kels_DirectX_CPL_addon_v90c.cab=G:\RyanVM\Addons - Pro
Kels_MS_MSICleaner_addon_v44.cab=G:\RyanVM\Addons - Pro
Kels_MSConfig_addon_v11.cab=G:\RyanVM\Addons - Pro
Kels_RegUnReg_addon_v11.cab=G:\RyanVM\Addons - Pro
Kels_Runtimes_addon_v8.6.2.7z=G:\RyanVM\Addons - Pro
Kels_Unicode2008_v1.626.6002.16489_addon.rar=G:\RyanVM\Addons - Pro
Microsoft_Silverlight_5.1.20513.0_Addon.7z=G:\RyanVM\Addons - Pro
Microsoft_UPHC-Service_1.6g_Addon.cab=G:\RyanVM\Addons - Pro
MrsP_Cabinet_Tools_SDK_Combo_Addon_v121.cab=G:\RyanVM\Addons - Pro
MrsP_Disable_WinPicFax_Addon_v13-070825.cab=G:\RyanVM\Addons - Pro
OnePiece_IE8_WinXPSP3_v4.5.0_AddOn_ENU.7z=G:\RyanVM\Addons - Pro
OnePiece_Microsoft.NET_Framework_v1.1.4322.2503_True_AddOn_ENU.cab=G:\RyanVM\Addons - Pro
OnePiece_Microsoft.NET_Framework_v3.5.30729.4056_True_AddOn_ENU.cab=G:\RyanVM\Addons - Pro
OnePiece_Microsoft.NET_Framework_v3.5.30729.7056_QFE_Update_AddOn.7z=G:\RyanVM\Addons - Pro
OnePiece_Microsoft.NET_Framework_v4.0.30319.1016_True_AddOn_ENU.cab=G:\RyanVM\Addons - Pro
PatchAddon_HIVESYS-1680x1050.7z=G:\RyanVM\Addons - Pro
RedDXManagedCode_Addon_1.1.0.exe=G:\RyanVM\Addons - Pro
Ricks_RecycleBin_SMD_AddOn_v0.6.rar=G:\RyanVM\Addons - Pro
RogueSpearAddonsInstallShieldScript.zip=G:\RyanVM\Addons - Pro
RogueSpearAddonsUpdateLiteXPSP3_3.5.5.7z=G:\RyanVM\Addons - Pro
RVMAddons_2.0.0_UH.7z=G:\RyanVM\Addons - Pro
Visual_Basic_C++_F#_J#_Redistributable_AIO_x86_x64.exe=G:\RyanVM\Addons - Pro
WScript57-100-Addon.7z=G:\RyanVM\Addons - Pro
xable_WGAN-v1.4_addon.cab=G:\RyanVM\Addons - Pro

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Tue Oct 29, 2013 5:06 pm

harkaz wrote: UPDATE#3: These flaws have been fixed (and some other bugs from M2 release seem to be gone too). The only thing I still need to take care of is the SP3 N Media Pack. I will also start working on CD-ROM installations.

I haven't yet decided whether I should release an XP SP4 M3 now, or after integrating MCE2005 UR2 + .NET1.1 SP1 RTM.
XP SP4 M3 now please. I'll guess there are not than many MCE users and we could be testing your update without it in the meantime.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Wed Oct 30, 2013 3:25 am

OK, Chiefzeke I will release M3 after finishing WMP11 integration.

I still have a problem with update.exe patching. I may need your help. You can test XP SP4 uninstallation on various configurations and see when you can't uninstall it.

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Wed Oct 30, 2013 4:53 pm

harkaz wrote: I still have a problem with update.exe patching. I may need your help. You can test XP SP4 uninstallation on various configurations and see when you can't uninstall it.
Harkaz
Have yet to install your SP4 on an installed version of XP, only been trying to slipstream SP4 into XP w/SP3 source and then testing Addons, etc.

I was not aware you had tested SP4 on an installed system and/or were ready for others to try to do the same - am leery of corrupting my installed XP. 8)

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Wed Oct 30, 2013 6:38 pm

Every XP SP4 Milestone has been tested on a live system. Since M2, live installation completes flawlessly on all possible upgrade paths. However, uninstallation may not be possible because the update.exe has been patched to accept the unsigned update.inf file, and thus fails to create uninstall INF file on some configurations.

If you haven't tested it yet on live system, wait for M3 release. I'm almost done with WMP11 integration.

tomasz86
Posts: 491
Joined: Tue Aug 09, 2011 12:12 pm
Location: windowsarchives.com
Contact:

Post by tomasz86 » Thu Oct 31, 2013 3:08 am

@harkaz Those conditional statements can get complicated as hell... You probably need to use the ProductInstall.ExtendedConditional and ExtendedConditional.Declare sections. I experimented with it some time ago but don't really remember all the details (and there's absolutely no documentation available anywhere).

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Thu Oct 31, 2013 12:42 pm

XP SP4 M3 is almost ready. Some final tests, update.ver updating and packaging is left.

UPDATE: It seems that the update.exe failure to create INF for uninstaller happens due to the great size of update.inf. XP SP4 M3 will not be uninstallable on configurations that allowed removal in previous Milestone releases.

The message that would be shown (I have patched update.exe not to show this) is: "The data area passed to a system call is too small".

In the next days I will publuish the disassembly from IDA of the relevant function.

I will need your help increasing the buffer size and enabling uninstallation on all configurations.
For the moment, XP SP4 M3 cannot be uninstalled once installed on a live system. It will be uploaded very soon.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Fri Nov 01, 2013 8:54 am

Some really good news: I have completely fixed the SP4 uninstallation issue :)

XP SP4 M3 has been finalised and receives final testing. It will be available for download and testing in a few hours.

User avatar
ELiTE
Posts: 12884
Joined: Sun Apr 08, 2007 8:33 pm
Location: Canada

Post by ELiTE » Fri Nov 01, 2013 9:14 am

harkaz wrote:XP SP4 M3 has been finalised and receives final testing. It will be available for download and testing in a few hours.
Just like to congratulate you on an excellent piece of work. You started out with a great idea and turned it into a functioning reality. Just amazing.............. 8)
By downloading an ELiTE Switchless Installer Addon you, the End User, agree to abide by any Terms of Use prescribed by the Freeware App contained within.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Fri Nov 01, 2013 4:21 pm

@Elite Thanks a lot for your support!
I want to inform you that I'm fixing some final flaws in Upgrade installations from XP SP4 CD-ROM. XP SP4 M3 fixes these issues for the first time and thus XP SP4 M3 download availability will be delayed.

Previously, XP SP4 would not update IE and WMP program files during the upgrade process from a previous version of Windows XP.

User avatar
bphlpt
Posts: 1351
Joined: Sat Apr 19, 2008 1:11 am

Post by bphlpt » Sat Nov 02, 2013 11:48 am

I just wanted to admit that when we were talking about certain folders not being needed for any reason, that I had forgotten about two files in WINNTUPG being needed under certain circumstances, NETMAP.INF & NETUPGRD.DLL.
Siginet wrote:It isn't a big deal to delete those. But basically if you delete them you would get an error message when you try to start a windows install from within windows (not booting to the disk).
Also I think they are needed if you want to be able to install the recovery concle from your slimmed down disk. ;)
You can read the whole story in this thread.

Your SP4 still shouldn't care whether they are there or not, but you might want to put a note in your ReadMe when you distribute it so the user can make an informed decision.

Cheers and Regards

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Sat Nov 02, 2013 3:02 pm

@bphlpt: That's interesting, I didn't know about it. Probably I'll include this in SP4 documentation.

Good news: I tested Upgrade from previous XP versions to XP SP4 and it works fine. I also fixed some issues related to WMP11 playlists not being available after install.

Now, I'm fixing a minor flaw in SP4 package uninstallation: Some locales which were not available prior to SP3, prevented its uninstallation. Now SP4 will not show the relevant error message, if it has been installed on top of SP3.

This, along with a custom dotnetfx\setup.exe bootstrapper, completes the XP SP4 M3 package.

scarface
Posts: 490
Joined: Sat Aug 02, 2008 7:25 am
Location: paris

Post by scarface » Sat Nov 02, 2013 5:30 pm

I tested sp4 M1 in vm, both integrated and installed, noticed no glitch. would be suitable to add windows update agent though...
sad youre not interested in windows 8.1 lite...
Probably next year I will prepare an exceptional version of windows 7 ultralite. Your help to bypass the sysprep limitation has been essential.
http://www.youtube.com/watch?v=FUyG68RLrTs

User avatar
Kelsenellenelvian
Moderator
Posts: 4383
Joined: Tue Nov 30, 2004 8:32 pm
Location: Pocatello, ID
Contact:

Post by Kelsenellenelvian » Sat Nov 02, 2013 9:01 pm

scarface wrote:I tested sp4 M1 in vm, both integrated and installed, noticed no glitch. would be suitable to add windows update agent though...
sad youre not interested in windows 8.1 lite...
Probably next year I will prepare an exceptional version of windows 7 ultralite. Your help to bypass the sysprep limitation has been essential.
http://www.youtube.com/watch?v=FUyG68RLrTs
If you do don't share it here that falls under the warez category

(Sharing a whole modified iso)

scarface
Posts: 490
Joined: Sat Aug 02, 2008 7:25 am
Location: paris

Post by scarface » Sat Nov 02, 2013 9:39 pm

Why would I want to share it? One tester like the specialist harkaz Is enough. Besides I dont have an internet line any longer, i cant do it. Im connecting on hotspots whenever I can find a code.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Sun Nov 03, 2013 8:31 am

Finished updating the SP4 uninstallation conditions.
I just noticed a glitch of the live installation version, also presnet in M2: No thumbnail icons show up in Windows Explorer after live SP4 install.

I'm trying to figure out what's going wrong (something related to Windows shell).

@scarface I'm looking forward to testing your new 7 Ultra lite version.

UPDATE: Just noticed that browseui.dll does not get updated by the SP4 installer. I wil try to fix this as well.

UPDATE#2: I ensured that all shell-related files get updated during Windows XP SP4 live install. However, the problem persists. In addition, trying to view picture thumbnails makes explorer.exe to crash.
This is not the case with CD-ROM installations, this happens only with live installs.

UPDATE #3: Issue fixed. Now , a final issue from M2 to take care of: WU/MU are not available from Start menu after SP4 uninstall.
It's interesting that WU/MU run properly after uninstall reboot - until all processes have been executed. Then, suddenly, WU cannot be launched from the Start menu.

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Mon Nov 04, 2013 1:30 pm

Windows XP SP4 Milestone 3 is ready!

Windows XP SP4 M3 fixes all previously known bugs, enhances SP4 reliability and adds new features to the service pack.

This release includes:

- Internet Explorer 8 RTM without any updates
- Windows Update Agent 7.6.7600.256
- Windows Media Player 11 with all updates till today.
These updates are: KB954155, KB973540, KB974905, KB975558, KB978695, KB2378111, UMDF 1.9 Update (this last update is also installed in N versions of Windows XP).
- Windows Royale color scheme
- Windows Messenger removed
- IMAPI2 (KB932716 v2)
- Windows Installer 4.5 (KB942288 v3)


Some notes about installation: Install Windows XP SP4 on top of SP1/SP2/SP3 live systems or integrate in XP RTM/SP1/SP2/SP3 media. To integrate in K,KN,N media, you have to create a special tag file in the Windows share directory (which contains the original installation media fies) before slipstreaming the service pack to inform the SP installer that this is a K,KN,N source). Create empty tag file named:

WIN51NIC for Windows XP Home N
WIN51NIP for Windows XP Prof N
WIN51KNIC for Windows XP Home KN
WIN51KNIP for Windows XP Pro KN

It is recommended, however, that you install SP4 from its executable on these systems.

For Windows N, you can install Media Packs. These Media Packs add WMP9 functionality. After installing the appropriate pack for the SP version you're running, run SP4 installer. The installer should automatically update WMP9 to WMP11.

Windows XP SP4 M3 can be installed and uninstalled in all Windows XP Builds: Home, Professional, K, KN, N, Starter. Its use is not recommended with MCE, however, because M3 does not include updated MCE components.
Milestone 4 will include MCE 2005 Update Rollup 2 + .NET Framework 1.1 SP1.

Download link: https://drive.google.com/file/d/0B7k-l_ ... sp=sharing
Size: 346 MB
MD5: E8256B3D9336C9A1F5BEF6F10EE19E75

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Mon Nov 04, 2013 4:06 pm

On a live system after SP4 is installed - any error messages/anomalies when you go to the Microsoft/Windows Updates site(s) and your sysytem is scanned? Any issues with other Microsoft products like Office, etc?

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Mon Nov 04, 2013 4:11 pm

@Chiefzeke: You still need to install the latest IE8 cumulative update to run Windows Update - this is not an XP SP4 bug. From next Milestone, I will start including the latest cumulative IE8 update.
No incompatibilities with other Microsoft products are known at this moment.

There were LOTS of flaws from previous milestones that have been fixed in this one. It was a bit exhausting to fix them all.

ChiefZeke
Posts: 767
Joined: Fri Mar 23, 2007 5:33 pm
Location: Victorville, California

Post by ChiefZeke » Mon Nov 04, 2013 4:42 pm

harkaz wrote:@Chiefzeke: You still need to install the latest IE8 cumulative update to run Windows Update - this is not an XP SP4 bug. From next Milestone, I will start including the latest cumulative IE8 update.
No incompatibilities with other Microsoft products are known at this moment.

There were LOTS of flaws from previous milestones that have been fixed in this one. It was a bit exhausting to fix them all.
Having IE8 with all updates already installed on both my #1 and #2 systems then, if I install SP4 M3 as a test I could then go to the Updates page and not experience any problems - as far as you know. :)

harkaz
Posts: 693
Joined: Fri Nov 16, 2012 10:23 am
Location: GR
Contact:

Post by harkaz » Mon Nov 04, 2013 5:20 pm

I haven't tested that. Probably the SP4 will revert the IE8 back to IE8 RTM, but I'm not sure. In any case, backup your system.

Post Reply