argh ! I think this is a bug that will possibly cause a problem, the basic program CheckFs (checkFs.bas)
this program is used to check if the filing system and set B%=TRUE for ADFS/NFS or B%=FALSE for DFS
B% is tested in other programs to set the required strings to unlock and lock files using "WR" and "LR" for ADFS/NFS or "" and "L" for DFS
but I was thinking that CheckFs will fail if the filing system is not DFS and the disk is write protected which will cause a write protected error and incorrectly set B% to FALSE which will later cause nasty error messages in the other programs (menu.bas, reset.bas, editor.bas)
Should I fix this bug ? and if so how ?
Is there a better way to test for DFS (supporting only L attribute) or other filing systems (supporting LR and WR attributes) that will also work with a write protected disk ?
Code:
ON ERROR B%=FALSE:CHAIN "Menu"OSCLI("ACCESS Menu LR"):B%=TRUE:CHAIN "Menu"B% is tested in other programs to set the required strings to unlock and lock files using "WR" and "LR" for ADFS/NFS or "" and "L" for DFS
but I was thinking that CheckFs will fail if the filing system is not DFS and the disk is write protected which will cause a write protected error and incorrectly set B% to FALSE which will later cause nasty error messages in the other programs (menu.bas, reset.bas, editor.bas)
Should I fix this bug ? and if so how ?
Is there a better way to test for DFS (supporting only L attribute) or other filing systems (supporting LR and WR attributes) that will also work with a write protected disk ?
Statistics: Posted by lovebug — Sun Jan 12, 2025 5:23 pm