| LoseThos Free Open-Source PC Operating System |
||||||||||||||||
| You used to buy a computer to program. They didn't do much else. LoseThos is intended for hobbiest programmers. A working knowledge of C programming is required. It more or less runs on least common denominator PC hardware without networking or the Internet. It is retro in some respects, having no security. As a programmer, I like having full access to my machine -- being able to turn-off interrupts or do direct disk block access. It is highly textual, so things can be scripted. It boots fast, and you can power-off whenever you feel like, but just don't do it during disk writes. |
||||||||||||||||
![]() |
||||||||||||||||
| I've made changes to the syntax of the language and used practically no standard formats. My critics point this out. However, what's the point of doing an inferior imitation of something that exists? No one needs another UNIX! I've given myself a clean slate and chosen a niche. This operating system is not for multi-user applications where crashing is a serious issue. (Mine reboots in a few seconds. No big deal for a single user system.) It's not for where privacy is an issue. It is however for everything else, including the whole friggin home computer market, or at least hobbiests! Features:
Downloads:
Supported Hardware:
Hardware Not Supported:
|
||||||||||||||||
![]() |
||||||||||||||||
| The command line is like being in an editor. LoseThos' document format supports graphics, so you can send graphics or file-links to the command line. The graphics in documents (CTRL-R) are more or less vector graphics, as opposed to bitmap. That is, it stores coordinates of the end points of lines, etc instead of whole images. Potentially, it could facilitate resolution independence, but higher-resolutions and more colors would take too much CPU under the current scheme. The document file format includes ASCII followed by binary data. Graphics are placed in the binary portion after the ASCII portion. They are referenced by ASCII commands indicated by '$' characters. An advantage of this approach is that file text searches (Grep) work. |
||||||||||||||||
![]() |
||||||||||||||||
| LoseThos is designed for programmers. The task (process) ID is shown in the title bar of each window. At the top of the screen, the "wallpaper" shows the date, the rate video memory is being updated by the CPU and free memory. (Refresh is not the hardware rate of the monitor.) The refresh rate is scaled-back when the CPU is busy. You can customize the wall-paper code to display whatever you want. The routine is in the /LT/ADAM/WINDOWS.CPZ file and is not part of the "kernel". It gets recompiled automatically when you reboot. In fact, almost everything in /LT/ADAM and /LT/UTILS gets recompiled every boot. (Still boots in a couple seconds.) Below, you can see the WordStat window showing suggestions for the word under the cursor. |
||||||||||||||||
![]() |
||||||||||||||||
![]() |
||||||||||||||||
| In the following, a class is defined at the command line. Since LoseThos is intended for programmers, the compiler retains information that assists in debugging. For the most part, there is no difference between typing at the command line and #including a script. The command line can be used for debugging. A function, ClassRep(), displays members of a class/struct. All commands usable at the command line can be incorporated into your programs, so you could call ClassRep() from within a program. You can even use ExecuteString("") to compile and run text from within a program. |
||||||||||||||||
![]() |
||||||||||||||||
| The LoseThos compiler will allow running code at compile time and inserting text into the code stream of the program being compiled. This is very flexible and eliminates the need for lots of compiler directives and the #defines normally used to change builds. Code placed in an exe {} block is run at compile time and any ExePrintf() statements will output text into the code stream following the conclusion of the exe{} block. |
||||||||||||||||
![]() |
||||||||||||||||
In depth discussions
Contact:
|
||||||||||||||||