harkaz
Content Type
Profiles
Forums
Events
Posts posted by harkaz
-
-
Well, the interest for the program has been kinda limited.
Probably the payment option was not appropriate but it was the best I could do at the moment.
Given the low interest, it was not worth waiting for any 'late-comers' that might purchase a license to use the program just before the end of support.
I always intended to stop availability just before end of support, it happended a bit earlier.
For those who got a copy of the Rebase tool, I hope I've lived up to your expectations in terms of support and programming quality.
0 -
IMPORTANT NOTICE: Rebase will not be available for purchase after June 30, 2016.
Support for existing users will end as stated in the documentation.
0 -
New payment option: Payment via Paypal to my e-mail address. Prior contact via e-mail is required.
0 -
I have sent Dibya a PM with the update package.
It will take much more work to be a full backport.
For example, the dxgkrnl.sys, updated dxdiag, patched rpcrt4.dll, version.dll, cdd.dll, ntoskrnl/HAL files
It requires advanced knowledge of the kernel structure. Recommend analysing the manifest files in Windows6.0-KB971512-x86 to get a first idea of the files needed. Then try understanding how this update brings DX11 functionality to Vista and try to combine this with DX10 in XP kernel.
Remember: there is no way you can avoid changes in kernel, due to dxgkrnl.sys
2 -
Working on a sxs.dll patch that will allow custom-signed assemblies to work.
This is necessary for installation of CRT, gdiplus assemblies.
1 -
Dibya has sent me some files for his DX11 backport.
I have started examining them and preparing the update package.
1 -
SP4 = SP3 + Post-SP3 updates + POSReady updates until January 2016 + Stefan Kanthak's security enhancements + Some Optional components fully updated
The only thing you cannot get from Microsoft is the security enhancements pack.
Consider it similar to a "Windows 98 SE" disk. Most of the included components could be downloaded from Microsoft directly and applied to Windows 98 FE. However, there were some under-the-hood fixes which were not available for Windows 98 FE.
I agree that SP4 should be used for clean install. Clean install offers a few more security enhancements than the live install.
0 -
There is no official XP installation CD-ROM with IE7/IE8 in it.
Even if there is one, it should be buggy. During Unofficial SP4 development I discovered that IE7/IE8 files will cause problems during Upgrade installs from previous versions of Windows (98, NT, 2000). Of course I applied a workaround (SP4 is the only update pack with such a workaround), but there is no official fix for that.
Thus, I believe there is no official XP disk with IE7/IE8 slipstreamed, either, since they would have to test it in all scenarios.
0 -
IMPORTANT: There is an issue with post-sp4 .NET FW 4.0 updates I would like to report, which is not caused by the SP4 itself.
Scenario: Install SP4 -> Enable .NET Framework 4.0-> Run Windows Update Manual Check. -> Install Updates -> reboot -> Installed all updates successfully -> Run Windows Update Manual Check.
You will get the old .NET Framework 4 GDR update (KB2468871) in the optional updates.
Reason: This happens because one of the newest updates deletes the:
HKLM, "SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2468871" and
HKLM, "SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Extended Profile\KB2468871"registry keys.
These keys are necessary to satisfy the WU detection algorithm for the XP product family (not the POSReady one), but they play no other significant role whatsoever; this is actually a flaw in WU detection algorithm.
SOLUTION: You can let Windows Update download and install the update automatically (it should not be removed afterwards).1 -
A major update, rebase 1.1.30.0 is now available!
This must-have upgrade of rebase will be rolled out to existing users in a few hours.
What's new in Rebase 1.1:- An ESSENTIAL upgrade of the cleanup algorithm. Fixes reliability issues with the old algorithm. Recommend rebuilding your images from scratch with the new rebase version.
- Fixes all previously reported issues, including a glitch with offline servicing of updates: Now all updates are marked as permanent in any rebase usage scenario.
- A new feature: the ability to hide all previously installed updates.
0 -
Only the following reg entry is installed:
HKLM,"SYSTEM\WPA\POSReady","Installed",0x00010001,1
0 -
Version 3.1b is being uploaded at the moment, it is intended for new installs only.
0 -
The reg file has been updated with the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded
0 -
All fixed.
0 -
It could be a good idea to remove the SYSTEM\WPA\WES and SYSTEM\WPA\WEPOS keys, even if they're set to Installed=0.
Similar changes may take effect in the next months.
@dencorso I think we should completely remove the references to these keys in the first post.
0 -
Yes, you should remove the key in any case.
0 -
@Roffen It should be really easy. Download the reg file from the SP4 thread, double click on it, click Yes on the message, done!
0 -
@bluebolt Fixed the SP4 thread to prevent confusion.
@Mcinwwl The keys related to Embedded versions are rather specific, so it wasn't difficult.
0 -
I'm certain this key is the culprit.
When I re-added the key and rechecked, WindowsUpdate.log file reported:
2016-03-08 23:20:37:234 1016 a6c AU AU setting next detection timeout to 2016-03-09 17:47:17
2016-03-08 23:20:37:234 1016 a6c AU Setting AU scheduled install time to 2016-03-09 01:00:00
2016-03-08 23:20:37:250 1016 a6c AU Cancelled download for invalidated/hidden/unapplicable update(s)
2016-03-08 23:20:37:250 1016 a6c AU WARNING: Download callback received for call not in AU's list. Ignore the call result.
2016-03-08 23:20:37:250 1016 a6c AU WARNING: Download callback received for call not in AU's list. Ignore the call result.
2016-03-08 23:20:42:218 1016 2ec Report REPORT EVENT: {D8339AE8-47A1-4EDA-A5C6-7A454C7AD8C7} 2016-03-08 23:20:37:218+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
0 -
IMPORTANT NOTICE FOR XP SP4 USERS:
Microsoft has changed its WU update detection strategy.
The following key must be removed to continue receiving automatic updates from WU:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded
A reg file is available at the first post to automate the process.
v3.1a users don't need to do anything more than that.
A new v3.1b version will be released soon with this change, just for new installs. No other updates will be added.
1 -
SP4 users must delete this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded
Run WU check after doing so.
2 -
I have found them at the catalog, but not from WU/MU
0 -
WU/MU still offers Posready February updates, so there is no change in detection method.
I'm working on SP4 VM.
0 -
Still 0 updates.
0
Windows 7 Resetbase backport
in Windows 7
Posted · Edited by harkaz
When I created Rebase in December, no free tool existed that could provide the same functionality.
Usability of Rebase for the average user is, indeed, questionable. However, given there was no free tool that offered exactly the same quality of functionality I decided to distribute Rebase as shareware and measure its reception.
I guess that most users don't grasp these subtle but substantial differences that exist between Rebase and other tools that offer similar functionality. Even those who may understand, they certainly do not trust an amateur, third-party developer. Winsxs management can be a tricky issue, even for Microsoft themselves.
And of course, to put it in a more general sense, developing software may not be the best way to make money...