DBYTEOS PRE-ALPHA TEST

This is not a release.
This is a bootable test image.
It boots.
It drops into the kernel shell.
It exposes a few hardware smoke paths.
Most of the dangerous stuff is still blocked on purpose.

EXPECT BUGS AND CHAOS
ISO 9660 BOOT IMAGE
RUN IT IF YOU WANT TO SEE WHERE IT BREAKS

DOC: QEMU_BOOT_SMOKE.md

 

Boot Smoke

DByteOS running from the ISO inside VMware Workstation.

 

IRQ Runtime Gate

Command used:

irq-runtime-final-gate-status

This is the current IRQ runtime boundary.

Nothing here is pretending to be “ready”.

• activation gate: blocked
• readiness matrix: blocked
• STI: blocked
• EOI dispatch: blocked
• PIC unmask: blocked
• IDT runtime bind: blocked
• hardware mutation: no
• runtime IRQ active: no

The kernel can show the gate before it crosses it.

No blind sti.
No live IRQ0/IRQ1.
No random PIC unmask.
No fake “it works on my machine” milestone.

 

DByte v3.3.0

DByte v3.3.0 is a public alpha release focused on the DByteOS userland prototype, shell session environment, and autopath command resolution.

DByte is a fast low-level scripting language for binary parsing, buffer patching, byte search, typed integer workloads, and automation scripts that need simple syntax with predictable behavior.

This release continues the move from “just a language” toward a personal programmable computing environment.

Highlights

• DByteOS userland prototype
• DByte shell session environment hardening
• Shell autopath command resolution
• Hyphenated command mapping, such as mkdir-demo resolving to mkdir_demo.dby
• DByteOS-style layout with /bin, /etc, /home, /sys, and /tmp
• Continued support for binary parsing, mutable buffers, byte search, and patching workflows
• REPL and DByte-native shell workflow
• Rust embedding support through dbyte_embed
• Public alpha Windows x64 release package

DByteOS Userland

DByteOS is a simulated operating-system-style userland running on the host DByte runtime.

It is not a native kernel yet. It is a userland prototype for experimenting with a personal computing environment where commands, tools, and runtime behavior are scriptable in DByte.

Current layout:

• /bin — command scripts and utilities
• /etc — configuration files
• /home — simulated user space
• /sys — internal profile and system logic
• /tmp — temporary scratch space

Autopath

With DByteOS autopath enabled, shell commands can resolve to scripts under bin/ without writing one alias per command.

Examples:

cat
mkdir-demo
path which mkdir-demo

Hyphenated command names can map to underscore script names:

mkdir-demo -> mkdir_demo.dby

Install

Download the release asset:

dbyte-v3.3.0-windows-x64.zip

Extract it, then run:

powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1

Verify:

dbyte --version
dbyte run --vm examples\hello.dby
dbyte test --engine vm

Expected version:

DByte 3.3.0

Manual Smoke Test

This release package was smoke-tested after packaging:

dbyte.exe --version
=> DByte 3.3.0

dbyte.exe run --vm examples\hello.dby
=> Hello, DByte!

dbyte.exe run --vm examples\binary_patcher.dby
=> patched 1
=> 009090909000

Release Asset

dbyte-v3.3.0-windows-x64.zip

Size:

686111 bytes

SHA-256:

8569341AEACFCA73526141E34FEBCB01057CA0DCFFB9565D47E7D2442957FFB6

Alpha Notice

DByte is still public alpha software. The language, shell, DByteOS userland, and standard library may continue to change before a stable release.

DByteOS is a userland prototype, not a native kernel.

Keep originals. Test output. Diff files. Then ship.