Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


harkaz

Member
  • Content Count

    240
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

43 Excellent

About harkaz

  • Rank
    Windows XP SP4 Developer

Profile Information

  • OS
    Windows 7 x64
  • Country

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Use the GH0stpak, as described in the RyanVM forum, in order to update your system. The May 2019 update pack is intended for new installations of WIndows XP from updated media.
  2. 1. In a Windows XP environment, extract/copy the contents of XP SP0/SP1/SP2/SP3 original media to an empty folder: C:\XPMEDIA. 2. Run this command from command line: WindowsXP-USP4-v3.1b-x86-ENU.exe /integrate:C:\XPMEDIA 3. As soon as 2 is complete, extract the update pack zip to a blank new folder named C:\updpack 4. Run C:\updpack\slipstream.bat. 5. Paste C:\XPMEDIA to the command line window that appears and press ENTER
  3. UPDATE: SP4 v3 October 2018 MUI Update ISO has been re-uploaded. UPDATE #2: Updated Windows XP Debugging Symbols for May 2019 post-SP4 update pack have been also uploaded. For more information, visit RyanVM.net.
  4. The "Windows XP SP4 MUI October 2018 Update" is the best way to use SP4 in languages other than English (ISO was flagged and no longer available, will re-upload sometime). However, several OS components will not be translated to another language.
  5. Extract zip anywhere you want, then run the .bat file.
  6. UPDATE [June 7, 2019]: Post-SP4 Update Pack released! This final update pack should be applied to Windows XP installation media immediately after slipstreaming SP4 v3.1b to a Windows XP RTM/SP1/SP2/SP3 source. This will update installation media to May 2019, including every single update released until the POSReady 2009 end-of-life in May 2019. Download available at RyanVM.net.
  7. @everyone FYI, new stuff has been released for XP SP4: 1. A SP4 v3.1b installer that does not install .NET Framework unless absolutely necessary (MCE, Tablet PC). 2. Windows XP SP4 Preinstallation Environment and OEM Preinstallation Kit (OPK) with SCSI drivers integrated 3. An updated MUI ISO with fixes and additions. Check my RyanVM thread for details.
  8. UPDATE - 15 OCT 2018: For novice users that do not want to wait for 20-30 minutes after installing XP SP4 AND rebooting For all .NET haters... A NEW RELEASE OF UNOFFICIAL SP4 3.1B WITHOUT .NET FRAMEWORK This release will not install .NET Framework in both live and slipstreamed install, unless: - Media Center Edition is used -> .NET Framework 1.1 SP1 is installed - Tablet PC Edition is used -> .NET Framework 1.0 SP3 is installed Users can still install .NET FWs of their choice from the Add/Remove Components wizard in Control Panel This alternative SP4 release is called: WindowsXP-USP4-v3.1b-NODOTNET-x86-ENU.exe In addition, XP SP4 OEM Preinstallation Kit ISOs with SCSI drivers, and an updated MUI ISO have been released!
  9. Registry settings to import as a .reg file after installing the latest cumulative IE8 update:
  10. You need to manually install the latest cumulative IE8 update and Office updates before scanning for updates. Updates can be downloaded from the Microsoft Update Catalog website (https://catalog.update.microsoft.com). Just search for posready and sort the updates shown in chronological order.
  11. MSI Error 1603: MSI (c) (30:60) [03:46:21:203]: Note: 1: 1708 MSI (c) (30:60) [03:46:21:203]: Product: Java 8 Update 161 -- Installation failed. MSI (c) (30:60) [03:46:21:203]: Windows Installer installed the product. Product Name: Java 8 Update 161. Product Version: 8.0.1610.12. Product Language: 1033. Installation success or error status: 1603. MSI (c) (30:60) [03:46:21:234]: Grabbed execution mutex. MSI (c) (30:60) [03:46:21:234]: Cleaning up uninstalled install packages, if any exist MSI (c) (30:60) [03:46:21:250]: MainEngineThread is returning 1603
  12. Try the offline installer at https://java.com/en/download/manual.jsp UPDATE: Tried that and it's not working. After some quick debugging it seems that there is an access violation exception related to C runtime implementation. ANTIDEBUGGING related stuff. The resource section includes an MSI file, which cannot install for some reason. Using Orca tto see more info.
  13. After applying the convenience rollup to a base SP1 image you will get the ability to run CheckSUR (System Update Readiness Tool) from inside DISM. The command can only be used online and it is the following one: dism /online /cleanup-image /scanhealth You cannot execute this command offline (on an install.wim image file), if that's what you're talking about.
  14. 1. The update.ses manifest file In a few big updates (like service packs) one may notice the presence of an update.ses file. The purpose of this file is to control package target installation state in different servicing stack conditions. For example, you could define a different behaviour when the servicing stack is of a different version, when the update is deployed online or offline. Ses stands for 'session'. This file controls the CBS session manager. Update.ses is digitally signed by the update.cat file. The same file is used to sign update.mum. Example from Windows 7 SP1: <?xml version="1.0" encoding="UTF-8"?> <Session version="1.0"> <Tasks operationMode="OnlineInstall"> ;Actions to take when installing online. <Phase servicingStack="6.1.7601.17514"> ;Prerequisite servicing stack version for update installation. ;Define target state for the specified package. See DISMAPI Documentation for supported installation states. <package id="Package_for_KB976902~31bf3856ad364e35~amd64~~6.1.1.17514" targetState="Installed"/> </Phase> <Phase exclusive="AllowPending"> <package id="Windows7SP1-KB976933~31bf3856ad364e35~amd64~~6.1.1.17514" targetState="Installed"/> </Phase> </Tasks> <Tasks operationMode="OnlineUninstall"> ;Actions to take when update is being uninstalled. <Phase exclusive="AllowPending"> <package id="Windows7SP1-KB976933~31bf3856ad364e35~amd64~~6.1.1.17514" targetState="Absent"/> </Phase> </Tasks> <Tasks operationMode="OfflineInstall"> <Phase> <package id="Windows7SP1-KB976933~31bf3856ad364e35~amd64~~6.1.1.17514" targetState="Absent"/> </Phase> </Tasks> <Tasks operationMode="OfflineUninstall"> <Phase> <package id="Windows7SP1-KB976933~31bf3856ad364e35~amd64~~6.1.1.17514" targetState="Absent"/> </Phase> </Tasks> </Session> 2. It is not essential to have a package container manifest (_manifest_.cix.xml) if there are no deltas in the update package. If there is no point in creating deltas (e.g. IE11 install package), because this will not save any disk space, then there is no need for adding such a manifest. The payload (files) each MANIFEST file copies to the system is stored in a FOLDER that has exactly the same name as its respective manifest: For example, all files copied by amd64_aagwrapper_31bf3856ad364e35_6.1.7601.17514_none_dd3e751b9f413882.manifest are stored in the directory amd64_aagwrapper_31bf3856ad364e35_6.1.7601.17514_none_dd3e751b9f413882 inside the update package root directory. In this case the sourceName in the MANIFEST file has to be defined explicitly: <file name="agilevpn.sys" destinationPath="$(runtime.drivers)\" sourceName="agilevpn.sys" sourcePath=".\" importPath="$(build.nttree)\"> <securityDescriptor name="WRP_FILE_DEFAULT_SDDL" /> <asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2"><dsig:Transforms xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" /></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha256" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" /><dsig:DigestValue xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">YscNoSf0j3lviJe7+iOrbrCAzJI/Dwkd+jhKk/XJDKE=</dsig:DigestValue></asmv2:hash></file>
  15. More details about the MUM/ Manifest connection: Some MUM files in the MUM chain may contain references similar to these: ;Create an 'update': a top-level 'bundle' to connect MUM with MANIFEST. <update description="wvpchbus_inf" displayName="wvpchbus_inf" name="INF_wvpchbus"> <applicable disposition="detect"> <detectUpdate> <parent name="wvpchbus_inf"/> ;No prerequisites </detectUpdate> </applicable> <component> <assemblyIdentity buildType="release" language="sv-SE" name="wvpchbus.inf-LanguagePack" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="7.1.7600.16393" versionScope="nonSxS"/> </component> </update> This section is responsible for linking the component (MANIFEST) named amd64_wvpchbus.inf-languagepack_31bf3856ad364e35_7.1.7600.16393_sv-se_e01330253ba0e3cd.manifest with the specific MUM file. So, apart from the CAT connection, there is also a link inside the MUM itself. The specified MANIFEST file, in turn, is a trigger for another MANIFEST file, referenced as dependency: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <?Copyright (c) Microsoft Corporation. All rights reserved.?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved." manifestVersion="1.0"> <assemblyIdentity buildType="release" language="sv-SE" name="wvpchbus.inf-LanguagePack" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="7.1.7600.16393" versionScope="nonSxS"/> <deployment/> <dependency discoverable="no"> <dependentAssembly dependencyType="install"> <assemblyIdentity buildType="release" language="sv-SE" name="wvpchbus.inf.Resources" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" version="7.1.7600.16393" versionScope="nonSxS"/> </dependentAssembly> </dependency> <rescache xmlns="urn:schemas-microsoft-com:rescache.v1"/> </assembly> This dependency contains everything we've seen previously (file copying, driver install, etc.). Everything is triggered from a single MUM file. It seems it's rather complicated after all. I'll continue to search for patterns in Windows Update packages and report anything significant here.
×
×
  • Create New...