Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Volume label creation issues if label is named like existing file or directory #190

Open
boeckmann opened this issue Oct 12, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@boeckmann
Copy link
Contributor

Under MS-DOS it is perfectly fine to create a volume label with the same name as an exiting file or directory within the root directory. This works with Microsoft LABEL and also with the FreeDOS LABEL running under the MS-DOS kernel.

Under the FreeDOS kernel however, the directory entry of an existing file is replaced when a label with the same name is created. I verified by inspecting the root directory sectors that the directory entry for the ordinary file is indeed gone. I have not yet inspected the FAT if there are orphaned clusters.

The kernel IS capable of reading a file with the same name as the volume label, provided that it was previously created correctly under MS-DOS.

Further, label creation fails if a directory with the same name is already there, with the effect that the previous label (if one was there) is deleted. The latter is not a kernel issue as the LABEL command most probably deletes the old label before trying to create a new one.

I further noticed that MS-DOS does not set a creation timestamp for labels:
Bildschirmfoto 2024-10-12 um 21 24 09

But FreeDOS does so (bytes 0x10E-0x111):
Bildschirmfoto 2024-10-12 um 21 22 44

But I guess this is ok, I document it only for the sake of completeness.

@boeckmann boeckmann added the bug Something isn't working label Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant