Getting Started: Difference between revisions

This guide tested under Windows XP, 7 SP1, 8.1 & 10 x86/x64, results may vary under other operating systems (if you will copy/paste source code at many times). For legacy version of the guide visit [https://rentry.co/build-win2k3 build-win2k3].

* 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.

* 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.

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>.

* 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>)

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

* Download the Missing Binaries pack, 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>!'''

* 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.

* 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!

 

* 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>sbs</code> - Windows Server 2003 Small Business Edition

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

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

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

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

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

** <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.

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.

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]

=== 'OfficialBuild' parameter / BuildMachines.txt ===

The <code>OfficialBuild</code> razzle parameter changes a few things in the build, which will make it match up closer to the retail builds, should be useful if you need to compare against retail for any reason.

 

For a list of things affected by the OfficialBuild parameter see <nowiki>https://pastebin.com/VgVph3Xv</nowiki> & <nowiki>https://pastebin.com/gYzWGLM5</nowiki>, thanks to the anon that compiled them! (note that these aren't complete lists, and not all things mentioned here are guaranteed to take effect).

 

'''However, using this parameter requires a file to be updated with info about your build machine first!'''

 

An easy way to update the file required is to run the following command inside a razzle window, at the root of the source tree:

 

<code>echo %COMPUTERNAME%,primary,%_BuildBranch%,%_BuildArch%,%_BuildType%,ntblus >> tools\BuildMachines.txt</code>

 

After that you can run <code>tools\verifybuildmachine</code> to make sure it was setup correctly, if there's any problem an error message will show, otherwise the command will return without any message.

 

With that in place you should now be able to use the <code>OfficialBuild</code> parameter next time you init razzle, eg. <code>tools\razzle.cmd free offline officialbuild</code>

 

Some small notes to be aware of:

* if you change build arch or build type (eg. to amd64, or to a checked build) you'll need to run the echo command again to add your machine for that build arch/type combination

* if you see <code>Clearing OFFICIAL_BUILD_MACHINE variable</code> after initializing razzle, rerun the echo command and then close down/re-initalize razzle again, else the build won't properly count itself as official.