Testers for EFI Partition Tool needed...
 

Testers need to have made sure that they know how the EFI partition boot method works, and that the manual method works for them, so they know what to do in the case of a problem. I also require that testers, if the tool does not work, can tell me what it has done wrong so that I know what to fix.

OK, so I got around to finishing up the EFI Partition Tool I had promised earlier. Now I need testers to make sure it works before polishing it

IF YOU ARE TESTING MAKE SURE YOU ARE TESTING ON A SPARE DISK BECAUSE THE TOOL DOES FORMAT PARTITIONS AND CHOOSING THE WRONG PARTITION WILL LEAD TO COMPLETE AND UTTER DISASTER

Warning said, if you are interested, post in this topic.

I'm interested but unfortunately too busy to do a proper job of testing.

I have yet to see this tool but I'd be interested since I wasn't able to deliver in time. ;) a few questions though...

does this tool assume you already have your HD partitioned with the GUID partition scheme?
when selecting the drives, does it look at the disks (i.e. /dev/diskX) or partitions/volumes (i.e. /dev/diskXsY)? differences in this could cause problems.
which version of the EFI partition mod does this include?

send me a PM with more info on how I can help out. :)

Hiya
could we have some more info on what exactly the tool does? Is this to automate putting kexts on to efi partition etc?

To answer nfoav8or's questions:

Yes it assumes that you have it partitioned as GUID, the drives are in the diskXsY format (the app uses 'diskutil list' to grab a list of the drives, finds the ones that are 1st partition with the EFI label and size 200MB then displays them in the drop down menu), and this is based on efi_boot_v6.1.

lanxxx,

This tool completely automates the EFI partition procedure including formatting EFI partition, installing the bootloader, setting partition as active, setting up directory tree, installing kexts/kernel/plist, These functions are available separately as well through the app's menu. I have JaS testing this for me right now, but meanwhile here's a screenshot that should explain a lot:

http://img60.imageshack.us/img60/8818/picture1ts5.png

wow. I love how simple it looks. so basically you have to separate the files into different folders based on whether they are kexts, kernel, and boot.plist or does the app look at the file extension and determine what files are appropriate for each section (such as if I placed all my extensions, kernel, and boot.plist file into the same folder and pointed to there)?

[edit] BTW I would love to test this out. Also, I wonder how easy it is to update this app when new versions for munky's Boot-EFI come out?

I'll test if you like have a spare usb drive I can muck around with.

You wont be able to store all the stuff you need into one folder. It's better to keep them separate, plus this way you'll know exactly what you are and are not installing.

I've tested and sent my results to pcwiz so far, the only bug that I had was with the fdisk part where the bootloader gets written to the MBR, if you follow munky's script, when you start fdisk and get to the "w" part, it asks you to confirm and alerts you to needing to reboot to take effect, and it selects [n] when it should be [y]. Other than that, from my test, it worked perfectly. I just needed to install the right kexts, which cause me not to boot but that was my fault, not the app.

Thanks for all the interest guys :) I will let any interested testers test after JaS has given me his results (sometime soon). And nfoav8or, you have to keep things separate and select Kexts folder, kernel, and plist. This way keeps it more organized, and it would be difficult to auto detect in a folder based only on the fact that mach_kernel has no recognizable file type, making it very hard to autodetect unless the very name of the file is mach_kernel, which is not always the case.

As for updating the app when new versions of munky's boot comes out, I will release updates whenever possible, but its easy to update yourself just by going into the Resources folder of the app and replacing the contents with a new version.

I've been running munky's EFI partition mod since the voodoo kernel came online so I've been around the block a bit with it. :) I'm just asking for clarification with his app and how the scripts work through their process and what is required when running the app... plain and simple. :)

I have been here waiting to help him out with this app in whatever way was needed and so by asking questions and seeing the reply, I'm simply making it known to everyone how it works... thats it. The question you answered wasn't meant to be for me (since I don't store the backups for this type of boot method install in the same sub-directory anyways) but rather for the benefit of those who will use it later. :cool:


Good to know, just thought it would be a good thing to double-check and to throw out there for testing. Thanks.

Would you mind alerting me to what kexts should go in the EFI partition so that I may move the there and never worry about an Apple update again? Stuff like AppleSMBIOS perhaps? System.kext? Etc?

first of all, I'm not saying I'm a know-it-all when it comes to this stuff... Just that I've been using it for a while and on a bunch of different (test) systems and (except for the first time doing it) haven't botched it. I've also been helping people install via this method via PM and have had a lot of positive results. All credit, of course, goes to munky (and those that helped him) though. I'm just the messenger who explains it a little more in depth and helps provide a few files. :)

chipset kexts are the biggest one (of course)... just make sure that any of the kexts you place in this partition don't have kexts within a sub-directory of itself as this tends to through it for a loop. Also, modified AppleHDA kexts don't want to work due to dependancies that aren't able to be linked properly from a separate partition.

the files I use with my system are: AppleDecrypt (or dsmos), AppleSMBIOSEFI, and Disabler (although I know the latest voodoo has support to blacklist IntelCPUPowerManagement)... as well as my AppleNForceATA chipset kext (which I use the Test variant for as it provides the best DVD support on my system). I also modify the com.apple.boot.plist file with an EFI string for my video card enabling it to work with the native NVDANV40Hal.kext file (post-Leopard_Graphics_Update).

I haven't had to include the System.kext file as I don't have an hiccups when I don't use corresponding kernel/kext versions except for seatbelt.kext. This is the only file I have to revert back to (native Apple file, just earlier version obtained from a downloaded update and saved).

does this help in any way? (or are you just messin' with me ;) )

Will this tool be able to replace Disk Utility or this tool can only CREATE partitions?

thanks

Neither. It takes the GUID 200MB EFI partition that already exists, modifies it so you can boot from it, load kexts, a kernel and boot plist in it, and use that to load most of your kexts so you can have an on disk boot-132 type setup, protecting you from most Apple Updates.

Can you tell me if this is compatible with soft raid that uses the "boot osx" partition

(Is this the automatic method of "[HowTo] EFI Partition Booting - Zero Modification installs on Intel SSE2 or better" thread?)

Thanks so much. I run the iPC 10.5.6 and have wanted to figure out what exact Kext I need for my system. I can figure out the ones that I explicitly installed (i.e. checked off during the customize install) but not the ones that are part of the "core system files" other than the voodoo kernel.

Willing tester
 

If you still need a tester I can help out hopefully. I've been experimenting with several efi booting processes lately and tinkering with my 3 different installs (5.4 via Kaly, 5.5 & 5.6 Retail via DFE's) but I've got a extra HD I can put in a USB case and try this as well. Looks nice, clean and simple and a great step forward to painless maintenance and updates.

Sure... I have three systems that can go EFI Partition Boot
 

... two desktops and a laptop... Just let me know.

Ten2Pwr6

I would like to be a tester..
 

Hi i would definately like to be tester, this seems like a very promising project.

I'm interested in testing. I've been doing this the manual way for quite some time, but I would love to test this out.

I'm interested to test that !
 

Hy, PCWIz

Ok if your still looking for tester I am here ! I know how this is working, and i am really interseted in this. It could make much easier/faster Apple Raid setting process !

Let me now !

( I'm trauma!@insanelymac ;))

Bye.