I know that is actually late integrating into RC release, and I also know that because for too many user's ideas you many times delay RC release. But anyway I hope that you will reconsider that option for Final version of the SP4.harkaz wrote:Your suggestions are interesting, but I won't make any further changes in the SP4.
I won't be able to release RC today: final tests have shown some glitches caused by the new way IE8 is installed and some others... I'll try to fix these and then release SP4 RC.
Welcome to Windows XP Service Pack 4
@Outbreaker Sounds interesting, let me take a look at the issue...
@maxtorix Because I have to perform extensive testing after integrating new components, I won't change Windows XP SP4 components after RC. RC will become Final if there are no bugs found.
There are two issues:
1. During Windows Setup, you cannot select Date and Time Settings. Instead, the Windows Components wizard appears (due to the patch I applied).
2. No HTTP lnks can be created in the start menu: Windows Catalog.lnk has no target HREF when created!
The second one might be the result of the new way IE8 files are installed (IE6 files are used first, then the new ones are copied-renamed during T13 by Session Manager at reboot).
The first one might be fixable using a patch. If it's not, I won't include the OC Manager patch in SP4...
UPDATE: I'm not knowledgeable enough to create such a patch. You need to create a new wizard page, otherwise Setup will crash (that's actually why ntoc.dll makes Setup crash)... So the OC Manager patch won't be included in XP SP4 at all. Still, I will sign the modified files so that you can use them if you wish to.
@maxtorix Because I have to perform extensive testing after integrating new components, I won't change Windows XP SP4 components after RC. RC will become Final if there are no bugs found.
There are two issues:
1. During Windows Setup, you cannot select Date and Time Settings. Instead, the Windows Components wizard appears (due to the patch I applied).
2. No HTTP lnks can be created in the start menu: Windows Catalog.lnk has no target HREF when created!
The second one might be the result of the new way IE8 files are installed (IE6 files are used first, then the new ones are copied-renamed during T13 by Session Manager at reboot).
The first one might be fixable using a patch. If it's not, I won't include the OC Manager patch in SP4...
UPDATE: I'm not knowledgeable enough to create such a patch. You need to create a new wizard page, otherwise Setup will crash (that's actually why ntoc.dll makes Setup crash)... So the OC Manager patch won't be included in XP SP4 at all. Still, I will sign the modified files so that you can use them if you wish to.
Confirmed that using IE6 files during setup causes the issue with links created by syssetup.dll.
This may happen because additional IE6 are required for proper shortcut creation during Windows Setup. I'll look into this further.
This may happen because additional IE6 are required for proper shortcut creation during Windows Setup. I'll look into this further.
Windows XP Unofficial SP4 (2014, 2016, and 2019): viewtopic.php?t=10321
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
It's just another utility that can be installed with your other apps. No need to make the pack even fatter. I can think of a dozen other things to include, but I don't feel the pack is the right place for it.maxtorix wrote:I know that is actually late integrating into RC release, and I also know that because for too many user's ideas you many times delay RC release. But anyway I hope that you will reconsider that option for Final version of the SP4.harkaz wrote:Your suggestions are interesting, but I won't make any further changes in the SP4.
I won't be able to release RC today: final tests have shown some glitches caused by the new way IE8 is installed and some others... I'll try to fix these and then release SP4 RC.
The HREF link problem will not be properly solved. Because it affects Windows Setup only, I will use the following workaround:
1) Windows Catalog link will be removed.
2) For K,KN editions I will try to copy the links manually (syssetup.inf will do it) and remove the lines used to create them. (Reminder: The problem is the creation of the shortcuts.
I think this solution is preferable to breaking Windows 9x/ Windows 2000 Upgrades.
1) Windows Catalog link will be removed.
2) For K,KN editions I will try to copy the links manually (syssetup.inf will do it) and remove the lines used to create them. (Reminder: The problem is the creation of the shortcuts.
I think this solution is preferable to breaking Windows 9x/ Windows 2000 Upgrades.
-
- Posts: 177
- Joined: Thu Nov 22, 2012 10:17 am
-
- Posts: 177
- Joined: Thu Nov 22, 2012 10:17 am
The good news is that the issue can been fixed by changing ie.inf
The question is: what registry changes are required?
As you understand I'm looking into it right now.
The question is: what registry changes are required?
As you understand I'm looking into it right now.
Windows XP Unofficial SP4 (2014, 2016, and 2019): viewtopic.php?t=10321
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
I have found a solution, now I'm doing some final tests...
Windows XP Unofficial SP4 (2014, 2016, and 2019): viewtopic.php?t=10321
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
-
- Posts: 52
- Joined: Sun Aug 14, 2011 5:35 pm
- Location: Chicago, Illinois USA
- Contact:
I have found a script that seems to do the job. This script will be run at T13 and reset specific Active Setup components that need to be run at first boot!
NEWS: Tested Windows NT 4 SP1 to Windows XP SP4 Upgrade (2 GB HDD used).
The recommended upgrade path is:
Windows NT 4 SP1 -> Windows NT 4 SP6 -> Windows XP SP4
After the Upgrade, free 500 MB of HDD space by removing .NET Frameworks 1.1 and 3.5 (otherwise disk will be full!).
IE was upgraded FLAWLESSLY from version 2.0 to version 8.0. Howewer, if you have version 4.0 installed, upgrade to 5.0 or later before installing Windows XP SP4.
This is a screenshot of the VM after update:

NEWS: Tested Windows NT 4 SP1 to Windows XP SP4 Upgrade (2 GB HDD used).
The recommended upgrade path is:
Windows NT 4 SP1 -> Windows NT 4 SP6 -> Windows XP SP4
After the Upgrade, free 500 MB of HDD space by removing .NET Frameworks 1.1 and 3.5 (otherwise disk will be full!).
IE was upgraded FLAWLESSLY from version 2.0 to version 8.0. Howewer, if you have version 4.0 installed, upgrade to 5.0 or later before installing Windows XP SP4.
This is a screenshot of the VM after update:

Tested Windows XP SP4 RC with Greek MUI. In general, Windows XP SP4 is compatible with MUI but there are specific issues to take care of. For example, Outlook Express MUI won't work (it's a MUI issue, not SP4 issue). If you use MUI a lot, you can test Windows XP SP4 with the following MUIs installed:
- XP SP3 MUI
- IE8 MUI
- RDP7 MUI
- WUA3 MUI
- WMP11 MUI
- .NET 1.0, 1.1, 3.5, 4.0 MUI
- MCE2005 MUI (specific langs)
- Tablet PC 2005 MUI (specific langs)
- Rosebud v12 MUI
Now building layout.inf files...
- XP SP3 MUI
- IE8 MUI
- RDP7 MUI
- WUA3 MUI
- WMP11 MUI
- .NET 1.0, 1.1, 3.5, 4.0 MUI
- MCE2005 MUI (specific langs)
- Tablet PC 2005 MUI (specific langs)
- Rosebud v12 MUI
Now building layout.inf files...
Windows XP Unofficial SP4 (2014, 2016, and 2019): viewtopic.php?t=10321
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Since its about October now, are you going to wait for the October Update? or when ever its done with what your doing, are you just going to release it?
ps. haven't been testing on installing games and such from cd's, its either the rom error from SP4 B3 or its littery dead. but then again, setup wouldn't be working at all to install this to my system.
~Keep up the good work~
ps. haven't been testing on installing games and such from cd's, its either the rom error from SP4 B3 or its littery dead. but then again, setup wouldn't be working at all to install this to my system.
~Keep up the good work~
@Anthony21 Windows XP SP4 will not include post-EOL updates except for May's mshtml.dll patch.
In October I will create a post-SP4 update pack, which can be integrated in any Windows XP SP4-integrated media. I'll try to keep this update pack up-to-date every month.
Today I'll try to finish building layout.inf, perform a couple of tests and release SP4 RC.
As mentioned above, SP4 RC will become Final if there are no bugs found within a couple of weeks.
In October I will create a post-SP4 update pack, which can be integrated in any Windows XP SP4-integrated media. I'll try to keep this update pack up-to-date every month.
Today I'll try to finish building layout.inf, perform a couple of tests and release SP4 RC.
As mentioned above, SP4 RC will become Final if there are no bugs found within a couple of weeks.
Already being done. http://www.ryanvm.net/forum/viewtopic.php?t=10479 I assume that addon will also workharkaz wrote: In October I will create a post-SP4 update pack, which can be integrated in any Windows XP SP4-integrated media. I'll try to keep this update pack up-to-date every month.
with this pack via RVMi.
- ricktendo64
- Posts: 3214
- Joined: Mon May 22, 2006 12:27 am
- Location: Honduras
@adric I haven't tested it yet but I'm afraid 5eraph's addon will cause issues with IE.
@ricktendo64 Nice find, thank you!
Just finished building layout.inf files. Finalizing...
@ricktendo64 Nice find, thank you!

Just finished building layout.inf files. Finalizing...
Windows XP Unofficial SP4 (2014, 2016, and 2019): viewtopic.php?t=10321
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
- Outbreaker
- Posts: 703
- Joined: Tue Aug 21, 2007 8:06 am
ricktendo64, Do you know which file to replace for the HotIfx "KB2870165-v3 (Remote Desktop)" in an UpdatePack?ricktendo64 wrote:Note that these win7 updates are compatible/work with XP
KB2979583 (Remote Desktop)
KB2870165-v3 (XPS Printer)

I extracted the Windows 7 HotFix but there are some many files in it, it's totally different than a Windows XP hotFix extracting.

I'm now generating a new certificate to sign Windows XP SP4 files. This certificate will be valid for 5 years, ready for use with the upcoming post-SP4 update pack.
Some final live install tests and Windows XP SP4 RC will be most likely available tomorrow. I fixed a small -final- xpfixit.inf issue. The xpfixit.inf file had caused various issues in its original form, and this is one of the reasons SP4 RC has delayed so much.
Some final live install tests and Windows XP SP4 RC will be most likely available tomorrow. I fixed a small -final- xpfixit.inf issue. The xpfixit.inf file had caused various issues in its original form, and this is one of the reasons SP4 RC has delayed so much.
Windows XP Unofficial SP4 (2014, 2016, and 2019): viewtopic.php?t=10321
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Finished building catalogs with the new certificate, tomorrow I will complete testing live installations...
Windows XP Unofficial SP4 (2014, 2016, and 2019): viewtopic.php?t=10321
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
- ricktendo64
- Posts: 3214
- Joined: Mon May 22, 2006 12:27 am
- Location: Honduras
I had them backwards, KB2870165-v3 is for RDPOutbreaker wrote:ricktendo64, Do you know which file to replace for the HotIfx "KB2870165-v3 (Remote Desktop)" in an UpdatePack?ricktendo64 wrote:Note that these win7 updates are compatible/work with XP
KB2979583 (Remote Desktop)
KB2870165-v3 (XPS Printer)
I extracted the Windows 7 HotFix but there are some many files in it, it's totally different than a Windows XP hotFix extracting.
Depends on the updatepack you are using and they have to previously integrated KB969084. Sometimes filename is lhmstsc.exe, lhmstcx.dll, the other files should have the same name...
As for what CAT digitally signs them, you can use signtool
http://www.ryanvm.net/forum/viewtopic.php?t=9543
- Outbreaker
- Posts: 703
- Joined: Tue Aug 21, 2007 8:06 am
I notice you had it backwards. 
And yes the UpdatePack i use has the KB969084 already integrated.
Do you have the new RDP update files by hand? I'm not so familiar with the extraction of the Windows Vista/7/8 HotFix'es.
EDIT: I will take a look at the new link you posted. Or i will wait for the SP4 RC and grab them for their.

And yes the UpdatePack i use has the KB969084 already integrated.
Do you have the new RDP update files by hand? I'm not so familiar with the extraction of the Windows Vista/7/8 HotFix'es.

EDIT: I will take a look at the new link you posted. Or i will wait for the SP4 RC and grab them for their.

Sereby published an extraction tool that works in XP for NT6+ MSUs some time ago, Outbreaker. I packaged a few simpler tools for my own use. If you just want a newer version of Expand, it's available separately.
Testing sfc /scannow after live installation. Unfortunately, SFC has NO LOG FILE (?!) so I have to figure out some things manually - for example the new certificate changed catalog file size.
Windows XP Unofficial SP4 (2014, 2016, and 2019): viewtopic.php?t=10321
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
@bphlpt Thanks for your support. The issue is not really big because it can be solved by inserting slipstreamed XP SP4 installation media. Probably some files which should be present in ServicePackFiles are not there and a SP4 CD-ROM is required. Also Windows XP SP4 CD2 is required repeatedly when .NET Framework 1.0 SP3 is installed (even if the CD2 is there, this is an old SP3 bug I think). I'll try to fix both issues, even if they're not very important.
I fixed the first issue (sfc /scannow asks only for the original CD-ROM now.
EDIT: I will re-test the second issue.
Now testing XP Pro N live install with Media Pack installed and performing a clean installation from USB on real hardware.
UPDATE: XP PRO N with Media Pack tested - OK
UPDATE #2 All sfc issues are fixed. To prevent issue 2 media center files have to be on the CD2 always.

EDIT: I will re-test the second issue.
Now testing XP Pro N live install with Media Pack installed and performing a clean installation from USB on real hardware.
UPDATE: XP PRO N with Media Pack tested - OK
UPDATE #2 All sfc issues are fixed. To prevent issue 2 media center files have to be on the CD2 always.
@Anthony21 It is not required to have two seperate disks, if that's what you mean. You can merge the files into a single disk. Do not forget the WIN51CD2 tag file.
NEWS: Tested XP Home USB-based installation. No issues on real hardware.
Probably you will be amazed by some performance improvements.
Also, there is are system behaviour changes in SP4 (if you haven't noticed this change is present since Beta 3):
- In Windows XP Home edition you won't be able to access Administrator account without entering safe mode.
This is most likely due to the updated msgina.dll/winlogon.dll files, although I'm not certain what causes this system behaviour change, but it's important in terms of security, since this account has not been password-protected during Windows XP Home setup...
Now, finally, I will test Windows XP Starter edition.
UPDATE: I won't be able to release XP SP4 at the moment, because it's too late for me (3:00 am right now) and I have to get some sleep. Howewer, expect the SP4 RC release tomorrow - all tests have been completed.
NEWS: Tested XP Home USB-based installation. No issues on real hardware.
Probably you will be amazed by some performance improvements.
Also, there is are system behaviour changes in SP4 (if you haven't noticed this change is present since Beta 3):
- In Windows XP Home edition you won't be able to access Administrator account without entering safe mode.
This is most likely due to the updated msgina.dll/winlogon.dll files, although I'm not certain what causes this system behaviour change, but it's important in terms of security, since this account has not been password-protected during Windows XP Home setup...
Now, finally, I will test Windows XP Starter edition.
UPDATE: I won't be able to release XP SP4 at the moment, because it's too late for me (3:00 am right now) and I have to get some sleep. Howewer, expect the SP4 RC release tomorrow - all tests have been completed.
ya, thats what i mean, I'm not planing on having 2 cd's, got my DVDRW 4.7GB I've been using. Been doing something else for the past month, I kinda lack off of the WIN51CD2 tag file, how ya do that again? just to refresh my mind.harkaz wrote:@Anthony21 It is not required to have two seperate disks, if that's what you mean. You can merge the files into a single disk. Do not forget the WIN51CD2 tag file.
once RC releases, gonna add drivers 1st with the SP4, then probably add a few codecs after it with some small programs like adobe and chrome.
Keep up the good work!
~Cheers n Regards~
@Anthony21 WIN51CD2 is automatically copied by package installer during slipstreaming.
Still working on Windows XP Starter... There is a very interesting issue (BSOD) caused after updating IE files. I reverted to the original IE installation method and now I'm testing it. In addition, note urlmon.dll version on Starter CD: it must be 6.0.2900.2823 no matter what version of IE is integrated. Also, the file is uncompressed on the Starter CD.
I'll keep you updated.
Still working on Windows XP Starter... There is a very interesting issue (BSOD) caused after updating IE files. I reverted to the original IE installation method and now I'm testing it. In addition, note urlmon.dll version on Starter CD: it must be 6.0.2900.2823 no matter what version of IE is integrated. Also, the file is uncompressed on the Starter CD.
I'll keep you updated.
UPDATE: Reverting to standard IE settings did not fix the issue. Now testing some changes in hive*.inf files...
Windows XP Unofficial SP4 (2014, 2016, and 2019): viewtopic.php?t=10321
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
Non-IT stuff:
Retinal changes in schizophrenia (2019): https://academic.oup.com/schizophreniab ... 06/5598443
@darkrats I have excluded the possibility that the issue is caused by the security enhancements.
It seems that it goes deeper than that. As you remember, in SP4 RC all files will be signed with a signle catalog - sp4cmp.cat - to enhance performance (mimizes the number of installed catalogs). Specific files have been also signed with their Microsoft-provided catalogs - licensing DLLs is a prime example.
Well, it seems that this BSOD is a signing issue. I've done some research around the Web and similar BSODs (at startup) are caused when a patched win32k.sys is used. I have disassembled ediskeer.dll and along with win32k.sys there is a number of other files under a structure named "StarterVitalFileList". The idea I'm working on right now is to selectively install MS catalogs for any updated files referenced there.
It seems that it goes deeper than that. As you remember, in SP4 RC all files will be signed with a signle catalog - sp4cmp.cat - to enhance performance (mimizes the number of installed catalogs). Specific files have been also signed with their Microsoft-provided catalogs - licensing DLLs is a prime example.
Well, it seems that this BSOD is a signing issue. I've done some research around the Web and similar BSODs (at startup) are caused when a patched win32k.sys is used. I have disassembled ediskeer.dll and along with win32k.sys there is a number of other files under a structure named "StarterVitalFileList". The idea I'm working on right now is to selectively install MS catalogs for any updated files referenced there.
Issue fixed!
Finalizing Windows XP Unofficial SP4...
NOTE: explorer.exe,etc v 5.1.2600.5669 are not digitally signed with a catalog file (but they have an embedded digital signature, which satisfies SFC). Since ediskeer.dll looks up installed catalogs signed explicitly from Windows Component Publisher the latest version available with catalog file is used for Starter only (KB951159 - 6.0.2900.5577)
The list of critical Starter files:
"%windir%\\system32\\nusrmgr.cpl"
"%windir%\\system32\\samsrv.dll"
"%windir%\\system32\\gdi32.dll"
"%windir%\\system32\\user32.dll"
"%windir%\\system32\\win32k.sys"
"%windir%\\system32\\winsrv.dll"
"%windir%\\system32\\shell32.dll"
"%windir%\\system32\\ntdll.dll"
"%windir%\\explorer.exe"
"%windir%\\system32\\rundll32.exe"
"%windir%\\system32\\taskmgr.exe"
"%windir%\\system32\\osk.exe"
"%windir%\\system32\\magnify.exe"
"%windir%\\system32\\narrator.exe"
"%windir%\\system32\\accwiz.exe"
"%windir%\\system32\\utilman.exe"
"%windir%\\system32\\msswchx.exe"
"%windir%\\winhelp.exe"
"%windir%\\system32\\winhlp32.exe"
"%windir%\\system32\\wpabaln.exe"
"%windir%\\system32\\wuauclt.exe"
"%windir%\\hh.exe"
"%windir%\\system32\\dwwin.exe"
"%windir%\\system32\\oobe\\msoobe.exe"


Finalizing Windows XP Unofficial SP4...
NOTE: explorer.exe,etc v 5.1.2600.5669 are not digitally signed with a catalog file (but they have an embedded digital signature, which satisfies SFC). Since ediskeer.dll looks up installed catalogs signed explicitly from Windows Component Publisher the latest version available with catalog file is used for Starter only (KB951159 - 6.0.2900.5577)
The list of critical Starter files:
"%windir%\\system32\\nusrmgr.cpl"
"%windir%\\system32\\samsrv.dll"
"%windir%\\system32\\gdi32.dll"
"%windir%\\system32\\user32.dll"
"%windir%\\system32\\win32k.sys"
"%windir%\\system32\\winsrv.dll"
"%windir%\\system32\\shell32.dll"
"%windir%\\system32\\ntdll.dll"
"%windir%\\explorer.exe"
"%windir%\\system32\\rundll32.exe"
"%windir%\\system32\\taskmgr.exe"
"%windir%\\system32\\osk.exe"
"%windir%\\system32\\magnify.exe"
"%windir%\\system32\\narrator.exe"
"%windir%\\system32\\accwiz.exe"
"%windir%\\system32\\utilman.exe"
"%windir%\\system32\\msswchx.exe"
"%windir%\\winhelp.exe"
"%windir%\\system32\\winhlp32.exe"
"%windir%\\system32\\wpabaln.exe"
"%windir%\\system32\\wuauclt.exe"
"%windir%\\hh.exe"
"%windir%\\system32\\dwwin.exe"
"%windir%\\system32\\oobe\\msoobe.exe"
Although Windows XP Unofficial SP4 RC is almost done, I won;t be able to release it tomorrow. The reason is that I have to be away from my system for the following 3 days. When I am back, Windows XP SP4 RC will be available.
Some remaining tasks for the live installer:
1) Copy explorer.exe,etc. for Starter (version number is less than 5.1.2600.5669)
2) Enhance ESENT Catroot2 reset reliability. The system might become unstable if user clicks Cancel, because catoot2 is rebuilt only at reboot.
Some remaining tasks for the live installer:
1) Copy explorer.exe,etc. for Starter (version number is less than 5.1.2600.5669)
2) Enhance ESENT Catroot2 reset reliability. The system might become unstable if user clicks Cancel, because catoot2 is rebuilt only at reboot.
- =[FEAR]=JIGSAW
- Posts: 400
- Joined: Mon Feb 18, 2008 11:54 am
- Location: Cape Town, South Africa
-
- Posts: 52
- Joined: Sun Aug 14, 2011 5:35 pm
- Location: Chicago, Illinois USA
- Contact:
-
- Posts: 52
- Joined: Sun Aug 14, 2011 5:35 pm
- Location: Chicago, Illinois USA
- Contact:
Good Point on letting him know but so far whats coming in RC that everything works and might be the last possible build unless there is a snag that comes with it.PROBLEMCHYLD wrote:That's fine and dandy, but how can he fixed something he's not aware of. Besides, I fixed computers on my spare time, so waiting for RC won't cut it for the customers.poolside wrote: Wait for RC and then integrate it into the source.
I like to use my CD-rom but from main a disk of integrated drivers and sp4, my rom isn't there, it is but it won't detect any disk thats in the rom.
Started uploading Windows XP SP4 Release Candidate (RC).
Windows XP SP4 RC will be available in a while. Windows XP SP4 RC is most likely the final build of Windows XP Unofficial Service Pack 4. It includes numerous under-the-hood changes: bug fixes, security enhancements, performance tweaks and stability improvements.
It has been tested in various different configurations - some of them were tested for the first time during development of this build - and it fixes specific issues (like Windows 9x/NT/2k upgrades to IE8) for the first time ever.
Windows XP SP4 RC ships in 4 EXEs: 2 of them can be used to create 6 bootable floppy disk for Home and Professional Editions, respectively, one is the main SP4 EXE and the other one is the main SP4 EXE without the POSReady update hack.
Windows XP SP4 RC includes all updates until XP's EOL plus the May 2014 mshtml.dll update, along with other runtime components. .NET Framework 4.0 won't installed by default. Neither will Windows Powershell 2.0, which is included as an optional component in this build.
In addition, Windows XP SP4 RC includes security enhancements addressing issues not fixed by Microsoft updates, and performance tweaks that make your PC run blazingly fast.
Download link will be available in a few hours.
Windows XP SP4 RC will be available in a while. Windows XP SP4 RC is most likely the final build of Windows XP Unofficial Service Pack 4. It includes numerous under-the-hood changes: bug fixes, security enhancements, performance tweaks and stability improvements.
It has been tested in various different configurations - some of them were tested for the first time during development of this build - and it fixes specific issues (like Windows 9x/NT/2k upgrades to IE8) for the first time ever.
Windows XP SP4 RC ships in 4 EXEs: 2 of them can be used to create 6 bootable floppy disk for Home and Professional Editions, respectively, one is the main SP4 EXE and the other one is the main SP4 EXE without the POSReady update hack.
Windows XP SP4 RC includes all updates until XP's EOL plus the May 2014 mshtml.dll update, along with other runtime components. .NET Framework 4.0 won't installed by default. Neither will Windows Powershell 2.0, which is included as an optional component in this build.
In addition, Windows XP SP4 RC includes security enhancements addressing issues not fixed by Microsoft updates, and performance tweaks that make your PC run blazingly fast.
Download link will be available in a few hours.
Thanks!
I've been checking back throughout the weekend for it's availability.
Some time in the future (not a big issue) would you be able to devote some thought to why having Symantec Endpoint Protection on my system (even when temporarily disabled) crashes with a BSOD the very moment I run the setup for your SP4? I usually install it by first totally disabling SEP (including drivers) and then re-enabling it when the installation is finished. The same thing happens when I attempt to install a monthly IE8 update. There must be others who use SEP and have installed SP4 or the monthly updates, but I haven't seen any posts from them regarding this particular problem.
For those of us in the Windows XP Community, your work is extremely valuable and very much appreciated. I'm 63 and I would like to think that I will be able to use XP for the rest of my life.
(Unless MS decides to bring it back by some miracle)
I've been checking back throughout the weekend for it's availability.
Some time in the future (not a big issue) would you be able to devote some thought to why having Symantec Endpoint Protection on my system (even when temporarily disabled) crashes with a BSOD the very moment I run the setup for your SP4? I usually install it by first totally disabling SEP (including drivers) and then re-enabling it when the installation is finished. The same thing happens when I attempt to install a monthly IE8 update. There must be others who use SEP and have installed SP4 or the monthly updates, but I haven't seen any posts from them regarding this particular problem.
For those of us in the Windows XP Community, your work is extremely valuable and very much appreciated. I'm 63 and I would like to think that I will be able to use XP for the rest of my life.
(Unless MS decides to bring it back by some miracle)