Krill's Loader, Repository Version 164 
Look for downloads on external sites:
Submitted by Krill on 28 August 2018
|Not an actual goof, but nota bene (recently added to the readme):|
TL;DR: Make sure the final directory block's first two bytes are 00 ff.
"The final directory block must begin with 00 ff. Some custom disk image creation tools produce an erroneous final directory block, such that its first bytes are 00 00. This is an invalid block length, and the loader rejects blocks with invalid track/sector links or block sizes. In the case of an invalid directory block, the loader keeps retrying to read it, effectively locking up."
(Apparently, ancient versions of cc1541 have this bug as well, but a quick test suggested they are older than the one shipped with the previous public release https://csdb.dk/release/?id=118713.)
Submitted by Krill on 27 August 2018
|Another bug that will be fixed with the upcoming patch release.|
After a file could not be found, the loader returns with carry set and accu = $fe (diskio::status::FILE_NOT_FOUND), but any subsequent load will fail and do the same, file existing or not.
--- loader/src/drives/drivecode-common.inc (revision 164)
+++ loader/src/drives/drivecode-common.inc (working copy)
@@ -267,7 +267,7 @@
; the disk was not changed, or the dir has just been read
samedisk: ldx NUMFILES; must not be 0
- beq invaliddir
+ beq nextdirseg
.if (.not .xmatch (drivetype, 1581))
Submitted by Krill on 16 August 2018
|A bug has sneaked in to the Bitnax decruncher:|
bitfire_lz_sector_ptr2 = * + 1 ;Copy the literal data, forward or overlap is getting a pain in the ass.
clc <----- add this
.lz_lcopy_len = * + 1
Will be fixed with an upcoming patch release (and the resident code be back to $0280 bytes).
· Goofs (3)|
· Hidden Parts