0 Members and 1 Guest are viewing this topic.
Efi only boots from fat32. I prefer ntfs for the speed and the fact the file system has no size limitations. To get around this on usb sticks, i make 2 partitions using acronis dd or easus. The first is ntfs, and the second is a 500 meg fat32 partition. As windows can only see one partition at a time, i use bootice http://bbs.ipauly.com/viewtopic.php?f=2&t=2 and select the usb. Then parts manage, select the fat32 partition, and select "assign drive letter". This will hide the ntfs partition and show the fat32 one. Then add the efi dir, a boot.wim in sources, make it bootable with /nt60, and revert back to the ntfs partition. Set this up as normal and make bootable with whatever you want (grub, syslinux, bootmngr, etc...). If you have efi enableed in bios, it will boot from the hidden fat32 partition in efi, and if you use the setup files in x:\sources\setup.exe it will find and use the install.wim on the ntfs partition. The boot.wim boots into ram, but the PE only sees the ntfs partition as its set active. If you use ntfs, syslinux 5.01 and grub4dos 0.4.5c-2013-03-03 both work with ntfs.
1st, its good you tried the files on various usbs with minimal changes. You have to have a good working base to be able to figure out the bugs. I use the Win8 x86 \boot dir as my base, and the Win8 x64 \efi directory and bootmgr.efi. Do you also add bootia32.efi to efi\boot, and do you use the x64 or x86 efi dir as a base? 2nd, you must download as much as me and have alot of HDDS. Both of our USB sticks are J: in bootice ;) I did notice one big difference in our Bootice settings. That leads me to believe that we formatted the sticks differently. Im sure we will figure this out through some tinkering, but it would be nice to have an exact method to do it so others can easily replicate this. I think i used Easus to format mine, but the big difference (besides cluster size) is partition size (does efi partitions have a size limit? ) and the fact my fat32 drive is set to active. As you can see, my fat32 is hidden like yours, but you have no active partition. That leads me to believe had the ntfs drive been active, it may not of worked also.As for booting .efi files from the bcd, thats something i would like to know more on also. The script in boot called @BCD.cmd will make a nice bcd from scratch, with many boot options. Just change the paths to your liking. There is a memtest.efi that can load, so its possible, unless there is a digital signature and its special. Otherwise, maybe we can substitute our favorite efi alternative in its place and run it via tab button. I think the main thing to consider with bcd booting is not trying to boot the actual efi file, but rather what the efi file is trying to load. As i use refind to boot efi, if i select the windows boot and get to the bcd, i can just hit escape and it takes me back to refind. From there you can load another efi file.Last but not least for this rant, i found that the newest Ubuntu 12.10 x64 is supposed to defeat secure boot. I don't have secure boot, so i can't test it, but i was wondering about some trickery like this.Ubuntu uses grub2, and loads efi\boot\bootx64.efi, wich defeats (supposedly) secure disk, and then loads grubx64.efi in the same directory. Im wondering if we can rename grubx64.efi to grub2.efi, and then renaming an efi file of our choice (like refind) and name it grubx64.efi having boot with secure boot disabled. If using refind, you could then load any efi file you want. Also, efi shell can be useful. It loads an efi cmd prompt, and you can just type in the name of any efi file in efi\boot and it will boot it.
Sorry, im not sure what you mean by changing the H. My oven profile, or mega?
Regardless, the mbr bios stuff should still be useful, and you can minimally test EFI stuff in VMware. The iso works in Vmware just fine, but you have to add your own wim files.
Something new i added was the wonderfull Easy2boot project in Grub4dos. You can put any ISO in the _ISO dir and it will show up in the grub4dos menu and boot if you select it. The same works for gz, img, ima, and a bunch of others if you put them in _ISO\UTILITY.
Here is a small ISO with my progress for anyone that would like to use it as a template, and it will do the following.https://mega.co.nz/#!zUd3iBKB!TqYAbHmsqw6JwNJhVfVLJFPco24XciyW3QtDZwbzCSMThese work from ntfs or fat32 USB, and CD\DVD. EFI will only boot from a fat32 usb, or with the dual partition trick on your USB. Grub2 EFI is a WIP, i am in the process of adding knoppix Grub2 for maximum support. From cd grub2 is minimal because of the size of grub.bin. There is a cmd file named @BCD.cmd that you can use to make a custom BCD file. Edit your paths accordingly.Something new i added was the wonderfull Easy2boot project in Grub4dos. You can put any ISO in the _ISO dir and it will show up in the grub4dos menu and boot if you select it. The same works for gz, img, ima, and a bunch of others if you put them in _ISO\UTILITY.