2025-09-29 18:57:23 +02:00
2025-09-29 18:54:16 +02:00
2025-09-29 17:52:43 +02:00
2025-09-24 00:40:56 +02:00
2025-09-29 18:57:23 +02:00
2025-09-24 00:49:54 +02:00
2025-09-24 00:40:56 +02:00
2025-09-29 17:44:14 +02:00
2025-09-29 18:54:48 +02:00
2025-09-29 18:54:48 +02:00
2025-09-24 00:40:56 +02:00
2025-09-24 00:53:09 +02:00
2025-09-24 00:40:56 +02:00
2025-09-29 18:54:48 +02:00
2025-09-29 18:54:48 +02:00
2025-09-29 18:54:48 +02:00
2025-09-24 00:51:56 +02:00
2025-09-24 00:40:56 +02:00
2025-09-24 00:40:56 +02:00
2025-09-29 18:54:48 +02:00
2025-09-29 18:54:48 +02:00
2025-09-29 18:00:00 +02:00
2025-09-14 16:15:44 +02:00
2025-09-29 18:54:48 +02:00
2025-09-29 18:00:00 +02:00

5150 stuff

The binary programs here use multiple conventions (more Fun!):

  • .asm files use NASM syntax and are built with nasm xx.asm
  • .s files use GAS syntax, they are built with ia16-elf-gcc

The reason is uh, because you see, I did things.

The .asm came first and was copy pasta from the internet. The .s files came from the output of ia16-elf-gcc -S when I couldn't be bothered to write programs in assembly but still needed to make them compatible with BASIC's CALL instruction.

Also the wozmon binary contains special care to make it into a boot sector (0xaa55 magic).

Anyway, just type

make binaries

and stop whining.

Useful stuff

Description
No description provided
Readme 276 KiB
Languages
C++ 40.1%
C 29.4%
Assembly 21.8%
Python 4.6%
Makefile 3.5%
Other 0.6%