Red Five

Bacopilot, SwitchResX should do the trick. You could probably use ControlPlane to trigger SwitchResX to switch display profiles. You could just run both screens side-by-side; I did it that way for years and I never had any problems.

I too was using my D630 Nvidia on the D/Port Advanced Port Replicator (not the full dock, this one doesn't have the PCI port or built-in power supply). DVI worked perfectly, everything worked except all of the on-dock audio ports (headphone jack and S/PDIF). I haven't used it in a while, though, since I moved to a new Hackintosh built on an Optiplex 960 (Core2Quad, GeForce GT640 w/2x 24" HD LCD via DVI). I'm rebuilding my D630 fresh, trying to get Mavericks to install, but currently can't get the installer to boot from my flash drive (keep getting a Mach-0 has bad magic number error); ML installer always works perfectly. Will be dual-booting ML/Mav and Ubuntu Studio (US supports an older FireWire audio interface I have, while OS X no longer does).

I bootstrapped my install by creating an OS X virtual machine inside VirtualBox; it was pretty straightforward once I had an ISO image of the install DVD. I installed it as a 64-bit OS X Server selection in VBox, then followed the instructions in this thread to create my thumb drive installer from inside VBox. Then I followed the rest of the instructions to install on my D630 and it's been fairly smooth sailing from there.

More RAM is always a good idea; more RAM means less need for and time spent on swapping to disk. And for systems with an SSD, less use of swap is a Very Good Thing. Excessive swapping can kill an SSD very quickly. If memory serves, HyperThreading was never part of the Core2 CPU feature set (Core and Core2 are basically multi-core 64-bit extensions of the P3/P3-mobile architecture, while the Core i series adds HyperThreading from the P4); it was only available on the Xeon CPUs around that time.

The Dell 1390 wireless card is known to work; it's what I'm using this very moment. I think most of the Dell-branded cards will work, too.

I updated to 10.8.2 a few days ago, no problems. The installer did the failure message thing, but it was successful.

What wifi card do you have? I think the standard install only works with a few cards, and if it's an Intel wireless card I think you're out of luck. I could be wrong there, but I think that's what I've seen on other threads here.

Ah, ok, I'll keep that in mind. That's in Disk Utility, right?

Once I plugged the device in and opened Audio Midi Setup, my onboard audio just vanished. And after a while, the Saffire quit working quite right as well.

I screwed up my OSX partition when I was trying to get rid of my old Ubuntu partitions, so I had to reinstall everything. I'm usable again, but haven't redone the firewire thing. I'm going to try using the kext from the 10.7.4 updater; I was seeing some odd behavior on my system once I got the SL version in place and working, it seemed to take out my system audio when I plugged in the Saffire box, then all sound quit working until I rebooted. No biggie right now, won't need to use the audio interface for a while. Thanks for your help, though, Bronxteck. It pointed me in a promising direction.

I got some sudden inspiration based on something I saw in another forum and the fact that the error I kept seeing said "link error": I had turned off FW networking. I turned it back on, and lo and behold the hackintosh now sees the audio interface! I'll have to see if I can revert to the ML version of the kext, but it'll probably work too.

Not yet, I wasn't sure if that would be the right thing since I figured it needed the IDs of the FW controller rather than the specific device. I'll give that a shot, though.

No joy on the 10.6.x kext. Maybe I still need to update the list of IDs as mentioned earlier. Do you know of any good way to get the vendor and module IDs? System Profiler is useless here; it gives me the IDs for my Saffire box, but nothing appears for the FW controller itself. I had to look through system.log to find what I tried earlier, but I'm not certain it gave me all the numbers I needed.

Possibly dumb question, but should I restart between myFix and trying to load the kext?

Cool, thanks. I'm trying that now, will report back shortly. I'm also getting the 10.7.4 updater from Apple Support, though I tried that yesterday without using myFix and it didn't work. I was able to extract everything necessary to find that kext from that updater; downloading 1.4GB for a single 2M file is a bit ridiculous, though...

No older versions, this is the first time I've tried osx on my laptop. What is the "e/e" you mentioned; Extras/Extensions or something?

Unless I did something wrong (perhaps I got the wrong controller IDs, which were difficult to find), that didn't work. The error I'm getting indicates that I should check the kext with kextutil, so I did. It says there are 2 unresolved symbols in the kext (before and after the ID update): __Z25IOAF_Float32ToNativeInt32PKfPij, and __Z25IOAF_NativeInt32ToFloat32PKiPfj Further googling indicates these are part of the Thunderbolt kexts, which of course this laptop does not have.

Would that be the device IDs of the FireWire controller, or the audio interface?

Definitely 8GB max RAM. I upgraded from 4G to 8G as soon as I realized I could. I sometimes have to test things in various operating systems, and need lots of RAM for virtual machines. Oh yeah, that's definitely 64-bit only. I haven't run a 32-bit OS ever on my D630; I'm basically switching from Ubuntu to Mountain Lion this weekend.

I followed this guide on my D630 NVidia, and it went pretty smoothly; thanks for all the hard work. I only have 2 questions, though: is it possible to get the digital outputs working on the D-Port/D-Dock (S/PDIF & IEC958), and has anyone else gotten FireWire audio devices working? AppleFWAudio.kext gives me a link error when I try to load it, so I can't use my Focusrite Saffire. I was able to successfully run the 10.8.1 updater, too, though it gave me an update failed message.

I got things running on my D630 yesterday, and I'm impressed. Almost everything works perfectly, and seems pretty smooth and peppy, too. I only have a couple major items: Is it possible to get the digital audio output working through the dock/port replicator, and I seem to be having some trouble with FireWire audio devices I have a D-Port replicator, and so far everything works except for the S/PDIF output and the headphone output. I also have a Focusrite Saffire 4-in/10-out FireWire audio device, and the AppleFWAudio.kext gives errors when it loads, whether automatically or manually. It says something about a link error. I'd appreciate any insight anyone might have on these items. Otherwise, things seem to be working pretty well. OS X even auto-detected and activated my 2nd monitor connected through my D-Port's DVI port, even during the install!