Windows XP Build 2600.1089.xpsp1.020801-1815
| Windows XP 的版本 | |
 | |
| 操作系统系列 | Windows NT 系列 |
|---|---|
| NT 版本 | Windows NT 5.1 |
| 内部版本号 | 2600 |
| 修订版本号 | 1089 |
| 体系结构 | x86 |
| 内部版本实验室 | xpsp1 |
| 编译日期 | 2002 年 8 月 1 日 |
| 关于对话框 | |
 | |
Windows XP Build 2600.1089 是 Windows XP 的未泄露 Service Pack 1 测试版本。它在 2002 年 8 月初的某个时候向测试人员发布，and was then shared online on 6 August 2002.[1]尽管版本本身尚未找到。此版本同时还是提及版本，在 Microsoft 故障排除文章中还引用了它，此文章记录了阻止安装 Build 2600.1079 的 PartitionMagic 相关注册表问题，其中指出已实施解决方法。
已知仅存在一张屏幕截图。[2]
文档
以下帮助文章在此处重新发布，仅用于存档目的。
知识库文章“System could not allocate the required space in registry log（系统无法在注册表日志中分配所需的空间）”：
System could not allocate the required space in registry log
Partition Magic makes changes to the registry. These changes take place during the process of resizing a partition. It is possible other changes made by Partition Magic also make registry changes, but this is only known instance where an issue has come up. This change to the registry has been present when using Partition Magic, however has not caused any known issues that we are aware of in prior releases of our operating systems.
Build 1079 and later versions of the service pack will expose this registry change with an error. When you install Service Pack 1 for Windows XP you will get the following error message. "System could not allocate the required space in registry log."
- Build 1079 presents this error. Build 1050 did not.
- Build 1089 and later builds have a workaround in place for people did not run into this problem with 1079.
Steps to reproduce: Run Partition Magic and resize the partition. When Partition Magic runs it modifies the system hive of the registry.
Partition Magic makes changes to the registry at boot time before the OS is loaded. They rename the registry mounteddevices key.
HKEY_Local_Machine\System\MountedDevices
The MountedDevices key is later renamed back. A new key is left in place MountedDevice1 for trouble-shooting purposes. The way the registry is modified affects the changes in build 1079 when we look at the LastKnownGood entry. The entry is not at the expected location, thus the error is generated. We can work around the issue in the next release of Service Pack 1 by making changes to mounteddevice1 registry key.
Resolution: The built in workaround only applies to systems that did not previously install 1079 and ran across the registry error message. If the user previously had the error. "System could not allocate the required space in registry log." you may not be able to install the service pack unless you restore from an image without any previous 1079 installation failures.
This is due to uninstall failing to complete properly and leaving the system in a partially installed / uninstalled state. If the uninstall actually succeeded, it may very well be possible to install build 1089 or a later version of the service pack. However, all internal attempts to install the service pack after this type of failure were unsuccessful. Booting with last known good also failed to resolve this problem.
This key is not used by the OS and is left on the system only for trouble-shooting. This registry entries will be fully fixed with Service Pack Two for Windows XP and will be fully fixed in Windows .NET. Powerquest is working on resolution that will prevent this from happening and will update their software.
