Hervé

If the installation was made with myHack, removing /S/L/E/myHack.kext is actually a bad idea. It holds the kexts that are usually necessary to boot your system. I'd proceed with extra care if you chose to follow that route... Furthermore, adding that kext to /E/E on a myHack installation will not do anything until myFix is re-run. That will rely on the presence of myHack.kext in /S/L/E, so if it's gone, you're sort of certain to end up in the shit. I'd try a couple of things with your USB installer: 1) replace the SMBIOS.plist of the boot pack (MBP8,2) by that of a MPB9,1 as the specs of a MBP9,1 match a lot more those of your Asus 2) add a recent VoodooHDA (e.g.: 2.8.x) + HDADisabler kexts to /E/E folder and redo a myFix on it.

Where did you remove your AppleHDA kext from? /E/E? AppleHDA is natively provided in /S/L/E! That's why you need the disabler.

Having sold my 1st D430, I spent some of the proceeds on a fairly cheap Plextor M5M 128Go mSata SSD for my other D430. The specs of that little SSD are rather good but I was also eyeing on a Kingston SMS200S3 120Go. Unfortunately, I never managed to get one within the budget I had limited myself to. So, I've ended up with the same setup as ddiego. I made an image of the ML HDD installation and restored it to the SSD rather than re-install from scratch. What a difference! ML 10.8.4 now boots in about 30s from the time I enter the BIOS system password to the time ML desktop is fully loaded on screen. The Toshiba 80Go HDD, albeit 4200rpm, did feel faster than the Samsung model I had in the other D430, but there's just no comparison with this SSD. It's complete night & day. An absolute must on those ageing D430s, if it can be obtained cheap enough. My battery too gained about 1hr of usage! NB: I was not seeing any TRIM support for that SSD module so I checked with Disk Utility. It does not seem too be detected as an SSD drive; I guess it's because it's connected through a PATA interface, i.e. non-AHCI. As an order of magnitude, here are some benchmark comparisons between the original 4200rpm HDD and the new mSata SSD: ML boot time HDD: ~90s ML boot time SSD: ~30s Using BlackMagic DiskSpeedTest app (free off AppStore): Write HDD: ~21MB/s Read HDD: ~16MB/s Write SSD: ~62MB/s Read SSD: ~81MB/s The D430 uses the ICH7-M IDE (PATA) interface which operates in Ultra ATA/100/66/33 mode with theoretical max read speed of 100MB/s and max write speed of 89MB/s. In practice, those rates fall to 80-90MB/s and 70-80MB/s respectively. Therefore, SSD mSATA specs get close to Zif PATA interface limits.

It'll never work properly. We can all get ML or Mavericks installed on unsupported systems like D430 or D620. Without full graphics support, there is no point, you need to accept that fact. You're just wasting your time in my opinion.

The DSDT is specific to the laptop, it is not part of Mavericks GM. As such, whatever DSDT file you used before would still be used with 10.9 GM. However, something in the DSDT may have stopped working with GM, so a different DSDT patch may be required.

Forget it, GMA3150 is totally unsupported by Mac OS X. There's just no point trying to Hack that system, it won't be usable.

Hi, you can start by reading the various threads about the M4400 in this particular section of the forum. Then read the various pages of the Web site, especially the EDP ones which provide the installation procedure we support here (i.e. with myHack installer).

You can't use EDP if the system is not in the list of systems covered by EDP. These are listed in the compatibility chart of the EDP section of the web site. myHack is just an installer and will not resolve these issues. What are the specs of that HP mini? Until you list the hardware used on that system, we can't really help you.

The info in "About this Mac" is just cosmetic.

Do you still have the USB installer you used initially to install Mac OS? If you do, boot off that USB installer, interrupt the Chameleon bootloader when you see the delay bar and select your HDD Mac partition.

So try via your USB installer as suggested before...

You did change the active partition with diskpart tool, didn't you? If you set the Win partition (#2) active, set back Mac partition (#3) active. If that does not work, boot off your USB installer and then select your HDD Mac partition. Once in Mac OS X, reinstall Chameleon with Cham Wizard.

Cham Wizard -> Install tab -> Select Cham version, select target partition, click Install. If it tells you it can't find the server and your Internet is up, then maybe the server at the other end is down. Wait and try later of copy whatever boot file you have on your USB installer to your HDD.

DW350/360 are natively supported, the patch is just to be able to turn BT on or off. Other than that, BT services remain operational, true.

If your wireless is not working or not connected, use your LAN port. But basically, you need network connectivity! The OSXL bootpack provides support for the LAN port from the onset.

In that case, once booted in Mavericks, just use Chameleon Wizard to update Chameleon version on your Mavericks HDD/boot partition.

Was your initial DSDT (the "defective" one) from the OSXL bootpack?

What was the problem? What did you do to fix it?

I believe I already told you: Snow Leopard!

The IOBluetoothFamily kext has been completely changed, so the kext from 10.8.4 is of no (re)use... Read my post about it. Look up your BT module in the USB part of the System Report and report that back. In all likelihood, it'll be a DW350 or DW360 and I can easily provide you with the patched kext to place in /E/E after update to 10.8.5. You'll find the PCI ids of the above modules in the 'Bluetooth for D Series' thread in R&D->Wifi/bluetooth section.

I do not believe that Celeron CPU would be supported by anything except possibly Snow Leopard. Or maybe with a custom kernel, like for Atom CPUs. From Lion, Mac OS X requires a Core2Duo minimum, and Celeron are below that minimum spec, as are dual core Pentium as far as I know. What you could do though is try out retail SL 10.6.0/10.6.3/10.6.8 with Nawcom's ModCD and see where that leads you.

Sounds like you would need to patch your graphics kexts for Intel HD4k then.

Incorrect keys in Fake SMC kext?

Thanks for your patience Sergio. It paid off for your system and we're now in a position to integrate this M4400 model (Core2Duo, nVidia FX 770M) to EDP. You're running with the DSDT of an E6400 (that I just modified for cosmetic benefits), so it would be much better to extract DSDT + SSDT tabled from Windows using Dinesh's documented process so that we have the best possible tables at our disposal. https://osxlatitude.com/index.php?/topic/1945-dsdtssdt-patching/ We just need to confirm operational status of webcam and card reader.

Recent VoodooHDA 2.8.1 -> 2.8.4 should all be Ok, bearing in mind that a VoodooHDA kext must be accompanied by the AppleHDADisabler to support audio properly.