From Wiki96
Revision as of 19:32, 5 August 2022 by Themirrazz (talk | contribs) (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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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 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:

{
  date: "Fri, 05 Aug 2022 18:28:00 GMT",
  message: "Something happened, you'll never guess what!",
  severity: "info",
  source: "behind you lol"
}

date: A stringified version of a Date 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 info, warning, or error. 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.