The OpenXP Wiki - User contributions [en]

Talk:Welcome

2025-11-16T23:26:59Z

UltimateQuack: /* Does OPENXP prioritize x64 or x86? (32-bit) */ new section

== Does OPENXP prioritize x64 or x86? (32-bit) ==

Question about codebase. [[User:UltimateQuack|UltimateQuack]] ([[User talk:UltimateQuack|talk]]) 23:26, 16 November 2025 (UTC)

User:UltimateQuack

2025-11-16T23:14:31Z

UltimateQuack: Created page with "Quack!"

Quack!

Development reset

2025-11-16T23:13:14Z

UltimateQuack: Better hyperlinking.

'''The Development Reset''' was one of the main, crucial events of the OpenXP development, which made the development of the [[OpenXP|codebase]] drop back to level 0.

== Reasons ==
OpenXP was a beginner project, and therefore it recruited developers with almost no experience and of any age. One of the developers hosted the Git server, until they were kicked out in November after deleting everything over allegations of problematic behavior. Source code was mirrored and backed up by the lead developer on his resources, and the mirror was recovered and development continued.

However development reset was already planned to happen, due to the messy and incomplete behavior of new programs, useless laboratory system and lots of inactive developers. It happened in November, 2024, and since then OpenXP's official website, wiki and download center have been released, with many more things coming soon.

[[Category:OpenXP]]
[[Category:History]]

Certificate Generation

2025-11-16T23:11:20Z

UltimateQuack: It is -> It's

This article will help you to generate valid certificates for [[OpenXP]] compilation via '''CertUtil''' CLI tool. It's very crucial to proceed compiled builds setup and bypass uncertified checks.

=== Prerequisites ===
For this guide you should have Linux machine (it may be virtual and local), or either an MSYS2 or Cygwin installed to your Windows machine. You can also use Git Bash, as it is practically the same MSYS2 shell, only modified to work better with Linux version of Git. This utility will be upgraded to work on Windows machines natively too, in near future.

== Generation ==

* For first, clone the tool from our [https://codeberg.org/openxp/certutil Codeberg repository] via this command: <code>git clone <nowiki>https://codeberg.org/openxp/certutil</nowiki></code>
* Then after, make your binaries executable recursively: <code>chmod 777 * -R</code>
* Then convert ''.sh'' files from DOS to Unix with '''dos2unix''' utility. It usually appears with MSYS2 by default, but if it's not, install it on your environment: <code>dos2unix generate.sh</code>
* And finally, execute generation script: <code>./generate.sh</code>

Resulted certificates will be placed on ''<code>srv03rtm.certs</code>'', which you simply need to copy to root of source code and replace all items there. Script also creates modified versions of certain checker files, which have hardcoded certificate bytes relying on current certificates, so it's vital to have them matched with newly generated certificates, otherwise builds will be screwed.
[[Category:Development]]

Razzle

2025-11-16T23:10:09Z

UltimateQuack: , -> ;

'''Razzle''' is the build environment of Windows NT operating systems, which is used in OpenXP too. It's name comes after the codename of Windows NT 3.1, and it's purpose is to define building variables and set up an environment for building necessary components and source code of Windows NT.

It was also used in OS/2 before the partnership refusal between Microsoft and IBM in plan of OS/2 development.

== Usage ==
The common arguments of Razzle are following:

* <code>free</code> - retail build;
* <code>chk</code> - checked build, which contains additional debugging information and therefore slower in execution;
* <code>offline</code> - isolates source code from Source Depot or similar linked programs. Without this argument, Razzle tries to connect with the source server via <code>sd.exe</code>, but due to internal addresses absence, it goes abrupt and errors start to appear. This workaround is fixed in OpenXP internally, changing points to Git.

=== Architectures ===
By default, Razzle builds for x86 platforms. To specify another one, you should append one of these arguments after previous one:

* <code>win64</code> - choosing an Intel Itanium 64 (IA-64) target for build. If you append <code>amd64</code>, it will build for AMD64 targets;
* <code>pocketpc</code> - builds ARMv4 target, prevailingly for Windows CE 2003 (or Windows Mobile 2003).

=== Miscellaneous ===
Miscellaneous arguments of Razzle are these:

* <code>verbose</code> - executes Razzle script suite and outputs every action happening;
* <code>ntttest</code> - builds NT test sources (if they exist);
* <code>emulation</code> - builds sources runnable on various simulators of processors and their architectures;
* <code>chkkernel</code> - builds checked versions of NT kernel;
* <code>no_opt</code> - disables compiler optimizations which may lead to larger file sizes;
* <code>mui_magic</code> - generates language-neutral (or pseudo language) build. Highly incomplete and needs workarounds;
* <code>no_binaries</code> - compiles without creating specific directory for binaries (e.g. <code>binaries.x86fre</code>);
* <code>binaries_dir</code> - specifies custom path of binaries different from original one;
* <code>sepchar</code> - replaces dot in binaries path with custom symbol, specified by user;
* <code>postbld_dir</code> - specifies path of post-build directory;
* <code>temp</code> - specifies custom temporary folder;
* <code>no_title</code> - disallows title change of Command Prompt to "Build Environment";
* <code>no_certcheck</code> - doesn't check for code signing certificate existence;
* <code>no_sdrefresh</code> - doesn't update Source Depot client (sd.exe);
* <code>restricted_path</code> - sets path to the same restricted path that build uses (for debugging "why can't build find my tool" problems);
* <code>officialbuild</code> - makes retail builds, reducing remnants of development code. It checks for tools/BuildMachines.txt, and if exists, the specific values to build official builds;
* <code>exec</code> - optional arguments to execute after Razzle initiation:
* <code>enigma</code> - turns on CSP signing and CSP signature checks;
* <code>vaultsign</code> - requires CSP's to be vault signed with the Microsoft key.
[[Category:OpenXP]]

Razzle

2025-11-16T23:08:39Z

UltimateQuack: Grammar fixing and stuff.²

'''Razzle''' is the build environment of Windows NT operating systems, which is used in OpenXP too. It's name comes after the codename of Windows NT 3.1, and it's purpose is to define building variables and set up an environment for building necessary components and source code of Windows NT.

It was also used in OS/2 before the partnership refusal between Microsoft and IBM in plan of OS/2 development.

== Usage ==
The common arguments of Razzle are following:

* <code>free</code> - retail build,
* <code>chk</code> - checked build, which contains additional debugging information and therefore slower in execution,
* <code>offline</code> - isolates source code from Source Depot or similar linked programs. Without this argument, Razzle tries to connect with the source server via <code>sd.exe</code>, but due to internal addresses absence, it goes abrupt and errors start to appear. This workaround is fixed in OpenXP internally, changing points to Git.

=== Architectures ===
By default, Razzle builds for x86 platforms. To specify another one, you should append one of these arguments after previous one:

* <code>win64</code> - choosing an Intel Itanium 64 (IA-64) target for build. If you append <code>amd64</code>, it will build for AMD64 targets,
* <code>pocketpc</code> - builds ARMv4 target, prevailingly for Windows CE 2003 (or Windows Mobile 2003).

=== Miscellaneous ===
Miscellaneous arguments of Razzle are these:

* <code>verbose</code> - executes Razzle script suite and outputs every action happening,
* <code>ntttest</code> - builds NT test sources (if they exist),
* <code>emulation</code> - builds sources runnable on various simulators of processors and their architectures,
* <code>chkkernel</code> - builds checked versions of NT kernel,
* <code>no_opt</code> - disables compiler optimizations which may lead to larger file sizes,
* <code>mui_magic</code> - generates language-neutral (or pseudo language) build. Highly incomplete and needs workarounds,
* <code>no_binaries</code> - compiles without creating specific directory for binaries (e.g. <code>binaries.x86fre</code>),
* <code>binaries_dir</code> - specifies custom path of binaries different from original one,
* <code>sepchar</code> - replaces dot in binaries path with custom symbol, specified by user,
* <code>postbld_dir</code> - specifies path of post-build directory,
* <code>temp</code> - specifies custom temporary folder,
* <code>no_title</code> - disallows title change of Command Prompt to "Build Environment",
* <code>no_certcheck</code> - doesn't check for code signing certificate existence,
* <code>no_sdrefresh</code> - doesn't update Source Depot client (sd.exe),
* <code>restricted_path</code> - sets path to the same restricted path that build uses (for debugging "why can't build find my tool" problems),
* <code>officialbuild</code> - makes retail builds, reducing remnants of development code. It checks for tools/BuildMachines.txt, and if exists, the specific values to build official builds,
* <code>exec</code> - optional arguments to execute after Razzle initiation,
* <code>enigma</code> - turns on CSP signing and CSP signature checks,
* <code>vaultsign</code> - requires CSP's to be vault signed with the Microsoft key.
[[Category:OpenXP]]

Download Center

2025-11-16T23:06:14Z

UltimateQuack: Removed unnecessary ","

'''OpenXP's Download Center''' is a dedicated place from where you can download Windows Server 2003's source code and patches released by OpenXP. This website is generally available for everyone to download all that stuff, and for public files it doesn't require registration.

== Planned features ==
At this moment, OpenXP's Download Center lacks several functionalities, which will be added in the future:

* Better UI for the website,
* Ability to download insider builds (available for testers),
* Sharing of downloadable items/links to everyone,
* Limiting download of constant items per day.

[[Category:OpenXP]]

Sandbox:OpenKernel

2025-11-16T23:04:52Z

UltimateQuack: Grammar fixing and stuff.

{{Revision|revision=1}}

'''OpenKernel''' (shortly `''ONT`'', ''`OK''`, longer ''`OpenXP Kernel`'') is a new, working-in-progress, upcoming sub-project of [[OpenXP]], intended to gradually replace the Windows NT kernel provided on the Windows Server 2003 source code tree. In difference of ReactOS, OpenKernel will be intended for more stability, reliability and more optimized behavior, in order to be flexible and expandable in modern terms of operating system development.

== Description ==
OpenKernel is an inspiration of combining original NT kernel with Microsoft's MinWin project, which is the partial refactor of the first one. Also huge accent will be placed into Linux principles of kernel development, because NT structure is itself great and promising, therefore rewrite of NT kernel is need, to turn NT into a really portable system. The architectural differences in contrary of NT Kernel are following:

# '''All functionalities into one kernel, instead of multiple ones''': this allows to reduce amount of produced binaries, and provide single in-replacement file for <code>ntoskrnl.exe</code>, <code>ntkrnlmp.exe</code> and it's siblings, which differ from each other with enabled code of processor-specific features (e.g. PAE extension support or config for multi-processors),
# '''Ability to support multiple boot loaders''': support will go beyond NTLDR and BOOTMGR, and will include open-source solutions such as GRUB, and will introduce special API to add support for third-party boot loaders, even self-made ones,
# '''Less architecture-specific code''': instead kernel should also provide HAL-different API for separate architectures, in order to expand/fix architecture-specific culprits, which may be brought up during kernel development,
# '''Open Source with GPL license''': this kernel will be available for everyone for free and navigated development, and will be expandable for everyone who wants to master OpenKernel.

=== Components ===
Since OpenKernel is planned to be expandable even beyond OpenXP, these following mini-projects will be planned for beyond:

* Unique replacement for MSVCRT, which includes latest C/C++ specifications and features, and will contain lightweight implementations,
* Enhanced boot loader from 0, like NTLDR but on steroids. Will be shipped as an illustration of boot loader expandable APIs of OpenKernel in action,
* New HAL architecture, which will support both legacy and proprietary HALs, and will allow everyone to write custom HAL for custom hardware.

Development reset

2025-11-16T23:02:52Z

UltimateQuack: The

'''The Development Reset''' was one of the main, crucial events of the OpenXP development, which made the development of the [[codebase]] drop back to level 0.

== Reasons ==
OpenXP was a beginner project, and therefore it recruited developers with almost no experience and of any age. One of the developers hosted the Git server, until they were kicked out in November after deleting everything over allegations of problematic behavior. Source code was mirrored and backed up by the lead developer on his resources, and the mirror was recovered and development continued.

However development reset was already planned to happen, due to the messy and incomplete behavior of new programs, useless laboratory system and lots of inactive developers. It happened in November, 2024, and since then OpenXP's official website, wiki and download center have been released, with many more things coming soon.

[[Category:OpenXP]]
[[Category:History]]

Development reset

2025-11-16T23:02:17Z

UltimateQuack: Formatting, grammar, etc.

'''Development reset''' was one of the main, crucial events of the OpenXP development, which made the development of the [[codebase]] drop back to level 0.

== Reasons ==
OpenXP was a beginner project, and therefore it recruited developers with almost no experience and of any age. One of the developers hosted the Git server, until they were kicked out in November after deleting everything over allegations of problematic behavior. Source code was mirrored and backed up by the lead developer on his resources, and the mirror was recovered and development continued.

However development reset was already planned to happen, due to the messy and incomplete behavior of new programs, useless laboratory system and lots of inactive developers. It happened in November, 2024, and since then OpenXP's official website, wiki and download center have been released, with many more things coming soon.

[[Category:OpenXP]]
[[Category:History]]