Jump to content


  • Content Count

  • Joined

  • Last visited

About MR2nice

  • Rank
    InsanelyMac Protégé
  1. If I am using a firewire audio interface then I wouldn't need to worry about patching the audio in the DSDT, right? If that's the case then I can probably just disable the onboard audi from BIOS.
  2. Hi blackosx. I have a quick question. I want to purchase the retail Snow Leopard, but I see on the site that they are only going to sell the Upgrade version. How would I get the full retail Snow Leopard or is the Upgrade DVD the same?
  3. Thanks for the guide. I've tested this method a few times and can confirm that this works for both the 10.5.7 and the 10.5.8 Combo Updates. I was not able to see the option "Start up automatically after a power failure" in System Preferences Energy Saver. Was it suppose to already be there after the install?
  4. Updated to 10.5.6 successfully. Had to reinstall Audio kext to get sound back. However, the System Profile could not pull up the Hardware info: "There was an error while gathering this information." Just saw another problem. The CPU Processor shows incorrect speed. Anyone have the same issue?
  5. Success! Thanks munky for this guide! Here's what I did: 1. Installed Retail 10.5.4 2. Followed your guide to install Boot from EFI partition 3. Using Software Update, updated it to 10.5.5 4. I wasn't able to get the IOAHCIFamily.kext to load until I boosted the version number (from 1.0.4 to 1.0.5). So now everything is working. I noticed something strange just now. My audio is working without having to patch the AppleHDA.kext into the S/L/E. The time stamped shows Jun 10, 2008, which I believe is the original from the 10.5.5 update. If this is true, then I am pretty much running Leopard without having to touch S/L/E. I am still new to this and have been doing extensive tests for different variations of install methods that are available on this forum. Thus, I installed 3 HDDs to test 3 different methods. They all work. I have questions regarding the 2 kext files that are currently in my System\Booter\ AppleDecrypt.kext and dsmos.kext Are these 2 the same, in terms of functionality? If so, which is the prefered to keep? Thanks again!!
  6. Yes, this would be great as I found out from my ongoing test this morning that for some reason after I installed the Logitech Control Center, the Configure page did not detect my MX600 Laser Cordless Mouse. However, it detected the S 530 Keyboard. So I browsed to the System\Library\ and noticed that the Extensions.mkext had updated with a new date/time stamped. So I copied the Extensions.mkext to my boot-partition. Rebooted, checked the Logictech Control Center and this time my mouse was detected and ready to configure. My question about the "sync-tool" is this. For those who disabled the "MacLoader" from automount, could this tool work? Thanks.
  7. I did some testing tonight with this method both on internal HDD and external USB HDD. With the internal HDD, I installed the Retail 10.5.4 and then updated to 10.5.5 using the MacOSXUpd10.5.5.dmg. Then I patched audio and copied the Extensions.mkext and mach_kernel to my boot-partition. Rebooted and everything was good. With the external USB HDD, installed Retail 10.5.4 and this time I updated through Apple's Software Update. It rebooted by itself the first time and the second time it booted up to 10.5.5. Again, I patched audio and copied the Extensions.mkext and mach_kernel to my boot-partition. Rebooted and here I am typing this post to give my feedback. Thanks Macinized and roisoft for this!
  8. Thanks Cm for the help!! I finally got a stable Leopard and everything is working great!
  9. I have the same board and I can say that it does works. What method did you use to install your OSX? Here's what I found out. I used boot-132 via GA-P35-DS4_ISO.iso. Afterwards, I was never able to get my system to Shutdown no matter which methods available on this forum. My last resort was the OpenHaltRestart.kext and it still didn't work for me at first. So I knew that something wasn't right with my setup. I decided to look inside the Extensions.mkext to see what kexts were inside and then cross-reference them with other modded boot-132. Of the 29 kext files that were originally in the GA-P35-DS4_ISO.iso, I started my test by removing the kexts I think I didn't need for this board and after many many attempts I finally narrowed the list down to just 7. At this point I had already tried 3 different Shutdown fix: GigabyteP35CC, poweroff_fix, and OpenHaltRestart.kext. I rebooted and ran -v -f. Once in I shutdown and to my surprise it worked. I then ran the uninstall.sh from the poweroff_fix and rebooted. Again, I shutdown and it still works. If anyone used the GA-P35-DS4_ISO.iso boot-132 with the P35-DS3L board then you may need to remove certain kexts from the boot loader. Although it allowed you to install properly, Shutdown may not work afterward because keep in mind that the GA-P35-DS4_ISO was modded for that board. The GA-P35-DS3L.iso didn't work for me. It crashed halfway during installation. So here are the current kexts that I have in my Extra\Extensions\ AppleDecrypt AppleHDA AppleSMBIOS HDAEnabler IntelCPUMDisabler IntelPIIXATA RealtekR1000 I then decided to redo a clean retail Leopard installation to my main partition from an external Leopard USB HDD and then used just the OpenHaltRestart.kext. It works!
  10. I have a couple of questions if any experts can guide me to the right path. I am currently using the GA-P35-DS4_ISO.iso to boot my retail Leopard DVD and it works great. None of the other .iso worked for me, ironically not even the GA-P35-DS3L.iso. However, the 10.5.5 update failed for me. Upon more research on this forum I've found out that's because of the AppleIntelCPUPowerManagement.kext. I now have a working 10.5.5. Then I started to look at the differences between these ISO's to hopefully perfect my installation so that it can perform future updates without any issues. I noticed that inside the GA-P35-DS4_ISO.iso, when I mount the INITRD.IMG I only see the "Extra" folder and inside it is the Extensions.mkext. No "Extensions" folder was seen. All of the other ISO's such as GA-P35-DS3L, generic, and BOOT-KABYL-BUMBY they have the "Extra\Extensions" and a list of many .kext files. On my Root drive, I see the "Extra" folder and inside it is the Extensions.kext. No "Extensions" folder either. My questions are: 1. How can I see what's inside the Extensions.mkext? Does this file contain a list of kext files similar to the ones you see inside the Extensions folder from other boot-132 ISO? 2. Would it work if I create a folder "Extensions" inside the "Extra" folder on the Root and then add to what I think are the proper kexts for my build? The following files are the ones I'm planning to add to the Extensions folder: Most of these files I grabbed directly from my System\Library\Extensions AppleACPIPlatform AppleAHCIPort AppleHDA AppleIntelIntegratedFramebuffer ; not sure if this is needed, but I saw it in other ISOs AppleSMBIOS dsmos IntelCPUPMDisabler IOAHCIFamily SMBIOSEnabler Thanks in advance for any help. Greatly appreciate it.
  11. MR2nice

    System Profiler

    Thanks guys for the fast reply. I started with 0.1.3 and then went to 0.1.5. Everything is working correctly now including the left panel now showing Hardware at the very top and my graphics/display now display the correct model. You guys are awesome!!
  12. MR2nice

    System Profiler

    Hello, I've been reading through the forum extensively and could not find a solution to my problem so I'm hoping that some experts can point me in the right direction. My problem happened after I installed the NVInstallerV.41.pkg to fix the QE and CI issue. Now when I go to the System Profiler, I noticed that for some reason on the left panel where "Hardware" used to be has now changed to "SPHardwareDataType" and when I select the Graphics/Displays I see that it says "I Can Has Model?" I am using BFG Nvidia GeForce 7800 GT. I've attached a screen shot below and marked my areas of concern in red. Hopefully someone knows how to fix this. Thanks.
  13. MR2nice

    Toast 9 Titanium Problem

    This was exactly the same thing I experienced. I tried almost everything suggested from Roxio's own forum to uninstalled, reinstalled, update CDRom firmware, etc. The thing I found out was that it worked on 10.5.2 but after you update it to 10.5.3 it will bounce a couple of times on the Dock and then disappeared. I tried Toast 8 and 9. Both failed after the update. However, all of my other softwares are perfectly fine. With that, here's what fixed my issue: I installed the NVInstallerV.41.pkg using Pacifist and selecting my video card RAM (256) along with the frameworks package and kexts. After that I rebooted and installed Roxio 9 again and to my surprise it finally launches completely and now works fine.