oh sorry i was focused on another part of the bootloader,

have you already tested this flag in your boot.plist (org.chameleon.Boot.plist or com.apple.Boot.plist)

Sorry but that doesn´t work, the problem is the same.

It is also on the first screen that apear where you can enter the bootflags.


This bootloader is really great and it would be really great if you can solve this.

Is it possible that it have something to do with the vesa modes?
Because i looked for the vesa resolutions in the bootloader gui and there are no resolutions in 16:9 just 4:3.

But if it is, why it´s working with chameleon?


Thx...

my guess would be the vesa modes too, because i think i had your problem. this fixed it for me: http://www.insanelymac.com/forum/ind...owtopic=211294

Yes but i don't want to flash my vbios of there is a bootloader fix for that.

well, if you ask me, i guess you have 2 options, either you use chameleon and flash your vbios which is safe if you follow carefully the instructions and make a backup of your current vbios OR use the other bootloader, which is not as good as chameleon, if i understand well...

I tried the Graphics Mode bootflag again and this time it worked.
I don´t know why but i´m really happy about it.

glad it worked out for you without much more hassle

Hey,
sorry that my first post are only noob questions, but I'm experimenting with x86-macs now for some time and never got the bootloader-thing quite working. Under Linux and Windows or with an hex-editor, there's no problem; but how exactly do I have to use the supported files? I only find some 'bootxxx'-files and a readme which only seems to describe parameters inside. How can I use the bootloader for an usb-stick with the lion-install-files? Tried the linux-dd-way of directly to the first sectors of the stick - no success. Also tried chameleon installer (in a virtual machine with SL installed) - I end up with a blinking cursor. And I don't find any kind of consistent how-to, tutorial or something like that - it's like the community just knows it all allready so that something like that isnt necessary Please?

Figured it out. For everyone else asking themselves the same questions a quick how-to/summary:
included in the zip are multiple files which are resembling the stages of the bootloader in some variants.
You need at least three files to get a boot image/flash stick or similar booting:
boot0, which is stage zero (written in the mbr),
boot1h. which is stage one and written in the first sector of the bootable and active partition,
boot, which is stage three, resembled by an true file on the active partition.
Now you task is to get these three files to their according destinations; stage zero by
sudo fdisk -f boot0 -u -y /dev/rdiskn (n resembling the disk number of the device you want to use - you can get it with 'diskutil list')
stage one by
sudo dd if=boot1h of=/dev/rdisknsm (m resembling the active partition number, count starts with 0),
stage two by copying the boot file to the destination
sudo cp boot /Volumes/SubjectNameHere (name of the stick/partition/image).

Hope this helps someone and I'm not repeating a thread I haven't found.