Doom on the Oldest Digital Computer in America! | Usagi Electric
#BendixG15
#FWakeOnTheHorn "Let's get Bill on the horn"
#FWakeVermont
#FWakeEmulator
#FWakeMusic /\
#FWakeMusicPlayback /\
#FWakeBendix #FWakeG15
#BendixG15 #FWakeSongs /\
Writing a custom music replay routine for #BendixG15 to play "At Doom's Gate": https://www.youtube.com/watch?v=no0CkQk7id0 (relevant bit starts around 6:40 or so)
This stuff immediately reminded me of The Story of Mel from The Jargon File: http://www.catb.org/jargon/html/story-of-mel.html (if you know this file you're officially an old fart)
People of the #Demoscene: You're always looking for challenging and interesting platforms. Here we have one... I'm expecting some "wild" wild compo entries. I think we have to resort to using the emulator here though.
#Bendix G-15 is playing music! https://youtu.be/-HibkocVn1U
I've been following Usagi Electric's Bendix G-15 saga since it began and I now love this 50s computer. Seems like it's working now!
Edit: I love that it has a bell ringing to indicate success, early beep codes!
Some random notes after glancing over the G15D programmer’s reference manual:
- Bendix G-15 doesn't use hex, but sex: The notation is 0-9 u-z (sexadecimal).
- Section 3.2.3 goes into details on how to optimize performance: You need to carefully plan the order of instructions and data on the drums for optimal speed. The most optimal code will overlay computation and memory accesses. This reminds me of "the story of Mel". The optimization tricks done don't differ much from handcrafting optimal assembly code on more modern systems where external memory accesses are very expensive vs computation within registers.
- The addressing notation directly addresses line on the drum and offset of the word on that line. There are 20 lines with 108 29-bit words on each. Arithmetic operations operate on a separate short "register" lines that circulate much faster than the actual memory (27x speed vs memory drum).
- Considering how slow it's to process individual memory loads / stores, it makes perfect sense that the system has block copy instructions.
- Each instruction has offset within the line to the next instructions to execute. That is, there's always an explicit jump encoded in each instruction. Conditional code execution occurs by suppressing the jump when condition is met, in which case the jump is not taken and next instruction is executed instead. In modern architectures you generally execute next instructions address and there are dedicated branch instructions.
- Code execution can happen from 7 long lines (0, 1, 2, 3, 4, 5, 19) and one short line (23). Some lines have reserved roles and offsets, at least when using the libraries provided by Bendix.
- As there is no built-in stack register or stack a return address for subroutine calls must be handled manually. This is reminiscent to link register on some later platforms (such as PowerPC). It of course is entirely possible to manually maintain a stack on some line, dedicating some fixed address as stack pointer. All code must then agree on this decided calling convention.
- Punched (paper) tape and magnetic tape is available for input, as well as typewriter (console). Output can be (IBM) punch cards, magnetic tape or typewriter (console). The typewriter also has some switches for control.
I love the introductory chapter in the Bendix G15 Programmer's Reference Manual - when computers were still fresh enough that you had to start from the very basic concepts.
http://www.bitsavers.org/pdf/bendix/g-15/G15D_Programmers_Ref_Man.pdf
[Usagi Electric’s] Bendix G15 Gets DC Power https://hackaday.com/2024/07/08/usagi-electrics-bendix-g15-gets-dc-power/ #Retrocomputing #usagielectric #vacuumtube #BendixG15 #Usagi #G15
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst