the Opening arguments

Operating system (OS) principals

What is "Project Dinkit" It's a new OS. No, not really. It's educational? No, not really. It's about an OS making it your way? No, Not really.

Is Dinkit a lot of "POO"? YES!
What is POO?
1. "Practical Order of Operation"
2. "Procedure Order of Operation"
3. "Proper Order of Operation"
4. "Proposed Order of operation"
Pick one they are all correct.
What is "POO"... It is the Entire "Dinkit Project".

Below is the first of one POO concept. It is called the "package". Learn how the package is stacked together and you will have learned how all of the 50 or so other Dinkit packages go together. There will be three intro packages, then the rest of the packages will be called "System_disk01" to "System_Disk50" or to how many total System_disk that there will be. The point is, learn this one POO concept and you are good to go for the next 50 or so packages. Now your concentration can be directed towards the more technical things inside each package. To ease the work of explaining the more technical parts of an OS, the workings of the OS is also placed on a POO list of is own. SO you, in a sense, have a POO list with in a POO list. In this approach you learn a building block one time and then use the hell out of it with out exception, deviation, variation, and changes in that block. This concept goes against the grain of some of the founders like "Intel", "IBM" and "Microsoft" in the making of "MS-DOS and Windows" with the unending variations, non-standards, and unorganized ways. Make no mistake I would not have done any better in writing an OS back in 1979. Nether they nor I would of had a P0O list to go by. So I will use what is here now and learning what to do and what not to do. At or near the end of the Dinkit project you will have a cute little working 12k-Dos-like OS . Not interested in the little 12k Dos toy? What if it could be the foundation for a much larger OS system with a mouse, graphic and all that good stuff, with little or no changes to the basics build blocks. If not I guess I have lost my argument, you are free to go.

The Do_me_first Package

Making dink_ttty

What is Dink_tty. It is a Wimpy typewriter like program? It cam be striped down to about 80 bites of code and can run out of Dos or a boot-sector. None of the Dink_tty code will be used in any Dinkit project, because the object of this project is not to learn Dink_tty, but to learn how to setup the procedures for all of the other 50 or so "Dinkit system disk".
Windows knows nothing about the Dinkit Operating system. It can't read any of the files on a Dinkit disk. In fact Windows can't even see the file names. It just sees a bunch of gobbuly Gook. What is needed is a mediator. There are thousands of projects out there that could use this basic concept

Download dink_tty
Go to the downloads page and click on the “Do_me_first” link