Thanks again to Giacomoleopardo for starting this thread and to all the members!
I was able to get everything working properly, including sleep + auto sleep + wakeup of the mouse & keyboard.
I was building a computer for my wife and was constantly tinkering with the build as it was not waking up from sleep properly. I was pulling out my USb bus analyzer to confirm that the mouse + keyboard were not re-enumerating properly when she suggested that the build was too complicated.
I stopped to look at some verbose boot ups and noticed the system hanging on waking up the onboard Bluetooth + wifi card.
I then had the idea to stop and take everything out but the bare board (no vid card, removed mini-pci e bt/wifi card) and start the build again from there.
Roughly,
0) updated the bios to f3d, took out the motherboard battery to clear the bios values, reinserted the battery, loaded default values for the bios, turned off pll voltage, set the first display to igfx
1) I loaded the Mountain Lion 10.8.4 installer via Unibeast onto a USB stick
2) Used the USB stick to load it onto an SSD
3) rebooted using the USB sticks loader to load my SSDs ML installation
4) I then used MaciASL to save the current DSDT
5) took the DSDT to another Mac and loaded the patches as per Giacomoleopardo's post, I chose the version for HD4000 (no vid card)
6) I then copied the generated DSDT to the SSDs desktop and ran Multibeast as per Giacomoleopardo's post
7) I then did the work to generate the ssdt.aml file and used Chameleon Wizard to set up the boot.plist file to use it and set the machine type to mac mini i7
8) I then confirmed that sleep / autosleep was working and that the mouse and keyboard were re-enumerating properly (this is with darkwake=0)
9) I set up speakers and verified that the motherboard line out was playing sound to them, I did NOT test the motherboard mic input
10) i used trim enabler
What doesn't work?
1) Well I've noticed that "System Report" shows the one memory stick is 1600 MHz and the other is 1333 but they really are both 1600 sticks and the bios shows them as both running at 1600
2) I've noticed that the ethernet cable needs to be connected at boot time for the adaptor to work. If you start it without the cable in and then connect it the machine assigns itself an ip address.
As an experiment I tried reinstalling my Nviidia gt 240 card and switched to the bios to start with it and got a kernel panic. I have no idea why this happened. Perhaps I need to use the Maciasl patch that has support for the video cards?
The wife is happy with the build. Thanks to everyone for your help. Feel free to ask questions.
