User:BF10/Sandbox

Featured article
Click here to see previous featured articles

Bad screenshots

 * Category:Bad screenshots

Deletion

 * Category:Possibly meeting criteria for quick deletion
 * Category:Active proposed deletions
 * Category:Expired proposed deletions
 * Category:Discussed for deletion
 * Articles for deletion

BetaWiki

 * Featured article

Template errors

 * Category:Pages using duplicate arguments in template calls

Mac OS X Leopard on QEMU
If you get "Install Failed" at end of setup, do not close QEMU or click Restart. Head to Utilities to select a startup disk and choose the hard drive.

If you can't at end of setup, restart QEMU with installation media and select Startup Disk at the start.

Basilisk II

 * Mac OS 7
 * Mac OS 7.5.5C3: this disk is not a Macintosh disk, do you want to initialize it
 * A good amount of 7.6 betas don't work as they request for a disk even though it's already inserted

SheepShaver

 * None of the Copland builds boot since they require specific models, debugger, and partition format that is not supported on SheepShaver so far
 * Mac OS 9
 * Mac OS 9.0b5: this disk is unreadable, do you want to initialize it
 * Mac OS 9.0b7c4: this disk is unreadable, do you want to initialize it

QEMU

 * Mac OS X Tiger
 * Mac OS X Tiger build 8A323: no valid state has been set by load or init-program
 * Mac OS X Tiger build 8A369: no valid state has been set by load or init-program
 * Mac OS X Tiger build 8A425: no valid state has been set by load or init-program
 * Mac OS X Leopard
 * Mac OS X Leopard build 9A241: no valid state has been set by load or init-program
 * Mac OS X Leopard build 9A466: no valid state has been set by load or init-program
 * Mac OS X Leopard build 9A559: no valid state has been set by load or init-program
 * Mac OS X Snow Leopard
 * Mac OS X Snow Leopard build 10A96: kernel panics on boot due to incompatible model
 * Mac OS X Snow Leopard build 10A190: hangs booting

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