8c9039bbd4
CORE-20279 PRELIMINARY REMARK: The described bug and code workaround only applies for x86 32-bit builds. ---- While the Winlogon notification handlers[^1] actually use a `STDCALL` calling convention, which can be trivially verified by debugging the official Windows <= 2003 winlogon.exe and its notification extensions, there exist 3rd-party Winlogon notification DLLs, like the `Ati2evxx.dll` one from AMD/ATI XP video drivers, that use a `CDECL` calling convention, or an invalid number (zero) of parameters. I think the reason why this happens is as follows. The official documentation[^1] indicates that the handlers have the following prototype: ```c void Event_Handler_Function_Name( _In_ PWLX_NOTIFICATION_INFO pInfo ); ``` The documentation (and possibly the internal header Windows is using for Winlogon) is sloppy, because it doesn't tell whether the convention is `STDCALL` or `CDECL`. When compiling routines with such a signature, the compiler will employ whatever default convention it is set to use. Windows code is typically compiled with `STDCALL` convention as the default (see e.g. how the Windows Development Kit is set up), thus, such a function signature would default to `STDCALL`. Observation (with debugger) shows that it is what Windows' winlogon.exe is indeed expecting. However, 3rd-party code using a different development environment, could set the compiler to use `CDECL` as the default calling convention. As a result, the function signature from above would use `CDECL` instead. The difference between the `STDCALL` and `CDECL` conventions is how the function parameters are passed on the stack and how the stack is cleaned at the end (`STDCALL`: the function unwinds the stack; `CDECL`: the caller does it). A calling convention mismatch would therefore corrupt the stack, and this is exactly what happens with the `Ati2evxx.dll` from the AMD/ATI drivers, see CORE-20279. The ReactOS Winlogon crashes from the `_RTC_Failure()` handler just after the 3rd-party handler returns, since we compile our code with runtime checks enabled. Windows' winlogon.exe doesn't apparently crash, because neither in Release nor in Checked/Debug mode did they compile winlogon.exe with RTC enabled. However, its stack would become more corrupt with time. In order to alleviate this in ReactOS' winlogon.exe, I decided to use a "generic" workaround, manually calling the handler with inline ASM (which is OK since the problem and solution is x86-specific only). It does something similar to what the RTC support does: it checks the stack pointer after the call and restores it if needed. An informative message is then emitted in the debugger telling which DLL is buggy and needs to be fixed. [^1]: https://learn.microsoft.com/en-us/windows/win32/secauthn/event-handler-function-prototype
Quick Links
Website • Official chat • Wiki • Forum • Community Discord • JIRA Bug Tracker • ReactOS Git mirror • Testman
What is ReactOS?
ReactOS™ is an Open Source effort to develop a quality operating system that is compatible with applications and drivers written for the Microsoft® Windows™ NT family of operating systems (NT4, 2000, XP, 2003, Vista, 7).
The ReactOS project, although currently focused on Windows Server 2003 compatibility, is always keeping an eye toward compatibility with Windows Vista and future Windows NT releases.
The code of ReactOS is licensed under GNU GPL 2.0.
Product quality warning
ReactOS is currently an Alpha quality operating system. This means that ReactOS is under heavy development and you have to be ready to encounter some problems. Different things may not work well and it can corrupt the data present on your hard disk. It is HIGHLY recommended to test ReactOS on a virtual machine or on a computer with no sensitive or critical data!
Building
To build the system it is strongly advised to use the ReactOS Build Environment (RosBE). Up-to-date versions for Windows and for Unix/GNU-Linux are available from our download page at: "Build Environment".
Alternatively one can use Microsoft Visual C++ (MSVC) version 2019+. Building with MSVC is covered here: "Visual Studio or Microsoft Visual C++".
See "Building ReactOS" article for more details.
Binaries
To build ReactOS you must run the configure script in the directory you want to have your build files. Choose configure.cmd or configure.sh depending on your system. Then run ninja <modulename> to build a module you want or just ninja to build all modules.
Bootable images
To build a bootable CD image run ninja bootcd from the build directory. This will create a CD image with a filename bootcd.iso.
You can always download fresh binary builds of bootable images from the "Daily builds" page.
Installing
By default, ReactOS currently can only be installed on a machine that has a FAT16 or FAT32 partition as the active (bootable) partition. The partition on which ReactOS is to be installed (which may or may not be the bootable partition) must also be formatted as FAT16 or FAT32. ReactOS Setup can format the partitions if needed.
Starting with 0.4.10, ReactOS can be installed using the BtrFS file system. But consider this as an experimental feature and thus regressions not triggered on FAT setup may be observed.
To install ReactOS from the bootable CD distribution, extract the archive contents. Then burn the CD image, boot from it, and follow the instructions.
See "Installing ReactOS" Wiki page or INSTALL for more details.
Testing
If you discover a bug in ReactOS search on JIRA first - it might be reported already. If not report the bug providing logs and as much information as possible.
See "File Bugs" for a guide.
NOTE: The bug tracker is not for discussions. Please use our official chat or our forum.
Contributing 
We are always looking for developers! Check how to contribute if you are willing to participate.
Legal notice: If you have seen proprietary Microsoft Windows source code (including but not limited to the leaked Windows NT 3.5, NT 4, 2000 source code and the Windows Research Kernel), your contribution won't be accepted because of potential copyright violation.
Try out cloud-based ReactOS development using Gitpod and Docker:
You can also support ReactOS by donating! We rely on our backers to maintain our servers and accelerate development by hiring full-time devs.
More information
ReactOS is a Free and Open Source operating system based on the Windows architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system.
It is not another wrapper built on Linux, like WINE. It does not attempt or plan to compete with WINE; in fact, the user-mode part of ReactOS is almost entirely WINE-based and our two teams have cooperated closely in the past.
ReactOS is also not "yet another OS". It does not attempt to be a third player like any other alternative OS out there. People are not meant to uninstall Linux and use ReactOS instead; ReactOS is a replacement for Windows users who want a Windows replacement that behaves just like Windows.
More information is available at: reactos.org.
Also see the media/doc subdirectory for some sparse notes.
Who is responsible
Active devs are listed as members of GitHub organization. See also the CREDITS file for others.
Code mirrors
The main development is done on GitHub. We have an alternative mirror in case GitHub is down.
There is also an obsolete SVN archive repository that is kept for historical purposes.