🪟 My favorite pieces from the Windows XP source code — Part 2

Part 2 of the collection. The first 10 pieces can be found here. 😊

The list in order:
11. \base\fs\rdr2\rdbss\ifskit.mrx\smbmrx\sys\ea.c
12. \XPSP1\NT\shell\applets\taskmgr\main.cpp
13. \XPSP1\NT\shell\ext\keyremap\mapcf.c
14. \XPSP1\NT\shell\iecontrols\framewrk\stdenum.cpp
15. \XPSP1\NT\shell\lib\util.cpp
16. \multimedia\dshow\filters.ks\tests\tstshell\tsseltst.c 😂
17. \base\mvdm\wow16\kernel31\tdb.inc
18. \inetsrv\iis\svcs\ftp\server\userdb.cxx
19. \base\mvdm\wow16\mmsystem\mmtask\mmtask.asm
20. \base\mvdm\dos\v86\doskrnl\dos\misc.asm

🪟 Hidden Windows OOBE features

Pressing the Windows key 5 consecutive times in the Windows 11 OOBE brings up the «provisioning menu».

Provisioning is slightly different to customizing an image and then deploying it. It's intended for a different purpose: you have to supply a provisioning package (a .ppkg file) with configuration settings every time you install Windows, whereas customizing the image prior to deployment locks the changes in and predetermines the configuration from the very beginning of the install.

An illustrative use case of provisioning is when one owns a medium-sized industry with a few hundred employees split into subdivisions, and each subdivision has its own Windows configuration. Creating multiple images makes no sense here — it's overkill for such a task. It's much easier to use a provisioning scenario.