<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="generator" content="TempleOS V5.03">
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="/style/templeos.css">
<script src="/script/templeos.js"></script>
<style type="text/css">
.cF0{color:#000000;background-color:#ffffff;}
.cF1{color:#0000aa;background-color:#ffffff;}
.cF2{color:#00aa00;background-color:#ffffff;}
.cF3{color:#00aaaa;background-color:#ffffff;}
.cF4{color:#aa0000;background-color:#ffffff;}
.cF5{color:#aa00aa;background-color:#ffffff;}
.cF6{color:#aa5500;background-color:#ffffff;}
.cF7{color:#aaaaaa;background-color:#ffffff;}
.cF8{color:#555555;background-color:#ffffff;}
.cF9{color:#5555ff;background-color:#ffffff;}
.cFA{color:#55ff55;background-color:#ffffff;}
.cFB{color:#55ffff;background-color:#ffffff;}
.cFC{color:#ff5555;background-color:#ffffff;}
.cFD{color:#ff55ff;background-color:#ffffff;}
.cFE{color:#ffff55;background-color:#ffffff;}
.cFF{color:#ffffff;background-color:#ffffff;}
</style>
</head>
<body>
<pre id="content">
<a name="l1"></a><span class=cF5> RedSea Reliability</span><span class=cF0>
<a name="l2"></a>
<a name="l3"></a>TempleOS is like the 1040EZ tax form compared to the full 1040 form. Obviously,
<a name="l4"></a>it is simpler. If you allow mission creep, pretty soon the 1040EZ looks just
<a name="l5"></a>like the 1040 and the messed-up 1040EZ has no purpose.
<a name="l6"></a>
<a name="l7"></a>The Commodore 64 had a file system that was simple enough for peers in my
<a name="l8"></a>generation to enjoy the thrill of knowing exactly what is going on at the
<a name="l9"></a>hardware level and writing fun projects to access it.
<a name="l10"></a>
<a name="l11"></a>My primary design criteria is simplicity. If it is simple enough for only
<a name="l12"></a>100,000 people to learn, lets try to make it simpler so that 1 million can learn
<a name="l13"></a>it.
<a name="l14"></a>
<a name="l15"></a>Obviously, we don't do bad block tables, or redundant FATs.
<a name="l16"></a>
<a name="l17"></a>We use the simplest possible technique, a contiguous-file-only allocation
<a name="l18"></a>bitmap, not </span><a href="/Wb/Doc/BlkChain.DD.HTML#l1"><span class=cF4>Block Chains</span></a><span class=cF0> or FAT tables.
<a name="l19"></a>
<a name="l20"></a>You can be a good toy or you can be a good professional tool, but not both.
<a name="l21"></a>TempleOS's file manager will start too slowly once a few thousand files exist
<a name="l22"></a>because the file manager makes a list of all files on start-up.
<a name="l23"></a>
<a name="l24"></a>Do not have more than a few thousand files or the file manager will not
<a name="l25"></a>function.
<a name="l26"></a>
<a name="l27"></a>You are encouraged to keep your entire drive limited to, maybe, 100 Meg of files
<a name="l28"></a>because you are suppoosed to operate as a kayak instead of a Titanic. If you do
<a name="l29"></a>this, backing-up will be only a minute or so and you should do it at least once
<a name="l30"></a>a day.
<a name="l31"></a>
<a name="l32"></a>Third party software should be run from ISO files or CD/DVDs directly, without
<a name="l33"></a>installing to hard drive.
<a name="l34"></a>
<a name="l35"></a>Multimedia graphics and sound is, basically, forbidden. If you ignore this, all
<a name="l36"></a>hell will break loose because memory will fragment with large files and the
<a name="l37"></a>original vision of kayak hard-drive back-ups won't work.
<a name="l38"></a>
<a name="l39"></a></span><span class=cF8>
<a name="l40"></a>* "Commodore 64" is a trademark owned by Polabe Holding NV.
</span></pre></body>
</html>