You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could not recreate the warning, however in testing I noticed...
gcb@gallah:~$ ls -l Shift.adf
-r--r--r-- 1 gcb gcb 901120 Jun 28 2024 Shift.adf
By rights, one shouldn't be able to make this .adf file writable from the GUI (because..) as far as the Host is concerned, the file is read-only... however one can disable the Write-protected widget regardless ??
Expected: the Write-protected widget to always be set when the Amiga <file> is read-only on the Host?
Is that correct, or is this some kind of bug?
TIA
The text was updated successfully, but these errors were encountered:
If you spin-up an A4000 config, and load the "workbench-311.hdf" file, it presents as;
Note: Read/Write checkbox is active.
This is a misnomer of course ~ if you boot that emulation construct to Workbench, and try to change & save any Prefs, you get the AmigaDOS warning of disk being write protected ... which is actually correct (at the $host level ~ disk file image is read-only)...
The apparent contradiction is not ideal ~ does amiberry even check the <file> flags at all? (just wrt floppy/HDD images)
...not something I ever worried about, but seeing as we're here ;)
Thanks, what I found in practice ....seems WinUAE does the same thing (but it does display the RA attribute), however, it's also more forthcoming/replete with information wrt the hardfile itself... ie;
...obviously we're not filling out the C/H/S or geometry fields, nor the RDB data .... I'm ambivalent, but for sure one day, somebody else not me is going to ask why these fields are there...but empty ;)
This starts here .... https://eab.abime.net/showthread.php?t=119530
I could not recreate the warning, however in testing I noticed...
By rights, one shouldn't be able to make this .adf file writable from the GUI (because..) as far as the Host is concerned, the file is read-only... however one can disable the Write-protected widget regardless ??
Expected: the Write-protected widget to always be set when the Amiga
<file>
is read-only on the Host?Is that correct, or is this some kind of bug?
TIA
The text was updated successfully, but these errors were encountered: