Better read_error: show Fault() generated error message on KS 2.0+
Cleaned up to always keep pr_CurrentDir consistent and pointing to a valid dos lock. Before the code would first UnLock() and then CurrentDir() to a new lock. While this kind of works, it might choke things that peek process list and resolve pr_CurrentDir.
Fixed a problem where filenames exactly MAX_FILE_NAME_LENGTH would lead to non-0-terminated strings. Now pt1210_file_gen_file_list also rejects exactly MAX_FILE_NAME_LENGTH char names to stay safe. I didn't increase MAX_FILE_NAME_LENGTH itself to avoid breaking cache compatibility (this is likely what we should do, but that would require bumping version, too).
Better read_error: show
Fault()
generated error message on KS 2.0+Cleaned up to always keep
pr_CurrentDir
consistent and pointing to a valid dos lock. Before the code would firstUnLock()
and thenCurrentDir()
to a new lock. While this kind of works, it might choke things that peek process list and resolvepr_CurrentDir
.Fixed a problem where filenames exactly
MAX_FILE_NAME_LENGTH
would lead to non-0-terminated strings. Nowpt1210_file_gen_file_list
also rejects exactlyMAX_FILE_NAME_LENGTH
char names to stay safe. I didn't increaseMAX_FILE_NAME_LENGTH
itself to avoid breaking cache compatibility (this is likely what we should do, but that would require bumping version, too).