kocoman and FlyingPig, iBoot is opensource for those who have a true interest in it's development. We are always looking to expand our team.

Maybe if the both of you actually participated and had a true interest in iBoot, you'd both have a different outlook...

OS_Ninja: what you describe is the opposite of opensource: Your attempt to recruit people to your closed project simply proves my point. If you are opensource, please post a link to a repository where the code is available. Open to "team members only" = closed.

I have been following (U)EFI developments closely since the MacEFIX86 project all those years ago, I think if you had seen as many projects come & go as I have, *your* outlook would be different.

It's your call: join the world or stay locked in your little corner, calling for assistants.

I have been trying all day with this thing, both the windows bootsector patch and mac version. I am not getting the .bin file that the users are reporting. I adhered to the instructions and the only file i put in was my dsdt. My GA-x58A-UD3R says in red letters "MBR START!" while performing DMI services and then goes to a black screen... Any help will be greatly appreciated. BTW I think this is awesome that someone made a true EFI emulation with the capability to run .efi shells. You don't have to take heat from the community for not being opensource too. You are being appropriately protective of what you made so only those with true intent of contributing to your work instead of ripping from it get the source.

I had already tried it, but it just give me black screen (with "no cursor") after the MBR Boot. I then tried/replaced an older version of EFILDR20, which booted iBoot 1.5a, but then when I tried to boot OSX Base Install in Lion, I get
I don't really mind open source or not, because C programming is not easy to understand, unless you can run a debugger while booting...

I did post about this problem in the previous messages in the same thread

Also where to ask for support? I go to IRC #iboot but no one answers/talks there

While working through the EDK source to figure out how the modular system of DUET works, and testing OS_Ninja's bootloader on a few other computers I have concluded that he did not add support for the X58 northbridge and i7 processors. Core and Core 2 chips are entirely functional though. Besides, Gigabyte just released it's hybrid EFI beta for the GA-X58A-UD3R so it should be able to run a boot.efi if I mess around with it a bit .

LOL! Yeah, i see. iBoot is there since you steal my code... Everybody knows it, oh boy.

Your poor, incompetent loser. Like i said.

He has no bootloader, he has my bootloader.

All he probably did was laid a crap UI over it and jacked it up. Idk how someone can beg for code, EDK is SIMPLE to build just look at tianocore and you'll figure it out eventually. Besides, UEFI is coming into PCs now so with a few extra .efi extensions it will be able to boot up into Mac with no hax . If you don't think that it will work because "Mac is not true EFI", well it is, just an old version (1.10) that bypasses the EFI BIOS screen. UEFI has backwards compatability so with an hfs+.efi you can boot with the mac "boot.efi" file. That is effectively what Tom is doing here with DUET.

Btw Tom, is this Core i7 problem because it is not in you EDK compilation?

Koco are you using an x58/i7 build too?

From sunki at this thread
http://www.projectosx.com/forum/inde...ic=2008&st=520

edit:
Using this source

http://www.projectosx.com/forum/inde...showtopic=2079

They can get 32bit Atom booting Lion ...

I don't know where everyone gone, but for now, only EFI (Duet Emulation) would boot lion for now


I hacked around the efi shell and ...

(if you AT least boot into the screen where it tell you have XGB ram, and cpu type and speed, then you can use this method. )

I have find a way to "solve" the iboot's SMBIOS Not found problem that nobody answered before..
(I haven't fully tested yet - will sleep now after this post)

this will need you to have complied your own edk2(64bit only, must match your Efildr20 type) or clover (still need look at fixing it for 64-bit compile), you will need to add Smbiosdxe and smbiosgen to the dsc file.. (can also explain how to if needed)

with my Efildr20 (64bit file) from hacklion.zip, (the others Efildr20 does not work for me (MSI Nvidia based motherboard), just stuck at WELCOME TO EFI WORLD, or black screen etc) I was able to boot into a shell, (I will explain how to do this if needed) -


then from there I just use these commands

fsX: your drive (X = drive, use map to find it, ie: USB0)
cd to the dir of the smbios*.* file
load smbiosdxe.efi
load smbiosgen.efi
cd to iboot dir
iboot.efi

then iboot didn't complain about smbios not found anymore.. and tried to boot mach_kernel..

can also try load vbox things from clover, etc, but try that later..

you could use "devices" shell command to see whats loaded, but for some reason smbios does not show up.. (its not a "device")

you can't run the smbiosdxe.efi directly, it will say "image is not an application"

I hope this help others in the future.

later I need try figure out what *.efi file is the vesa driver (XPC complain no vesa driver)