User:BF10/Sandbox

Featured article
Click here to see previous featured articles

Screenshots
Thanks to Foxlet for writing this! Screenshots should be "clean" (no extraneous borders outside the video area) and scaled to their true size. If possible, use the Windows screenshot feature ( Print Screen key, Snipping Tool) to take pictures of the desktop, or use the screenshot feature if using a hypervisor/emulator. For "Full Screen" shots, if a cursor is present, it should be isolated in a corner of the background if possible (to show unique features of the cursor). All screenshots should be lossless (JPEG is not acceptable and non-animated GIF is not recommended, unless the respective build is unleaked and the only available screenshots are in JPEG or GIF).

Article Screenshots
Each main article usually requires three components: the Desktop, the About window, and (sometimes) the Logo. In most cases, a build article only needs the first two. "Full Screen" shots (such as for the Desktop and Start Menu) should be 1024x768 in 16-bit color at minimum, unless the subject in question does not support such a video mode (for example, 1024x768 in 256 colors is fine for Windows 3.1 and early Windows 95 builds). Screenshots must not use themes, wallpapers, or other graphics that are not included with the particular operating system or application build, even if they are "Demo" screenshots. The default look and feel should be used for most screenshots; any personalization options can be reasonably demonstrated in a "Demo" screenshot in the Gallery.

Desktop shots should be void of any extra windows, it should represent the state of the system when it is completely idle without any running programs. In the case that the OS shows a tool or special graphic (such as a welcome screen) on boot, that is known as a "First Boot" shot, and is separate from the Desktop shot.

Each article also contains a Gallery, where other associated shots are contained. Additional full screen shots belong here, such as the "Demo" (which shows off particularly unique features of a build). The remaining shots are usually those of programs unique to a build. Those shots should be cropped to the size of the program's window (including transparency and window shadows if such effects are present). Child windows (if any) should be visible in their full area. The screenshots should be free of any watermarks, unless the respective build is unleaked and the only available screenshots are watermarked. Article screenshots should not be annotated in Paint or any other image editor, again the only exception is if there's no other screenshot available and the build is unleaked.

Compatibility

 * Apparently MS Plus! Digital Media Edition installs on Longhorn builds. Tested on build 3713 and build 4015, they both install (images of 4015 running it can be seen in my demo image gallery). MS Plus! XP crashes loading setup though.

Pages to watch

 * Category:Infobox macOS build using compile parameter
 * Category:Infobox Windows build using bios parameter
 * Category:Bad screenshots
 * Apple DOS
 * Featured article

Wanted images
These pages needs images, however they aren't provided yet, most often due to builds requiring real hardware only. Please help this wiki by providing images for these builds or applications:
 * Windows 2000 build 1855.1 (thanks to compgeke on BetaArchive)
 * Windows XP build 3787
 * Windows XP build 3790 (better image at least)
 * Windows 10 Anniversary Update to present
 * Windows Server 2016 Technical Preview 5 (thanks to Caveria)
 * Windows Server version 1709 to present
 * Mac System Software 3.0 to Mac OS 8.7
 * Mac OS 9 betas
 * Mac OS X Server 1.0 - 1.2
 * Mac OS X Developer Preview 1 (thanks to Foxlet)
 * Mac OS X Puma build 5F24
 * Mac OS X Leopard to present (especially Catalina)
 * Hyper-V (thanks to Bubbles)

Processes info
(ported from a test wiki of mines)

Here is a list of critical Windows processes that you will see on Windows NT systems. These processes more than often cannot be killed via Task Manager (unless on Vista or later). If the process's watcher is not terminated, the results listed will occur.

Credit to this blog from Mark Russinovich for the info.


 * : Deals with Windows login sessions, watches  and  . Run when booting; when terminated:
 * XP: BSOD
 * Vista and up: Log off
 * : Session manager. Watches, which if not terminated first, causes BSOD. Run when logging in, when terminated:
 * XP: Does nothing
 * Vista and up: BSOD
 * : Client Server Runtime Subsystem. OS runs on top of this. Run when booting; when terminated, cause BSOD (STOP 0x0F4).
 * : Local Security Authority Subsystem Service. Verifies user logins and allows password changes. Run when logging in; when terminated, reboot computer after 1 minute.
 * : Service Control Manager. Controls all Windows services. Run when booting; when terminated, reboot computer after 1 minute.
 * : Windows Explorer. Holds the main interface. Run when logging in; when terminated, gets rid of Taskbar, all Window Explorer processes, and desktop icons. On Windows 8 and up, also removes background. Usually reopens if it is terminated in any way except by terminating it manually.
 * : Service Host. Holds user's themes. On Windows Vista and up, many instances of this process will run and they will usually relaunch if terminated. Run when booting; when terminated:
 * XP: Revert theme to lowest default
 * Vista and up: Does nothing
 * System: Holds system threads. Cannot be terminated.
 * System Idle Process: Not a real process, tracks time no thread was running. Cannot be terminated.
 * DCOM Server Process Launcher: Helps communicate the system with applications, if terminated:
 * Windows XP-7: Reboot computer after 1 minute
 * Windows 8-10: BSOD