Replies: 4 comments 14 replies
-
This shouldnt destroy the MBR. Have you tried other usb drives? |
Beta Was this translation helpful? Give feedback.
-
i got the same on diffrent usb drives, all 32fat formatet... some times it works fine on my amiga but then after i change some disks over 000. it make often A-D then over night, next day = drive error F-F. Stick on PC always the same partition is complete gone... re-partition, format, copy again the files over.... it is not only annyoing, all my save games etc. are gone again.... it makes no fun anymore. always i hope this time it is working and then after some days again all lost. like he write: all mbr complete gone, how can the software have so many rights to destroy a full partition. sticks are |
Beta Was this translation helpful? Give feedback.
-
All said and done there's probably no good reason to allow block 0 writes. I can't think of one. Are you interested in testing a firmware which blocks such writes, or perhaps block writes until an explicit LBA change after entering direct access mode? |
Beta Was this translation helpful? Give feedback.
-
Okay, here is a test firmware which disallows writes outside of the mounted FAT volume. This will disallow writes to the MBR, and even to the mounted volume's own boot/BPB sector. It should prevent total trashing of the pen drive. You need to be logged into Github to follow this link: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Not filling a bug report yet and trying to figure out first if that is not a problem on my side. In short, I very often have a destroyed filesystem after quickly changing selected disk slot (meaning it is not readable by Gotek and PC anymore).
I have Gotek SFRC922D connected to Amiga with 2 buttons and simple LCD. Previously had firmware v0.9.16a and thought that this may be an error thus upgraded to v3.29. I was using HxC file selector, now FF's
How to reproduce?
Also this happened to me when I booted Amiga and was on slot 006, then directly after booting quickly changed to 000 and... boom!
In overall I understand that changing selected disk slot when Amiga writes data may destroy disk image, but did not expect that can destroy whole filesystem. Also I have a question, how to properly change slots (i.e. to select slot 000 quickly?)
Beta Was this translation helpful? Give feedback.
All reactions