System Configuration Manager - Revision history

Utf: Reverted edits by 94.233.241.205 (talk) to last revision by Kelbaz

2023-05-16T16:38:37Z

Reverted edits by 94.233.241.205 (talk) to last revision by Kelbaz

@@ Line 1: / Line 1: @@
-__NOTOC__NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
+System Configuration Manager (SCM) is a utility used to edit the current system configuration. It is very much like the Registry Editor seen in Microsoft Windows and serves a similar purpose. Since invalid configurations can cause a multitude of problems, only users with reasonable knowledge of the OS internals should be using it.
-NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
-NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
+Most changes that SCM makes are live, but it is recommended to reboot after a configuration change, depending on what configuration you changed and for which application.
-NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
-NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
+== Structure ==
-NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
+[[File:Scm Screenshot.png|thumb|SCM showing the configuration root.]]
-NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
+SCM stores configurations in so-called roots, which are simply separate (named) stores of configuration objects (the <config root> in SCM shows the currently available stores). Stores are in-memory and have to be synced manually to the disk each time a change is made (write-back). Users cannot add new stores through SCM, but it is possible by adding a new index in <code>c:/system/config/SCM/index</code> (although this is not recommended).
-NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD

94.233.241.205: SEXX

2023-05-16T06:57:53Z

SEXX

@@ Line 1: / Line 1: @@
-System Configuration Manager (SCM) is a utility used to edit the current system configuration. It is very much like the Registry Editor seen in Microsoft Windows and serves a similar purpose. Since invalid configurations can cause a multitude of problems, only users with reasonable knowledge of the OS internals should be using it.
+__NOTOC__NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
+NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
-Most changes that SCM makes are live, but it is recommended to reboot after a configuration change, depending on what configuration you changed and for which application.
+NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
+NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
-== Structure ==
+NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
-[[File:Scm Screenshot.png|thumb|SCM showing the configuration root.]]
+NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
-SCM stores configurations in so-called roots, which are simply separate (named) stores of configuration objects (the <config root> in SCM shows the currently available stores). Stores are in-memory and have to be synced manually to the disk each time a change is made (write-back). Users cannot add new stores through SCM, but it is possible by adding a new index in <code>c:/system/config/SCM/index</code> (although this is not recommended).
+NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
+NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD

Kelbaz at 13:17, 11 March 2023

2023-03-11T13:17:56Z

← Older revision		Revision as of 15:17, 11 March 2023
Line 24:		Line 24:
	\|Explorer configuration.		\|Explorer configuration.
	\|}		\|}
			[[Category:Apps]]

Ctrl: punctuation

2022-04-09T03:35:34Z

punctuation

← Older revision		Revision as of 05:35, 9 April 2022
Line 5:		Line 5:
	== Structure ==		== Structure ==
	[[File:Scm Screenshot.png\|thumb\|SCM showing the configuration root.]]		[[File:Scm Screenshot.png\|thumb\|SCM showing the configuration root.]]
	SCM stores configurations in so-called roots, which are simply separate (named) stores of configuration objects (the <config root> in SCM shows the currently available stores). Stores are in-memory and have to be synced manually to the disk each time a change is made (write-back). Users cannot add new stores through SCM, but it is possible by adding a new index in <code>c:/system/config/SCM/index</code>, although this is not recommended.		SCM stores configurations in so-called roots, which are simply separate (named) stores of configuration objects (the <config root> in SCM shows the currently available stores). Stores are in-memory and have to be synced manually to the disk each time a change is made (write-back). Users cannot add new stores through SCM, but it is possible by adding a new index in <code>c:/system/config/SCM/index</code> (although this is not recommended).

	A special type of stores called "Pseudo-stores" also exist, but they are mainly used for representation of other configuration objects. Pseudo-stores are not synced to the disk, and need to be defined programmatically. By default, <code>$Pseudo</code> is a representation of the current execution context of Windows 96, and is defined on system startup.		A special type of stores called "Pseudo-stores" also exist, but they are mainly used for representation of other configuration objects. Pseudo-stores are not synced to the disk, and need to be defined programmatically. By default, <code>$Pseudo</code> is a representation of the current execution context of Windows 96 and is defined on system startup.

	== Common Paths ==		== Common Paths ==

Ctrl: add SCM page

2022-02-21T14:50:03Z

add SCM page

New page

System Configuration Manager (SCM) is a utility used to edit the current system configuration. It is very much like the Registry Editor seen in Microsoft Windows and serves a similar purpose. Since invalid configurations can cause a multitude of problems, only users with reasonable knowledge of the OS internals should be using it.

Most changes that SCM makes are live, but it is recommended to reboot after a configuration change, depending on what configuration you changed and for which application.

== Structure ==
[[File:Scm Screenshot.png|thumb|SCM showing the configuration root.]]
SCM stores configurations in so-called roots, which are simply separate (named) stores of configuration objects (the <config root> in SCM shows the currently available stores). Stores are in-memory and have to be synced manually to the disk each time a change is made (write-back). Users cannot add new stores through SCM, but it is possible by adding a new index in <code>c:/system/config/SCM/index</code>, although this is not recommended.

A special type of stores called "Pseudo-stores" also exist, but they are mainly used for representation of other configuration objects. Pseudo-stores are not synced to the disk, and need to be defined programmatically. By default, <code>$Pseudo</code> is a representation of the current execution context of Windows 96, and is defined on system startup.

== Common Paths ==
Below are some common configuration paths for certain programs/system components:
{| class="wikitable"
!Path
!Description
|-
|System/WndMan
|Window manager settings. You can manipulate these visually with WMSM (WM Settings Manager).
|-
|System/Session/Shell
|Current shell configuration. Edit this with care, providing an invalid binary will cause the system to stop booting.
|-
|Software/Explorer
|Explorer configuration.
|}