Holy-Days experiments 🌊 🌴 🌞 (Installing TempleOS/Holy-C on VirtualBox)

This post is mostly instructions on how to install the Temple OS on Debian using VirtualBox. Temple OS is an operating system written from scratch by Terry A. Davis in order to make programming and the creation of games more fun. Its shell is a Holy-C compiler where users can write commands in Holy-C and see the generated assembly. Temple OS lacks networking and security. Every program runs in ring-0 mode, which means that it has full access to the hardware. This is on purpose, “because it’s fun”. As Terry said, he didn’t want to write another UNIX and his goal was to create a modern Commodore64-like OS where the users can start writing code immediately after boot. If you are not familiar with the Temple OS and Terry A. Davis’s story, you can check the links at the end of this post.

Let’s see the steps to install the Temple OS on Debian using Virtualbox:


Step 1: VirtualBox installation

The host is Debian:

Optionally install the extension pack from here: https://www.virtualbox.org/wiki/Downloads

Step 2: Temple OS installation on VirtualBox

First, download the TempleOS iso from here:


Then, on VirtualBox, create a virtual machine selecting “Other 64-bit” OS type and reserve at least 512 MB of RAM.


Then create the VDI as you like and start the VM having the TempleOS.ISO mounted, and you must see the following screen:

Press y to install the TempleOS, and when the installation is done eject the TempleOS.ISO and restart the vm.

Step 3: PC speaker passthrough

When you boot the vm with the installed TempleOS, you might want to test the “songs” and the music. TempleOS plays music using the pc speaker which cannot be accessed by default from VirtualBox.

Supposing that:

  • the pc you run the host OS has a pc speaker
  • you are using the ALSA sound architecture
  • the pcspkr kernel module is loaded (lsmod to check, modprobe pcspkr to load it, also check the module is not blacklisted)

you can do the following:

1. Unmute the speaker if it’s muted (I usually have it muted by calling xset b 0 automatically when I start X). The easiest way is through alsamixer: run it, press F6 to select device and select the HDA Intel PCH (I haven’t tested it with other devices), press enter, move with the arrows until you find the Beep column, if it’s muted (MM) press M to unmute and ESC to exit:


2. Then, check that the pc speaker works on the host:


3. If you can’t hear any sound check if your user has permissions to use the pc speaker. The pc speaker is listed under the /dev/input directory on Debian (/dev/input/by-path/platform-pcspkr-event-spkr) where only root and the input group users have permissions and so, you should add your user to the input group (adduser $USER input) to be able to play sound from it.

4. Edit the virtual machine settings to be:

5. Pass through the pc speaker to the host:

where TempleOS is the name of the vm, and 1 is for /dev/input/by-path/platform-pcspkr-event-spkr according to the VirtualBox documentation.

6. Test the sound by playing a “song” by pressing F6 πŸ™‚

Step 4: Playing with the OS

Closing this post, here’s a list of interesting things to do with Temple OS:

  • Write Holy-C commands on the shell and disassemble them.
  • Use the editor: it is not just a text editor, it can edit any object (graphics objects for example).
  • Play the games and modify them to do something different.
  • Read the endless documentation about everything that is everywhere: almost every word you select is a link to something.
  • Pack words inside the character literals just because you can! (Each character literal is a full 64bit integer number, and so each character can store 8 bytes). “7-bit signed ASCII is retarded!”
  • Try to compose music using the app for it.
  • Check out the “God” generated messages and songs and try to make sense… just kidding πŸ™‚ although I found it fun to play with the random numbers generator.
  • Explore! πŸ™ƒ

Don’t forget to enable redshift or something similar and reduce the brightness to 0… :p (I really loved the OS but these colors/fonts made my eyes bleed… 😡😎)

Playing games on TempleOS (when we ran it without installing it in our tv-pc):

Out of scope of this post, something I was thinking after I watched the “Down the rabbit hole” documentary on Temple OS:

That image I used at the top was made by Terry A. Davis using a 16 color palette:

Terry wrote in public that this elephant was pleasant to create and after I’ve seen his editor and the way he creates graphics, I suppose that it must really have been so. What is really weird though, is that people thought that he was delusional and he was believing that his drawing was superior than the 16777216 color graphics. Even in the documentary about him, it was mentioned that because he was schizophrenic he believed that his elephant was better than a 16777216 color elephant! I really can’t see how people can misunderstand this phrase so much! Just try to create an elephant 3D object with thousands of polygons in a 16777216 color system and then ray trace it and you will see what he meant. A 16-color palette elephant really is more easy and more pleasant to create! He said to create, not to watch! 🐘🐘🐘

playing with the elephant demo πŸ™‚

And here are some screenshots from the TempleOS editor where someone can mix and edit objects, plots, source code and text (personally, I loved the concept in the context of an OS that is written to make programming fun! I don’t know if it would be easy to use in another OS, and for other purposes though):


Something that is not very obvious in the screenshots is that most of the 3D objects are also animated. But anyway, just follow the instructions, install the TempleOS and explore yourselves the Demos!

More info on Temple OS can be found in the links below:

The End!

5 thoughts on “Holy-Days experiments 🌊 🌴 🌞 (Installing TempleOS/Holy-C on VirtualBox)”

  1. Have you tried using it as a oracle with the helper’s menu inside? I think you’ll find it really interesting to post about, and very enlightening to see! Really great, actually. That’s what Terry wanted people to look into with a listening mind so they may talk to their Lord. God Bless. Amen. Hope you’ll try it, and see! With love for The Word. Love and go!

  2. I was the guy who explained why 7bit signed ascii is retarded. Why was I so angry when I wrote that haha. I cleaned up some of the cursing so its not so vulgar(and to prove im not lying). I wrote an introduction to Terrys compiler and assembler based on his videos and the code https://spellsoftruth.blog/2019/11/15/gospel-of-terry/
    Check It Out!

    Also your instructions for how to add sound to a virtual box version of TempleOS was the closest Ive gotten to actually getting the darn sound to work on Virtual Box. I got stuck on the alsa mixer part because mine didn’t show a ‘Beep’ column. I remember him having a video explaining how to add .bmp files but I forget how he transferred it to the TempleOS harddrive. Any ideas on how to do that?

    1. Hmm, I am not sure why you can’t see a “beep” column, I’d check if my PC/laptop has a PC speaker (modern hardware doesn’t always have) and if I’ve selected the correct sound card (Press F6 to select between cards and other hardware seen as sound cards) as well as my general alsa configuration. I don’t remember having seen the video with the .bmp file. According to the Temple OS documentation the OS supports the Red Sea and FAT32 filesystems. You could try to mount a FAT32 device on Linux with some .bmp files inside and then create an auto-mounted shared folder on VirtualBox (using the Linux path to the FAT32 bmp directory) to see if you can read the images. I might try this myself to see if it works. I’ve never tried to exchange files TBH πŸ™‚

Leave a Reply

Your email address will not be published. Required fields are marked *