Windows XP Build 2505.0.main.010626-1514：修订间差异

As it turns out, a copy of the relevant OEM Preinstallation Kit (OPK) intended for use by system builders can be found in the "Friends and Family" self-host variant of Release Candidate 1 handed out to Microsoft employees<ref>https://archive.org/details/ms-winxp-rc1-family-evalkit</ref> that is believed to be the most widespread distribution containing such due to its encouragement of showcasing with those closest to the holder although could’ve possibly appeared in an entirely different “Evaluation Kit” as well<ref>https://archive.org/details/photo-aug-23-12-03-10-pm/</ref>. Traditionally, extra components were made available only to business customers within the corporate sector in possession of the corresponding WinPE toolkit CD dependent on version number{{efn|“..\..\docs\winpe” in the same source code reveals this difference between Independent Software Vendors (ISV)’s that are granted permission for use of the OPK and corporations that enter into a contract to own the WinPE toolkit CD. To cut it short; besides stating that ISV’s were barred from “run[ning] any Microsoft executables” whatsoever per licensing agreements disallowing them “support for standard scripting environments used to create custom tools” such as what can be created by these scripts, it turns out they were planned to be unified into one so that “WSH is included automatically [alongside HTA if chosen so that it] cannot be removed” however since the docs were written [[Windows 预安装环境#版本列表|just a few some short months after RTM]] it appears only the output was made available which bears some resemblance here with system components provided in compressed ZIP archives that negate need for checking the CD tag file.}}; of these offered include optional support for either MSFT. HTML Applications (MSHTA) & Windows Script Host (WSH) to aid in deploying system images onto [[Windows XP Embedded|embedded units]] over net share and/or ActiveX Data Objects (ADO) that allow for database connectivity to a [[SQL Server 2000|Microsoft SQL Server]].

So the inclusion of an image builder script right in the leaked [[Windows XP]] SP1 source code (located at <code>base\ntsetup\opktools\winpeoc\imgbld\</code> as superseded by the contents of <code>winpebins</code>) may come at a surprise to some as it contains leftovers for this stage of development particularly{{efn|Having been outlined in the “..\xwinpe\docs\winpe build process.doc” with mention of [[Windows XP Build 2496.0.main.010615-1711|interim builds]] matching in close proximity.}} that is able to create Windows PE media which incorporate this very functionality when used alongside. Despite having the ability to select CD-ROM as the drive type for creating an ISO image, the custom-made <code>autoexec.cmd</code> script to initialize corresponding DLL libraries will try to CD to a nonexistent <code>\MININT</code> directory upon completion due to only being applicable when creating bootable flash drives. One other thing worth mentioning is the fact Home Edition won’t be sufficient enough for this specific use case since the detection checks put in-place require for the Professional SKU media to be inserted as warned throughout the beginning steps of the process.