WoeUSB
WoeUSB copied to clipboard
Add a helpful hint to novices
Add a helpful hint to novices about the error code.
I think this is a great idea, as I've had this problem before when using WoeUSB.
Yes and that Windows 10 requires NTFS and not Fat32 or is it the other way around bur yeah
Windows 10 requires NTFS, doesn't work with FAT32
Might be helpful to hint that since it still lets you flash
Is this really necessary since the default implementation will recreate the partition table anyway?
During my use I get the following output:
determine_target_parameters: Info: Target device is '/dev/sde'.
determine_target_parameters: Info: Target partition is '/dev/sde1'.
Mounting source filesystem...
Wiping all existing partition table and filesystem signatures in /dev/sde...
/dev/sde: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
/dev/sde: calling ioctl to re-read partition table: Success
Ensure that /dev/sde is really wiped...
Creating new partition table on /dev/sde...
Creating target partition...
Making system realize that partition table has changed...
Wait 3 seconds for block device nodes to populate...
Cluster size has been automatically set to 4096 bytes.
Creating NTFS volume structures.
mkntfs completed successfully. Have a nice day.
Under what circumstance does WoeUSB allow you to flash an image without repartitioning?
@llamositopia It happened when I used it on Pop OS , and was a huge pain for me until I tried the recommended idea. If it's not helpful, it can always be ignored.