Why FlashBoot?

1. Rich Features

FlashBoot is a tool with rich feature list:

Install fully-functional version of Windows 8 to the USB thumbdrive or USB HDD
Convert Windows XP, Windows Vista, Windows 7 installation CD/DVD disc to bootable USB disk (to install Windows on netbooks and other computers without CD/DVD drive)
Extract Windows XP recovery console from Windows XP installation CD to bootable USB disk
Convert BartPE bootable CD to bootable USB disk
Convert IsoLinux, SysLinux, GRUB4DOS and DOS bootable CDs/DVDs/floppy disks to bootable USB disks
Duplicate USB disks

You get all the features "in one box" if you use FlashBoot.

FlashBoot can either format physical disk or write an image file. So you may create customized USB disk manually or with another tool and use FlashBoot to create image out of it and redistribute it in local network or online.

2. Ease of Use

FlashBoot is organized as simple wizard, which does now show or ask unnecessary information or options and helps you to focus on your task (converting different types of bootable CDs/DVDs and floppies to bootable USB disks). Type of input disk and conversion scenario is detected automatically, although experienced user can override it.

3. Wide Compatibility

FlashBoot is designed to be compatible with all brands. It is not bound to Transend, Kingston, HP or to any other particular manufacturer of USB Flash or other types of USB disks.

FlashBoot supports both USB Flash and USB HDD devices (except U3 flash disks, as for now). We plan to add support for U3 flash disks in future releases.

FlashBoot is compatible with all known BIOS bugs and weird features.

Some BIOSes does have an option to boot from USB disk as a USB-ZIP, USB-HDD, USB-Floppy or Auto. When this option is not set properly, USB disk is not bootable.	FlashBoot does not shift to user the burden of choice between "USB-ZIP" and "USB-HDD" at format time and proper BIOS setup at boot time. There is one unified format, "Multiformat", and every USB disk is formatted in such way that it will work in every environment properly, regardless of current BIOS setting
When BIOS boots from ordinary, non-FlashBoot formatted USB disk, this disk is mapped to A: or C: at BIOS discretion, quite randomly. In the majority of real world cases USB-ZIP formatted disks are mapped to A: and USB-HDD disks are mapped to C:. But there are some exceptions. For example, ASUS P5GDC-V BIOS in Auto mode maps 0-512Mb USB disks to A: and 512+ Mb disks to C:. ASUS P6T BIOS in Auto mode maps 0-1024Mb USB disks to A: and 1024+ Mb disks to C:. ASUS netbooks show similar behavior, but unfortunately there is no setting in their BIOS setups to override such "Auto mode" when choice between A: / C: is made by BIOS depending on disk size	All this diversity is no more a problem for FlashBoot user. When formatting USB disk, you'll be able to specify target drive letter, e.g. A: or C:, and stage2 loader of FlashBoot will take care of this problem at run time.
Sometimes disk CHS geometry is different from BIOS to BIOS. E.g., when formatted on the workstation, the USB disk sometimes is not bootable on the embedded hardware because of different CHS geometry on Windows and under embedded BIOS.	FlashBoot 2 allows to specify disk CHS geometry explicitly at format time, and stage2 loader will force it to predefined values at run time.
Some BIOSes cut off MBR track from USB disk when booting (especially for A:-mapped boots). E.g., they map only partition 1 of USB disk via int 13h.	FlashBoot stage2 loader emulates MBR track in such cases, thus hiding firmware diversity and avoiding OS confusion when it switches to native hardware drivers to access USB disk.
Some BIOSes provide int 13h extended API for USB disks, some do not. Some BIOSes do not provide these services in USB-ZIP mode, but provide ones in USB-HDD mode.	To unify runtime environment, FlashBoot 2 stage2 loader always provides LBA and CHS disk access to USB device it boots from.