Wip

Author: intoinside

E000.md

@@ -25,7 +25,7 @@ Routine needs parameter to be set:
 
 If the specified drive is not present or turned off, or the disk does not contain valid boot sectors, the routine will return carry bit set.
 
-BOOT_CALL routine at [$F890](#F890) which attempts to load and execute the boot sector from an auto-boot disk in the given drive and device. The BOOT protocol is as follows:
+BOOT_CALL routine at [$F890](#F890) attempts to load and execute the boot sector from an auto-boot disk in the given drive and device. The BOOT protocol is as follows:
 
 * Close all open files on boot device.
 * Read track 1 sector 0 into TBUFFR ($B00).
@@ -51,14 +51,14 @@ The following examples illustrate the flexibility of this layout. This loads and
 <pre>
 $00 -> "CBM"
 $03 -> $00, $00, $00, $00 // no other BOOT sector
-$07 -> "NAME",$00         // message "NAME"
-$0C -> $00                // no filename
+$07 -> "NAME",$00         // message "NAME" (+ terminator A)
+$0C -> $00                // no filename (only terminator B)
 $0D ->                    // code
   $A2, $13,               // LDX #$13
   $A0, $0B,               // LDY #$0B
   $4C, $A5, $AF           // JMP $AFA5 (J_EXECUTE_A_LINE)
-$14 -> RUN"PROGRAM"       // data (BASIC statement)
-$20 -> $00
+$14 -> RUN"PROGRAM"       // BASIC statement
+$20 -> $00                // empty code (C)
 </pre>
 
 This results in the message Booting NAME... being displayed and, utilizing a C128 BASIC jump table entry that finds and executes a BASIC statement, loads and runs the BASIC program named "PROGRAM". The same header can be used to load and execute a binary (machine code) program by simply changing RUN to BOOT.
@@ -68,9 +68,9 @@ While the file auto-load feature of the boot header could be used to load binary
 <pre>
 $00 -> "CBM"
 $03 -> $00, $00, $00, $00   // no other BOOT sector
-$07 -> $00                  // no message
-$0C -> $00                  // no filename
-$0D ->                      // code
+$07 -> $00                  // no message (only terminator A)
+$08 -> $00                  // no filename (only terminator B)
+$09 ->                      // code (C)
   $20, $7D, $FF,            // JSR $FF7D (JPRIMM)
   $0D, $53, $45, $4C, $45,  // String start
   $43, $54, $20, $4D, $4F,
@@ -92,13 +92,13 @@ $0D ->                      // code
   $EB, $4C, $00, $B0
 </pre>
 
-Starting from $0D, the first three bytes stands for
+Starting from $09, the first three bytes stands for
 
 <pre>
 JSR $FF7D
 </pre>
 
-which is a jump to $FF7D (JPRIMM). It prints on screen the
+which is a jump to [$FF7D](E000#FF7C) (JPRIMM). It prints on screen the
 string of character codes immediately following the JSR.
 
 So, the code above shows this message and waits for a key press:

index.md

@@ -20,6 +20,7 @@ All references have been eliminated and are being reviewed to verify that the us
 
 ### Memory reference
 
+* [$0000-$00FF - Zero Page](0000) (WIP)
 * [$E000-$FFFF - Kernal Rom, Standard Commodore Jump Table](E000) (WIP)
 
 Most references have been eliminated and are being reviewed to verify that the user license complies with the proposed contents. The contents will gradually be reinserted after the necessary checks.
@@ -50,3 +51,5 @@ An article from Marko Mäkelä about Vic2 (and Vic2e) memory access
 
 * [The MOS 6567/6569 video controller (VIC-II) and its application in the Commodore 64](https://ist.uwaterloo.ca/~schepers/MJK/ascii/VIC-Article.txt)
 An article from Christian Bauer about Vic2
+
+* [unusedinode](http://unusedino.de/ec64/technical.html) some tech info about C64