Thank you, you're far too kind, I'm simply standing on the shoulders of many giants.
As far as the wiki goes, if we're going to copy & paste what I've just written, I'll go through it and write it out in a better way and PM it to you. Hopefully I can get to it by the end of the week. Looks like I'll probably have some time Thurs and/or Fri.
I like your idea about *if unetbootin didn't work*, because many people are familiar with it and most would rather use a GUI than cmd line. Also, it's possible that unetbootin will start working with UEFI USB creations at some point.
Any ideas what tools are working for people - I would be willing to explore and assist with updating (if needed). Should any Wiki pages need updating, I am back around for a bit as life has calmed down - let me know!
Unetbootin has not worked correctly for me the past few times I've tried to use it, so I've basically just stopped using it. Some others on the forums may have other graphical tools that they like, hopefully they will chime in here.
There is a tool called rufus that does a great job of creating bootable USB's, however it only runs natively in Windows. It's capable of creating UEFI bootable USB's with GPT partitioning, as well as Legacy/BIOS bootable USB's with MBR/MSDOS partitioning. But you have to know ahead of time which you are going to need. Which can be a bit confusing if one has never dug into that stuff before. Bringing me to the beauty of the 'dd' method below...
Otherwise, currently the best way to create a bootable USB for Bodhi is by issuing a variant of the command
sudo dd if=/path/to/bodhi.iso of=/dev/sdX
in the terminal, where sdX is the plugged USB designation. (The command `sudo parted -l` should give a good listing of which /dev/sdX belongs to your plugged in USB) This method will make the USB bootable and installable in both Legacy/BIOS and UEFI systems. No other action is necessary in USB creation. **except very rarely, on some systems I have had to unplug the USB while power is off and re-insert before booting, not sure why** Our ISO's are created using a hybrid boot method very similar to what Ubuntu also uses. So basically, a USB created using 'dd' will automatically know how to boot based on the current settings in the "BIOS". (You probably know all of this stuff, but I'm just putting it here for completeness.)
Alternatively, if someone wants to burn a CD/DVD that will be bootable under both Legacy & UEFI, this command will work:
(it is basically the equivalent of 'dd' for a CD/DVD)
xorrecord dev=/dev/sr0 speed=12 fs=8m blank=as_needed -eject padsize=300k /path/to/bodhi.iso
-- or --
you may need to replace 'sr0' above with one of --> cdrom, cdrw, dvd, dvdrw (or possibly others)
Back to rufus, or any other graphical USB creator...
Windows 8/10 users will have to create a UEFI-USB if they want to maintain dual boot with Windows.
Windows 7 users may have to experiment a bit to determine *for sure* which boot methed they need to use. GPT partitioning and UEFI boot methods were beginning to be implemented during the Windows 7 era.
Windows XP and below users will for sure be booting in Legacy mode.
But again, if the USB is created using the 'dd' method above, the USB will automatically boot using the correct method for that PC's "BIOS" setup. (BIOS vs UEFI is a whole different conversation, there are actually very very few machines that will be using BIOS to boot. Even though it may be an old PC booting in Legacy mode, there's a very good chance that it's actually using a UEFI interface, not technically BIOS. Anyway... Squirrel !)
Thanks to all who work on the wiki, and many regards.