harkaz
Content Type
Profiles
Forums
Events
Posts posted by harkaz
-
-
Use Google, but be careful of the setupp.inf in the ISOs you find, and make sure you have a product key for it.
0 -
@submix8c v2 EXEs will never be removed, but they are not current any more. There will be an INF file with the latest registry fixes for these builds.
Also, this dx bug was also present in v2, it's part of the SP4 security enhancements.
0 -
XP SP4 wouldn't be that good without the help of excellent testers. GH0st at ryanvm.net found a new regression issue which I'm about to fix in a v3.1 release (it's coming really soon).
1 -
This is a known SP3 issue.
The Unofficial SP4 fixes this.
0 -
The PDF is not in the EXE package, and has been already fixed. So, no need to wait for another package.
0 -
The year number... haha I'll fix it. UPDATE: Fixed it.
Well, SP4v3 includes all POSready updates as well with the exception of the buggy shlwapi.dll (this won't be ever fixed unfortunately..). The NOPOS flavor is deprecated, it won't be updated any more.
Check the special "POSReady updates" section to see what's included.
@Dave-H Thank you so much, it's really been a huge number of hours working on this project, especially in Q4 2013 and August-November 2014. I remember doing nothing else but working on the SP4. But it's my privilege to build the final SP for the best OS probably ever made. There are so many machines out there -including medical devices and ATMs- still running XP so it is very important to try and keep it as secure, fast and reliable as possible. I did my best to contribute to the community of XP users, other experts out there will contribute even further. I feel I've done my part.
1 -
FYI, the latest SP4v3 version, which has just been released has a working 4GB patch for the latest HAL/KERNEL files.
Download at RyanVM.net.
Technical info about the patch available here: http://www.ryanvm.net/forum/viewtopic.php?p=140551#140551
0 -
SP4 v3 is now available.
Download available at the usual location.
0 -
NEWS: A v3 of SP4 will be released soon.
This version will include:
- A fix for the 16-bit app emulation not working when installed from CD-ROM
- Latest updated file versions except for the buggy May 2014 shlwapi.dll
- Some security enhancements with firewall configuration
- Removal of FP "malware" files and replacement with new, clean, smaller placeholders
This will be the final-final build of SP4 ever.
0 -
Rebase will leave placeholder-files in the winsxs folders of size ~30 bytes each.
Hardlinks will not decrease the size reported (including the wim file) and may cause problems in the future.
As a side note, rebase does not touch any hardlinks necessary to service future updates.
0 -
It saves 2GB more after running this hotfix you mention.
0 -
It saves about 2 GB on x64 systems, 1 GB on x86 systems.
0 -
Rebase Build 1.0.20.21
Release date: 30 Dec 2015
BUG FIX: Rebase will not cleanup updates added offline.
Reason: All updates installed offline are marked as pending and rebase was programmed not to remove files corresponding to updates that are marked as pending. Now rebase will ignore the pending indication if working offline.0 -
@alacran Sent you a PM. Hope this will reassure you that rebase is reliable. And remember: you save 1.5 GB in addition to what system restore cleanup would save you.
0 -
Release trailer ready:
Win7 Pro x86 winsxs reduced from: 6.77 GB to 5.29 GB without the extreme option, 4.40 GB with the extreme option
0 -
Rebase RTM (1.0.20.16) is ready.
A release trailer will be uploaded in a few hours.
0 -
Rebase Beta Build has been reached.
Pending tasks:
Error handling and log output, Documentation, EULA, Release Trailer.
0 -
UPDATE: I found a way to properly remove staged OS Editions (Working offline on Windows 7 Home Premium image).
However, the winsxs size was reduced only slightly: 70 MB
0 -
Filtering locales is not needed as long as you have only one language installed. There are tools like RT7 lite or NTLite that will help you remove keyboard languages.
Removing unnecessary SKUs is something I will try in the future. There are specific "target-editions" which can be shown via DISM. The goal is to remove redundant Target editions.
Rebase will help you removing inactive builds.
0 -
@vinifera That "theoretical" size is without removing components. If you remove components you can go <600MB as you mention.
0 -
IE/ WMF seem to work just fine.
Added the code to mark permanence. Everything works as it should.
Well, it's only error handling and we're done in here
0 -
I have good news for you: I fixed the bugs with WU, so now I only need to test the IE9/IE10, WMF stuff.
Checked compatibilty with Windows update cleanup addon -> ok so far, will recheck later.
Stay tuned
0 -
@jaclaz "Winner" is an internal name at Microsoft for "component family". Maybe I should use this instead.
WIM mounting is the only one supported, although other mount types may be work just fine.
I have some issues with Windows Update - CBS finds some "inconsistencies" in the component store.
Namely it tries to open packages that correspond to removed payloads and it fails.
Consequently I need to further improve the method. Final release will delay a bit more.
0 -
Please be patient; testing is not fully automated.
0
Introducing - Unofficial Windows XP SP4
in Windows XP
Posted
Some registry entries are not found by dxdiag, because they are registered using full paths and not just the file name + extension.
All keys that are dpnet.dll-related and two others: Key 'HKCR\CLSID\{4516EC43-8F20-11d0-9B6D-0000C0781BC3}\InprocServer32', Value '', Value ''Key 'HKCR\CLSID\{4516EC41-8F20-11d0-9B6D-0000C0781BC3}\InprocServer32', Value '', Value ''