RogerP

Many thanks. The USB is fat32; my OS filesystem is btrfs (more's the pity).. With the "do not mount" filesystem option requested the GUI gave the same error as above, top, so I used: sudo veracrypt -m=nokernelcrypto --filesystem='none' /dev/sdb1 vera which returned with no errors but the following is still the case: sudo fsck.fat -vn /dev/sdb1 fsck.fat 4.2 (2021-01-31) Logical sector size (33104 bytes) is not a multiple of the physical sector size. (obviously not good), and sudo fsck.fat -a /dev/sdb1...

Many thanks. The USB is fat32; my OS filesystem is ext4. With the "do not mount" filesystem option requested the GUI gave the same error as above, top, so I used: sudo veracrypt -m=nokernelcrypto --filesystem='none' /dev/sdb1 vera which returned with no errors but the following is still the case: sudo fsck.fat -vn /dev/sdb1 fsck.fat 4.2 (2021-01-31) Logical sector size (33104 bytes) is not a multiple of the physical sector size. (obviously not good), and sudo fsck.fat -a /dev/sdb1 fsck.fat 4.2 (2021-01-31)...

Many thanks. The USB is fat32; my OS filesystem is ext4. With the "do not mount" filesystem option requested the GUI gave the same error as above, top, so I used: sudo veracrypt -m=nokernelcrypto --filesystem='none' /dev/sdb1 vera which returned with no errors but the following is still the case: sudo fsck.fat -vn /dev/sdb1 fsck.fat 4.2 (2021-01-31) Logical sector size (33104 bytes) is not a multiple of the physical sector size. (obviously not good), and sudo fsck.fat -a /dev/sdb1 fsck.fat 4.2 (2021-01-31)...

Many thanks. The USB is fat32; my OS filesystem is ext4. With the "do not mount" filesystem option requested the GUI gave the same error as above, top, so I used: sudo veracrypt -m=nokernelcrypto --filesystem='none' /dev/sdb1 vera which returned with no errors but the following is still the case: sudo fsck.fat -vn /dev/sdb1 fsck.fat 4.2 (2021-01-31) Logical sector size (33104 bytes) is not a multiple of the physical sector size. (obviously not good), and sudo fsck.fat -a /dev/sdb1 fsck.fat 4.2 (2021-01-31)...

sudo udevadm lock --device=/dev/sdb mkfs.msdos /dev/sdb produces: mkfs.msdos: unable to open /dev/sdb: Read-only file system Whereas: sudo udevadm info --query=all --name=/dev/sdb produces: P: /devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:1.0/host6/target6:0:0/6:0:0:0/block/sdb M: sdb U: block T: disk D: b 8:16 N: sdb L: 0 S: disk/by-id/usb-_USB_DISK_3.0_070B6AEA1DC05916-0:0 S: disk/by-path/pci-0000:00:14.0-usbv3-0:1:1.0-scsi-0:0:0:0 S: disk/by-diskseq/2 S: disk/by-path/pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0...

I only use Linux (Arch). I have two computers, both single-booted with Linux, the following behaviour is the same on both. With a USB stick mounted using Veracrypt2 (as a "Device"), my OS crashed. After the reboot I remounted the Veracrypt volume via the GUI, it was mounted read-only (ro). I checked the Settings->Default Mount Parameters. The ro flag was not set. The attempt to mount the drive via the Veracrypt GUI gives: device-mapper: reload ioctl on veracrypt2 (254:0) failed: Read-only file system...

Pity nobody replied yet. I don't know which OS you're thinking about. I only know Linux, and with that there's no reason your idea cannot be implemented, provided the boot-up has moved out of the BIOS phase. When the OS starts to be loaded, the boot-up process loads and reads no end of scripts and config files. Simple beeps etc should be easy to do at that stage. I don't understand what is meant by the "memory detection mechanism" in your comment: I noticed that the memory detection mechanism should...

Hi, I've switched from using aymptote to asypictureB. In the asymptote language you...