/tech/ - Technology and Computing

Technology, computing, and related topics (like anime)

I Fucked Up

Max message length: 6144

Drag files to upload or
click here to select them

Maximum 5 files / Maximum size: 20.00 MB

More

(used to delete files and postings)


Whatever happened to TempleOS? Anonymous 10/06/2019 (Sun) 00:03:16 No.421
Did those two faggots ever get a hold of it? I miss Terry.
>>421
What? TempleOS is public domain.
I guess no one has bothered picking up the development. But it's a cool piece of software, I wish I had a few days of free time to expriment with TOS and HolyC.
Open file (437.32 KB 480x270 QB_animated.gif)
>>421
Anon! I can grant you any wish, but in return, you must become a high priest and fight CIA niggers.
You can still download the iso from this link: https://archive.org/download/TempleOS_ISO_Archive/TempleOSCDV4.13.ISO
Do it like a white man!
Open file (54.45 KB 360x383 pls__rember.png)
Open file (38.77 KB 553x162 terry_tweet.png)
TempleOS Video Archive
* https://archive.org/details/TerryADavis_TempleOS_Archive
* https://ia600600.us.archive.org/31/items/TerryADavis_TempleOS_Archive/videos/
* There are also a few channels on YT (for example, NIST Oracle and Terry Davis Archive).


TempleOS ISO Archive
* https://archive.org/details/TempleOS_ISO_Archive
* https://archive.org/download/TempleOS_ISO_Archive
* Download version 4.13 because it has most programs (like After Egypt)
* Shrine (unofficial TOS distro) https://github.com/minexew/Shrine
* You must install TOS inside a VM; Use QEMU, VirtualBox or VMware. To get sound, your VM must support PC speaker. (Note that sound doesn't work with VirtualBox)
* TempleOS FAQ: https://web.archive.org/web/20161129044519/http://www.templeos.org/Wb/Doc/FAQ.html
* HolyC: https://web.archive.org/web/20170325000321/http://www.templeos.org/Wb/Doc/HolyC.html
* Compiler overview: https://web.archive.org/web/20170305045826/http://www.templeos.org/Wb/Doc/CompilerOverview.html
* Guidelines: https://web.archive.org/web/20170306232214/http://www.templeos.org/Wb/Doc/GuideLines.html
* Demands: https://web.archive.org/web/20170305045050/http://www.templeos.org/Wb/Doc/Demands.html


TempleOS

You can't do anything until you burn a TempleOS CD/DVD from the ISO file
and boot it, or you aim your virtual machine's CD/DVD at the ISO file
and boot.

TempleOS is 64-bit and will not run on 32-bit hardware.

TempleOS requires 512 Meg of RAM minimum and can have 256 Gig of RAM or more!

TempleOS files are compressed with a nonstandard LZW format and the source
code can only be compiled by the TempleOS compiler because it is HolyC, a
nonstandard C/C++ dialect. You must boot TempleOS. Then, you can compile it
because it is 100% open source and all source present on the distro.

If attempting to run on native hardware, TempleOS may require you to enter I/O
port addresses for the CD/DVD drive and the hard drive. In Windows, you can
find I/O port info in the Accessories/System Tools/System Info/Hardware
Resources/I/O ports. Look for and write down "IDE", "ATA" or "SATA" port numbers.
In Linux, use "lspci -v". Then, boot the TempleOS CD and try all combinations.
(Sorry, it's too difficult for TempleOS to figure-out port numbers, automatically.)
>>478
TempleOS Charter (abridged)

* TempleOS is God's official temple. Just like Solomon's temple, this is a
community focal point where offerings are made and God's oracle is consulted.

* God said 640x480 16 color graphics is a covenant like circumcision. Children
will do offerings. Think of 16 colors like the Simpson's cartoons. In the
future, even if one GPU were universal, we would keep 640x480 16 color and not
use GPU acceleration. Graphics operations should be transparent, not hidden in
a GPU.

* God said to use a single-voice 8-bit signed MIDI-like sample for sound. God
does not want death screams, perhaps, because God has PTSD or soldiers have
PTSD. (Imagine wounded on battlefields.)

* God said His temple must be perfect. We don't think twice about breaking
compatibility. God said we do a seven year release cycle. I say the PC
hardware follows a 49 year, jubilee cycle, like broadcast TV upgrades.

* The vision is the same usage model and niche as the Commodore 64 -- a
non-networked, simple machine where programming was the goal, not just a means
to an end. However, it is modern, 64-bit and multi-cored. It is special
purpose, not general purpose, so some things it will not do. Also, it's a
kayak, not a Titanic. The priority is user developers, not 3rd party developers.

* We do not put any hooks for future changes. "Perfect" means we always act as
though it is final, for all time. Microsoft allowed the Windows BMP file format
to adapt to the future and it became grotesque.

* Low line count is the highest good, so it is easy to learn the whole thing.
Users should see the light at the end of the tunnel. One file system, for
example, is better than many file systems.

* There is a limit of 100,000 lines of code for all time, not including
applications and demos. Code comments count, however. Currently, there are
81,502 lines of code. 3rd party libraries are banned because they circumvent
the intent of this limit. The vision is a Commodore 64 ROM -- a fixed core API
that is the only dependency of applications. Dependency on components and
libraries creates a hell that is no longer blissful.

* Minimal abstraction is a goal. Sheep are fools. They always respect a design
that is more complicated than another. Any genius can make it complicated.
Like in physics, it takes a supra-genius to make it simple.

* One platform. x86_64 PC compatibles. Desk-tops are all we design for, but
laptops can tag along.

* All hardware access will be done through x86 IN/OUT instructions, not PCI
drivers. A frame buffer for VGA is an exception.

* One driver for each class of device. Limited exceptions are allowed. With
divergent device capabilities, it is a nightmare for user applications and what
is gained? A three bttn mouse is like a leg you cannot put weight on.

* Ring-0-only. Everything runs in kernel mode, including user applications.

* Full access to everything. All memory, I/O ports, instructions, and similar
things must never be off limits. All functions, variables and class members
will be accessible. There are no C++ public/private protections and all
functions, even secondary ones in the kernel, can be called.

* Single-address-map as though paging is not used. Long mode requires paging,
however, so the nearest thing is keeping all memory identity-mapped.

* No networking, so malware is not an issue.

* No encryption or passwords. Files are compressed, not encrypted.

* Free and public domain.

* 100% open source with all source included.

* Documents are not for printing. They're dynamic, intended for the scrn.

* Just one 8x8 fixed-width font. No Unicode, just Extended ASCII. Other
countries can make their own versions. The versions should be just for one
language and platform.

* No multimedia. Sounds and images will be primarily calculated in real-time,
not fetched from storage.


* "Commodore 64" is a trademark owned by Polabe Holding NV.
* "The Simpso
>>478
Thanks anon for the links. That archive.org repo must be nearly exhaustive.

Report/Delete/Moderation Forms
Delete
Report