From ReactOS Wiki
Jump to: navigation, search

Arwinss is an alternative implementation of the core Win32 subsystem components. Technical information about implementation details is available at this page: Arwinss technical.


Checkout the arwinss branch (svn://, and compile using following command:

makex comctl32 user32 gdi32 win32k winent win32csr freetype kernel32 explorer winlogon

This will build all needed modules of a new subsystem, which you need to copy over to the installed ReactOS version (see Transfer files from the host OS to the virtual drive). A modified KERNEL32.DLL is needed only for a compatible global atoms support.

If you want to build winex11 module, you need to firstly copy lib/3rdparty/libX11/libX11.a file from your working copy to the obj-i386/lib/3rdparty/libX11 directory (creating it if it does not exist). This will fix the winex11.drv linking issues, and you can just type

makex winex11

to build this optional module.


Arwinss uses parts of the Wine architecture and parts of Windows NT architecture in appropriate places and in a good way.The overall call flow / architecture of Arwinss looks like this:


It consists of the following modules, one of them being optional (winex11.drv):

  • dll/3rdparty/freetype - implements usermode font rendering (FreeType library, with small ReactOS glue), used by GDI32.DLL
  • dll/win32/user32 - implements USER API
  • dll/win32/gdi32 - implements GDI API
  • dll/win32/winent.drv - implements native graphics and user drivers
  • dll/win32/winex11.drv - implements X11 X-windows graphics and user drivers
  • subsystems/win32/win32k - implements kernel mode counter part of the native graphics driver, a Simple Window Manager (SWM) and a kernel mode USER server.
  • subsystems/win32/csrss/win32csr - implements needed parts of the CSR subsystem along with handling user input


Most of the hacking happens in WINENT.DRV and WIN32K.SYS, with very rare fixes to the user32/gdi32 (mainly, because it's a tested Wine's code with only minor changes).

Convention for marking changes. C++ code comments (//) mean that the place has some special mark up for debugging. A typical use is for a

// FIXME: Something

Potential Benefits

These bugs would be fixed if Arwinss was ready (just a short list): {{#bugzilla:|id=933,1175,1239,1776,2769,2788,3101,3429,3500,3542,4443,4612,5069,5305|columns=id,resolution,summary}}

As one can see from these bug titles it mainly boils down to drastically improved user32 and gdi32 support.


See ReactOS Bugzilla (component "Arwinss")

  1. Enable commented out places in the font output code (ET_OPAQUE, etc)
  2. Implement RegisterShellHookWindow (Taskbar doesn't show any proccess)
  3. Implement hotkeys support
  4. Implement clipboard support


You can get the lastest ARWINSS ISO in the first message of this thread or here.

Donations for Maintenance Costs

Please Help Us to Pay for Hosting and Domain Registration for

Yearly Costs:

  1. Hosting - $60.00
  2. Domain Registration - $7.99

Please help us to deliver to you our latest builds and ensure fast downloads and archives of every Arwinss Release

Click To Donate ->