![]() The answer given is thus unacceptable, as FAT32 is clearly not working in some use cases.Īfter two days of reading and trying, I have come to the following conclusion: I have formatted the loopback partition as FAT32 (mkfs.msdos -F 32 /dev/loop0), mounted it, and Unetbootin still ignores it like it was never there. I don't see "format with FAT32" as a viable fix. ![]() For people looking for a tutorial: nevermind, unetbootin doesn't allow it anymore! I am attempting to install a CD-bootable ISO into a loopback device to create a new ISO that will properly chainload from GRUB I use Unetbootin ISOs + GRUB for cleanly segregated multiboot on a thumb drive. Why not let the targetdrive option be unrestricted? The mere presence of the option could act as though "Show all Drives" is in effect (for the chosen device at any rate). This is downright dangerous if one doesn't look closely! If they are removing features to prevent people from making dumb mistakes, I would highly recommend a consistent approach: when the targetdrive commandline option is invalid, please exit with an error instead of changing the selection!įurther, commandline options are typically used by the type of people who enjoy shooting themselves in the feet. But there is a bigger problem if one is using the command line options: setting "targetdrive=blah" where blah is not a valid option in the dropdown will simply select a different targetdrive. I also found the lack of a "Show all Drives" selection to be a problem.
0 Comments
Leave a Reply. |