A thing even more useless than [[API:w96.sys|w96.__sys]]. Or rather, it just contains (a very little) information about the kernel build.

Seems to be present on both V2 and V3. Plus, its the exact same. So we aren't going to add those "V2", "V3" headers.

Changing any of these properties wont do anything:
* poly - If <code>true</code>, then the build contains [[wikipedia:Polyfill (programming)|polyfills]].
[[Category:API]]

API:w96bld

2022-07-02T09:44:26Z

Cab: did the edit too early

A thing even more useless than [[API:w96.sys|w96.__sys]]. Or rather, it just contains (a very little) information about the kernel build.

Seems to be present on both V2 and V3. Plus, its the exact same. So we aren't going to add those "V2", "V3" headers.
==poly==
The only property. If <code>true</code>, then the build contains [[wikipedia:Polyfill (programming)|polyfills]].
[[Category:API]]

API:w96bld

2022-07-02T09:43:19Z

Cab: thanks ctrlz

API:w96bld

2022-06-09T10:31:52Z

Cab: Created page with "A thing even more useless than w96.__sys. Seems to be present on both V2 and V3. Plus, its the exact same. So we aren't going to add those "V2", "V3" headers. ==poly== The only property. Is equal to <code>true</code>."

A thing even more useless than [[API:w96.sys|w96.__sys]].

Seems to be present on both V2 and V3. Plus, its the exact same. So we aren't going to add those "V2", "V3" headers.
==poly==
The only property. Is equal to <code>true</code>.

API:w96.sys

2022-06-09T10:28:45Z

Cab: small page

{{ActualTitle|w96.__sys}}
Quite possibly the most useless thing in the w96 namespace.

Undocumented on the API docs.
==V2==
===DesktopShell===
Literally the exact same as <code>w96.shell.desktop</code>. No idea why is it there.
==V3==
Sadly, it doesn't even EXIST there.

Template:ActualTitle

2022-06-07T13:00:08Z

Cab: crap

''Note: the actual title should be "{{{1}}}", but due to MediaWiki moments, it is not possible to make it look the way it should.''<br>

API:w96.debug

2022-06-07T12:59:43Z

Cab:

{{ActualTitle|w96.__debug}}
The API docs say this:
<blockquote>
<div style="font-size:1.1em;line-height:1.333em;margin-bottom:2em;">Debug export namespace.</div>
This is purely for the Windows 96 developers, there is no need to mess with it.
</blockquote>
and an const named "__empty" is also listed, which is a null value. (it doesn't actually exist though)

But we're (or rather, I'm ([[User:Cab|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 <code>init()</code> method, so as a result, calling it is unnecessary.
====<code>init()</code>====
Asynchronized method. Returns nothing (undefined).

Initializes the IMDE. As said above, it is unnecessary to call it.
====<code>closeAllPopups()</code>====
Synchronized method. Returns nothing (undefined).

Doesn't seem to do anything. Calling toString() reveals this: <code>function w(){document.querySelectorAll(".imde-ui-popup").forEach((e=>e.remove()))}</code>
===Winlogon===
All those methods require a SAM config (basically just a login password set).
====<code>displayLogonUI(e)</code>====
Asynchronized method. Returns nothing (undefined).

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

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

Also, from that screen, you can reboot.
====<code>displayLogonUIAsync()</code>====
Asynchronized (technically synchronized) method. Returns a Boolean.

Same as <code>displayLogonUI</code>, except no parameter is required - the alternative here is the result. <code>false</code> if the SAM config is missing, <code>true</code> after the correct password was entered.
===processes===
This is an interesting one. It's not an object, 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.
==V3==
As of 07.06.2022 (dd.mm.yy).

Won't be listing anything old, as its the same.
===SdgfxTest===
A...class? Looking through the toString reveals that its some <canvas> test.

After constructing it and running <code>main()</code> manually, it shows this window:

[[File:SdgfxTest.png]]

But that seems to be all there is.

Template:ActualTitle

2022-06-07T12:59:16Z

Cab: Created page with "''Note: the actual title should be "{{{1}}}", but due to MediaWiki moments, it is not possible to make it look the way it should.''"

''Note: the actual title should be "{{{1}}}", but due to MediaWiki moments, it is not possible to make it look the way it should.''

API:w96.debug

2022-06-07T12:58:19Z

Cab:

''Note: the actual title should be "w96.__debug", but due to MediaWiki moments, it is not possible to make it look the way it should.''

The API docs say this:
<blockquote>
<div style="font-size:1.1em;line-height:1.333em;margin-bottom:2em;">Debug export namespace.</div>
This is purely for the Windows 96 developers, there is no need to mess with it.
</blockquote>
and an const named "__empty" is also listed, which is a null value. (it doesn't actually exist though)

But we're (or rather, I'm ([[User:Cab|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 <code>init()</code> method, so as a result, calling it is unnecessary.
====<code>init()</code>====
Asynchronized method. Returns nothing (undefined).

Initializes the IMDE. As said above, it is unnecessary to call it.
====<code>closeAllPopups()</code>====
Synchronized method. Returns nothing (undefined).

Doesn't seem to do anything. Calling toString() reveals this: <code>function w(){document.querySelectorAll(".imde-ui-popup").forEach((e=>e.remove()))}</code>
===Winlogon===
All those methods require a SAM config (basically just a login password set).
====<code>displayLogonUI(e)</code>====
Asynchronized method. Returns nothing (undefined).

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

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

Also, from that screen, you can reboot.
====<code>displayLogonUIAsync()</code>====
Asynchronized (technically synchronized) method. Returns a Boolean.

Same as <code>displayLogonUI</code>, except no parameter is required - the alternative here is the result. <code>false</code> if the SAM config is missing, <code>true</code> after the correct password was entered.
===processes===
This is an interesting one. It's not an object, 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.
==V3==
As of 07.06.2022 (dd.mm.yy).

Won't be listing anything old, as its the same.
===SdgfxTest===
A...class? Looking through the toString reveals that its some <canvas> test.

After constructing it and running <code>main()</code> manually, it shows this window:

[[File:SdgfxTest.png]]

But that seems to be all there is.

2022-05-06T10:03:31Z

Cab: add example app

An addon for HiAsm, a russian no-code IDE (for Windows), that lets you make apps for Windows 96 with almost no effort. It is created by [[User:Cab|Cab]].
[[File:29-04components.png|thumb|All the components, as of the April 29th release. In case you dont know, a component is like a lego block of an application created with HiAsm.]]
==What is the point?==
Most people are too lazy to learn how to code, or if they do know how to, they may be lazy to even code in the first place.
<br>But really, the pack is made for fun.
==What are even the benefits from just coding alone?==
*You barely touch the keyboard.
*Code is '''generated''' on demand - a single button press or hotkey!
*HiAsm has a built-in form (window) designer.
*The pack does all the UI bullshit for you.
==Installation guide==
In case you got interested, here's a guide on how to install both HiAsm and the pack.

Skip Part 1 if you already have HiAsm installed.
===Part 1: Installing HiAsm===
Go to [https://hiasm.com/ HiAsm's website]. In the top menu bar, click on "Скачать".

On the next page, click on the first link if you want the official build (less stuff, also right click then click save as), or the second if you want the alternative build (more stuff).

If you get the official build, you should get a .rar, which contains the HiAsm installer. Just go through the instructions, and at the last instruction, enter whatever you want (it will ask you for kinda personal information, however that is not important nor does HiAsm or the installer send it anywhere in anyway).

If you get the alternative build, you should get an executable directly. Just click on it and then "Установить". Wait until the installation finishes. You should get a window with the following checkboxes:
#Add a shortcut to HiAsm on the desktop
#Add a shortcut to HiSVN (the updater) on the desktop (you may wanna untick this)
#Add shortcuts to the start menu
#Add service information to the registry
#Don't change the current HiAsm settings (if its your first time installing the program, it'll be disabled)
#Launch the take-own script for the HiAsm directory (you may wanna untick this as its pretty much useless if you have administrator (or if you're on xp and below))
#Let alone updated KOL for D4 (not sure what this does, so maybe leave it turned off)
Now, HiAsm is installed. Just run it once, then exit it. Create a folder at %USERPROFILE%\Projects (for example C:\Users\User\Projects), if it doesn't exist yet. This will be required from now on.

You may have noticed the weird gibberish text inside, that's an issue related to the fact that you dont have cyrillic fonts installed. Or maybe you do, but then your fonts arent configured to be cyrillic.

Anyway, now onto Part 2.
===Part 2: Installing the pack===
First, [https://cdn.discordapp.com/attachments/931861855427764274/969628402313211954/w96.zip download the pack]. The installation instructions are inside the archive.

In other words:
#Download the pack using the link above
#Extract the archive into (HiAsm installation path)\Elements\w96 (for example <code>C:\Program Files (x86)\HiAsm\Elements\w96</code>)
#Go to the extracted archive, and run the w96.his file '''from there'''. HiAsm should open and immediately close
To make sure the pack did install, run HiAsm again, and click on the file icon on the toolbar on the top. A (new project) window should appear. If you see "w96" there, then that means the pack has been installed!
===Part 3: Getting at least a very basic app to generate===
In the New Project window, click on w96, then Entry point. You should be met with a blank white grid with only one component: the EntryPoint. Click on the icon with a file and zeros and ones to generate a w96 app. (do not click the green triangle its not gonna do anything useful)

Go to the Projects folder you created earlier, and you should see a .js file. That IS the app that was generated! It should look like this:
<syntaxhighlight lang="javascript">
//!wrt
const { Theme } = w96.ui;
class hiProject1 extends w96.WApplication {
constructor() {super();}
async main(argv) {
super.main(argv);
const mainwnd = this.createWindow({
center: true,
controlBoxStyle: "WS_CBX_CLOSE",
resizable: false,
initialWidth: 320,
initialHeight: 240,
title: "Form",
taskbar: true,
body: ''
}, true);
mainwnd.show();
}
}
return await WApplication.execAsync(new hiProject1(), this.boxedEnv.args);
// simply double click to run
// Generated using HiAsm 4.5 build 186
</syntaxhighlight> (assuming you didnt touch anything)
====Part 3.1: Switching between versions====
By default, new projects in the w96 pack generate for v3. This can be changed by going into the properties of the EntryPoint component (after selecting it click on the tab on the right that has a hand pointing to a sheet of paper), in Script -> Version. After clicking on the "text" field, click the little button on the right.
You can select v3, v2, or (you wont fucking believe it) v1.
===Part 4: Finish===
You have successfully installed HiAsm and the pack. You may use the tab on the left (in the IDE when a w96 pack project is open) to insert other components.

Have fun!

API:w96

2022-05-06T09:59:59Z

Cab: lol the link doesnt even work

{{Stub}}
This is the main API namespace for all Windows 96 functions.

A full list of members can be found in the API Reference [https://r3-api-doc.windows96.net/modules/w96.html here].

Mikesoft

2022-05-06T09:59:15Z

Cab:

{{Stub}}
Mikesoft is the fictional company used for the Windows 96 branding. The name was chosen since it closely resembles the name "Microsoft", the original developer of the Windows Operating System.

The name does not mean anything, and is an alternate way to refer to Sys36, especially when talking in the context of Windows 96 "branding". In other words, you should assume all Mikesoft products are actually Sys36 products.