SpartaDOS 3.2x bug reports:››Directory entries opened for write and never closed››Whenever a file is opened and never closed it will appear in your directory listing with a zero byte count. Not all files with a zero byte count are opened files. But how can you tell? You probably don't have a program that will let you know.››All you need to know is that you do not want to delete this file using SpartaDOS's delete (erase) command. Just run Cleanup on the disk whenever you suspect that a file was opened and never closed. Cleanup will restore the sector count properly. If you just delete the file, the sector count on that disk will not be updated!››SpartaDOS X users do not have this problem. The DIR command of SpartaDOS X will not display these files. So you don't know they exist and will not be tempted to delete them.››If you want to experience this bug for yourself, just do the following:››Format a new disk›Enter BASIC›Type: open #1,8,0,"Dn:opened" (n = drive number)›Now hit the reset key›This file will not be closed››Delete this file and then use Cleanup. You will notice that Cleanup has not corrected the error.››Do the above again. But this time do not erase the file. Then run Cleanup. Cleanup should now correct the problem.›››SpartaDOS 3.2f and SpartaDOS X (up to 4.21?) UnErase command bug››SpartaDOS's UnErase command has two major bugs that I know of.››Whenever you open a directory for read and update, you cannot read past the end of the directory's length with the input command. This will actually increase the byte count of the directory the length of the bytes you are reading. If you tried to read 23 bytes the directory length will be incremented 23 bytes. But the directory will not be properly updated. Luckily you can then use Cleanup to correct the problem.››What program will contain such a bug? You guesed it! UnErase.››To experience this bug for yourself. Delete a file. Then immediately UnErase the file. Then use Cleanup on this disk. It should report an incorrect directory length error.››The other bug in UnErase is when you use it on disks with two or more bitmaps. When you unerase a file which occupies sectors that cross over bitmaps. The sectors which cross over to the next bitmap will not be marked (set) by UnErase as in use in. When you copy another file to this disk, DOS might allocate these sectors to the new file because they appear in the bitmap as unused sectors. Overwriting the sectors of the file you unerased. This will then create another problem known as cross-linked files. Files which claim the same sectors on the disk.››How to cure these bugs?››Easy, use Cleanup when you suspect that a zero length file on your disk or hard-drive partition might not have been closed and after you unerase, at least until I finish vUnErase.›