API:w96.sys.log - Revision history

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

2023-05-16T16:35:45Z

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

← Older revision		Revision as of 18:35, 16 May 2023
Line 1:		Line 1:
	~~__NOTOC__NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~		The system log is a feature in [[Windows 96 v3]] that allows you to see important information from the system. It is stored in the RAM of Windows 96, and can be edited through a special API.
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~
			=== w96.sys.log.events ===

			An array of objects that are formatted in what I'm calling the SLogEvent format.

			=== w96.sys.log.limits ===
			An object with one property, <code>eventCount</code> that sets limits for the event log.

			=== w96.sys.log.limits.eventCount ===
			The amount of events that can be stored in system log.
			When initiated, it is set to 1000.

			=== SLogEvent Format ===
			This format is an object representing an event.
			An example object looks like this:
			<syntaxhighlight lang="json">
			{
			date: "Fri, 05 Aug 2022 18:28:00 GMT",
			message: "Something happened, you'll never guess what!",
			severity: "info",
			source: "behind you lol"
			}
			</syntaxhighlight>

			date: A stringified version of a <code>Date</code> version, but can also be milliseconds since UNIX epoch.
			message: The message of the event.
			severity: What icon and level label to show. Can either be <code>info</code>, <code>warning</code>, or <code>error</code>.
			source: What part of the system is sending the message. For example, when ever a disk is mounted to the filesystem, the log's source is labeled "FS Service".

			=== w96.sys.events.silenced ===
			True if the "Disable system event log" flag is enabled, basically like the do-not-track of System Log.
			However, non-built-in services can still use the log freely, and may completely ignore this.

94.233.241.205: SEXX

2023-05-16T06:57:50Z

SEXX

← Older revision		Revision as of 08:57, 16 May 2023
Line 1:		Line 1:
	~~The system log is a feature in [[Windows 96 v3]] that allows you to see important information from the system. It is stored in the RAM of Windows 96, and can be edited through a special API.~~		__NOTOC__NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
			NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
	~~=== w96.sys.log.events ===~~

	~~An array of objects that are formatted in what I'm calling the SLogEvent format.~~

	~~=== w96.sys.log.limits ===~~
	~~An object with one property, <code>eventCount</code> that sets limits for the event log.~~

	~~=== w96.sys.log.limits.eventCount ===~~
	~~The amount of events that can be stored in system log.~~
	~~When initiated, it is set to 1000.~~

	~~=== SLogEvent Format ===~~
	~~This format is an object representing an event.~~
	~~An example object looks like this:~~
	~~<syntaxhighlight lang="json">~~
	{
	~~date: "Fri, 05 Aug 2022 18:28:00 GMT",~~
	~~message: "Something happened, you'll never guess what!",~~
	~~severity: "info",~~
	~~source: "behind you lol"~~
	}
	~~</syntaxhighlight>~~

	~~date: A stringified version of a <code>Date</code> version, but can also be milliseconds since UNIX epoch.~~
	~~message: The message of the event.~~
	~~severity: What icon and level label to show. Can either be <code>info</code>, <code>warning</code>, or <code>error</code>.~~
	~~source: What part of the system is sending the message. For example, when ever a disk is mounted to the filesystem, the log's source is labeled "FS Service".~~

	~~=== w96.sys.events.silenced ===~~
	~~True if the "Disable system event log" flag is enabled, basically like the do-not-track of System Log.~~
	~~However, non-built-in services can still use the log freely, and may completely ignore this.~~

Themirrazz: Created page with "The system log is a feature in Windows 96 v3 that allows you to see important information from the system. It is stored in the RAM of Windows 96, and can be edited through a special API. === w96.sys.log.events === An array of objects that are formatted in what I'm calling the SLogEvent format. === w96.sys.log.limits === An object with one property, `eventCount` that sets limits for the event log. === w96.sys.log.limits.eventCount === The amount of even..."

2022-08-05T18:32:17Z

Created page with "The system log is a feature in Windows 96 v3 that allows you to see important information from the system. It is stored in the RAM of Windows 96, and can be edited through a special API. === w96.sys.log.events === An array of objects that are formatted in what I'm calling the SLogEvent format. === w96.sys.log.limits === An object with one property, <code>eventCount</code> that sets limits for the event log. === w96.sys.log.limits.eventCount === The amount of even..."

New page

The system log is a feature in [[Windows 96 v3]] that allows you to see important information from the system. It is stored in the RAM of Windows 96, and can be edited through a special API.

=== w96.sys.log.events ===

An array of objects that are formatted in what I'm calling the SLogEvent format.

=== w96.sys.log.limits ===
An object with one property, <code>eventCount</code> that sets limits for the event log.

=== w96.sys.log.limits.eventCount ===
The amount of events that can be stored in system log.
When initiated, it is set to 1000.

=== SLogEvent Format ===
This format is an object representing an event.
An example object looks like this:
<syntaxhighlight lang="json">
{
date: "Fri, 05 Aug 2022 18:28:00 GMT",
message: "Something happened, you'll never guess what!",
severity: "info",
source: "behind you lol"
}
</syntaxhighlight>

date: A stringified version of a <code>Date</code> version, but can also be milliseconds since UNIX epoch.
message: The message of the event.
severity: What icon and level label to show. Can either be <code>info</code>, <code>warning</code>, or <code>error</code>.
source: What part of the system is sending the message. For example, when ever a disk is mounted to the filesystem, the log's source is labeled "FS Service".

=== w96.sys.events.silenced ===
True if the "Disable system event log" flag is enabled, basically like the do-not-track of System Log.
However, non-built-in services can still use the log freely, and may completely ignore this.