Organized files and expanded notes

notes.org

@@ -51,3 +51,43 @@ This repository contains a hex compiler written for Linux in hex and assembly as
 well as a platform independent C implementation.
 Then to complete the build process write to the master boot record of a floppy disk.
 Or should you desire simply use qemu to boot the compiled file directly.
+* Creation journal
+** Linux bootstrap
+The initial prototyping was done on linux with the goal of not
+requiring anything other than the linux kernel.
+However it was pointed out to me that should a trusting trust attack be in the compiled kernel,
+there would be no way to even trust the binaries produced by these programs.
+That being said they may be of some use to you.
+
+** Stage 0
+Lacking a good basis for reducing the trusting trust attack, it was decided to reduce the scope down.
+By writing the stage 0 code in commented hex, it becomes possible for universal cross compilation and verification.
+The only real problem is that the commented hex has to be manually validated [An insanely painful process] and
+each and every single platform has to perform the exact same tasks.
+Since all such projects have to start somewhere, I have choosen to do it myself and with the 8088.
+
+To make my work easier, I first created the working code in 16bit assembly. Then after testing is validated,
+I begin the pain staking process of manually converting the code to hex [With usually a dozen bugs along the way].
+
+What I however require is someone with a completely alien platform verify the compiled hex for the stage0_monitor.
+Which has the following checksum values:
+md5: 9e29544f0220636437741cb5092cc411
+sha1: b26c72762d2f77d8634cb532d581c1e76adceb3f
+sha256: 045ef96e1c8fb011cba89f268f823c06b21f91270fb9afb0af42a1ac8c3ee44b
+
+If your compiled hex is different in any way, please let me know as the process should produce bit idential binaries.
+
+** Stage 1
+Stage 1 attempts to save myself from alot of manual typing and the inevitable errors that occur.
+It simply provides the functionality required to produce 32KB or smaller binaries from Commented Hex files.
+This is a minor stopping point of functionality that provides a stable nub for our much more ambitious stages that come later.
+
+The editors lack the ability to correct mistakes and always writes a 64KB file onto the B: floppy.
+The loader is so stupid is only loads 64KB from the A: Floppy and doesn't even prompt the user.
+
+However despite those stupid limitations, they have saved alot of manual work compared to stage0.
+Having these binaries are a huge step forward compared to not having them but they assume you don't make mistakes.
+
+** Stage 2
+Stage 2 will be introducing enhancements to Stage 1 programs that allow you to fix the problems you accidentially introduce.
+We will also begin to introduce programs that make software development alot easier.