The prose description ("update body_syms.inc from body_syms_new.txt,
without DATA/CONF") wasn't clear on its own -- replaced with the
actual grep command and a short explanation of why DATA/CONF get
stripped (zc_sd_driver.asm already declares them itself).
zc_sd_driver.asm INCLUDEs it directly; without it the repo isn't
buildable from a fresh clone. Generated from zc_sd_driver_body.asm's
own --sym dump (DATA/CONF stripped, see _sd/README.md's build steps).
sv512_advance/lv512_advance hardcoded the post-wrap offset to exactly
#4000, discarding whatever the add overshot #8000 by. Invisible for
page-aligned transfers, but create_filename's ".EXT"-marker handling
(strips a leading 4-byte ".TRD"/".SCL"/etc marker some archive
downloads carry) starts thread.adress a few bytes past #4000, so the
reset silently dropped that offset on the first page wrap only,
splicing 4 stray bytes into the saved file and losing its real last 4
bytes. Fixed by subtracting #40 from H instead of resetting it (CP
doesn't touch A, so this costs zero extra bytes). Confirmed via a
direct RAM-vs-disk MD5 comparison on a 640KB, 40-page-boundary
download: byte-for-byte identical after the fix.
Renamed as zc_sd_driver.asm/zc_sd_driver_body.asm (no relation to Wild
Commander). Fixes a stale-IX bug where core_mkfile's filter_name_to_83
left IX pointing into driver memory instead of restoring it, causing
zifi.asm's save_downloaded_file to read the wrong page/address for
every SAVE512 call after MKFILE. All CORE dispatch entry points now
preserve IX across the call. Also fixes a body/#2000 jump-table
overlap, sdbuf DMA word-alignment, and a load_ram_page staleness race
in zifi.asm's own download bookkeeping.
alex