Comments on: [MacOS] Save your Data after EFI-X Crash

By: [MacOS] Is EFI-X illegally using 3rd Party Program Code?

[MacOS] Is EFI-X illegally using 3rd Party Program Code? — Wed, 26 Aug 2009 16:02:21 +0000

[...] removed aswell and one of our members has been officially banned from their forums (the reason was this article in october [...]

By: AsereBLN

AsereBLN — Mon, 06 Jul 2009 13:41:16 +0000

I am, …no was, a customer of EFI-X. After 6 months the module disappeared from BIOS. No way to bring it back to life. It’s defect now. Further since EFI-X firmware update 3.6.11 ethernet and Sleep/Wakeup is unusable. For more then 1 month now, no official word from ASEM about that. So I decided to search for an alternative.

I’m using now a Chameleon based solution and wrote a very detailed tutorial about it.

It’s quite easy and it works absolutely perfect.

SEE: http://aserebln.blogspot.com

Have fun!

thanks looks good. We appreciate detailed guides over not detailed guides :-)
metapapa

By: metapapa

metapapa — Wed, 25 Feb 2009 10:08:17 +0000

@BuildSmart
thanks for the link. As I just moved from one place to another I am still unpacking boxes and rebuilding closets. So my hackintosh test system is still somewhere and I don’t have internet access at my home place. I’ll get back to you, as I like your work a lot and it looks very promising.

Prolly you don’t know our solution yet. I feel like it might be quite equivalent to yours. You may find it here:
http://news.metaparadigma.de/?p=1706
It is based on Munky’s findings.
Kudos!

By: BuildSmart

BuildSmart — Sun, 15 Feb 2009 15:51:10 +0000

Interestingly enough, this update issue appears to be very common, the warranty while they claim is valid till nickel and dimes you on the replacement shipping.

munky, DFE, Zef, AnV did some work in the boot loader area and the work I did was based in part on their work.

The solution I provide does not modify any apple installed software/drivers, the only extension added to the system is a sound driver and if you purchased an audio device you would install the third party driver so updates don’t destroy audio.

No audio injector, no device-properites string, natit or nvkush required, all hardware is properly mapped from a transparent boot loader and no swap CD is required to boot the Apple retail installation media so I find it hard to believe that the EFI-X could provide a more compatible solution, it doesn’t fix everything, in fact on some motherboards you can’t use the built-in ethernet and must use a compatible PCI card and onboard audio is not supported either so what are the benefits when you are limited to specific hardware?

SEE: http://www.insanelymac.com/forum/index.php?s=&showtopic=134515&view=findpost&p=953319

By: metapapa

metapapa — Tue, 04 Nov 2008 10:14:25 +0000

@Mike,

we really love the EFi-X device. Coding and development of all required kexts for the Gigabyte series is a whole bunch of work. This really is standing work of the EFI-X dev team.

Anyway we really wonder, how things are working out. They obviously benefit from the OSX86 community but don’t give anything back in return, but selling their devices (for a lot higher prices than initially announced in june)…

Releasing some of their specific kexts like Psystar did might be a first step into the right direction to give something back to the community.

But currently they keep hiding behind the formula:

“EFI-X is perfectly legal, the rest is not.” Anyway nobody can proof this or the opposite.

The only thing we know is: using or generating OSK0 and OSK1 is legally controversial – no matter if it’s integrated into a hardware device like EFI-X or into a software kext like dsmos.kext or AppleDecrypt.kext