Should I include it in Leo-10.5.2 ?

I've installed it manually and all is ok but after adding it to the ISO and trying an installation I get a kernel panic on first boot ...

---

Mac OS X 10.6.3 • 2.8 GHz Intel Core I7 860 • ASUS P7P55D • 2 GB 2 Ghz DDR3 • ATI RADEON XFX 4890 1GB • 2 x Hitachi 160 GB Serial-ATA • PIONEER DVD-RW DVR-112 • LaCie Desktop Harddrive 750 GB USB

Yes, EFI is included but I think I've just find why it gives me a kernel panic ...

EDIT: BTW I was talking about 9.2.0 kernel not EFI .

---

Mac OS X 10.6.3 • 2.8 GHz Intel Core I7 860 • ASUS P7P55D • 2 GB 2 Ghz DDR3 • ATI RADEON XFX 4890 1GB • 2 x Hitachi 160 GB Serial-ATA • PIONEER DVD-RW DVR-112 • LaCie Desktop Harddrive 750 GB USB

What was the reason you were getting a kernal panic? It is 9.2.0 in 10.5.1 too right?

Nop It's 9.2.0 in 10.5.2 . And ... I still don't understand why it gives me a kernel panic ... grrr

---

Mac OS X 10.6.3 • 2.8 GHz Intel Core I7 860 • ASUS P7P55D • 2 GB 2 Ghz DDR3 • ATI RADEON XFX 4890 1GB • 2 x Hitachi 160 GB Serial-ATA • PIONEER DVD-RW DVR-112 • LaCie Desktop Harddrive 750 GB USB

Same thing.
However, I'll be waiting.

so basically you slipstreamed 10.5.2 with your update, and all of a sudden gave you a kernal panic?

Exactly but not all of a sudden ... Just because I made an error in a script ! :-)

---

Mac OS X 10.6.3 • 2.8 GHz Intel Core I7 860 • ASUS P7P55D • 2 GB 2 Ghz DDR3 • ATI RADEON XFX 4890 1GB • 2 x Hitachi 160 GB Serial-ATA • PIONEER DVD-RW DVR-112 • LaCie Desktop Harddrive 750 GB USB

It gives me a headache with that damn sound everytime this kind a message appears ...

Someone experiences the same issue with 10.5.2 update ?

---

Mac OS X 10.6.3 • 2.8 GHz Intel Core I7 860 • ASUS P7P55D • 2 GB 2 Ghz DDR3 • ATI RADEON XFX 4890 1GB • 2 x Hitachi 160 GB Serial-ATA • PIONEER DVD-RW DVR-112 • LaCie Desktop Harddrive 750 GB USB

Thanks for closing that other thread, "What is your status Zephyronth?" It was going to become endless. @DoiX,I read your post nice and carefully. I see where your intentions were. Sometimes its better not to disclose that kind of language.

Wouldn't that be something to announce to Apple. Apple is responsible for these kind of problems, unless you patched something so it can work with AMD-based processors.