Go to file
2025-09-14 15:35:43 +02:00
crc16.c Initial commit: try make binaries 2025-09-14 15:34:16 +02:00
crt0.c Initial commit: try make binaries 2025-09-14 15:34:16 +02:00
Dockerfile Initial commit: try make binaries 2025-09-14 15:34:16 +02:00
Makefile Initial commit: try make binaries 2025-09-14 15:34:16 +02:00
readfloppy.asm Initial commit: try make binaries 2025-09-14 15:34:16 +02:00
README.md Initial commit: try make binaries 2025-09-14 15:34:16 +02:00
wozmon.cc Initial commit: try make binaries 2025-09-14 15:34:16 +02:00
wozmon.s wozmon: make it fit the boot sector 2025-09-14 15:35:43 +02:00
writefloppy.asm Initial commit: try make binaries 2025-09-14 15:34:16 +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 ia14-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).