From Wiki96
Revision as of 16:46, 5 June 2022 by Cab (talk | contribs) (gonna document contents of it in v3)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
StubEmoji.jpg
Where is the content?

This page is a stub. You can help Wiki96 by extending it.
User note: No note given

The API docs say this:

Debug export namespace.

This is purely for the Windows 96 developers, there is no need to mess with it.

and an const named "__empty" is also listed, which is a null value.

But we're (or rather, I (Cab) gonna document what's actually there anyway.

V2

As of the latest service pack.

ImmersiveDesktopEnvironment

The Immersive Desktop Environment (or the IMDE). It gets initialized on startup, even though it has an exposed init() method, so as a result, calling it is unnecessary.

init()

Asynchronized method. Returns nothing (undefined).

Initializes the IMDE. As said above, it is unnecessary to call it.

closeAllPopups()

Synchronized method. Returns nothing (undefined).

Doesn't seems to do anything. Calling toString() reveals this: function w(){document.querySelectorAll(".imde-ui-popup").forEach((e=>e.remove()))}

Winlogon

All those methods require a SAM config (basically just a login password set).

displayLogonUI(e)

Asynchronized method. Returns nothing (undefined).

Shows a login screen, and requires you to enter your password. After the correct password is entered, the e function is called with one parameter, that's equal to true.

If no SAM config is found, it shows an error message, and calls the e function with one parameter, that's equal to false.

Also, from that screen, you can reboot.

displayLogonUIAsync()

Asynchronized (technically synchronized) method. Returns a Boolean.

Same as displayLogonUI, except no parameter is required - the alternative here is the result. false if the SAM config is missing, true after the correct password was entered.

processes

This is an interesting one. It's not an object, like the previous objects, its an array instead.

If we're going by its initial length, the maximum amount of processes in Windows 96 is limited to 8192. Currently it is untested whether or not Windows 96 malfunctions when this amount is exceeded.