Problem booting 32bit kernel

On my other computer I have dual boot and chameleon boot automatically, without problems.

But on this one I don't have any Windows installed, only OS X. Think that is the problem, isn't it?

Just ascertained, that the order of your strokes is a little bit different of mine.
Your Timeout strokes are above your kerlen strokes. In my plist it looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Kernel</key>
	<string>mach_kernel</string>
	<key>Kernel Flags</key>
	<string>arch=i386 -legacy</string>
	<key>Timeout</key>
	<string>2</string>
</dict>
</plist>

Could that be the reason for the automatic boot in 64 bit kernel?
Could you please show me how your code looks like?

You have much more information in your plist. Do you know if I just can take this one for my HackBook?

Also the string with the graphics is very interesting. I don't have such a big resolution. Is it possible to get it just like that?

@spalek83That graphics string is built only for my specific graphics card. You would have to make an efi specific to your card. k exts.com/view/91-efi_studio..html you would not be making a graphics efi if you are using a graphics injector (natit, nvenabler, so forth) Besides that, the default partition specified is probably different then…

That's a very good information! I'll try that out!

@dissonanzI also would lilke to know, if somebody knows a solution, how to tell Chameleon to automatically boot my HD, when I don't use dual boot with windows. The problem is, that I have to hit Enter every time Chameleon starts.

I don't get this question. Once in Chameleon mine boots to OSX without hitting any key. Maybe you should explain how you do your dual boot. Do you physically remove your Windows drive?

maybe 2 is too low of a timeout, try 5?

<key>Timeout</key>
    <string>5</string>
    <key>Kernel Flags</key>
    <string>-x32 arch=i386</string>

That graphics string is built only for my specific graphics card. You would have to make an efi specific to your card. k exts.com/view/91-efi_studio..html
you would not be making a graphics efi if you are using a graphics injector (natit, nvenabler, so forth)

Besides that,

the default partition specified is probably different then yours
the name of the kernel specified is probably different then yours (you could rename your kernel to mach_legacy so that it doesn't get overwritten when using software update). Ignore this if you use vanilla kernel
and the resolution would need to be changed to what your monitor supports, like you said