User Tools

Site Tools


kernal_call_manual

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
kernal_call_manual [2017/07/03 19:37]
z00m [File System Related Calls]
kernal_call_manual [2017/07/03 19:41] (current)
z00m [File System Related Calls]
Line 409: Line 409:
   * none   * none
  
-//Note:// Use after "​kjt_open_file"​ (if required)\\+//Note:// Use after "[[kernal_call_manual#​kjt_open_file]]" (if required)\\
 \\ \\
 ---- ----
Line 423: Line 423:
   * none   * none
  
-//Note:// Use after kjt_find_file (if desired)\\+//Note:// Use after [[kernal_call_manual#​kjt_find_file]] (if desired)\\
 \\ \\
 ---- ----
Line 440: Line 440:
 //Notes// //Notes//
  
-  * "​kjt_open_file"​ MUST be called first before using this routine.+  * "[[kernal_call_manual#​kjt_open_file]]" MUST be called first before using this routine.
   * Whenever a disk file transfer reaches address $FFFF, it wraps around to $8000 and continues onto the next bank.    * Whenever a disk file transfer reaches address $FFFF, it wraps around to $8000 and continues onto the next bank. 
 \\ \\
Line 641: Line 641:
 |$13 byte|fs_z80_bank| |$13 byte|fs_z80_bank|
  
-//Note:// When restoring altered data, the first byte "​fs_filepointer_valid"​ should always be cleared. This causes the read operations to cleanly ​ seek from the beginning of files when file transfer (re)commences. ​ (Access will be noticably ​slower than a single continuous load.)\\+//Note:// When restoring altered data, the first byte "​fs_filepointer_valid"​ should always be cleared. This causes the read operations to cleanly ​ seek from the beginning of files when file transfer (re)commences. ​ (Access will be noticeably ​slower than a single continuous load.)\\
 \\ \\
 ---- ----
kernal_call_manual.txt ยท Last modified: 2017/07/03 19:41 by z00m