User:BF10/Sandbox

Deletion Request: Various unsourced articles
Articles in question:
 * Windows XP build 2239
 * Windows XP build 2422
 * Windows XP build 2455
 * Windows XP build 2464
 * Windows XP build 2493
 * Windows Server 2003 build 2250.1
 * Windows Longhorn build 4002 (Lab04 N)
 * Windows Longhorn build 4003
 * Windows Longhorn build 4028
 * Windows Vista build 5004
 * Windows Vista build 5439
 * Windows Vista build 5441

All these pages have absolutely no sources or images and haven't been updated in a long time. Alongside, while some builds such as Windows XP build 2464 and 2493 might have client versions and vice versa, there is currently no source to prove that. If we were to keep those pages, then we might as well make Windows Longhorn build 4066 too. Even though BuildFeed listed these buildtags, they often had no source (the 2239 buildtag only had info on the Server version), and even builds 4002 (Lab04 N), 4003, 5439, and 5441 was not listed on BuildFeed. I'm not sure if all have to be deleted, so if you choose remove but want to keep some of the pages, be sure to list what pages should be kept. Voting keep will keep all the pages.

Windows Article Example
Windows Nashville build 3670 is the general availability build of Windows 2.0. It includes Internet Explorer 9, Office 2019, improved Fax features, and a new Task Manager. Alongside, Watercolor, Luna, Royale, Zune, Embedded, Plex, Slate, Jade, and Windows Aero are available themes.

Enabling Desktop Composition Engine
This is a guide on how to enable the Desktop Composition Engine in most builds.

Video Drivers
DCE requires a graphics card that supports Pixel Shader 2.0 and DirectX 9. In VMware, SVGA drivers from VMware version 6.0-7.1 can be capable of enabling DCE, although it is recommended to use older VMware versions to install DCE, as compatibility mode might not always work.

macOS Article Example
Paul Thurrott's home for Windows 7 screenshots

Sourceless Pages (for use in deletion requests)

 * Windows XP build 2239
 * Windows XP build 2422
 * Windows XP build 2455
 * Windows XP build 2464
 * Windows XP build 2493
 * Windows Longhorn build 4002 (Lab04 N)
 * Windows Longhorn build 4003
 * Windows Longhorn build 4028
 * Windows Vista build 5004
 * Windows Vista build 5439
 * Windows Vista build 5441

5111.1

 * Most ISOs out there (including the copy I currently have) doesn't requests a product key and nullifies the time bomb (so it works like as I like to call it "2000 SP7"). However, the ISOs on more reliable resources like BetaArchive's FTP uses a product key (which also allows 98SE product keys) and a varying timebomb.
 * Internet Explorer 6 is a big no for this build. It messes up a lot of features including the logon screen.
 * You can shut off Neptune; it only hibernates by default.

BSoD Hunt

 * Find all BSoDs or crashes:
 * Windows 1.x series: run aux.
 * Windows 2.x series: Dunno, it's somehow resistant to aux and con. Some application from Toastytech seems to crash the computer on me once though.
 * Windows 3.x and 9x (except ME): run con/con. System freezes on 3.x.
 * Windows ME: Dunno, if it is running stable, it is hard to crash. Still uses same BSOD as Windows 9x though.
 * Windows NT and 2000: dir C:\WINNT\System32, press F7 and enter many times while its running.
 * Windows Whistler/XP: Kill winlogon.exe in Process Explorer. No, you cannot crash without Process Explorer.
 * Windows Longhorn and up: Kill csrss.exe in Task Manager (doesn't work on Longhorn 4029 and later if you don't see all processes)

Compatibility

 * Apparently MS Plus! Digital Media Edition installs on Longhorn builds. Tested on build 3713 and build 4015, they both install. MS Plus! XP crashes loading setup though.
 * PCem doesn't run Windows XP build 2433. It usually crashes during TXT setup with hardware storm hangs.
 * My god, Windows Server 2008 build 4028. This build doesn't like many emulators. I tried PCem, and it hangs loading WinPE. I tried QEMU, and it BSOD when loading hardware stage of setup.

Trivia
Did you know...
 * All the Windows ME beta builds share the same product key?