-
Notifications
You must be signed in to change notification settings - Fork 201
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
Write protection option in eject menu doesn't persist #516
Comments
You are correct it is a soft setting which does not get saved to the usb drive. I never thought about doing that. Perhaps it makes more sense. |
Indeed, the current behavior might be confusing. I spent some time trying to understand why the write protection "disappeared", e.g. thought there's something wrong with my USB stick ;-) Maybe, if you don't want to change read-only attributes on the USB drive, it could make more sense to call the option "temporary write protection", or something like that... |
I case changing the ADFs attributes isn't possible or desirable, maybe we can create a file like "Game.adf.rw" as a workaround to keep track of the read-only status? |
Persisting the change in FAT attributes is I think doable. I wonder whether it is better than the current behaviour. |
Hi!
I'm using Flash Floppy v3.21 and have my config set to respect the FAT read-only attribute instead of forcing it on.
I have enabled read-only in all my ADFs and they shows "Write protection" option in Eject menu correctly enabled
The problem comes when i decide to change the option from the Eject menu.
I have followed these steps:
The option is again ON, as it was at the beginning.
So, it seems to me that the read-only flag isn't saved correctly when changed from Flash Floppy menu...
Thanks for your assistance!
The text was updated successfully, but these errors were encountered: