Hervé

Good stuff. Once you get to SL 10.6.8, you should then be able to use the latest legacy kernel 10.8.0. It's available in the Precision 670 boot pack if I remember well. If not, you'll easily find it on the web.

Mmm, legacy iboot (chameleon, stolen and rebranded)... Maybe the Pentium D is not compatible with Mach kernel (I thought it were), although, usually, you get a kernel panic and a system reset in such case... What you could try to do then, is add one of Nawcom's legacy kernels to the root of your myHack USB installer and specify it when you boot it (just type , eg: Darwin_10.8.0). If that works, you'll have to copy the legacy kernel to your HDD after your initial installation and specify it in your Chameleon boot plist. Try with the attached kernel. Darwin_10.4.0.zip

You're not very clear. Are you or are you not making use of a proxy, i.e. do you have one to control access to the Internet? If you do, you probably need to configure your SVN client to make use of your proxy. You can look it up on the web, there are tutorials. Are you in an office environment?

The Optiplex SFF uses a Q965 Express Intel chipset with GMA3000 integrated graphics. That graphics chip is totally unsupported by Mac OS X so you basically need to add a supported PCIe x16 graphics card to get anywhere (without graphics support, a Hackintosh is hardly usable...). Your choice in that respect could be limited since I believe the SFF model can only accept low-profile cards. I have some experience on that front: my Vostro 200 is the Slim Tower version. Low-profile cards that will work in SL include: ATI Radeon Pro X1300 (Dell fitted a fanless version to some of their Slim PCs (I have it). Available cheaply on ebay) ATI Radeon HD5570 nVidia 8400GS nVidia GT520? -> needs confirmation I believe all those exist in passive/fanless form, which is probably what you need on your Optiplex 745 SFF (Dell's documentation mentions 25W max. on PCIe x16 slot and a 275W power supply). Be careful though, as they may take up 2 slots due to heatsink height/depth. Intel Q965 chipset operates an ICH8 I/O controller. That is normally supported by the IOATAFamily kext, but if using that kext does not help in seeing/detecting your HDD, you ought to check the PCI device id for your on-board controller as it may differ from the id(s) specified in the kext plugin. If you open up IOATAFamily kext and browse to the PlugIns folder, you'll see a kext called AppleIntelPIIXATA. In that kext, you'll find a file called Info.plist. This is where details of the I/O controllers can be found. For instance, this is the sort of things you should find in the plist, for ICH8 controllers: ICH8 ATA/100 CFBundleIdentifier com.apple.driver.AppleIntelPIIXATA Controller Name ICH8 ATA/100 IOClass AppleIntelPIIXATARoot IOPCIPrimaryMatch 0x28508086 [...] ICH8 Serial ATA CFBundleIdentifier com.apple.driver.AppleIntelPIIXATA Controller Name ICH8 SATA IOClass AppleIntelPIIXATARoot IOPCIPrimaryMatch 0x28208086 [...] ICH8 2 Port Serial ATA CFBundleIdentifier com.apple.driver.AppleIntelPIIXATA Controller Name ICH9 2PTS SATA IOClass AppleIntelPIIXATARoot IOPCIPrimaryMatch 0x28258086 [...] ICH8-M Serial ATA CFBundleIdentifier com.apple.driver.AppleIntelPIIXATA Controller Name ICH8-M SATA IOClass AppleIntelPIIXATARoot IOPCIPrimaryMatch 0x28288086 [...] The lines reading provide the full PCI id of the hardware: the 4digits number right after '0x' is the device id and 8086 is the vendor id for Intel. If you still have Windows running on that Optiplex, you can easily retrieve the device id of your controller: open-up the Device Manager, select your ICH8/SATA HDD controller and right-click to Properties. In the 'Details' tab and you should see PCI device id + vendor id in a line that looks like: "PCI\VEN_8086&DEV_xxxx&SUBSYS_--------------". The number displayed after DEV is your PCI device id. Alternatively, use Terminal command lspci -nn (need kext lspcidrv loaded though). If the above plist does not contain your particular device id, you need to add it: you can either copy/paste an existing ICH8 section, rename it to something like "ICH8 3" (or whatever you like) and replace the device id by your particular number or you could just overwrite an existing PCI id. You can use a simple editor like TextEdit to make your changes. This process is called patching the plist/patching the kext. No guarantee that it'll work afterwards though... Note that, to be able to edit the kext plist, you'll probably have to copy it (not move it) away from /E/E before you make your changes, or you're likely to meet a Write access issue. After making and saving your changes, copy the kext back to /E/E (replace the existing file if prompted to) and re-run myFix (quick).

I understand this audio chip to be supported by VoodooHDA. Try it! Look here too: https://osxlatitude.com/index.php?/topic/1970-fix-for-audio-issue-after-sleep-in-alc269/

The Optiplex 745 is already integrated in EDP, although I admit there are several forms of that particular model. However, they share the same underlying platform. Did you use the Optiplex 745 boot pack? Can you set your SATA HDD mode to AHCI on the BIOS at all? I'd also advise you to search for posts about your model on the forum. It's been discussed before.

HWMonitor is accurate regarding CPU T° as long as the the IntelCPUMonitor kext has the right Tjmax value in its plist. You can get the Tjmax info for your CPU off Ark Intel. In all likelihood, the 2.0GHz CPU in your D630 is T7250 or a T7300. As mentioned before, I doubt it can be a T7200 out of a D620 since sockets are different between the 2 laptops and a socket M T7200 does not fit in a socket P (incompatible pinouts). Those CPUs have a Tjmax of 100° by the way.

myHack usually places deleted kexts in /Extra/RemovedExtensions; they can therefore be retrieved and re-instated.

Can you upload your IOATAFamily kext please?

May be it's not the touchpad itself but the ribbon cable...

Your RAM modules are Ok.

D620 has Socket M and uses FSB 667MHz CPUs whereas D630 has Socket P and uses FSB 800MHz CPUs; the CPUs are not interchangeable (I just checked: a T7200 out of a D620 cannot physically fit in the socket of a D630). You really need to know what you have in there, it could just be a low-end FSB800 proc.

I'd make sure your hardware is D630, not D620. As Bronxteck said, it's pretty easy to put the button front panel of a D630 on a D620. T7200 is a typical D620 CPU laptop reset on wake is a well-known D620 GMA issue when BIOS system password is not set but D620 BIOS stopped at A10 version, D630 BIOS went up to A18...

A T7200 in a D630? Mmm, that sounds wrong: the T7200 is FSB667 whereas the D630 takes FSB800 CPUs. You seem to have a D630 with D620 aspects... What does your BIOS say about CPU (min and max frequency)? If you want native SpeedStep, just don't install NullCPUPowerManagement. You can verify native SpeedStep operation with HWMonitor tool which is found in /Extra/Storage/apps after EDP is installed: you should see the CPU frequency change when you click on the icon in the menu bar. You may need a more recent version of FakeSMC, but that would need to be verified. No harm in trying "as is" anyway...

-> PM

You can select max. frequency with PState drop-down menu, but that's not really the best way to run a EIST capable laptop (for obvious heat/battery/fan reasons). I find emulated SpeedStep on-demand mode to work rather well, including manual frequency selection. A few questions: which exact CPU model do you have (e.g. T7500) ? did you configure your BIOS settings as per recommended way, especially the CPU settings? do you use NullCPUPowerManagement kext in /E/E? what CPU settings are currently selected in your Chameleon boot plist? You wrote you "tried to unselect the emulated speedstep", what did you do exactly? It's not that straightforward to remove emulated speedstep once it's installed... Now, if PState is not to your liking, you could also try native SpeedStep (means no use of NullCPUPowerManagement), but that retains the on-demand CPU power functionality...

I think you need to keep GraphicsEnabler set to 'No' for the injecter (i.e. EVOenabler) to load. But try either anyway.

What's "widget ripple"? Do you have translucent finder menu bar? If it's translucent and you can switch between resolution in the screen preference panel (or through screen icon in menu bar), you have full QE/CI. Look here, you'll see the difference with the menu bar: https://osxlatitude.com/index.php?/topic/2032-dell-vostro-200/ It stays plain grey when hardware acceleration is not active.

Yes, do it that way, especially if your initial version is lower that 10.7.4, since that particular one would break the Hackintosh (ACPI kext issue). EDP takes care of that problem.

Just re-run the EDP system build. That can be done at any time. No need to re-install the OS from scratch! System reset on wake is not something that normally affects the D630. Make sure your BIOS settings comply with the published recommended parameters. You would not have confused D630 with D620 by any chance? Because the D620 GMA does need a system password to avoid that particular wake problem.

I've done some checkings and tests with 64bit mode on my D630 X3100 HiRes with Lion 10.7.5: NullCPUPowerManagement + SleepEnabler kexts are 32/64bit I can boot 64bit mode kernel with "-force64" boot flag (unchecking 32bit in boot plist was not sufficient) in 64bit kernel mode, I have no graphics support as expected (and I loose keyboard + trackpad too -> 'have to use USB input devices) in 64bit kernel mode, I can put laptop to sleep and it will wake Ok, but always with a black screen (-> 'have to reboot!) no boot plist option changed that wake behaviour (darkwake, npci, ...) in 64bit kernel mode no change either, when booting with or without NullCPUPowerManagement + SleepEnabler (although I did experience the odd KP without them) Without graphics support the laptop certainly feels sluggish (very obvious when double clicking on the HDD icon to open up the finder window). To make sure you run in 64bit kernel mode, open About this Mac -> More info... -> System Report -> Software. Check the penultimate line that reads "64bit kernel and extensions". It'll say Yes or No. If you uncheck "32bit" option in Chameleon boot plist but do not select "force64", the D630 still boots in 32bit kernel mode.

I'm not sure about this, but maybe the SleepEnabler kext is 32bit only. You could try to run your D630 without NullCPUPowerManagement and without SleepEnabler to see if it makes any difference. In fact, I'll try it myself... 2 off-topic comments: - I guess you're running in 64bit kernel mode without graphics support (Apple dropped 64bit X3100 kexts after 10.6.2). Yet, you find the system to run much better??? - You kind of hint you get 8GB RAM support only with 64bit kernel. I've no experience on the matter but I would have expected 8Gb to be supported regardless of the kernel mode (OS X does not operate like Windows).

Did you install the EDP package and do a system build? When in there, select VoodooPS2Controller or MyHack controller as opposed to ANV-SLice which I think is default. The system build will install the sleepenabler kext if it's required. If you have not done your EDP system build, do it after running your 10.7.5 combo update but before the reboot.

Try Nawcom's ModCD with a retail version of SL 10.6.3. Then pray... Try and check on the Net if your hardware is supported at all: 1) CPU, with Nawcom's legacy kernels (and/or other legacy kernels) 2) nVidia nForce chipset 3) FX4500 graphics card (I believe that card may have been fitted to some MacPro) Good luck!

Since you appear to have same X1300 card as in my Vostro 200, yes, just copy the 3 related kexts from the Vostro200 SL bootpack to /E/E (EVOenabler + ATIRadeonX1000 + ATI1300Controller). As I said at the bottom of the Vostro 200 guide, you no longer need the Azimutz Chameleon branch because newer versions of Chameleon (r2181 for instance) support the card. Install Chameleon Wizard and you'll be able to set Chameleon boot file to particular version within a recent range. With the use of myHack, yes, kexts in /E/E supersede their equivalent/counterpart in /S/L/E. As such, no need to do anything to kexts in /S/L/E; they can be left as is, i.e. that folder stays totally original/vanilla. What you see on screen with verbose boot flag actually goes by default to the system log. Open up Console tool and you'll see (in Applications -> Utilities). It sounds like a "simple" matter of device id needing to be covered by the IOATA kext. Indeed, the AppleIntelPIIXATA plugin of the IOATAFamily kext I attached above does not refer to device id 2822. If you edit the Info.plist file of the plugin and add your particular device id to the ICH sections, you'll probably get your controller detected and working... For instance, copy the 1st ICH8 SATA section, paste it, rename it ICH8R (or ICH9R or ICH10R depending on revision, although it does not really matter what you call it) and replace 0x28208086 by 0x28228086. http://www.pcidataba...vice_search.y=0 http://www.pcidataba...ils.php?id=1302 Remember to re-run myFix (full) everytime you work on kexts in /E/E.