The usb is created using liveusb creator on Fedora 19. The source img is a fedora 19 live ISO.
I tried several times, but always get Missing Operating System error when boot from the USB.
The following is the list of the files contained in the usb:

[root@fed b1]# ls -R
.:
boot EFI ldlinux.sys LiveOS syslinux

./boot:
olpc.fth

./EFI:
BOOT

./EFI/BOOT:
boot.conf BOOTX64.efi fonts grub.cfg grubx64.efi

./EFI/BOOT/fonts:
unicode.pf2

./LiveOS:
osmin.img squashfs.img

./syslinux:
boot.cat initrd0.img macboot.img syslinux.cfg vmlinuz0
efiboot.img isolinux.bin memtest vesamenu.c32

Could someone who has a successful creation of bootable USB for fedora 19 Live help me to identify what files are missing and fedora support to help me to fix the issue?

Also, when I tried to use a SanDisk Cruzer Switch 16GB usb to create the bootable usb, the software couldn't find the usb, so not able to use it.
Thanks in advance.

Is your computer BIOS set to boot from usb drive? i.e, it can boot from usb and correct boot order is set.

When I start my Windows 7, got error message "Missing Operating System". Tried methods found online, I finally chose Windows Boot Genius to get me out of problem and login pc again!

Yes. later I used a 16GB usb to make the Fedora 19 Live bootable usb, it works.
So it seems the issue is related with the usb size: my problem one is 1GB or 1000MB, the live F19 iso is 951MB, the issue is I didn't see any error while making the bootable usb.
Also I found even when making a Fedora 17 Live bootable USB on the 1GB USB is not working, even though the iso size is less than 700MB.

Not the usb size unless it is a black market model.

Some issue with how bios views the usb device. Could be the usb device. Some are very difficult to make bootable. Used to use the HP usb tool to fix stubborn ones. Syslinux seems to fix some.

So, don't know why the 1GB won't work.

Try dd. Programs to make bootable flash drives had me convinced my computer couldn't boot usb. uNetbootin never worked, nor did anything on windows. I never figured out if it was the drive or the programs. dd has worked every single time though. If you do it make sure you do /dev/sda or whatever but don't include the partition number like this /dev/sda1.