Hervé

Ha! Missed that, sorry! Ok, he can install myHack on his ModCD SL installation, it's not a problem. After EDP is installed and the EDP System Build is done, everything will be nearly as if it were a myHack installation from the very beginning (the difference is ModCD installs kexts directly in /S/L/E, whereas myHack places them cleanly and more efficiently under /S/L/E/myHack kext). No need to start all over again, but it's a good exercise to do once at least. Something to do on a small 2nd and temporary HDD partition maybe... Turning in now, 'way past normal bed time!

1. No, after installation is done, you reboot off the HDD (you can put ModCD disc away from that point). When you'll see the Chameleon horizontal delay bar move, press a key to interrupt the bootstrap and enter the option as listed, then press [ENTER]. 2. You install EDP through the EDP package that you will download or have already downloaded. You need an Internet connection to install EDP because it fetches files off our server. However, I don't understand what you mean here. EDP is a post-install (i.e. post OS X install) tool that provides all the tuning necessary to complete your OS X installation 100%. You need to have OS X installed and booted up to install and use EDP.

There's an easy way to know if you have an Intel wireless card or not: go to the BIOS System tab at the top and move down to Device Info. If you have an Intel wireless card, it'll show "Wi-Fi Device = Intel Wireless", if you have a Broadcom-based card such as DW1390/1395/1490/etc, it'll show "Wi-Fi Device = Dell Wireless" and if it's a 3rd-party card like an Atheros, it'll show "Wi-Fi Device = Unknown device installed". If it's Intel, yes disable it in BIOS or take it out, it would have to go anyway... When ModCD is booting, right before it switches to the OSX86 ModCD B&W screen, it should say: Reading ramdisk image: bt(0,0)/Extra/Preboot.dmg Mounting: done You should not have any error message, so yes, it would appear you have a problem, most probably the disc did not burn properly... May be too fast a speed. Or your ModCD image download got corrupted. I would recommend that you start all over again with the ModCD disc.

Ha ha, you wish!

Well, it actually depends on the FSB speed detected by the OS or the BIOS. The T9300 is actually a 2.50GHz CPU: quad-pumped FSB 800MHz and multiplier 12.5 makes it a 200MHz x 12.5 = 2500MHz CPU. You can check more details here: http://ark.intel.com/products/33917/ Now, hardly any computer runs at the exact theoritical/paper speed and there can be slight variations; for instance you may see the FSB run at 798MHz instead of 800MHz exactly. Use a tool like CPUID/CPUZ in Windows and you'll see. Anyway, if you have a T9300, then this is the exact same CPU that I have and, with my pack, you'll indeed see OS X report a 2.49/2.5GHz speed; that is the correct speed, the speed to expect. I have BIOS A18 (you ought to have A17 or A18) and it always shows a max clock speed of 2.50GHz with min clock speed of 1.20GHz.

Make sure to repair permissions (you can use Disk Utility for that) and that you rebuild cache (use Terminal command sudo touch /S/L/E for that then verify timestamping of the files in /S/L/Caches/com.apple.kext.caches/Startup, bearing in mind that cache regeneration can take a min or two). Of course, if you're not using EDP and/or myHack, you may have your own other tool to manage kexts.

Ha, you should stay away from multifail, we've got everything optimized for those models. Anyway, here's a little Mavericks pack for the D630 nVidia; it has everything you would need and, yes, it's not a lot. But that's all you need, the rest is all Vanilla. No strange CPU speed reports with that... Remember to check your BIOS settings against the recommend values and disable IDA if you have a T7xxx CPU (you can keep IDA with T9xxx CPU). D630n_Mav_Pack.zip You may also optimize Bluetooth if required/desired (DW350/DW360), in which case look at the dedicated thread in Reseach section. NB: the pack does not include any wireless kext that you may require, depending on the card you use...

You can probably ignore it, I've seen that before. EDP is totally Ok for Mavericks. If using it caused boot issues, then you proabably did something wrong in the process. What kexts are you using, what Chameleon boot options, what SMBIOS profile, etc? Also what CPU do you have in that D630? I'm not aware of any 2.55GHz FSB800 CPU that could be used in that laptop.

When you run the EDP package to install EDP on your system, it will download a lot of files, you can actually see it if you click the Details button. At the end, the installation package will ask you if you want to run EDP or not. If you reply Yes, then EDP will launch and then you can do your System Build. At that point, I do not know of any script that would ask you to answer Yes or No. The only thing that EDP prompts on startup is a Terminal window where you have to enter your password. After that, nothing. Try and re-install EDP and click Details to monitor what happens. Just a few days ago, we had a forum member who encountered issues installing EDP and it turned out to be his ISP who was blocking the downloads (and so he was getting absolutely nothing!). When he used a 3G connection, everything went trough and he was able to run EDP and finalise his OS X installation.

Hi, You probably know it, but that sort of mod has been done before, though maybe not on a D830. There are quite a few vids on youtube and various forums that show the results. I think we might even have a forum member here who had done this same mod and gave the details, but I can't be 100% certain.

I'm actually using the Voodoo#3 from EDP system build; it's v2.8.1. Works perfectly. Did you use EDP on your system? It's perfectly safe to do a System Build. If you're without EDP, remember to use AppleHDADisabler with VoodooHDA kext.

There is actually a way to be able to turn Bluetooth on and off in Mac OS by patching the appropriate Bluetooth controller (it may not turn BT radio off though...). In the case of the DW350 (dev id 0x8103) and DW360 (dev id 0x8140), we're in the presence of CSR chips (ven id 0x413c). We can therefore patch the CSR Controller kext in the following manner (Mountain Lion samples below): extract a copy of CSR Bluetooth Controller Transport kext from /S/L/E/IOBluetoothFamily.kext PlugIns folder and place it to your desktop open up the kext and edit its info.plist file as detailed below insert lines similar to the following ones (copy, paste and modify an existing Apple Portable module of the file), where PCI ven ids and dev ids are entered in decimal, not hex: <key>DW350</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.iokit.CSRBluetoothHCIControllerUSBTransport</string> <key>IOClass</key> <string>CSRBluetoothHCIControllerUSBTransport</string> <key>IOProviderClass</key> <string>IOUSBDevice</string> <key>idProduct</key> <integer>33027</integer> <key>idVendor</key> <integer>16700</integer> </dict> <key>DW360</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.iokit.CSRBluetoothHCIControllerUSBTransport</string> <key>IOClass</key> <string>CSRBluetoothHCIControllerUSBTransport</string> <key>IOProviderClass</key> <string>IOUSBDevice</string> <key>idProduct</key> <integer>33088</integer> <key>idVendor</key> <integer>16700</integer> </dict> delete every reference to existing Apple modules, Dlink, CSR and otherwise: <key>AppleDesktopModule</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.iokit.CSRBluetoothHCIControllerUSBTransport</string> <key>IOClass</key> <string>CSRBluetoothHCIControllerUSBTransport</string> <key>IOProviderClass</key> ... ... ... <key>idVendor</key> <integer>3641</integer> </dict> save the edited plist copy the patched kext to /E/E or /S/L/E or other, repair permissions & rebuild cache (use myFix if applicable), then reboot After reboot, you should be able to see the Turn On/Turn Off option in the scroll-down menu when you click on the top menu bar BT icon: NB: Apple having the tendency to bring out different Bluetooth kexts at each version or release of Mac OS, it's strongly recommended to repatch the kext from the running version after each Mac OS installation or update, rather than carry kext from previous version or release as they may not work any more. The same principles should be applicable to other BT modules too. This was brought to you by our resourceful friend Bronxteck.

Ok, just did a fresh install with Nawcom's ModCD + retail 10.6.0. You need: ModCD on CD or DVD Retail SL DVD or USB key with retail SL image restored to it a small USB key (for the D630 intel LoRes bootpack) an external screen with VGA cable (for 1st reboot) Here's what to do: boot ModCD swap discs and press [F5] select Mac OS X Install DVD and press [ENTER] (this will boot with default legacy kernel, but it's Ok) select your desired language and click right arrow at the bottom at main install screen, click on language flag at top right corner and choose the appropriate input source that matches your keyboard Click on Utilities in top menu bar and select Disk Utility create your GUID/Mac OS Extended (journaled) partition on your HDD, then exit Disk Utility, click Continue, then Agree at main installation screen, click on your target SL HDD partition to select it, then click Customize button in the displayed list, unselect Printer Support/Additional Fonts/Addtional Languages (unless you want to add another one) and leave the rest unchanged. Then, click Ok. Click Install to proceed with installation on your target SL partition. This will take approximately 20minutes. Once installation completes, you will be prompted to Restart (will do it automatically after 60s). Attach an external display, you're going to need it. When reboot starts: force display output to the external screen by pressing [Fn-F8] key combination. If you do not do that, you'll always end-up with blackscreen when the Snow Leopard Welcome tune plays. interrupt bootstrap and specify boot option GraphicsEnabler=No (mandatory on D630 X3100 LoRes 1280x800 to avoid LCD garbage; not required at all on D630 X3100 HiRes 1440x900). You'll see the boot process on the external screen, then, right at the time when the system switches to Mac OS X desktop, the display will automatically swap back to built-in LCD. The Welcome video will play accompanied by the Welcome tune. Then finish off 1st boot installation. Basically, SL will boot to blackscreen without this trick due to lack of proper info about the built-in LCD in the BIOS DSDT. As such, you need to use our patched DSDT table: download our bootpack from a Windows PC and place it on a FAT-formatted USB key connect that key to your D630 running SL (i.e. once it has booted into SL as per above process) copy the DSDT file to /Extra From there on, you will be able to reboot your D630 straight into Snow Leopard (with full graphics support) and without the external screen trick. Next, you need to finalise your D630 installation (audio, network, BT, etc.) and probably update to SL 10.6.8: download the 10.6.8 Combo update off Apple's web site download myHack 3.1.2 off the Net download EDP package off EDP pages of OSXLatitude website Delete VoodooHDA from /System/Library/Extensions. It was placed there by ModCD, but causes KP when booting 10.6.8 Run myHack 3.1.2 and: Install Extra->Use my own, pointing to our bootpack that you've previously placed on a USB key Install myHack utilities If you have Internet connection, run EDP package to install it, then launch EDP and do a system build, using pre-selected options. If you don't have Internet connection, reboot and repeat this operation (with bootpack installed at previous step (myHack), you'll have your Ethernet connection working after reboot) Run and apply 10.6.8 Combo Update -> You may now reboot into SL 10.6.8 and enjoy full vanilla Snow Leopard! NB: at that stage, you can make an image of your retail DVD. This can subsequently be restored to a USB key on which you can also apply ModUSB + our bootpack/DSDT. That then provides you with a single bootable USB key that allows you to install SL completely from scratch and a bit quicker too.

I'll try it later on on my own D630 Intel. But I can 100% confirm it works because that is how I started on the D630 all those moons ago. What wireless card do you have in that laptop?

It seems you need to re-install Chameleon on that USB installer or redo it.

This should be all over the place as we keep repeating it on and on, but Intel wireless cards are not supported and can cause Kernel Panics. As such, if you have one, disable it in BIOS or, better, remove it completely. Those cards have got to go and be replaced by Mac OS compatible cards (there's a non-exhaustive listed published in Research section of the forum).

There's a pinned thread dedicated to BIOS settings at the very top of the D6xx section. Remember: you need a retail SL DVD (10.6.0 and10.6.3, possibly10.6.8), not a disc that came with a Mac or a recovery disc. Alternatively you can use a USB key/external HDD that has the installation image restored to it (but that would require a Mac or a Hack to achieve).

Well start with myHack and Generic bootpack/Extra. If that takes you to installation, you'll probably be able to get a basic ML installation to boot and, once in there, open up a Terminal command and send us the results of the command: lspci -nn

https://osxlatitude.com/index.php?/topic/2880-d420-video-issues-w-multiple-osx-versions-what-am-i-doing-wrong-here/&do=findComment&comment=22054 Links to ModCD are in a few posts up in that thread. Once you're done, read-up the EDP pages of this web site and visit myHack's site too.

You would have much to gain by reading the EDP documentation page, as well as myHack's documentation. Then spend some time researching this forum and others too. I know it's very easy to just pop the questions, but it pays to make your own research, test and try things, fail, restart, etc.

Just erased my old D620 GMA950 SL installation (it was on an MBR partition) and replaced it with MLPF ML 10.8.4 (on GUID partition). Not a problem at all using the posted guide. Just make sure that: you run the latest BIOS you've configured it as per recommended settings you have no Intel wireless card plugged in (take it out otherwise, it'll have to go anyway). that you install on a GUID partition, formatted Mac OS Extended (journaled) Also, when you create your MLPF installer, make sure you pick the exact same ML version in the list as what you actually used for your initial Vanilla installation. Otherwise, it won't work since MLPF will be looking for that install app in Applications folder. For instance, if you started with ML install app 10.8.0, then updated to 10.8.3 or 10.8.4, create your MLPF installer with 10.8.0. Only when you've booted off that MLPF installer, you can choose 10.8.3, 10.8.4 or whatever final Vanilla ML installation you have to apply MLPF on it. I hope you're clear on that. NB: I created the MLPF installer on a 8Gb 2nd partition on the laptop's HDD, but a USB key or USB HDD worked just as well for me in the past.

Yes, that is one of the most basic requirements to install Mac OS X: your HDD partition has to be formatted Mac OS Extended (journaled). Ideally, you should use GUID/GPT partitions too.

Which audio kext are you using? Patched STAC9205 or Voodoo? Maybe that card can only be supported through AppleHDA drivers. Whatever driver you're using, try the other one listed in EDP, you never know...

Repair permissions with Disk Utility. Re-run myFix (full).

The guide has been thoroughly tested prior to publication. I've validated it for all ML versions up to 10.8.4, i.e. the current one. If you follow it to the letter, you should get there without a hiccup. You seem to have your KP when booting the MLPF installer. What does it say at KP? Make sure you've used the correct bootpack/DSDT, that you have indeed create the /Extra folder on the MLPF installer partition with DSDT and plist files and boot using "-f" flag, not "/f". Is your HDD partitioned GUID (Ok) or is it MBR (NOk)?