Windows XP Build 2531.0.xpclient.010730-1640：修订间差异
跳转到导航
跳转到搜索
Windows XP Build 2531.0.xpclient.010730-1640 (查看源代码)
2026 年 1 月 10 日 (六) 09:09 的版本
、 2026 年 1 月 10 日 (星期六)无编辑摘要
小无编辑摘要 |
小无编辑摘要 |
||
| 第 18 行： | 第 18 行： | ||
}} | }} | ||
Windows XP Build 2531 是 [[Windows XP]] 的 RC2 后版本。该版本的 | Windows XP Build 2531 是 [[Windows XP]] 的 RC2 后版本。该版本的 Professional SKU 最初于 2001 年末以粗劣打包的 ISO 镜像形式上传。现有的安装介质最初捆绑了一个“自动补丁”，该补丁原本是为 [[Windows XP Build 2520.0.main.010717-1624|Build 2520]] 从一开始就应用，这除了移除[[时间炸弹]]并规避[[Windows 产品激活|产品激活]]机制外，还整合了诸多定制优化：包含多种背景主题，甚至预先注册了水族箱屏保 — 这些内容从未出现在任何官方版本中。 | ||
为恢复操作系统安装介质并撤销原始上传者所做的修改，OSBA 成员 lucasm 与 gus33000 于 2015 年 5 月 8 日首次展开协作尝试，但设置默认壁纸时仍存在问题。<ref>https://web.archive.org/web/20150610005724/http://www.osbetaarchive.net/topic/156-windows-xp-whistler-build-2531-restored-iso/</ref>。然而，qazmko1029 于 2020 年 5 月 4 日设计了一种更全面的方法，其光盘镜像由 Lucas Brooks 制作，于 2022 年 6 月 18 日面世。值得注意的是，不仅初始修复版本，此后所有后续尝试均存在某些不准确之处（例如 ISO 文件系统细节、错误的 CDIMAGE 构建参数，以及与该水族馆屏保相关的残留注册数据），这些问题始终存在。 | |||
== README Contents == | |||
As taken from the Chinese website BetaWorld on their miscellaneous page<ref>https://www.betaworld.cn/%E7%94%A8%E6%88%B7:%E9%9A%8F%E4%BE%BF%E9%97%AE%E6%88%91</ref>: | |||
{{Collapse top|title=Auto-Patch for WinXP #2520}} | |||
{{:文档:autopatch for xp2520}} | |||
{{Collapse bottom}} | |||
It's peculiar this documentation would mention the reversal for bringing back the pop-up balloon since [[Windows XP Build 2495.0.main.010614-1724|Build 2495]] takes it a step further and comments out the respective files completely from <code>TXTSETUP.SIF</code> although this would explain the absence of <code>IDWLOG.EXE</code> now to point it out.<ref>https://www.neofriends.net/threads/method-to-escape-wpabaln-exe.17112/</ref> As you'll soon find out, the "60 day grace period ''(new)''" is no more than the aforementioned product key that would've been considered the best available at this moment in time being automatically injected upon installation: | |||
{{Collapse top|title=RESET3 Release Notes}} | |||
{{:文档:RESET3 RELEASE}} | |||
{{Collapse bottom}} | |||
Furthermore, despite claims that this "should foreseeably work on the RTM version" the error code below is logged when tried on [[Windows XP Build 2542.0.xpclient.010811-1534|Build 2542]] at the last stage in finalizing changes: | |||
<syntaxhighlight lang="doscon"> | |||
C:\WINDOWS\system32\config>regrest system.14D system.old machine system | |||
replacing system with system.14D | |||
Replace failed | |||
hivebranch='machine', hive='system', result='0x000003f1' | |||
newfile='system.14D' | |||
savefile='system.old' | |||
</syntaxhighlight> | |||
== Notable Findings == | |||
Between the Time-Limit "RESET3" Fix and the "SECRESET" script, they more or less expurgate the SECURITY hive at every shutdown/reboot to get rid of the "Activation counters" that keep track of the Grace Period as described by the authors which proves as far more of an undertaking than the previous iteration, [[Windows XP Build 2495.0.main.010614-1724|"RESET2"]], since that procedure isn't enough to function for this build anymore. It's believed this was pioneered by DrSeuss since he wasn't named in the previous release notes as special shout-out was ceremoniously given to members of the WiNBETA DALnet as a whole, the revamped "Reset 5" that only kept the namesake for consistency<ref>https://www.cc-community.net/threads/reset-version-5-unleashed.6062/</ref> gives kudos to AngelDeath & Enyh, previously known from last time, but yet also makes mention of his involvement which alludes to the likelihood he in particular may've played a key role in the making this time around<ref>https://cracknfo.eu/motion/Reset-v5.00-for-Windows-XP,-XPSP1-and-.NET-up-to-RC1-patch-by-WiNBETA-bee114f12a/</ref>. Besides minute changes as to which of the corresponding keys are chosen, the original "RESET3" script creates its own self-identifiable SOFTWARE subkey to back-up the Plug&Play (PnP) information as catalogued by WPA that is then re-applied using <code>regdel</code> provided on the NT 4.0 Resource Kit supplied distinctly for this purpose<ref>https://web.archive.org/web/20040625191235/http://support.microsoft.com/default.aspx?scid=kb;en-us;165042</ref> for removal whereas "SECRESET" neglects this step entirely and uses the traditional <code>reg del /f</code> regardless of any privilege rights as made savvy by the lookup via <code>regdmp</code> to query the <code>CurrentControlSet</code> over the value of <code>HKLM\SYSTEM\Select</code>; it's suspected this difference was made since hardware information is recorded by <code>wpa.dbl</code> and so doing it this way would camouflage any changes done to the system after the fact while at the same time avoiding to trip up any safety guards within the process.<ref>http://windowsxp.htmlplanet.com/page15.htm</ref> | |||
<gallery> | |||
File:PnP-Reset.png|Both scripts together showing precisely this exact difference for reasons explained | |||
</gallery> | |||
== 新增功能和更改 == | == 新增功能和更改 == | ||