Getting Started: Difference between revisions

Line 2:

== Preparing for Build ==

Disable any AV (and Windows Defender) before extracting and building, as both of those actions create a lot of new files, and AV scans for execution of them all - this also counts for any other tools that monitor files, such as voidtools' Everything, but they aren't impacting much as your antivirus does. Also disable User Account Control. This can be accomplished via Control Panel, or via Registry Key: navigate to <code>HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System</code> and set <code>EnableLUA</code> to <code>0</code>. Some versions may require restart after registry apply.

* Disable any AV (and Windows Defender) before extracting and building, as both of those actions create a lot of new files, and AV scans for execution of them all - this also counts for any other tools that monitor files, such as voidtools' Everything, but they aren't impacting much as your ~~antivirus does.~~

After preparing your machine, extract source tree to a folder named <code>srv03rtm</code>, or <code>srvrtm</code> on the root of a drive, drive letter doesn't seem to matter (just don't use C:\ drive as that has some extra security). It is recommended to use <code>D:\srvrtm\</code> as the path to match RTM binaries.

* Also disable User Account Control. This can be accomplished via Control Panel, ~~or via Registry Key: navigate~~ to <code>~~HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System~~</code> ~~and set <code>EnableLUA</code> to <code>0~~</code>~~. Some versions may require restart after registry apply.~~

* Extract source tree to a folder named <code>srv03rtm</code> on the root of a drive, drive letter doesn't seem to matter (just don't use C:\ drive as that has some extra security). It is recommended to use <code>D:\~~srv03rtm~~\</code> as the path to match RTM binaries.

=== For 2000/XP/2003 Users ===

Before initializing Razzle, it's mandatory to install .NET Framework 1.1, because without it Razzle will fail to initialize environment normally (despite that two versions of .NET 1.1 are included in <code>tools\x86</code>). The ~~installer is~~ included at <code>tools\prereq</code>.

Before initializing Razzle, you should update your build machine. If you're using Windows XP/Server 2003, and you haven't updated it yet with [https://legacyupdate.net Legacy Update], it's mandatory to install .NET Framework 1.1, because without it Razzle will fail to initialize environment normally (despite that two versions of .NET 1.1 are included in <code>tools\x86</code>). The installation files are included in <code>tools\prereq</code> folder.

=== Running environment ===

* Run command-prompt as administrator (can usually be done by typing <code>cmd</code> into start menu, right click <code>Command Prompt</code> -> <code>Run as administrator</code>)

* Run command-prompt as administrator (can usually be done by typing <code>cmd</code> into start menu, or by right click <code>Command Prompt</code> -> <code>Run as administrator</code>)

* In the command-prompt, change to the source folder: <code>cd /d D:\~~srv03rtm~~</code>

* In the command-prompt, change to the source folder: <code>cd /d D:\srvrtm</code>

* Now start razzle: <code>tools\razzle.cmd free offline</code> for 32-bit clients, and <code>tools\razzle64.cmd free offline</code> for 64-bits. This initiates retail build of x86. The first time you run razzle inside that copy of the source code it'll need to initialize a few things, give it a few minutes, after a while a Notepad window will appear - make sure to close this for the initialization to continue.

* '''Important for first time!''' Run the prebuild script, if you're initiating source code for first time: <code>tools\prebuild</code>. This scripts sets all read-only attributes for necessary stuff and makes 16-bit stuff workable for x64 environments.

If you want to have official builds, append <code>official</code> argument. This argument is modified and removed <code>OfficialBuild</code> argument, which previously checked build machine for eligibility of building official builds. <code>official</code> argument sets necessary values for official build independently of your machine eligibility, because of it's moot behavior and requirement to be connected into legacy build servers.

=== Build ===

Line 24:

=== Post-build ===

* Download the Missing Binaries pack, which contains missing binaries both for AMD64 and x86 builds.

* Download the Missing Binaries pack from OpenXP Download Center, which contains missing binaries both for AMD64 and x86 builds.

* ~~From that 7z, extract~~ the contents of the binaries folder for the build type you're building into your build trees binaries folder (eg. <code>D:\binaries.x86fre</code>, should have been created during the build), the 7z should contain files for all SKUs (uses pidgen.dll from Win2003 Enterprise, so your builds should accept Enterprise product keys), '''When asked during extraction to overwrite folders select <code>Yes</code>, but when asked to overwrite files, make sure to select <code>No</code>!'''

* Extract the contents of the binaries folder for the build type you're building into your build trees binaries folder (e.g. <code>D:\binaries.x86fre</code>, should have been created during the build), the 7z should contain files for all SKUs (uses <code>pidgen.dll</code> from Win2003 Enterprise, so your builds should accept Enterprise product keys), '''When asked during extraction to overwrite folders select <code>Yes</code>, but when asked to overwrite files, make sure to select <code>No</code>!'''

* Inside the razzle window run <code>tools\postbuild</code> (use <code>-sku:{sku}</code> if you want to process only specific one (no brackets!), expect <code>filechk</code> errors if you ~~ignore this and didn~~'t ~~use~~ missing.7z / ~~missing~~.~~cmd with every sku). For first time~~ you ~~can use~~ <code>~~tools\postbuild~~ -full</code>~~, altrough it isn't necessary.~~

* Inside the razzle window run <code>tools\postbuild</code>. You can use <code>-sku:{sku}</code> if you want to process only specific one (no brackets!), expect <code>filechk</code> errors, if you haven't extracted missing binaries from <code>misbin.7z</code>. If you have a wish to do a full post-build, append <code>-full</code> argument

==== Issues ====

* Once ~~postbuild~~ has finished, assuming you used the <code>misbin.7z</code> file above and followed the guide properly, it should have hopefully succeeded without errors, and there shouldn't be any <code>binaries.x86fre\build_logs\postbuild.err</code> file!

* Once post-build has finished, assuming you used the <code>misbin.7z</code> file above and followed the guide properly, it should have hopefully succeeded without errors, and there shouldn't be any <code>binaries.x86fre\build_logs\postbuild.err</code> file!

* Otherwise take a look inside the <code>postbuild.err</code> - most messages in here are negligible, but if you see <code>filechk</code> errors associated with the edition you want to use, you may need to re-run <code>tools\missing.cmd</code>, or extract <code>misbin.7z</code> again.

* If <code>postbuild.err</code> contains messages like <code>(crypto.cmd) ERROR</code> or <code>(ntsign.cmd) ERROR</code> try re-importing the <code>tools\driver.pfx</code> key-file (double-click it, press Next through the prompts, password is empty), and make sure your system date is set to the current date.

Line 44:

=== Creating ISO files ===

Execute <code>tools\oscdimg {sku} [destination-file (optional)]</code> where <code>{sku}</code> is one of:

* Execute <code>tools\oscdimg {sku} [destination-file (optional)]</code> where <code>{sku}</code> is one of:

* <code>srv</code> - Windows Server 2003 Standard Edition

** <code>srv</code> - Windows Server 2003 Standard Edition

* <code>sbs</code> - Windows Server 2003 Small Business Edition

** <code>sbs</code> - Windows Server 2003 Small Business Edition

* <code>ads</code> - Windows Server 2003 Enterprise Edition

** <code>ads</code> - Windows Server 2003 Enterprise Edition

* <code>dtc</code> - Windows Server 2003 Datacenter Edition

** <code>dtc</code> - Windows Server 2003 Datacenter Edition

* <code>bla</code> - Windows Server 2003 Web Edition

** <code>bla</code> - Windows Server 2003 Web Edition

* <code>per</code> - Windows XP Home Edition

** <code>per</code> - Windows XP Home Edition

* <code>pro</code> - Windows XP Professional

** <code>pro</code> - Windows XP Professional

* <code>winpe</code> - Windows Preinstallation Environment

** <code>winpe</code> - Windows Preinstallation Environment

ISO will be saved to <code>{build-drive}\{build-tag}_{sku}.iso</code>, unless <code>[destination-file]</code> is provided as a parameter.

* ISO will be saved to <code>{build-drive}\{build-tag}_{sku}.iso</code>, unless <code>[destination-file]</code> is provided as a parameter.

=== Troubleshooting ===

If you get any problems during the build hopefully your problem might be answered ~~here~~, ~~if it's not feel free to post in the thread.~~

If you get any problems during the build hopefully your problem might be answered in our Discord server, by lurking

====== Certificate Import Wizard: An internal error occurred... ======

Line 86:

Line 85:

Kernel debugging can be enabled by editing the <code>C:\boot.ini</code> file in your installed build, and adding <code>/debug /debugport=COM1 /baudrate=115200</code> to the end of a config line.

For example here's a boot.ini with two choices, one with debugging & one without, with this NTLDR will show an OS boot choice menu at startup:<blockquote>[boot loader]

For example here's a <code>boot.ini</code> with two choices, one with debugging & one without, with this NTLDR will show an OS boot choice menu at startup:<blockquote>[boot loader]

timeout=30

@@ Line 2: / Line 2: @@
 == Preparing for Build ==
+Disable any AV (and Windows Defender) before extracting and building, as both of those actions create a lot of new files, and AV scans for execution of them all - this also counts for any other tools that monitor files, such as voidtools' Everything, but they aren't impacting much as your antivirus does. Also disable User Account Control. This can be accomplished via Control Panel, or via Registry Key: navigate to <code>HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System</code> and set <code>EnableLUA</code> to <code>0</code>. Some versions may require restart after registry apply.
-* Disable any AV (and Windows Defender) before extracting and building, as both of those actions create a lot of new files, and AV scans for execution of them all - this also counts for any other tools that monitor files, such as voidtools' Everything, but they aren't impacting much as your antivirus does.
+After preparing your machine, extract source tree to a folder named <code>srv03rtm</code>, or <code>srvrtm</code> on the root of a drive, drive letter doesn't seem to matter (just don't use C:\ drive as that has some extra security). It is recommended to use <code>D:\srvrtm\</code> as the path to match RTM binaries.
-* Also disable User Account Control. This can be accomplished via Control Panel, or via Registry Key: navigate to <code>HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System</code> and set <code>EnableLUA</code> to <code>0</code>. Some versions may require restart after registry apply.
-* Extract source tree to a folder named <code>srv03rtm</code> on the root of a drive, drive letter doesn't seem to matter (just don't use C:\ drive as that has some extra security). It is recommended to use <code>D:\srv03rtm\</code> as the path to match RTM binaries.
 === For 2000/XP/2003 Users ===
-Before initializing Razzle, it's mandatory to install .NET Framework 1.1, because without it Razzle will fail to initialize environment normally (despite that two versions of .NET 1.1 are included in <code>tools\x86</code>). The installer is included at <code>tools\prereq</code>.
+Before initializing Razzle, you should update your build machine. If you're using Windows XP/Server 2003, and you haven't updated it yet with [https://legacyupdate.net Legacy Update], it's mandatory to install .NET Framework 1.1, because without it Razzle will fail to initialize environment normally (despite that two versions of .NET 1.1 are included in <code>tools\x86</code>). The installation files are included in <code>tools\prereq</code> folder.
 === Running environment ===
-* Run command-prompt as administrator (can usually be done by typing <code>cmd</code> into start menu, right click <code>Command Prompt</code> -> <code>Run as administrator</code>)
+* Run command-prompt as administrator (can usually be done by typing <code>cmd</code> into start menu, or by right click <code>Command Prompt</code> -> <code>Run as administrator</code>)
-* In the command-prompt, change to the source folder: <code>cd /d D:\srv03rtm</code>
+* In the command-prompt, change to the source folder: <code>cd /d D:\srvrtm</code>
 * Now start razzle: <code>tools\razzle.cmd free offline</code> for 32-bit clients, and <code>tools\razzle64.cmd free offline</code> for 64-bits. This initiates retail build of x86. The first time you run razzle inside that copy of the source code it'll need to initialize a few things, give it a few minutes, after a while a Notepad window will appear - make sure to close this for the initialization to continue.
 * '''Important for first time!''' Run the prebuild script, if you're initiating source code for first time: <code>tools\prebuild</code>. This scripts sets all read-only attributes for necessary stuff and makes 16-bit stuff workable for x64 environments.
+If you want to have official builds, append <code>official</code> argument. This argument is modified and removed <code>OfficialBuild</code> argument, which previously checked build machine for eligibility of building official builds. <code>official</code> argument sets necessary values for official build independently of your machine eligibility, because of it's moot behavior and requirement to be connected into legacy build servers.
 === Build ===
@@ Line 24: / Line 24: @@
 === Post-build ===
-* Download the Missing Binaries pack, which contains missing binaries both for AMD64 and x86 builds.
+* Download the Missing Binaries pack from OpenXP Download Center, which contains missing binaries both for AMD64 and x86 builds.
-* From that 7z, extract the contents of the binaries folder for the build type you're building into your build trees binaries folder (eg. <code>D:\binaries.x86fre</code>, should have been created during the build), the 7z should contain files for all SKUs (uses pidgen.dll from Win2003 Enterprise, so your builds should accept Enterprise product keys), '''When asked during extraction to overwrite folders select <code>Yes</code>, but when asked to overwrite files, make sure to select <code>No</code>!'''
+* Extract the contents of the binaries folder for the build type you're building into your build trees binaries folder (e.g. <code>D:\binaries.x86fre</code>, should have been created during the build), the 7z should contain files for all SKUs (uses <code>pidgen.dll</code> from Win2003 Enterprise, so your builds should accept Enterprise product keys), '''When asked during extraction to overwrite folders select <code>Yes</code>, but when asked to overwrite files, make sure to select <code>No</code>!'''
-* Inside the razzle window run <code>tools\postbuild</code> (use <code>-sku:{sku}</code> if you want to process only specific one (no brackets!), expect <code>filechk</code> errors if you ignore this and didn't use missing.7z / missing.cmd with every sku). For first time you can use <code>tools\postbuild -full</code>, altrough it isn't necessary.
+* Inside the razzle window run <code>tools\postbuild</code>. You can use <code>-sku:{sku}</code> if you want to process only specific one (no brackets!), expect <code>filechk</code> errors, if you haven't extracted missing binaries from <code>misbin.7z</code>. If you have a wish to do a full post-build, append <code>-full</code> argument
 ==== Issues ====
-* Once postbuild has finished, assuming you used the <code>misbin.7z</code> file above and followed the guide properly, it should have hopefully succeeded without errors, and there shouldn't be any <code>binaries.x86fre\build_logs\postbuild.err</code> file!
+* Once post-build has finished, assuming you used the <code>misbin.7z</code> file above and followed the guide properly, it should have hopefully succeeded without errors, and there shouldn't be any <code>binaries.x86fre\build_logs\postbuild.err</code> file!
 * Otherwise take a look inside the <code>postbuild.err</code> - most messages in here are negligible, but if you see <code>filechk</code> errors associated with the edition you want to use, you may need to re-run <code>tools\missing.cmd</code>, or extract <code>misbin.7z</code> again.
 * If <code>postbuild.err</code> contains messages like <code>(crypto.cmd) ERROR</code> or <code>(ntsign.cmd) ERROR</code> try re-importing the <code>tools\driver.pfx</code> key-file (double-click it, press Next through the prompts, password is empty), and make sure your system date is set to the current date.
@@ Line 44: / Line 44: @@
 === Creating ISO files ===
+Execute <code>tools\oscdimg {sku} [destination-file (optional)]</code> where <code>{sku}</code> is one of:
-* Execute <code>tools\oscdimg {sku} [destination-file (optional)]</code> where <code>{sku}</code> is one of:
+* <code>srv</code> - Windows Server 2003 Standard Edition
-** <code>srv</code> - Windows Server 2003 Standard Edition
+* <code>sbs</code> - Windows Server 2003 Small Business Edition
-** <code>sbs</code> - Windows Server 2003 Small Business Edition
+* <code>ads</code> - Windows Server 2003 Enterprise Edition
-** <code>ads</code> - Windows Server 2003 Enterprise Edition
+* <code>dtc</code> - Windows Server 2003 Datacenter Edition
-** <code>dtc</code> - Windows Server 2003 Datacenter Edition
+* <code>bla</code> - Windows Server 2003 Web Edition
-** <code>bla</code> - Windows Server 2003 Web Edition
+* <code>per</code> - Windows XP Home Edition
-** <code>per</code> - Windows XP Home Edition
+* <code>pro</code> - Windows XP Professional
-** <code>pro</code> - Windows XP Professional
+* <code>winpe</code> - Windows Preinstallation Environment
-** <code>winpe</code> - Windows Preinstallation Environment
+ISO will be saved to <code>{build-drive}\{build-tag}_{sku}.iso</code>, unless <code>[destination-file]</code> is provided as a parameter.
-* ISO will be saved to <code>{build-drive}\{build-tag}_{sku}.iso</code>, unless <code>[destination-file]</code> is provided as a parameter.
 === Troubleshooting ===
-If you get any problems during the build hopefully your problem might be answered here, if it's not feel free to post in the thread.
+If you get any problems during the build hopefully your problem might be answered in our Discord server, by lurking
 ====== Certificate Import Wizard: An internal error occurred... ======
@@ Line 86: / Line 85: @@
 Kernel debugging can be enabled by editing the <code>C:\boot.ini</code> file in your installed build, and adding <code>/debug /debugport=COM1 /baudrate=115200</code> to the end of a config line.
-For example here's a boot.ini with two choices, one with debugging & one without, with this NTLDR will show an OS boot choice menu at startup:<blockquote>[boot loader]
+For example here's a <code>boot.ini</code> with two choices, one with debugging & one without, with this NTLDR will show an OS boot choice menu at startup:<blockquote>[boot loader]
 timeout=30