Wiki96 - User contributions [en]

Package Manager

2024-01-25T22:05:45Z

Kelbaz: Changed Onofficiel's repository url

[[File:Package Manager.jpg|thumb|The Package Manager program.]]
The package manager is Windows 96's primary method of distribution for programs. The term "package" refers to a complex set of folders and files, which when coupled with a JSON file and structured correctly, can be decoded by the package manager program and unpacked into the Windows 96 filesystem.

==Functioning ==
Packages are hosted on a webserver, where the root URL of the package folder is then set as a package repository in the package manager. Packages can be hosted on any static website host (i.e. Github Pages), and comprise of a set of 16x16 and 32x32 pixel icon files, as well as a "content@1.0" directories/zips and a JSON file which sets the folders and icons as variables.[[File:Pkgman-structure.png|The package manager file structure.|thumb]]
==Package structure==
During the creation of a package repository, the package manager must be able to decode the structure of the package to be able to successfully unpack any files or folders inside. The file sctructure can be found on the right.

==Community==
Packages are created by the community to share their work to other users. Packages may contain applications, programs, tools, themes, or wallpapers. Here are some repositories created by the community:
{| class="wikitable"
!URL
!Author
!Note
|-
|[https://packages.windows96.net/community https://packages.windows96.net/r3-main]
|Windows 96
|The official main repository.
|-
|https://packages.windows96.net/community
|Windows 96 Contributors
|The official community repository. Packages are picked using a high standard. (Down)
|-
|https://nandertga.ddns.net/w96-packages
|NanderTGA
|
|-
|https://sgeo.github.io/win96-repos/apps
| rowspan="2" |Sgeo
|
|-
|https://sgeo.github.io/win96-repos/malware
|Malware repository - use at your own risk
|-
|https://jameisepic.github.io/thinkjame/public/main
|JameIsEpic
|
|-
|[https://onofficiel.github.io/w96/v3 https://onofficiel.github.io/w96]
|Onofficiel ([[User:Kelbaz|Kelbaz]])
|
|-
|https://plopilpy.github.io/w96
|[[User:Plopilpy|Plopilpy]]
|
|-
|https://pack96.awesomecrater.repl.co/main
| rowspan="3" |[[User:Themirrazz|themirrazz]]
|Only for [[Windows 96 v2]] (Down)
|-
|https://themirrazz.vercel.app
|
|-
|https://themirrazzjp.vercel.app
|Japanese Repo (Beta) / 日本語リポジトリー (ベータ版)
|-
|https://w96.boomlings.xyz/repo/v3
| rowspan="2" |[[User:Nolanwhy|nolanwhy]]
|
|-
|https://w96.boomlings.xyz/repo/v3/malware
|Malware repository - use at your own risk
|-
|https://egg.l5.ca/w96
|egg.l5.ca
|Contains wallpaper packs, themes and games
|-
|https://raw.githubusercontent.com/Driftini/w96pkgs/main
|Driftini
|
|}

API:w96.FS

2023-12-22T18:53:09Z

Kelbaz: Filled every single methods

=== <code>class FS</code> ===
This namespace refers to the file system API of Windows 96. <code>w96.FS</code> allows manipulation of file system entries by, for example, renaming, deleting or copying them. It is also possible to create, read and write files and directories.

== Structure ==

=== <code>mount(fso: IFileSystem): Promise<void></code> ===
Mounts a file system using the specified object ("driver").

=== <code>umount(prefix: String): Promise<void></code> ===
Unmounts a file system instance.

=== <code>mounts(): IFileSystem[]</code> ===
Gets all mounted file systems.

=== <code>list(): String[]</code> ===
Gets all mounted file system prefixes.

=== <code>nextLetter(): String</code> ===
Get the next available drive letter.

=== <code>toBlob(path: String): Promise<Blob></code> ===
Creates a blob from a specified path.

=== <code>get(prefix: String): IFileSystem</code> ===
Retuns a file system by its prefix.

=== <code>toURL(path: String): Promise<String></code> ===
Creates a URL from the specified file path.

=== <code>isFile(path: String): Promise<Boolean></code> ===
Returns <code>true</code> if the entry is a file.

=== <code>isEmpty(path: String): Promise<Boolean></code> ===
Returns <code>true</code> if the file is empty.

=== <code>mkdir(path: String): Promise<Boolean></code> ===
Creates a directory at the specified path.

=== <code>rmdir(path: String): Promise<Boolean></code> ===
Deletes a directory at the specified path.

=== <code>touch(path: String): Promise<Boolean></code> ===
Creates a file at the specified path.

=== <code>rm(path: String): Promise<Boolean></code> ===
Deletes a file at the specified path.

=== <code>readdir(path: String, scan_mode: Boolean): String[]</code> ===

* If scan_mode is set to true, then the filetype is included with the path

Returns a list of entities contained in the specified path.

=== <code>cpdir(src: String, dest: String): Promise<Boolean></code> ===
Copies a directory to a new destination.

=== <code>cpfile(src: String, dest: String): Promise<Boolean></code> ===
Copies a file to a new destination.

=== <code>mvfile(src: String, dest: String): Promise<Boolean></code> ===
Moves a file to a new destination.

=== <code>mvdir(src: String, dest: String): Promise<Boolean></code> ===
Moves a directory to a new destination.

=== <code>exists(path: String): Boolean</code> ===
Checks if an entity exists.

=== <code>readstr(path: String): Promise<String></code> ===
Reads the specified file as a string.

=== <code>readbin(path: String): Promise<Uint8Array></code> ===
Reads the specified file as binary.

=== <code>filetype(path: String): 0 | 1 | -1</code> ===
Returns the file type of a node. This can be a binary or text file.

=== <code>writestr(path: String, data: String): Promise<Boolean></code> ===
Truncates and writes a UTF-8 encoded string to the specified file.

=== <code>writebin(path: String, data: Uint8Array | Number[]): Promise<Boolean></code> ===
Truncates and writes data to the specified file.

=== <code>walk(path: String): String[]</code> ===
Walks through the contents of a directory.

=== <code>stat(path: String): FSStatResult</code> ===
Retrieves information about a file system entry.

=== <code>rename(path: String, newName: String): Promise<Boolean></code> ===
Renames a file or folder.

=== <code>readBinChunk(path: String, start?: Number, end?: Number): Promise<Uint8Array></code> ===
Returns a slice of a file binary data from a path, a start and an end index.

=== <code>readStrChunk(path: String, start?: Number, end?: Number): Promise<String></code> ===
Returns a slice of a file as a string from a path, a start and an end index.

=== <code>cache(path: String, params: { type: "binary" | "string" | "blob", overwrite: Boolean }): Promise<void></code> ===
Caches a file from a given path depending on parameters like the overwriting or the file type.

=== <code>uncache(path: String): void</code> ===
Uncaches the file at a specified path.

=== <code>getFromCache(path: String): Uint8Array | String | Blob | undefined</code> ===
Gives the the data from the cached file at a specified path. If the file wasn't cached, it returns <code>undefined</code>.

=== <code>hash(path: String, algorithm: "default" | "md5" | "sha256" | "sha512"): Promise<String></code> ===
Creates a hash from a given path and algorithm.

=== <code>assert(path: String): Promise<void></code> ===
Checks if a file exists at a specific path. If not, it will throw an <code>Error</code>.
[[Category:API]]

Required Knowledge for Development

2023-11-29T22:25:48Z

Kelbaz: First sentence :/

[[Category:Prerequisites]]
As Windows 96 is based on web technologies, basic knowledge of JavaScript and HTML is required.

Startup Arguments

2023-11-29T22:21:05Z

Kelbaz: Added the "faster" argument

It is possible to start Windows 96 with additional startup arguments to enable/disable specific functionality. They can be specified in the URL as query parameters.

Note: This is different from system flags and takes higher precedence in the startup process, since it foregoes any storage to persist its values.

Example: <code>https://windows96.net/?live=1</code>

=== List of startup arguments ===
{| class="wikitable"
!Argument
!Value
!Description
|-
|live
|1/0
|Whether to boot Windows 96 in "Live Mode" (a mode which does not install Windows 96 locally, but on a temporary RAM disk instead). This mode also skips setup prompts and gives you the default experience straight away.
|-
|debug
|1/0
|Whether to enable debug mode. This flag enables a console.
|-
|rootfs
|<string>
|Specifies the path/URL of the root filesystem zip to use.
|-
|faster
|1/0
|If set to 1, the boot time will be faster.
|}

Package Manager

2023-10-27T22:59:38Z

Kelbaz: nolan not happy because caps

[[File:Package Manager.jpg|thumb|The Package Manager program.]]
The package manager is Windows 96's primary method of distribution for programs. The term "package" refers to a complex set of folders and files, which when coupled with a JSON file and structured correctly, can be decoded by the package manager program and unpacked into the Windows 96 filesystem.

==Functioning ==
Packages are hosted on a webserver, where the root URL of the package folder is then set as a package repository in the package manager. Packages can be hosted on any static website host (i.e. Github Pages), and comprise of a set of 16x16 and 32x32 pixel icon files, as well as a "content@1.0" directories/zips and a JSON file which sets the folders and icons as variables.[[File:Pkgman-structure.png|The package manager file structure.|thumb]]
==Package structure==
During the creation of a package repository, the package manager must be able to decode the structure of the package to be able to successfully unpack any files or folders inside. The file sctructure can be found on the right.

==Community==
Packages are created by the community to share their work to other users. Packages may contain applications, programs, tools, themes, or wallpapers. Here are some repositories created by the community:
{| class="wikitable"
!URL
!Author
!Note
|-
|https://packages.windows96.net/community
|Windows 96 Contributors
|The official community repository. Packages are picked using a high standard. (Down)
|-
|https://nandertga.ddns.net/w96-packages
|NanderTGA
|
|-
|https://sgeo.github.io/win96-repos/apps
| rowspan="2" |Sgeo
|
|-
|https://sgeo.github.io/win96-repos/malware
|Malware repository - use at your own risk
|-
|https://jameisepic.github.io/thinkjame/public/main
|JameIsEpic
|
|-
|https://onofficiel.github.io/w96/v2
| rowspan="2" |Onofficiel ([[User:Kelbaz|Kelbaz]])
|Only for [[Windows 96 v2]]
|-
|https://onofficiel.github.io/w96/v3
|
|-
|https://plopilpy.github.io/w96
|[[User:Plopilpy|Plopilpy]]
|
|-
|https://themirrazz.repl.co
|[[User:Themirrazz|TheMirrazz]]
|
|-
|https://nolanwhy.github.io/w96-repo/v3
|nolanwhy
|
|}

Package Manager

2023-10-27T22:57:17Z

Kelbaz: added repo

[[File:Package Manager.jpg|thumb|The Package Manager program.]]
The package manager is Windows 96's primary method of distribution for programs. The term "package" refers to a complex set of folders and files, which when coupled with a JSON file and structured correctly, can be decoded by the package manager program and unpacked into the Windows 96 filesystem.

==Functioning ==
Packages are hosted on a webserver, where the root URL of the package folder is then set as a package repository in the package manager. Packages can be hosted on any static website host (i.e. Github Pages), and comprise of a set of 16x16 and 32x32 pixel icon files, as well as a "content@1.0" directories/zips and a JSON file which sets the folders and icons as variables.[[File:Pkgman-structure.png|The package manager file structure.|thumb]]
==Package structure==
During the creation of a package repository, the package manager must be able to decode the structure of the package to be able to successfully unpack any files or folders inside. The file sctructure can be found on the right.

==Community==
Packages are created by the community to share their work to other users. Packages may contain applications, programs, tools, themes, or wallpapers. Here are some repositories created by the community:
{| class="wikitable"
!URL
!Author
!Note
|-
|https://packages.windows96.net/community
|Windows 96 Contributors
|The official community repository. Packages are picked using a high standard. (Down)
|-
|https://nandertga.ddns.net/w96-packages
|NanderTGA
|
|-
|https://sgeo.github.io/win96-repos/apps
| rowspan="2" |Sgeo
|
|-
|https://sgeo.github.io/win96-repos/malware
|Malware repository - use at your own risk
|-
|https://jameisepic.github.io/thinkjame/public/main
|JameIsEpic
|
|-
|https://onofficiel.github.io/w96/v2
| rowspan="2" |Onofficiel ([[User:Kelbaz|Kelbaz]])
|Only for [[Windows 96 v2]]
|-
|https://onofficiel.github.io/w96/v3
|
|-
|https://plopilpy.github.io/w96
|[[User:Plopilpy|Plopilpy]]
|
|-
|https://themirrazz.repl.co
|[[User:Themirrazz|TheMirrazz]]
|
|-
|https://nolanwhy.github.io/w96-repo/v3
|[[User:Nolanwhy|NolanWhy]]
|
|}

API:w96.FS

2023-10-26T15:54:40Z

Kelbaz: Dare you scan mode!

=== <code>class FS</code> ===
This namespace refers to the file system API of Windows 96. <code>w96.FS</code> allows manipulation of file system entries by, for example, renaming, deleting or copying them. It is also possible to create, read and write files and directories.

== Structure ==

=== <code>mount(fso: IFileSystem): Promise<void></code> ===
Mounts a file system using the specified object ("driver").

=== <code>umount(prefix: String): Promise<void></code> ===
Unmounts a file system instance.

=== <code>mounts(): IFileSystem[]</code> ===
Gets all mounted file systems.

=== <code>list(): String[]</code> ===
Gets all mounted file system prefixes.

=== <code>nextLetter(): String</code> ===
Get the next available drive letter.

=== <code>toBlob(path: String): Promise<Blob></code> ===
Creates a blob from a specified path.

=== <code>get(prefix: String): IFileSystem</code> ===
Retuns a file system by its prefix.

=== <code>toURL(path: String): Promise<String></code> ===
Creates a URL from the specified file path.

=== <code>isFile(path: String): Promise<Boolean></code> ===
Returns <code>true</code> if the entry is a file.

=== <code>isEmpty(path: String): Promise<Boolean></code> ===
Returns <code>true</code> if the file is empty.

=== <code>mkdir(path: String): Promise<Boolean></code> ===
Creates a directory at the specified path.

=== <code>rmdir(path: String): Promise<Boolean></code> ===
Deletes a directory at the specified path.

=== <code>touch(path: String): Promise<Boolean></code> ===
Creates a file at the specified path.

=== <code>rm(path: String): Promise<Boolean></code> ===
Deletes a file at the specified path.

=== <code>readdir(path: String, scan_mode: Boolean): String[]</code> ===

* If scan_mode is set to true, then the filetype is included with the path

Returns a list of entities contained in the specified path.

=== <code>cpdir(src: String, dest: String): Promise<Boolean></code> ===
Copies a directory to a new destination.

=== <code>cpfile(src: String, dest: String): Promise<Boolean></code> ===
Copies a file to a new destination.

=== <code>mvfile(src: String, dest: String): Promise<Boolean></code> ===
Moves a file to a new destination.

=== <code>mvdir(src: String, dest: String): Promise<Boolean></code> ===
Moves a directory to a new destination.

=== <code>exists(path: String): Boolean</code> ===
Checks if an entity exists.

=== <code>readstr(path: String): Promise<String></code> ===
Reads the specified file as a string.

=== <code>readbin(path: String): Promise<Uint8Array></code> ===
Reads the specified file as binary.

=== <code>filetype(path: String): 0 | 1 | -1</code> ===
Returns the file type of a node. This can be a binary or text file.

=== <code>writestr(path: String, data: String): Promise<Boolean></code> ===
Truncates and writes a UTF-8 encoded string to the specified file.

=== <code>writebin(path: String, data: Uint8Array | Number[]): Promise<Boolean></code> ===
Truncates and writes data to the specified file.

=== <code>walk(path: String): String[]</code> ===
Walks through the contents of a directory.

=== <code>stat(path: String): FSStatResult</code> ===
Retrieves information about a file system entry.

=== <code>rename(path: String, newName: String): Promise<Boolean></code> ===
Renames a file or folder.

=== <code>readBinChunk()</code> ===

=== <code>readStrChunk()</code> ===

=== <code>cache()</code> ===

=== <code>uncache()</code> ===

=== <code>getFromCache()</code> ===

=== <code>hash(path: String, algorithm: "default" | "md5" | "sha256" | "sha512"): Promise<String></code> ===
Create a hash from a given path and algorithm.

=== <code>assert()</code> ===
[[Category:API]]

Package Manager

2023-10-15T17:09:41Z

Kelbaz: Updated the table

[[File:Package Manager.jpg|thumb|The Package Manager program.]]
The package manager is Windows 96's primary method of distribution for programs. The term "package" refers to a complex set of folders and files, which when coupled with a JSON file and structured correctly, can be decoded by the package manager program and unpacked into the Windows 96 filesystem.

==Functioning ==
Packages are hosted on a webserver, where the root URL of the package folder is then set as a package repository in the package manager. Packages can be hosted on any static website host (i.e. Github Pages), and comprise of a set of 16x16 and 32x32 pixel icon files, as well as a "content@1.0" directories/zips and a JSON file which sets the folders and icons as variables.[[File:Pkgman-structure.png|The package manager file structure.|thumb]]
==Package structure==
During the creation of a package repository, the package manager must be able to decode the structure of the package to be able to successfully unpack any files or folders inside. The file sctructure can be found on the right.

==Community==
Packages are created by the community to share their work to other users. Packages may contain applications, programs, tools, themes, or wallpapers. Here are some repositories created by the community:
{| class="wikitable"
!URL
!Author
!Note
|-
|https://packages.windows96.net/community
|Windows 96 Contributors
|The official community repository. Packages are picked using a high standard. (Down)
|-
|https://nandertga.ddns.net/w96-packages
|NanderTGA
|
|-
|https://sgeo.github.io/win96-repos/apps
| rowspan="2" |Sgeo
|
|-
|https://sgeo.github.io/win96-repos/malware
|Malware repository - use at your own risk
|-
|https://jameisepic.github.io/thinkjame/public/main
|JameIsEpic
|
|-
|https://onofficiel.github.io/w96/v2
| rowspan="2" |Onofficiel ([[User:Kelbaz|Kelbaz]])
|Only for [[Windows 96 v2]]
|-
|https://onofficiel.github.io/w96/v3
|
|-
|https://plopilpy.github.io/w96
|[[User:Plopilpy|Plopilpy]]
|
|-
|https://themirrazz.repl.co
|[[User:Themirrazz|TheMirrazz]]
|
|}

Windows 96 Development Toolchain

2023-10-12T17:20:52Z

Kelbaz: Adding Directives part

[[File:WDT.png|thumb|The Windows 96 Development Toolchain running in Windows96.]]
The Windows 96 Development Toolchain (WDT) is a build system developed by the Windows 96 Team in 2023. It addresses the need for an efficient build system for system apps within the Windows 96 environment. This toolchain was created to overcome limitations of the old builder, providing enhanced performance, project management, and portability. WDT follows the principle of "eating your own dog food" where the system is used to build itself.

WDT runs on Windows, MacOS, Linux and Windows 96 itself.

== Features ==
WDT offers a range of features designed to streamline the app development process within the Windows 96 ecosystem:

* '''Project Management:''' Create, manage, and compile app projects seamlessly.
* '''Preprocessing:''' Perform operations like handling includes and defining directives.
* '''Portability:''' Build projects on various systems without strict location or OS constraints.
* '''Concurrency:''' Leverage CPU concurrency to accelerate project builds.
* '''Task Management:''' Manage the build process using WMakefiles.
* '''Modernization:''' Replaces the outdated previous build system with a more efficient and user-friendly solution.

== Commands ==
Here are all the WDT commands:
{| class="wikitable"
|+
!Command Name
! colspan="2" |Argument(s)
!Description
|-
|<code>build</code>
|Project Path
|''Output Path''
|Builds a project
|-
|<code>version</code>
| colspan="2" |
|Gets the current toolchain version
|-
|<code>preproc</code>
|In Path
|Out Path
|Runs a file through the source preprocessor
|-
|<code>help</code>
| colspan="2" |''Command''
|Gets command help (or general CLI help without the command parameter)
|-
|<code>make</code>
| colspan="2" |''Path''
|Runs a makefile (WMakefile) in the current directory or the specified path
|-
|<code>minify</code>
|Input
|Output
|Minifies JavaScript code
|-
|<code>project init</code>
|Project Path
|''<code>--template</code> Template Name''
|Inits a project at the path (from a template if specified)
|-
|<code>project import</code>
| colspan="2" |
|''Not implemented yet''
|}

== Preprocessor Directives & Macros ==
Directives are preprocessor statements used to guide the compilation process by providing instructions to the preprocessor. In the context of WDT, a directive is defined using two dollar signs, followed by the directive name.

Here are the currently supported macros in WDT:
{| class="wikitable"
|+
!Definition
!Description
|-
|<code>$$Include("./file.js")</code>
|Include a file
|-
|<code>$$IncludeOnce("./file.js")</code>
|Include a file enable checks to ensure its only included once
|-
|<code>$$Define("Macro")</code>
| rowspan="2" |Define a macro
|-
|<code>$$Define("MacroName", "OptionalValue")</code>
|-
|<code>$$Undef("Name")</code>
|undefine a macro
|}
It's important to note that preprocessing directives must be terminated by a newline for proper parsing and execution during the compilation process. <code>$[("MacroName")]</code> allows to get a macro value.

WDT

2023-10-12T16:08:11Z

Kelbaz: Redirected page to Windows 96 Development Toolchain

#REDIRECT [[Windows 96 Development Toolchain]]

Windows 96 Development Toolchain

2023-08-25T22:07:27Z

Kelbaz: Added image

File:WDT.png

2023-08-25T22:06:23Z

Kelbaz:

The Windows 96 Development Toolchain running in Windows 96

Windows 96 Development Toolchain

2023-08-25T21:50:31Z

Kelbaz: Creating the page

The Windows 96 Development Toolchain (WDT) is a build system developed by the Windows 96 Team in 2023. It addresses the need for an efficient build system for system apps within the Windows 96 environment. This toolchain was created to overcome limitations of the old builder, providing enhanced performance, project management, and portability. WDT follows the principle of "eating your own dog food" where the system is used to build itself.

WDT runs on Windows, MacOS, Linux and Windows 96 itself.

== Features ==
WDT offers a range of features designed to streamline the app development process within the Windows 96 ecosystem:

* '''Project Management:''' Create, manage, and compile app projects seamlessly.
* '''Preprocessing:''' Perform operations like handling includes and defining directives.
* '''Portability:''' Build projects on various systems without strict location or OS constraints.
* '''Concurrency:''' Leverage CPU concurrency to accelerate project builds.
* '''Task Management:''' Manage the build process using WMakefiles.
* '''Modernization:''' Replaces the outdated previous build system with a more efficient and user-friendly solution.

== Commands ==
Here are all the WDT commands:
{| class="wikitable"
|+
!Command Name
! colspan="2" |Argument(s)
!Description
|-
|<code>build</code>
|Project Path
|''Output Path''
|Builds a project
|-
|<code>version</code>
| colspan="2" |
|Gets the current toolchain version
|-
|<code>preproc</code>
|In Path
|Out Path
|Runs a file through the source preprocessor
|-
|<code>help</code>
| colspan="2" |''Command''
|Gets command help (or general CLI help without the command parameter)
|-
|<code>make</code>
| colspan="2" |''Path''
|Runs a makefile (WMakefile) in the current directory or the specified path
|-
|<code>minify</code>
|Input
|Output
|Minifies JavaScript code
|-
|<code>project init</code>
|Project Path
|''<code>--template</code> Template Name''
|Inits a project at the path (from a template if specified)
|-
|<code>project import</code>
| colspan="2" |
|''Not implemented yet''
|}

User:Kelbaz

2023-07-13T15:11:39Z

Kelbaz: /* Links */

[[File:Kelbaz graph.png|thumb|A beautiful logo]]
Hey there! I'm Kelbaz, the dev behind [[Border]], the TypeScript Compiler for Windows 96 and KoreJS. I'm active in the community and on this wiki. You can contact me [mailto:its.kelbaz@gmail.com here].

== Repository ==
All my apps are available on [https://onofficiel.github.io/w96 this repository] (a guide on how to add it to your installation is present on the website). They are all open source so your contribution is welcomed!

== Links ==

* [https://codeberg.org/kelbaz Codeberg]
* [https://kelbazz.github.io Website]
* [https://github.com/kelbazz Github]
*[https://mastodon.social/@Kelbaz Mastodon]

Win96 Run Time

2023-07-12T20:38:10Z

Kelbaz: Added the Module Part

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, this script 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 before. these script 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 asyncronous context, so it is possible to use top-level <code>await</code>.

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

* Start the script with the following shebang: <code>//!wrt</code>
* Run the <code>wrtrun</code> command with the path to the script

== History ==
The Windows Runtime was introduced in Windows 96 v2 Service Pack 2.<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 ==
The shebang is the first line of a binary. The WRT shebang starts with <code>//!wrt</code>. The shebang denotes that this regular file is a WRT bin, and must be the very first line in any WRT application.

=== The binary specification (BSPEC) ===
The binary specification (BSPEC) is a way to describe metadata for a WRT bin. 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. Those files will also run in WRT and will 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 will 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>.

Dynamic Wallpaper (DWP)

2023-07-11T20:00:10Z

Kelbaz: /* Known Glitches */

A Dynamic Wallpaper is a special JSON-based wallpaper format for moving wallpapers. A dynamic wallpaper file (DWP) is a JSON object with the properties `name`, `author`, `url`, and `properties` properties (sounds weird to say "properties properties"). Dynamic Wallpapers were introduced with the release of [[Windows 96 v2]] Service Pack 1.

''This is the contents of the DWP file for the Cloud Animated wallpaper:''
<syntaxhighlight lang="json">
{
"name": "Cloudy Animated",
"author": "litevx",
"url": "/system/resource/dwp/clouds/index.html",
"properties": {}
}
</syntaxhighlight>
== Documentation ==

name: The name of the animated wallpaper

author: The name of the person who created the wallpaper

url: The web page the wallpaper is located at

properties: An empty object, unknown what it is for.

== Known Glitches ==

Dynamic Wallpaper also uses iFrames to display content (just like [[InternetE]]).

Most browsers allow javascript: URLs to run inside an iFrame. When javascript: URLs are run in an iFrame, they are treated as same-origin (just like about:blank). This means users can get infected with malware from applying DWPs or even just previewing them. The JavaScript code could also show an actual wallpaper while secretly corrupting files, adding boot scripts, replacing the shell, adding a custom kernel, and running other malicious processes.

Win96 Run Time

2023-06-03T16:07:36Z

Kelbaz: /* Usage */ updating to wrtrun bin

Disk Encryption

2023-06-03T16:05:57Z

Kelbaz:

[[File:Disk encryption wizard.png|thumb|The Disk Encryption setup wizard]]
[[File:Disk encryption password prompt.png|thumb|The dialog asking for your password to decrypt the C: drive on boot]]Disk Encryption is a feature introduced in [[Windows 96 v3|v3]] that allows you to protect your files by encrypting your disk.

== Features ==
Disk Encryption is different than a login password. A login password is stored in a file, which can easily be removed via your browser's DevTools console. Disk Encryption encrypts all your files with an encryption key generated from a password you choose. Once you enable Disk Encryption, you will need your password to access your files.

'''''Note:''' If you forget your password, you have no choice but to reset your Windows96 installation.''

== Usage ==
Disk Encryption can only be launched from the Control Panel, but the Disk Encryption wizard has to be ran in recovery mode. Therefore, launching Disk Encryption will automatically reboot Windows 96 into recovery mode.

User:Kelbaz

2023-05-20T13:13:03Z

Kelbaz:

Monaco

2023-04-15T15:58:48Z

Kelbaz: Languages update

[[File:Monaco.jpg|thumb|Monaco editing a CSS file.]]
Monaco is a Windows 96 code editor based on [[Microsoft]]'s similarly named editor. Monaco supports syntax highlight. It also supports code completion, refactoring and formatting.

== Languages ==
Monaco supports several languages, here is a list of them:

* HTML
* CSS
* JavaScript
* TypeScript
* Batch
* C / C++
* INI
* JSON
* Lua
* Markdown
* Python
* YAML

== Customisation ==
Monaco can be customized by editing a configuration file stored at <code>C:/user/appdata/Monaco/config.json</code>. Here is an example of configuration:<syntaxhighlight lang="json" line="1">
{
"theme": "vs-dark",
"enableMinimap": true,

"fontFamily": "JetBrains Mono",
"fontSize": 13,
"lineHeight": 18
}
</syntaxhighlight>

== Additional informations ==

* A command palette can be displayed by pressing <code>F1</code>
* HTML files can be viewed in [[InternetE]] by clicking on ''"Tools > Preview in Browser"''

[[Category:Apps]]

File System Structure

2023-04-15T15:15:11Z

Kelbaz: Added /system/startup

Windows 96 has a unique file structure, which has gone through many changes in each major version.

== Default Volumes ==
Upon boot, the kernel mounts 4 default volumes, which are deemed essential to the operation of a Windows 96 session.
{| class="wikitable"
!Letter
!Description
|-
|B:
|A hidden cache drive, which is commonly used to store boot logs, etc.
|-
|C:
|The root drive of a Windows 96 installation, containing the files needed for a successful startup.
|-
|W:
|A file system representation of the true system files (the files which boot Windows 96 in in browser)
|-
|Z:
|A ramdisk used to store files which are only needed for the current session.
|}

== General Purpose Locations ==
{| class="wikitable"
!Path
!Description
|-
|c:/user
|Personal home folder.
|-
|c:/user/appdata
|Application data.
|-
|c:/user/desktop
|The desktop folder, which contains the files shown on the desktop.
|-
|c:/user/documents
|A generic folder for document storage.
|}

== System Locations ==
{| class="wikitable"
!Path
!Description
|-
|c:/trash
|Where deleted files go before being permanently deleted.
|-
|c:/local
|A directory which stores programs/program data local to the current installation (e.g. packages from Package Manager).
|-
|c:/system
|System files. Usually configuration files, boot scripts, app registration files, etc.
|-
|c:/system/boot
|Where boot scripts are stored (scripts that run before startup).
|-
|c:/system/startup
|Where startup scripts are stored (scripts that run on startup).
|-
|c:/system/config
|Where configuration files are stored.
|-
|c:/system/etc
|Where system configuration files are stored.
|-
|c:/system/resource
|A folder which can store custom themes, icon and sound packs.
|-
|c:/system/local
|Local system programs/binaries/libraries. Also stores modules used for WRT.
|-
|c:/system/log
|A folder where log files are usually stored.
|-
|c:/system/packages
|A folder which contains package manager data.
|-
|c:/system/programs
|Shortcuts which are displayed in the start menu.
|-
|c:/system/temp
|Temporary files are stored here. They are removed on reboot.
|-
|c:/system/wallpapers
|Where wallpapers are stored.
|}

April 10th

2023-04-10T21:33:31Z

Kelbaz: 2023

April 10th is the official anniversary day of Windows 96. The OS is currently 4 years old as of last anniversary.

== 2020 ==
Nothing special occurred during 2020, mainly due to the 2020 pandemic and lack of motivation during such crippling times.

== 2021 ==
[[File:Service Pack 1 Upgrade Screenshot.png|thumb|Service Pack 1 welcome screen (triggered on startup)]]
A special anniversary welcome screen was added during the anniversary, which included numerous apps, features, and bug fixes.

An open sourcing of Windows 96 was (and still is to some extent) planned, but this was delayed indefinitely.

== 2022 ==
V3 was initially planned to be released on the third anniversary of Windows 96. This didn't happen due to a multitude of development roadblocks.

Instead, an anarchy Minecraft server event was held in the Windows 96 Discord, where a player could win a prize for the best looking base.

== 2023 ==
For the 2023 Anniversary of Windows 96, Userland was opensourced. Some of the changes includes a new [[Monaco]] release and the complete rework of [[MsgRoom]].

Developing Applications

2023-04-05T12:18:32Z

Kelbaz: Categorization

Windows 96 includes a flexible API for developing your own applications. All applications are ran under WRT, which is a partial sandbox and runtime provided by Windows 96 for applications.

Applications may be referred to as "bins", "WRT bins", "application bin", or "sysbins" depending on the context.

== Structure of an application ==
Windows 96 applications are simply JavaScript files without the .JS extension that include a WRT shebang (<code>//!wrt</code>). The shebang denotes that this regular file is a WRT bin, and must be the very first line in any WRT application. It may sometimes include a binary specification (BSPEC) suffix to describe some metadata about the application.

=== The binary specification (BSPEC) ===
As mentioned before, the binary specification (BSPEC) is a way to describe metadata for a WRT bin. 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>

=== A GUI example program ===

Here is an example of a very basic Windows 96 GUI program:<syntaxhighlight lang="javascript" line="1">
//!wrt
const { Theme } = w96.ui;

class GUIApplication extends WApplication {
/**
* Application constructor.
*/
constructor() {
super();
}

/**
* Main entry point.
* @param {String[]} argv The program arguments.
*/
async main(argv) {
super.main(argv);

// Create the window
const mainwnd = this.createWindow({
title: "Sample Application",
body: "Sample text",
bodyClass: "sample-app",
taskbar: true,
resizable: true,
initialHeight: 480,
initialWidth: 640,
icon: await Theme.getIconUrl("mime/executable", '16x16')
}, true);

// Show the window
mainwnd.show();
}
}

return await WApplication.execAsync(new GUIApplication(), this.boxedEnv.args);
</syntaxhighlight>Save this file anywhere, without a file extension, and then double click to run it. You may need to refresh your explorer view to allow it to recognize this file as a program.

=== A CLI example program ===
Here is an example of a very basic Windows 96 terminal program:<syntaxhighlight lang="javascript" line="1">
//!wrt $BSPEC:{"ssy":"cli"}

const term = this.boxedEnv.term;
// If the program is not executed in a terminal, exit.
if (!term) return;

class CLIApplication extends WApplication {
/**
* Application constructor.
*/
constructor() {
super()
}

/**
* Main entry point.
* @param {String[]} argv The program arguments.
*/
async main(argv) {
super.main(argv);

// Write some text in the terminal.
term.writeln("Hello World!");
term.writeln("Welcome to the most useful app!");

// Get user input and store it in a variable.
let e = await term.prompt("Enter your first name: ");
term.writeln("Nice job " + e + "!");

let r = await term.prompt("Last name: ");
term.writeln(`Hi there ${e} ${r}!`);

// Pause the program.
await term.pause()
}
}

return await WApplication.execAsync(new CLIApplication(), this.boxedEnv.args, this);
</syntaxhighlight>Save this file anywhere, without a file extension, and then enter the path to the file in the terminal to run it.

== Running an application ==
To run an application, you can either:

* Run it from the Run box or terminal with its executable name, if the binary is present in any directory denoted by the PATH environment variable.
* Double click it in an explorer window to execute it in the current directory.
* Enter the absolute path of the application bin in a Run box or terminal window.
[[Category:Tutorials]]

Developing Games

2023-04-05T12:17:57Z

Kelbaz: Categorization

Windows 96 can be pretty boring at times. There are games in the Package Manager, but what if you want to create your own games?

You can [[Developing Games/JavaScript|use JS]], otherwise here are some tutorials for various game engines (that are known to export to HTML5):
* [[Developing Games/Unity|Unity]]
* [[Developing Games/Godot|Godot Engine]]
* [[Developing Games/Construct|Construct 2/3]]
* [[Developing Games/Flixel|HaxeFlixel]]
* [[Developing Games/Fusion|Clickteam Fusion]]
[[Category:Tutorials]]

Category:Tutorials

2023-04-05T12:14:16Z

Kelbaz: r

Various tutorials to help you customise your Windows 96

Jsh

2023-04-05T12:12:54Z

Kelbaz: Added apps category

[[File:Jsh.jpg|thumb|The JSH program]]
JSH ''(aka JS Shell)'' is a Windows 96 command line interface read–eval–print loop ''(REPL)'' program able to evaluate JavaScript inside a [[Win96 Run Time|WRT]] module environment.

== Specificities ==
Unlike inside WRT modules, it is not possible to use top-level await in the JSH REPL. JSH also features commands, it is possible to see all of them by typing <code>.help</code> in the shell. JSH will format all the outputs with syntax highlighting.

== Commands ==
JSH has several commands that can be used to do specific actions. Here are them:
{| class="wikitable"
|+
!Command
!Arguments
!Description
|-
|<code>.clear</code>
|
|Clears the screen
|-
|<code>.exit</code>
|
|Quits the REPL shell
|-
|<code>.load</code>
|path
|Loads the specified file into the current shell
|-
|<code>.help</code>
|
|Shows the help message
|}
[[Category:Apps]]

Jsh

2023-04-04T17:45:27Z

Kelbaz: Created JSH page

File:Jsh.jpg

2023-04-04T17:16:38Z

Kelbaz:

The JS Shell Program

Package Manager

2023-03-25T17:54:57Z

Kelbaz: Structured and added community repos so much easier to find

[[File:Package Manager.jpg|thumb|The Package Manager program.]]
The package manager is Windows 96's primary method of distribution for programs. The term "package" refers to a complex set of folders and files, which when coupled with a JSON file and structured correctly, can be decoded by the package manager program and unpacked into the Windows 96 filesystem.

==Functioning ==
Packages are hosted on a webserver, where the root URL of the package folder is then set as a package repository in the package manager. Packages can be hosted on any static website host (i.e. Github Pages), and comprise of a set of 16x16 and 32x32 pixel icon files, as well as a "content@1.0" directories/zips and a JSON file which sets the folders and icons as variables.[[File:Pkgman-structure.png|The package manager file structure.|thumb]]
==Package structure==
During the creation of a package repository, the package manager must be able to decode the structure of the package to be able to successfully unpack any files or folders inside. The file sctructure can be found on the right.

==Community==
Packages are created by the community to share their work to other users. Packages may contain applications, programs, tools, themes, or wallpapers. Here are some repositories created by the community:
{| class="wikitable"
!URL
!Author
!Note
|-
|https://packages.windows96.net/community
|Windows 96 Contributors
|The official community repository. Packages are picked using a high standard.
|-
|https://nandertga.ddns.net/w96-packages
|NanderTGA
|
|-
|https://billygoat891.github.io/w96/repo
|billygoat891
|
|-
|https://sgeo.github.io/win96-repos/apps
| rowspan="2" |Sgeo
|
|-
|https://sgeo.github.io/win96-repos/malware
|Malware repository - use at your own risk
|-
|https://packages.ctrl.wtf/main
|ctrlz
|
|-
|https://jameisepic.github.io/thinkjame/public/main
|JameIsEpic
|
|-
|https://w96.stilic.ynh.fr/main
|Stilic
|
|-
|https://onofficiel.github.io/w96/v2
| rowspan="2" |Onofficiel
|Only for [[Windows 96 v2]]
|-
|https://onofficiel.github.io/w96/v3
|
|}

File:Pkgman-structure.png

2023-03-25T17:32:15Z

Kelbaz:

The package manager file structure.

File:Package Manager.jpg

2023-03-25T17:27:21Z

Kelbaz:

The Package Manager application

API:w96.FS

2023-03-22T15:32:20Z

Kelbaz: Started this page

=== <code>class FS</code> ===
This namespace refers to the file system API of Windows 96. <code>w96.FS</code> allows manipulation of file system entries by, for example, renaming, deleting or copying them. It is also possible to create, read and write files and directories.

== Structure ==

=== <code>mount(fso: IFileSystem): Promise<void></code> ===
Mounts a file system using the specified object ("driver").

=== <code>umount(prefix: String): Promise<void></code> ===
Unmounts a file system instance.

=== <code>mounts(): IFileSystem[]</code> ===
Gets all mounted file systems.

=== <code>list(): String[]</code> ===
Gets all mounted file system prefixes.

=== <code>nextLetter(): String</code> ===
Get the next available drive letter.

=== <code>toBlob(path: String): Primise<Blob></code> ===
Creates a blob from a specified path.

=== <code>get(prefix: String): IFileSystem</code> ===
Retuns a file system by its prefix.

=== <code>toURL(path: String): Primise<String></code> ===
Creates a URL from the specified file path.

=== <code>isFile(path: String): Primise<Boolean></code> ===
Returns <code>true</code> if the entry is a file.

=== <code>isEmpty(path: String): Primise<Boolean></code> ===
Returns <code>true</code> if the file is empty.

=== <code>mkdir(path: String): Primise<Boolean></code> ===
Creates a directory at the specified path.

=== <code>rmdir(path: String): Primise<Boolean></code> ===
Deletes a directory at the specified path.

=== <code>touch(path: String): Primise<Boolean></code> ===
Creates a file at the specified path.

=== <code>rm(path: String): Primise<Boolean></code> ===
Deletes a file at the specified path.

=== <code>readdir(path: String): String[]</code> ===
Returns a list of entities contained in the specified path.

=== <code>cpdir(src: String, dest: String): Promise<Boolean></code> ===
Copies a directory to a new destination.

=== <code>cpfile(src: String, dest: String): Promise<Boolean></code> ===
Copies a file to a new destination.

=== <code>mvfile(src: String, dest: String): Promise<Boolean></code> ===
Moves a file to a new destination.

=== <code>mvdir(src: String, dest: String): Promise<Boolean></code> ===
Moves a directory to a new destination.

=== <code>exists(path: String): Boolean</code> ===
Checks if an entity exists.

=== <code>readstr(path: String): Promise<String></code> ===
Reads the specified file as a string.

=== <code>readbin(path: String): Promise<Uint8Array></code> ===
Reads the specified file as binary.

=== <code>filetype(path: String): 0 | 1 | -1</code> ===
Returns the file type of a node. This can be a binary or text file.

=== <code>writestr(path: String, data: String): Promise<Boolean></code> ===
Truncates and writes a UTF-8 encoded string to the specified file.

=== <code>writebin(path: String, data: Uint8Array | Number[]): Promise<Boolean></code> ===
Truncates and writes data to the specified file.

=== <code>walk(path: String): String[]</code> ===
Walks through the contents of a directory.

=== <code>stat(path: String): FSStatResult</code> ===
Retrieves information about a file system entry.

=== <code>rename(path: String, newName: String): Promise<Boolean></code> ===
Renames a file or folder.

=== <code>readBinChunk()</code> ===

=== <code>readStrChunk()</code> ===

=== <code>cache()</code> ===

=== <code>uncache()</code> ===

=== <code>getFromCache()</code> ===

=== <code>hash(path: String, algorithm: "default" | "md5" | "sha256" | "sha512"): Promise<String></code> ===
Create a hash from a given path and algorithm.

=== <code>assert()</code> ===
[[Category:API]]

User:Kelbaz

2023-03-21T20:32:05Z

Kelbaz: undo

[[File:Kelbaz graph.png|thumb|A beautiful logo]]
Hey there! I'm Kelbaz, the dev behind Border, TSC for Windows 96 and Faastify. I'm active in the community and on this wiki.

== Repository ==
All my apps are available on [https://onofficiel.github.io/w96 this repository] (a guide on how to add it to your installation is present on the website). They are all open source so your contribution is welcomed!

== Links ==

* [https://github.com/kelbazz Github]
* [https://kelbazz.github.io Website]
* [https://codeberg.org/kelbaz Codeberg]

MsgRoom

2023-03-21T18:49:45Z

Kelbaz: Added to the apps category

[[File:MsgRoom Screenshot.png|thumb|MsgRoom with a dark theme applied. You can also see the staff title, which many users try to fake in the MSGroom. Stop doing that, you aren't fooling anyone.]]
MsgRoom is a chat room for Windows 96. It allows people to chat to others in real time. No registration is required to use the service, though IP bans can be given out in cases of abuse.

== Features ==
MsgRoom offers the following features:

* 3 default themes, with the option to create your own using css stylesheets.
* Markdown formatting in text messages.
* TweMoji rendering for messages containing emoji. There is no dedicated emoji picker as of now.

== Commands ==
MsgRoom is equipped with several useful commands. Here is a list of them and what they do.
{| class="wikitable"
!Command
!Description
|-
|/about
|Prints some about text displaying the current version of MsgRoom.
|-
|/block <user_id>
|Blocks a user by ID. This will prevent you from seeing their messages.
|-
|/clear
|Clears the current chat log.
|-
|/config
|Edits the current chat configuration.
|-
|/help
|Views the built in help.
|-
|/list
|View online members. This command also displays their user IDs and whether they are blocked.
|-
|/unblock <user_id>
|Unblocks a user by ID.
|}

== Trivia ==

* A witty comment will be displayed if you attempt to block yourself.
* The nickname "System" cannot be used as nickname. Doing so will prompt an error.
[[Category:Apps]]

SCM

2023-03-21T16:08:32Z

Kelbaz: Redirected page to System Configuration Manager

#REDIRECT [[System Configuration Manager]]

TUT:Set a search engine in InternetE

2023-03-21T15:43:42Z

Kelbaz: /* Example search engines */

{{DISPLAYTITLE:Set a search engine in InternetE}}

= How to set a Search Engine in InternetE =

==Opening SCM==
[[File:Scm-in-start-menu.png|alt=The start menu entry to access System Configuration Manager|thumb|276x276px]]
Start by opening up the [[System Configuration Manager|System Config Manager]] (SCM).

You can open it either by

#going to <code>Start Menu > Programs > System > System Config Manager</code>
#or entering <code>scm</code> into the run box.

== Browsing the configuration==
[[File:Internete_scm_folder.png|alt=The InternetE folder in the "Software" Section of the System Config Manager|thumb|275x275px]]
Once in SCM, go to <code>Software > InternetE</code>. If you don't see the [[InternetE]] folder, it means you probably haven't used InternetE and need to open the InternetE in order for the folder to appear.

''Note: If you don't see the Software folder, reboot Windows96. If it still doesn't show up, you may need to reinstall Windows96''

==Configure the new search engine==
[[File:Scm-edit-internete-search.png|alt=The dialog to edit the InternetE search engine in SCM|thumb|280x280px]]
Once in the InternetE folder, double-click the "searchEngine" entry. Delete the text in the <code>JSON Value</code> box, and put a pair of quotation marks (<code>"</code>). You can now put the URL to your favorite search engine. To determine where the search query will go, put <code>%SEARCH_QUERY%</code>.

==Example search engines==
To help you, some entries for popular search engines will go here (including the quotes).
{| class="wikitable"
|+
!Search Engine
!URL
!CORS Unblocker need ?
|-
|Google
|<code>"<nowiki>https://www.google.com/search?igu=1&q=%SEARCH_QUERY</nowiki>"</code>
|no
|-
|Bing
|<code>"<nowiki>https://bing.com/search?q=%SEARCH_QUERY%</nowiki>"</code>
|no
|-
|DuckDuckGo
|<code>"<nowiki>https://duckduckgo.com/search?q=%SEARCH_QUERY%</nowiki>"</code>
|yes
|-
| Brave
|<code>"<nowiki>https://search.brave.com/search?q=%SEARCH_QUERY%</nowiki>"</code>
|yes
|-
|Skynet (Windows 93)
|<code>"<nowiki>https://pierrepapierciseaux.net/.skynet/?q=%SEARCH_QUERY%</nowiki>"</code>
|no
|-
|Ecosia
|<code>"<nowiki>https://ecosia.org/search?q=%SEARCH_QUERY%&method=index</nowiki>"</code>
|yes
|-
|Wikipedia
|<code>"<nowiki>https://en.wikipedia.org/wiki/?search=%SEARCH_QUERY%</nowiki>"</code>
|no
|-
|YouTube
|<code>"<nowiki>https://youtube.com/results?search_query=%SEARCH_QUERY%</nowiki>"</code>
|yes
|}
[[Category:Tutorials]]
{{DEFAULTSORT:Set_a_search_engine_in_InternetE}}

WRT

2023-03-21T15:31:19Z

Kelbaz: Added a redirection page

#REDIRECT [[Win96 Run Time]]

Win96 Run Time

2023-03-21T15:27:36Z

Kelbaz: Created WRT page

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, this script 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 before. these script 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 asyncronous context, so it is possible to use top-level <code>await</code>.

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

* Start the script with the following shebang: <code>//!wrt</code>
* Run the <code>wjs</code> command with the path to the script

== History ==
The Windows Runtime was introduced in Windows 96 v2 Service Pack 2.<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 ==
The shebang is the first line of a binary. The WRT shebang starts with <code>//!wrt</code>. The shebang denotes that this regular file is a WRT bin, and must be the very first line in any WRT application.

=== The binary specification (BSPEC) ===
The binary specification (BSPEC) is a way to describe metadata for a WRT bin. 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>

TUT:Set a search engine in InternetE

2023-03-21T14:08:03Z

Kelbaz: Clearify the tutorial

{{DISPLAYTITLE:Set a search engine in InternetE}}

= How to set a Search Engine in InternetE =

==Opening SCM==
[[File:Scm-in-start-menu.png|alt=The start menu entry to access System Configuration Manager|thumb|276x276px]]
Start by opening up the [[System Configuration Manager|System Config Manager]] (SCM).

You can open it either by

#going to <code>Start Menu > Programs > System > System Config Manager</code>
#or entering <code>scm</code> into the run box.

== Browsing the configuration==
[[File:Internete_scm_folder.png|alt=The InternetE folder in the "Software" Section of the System Config Manager|thumb|275x275px]]
Once in SCM, go to <code>Software > InternetE</code>. If you don't see the [[InternetE]] folder, it means you probably haven't used InternetE and need to open the InternetE in order for the folder to appear.

''Note: If you don't see the Software folder, reboot Windows96. If it still doesn't show up, you may need to reinstall Windows96''

==Configure the new search engine==
[[File:Scm-edit-internete-search.png|alt=The dialog to edit the InternetE search engine in SCM|thumb|280x280px]]
Once in the InternetE folder, double-click the "searchEngine" entry. Delete the text in the <code>JSON Value</code> box, and put a pair of quotation marks (<code>"</code>). You can now put the URL to your favorite search engine. To determine where the search query will go, put <code>%SEARCH_QUERY%</code>.

==Example search engines==
To help you, some entries for popular search engines will go here (including the quotes).
{| class="wikitable"
|+
!Search Engine
!URL
!CORS Unblocker need ?
|-
|Google
|<code>"<nowiki>https://www.google.com/search?igu=1&q=%SEARCH_QUERY</nowiki>"</code>
|no
|-
|Bing
|<code>"<nowiki>https://bing.com/search?q=%SEARCH_QUERY%</nowiki>"</code>
|no
|-
|DuckDuckGo
|<code>"<nowiki>https://duckduckgo.com/search?q=%SEARCH_QUERY%</nowiki>"</code>
|yes
|-
| Brave
|<code>"<nowiki>https://search.brave.com/search?q=%SEARCH_QUERY%</nowiki>"</code>
|yes
|-
|Skynet (Windows 93)
|<code>"<nowiki>https://pierrepapierciseaux.net/.skynet/?q=%SEARCH_QUERY%</nowiki>"</code>
|no
|-
|Ecosia
|<code>"<nowiki>https://ecosia.org/search?q=%SEARCH_QUERY%&method=index</nowiki>"</code>
|yes
|-
|Wikipedia
|<code>"<nowiki>https://en.wikipedia.org/w/index.php?search=%SEARCH_QUERY%</nowiki>"</code>
|no
|-
|YouTube
|<code>"<nowiki>https://youtube.com/results?search_query=%SEARCH_QUERY%</nowiki>"</code>
|yes
|}
[[Category:Tutorials]]
{{DEFAULTSORT:Set_a_search_engine_in_InternetE}}

April 10th

2023-03-21T13:05:30Z

Kelbaz: Changing age

Media Player

2023-03-21T12:44:28Z

Kelbaz: Added content

[[File:MediaPlayer Control Panel.jpg|thumb|The Media Player control panel]]
[[File:MediaPlayer Video Player.jpg|thumb|The Media Player video player.]]
The Media Player (also known as "MPlayer") is a Windows 96 application which can, as it's name suggests, play audio and video files. This application is not complete but most features are already implemented. The interface is composed of a progress bar to go to a specific moment of the media and of buttons to control to the stream.

== History ==
Media Player was introduced in [[Windows 96 v3|v3]]. Before the 3<sup>rd</sup> Windows 96 release, it was not possible to play audio from files from the user interface. Media Player is the successor to Video Player from [[Windows 96 v2]].

== Features ==
Here is the list of features that Media Player offer:

* Play, pause, stop and eject the stream
* Rewind and fast forward (2 seconds)
* Mark navigation
* Time, frame, track scaling
* Time selection

[[Category:Apps]]

File:MediaPlayer Video Player.jpg

2023-03-21T12:07:38Z

Kelbaz:

The MediaPlayer video player

File:MediaPlayer Control Panel.jpg

2023-03-21T11:41:54Z

Kelbaz:

The MediaPlayer control panel.

InternetE

2023-03-21T11:24:02Z

Kelbaz: Added content

[[File:Internetee screenshot.png|thumb|alt=A screenshot of InternetE displaying the start page|A screenshot of InternetE displaying the start page]]InternetE is the successor to [[Internet Exploder]]. InternetE was first introduced in [[Windows 96 v3]] during the beta program. Despite being completely rewritten from the ground up, click "about" in the "Help" menu will yield a dialog declaring the current version installed to be 2.0.

== Features ==
InternetE uses [[.URL_files|URL Files]] to store bookmarks instead of storing them in JSON Format like [[Internet Exploder]]. InternetE also saves the browsing history, so it is now possible to navigate through it. It is also possible to set a default home page ''(InternetE also uses the same start page as [[Internet Exploder]]).'' InternetE can, unlike its predecessor, define a search engine.

== Option panel ==
[[File:InternetE options.jpg|thumb|InternetE option panel by default.]]
InternetE also introduce a new option panel. This allows the user to configure the browser and control the history. Those options are divised in categories. Here are the current settings:
{| class="wikitable"
|+General
!Setting
!Default value
!Description
|-
! colspan="3" |Home page
|-
|Address
|about:start
|The current page used as the home page.
''(Opened on startup and when the home button is clicked)''
|-
|Use Current
|''(button)''
|Use the current website as home page.
|-
|Use Default
|''(button)''
|Use "about:start" as home page.
|-
|Use Blank
|''(button)''
|Use "about:blank" as home page.
|-
! colspan="3" |History
|-
|Clear History
|''(button)''
|Clears browser history
|}

== Configuration ==
InternetE also provides settings in the [[System Configuration Manager]]. Here are the editable properties:
{| class="wikitable"
|+
!Key
!Default Value
!Description
|-
|homepage
|<code>"about:start"</code>
|The current page used as the home page.
|-
|searchEngine
|<code>"about:blank?placeholder&q=%SEARCH_QUERY%"</code>
|The search engine to use in InternetE. ''(Using "Search" button)''
|}
[[Category:Apps]]

File:InternetE options.jpg

2023-03-21T10:48:16Z

Kelbaz:

InternetE option menu

User:Kelbaz

2023-03-21T09:59:39Z

Kelbaz: That's just a waste of time bro

User:Kelbaz

2023-03-20T18:01:43Z

Kelbaz:

File:Kelbaz graph.png

2023-03-20T17:13:11Z

Kelbaz:

Kelbaz's logo

Monaco

2023-03-20T17:08:04Z

Kelbaz: /* Additional informations: */

[[File:Monaco.jpg|thumb|Monaco editing a CSS file.]]
Monaco is a Windows 96 code editor based on [[Microsoft]]'s similarly named editor. Monaco supports syntax highlight in JS, CSS, HTML and JSON. It also supports code completion, refactoring and formatting.

== Customisation ==
Monaco can be customized by editing a configuration file stored at <code>C:/user/appdata/Monaco/config.json</code>. Here is an example of configuration:<syntaxhighlight lang="json" line="1">
{
"theme": "vs-dark",
"enableMinimap": true,

"fontFamily": "JetBrains Mono",
"fontSize": 13,
"lineHeight": 18
}
</syntaxhighlight>

== Additional informations: ==

* A command palette can be displayed by pressing <code>F1</code>
* HTML files can be viewed in [[InternetE]] by clicking on ''"Tools > Preview in Browser"''

[[Category:Apps]]

Programs

2023-03-20T14:03:48Z

Kelbaz: Added links

Windows 96 comes with a large set of programs preinstalled. They can be found under Start > Programs.

== List of programs ==
Below is a list of all included programs. This list may not always be up to date.

=== Accessories ===
* Editors
** [[Monaco]]
** [[Textpad]]
* Activate Windows
* [[Explorer]]
* Image View
* [[InternetE]]
* [[Media Player]]
* PDF Reader
=== Developer ===
* API Reference
* API Samples
* Developer Documentation
* JS REPL (GUI)
* Performance Counters
* System Flags
=== Entertainment ===
* Emulators
** DosBox
** NES
** [[Super Player]]
* BassonTracker
* Blocks
* [[Gameing]]
* Meme Man
* Pinball
* Pumkin World
* Troll
=== Network ===
* [[MsgRoom]]
* [[P3]]
* [[ShareBoard|Share Board]]
* [[SuperTerm]]
* Win96 Multiplayer
=== Other ===
* [[API:BSOD|BSOD]]
* Effects
* GL Test
* Matrix
* Tips
* [[Version Browser]]
* Wiki96
=== System ===
* Backup
* Device Manager
* Linux
* [[Package Manager]]
* [[System Configuration Manager|System Config Manager]]
* Task Manager
* Terminal
* Window Manager Settings
=== Utility ===
* Base64
* MDView
* PC Health Check
* [[Bug Report Tool|Report Bug]]
* [[Uploader]]
* Wasm Tools
* noTRON AV
=== WINE ===
* WINE
=== WTF ===
* [[YouAreAnIdiot]]