Windows Server 2003 patch-v10a-240204.7z

## Windows Server 2003 (NT 5.2.3790.0) build guide *Version 10a, last updated 2020/11/29* Build guide tested under XP SP3 x86, Win7 SP1 x86/x64 & Win10 x64, results may vary under other operating systems. ## Build Preparations --- - It's recommended to disable any AV before extracting/building, as both of those actions create a lot of new files (your AV will likely try scanning every one, slowing down the extraction/build by quite a bit) - this also counts for any other tools that monitor files such as voidtools' Everything. - **Ensure build machine date is current** - there's no longer any need to set date to 2003 or anything. - Extract source tree to a folder named `srv03rtm` on the root of a drive (**important, as pre-built DirectUI files will only link properly under this path**), drive letter doesn't seem to matter (just don't use C:\ drive as that has some extra security), use `D:\srv03rtm\` as the path to match RTM binaries. - Unset Read-only on extracted directory, including subfolders and files (note that after unsetting this and closing/reopening the folder properties again you might see that read-only has been set again, this is fine, as long as you unset it once it should let the build work without issue) - Copy over files from this ZIP into source tree, overwriting existing files as necessary - **If using a 64-bit host OS to build with:** copy the contents of the ZIPs `_x64` folder into the source tree, overwriting if asked. **If your OS doesn't use UAC (XP/2003)**: - Create desktop shortcut for `%windir%\system32\cmd.exe /k D:\srv03rtm\tools\razzle.cmd free offline` (see below for explanation) and change `Start in` to `D:\srv03rtm` - **If using 64-bit host OS** use `razzle64.cmd` in the shortcut instead of `razzle.cmd` - Open razzle window using shortcut you created. **If your OS uses UAC (Vista+)**: - Run command-prompt as administrator (can usually be done by typing cmd into start menu, right click `Command Prompt` -> `Run as administrator`) - In the command-prompt, change to the drive you extracted source-code to by typing in the drive letter , eg. `E:` - Change to the source folder: `cd srv03rtm` - Now start razzle: `tools\razzle.cmd free offline` (**If using 64-bit host OS** use `tools\razzle64.cmd free offline` instead) The first time you run razzle inside that copy of the source code it'll need to initialise a few things, give it a few minutes, after a while a Notepad window will appear - make sure to close this for the initialisation to continue. **Important:** Once razzle has initialised run `tools\prebuild.cmd` to finish preparing the build environment (only need to run once after initing razzle for first time in this tree) ## Building --- **Important:** Currently the build doesn't seem to play well when building with many (over 4) threads. If your build machine has more than that it's recommended to cap it to 4 threads maximum via the `-M 4` switch, added to the build command (eg. `build /cZP -M 4`, or `bcz -M 4`) ### Clean build Performs clean rebuild of all components (**recommended for first build!**): - `build /cZP` (`bcz` is also aliased to this) ### "Dirty" build Builds only components that have changed since last clean build: - `build /ZP` (`bz` is also aliased to this) ### Post-build - Download the [win2003_x86-missing-binaries.7z](https://gofile.io/d/SvWudI) pack, which contains missing binaries for both x86fre & x86chk 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. `D:\binaries.x86fre`, 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 `Yes`, but when asked to overwrite files like DUser.pdb/dll make sure to select `No`!** - Once missing files have been added, you should have files such as `binaries.x86{fre/chk}\_pop3_00.htm`, `binaries.x86{fre/chk}\ql10wnt.sys`, etc. - Inside the razzle window run `tools\postbuild.cmd` (use `-sku:{sku}` if you want to process only specific one (no brackets!), expect `filechk` errors if you ignore this and didn't use missing.7z / missing.cmd with every sku) Once postbuild has finished, assuming you used the `win2003_x86-missing-binaries.7z` file above and followed the guide properly, it should have hopefully succeeded without errors, and there shouldn't be any `binaries.x86fre\build_logs\postbuild.err` file! Otherwise take a look inside the `postbuild.err` - most messages in here are negligible, but if you see `filechk` errors associated with the edition you want to use, you may need to re-run `missing.cmd`, or extract `2k3-missing.7z` again. If `postbuild.err` contains messages like `(crypto.cmd) ERROR` or `(ntsign.cmd) ERROR` try re-importing the `tools\driver.pfx` 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 (updated certs are only valid from October 2020 to October 2021) If postbuild.err has filechk errors about missing `hwcomp.dat` files, try copying the following into a batch script and run it in a razzle prompt (after using postbuild once already): ``` @echo off hwdatgen -i:%_NTPOSTBLD%\pro\i386 -o:%_NTPOSTBLD%\.\hwcomp.dat hwdatgen -i:%_NTPOSTBLD%\per\i386 -o:%_NTPOSTBLD%\perinf\hwcomp.dat hwdatgen -i:%_NTPOSTBLD%\bla\i386 -o:%_NTPOSTBLD%\blainf\hwcomp.dat hwdatgen -i:%_NTPOSTBLD%\sbs\i386 -o:%_NTPOSTBLD%\sbsinf\hwcomp.dat hwdatgen -i:%_NTPOSTBLD%\srv\i386 -o:%_NTPOSTBLD%\srvinf\hwcomp.dat hwdatgen -i:%_NTPOSTBLD%\ads\i386 -o:%_NTPOSTBLD%\entinf\hwcomp.dat ``` ### Creating bootable ISO files - Execute `tools\oscdimg.cmd {sku} [destination-file (optional)]` where `{sku}` is one of: - `srv` - Windows Server 2003 Standard Edition - `sbs` - Windows Server 2003 Small Business Edition - `ads` - Windows Server 2003 Enterprise Edition - `dtc` - Windows Server 2003 Datacenter Edition - `bla` - Windows Server 2003 Web Edition - `per` - Windows XP Home Edition - `pro` - Windows XP Professional - ISO will be saved to `{build-drive}\{build-tag}_{sku}.iso`, unless `[destination-file]` 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. ###### After running razzle it shows a bunch of errors, "tfindcer not recognized" etc You're likely on a 64-bit system but running `razzle.cmd` directly, you should use `razzle64.cmd` instead, this'll set things up so that razzle will use the correct tools for you. Hopefully with that the `tfindcer not recognized` & other errors should go away. ###### During build I get a `directui.lib(parse.obj) LNK2011` error, mentioning `precompiled object not linked in` This is caused by the pre-built parse.obj file we currently have to use in order to build a working directui.lib, currently this file requires your source tree to be inside a `srv03rtm` folder on the root of a drive, using any other folder will cause the error to happen. Sadly attempts to fix this such as editing the parse.obj or updating the code to build parse.cpp instead haven't been successful yet. ###### After a full build I get 1000+ errors, build.err has `has bad storage class` errors inside Seems to be caused by your locale, this is reported to happen with Simplified Chinese language, but can probably happen with other languages too. Besides changing your locale/language settings, you could also try editing the source files to remove the characters that cause problems, an anon posted a list of the files that need changes [here](https://archive.rebeccablacktech.com/g/thread/78406946/#78416976) ###### I get a `TAPI.RES` error