Wiki96 - User contributions [en]

Windows 96 v2

2024-06-28T13:57:33Z

Undefishin:

{{NoSupport}}
[[File:Windows 96 v2 screenshot.png|thumb|Windows 96 version 2.0 default desktop. Note that this is an older build and might not have the latest features.]]
Windows 96 v2 is a version of Windows 96 which is the successor to [[Windows 96 v1]]. Note that this was the version where Windows 96 completely rewritten from scratch. Therefore, it only bears visual similarity to its [[Windows 96 v1|predecessor]]. Windows 96 v2 RTM released on the 5th of February 2021, while SP1 and SP2 released on the 4th of April and the 29th of June respectively.

You can visit this release at [https://rel2.windows96.net https://rel2.windows96.net].

== Why the rewrite? ==
* The code was not well optimized and it was impossible to do so due to the inefficient source code structure.
* It became spaghetti code due to all the OS logic being fit into one file.
* As a result of this, it became near impossible to make the code modular and the effort would be better spent rewriting the OS from scratch.
* Windows 96 v1 had a synchronous design all round, which meant that any async operations would not fit in well and make the spaghetti code situation even worse.
* WebFS's mixed asynchronous model still imposed annoying file limits often reached by regular users, and also generally made the experience feel much slower.
* Cross browser support was not 1:1 due to the lack of CSS normalization/use of browser specific functionality. This meant that Windows 96 would not have a consistent look across browsers.
* A more efficient OS architecture was proposed, where the pros of rewriting the OS eventually outweighed the cons of not rewriting it.
* To allow more than 1 developer to work on the source code without losing their mind.
* And lastly, because of ES6 (ECMAScript v6). Most people and browsers cannot support them.

== Version Highlights ==
* Too many to count (TODO)

== Trivia ==
* The rewrite took around 6 months to be somewhat usable. During this time, the original Windows 96 community died out completely and many fans left without a trace, due to the year-long period.
* The COVID-19 pandemic also made it a pain to stay motivated to keep developing Windows 96.
* The project reached an extent where more than 1 developer was needed.

Windows 96 v1

2024-06-28T13:55:44Z

Undefishin:

{{NoSupport}}
[[File:Screenshot01-v1.png|thumb|A fresh Windows 96 version 1.0 desktop.]]

Windows 96 v1 is the last "classic" version of Windows 96 released on the 15th of August 2019.

It's dubbed as the last classic version due to a total rewrite that occurred between Windows 96 v1 and v2. The rewrite made Windows 96 v1 apps completely incompatible with [[Windows 96 v2|2.0]] due to a different architecture and API set.

It can still be found at https://rel1.windows96.net.

== Version Highlights ==
* A package manager was introduced to allow users to install extra applications not part of the original OS.
* KeyboardMusic was added to allow users to make music using their keyboards.
* Many window manager bugs that existed in version 0.5 were fixed (e.g. active window switching bug).
* The <code>x:/content</code> folder was emptied.
* Window icons were added and the taskbar functionality was improved.
* Many apps had their functionality refined.

== Trivia ==
* This version was the main version of Windows 96 for a very long time.
* Most changes were API updates and app refinements, compared to version 0.5.

Windows 96 v0.5

2024-06-28T13:54:04Z

Undefishin:

{{NoSupport}}
[[File:Windows 96 v0.5 screenshot.png|alt=The default desktop of a fresh Windows 96 v0.5 install.|thumb|The default desktop of a fresh Windows 96 v0.5 install.]]
Windows 96 v0.5 is an old version of Windows 96 released on the 7th of July 2019.

This version introduced major improvements to the OS and the quality of life of the user using it.

This version can still be found at https://rel05.windows96.net.

== Version Highlights ==
* The widespread use of the new Pixel Arial font was applied everywhere.
* A terminal was added for command line based applications.
* A folder containing various silly and weird things was added, which could be accessed at <code>x:/content</code>.
* A bunch of new entertainment apps were added.
* The Windows 96 Wiki was updated to include more in-depth API samples.
* A massive UI lift occurred, which made the OS feel more like Windows 9x compared to previous releases. This includes under-the-hood changes, such as updated UI APIs and CSS level changes, such as the removal of certain fonts and incompatible styles.
* The Windows 96 C/C++ SDK was introduced to allow users to write Windows 96 apps in C++.
* The window manager underwent major improvements.
* Support for JavaScript and HTML document highlighting was added to the default text editor.
* Cross browser support was improved through compatibility stylesheets.
* File uploading was added.
* With the introduction of file uploading, the file system switched to a mixed asynchronous model, which allowed for a theoretical 32 gigabytes of useable space (compared to 8 MB).

== Trivia ==
* This version is considered to be the first version where the Windows 96 design principles were ratified properly.
* A Start menu bug exists where the applications menu will appear after the Start menu is closed.
* There is an XSS bug in Terminal using the <code>title</code> command.

Windows 96 v0.1

2024-06-28T13:51:59Z

Undefishin:

{{NoSupport}}
[[File:Windows 96 v0.1 screenshot.png|alt=The default desktop of a fresh Windows 96 v0.1 installation.|thumb|The default desktop of a fresh Windows 96 v0.1 installation.]]

Windows 96 v0.1 is an old version of Windows 96, which released on the 20th of April 2019.

This is not the first version, but this is the first version which had semi-usable applications, windows, and file system.

This version can still be found at https://rel01.windows96.net.

== Version Highlights ==
* The default fonts used were Pixel Verdana and LWindows, but these were eventually swapped for Pixel Arial in later releases.
* The file system during this time was fully synchronous (utilizing <code>localStorage</code>), which meant that there was a hard browser cap at around 8 megabytes of total data storage.
* The context menus in this version were not yet completed.
* The window manager in this version was extremely primitive and had no way to tell active and inactive windows apart, often resulting in windows not appearing as they should.
* Taskbar tasks could not have an icon representing their appropriate function.
* Terrible font blurring is present all around this version and cross browser support was horrible.
* Half of the Start menu was not functional at all and the Start menu was extremely glitchy.

== Trivia ==
* [[Ctrlz]] (the only developer at the time) had zero idea how to render bitmap fonts properly using CSS and generally had weak CSS abilities during this time.
* Windows 96 was actually not [[Ctrlz]]'s first attempt at making a Web OS. He has attempted it before with unsatisfying results.
* [[Ctrlz]]'s longtime friend Dan conceptualized parts of (and heavily tested) the first releases of Windows 96.
* Most of Windows 96 v0.1 was developed during a school drama performance, where [[Ctrlz]] and Dan were tasked to record the performance, but obviously didn't because they were too busy working on the future of the internet (:wooge:).
* [[Ctrlz]] and Dan still regularly poke fun with Windows 96, often attempting to run the Web OS at random places or random devices for absolutely no reason.

API:BSOD

2024-06-28T13:49:48Z

Undefishin:

Using this simple API, you can render a BSOD (Blue Screen of Death). This simple function works in [[Windows 96 v2]] and newer.

=== Usage ===
Rendering a BSOD is very simple. It uses one function that only requires one argument.

<syntaxhighlight lang="js">
w96.sys.renderBSOD("message of BSOD")
</syntaxhighlight>

Win96 Run Time

2024-06-28T13:49:17Z

Undefishin:

'''Win96 Run Time''', sometimes abbreviated as WRT, is the runtime behind the Windows 96 binaries.

== Features ==
A script executed with the WRT will behave differently than a normal script. Firstly, WRT scripts will be able to use <code>FS</code>, <code>FSUtil</code>, <code>WApplication</code>, <code>StandardWindow</code>, <code>registerApp</code> and <code>deregisterApp</code> without having to use the <code>w96</code> namespace. They will also be able to use the WRT module API where the <code>module</code> object is available for exporting data and <code>include</code> for getting module exported data. Scripts executed with the WRT will also be executed in an asynchronous context, making it possible to use top-level <code>await</code>.

== Usage ==
To execute a script using the WRT, there are 2 options:

# Have this shebang <code>//!wrt</code> be the first line of the script
# Run the <code>wrtrun</code> command with the path to the script in the Terminal.

== History ==
The Windows Runtime was introduced in [[Windows 96 v2]] Service Pack 2.

From the changelog:

<blockquote>"A set of APIs which allow you to easily make apps and include modules, without worrying about the filesystem and stuff like that."

''Windows 96 devs in the rel2sp2 changelog.''</blockquote>

== Shebang ==
A shebang is a marker starting with <code>//</code> (or <code>#!</code> in Unix's case which is where this feature comes from), which can contain a path to any executable. It is always placed at the first line of a file. If any file with a shebang is ran like an executable, the program loader loading the file will interpret the shebang and pass the file being ran to the shebang's specified executable as the first argument.

In this case, a shebang for the WRT is defined like so: <code>//!wrt</code>. The shebang denotes that the file is a WRT binary, and must be the very first line in any WRT application.

=== The binary specification (BSPEC) ===
The binary specification (BSPEC) is a structure which contains metadata for a WRT binary. It always follows the shebang on the same line, where the cumulative line size must not exceed 256 characters.

The BSPEC is a simple JSON object prefixed with <code>$BSPEC:</code> and contains the following fields:

* <code>icn</code> - The name of the icon to use.
* <code>cpr</code> - The copyright holder of the application.
* <code>dsc</code> - A basic description of the application.
* <code>frn</code> - The display name of the application.
* <code>aut</code> - The application author.
* <code>ssy</code> - The subsystem to use for this application. Can either be <code>gui</code> or <code>cli</code>.
* <code>ver</code> - The version of the application.

Below is an example of a binary specification declaration for the File Explorer application.

<syntaxhighlight lang="javascript">
//!wrt $BSPEC:{"icn":"apps/explorer","cpr":"Copyright (C) Windows 96 Team 2021.","dsc":"System File Explorer","frn":"Explorer","ver":1}
</syntaxhighlight>

== Modules ==
A module is a file called by a script in the WRT. They will also run in WRT and have access to WRT features. In addition to this, modules can export data that can be used in other scripts and modules. A module can be called with the <code>include</code> function. It returns a Promise with the module exports.

The <code>include</code> function returns:

* The <code>module.exports</code> of a JavaScript file.
* The parsed content of a JSON file.
* The raw content of any other file type.

=== Global Modules ===
Modules can also be global by declaring a JSON manifest in <code>C:/system/local/lib/modules</code> in the following format: <code>MODULE.json</code> where <code>MODULE</code> is the name of the module when including it. The content of this file should look like this:

<syntaxhighlight lang="json" line="1" start="-2">
{
"libPath": "C:/path/to/module.js"
}
</syntaxhighlight>

Then, the module can be accessed from any file by doing <code>include("MODULE")</code>.

Win96 Run Time

2024-06-28T13:48:06Z

Undefishin: This wiki is very active as you can tell,

'''Win96 Run Time''', sometimes abbreviated as WRT, is the runtime behind the Windows 96 binaries.

== Features ==
A script executed with the WRT will behave differently than a normal script. Firstly, WRT scripts will be able to use <code>FS</code>, <code>FSUtil</code>, <code>WApplication</code>, <code>StandardWindow</code>, <code>registerApp</code> and <code>deregisterApp</code> without having to use the <code>w96</code> namespace. They will also be able to use the WRT module API where the <code>module</code> object is available for exporting data and <code>include</code> for getting module exported data. Scripts executed with the WRT will also be executed in an asynchronous context, making it possible to use top-level <code>await</code>.

== Usage ==
To execute a script using the WRT, there are 2 options:

# Have this shebang <code>//!wrt</code> be the first line of the script
# Run the <code>wrtrun</code> command with the path to the script in the Terminal

== History ==
The Windows Runtime was introduced in [[Windows 96 v2]] Service Pack 2.

From the changelog:
<blockquote>"A set of APIs which allow you to easily make apps and include modules, without worrying about the filesystem and stuff like that."

''Windows 96 devs in the rel2sp2 changelog.''</blockquote>

== Shebang ==
A shebang is a marker starting with <code>//</code> (or <code>#!</code> in Unix's case), which can contain a path to any executable. It is always placed at the first line of a file. If any file with a shebang is ran like an executable, the program loader loading the file will interpret the shebang and pass the file being ran to the shebang's specified executable as the first argument.

In this case, a shebang for the WRT is defined like so: <code>//!wrt</code>. The shebang denotes that the file is a WRT binary, and must be the very first line in any WRT application.

=== The binary specification (BSPEC) ===
The binary specification (BSPEC) is a structure which contains metadata for a WRT binary. It always follows the shebang on the same line, where the cumulative line size must not exceed 256 characters.

The BSPEC is a simple JSON object prefixed with <code>$BSPEC:</code> and contains the following fields:

* <code>icn</code> - The name of the icon to use.
* <code>cpr</code> - The copyright holder of the application.
* <code>dsc</code> - A basic description of the application.
* <code>frn</code> - The display name of the application.
* <code>aut</code> - The application author.
* <code>ssy</code> - The subsystem to use for this application. Can either be <code>gui</code> or <code>cli</code>.
* <code>ver</code> - The version of the application.

Below is an example of a binary specification declaration for the File Explorer application.<syntaxhighlight lang="javascript">
//!wrt $BSPEC:{"icn":"apps/explorer","cpr":"Copyright (C) Windows 96 Team 2021.","dsc":"System File Explorer","frn":"Explorer","ver":1}
</syntaxhighlight>

== Modules ==
A module is a file called by a script in the WRT. They will also run in WRT and have access to WRT features. In addition to this, modules can export data that can be used in other scripts and modules. A module can be called with the <code>include</code> function. It returns a Promise with the module exports.

The <code>include</code> function returns:

* The <code>module.exports</code> of a JavaScript file.
* The parsed content of a JSON file.
* The raw content of any other file type.

=== Global Modules ===
Modules can also be global by declaring a JSON manifest in <code>C:/system/local/lib/modules</code> in the following format: <code>MODULE.json</code> where <code>MODULE</code> is the name of the module when including it. The content of this file should look like this:<syntaxhighlight lang="json" line="1" start="-2">
{
"libPath": "C:/path/to/module.js"
}
</syntaxhighlight>Then, the module can be accessed from any file by doing <code>include("MODULE")</code>.

Virtual Machine

2024-03-08T08:18:17Z

Undefishin:

{{Nov3}}
[[File:Vm.png|thumb|Virtual Machine app in [[Windows 96 v2|version 2.0 SP2]]]]
''For the v3 version of this program, see [[Version Browser]].''

'''Virtual Machine''' (in v3 known as Version Browser) is a program that allows users to launch old versions of [[Windows 96]] and use them as you would back then. The earliest version is [[Windows 96 v0.1|version 0.1]] and the newest is [[Windows 96 v1|version 1.0]].

ShareBoard

2024-02-08T20:03:46Z

Undefishin:

[[File:ShareBoard screenshot.png|thumb|ShareBoard homepage in the dedicated Windows 96 app.]]
ShareBoard was an anonymous board hosted on Windows 96 where users can make text posts of any kind. It also had a comment system and downloading functionality. ShareBoard was released as part of [[Windows 96 v2|Windows 96 v2 SP1]], and got removed in [[Windows 96 v3]]. It was accessible as an app on the Windows 96 desktop.

Image and file uploading functionality is planned, but it's unknown when this will be implemented.

== Common posts ==
Currently (as of May 2021), the ShareBoard userbase creates several types of posts:

* Random posts where nobody knows what the person is talking about.
* Posts mentioning current affairs in the world.
* Posts that either criticise or praise the website.
* Posts with genuine suggestions.
* The occasional wholesome post.
* Posts where users ask how to use Windows 96.
* Posts where the user is confused how they got to this website in the first place.
* The occasional NSFW post/post that breaks the rules. Usually deleted on sight in short time.
* Completely unfunny Among Us memes, usually containing a lot of "sus" phrases.
* Posts that try to abuse/exploit the board. These users usually try the same thing, which is to attempt to XSS the board with HTML in their post.

Of course, a lot of this is generalized, and you can help us improve the general vibe of the board by refraining from making rule-breaking posts, etc.

== Current state ==
The state of ShareBoard is not clear, and it is unknown whether development will continue on the site, since it has been closed for quite some time.

== Trivia ==
* There was an XSS problem which allowed users to put arbitrary HTML code into their posts.
* Even though the list above sounds a bit negative, there is a large chunk of the ShareBoard community who are very wholesome and kind.
* Account registration was planned for more recurring users, but this was not required and the board can be used completely anonymously.

API:w96.debug

2024-02-08T19:56:53Z

Undefishin:

{{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 a const named "__empty" is also listed, which is a null value. (it doesn't actually exist though, but if you do want to make it exist, do <code>w96.__debug.__empty = null;</code>)

But we're (or rather, I'm ([[User:Cab|Cab]])) gonna document what's actually there anyway.
== V2 ==
=== 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, it's an array instead. Contains all the processes in the system.

If we're going by its initial length, the maximum amount of processes in Windows 96 is limited to 8192.

When the limit is exceeded, no applications will run - they will display an error in the console. From that point, closing any open application WILL LOWER THE LIMIT! So the only option is to restart the system.

<code>Object.seal()</code>ing the array will cause a similar situation to the process limit being exceeded, however you won't be able to close any windows.

== V2 SP1+ ==
=== 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 <code>.toString()</code> on it reveals this: <code>function w(){document.querySelectorAll(".imde-ui-popup").forEach((e=>e.remove()))}</code>

== V3 ==
As of June 7, 2022.

Won't be listing anything old, as it's the same.

=== SdgfxTest ===
A...class? Looking through the <code>.toString()</code> output 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.
[[Category:API]]

Windows 96 v2

2024-02-08T19:53:12Z

Undefishin:

{{NoSupport}}
[[File:Windows 96 v2 screenshot.png|thumb|Windows 96 version 2.0 default desktop. Note that this is an older build and might not have the latest features.]]
Windows 96 v2 is a version of Windows 96 and was completely rewritten from scratch. Therefore, it only bears visual similarity to its [[Windows 96 v1|predecessor]]. Windows 96 v2 RTM released on the 5th of February 2021, while SP1 and SP2 released on the 4th of April and the 29th of June respectively.

You can visit this release at [https://rel2.windows96.net https://rel2.windows96.net].

== Why the rewrite? ==
* The code was not well optimized and it was impossible to do so due to the inefficient source code structure.
* It became spaghetti code due to all the OS logic being fit into one file.
* As a result of this, it became near impossible to make the code modular and the effort would be better spent rewriting the OS from scratch.
* Windows 96 v1 had a synchronous design all round, which meant that any async operations would not fit in well and make the spaghetti code situation even worse.
* WebFS's mixed asynchronous model still imposed annoying file limits often reached by regular users, and also generally made the experience feel much slower.
* Cross browser support was not 1:1 due to the lack of CSS normalization/use of browser specific functionality. This meant that Windows 96 would not have a consistent look across browsers.
* A more efficient OS architecture was proposed, where the pros of rewriting the OS eventually outweighed the cons of not rewriting it.
* To allow more than 1 developer to work on the source code without losing their mind.
* And lastly, because of ES6 (ECMAScript v6). Most people and browsers cannot support them.

== Version Highlights ==
* Too many to count (TODO)

== Trivia ==
* The rewrite took around 6 months to be somewhat usable. During this time, the original Windows 96 community died out completely and many fans left without a trace, due to the year-long period.
* The COVID-19 pandemic also made it a pain to stay motivated to keep developing Windows 96.
* The project reached an extent where more than 1 developer was needed.

The Windows 96 HiAsm Pack/Element Support

2024-02-06T13:34:24Z

Undefishin:

As the pack lets you switch the target Windows 96 version for building, the elements in the pack need to be supported for essentially every Windows 96 version.

And because of the above, there's an element named "VersionSwitch", which was made for making some code appear on one version, but not on other.

''TODO: add the background color thing to the middle column''

== Tables ==
MultiThreads and Helpers are excluded since they are CodeGen and IDE only.
{| class="wikitable"
|+ Main
|-
! Name !! Support !! Notes
|-
| Label || All ||
|-
| Edit || All ||
|-
| CheckBox || All ||
|-
| RadioButton || All ||
|-
| Button || All ||
|-
| DropDown || All ||
|-
| ListBox || All ||
|-
| TextArea || Partial || ''doSave and doLoad are not supported on V1''
|-
| ProgressBar || All ||
|-
| IFrame || All ||
|-
| Image || All ||
|-
| Canvas || All ||
|}

{| class="wikitable"
|+ Controls
|-
! Name !! Support !! Notes
|-
| Timeout || All || This really has to be remade
|-
| Wait || V2+ only || Uses API that's only present in the next version. This really has to be remade
|-
| Interval || All || This really has to be remade
|-
| MessageBox || All ||
|-
| MsgBoxSimple || Partial || ''doIdleProgress is V2+ only''
|-
| Alert || Partial? || Is meant to use the system's custom alert method, which doesnt exist in V1
|-
| ContextMenu || V2+ only ||
|-
| WApplication || V2+ only ||
|-
| NotifyIcon || All || In older versions of the pack, there was no support for V1
|}

{| class="wikitable"
|+ Graphics
|-
! Name !! Support !! Notes
|-
| Cnv_Point || All ||
|-
| Cnv_Line || All ||
|-
| Cnv_Rectangle || All ||
|-
| Cnv_Ellipse || All ||
|}

{| class="wikitable"
|+ System
|-
! (Subcategory/)Name !! Support !! Notes
|-
| Exec || Partial || doExec is not available in V1
|-
| Reboot || All || In V1, simply reloads the page
|-
| WRT || V2+ only ||
|-
| OSRelease || V2+ only ||
|-
| Console || All || Fun Fact: Nander once wrote a Console element that only had a Log method
|-
| Components/SystemConfig || V3 only ||
|-
| Components/SystemFlags || V2+ only ||
|-
| Components/WindowSystem || Partial || ''doCloseAllWindows, doDeactivateAllWindows and StartZIndex are not available in V1''
|-
| Miscellaneous/[[API:w96.debug|__debug]] || V2+ only ||
|}

{| class="wikitable"
|+ Network
|-
! Name !! Support !! Notes
|-
| WebSocket || All ||
|-
| SocketIO || All ||
|-
| SocketIOShared || All ||
|}

{| class="wikitable"
|+ Strings
|-
! (Subcategory/)Name !! Support !! Notes
|-
| StrList || V2+ only || ''doSave and doLoad are not supported on V1''
|-
| Delete || All ||
|-
| Copy || All ||
|-
| Insert || All ||
|-
| Length || All ||
|-
| Convert || All ||
|-
| Concatenation/StrCat || All ||
|-
| Concatenation/StrCatDelim || All ||
|-
| Concatenation/FormatStr || All ||
|-
| Separation/Split || All ||
|-
| Search/Position || All ||
|-
| Substitution/StrCase || All ||
|-
| Substitution/Replace || All ||
|-
| Substitution/Trim || All ||
|}

{| class="wikitable"
|+ File System
|-
! (Subcategory/)Name !! Support !! Notes
|-
| DirTools || V2+ only ||
|-
| FileTools || V2+ only ||
|-
| UniversalTools || V2+ only ||
|-
| DirForEach || V2+ only ||
|-
| FileStat || V2+ only ||
|-
| MkShortcut || All ||
|-
| Ini || V3 only ||
|-
| Dialogs/ODialog || V2+ only ||
|-
| Dialogs/SDialog || V2+ only ||
|-
| Custom File Systems/LocalStorageFileSystem || V2+ only ||
|-
| Custom File Systems/IndexedFileSystem || V2+ only ||
|-
| Custom File Systems/RamFileSystem || V2+ only ||
|}

{| class="wikitable"
|+ Logic
|-
! Name !! Support !! Notes
|-
| Operation || All ||
|-
| Rand || V2+ only || Will most likely have a polyfill in the future
|-
| If || All ||
|-
| Between || All ||
|-
| For || All ||
|-
| While || All ||
|-
| Boolean || All ||
|-
| IsNaN || All ||
|}

{| class="wikitable"
|+ Arrays
|-
! Name !! Support !! Notes
|-
| ArrayRW || All ||
|-
| ArrayEnum || All ||
|}

{| class="wikitable"
|+ Tools
|-
! (Subcategory/)Name !! Support !! Notes
|-
| DoData || All ||
|-
| EventFromData || All ||
|-
| Variable || All || This really has to be remade
|-
| IndexToChanel || All || The grammar mistake is intentional
|-
| VisualStrings || All ||
|-
| InlineCode || All ||
|-
| TryCatch || All ||
|-
| Function || All ||
|-
| Comment || All ||
|-
| VersionSwitch || All ||
|-
| Util || V2+ only ||
|-
| FakeLocalStorage || All ||
|-
| Object || All ||
|-
| Types/TypeOf || All ||
|-
| Types/Converter || All ||
|}

{| class="wikitable"
|+ Exposed Objects
|-
! Name !! Support !! Notes
|-
| StandardWindow || All ||
|-
| WindowParams || V2+ only ||
|-
| MouseEvent || All ||
|}

The Windows 96 HiAsm Pack/QNA

2024-02-06T13:33:03Z

Undefishin:

{{Stub|help add questions}}

== Questions and Answers ==
=== How do I use HiAsm? ===
There's plenty of tutorials, guides, etc on other websites, including YouTube.

Be aware that most of them are in Russian, due to the nature of the program's country of origin.

=== The elements are limiting what I can do, how do I exceed those limits? ===
Three options:
* If you can write JavaScript code, you can use the InlineCode element. It's located in the Tools category.
* Ask the developer(s) to make an element for what you're trying to do. Or try to make one yourself.
* Use elements that are available to do the job. Note that this may not work for some things.

=== Can I make apps for Windows 93? ===
No. Maybe in the future it will be possible as a separate pack.

=== Why are some elements unavailable in earlier versions? ===
Some things are just unavailable in them. Built-in polyfills might be added later.

=== I want a child window, how do I make one? ===
You can experiment with InlineCode, but that's probably it; MultiElement(Ex/Poly)s are too complex to implement at the moment. They're the base of ChildWindows.

== Problems and Solutions ==
=== The pack is not showing! ===
Make sure you:
* Didn't change the IDE's language to English. There's a weird bug that hides custom packs when the language is set to English.
* Extracted the pack correctly. Make sure you extracted it as <code>(HiAsm installation directory)\Elements\w96</code> (for example, <code>C:\Program Files (x86)\HiAsm\Elements\w96</code>). If you extracted it as a subfolder (like <code>(HiAsm installation directory)\Elements\w96\w96</code>), it won't work.
* Ran the w96.his file. If it shows a "unknown file" window, drag it into the HiAsm icon, or if HiAsm is open, just drag it into the IDE.
* Didn't delete the Elements.db file. It contains all elements.

The Windows 96 HiAsm Pack

2024-02-06T13:31:40Z

Undefishin: didn't think I would make constructive edits here, huh?

[[File:04-08components.png|thumb|All the element, as of the August 4th release. An element (or component) is like a lego block of an application created with HiAsm.]]

An addon for HiAsm, a niche no-code IDE from Russia (for Windows only), that lets you make apps for Windows 96 with almost no effort. It is created by [[User:Cab|Cab]].

== Sub-pages ==
* [[The Windows 96 HiAsm Pack/QNA|Questions & Answers]]
* [[The Windows 96 HiAsm Pack/Element Support|Element Support]]

== What's 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.

But really, the pack is made for fun.

== What are even the benefits from just coding alone? ==
* The code is '''generated'''.
* HiAsm has a built-in form (window) designer.
* The pack does all the UI work for you.
* Easy prototyping.
* Code generation for [[Windows 96 v3|v3]], [[Windows 96 v2|v2]] and even [[Windows 96 v1|v1]] if you want.

== 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 "Скачать" (Download, in Russian).

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 "Установить" (Install). 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 it's 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 <code>%USERPROFILE%\Projects</code> (for example <code>C:\Users\(USERNAME)\Projects</code>), 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/750475455051726848/1017783075079463052/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 <code>(HiAsm installation path)\Elements\w96</code> (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 element: 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 didn't touch anything)

==== Part 3.1: Switching between versions ====
By default, new projects in the Windows 96 Pack generate for V3. This can be changed by simply going into the properties of the EntryPoint element (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 won't believe it) v1.

=== Part 4: Fin ===
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 elements.

Have fun!

== Example applications, by the author ==
* Trash Cleaner ([https://cdn.discordapp.com/attachments/750475455051726848/1002200102301089843/TrashCleaner.js V3], [https://cdn.discordapp.com/attachments/750475455051726848/1002200186212331570/TrashCleaner.js V2])
* Create a Drive ([https://cdn.discordapp.com/attachments/750475455051726848/976520092445712454/CreateFS.js V3], [https://cdn.discordapp.com/attachments/750475455051726848/976520345693597706/CreateFS.js V2])
* Guess a Number ([https://cdn.discordapp.com/attachments/750475455051726848/971746605273342113/GuessNumber.js V3], [https://cdn.discordapp.com/attachments/750475455051726848/971746664719220746/GuessNumber.js V2])

Windows 96 v3

2024-02-06T13:27:54Z

Undefishin:

Windows 96 v3 is the current version of [[Windows 96]] that is the successor to [[Windows 96 v2|v2]]. It added a lot of features, most notably a much more faithful Windows 9x style UI. It had some cut content which you can see [[Windows 96 v3 Cut Content|here]].

== Version Highlights ==
* The 9x style of the OS has been vastly improved.
* The apps are now in the [[Root Filesystem|filesystem]] instead of in the Windows96 kernel.
* A new terminal, compatible with XTerm.
* System Config Manager (SCM) that works similarly to the Windows Registry.
* A new shell, and a highly advanced theming engine.
* A new file explorer that looks more like the Windows 98 one.
* BoxedWine (bWINE) is now built in into Windows 96.
* More apps, including: WMBox, JSLinux, 3D Pinball Space Cadet (the IMGUI port), and PDF Reader.
* An Out Of Box Experience that can triggered by pressing ALT+O on Windows 96 boot.
* [[Disk Encryption]].
* The new and improved WEX (Windows96 C/C++ API) (as opposed to the old SDK), that allows you to write Windows 96 apps in C/C++.
* A new wiki which you are on right now.
* Task Manager, allowing you to easily kill misbehaving apps.
* [[Media Player]], replaces the old Video Player.
* [[Version Browser]], replaces the old [[Virtual Machine]].
* [[InternetE]], replaces the old [[Internet Exploder]].
* The filesystem is now fully asynchronous.
* P3FS
* The YouAreAnIdiot app now bounces across the screen, like the real YouAreAnIdiot.

== Trivia ==
* This version took a very long time to release, due to the extended development time.

Windows 96 v2

2024-02-06T13:23:15Z

Undefishin:

{{NoSupport}}
[[File:Windows 96 v2 screenshot.png|thumb|Windows 96 version 2.0 default desktop. Note that this is an older build and might not have the latest features.]]
Windows 96 v2 is a version of Windows 96 and was completely rewritten from scratch. Therefore, it only bears visual similarity to its [[Windows 96 v1|predecessor]]. Windows 96 v2 RTM released on the 5th of February 2021, while SP1 and SP2 released on the 4th of April and the 29th of June respectively.

You can visit this release at [https://rel2.windows96.net https://rel2.windows96.net].

== Why the rewrite? ==
* The code was not well optimized and it was impossible to do so due to the inefficient source code structure.
* It became spaghetti code due to all the OS logic being fitted into one file.
* As a result of this, it became near impossible to make the code modular and the effort would be better spent rewriting the OS from scratch.
* Windows 96 v1 had a synchronous design all round, which meant that any async operations would not fit in well and make the spaghetti code situation even worse.
* WebFS's mixed asynchronous model still imposed annoying file limits often reached by regular users, and also generally made the experience feel much slower.
* Cross browser support was not 1:1 due to the lack of CSS normalization/use of browser specific functionality. This meant that Windows 96 would not have a consistent look across browsers.
* A more efficient OS architecture was proposed, where the pros of rewriting the OS eventually outweighed the cons of not rewriting it.
* To allow more than 1 developer to work on the source code without losing their mind.
*And because the ES6 (ECMAScript v6). Most people and browsers cannot support them.

== Version Highlights ==
* Too many to count (TODO)

== Trivia ==
* The rewrite took around 6 months to be somewhat usable. During this time, the original Windows 96 community died out completely and many fans left without a trace.
* The COVID-19 pandemic also made it a pain to stay motivated to keep developing Windows 96.
* The project reached an extent where more than 1 developer was needed.

Windows 96 v1

2024-02-06T13:18:24Z

Undefishin:

{{NoSupport}}
[[File:Screenshot01-v1.png|thumb|A fresh Windows 96 version 1.0 desktop.]]

Windows 96 v1 is the last "classic" version of Windows 96 released on the 15th of August 2019.

It's dubbed as the last classic version due to a total rewrite that occurred between Windows 96 v1 and v2. The rewrite made Windows 96 v1 apps completely incompatible with [[Windows 96 v2|2.0]] due to a different architecture and API set.

It can still be found at https://rel1.windows96.net.

== Version Highlights ==
* A package manager was introduced to allow users to install additional apps from what was already provided.
* KeyboardMusic was added to allow users to make music using their keyboards.
* Many window manager bugs that existed in version 0.5 were fixed (e.g. active window switching bug).
* The <code>x:/content</code> folder was emptied.
* Window icons were added and the taskbar functionality was improved.
* Many apps had their functionality refined.

== Trivia ==
* This version was the main version of Windows 96 for a very long time.
* Most changes were API updates and app refinements compared to version 0.5.

User talk:Undefishin

2024-02-06T13:13:13Z

Undefishin:

'''Welcome to ''Wiki96''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:Z8|Z8]] ([[User talk:Z8|talk]]) 14:10, 6 February 2024 (CET)
: I certainly will. Thank you for letting me on here, it is very well appreciated! --[[User:Undefishin|Undefishin]] ([[User talk:Undefishin|talk]]) 14:13, 6 February 2024 (CET)