Documentation & Support

Important: The ISO currently available for download is a prototype build. It is intended for testing and feedback only — expect bugs, incomplete features, and possible data loss. Do not use this build in production systems.

Guides, troubleshooting, and resources to help you install, configure, and contribute to Merdekasoft products.

Getting Started

Welcome — this short guide helps you download and try B OS quickly using the Live session, or perform a full installation.

Prototype notice: The build currently published is a prototype. Use it only for testing and evaluation. Please back up important data and test in a virtual machine or spare hardware where possible.

  1. Download the latest ISO from our download page (merdekasoft.id).
  2. Verify the ISO checksum (recommended).
  3. Create a bootable USB (see Installation section).
  4. Boot into the Live environment to test hardware compatibility.
  5. Run installer to install to disk when you are ready.

Installation

Download

Get the prototype ISO from our releases. This build is an early prototype and may change frequently. We publish checksums with each release — always compare the checksum shown on the download page before testing.

You can download the prototype ISO from our site: https://merdekasoft.id/#download

Verify ISO (Checksums)

We publish SHA256 checksums with each release. To verify your download, use your operating system's graphical checksum utility or a file-hash tool and compare the result with the checksum published on the download page.

Create bootable USB (recommended)

Use a graphical USB writer to create a bootable USB from the downloaded ISO. Popular, user-friendly tools include:

These tools provide a safe, guided workflow to write the ISO to your USB drive. Be careful — writing an image will erase the target drive.

Installation steps

  1. Boot from the USB and select "Try Live" to test.
  2. On the Live desktop, double-click the installer icon.
  3. Follow installer: choose language, time zone, keyboard layout.
  4. Choose installation type: erase disk or manual partitioning (advanced).
  5. Create user account and complete installation. Reboot when finished.

Rufus (Windows)

Rufus is a small Windows utility that helps create bootable USB drives from ISOs.

Prototype reminder: When writing the prototype ISO, remember this is an early build — use test hardware or a virtual machine and do not rely on it for production data.

  1. Download Rufus from the official site: https://rufus.ie/
  2. Run Rufus (no installation required for the portable build).
  3. Insert a USB drive and select it under "Device".
  4. Under "Boot selection", choose "Disk or ISO image (Please select)" and click Select to pick B-OS-live-prototype-amd64.hybrid.iso.
  5. Leave partition scheme and target system as recommended (Rufus usually detects correct defaults for BIOS/UEFI). If you need UEFI-only, choose GPT; for older BIOS choose MBR.
  6. Click Start and follow prompts. If Rufus offers write-mode choices, choose the recommended ISO/image mode unless you have a specific need to change it.
  7. Wait until Rufus finishes, then safely eject the USB drive.

Warning: This will erase the target USB drive. Make sure you selected the correct device.

Ventoy (Windows / Linux)

Ventoy lets you create a bootable USB that can contain multiple ISO files — great for maintaining several installers on one drive.

Prototype reminder: The ISO you copy to Ventoy is a prototype. Please treat it as experimental and keep backups of any important data.

  1. Download Ventoy from the official project: https://www.ventoy.net/
  2. Follow the platform instructions provided on Ventoy's website:
    • Windows: use the Ventoy utility to install Ventoy to the USB device.
    • Linux: follow the installation steps described on the Ventoy site for Linux systems.
  3. Install Ventoy to the USB device (this formats the drive).
  4. After installation, simply copy B-OS-live-prototype-amd64.hybrid.iso (and other ISOs) to the USB partition created by Ventoy.
  5. Boot from the USB and Ventoy will present a menu to choose which ISO to boot.

Ventoy preserves the USB layout so you can add or remove ISOs without reformatting.

System Requirements

This is a prototype build — please test on spare hardware or in a virtual machine and back up important data.

Post-install Setup

After installing, we recommend:

Key Features

FAQ

For major version changes we recommend a fresh install. For regular updates, use the system's graphical Software Updater. The updater will show available package updates and guide you through installing them.
Yes — choose manual partitioning during install and make sure to back up all important data first. If you are unsure, test the installer in a virtual machine or on spare hardware. Our documentation includes general advice but always review your device's manufacturer guidance for boot options and UEFI settings.
Open issues on our issue tracker (link in footer) or use the support email. When reporting, include: a clear title, steps to reproduce, what you expected, what happened, screenshots or short screen recordings, and the environment (device model, BIOS/UEFI, and whether you used Live or full install). Since the current release is a prototype, please include the prototype version or ISO filename when possible.
We publish checksums with every release on the download page. Use a graphical checksum tool or file-hash utility to compute the checksum of the downloaded file and compare it to the value on the site. If the checksums don't match, re-download the ISO and avoid using the corrupted copy.
The prototype may include incomplete features, temporary UI text, driver limitations, or installer rough edges. Hardware support can be limited (especially new Wi‑Fi or GPU models). Expect frequent updates; do not use the prototype on critical systems. Check the Changelog and the Troubleshooting section for currently tracked issues.
Installing to disk can overwrite existing data if you choose to erase the disk. Always back up important files before installing. If you want to try without affecting your system, use the Live session or test inside a virtual machine.
Use the system's Software & Updates (if present) or vendor-provided utilities to locate and install proprietary drivers. If hardware isn't detected in the Live session, include device details when filing a bug so developers can investigate driver support.
We welcome contributions. Fork the repository, make your changes (including docs), and submit a pull request. See CONTRIBUTING.md for style, testing, and review guidelines. Small doc fixes (typos, clarifications) are especially helpful for new users.
Yes. The app installer supports common formats like .deb, AppImage, and Flatpak. Use the app installer GUI to add applications and check sandboxing/security options when available.
Open a feature-request on the issue tracker with a clear description, use-case, and any mockups or examples. Label it as a feature request so maintainers can triage it appropriately.
Use our community forum, support email, or issue tracker. For faster help, include screenshots, logs, and steps you've already tried. Community volunteers and maintainers monitor these channels and will guide you through troubleshooting.

Troubleshooting

Boot issues

If the system doesn't boot from USB, check:

Wi‑Fi not working

Try installing additional drivers using the system's Software & Updates or vendor-provided driver utilities. If those aren't available, connect via Ethernet to the internet and consult the vendor website or documentation for driver packages and installation instructions.

Display problems

Use safe graphics mode or install vendor drivers (NVIDIA/AMD) from vendor-provided utilities or instructions. If you are unsure, test in the Live session and include hardware details when reporting issues.

Contribute

Want to help? Report issues or open a pull request on our GitHub: github.com/merdekasoft. Check the repository for contribution guidelines.

Support

If you need help beyond documentation:

Because the current release is a prototype, please include detailed reproduction steps, logs, and the environment you used when reporting bugs — this helps the development team address issues faster.