Ok, well here is a picture of qemu boot of boot.efi, it drops to a error quickly afterwards though

http://img263.imageshack.us/my.php?image=qscreenshot6zv0.png

http://img135.imageshack.us/my.php?image=q...enshot15fp3.png

http://img264.imageshack.us/my.php?image=q...enshot16zf6.png

This is after loading the UGA driver, so it shows that some of our problems have been due to lack of drivers for our video cards (lack of efi drivers)

Very impressive, so this would make it so if you wanted efi support you would need a support card that maybe Apple uses so you can extract an efi driver?

Which kernel are you using?? If your useing a semthex kernel or something there was plenty of EFI data pulled.

Trust me, we wouldnt be using his kernel for this, this is a error from boot.efi itself.

as i sad you before, sources of "boot" file for pc's are available, so instead of hacking boot.efi we just need to port "boot" to efi enviroment

Thats a great thing!
If I can help, just tell me
A PM is enough!


cYa ~Neo

You mean the darwin bootloader sources? If so then that might be a option i though u meant BootX

i mean this - http://www.opensource.apple.com/darwinsour...8.x86/boot-132/

@Kiko:

What revision of DUET are you using? Is it the latest stable development version from edk.tianocore?

If so, what is the version of boot.efi you have? Unmodified? Or stripped? I found 3 different boot.efi files in the archive, but dont know what your using currently.

Also using vmware or any other emulation software tends to mess things up with DUET trying to boot an OS.

Booting Linux was no problem from the DUET-usb drive here ...

So if I get a "supposed" to work boot.efi I can test more, Im stuck atm (maybe make sticky with current "releases" for testing etc)

Also extracting with xfv-3 I get all garbage .efi files (names I mean are GUID's? ... file used: "LOCKED_MP11_005C_04B.fd")

/edit: what kernel are you using? Build from xnu sources?



For those having problems building DUET get Visual Studio Express 2005 + Platform SDK + WinDDK.
Install MASM32v9R into default folder (C:\masm32)
Install MASM611 into default folder (C:\masm611)
Open console.
Set the path with: "set path=%path%;c:\masm32\bin" (no quotes ofc)
Load the VSE2k5 envsettings then the PSDK envsettings.
Goto the DUET dir
Try building again (nmake efi32)

Or read the readme

I was using the latest as of the november patch, im gonna work on efi some more now, so im going to get the latest build. Im using a non-patched kernel, and use any of the boot.efi files.

Well im working on EFI alot lately, so you are using a non patchedd kernel (I assume 10.4.9 kernel from the update?)

Then I got 4 boot files (boot.efi mod_boot.efi dec_boot.efi and dec_mod_boot.efi) so I just take the boot.efi and mod_boot.efi to test?



Also downloading this windows ISO so I dont have to use my brothers PC to compile over and over again ><




Another warning DO NOT try to use DUET in an emulation suite, it seems to screw things up atleast I {censored}ed over my USB drive trying to boot from it in VMware (booting linux) and it doesnt when I try native .....

(It hangs right after loading kernel and {censored}s over USB drive, in native it loads kernel (waits 1-2secs) boots linux ...)

/edit: forgot to mention I had to remake the USB drive to be bootable, windows took about half an hour to complete the "format phase" but it did work again ><

whoopyy i found a way how to use temporary firmware on my laptop pc, firmware are loading from floppy disk, now i need to figure out how to add efishell on that temporary firmware and i could use shell on my hardware without any emulation

Btw why aren't you on IRC anymore?

i haven't time now.. summer egzams is near. studies studies and one more time studies.. i will beck soon as i can

How far did you guys get?
I would like to test the EFI environment and see if I can do anything for this project. I have some experience related to making multi-bootable ISOs and some BIOS hacking. If you could use my help, PM me or just post here.