Forum: EasyBoot
Topic: Cant boot from USB 3 flash drive...
started by: EB1000
Posted by EB1000 on May 20 2013,03:55
Hi again

I finally got my USB multiboot ready and working... I've tested it with bakder v2 script on sandisk cruzer 32GB and it works fine.. The only problem is that this usb flash is way too slow to read and write to...

So I got a new super fast Trancend JetFlash USB3 compatible MLC flash stik (32GB). I once again used balder script... But no matter if I plug this usb to a regular socket or USB3 socket, it wont boot.. I get a cursor blinking...

Any ideas how to fix this?

Thanks
Posted by EB1000 on May 20 2013,04:05
BTW, this USB drive is only compatible with USB3 and USB2 specifications. It says on the box not compatible with usb 1.1.. Could this be the problem?
Posted by EB1000 on May 20 2013,05:27
OK

If I use ezboot burn to USB on this USB3 drive it does work and I can boot into the menu and most of the items work, except for the kicker images as usual (this problem was only solved with balder script)

So my dear friend balder, it seems that your usb script is not working with new usb3 compatible flash drives... Can you check if this could be fixed somehow? Why ezboot usb method works (USB-HDD+) and not yours?

I'll try other methods like express write and report

Thanks
Posted by EB1000 on May 20 2013,05:39
OK

some of the kicker images work but only if I change the command from bcdw cd.img to run cd.img but some don't.. I used ezboot burn to usb with default settings (USB HDD+ no hidden partition). What is the difference between these 2 commands? Should I use other methods like USB-HDD-v2 or ZIP or should I check hidden partition or maybe use express write method? There most be a good configuration that will work on kicker images with run cd.img command...

Thanks and sorry for all the posts...
Posted by balder on May 20 2013,07:20
@EB1000

Quote: "if I change the command from bcdw cd.img to run cd.img"

The 'bcdw' command is mainly for CDFS-file system (CD\DVD-unit). In fact, 'bcdw' cannot be used from FAT32 at all - you must use 'run' or 'memdisk' :O

Further more... In most cased (in majority of cases) you don't need kicker images
In most cases, EasyBoot from V6.0 is able to run ISO image directly - read < HERE >

But as told, in some cases we must use my kicker-image to launch ISO-files :cool:
Typically case is WinPE built from a NT5-system (NT5-system is typically WinXP, Server-2003 which is used in ERD-2003 and ERD5 and BartPE and Reatogo to mention some commonly used products).

Kicker-images can also be 'special-configured' to launch Linux distros such as ylmf or similar distro :;):

Quote: "Should I use other methods like USB-HDD-v2 or ZIP or should I check hidden partition or maybe use express write method?"
I strongly recommend starting with use the default settings (USB HDD+ no hidden partition).
I quote from < HERE >
"USB-HDD+ v2' is recommended for most computers, you may select 'USB-ZIP2+ v2' for old computers"

Quote: "Should I use other methods like USB-HDD-v2 or ZIP"
Only use 'other methods' if having problems (it depends how motherboard acts - especially how BIOS is responding to USB devices)

Quote: " or should I check hidden partition or maybe use express write method?"
Only use 'hidden partition' if you want to 'hide' your build
Attention! If using 'hidden partition' some distros can stop working correctly
Typical example is Hiren's BOOT-CD, that need the folder 'HBCD' to be visible on the root of USB
If ticking 'hidden partition' folder HBCD is hided and by this not accessible - which stops Hiren from run correctly

Note: you can tick 'hidden partition' and still launch any WinPE-iso-file that is in folder EZBOOT (or any ISO-file that is launched using 'special-configured' kicke-image and is put inside folder EZBOOT)
Folder EZBOOT can be hidden and menu still is working correctly (including launch ISO-files that is put inside folder EZBOOT)
----------------------

Quote: "it seems that your usb script is not working with new usb3 compatible flash drives..."
It's not possible for me at present time to check if USB3 is working or not - frankly I cannot understand why it shouldn't ???
There is no major differences how USB2 and USB3 is booted, it's basically the same
Anyway in a couple of months I'm able to check this out

Finally quote: Thanks and sorry for all the posts..."
He, he no problem... :D

regards balder

Posted by EB1000 on May 20 2013,17:03
Thanks again balder.
I just want to clear something:

If I already used your old script to create kicker image (iso file located in disk1 plus img file in ezboot, and this method is working from DVDROM by using the bcdw cd.img command, Can I replace the bcdw with "run" or "memdisk" to make it work from usb? If so, which command is better, run or memdisk?

Thanks
Posted by cafayzieg on May 20 2013,23:56
I'd say its whatever you are trying to boot to, doesn't have the drivers for USB 3.0

Windows 7 doesn't have drivers for USB 3.0 on my board, had to download it manually via the manufacturer website or via windows update... tried to boot to a USB W7 installer on USB 3, doesn't work.... maybe you can slipstream the driver in?
Posted by balder on May 21 2013,01:31
@EB1000

Quote: "If so, which command is better, run or memdisk?"

To clear things up... :;):
You cannot use the 'bcdw' command from FAT32 (same problem to NTFS).
FAT32 is what you use in 'normal case' from USB
Further more, if using 'Burn' in EasyBoot, it always choose FAT32 to USB device with size larger than 2 GB (which I assume you are using - so you CANNOT use 'bcdw')

And I suggest you use 'run' and memdisk in some rare cases (I can explain this later if or when we are hitting such scenario)
By the way, may I ask what kind of ISO-file you are launching with 'kicker-image' ???

regards balder

---------------
@cafayzieg

Quote: "I'd say its whatever you are trying to boot to, doesn't have the drivers for USB 3.0"

Hmmm... Interesting information - thanks @cafayzieg :;):
This means there can be some problem related to test in vmWare as example (to not mention rebooting and also having problems with BIOS regarding USB3)

Well it doesn't work for the 'kicker-image' if there is no support to the USB3 device inside ISO-file (software inside ISO-file)
This is important information - thank you @cafayzieg

regards balder

Posted by EB1000 on May 21 2013,09:35
Thanks

I'm using kicker to launch win7 based PE (like Acronis True image) and some DART XP rescue disk. For some reason run iso does not work for all win7 based live cd's.. Anyway, after changing all bcdw commands to "run" now all kicker images are working when I create USB using ezboot express write... But again I cannot use the boot to hard disk command, not boot 80 nor your harddisk.img are working (the first only reboots the usb and the second fails with error)

Posted by balder on May 21 2013,11:07
@EB1000

Quote: "DART XP rescue disk"

Okay I got it... :;):
To launch DART XP ISO-file you must tick 'Run ISO From RAM' in my script 'easyboot-iso.script'
But do not tick 'Run ISO From RAM' to other WinPE as this isn't needed :O

Note: you don't need my script (or kicker image) at all to launch Acronis or MsDart60\70 or any WinPE based on NT6-system (Vista\Win7\8\Server8 are all NT6-systems) and can all be launched in EasyBoot with menu command:  run ***.iso

Attention! DART XP is based on NT5-system (folder i386 inside ISO-file) and must be run from RAM with support from 'firadisk' - which is automatically implemented by my script when you tick 'Run ISO from RAM'
Note: if having several different DART XP-PE-ISO-files (BartPE or Reatogo or similar), script automatically use the same 'firadisk'-drivers to make it convenient to the user :;):

Quote: "But again I cannot use the boot to hard disk command"
Quote: "not boot 80"
I guess you mean menu command:  swap;boot 80

It is strange my image 'harddisk.img' cannot solve this issue ???

You don't by any chance having several USB devices in use at same time when trying to BOOT your 'primary' harddisk ???
Because if having let's say two USB sticks connected at same time, you fool 'harddisk'img'
Image tries to launch second disk unit which is the second unit counted from the USB drive that 'harddisk.img' assume is the first and only USB disk unit connected to motherboard

Could you please check text-file 'menu.lst' inside floppy image 'harddisk.img'
it should look like this:

rootnoverify (hd1,0)
chainloader +1

If not having this text - do a new download and use latest 'harddisk.img'


regards balder

Posted by EB1000 on May 21 2013,17:12
Thanks. I never knew the command swap;boot 80, to boot from hard dusk when using a cdrom, I just use "boot 80" and it works,, But not from USB... I only have one USB inserted and it keeps booting the usb... Anyway, the only mystery is that your v2 script cannot be used on a USB3 based stick, even if it is inserted into a USB2 socket.. The exboot usb burn works ok on this USB3 DOK even when plugged to a USB3 (boots very fast as expected).
Posted by balder on May 22 2013,02:46
@EB1000

Quote: "I never knew the command swap;boot 80, to boot from hard dusk when using a cdrom, I just use "boot 80" and it works"
Maybe you misunderstood me ???

What I mean is that menu command 'boot 80' is used from CD\DVD-unit and 'swap;boot 80' is used from USB drive :)
The 'swap' is used to 'jump' from USB drive to the first hard disk drive, which is assumed to be the first internal harddisk drive - and 'boot 80' is the target for the first bootable partition on the first hard drive ('boot 81' is hereby the second bootable drive).
Note: the USB drive (USB stick or USB harddrive) is assuemed to be the first USB disk drive connected to motherboard.

Unfortunately some BIOS isn't that clever and behaves odd - something we daily have to live with :(

Quote: "I only have one USB inserted and it keeps booting the usb"
This is strange ???
Take a closer look if you can do something with the BIOS - in which order and which 'drives' that is the 'first', 'second' etcetera bootable drive!

Quote: "your v2 script cannot be used on a USB3 based stick, even if it is inserted into a USB2 socket"
Okay I got the point - but cannot see why it shouldn't work ???
I'll see in a couple of months what I can find out about this (I have not hardware at present time to test with)

--------------------------
You could also test using swap;boot 81  and  swap;boot 82 etcetera as a test to figure out what is going on here
Note: 'boot 80' is the command to boot from first bootable hard drive and 'boot 81' is the command to boot from the second hard drive and as told 'swap' is to 'swap' between the hard drive and the USB drive (USB stick or USB hard drive)

------------------
Finally; you don't need my script 'easyboot-usb_v2.script' if your intension is to only use FAT32 - use 'Burn' in Easyboot
My script is mainly for NTFS - where script launch the ISO-file of EasyBoot instead of using 'ezldr'
The 'loader file' 'ezldr' used in EasyBoot, cannot be run from NTFS - that's why my script instead launch the ISO-file created by EasyBoot.

This means you can have two partitions to you USB drive (usually a USB harddrive), where partition one (the 'boot-partition') has the ISO-file with EasyBoot menu which then launch a linux ISO-file on the second partition (which has FAT32)
Note: you can still have WinPE-ISO-files inside the EayBoot ISO-file (MsDart60 or similar NT6-WinPE) which run excellent inside EasyBoot ISO-file that you have on the NTFS-partition.

I'll say the 'sky is the limit' for what we can do with EasyBoot

regards balder