RyanVM.net Discussion Board

harkaz

Sorry for the delay, guys. It's also an exam period, so I cannot focus on this project constantly.

But I have been able to fully test RDP for the first time:

XP Mode is working fine
I connected two VMs (one with sp4, one with sp3 and everything plays just fine).

harkaz

Some final tests before distributing v3.1.

Checking K/KN versions.

The Product key modification tool for XP SP4 has been prepared.

harkaz

NEWS: Building a product key change tool from the Microsoft one so that is compatible with SP4 v3.1. The MUI pack for XP SP4 Professional will be ready soon. Wait a few more hours for the full upload I recommend downloading the entire v3.1 package along with the accessories, but there will be an INF...

harkaz

wmic is fine. This happens only the first time wmic is run and it's not affected by xpfixit.inf.

harkaz

Thanks for reporting the issue, tipoole, I will fix the checksums of the hal*.dll files once again and then release the SP4 v3.1

harkaz

SP4 v3.1 will be delayed until this is clarified. Have to sleep.

harkaz

What is the error you get?

harkaz

That's a good idea, GH0st. I updated the file but it will be uploaded in a while.

harkaz

Tonight I will start uploading the 3.1 and the new extra files to somewhere else. (PAE patch is not changed in v3.1) I'll keep it in mind thank you. The netfx35_showupdates.zip will be deprecated in the 3.1 version. Instead there will be a netfx35_hideupdate.zip which will hide the updates Hope I do...

harkaz

@tipoole That's what's the 4 GB PAE patch is for.
Just copy-paste to the slipstreamed ISO.

I keep Version 2014 for "historic" purposes.

harkaz

@Mirza Wait for v3.1 it should fix some issues. What patch do you mean? You should run a reg file to get all SP4 v3 fixes, which I will upload soon. These issues are related with SP4 security enhancements (they don't always work well, do they?) . @poolside It should be possible (the ocmandold.dll is...

harkaz

GH0st reported a small issue with DX registration in CD-ROM installs. I'll fix everything as soon as he finishes testing.

harkaz

An additional note about the MUI: You need to add language-specific version of the xpsp4res.dll as well. I might do this part for you, Dibya. WUA 3.0 MUI is already included in SP4. Onepiece does has .NET FW 3.5 and 4.0 MUIs, don't know about 1.1 .NET 1.0 language resources are pre-included in SP4. ...

harkaz

TXTSETUP guide: http://www.msfn.org/board/topic/127677-txtsetupsif-layoutinf-reference/ Do not update the live installer, it's really a waste of time. I recommend creating a post-SP4 update pack, like the November 2014 for v2. You need to update syssetup.inf, qfecheck.inf with generic update-specifi...

harkaz

And while you're working on it, Dibya, you might also want to add MUI support to the XP SP4 addons. I have already: XP MUI -generic XP MUI for SP3 IE8 MUI WMP11 MUI WUA (Windows Update Agent) 3.0 MUI I will upload the MUI files I have, but there are some components left to be added: MSXML 4.0 Window...

harkaz

@Dibya Go for it. We are all looking forward to your update packs.

@GH0st Nothing to worry about as far as the ntfs.sys error is concerned. Let's see how Office 2007 performs.

harkaz

@Data Thanks for pointing this out; I will update the first post accordingly.

Yes, the release notes for v2 are no longer relevant to SP4 v3.

For OC-PATCHES, there is no way to add them via nLite. Simply copy-paste the respective file (compressed inf file) to the \I386 directory.

harkaz

The only reason I removed the .NET from the ARP (marked as system component) is because no more MSI update packages will be released for .NET FW 3.5. You won't need to remove any installed updates and there is no reason to keep it visible. You cannot remove any .NET updates pre-integrated in SP4. Th...

harkaz

Yes, of course, you may use the files for your addon.

harkaz

And that's it, the final SP4 version has been released.

I thank you all for your support all these years. I hope you enjoy Windows XP in the years to come.

harkaz

What's new in version 3.0:

1. POSReady updates until January 2016 have been included
2. 16-bit app emulation issue when installing from slipstreamed CD-ROM has been fixed
3. Fixed the 4GB+ PAE patch
4. Some other minor fixes
5. Fixed the "FP" (false positive) "malware" files in SP4 v2.

harkaz

Legacy (v2) version information: All these files are available under the Legacy folder. 1. Verification info and description 1. WindowsXP-USP4-v2-x86-ENU.exe (recommended) Description: Windows XP SP4 Installer with POSReady Update support Version: 2.0 MD5: CF07D21FFFF544283AEB455CBEBAFF8C SHA1: 95A...

harkaz

@Dibya The IDA Pro will not patch the file, it will give you the offset where the file should be patched. I have been able to test the 4GB patch on SP4 v3 for the first time and it's working! It may feel a bit slower though. Remember you will lose the patch if a future hal/kernel update is installed...

harkaz

The shlwapi.dll bug is that it does not allow changing the Internel and E-mail clieant shown in the start menu from Start menu properties. As for DP, may I recommend customizing the ISO even further: Use Type 1 integration for the basic drivers (SCSI, Network, Chipset). Type 1 has a size limit but i...

harkaz

4 GB Geoff Chappel's patch IDA code: 4GB RAM patch 1. KERNEL a- Patch 1 PAGELK:0056A724 loc_56A724: ; CODE XREF: MmAddPhysicalMemoryEx(x,x,x)+C1j PAGELK:0056A724 cmp edi, ebx PAGELK:0056A726 jnb short loc_56A701 PAGELK:0056A728 push 7 ; SuiteType PAGELK:0056A72A call _ExVerifySuite@4 ; ExVerifySuit...

harkaz

I will remove these 2 keys, but I won't add any further customizations. I want to keep the SP4 as generic as possible. It seems they couldn't care less about fixing shlwapi.dll. Server 2003 support has ended, so there won't be any fixes about it in the future. If was a software engineer I would have...

harkaz

I had noticed a bug with Start Menu icons after applying a POSReady update. Has the issue been fixed yet? If not, I will reconsider the inclusion of POSReady updates in the SP4 and make them available in the WIM only.

harkaz

Well, it seems that the 16-bit error is finally fixed. So I'll just need to integrate the updated files, remove some Firewall-related stuff (as suggested by GH0ST) and finalize V3. I will also try to prepare a generic WIM file with .NET FW 1.1, 3.5, 4.0 preinstalled. Language-specific WIMs (SP4+MUIs...

harkaz

@MrMaguire I won't create any customized SP4 versions. What I'm thinking about is creating a video on how to create a generic WIM file for Windows XP, like the one included with POSReady 2009 setup ISO. You could then easily create a WIM starting from SP3 and performing any customizations you'd like...

harkaz

Please send me the svcpack.log located in %systemroot%
The ISO file is used alternatively of the self-extracting installer by copying the ISO contents to a local folder of your hard drive and launching the i386\update\update.exe program.

harkaz

The v3 will be the final version of SP4, so it will include all updates until its release and I'll take the time needed to include all .NET FW updates as well.
It's difficult to fix everything you report to me, but I'll try to address most of these issues.

harkaz

This KTD bug is weird. I will have to run it in VM.

@Mirza In 99% of cases it is "Failed to install catalog files".

If this is the case:

Type net stop cryptsvc at cmd prompt
Delete the \WINDOWS\SYSTEM32\catroot2 folder
Type net start cryptsvc at cmd prompt.
Restart SP4 installer.

harkaz

@Kurt_Aust What is the error you get with KTD, exactly?
The driver cabinet is still named sp3.cab, so I don't think this has to do with anything.

Happy and prosperous 2016 to everyone!

I may be able to start working on the v3 soon.

harkaz

This is a method similar to my CAT signing procedure in SP4. After you follow the same steps described in the SP4 thread to create CAT files, you need to modify the catalog files in the appropriate places: \Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} \Windows\winsxs\Catalogs (bec...

harkaz

You can automate the process by creating a tool.
I edited update.ver manually.

harkaz

Update.ver:

FILENAME = MD5, [version number in hex], size, branch, CRC32

harkaz

Hi everyone. It's been a long time since my last post here. I'm stuck with the 16-bit issue. I have excluded the new IE installation method from being the culprit, but I haven't yet traced the cause in any CD-ROM specific INF file. Because my free time is limited (USMLE preparation + medical researc...

harkaz

I hope I will finalize v3 soon. This version will fix the 16-bit app CD-ROM issue only. (I haven't been able to reproduce explorer.exe/shell crashes consistently + debug them). Still trying to identify the cause of the 16-bit issue. It seems however that's not related to the way IE8 is installed. I'...

harkaz

@darkrats This is probably done because the .NET 2.0 CLR optimization service starts for the first time. I didn't include any instruction for it to launch a connection, so it is most likely native behaviour of mscorsvw.exe.

FYI, USMLE stands for United States Medical Licensing Examination.

harkaz

@GH0st The shell crash is difficult for me to understand. I can't find a common link between the programs you install and the crash generated. Probably you could describe, in detail, the software changes you make before getting the crash. @Stormit These firewall exceptions are from Stefan Kanthak's ...

harkaz

@Outbreaker Unfortunately, there is no simple way to create a perfect PAE patch for XP. Geoff Chappel has explained this in his article. However, because we're deploying it on 4 GB+ RAM only we can use Chappel's patch as a prototype for any new patches. I'll post on how to patch every file soon.

harkaz

Yes, NTKRNLPA.EXE should be patched if you need support for single-core CPUs. (NOTE: Intel Pentium 4 with HT ENABLED counts as 2 cores!) It's not necessary to patch every HAL though, you must patch only the one(s) that will be selected during Windows Setup. (Of course, if you patch everything you co...

harkaz

64 GB I think. I've read this Geoff Chapels' article before. The following files are changed in my patch: Patched 5.1 files halmacpi.dll ntkrpamp.exe 5.2 files: usbccgp.sys usbd.sys usbehci.sys usbohci.sys usbuhci.sys usbport.sys WARNING: This patch should be used only if your system has more than 4...

harkaz

@Outbreaker I've added your request to my checklist. :) @GH0st Stefan does not make such a tool, unfortunately. Moreover he has created his enhancements for German only. My schedule is so tight that I don't have enough time to restore the original IE installation method and test it - struggling for ...

harkaz

@Outbreaker The problem is that even if I create a batch file that patches the files, you'll still need to sign them. Hopefully the instructions on how to create your own CA and certificate are not too complicated.

harkaz

What is the exact error you're getting when you're slipstreaming? Please attach a picture.

harkaz

Clean install issues might be due to other reasons than Stefan's security enhancements. Probably I'll use the "normal" IE instrallation method if this solves the issues. If I do so, Windows Upgrade installs from Win2k/NT will not be possible will be problematic using an SP4 disk. But I don't think t...

harkaz

Try using a download manager and verify the MD5 checksums of the downloaded files.

harkaz

@GH0st This is also true for the SP3 live installer I think. I had tried to fix those warnings but it prevented specific media files from playing (ie the 'Like Humans Do' song from pre-SP2 installations). So I've decided not to change anything in the live installer. Hope you fixed the other issues y...

harkaz

First of all, Happy new year to everybody! Windows XP x64 SP3 will not be created by me. I want to move on to other projects in the future. @GH0st The file extension issue has already been reported but it can't be reproduced in a VM or real hardware. Probably there's somethiing special with your con...

RyanVM.net Discussion Board

Search found 740 matches

Changes in SP4 v3

Legacy (v2.0) version info

Patching files in Windows 6.x , 10.0 [SFC happy]