Jump to content
InsanelyMac Forum

schnogg

Members
  • Content count

    25
  • Joined

  • Last visited

About schnogg

  • Rank
    InsanelyMac Protégé
  1. This guy might be on to something. From my experience, everything seems to work correctly, except for Identifying the processor. http://www.insanelymac.com/forum/index.php...p;#entry1284918
  2. No there is not. This isn't called a PCintosh, its a Hackintosh: You have to hack it together yourself. You are going to want to read and research to find out what people have done that works and what doesn't work. I have the lifehacker setup and i'd say its 95%. I'm still working on getting the CPU recognized correctly. The server version is largely like the client version. The big difference is that the server has a phone home validation feature. If you just want to run some services, you can do it wihout setting up SL server. I'm not sure why people use windows, but I have heard that strange behavior happens with ACPI when you flip back and forth between windows and snow leopard. Chameleon is basically a boot loader that emulates some of the efi magic that is built into apple macs. The newer versions do other cool stuff like inject codes and drivers into the kernel at boot time. The only reason to use 10.5 now is if something isn't supported in 10.6. With Chameleon, you can always boot into 32 bit mode by using arch=i386. Good luck.
  3. I'm pretty psyched about this. Hopefully it will not make FCP tell me that it needs Rosetta anymore. I'm a little confused about using the CPU codes. Do you need to put in the base64 encoded hex value by itself? Or do you put in the base64 and the hex value together? For example, C2D is 0103, the xlate page on that web site translates that to the base64 version, AQM=. UPDATE: I used AQM=0103 and it says the processor name is Intel Core 2 Duo. Installed Silverlight fine.
  4. schnogg

    Netflix DRM 8152 ***Snow Leopard***

    Many have this problem, but nobody knows how to fix. I think that the Netflix eror comes from the platform information. I mean, it is trying to identify what type of computer you are running. When it gets to the processor, for some reason, the computer can't identify it, so it is not reported, and throws an error. I think it is related to the fact that I can't install Silverlight, Final Cut Pro, Office. When I look in system profiler, Processor Name isnt' listed. For me, it is the last single item before I have a perfect install. I've tried a few different things. Changing the About this mac information doesn't make a difference; its purely cosmetic. I tried some different processor ID in DSDT and tried changing the MacPro3,1 to different values, to no avail. I think that the SMBIOS is responsible for this reporting, but I'm not smart enough to hack it up.
  5. Yeah it is quite confusing. I'm really hoping to make some sense of this issue. I don't see why system profiler doesn't just get the id information from the processor? How does the system profiler get this information?
  6. schnogg

    Booting in 32bit takes forever!

    I find the same thing, so I just boot to 64 always.
  7. I'm starting to think that this might be fixed in DSDT. I just wish I knew enough about it to debug.
  8. schnogg

    Can't see other Hacks on network

    This sounds like the issue that I had to fix with the Bonjour broadcast not working. Look at the part in this post about running the ifconfig command at start up to enable permiscious mode. Under Troubleshooting, Bonjour at boot http://www.insanelymac.com/forum/index.php?showtopic=181903
  9. This is an annoying problem. I am having it as well. I have the LifeHacker board, the GA-ep45-ud3p running a e8400. I used the lifehacker guide with the pkg installer. I just tried the fakesmc.kext form netkas, but I still get no processor name info in system_profiler SPHardwareDataType -xml
  10. I had a pretty good install going except for sound until I installed Little Snitch beta2. Now It just is stuck in a reboot loop where it boots, reloads all extensions like the cache has been flushed, then reboots again. I removed /System/Library/Extensions/LittleSnitch.kext, but the issue persists. Is that all there is to removing little snitch? My setup: IP35 (Yukon2 Ethernet, ALC888 Audio) E8400 Geforce 7300GT 256MB
  11. schnogg

    OSX Leopard 10.5.7 + Nvidia 7300

    So, my issue was that after 10.5.7, I had some drivers that were conflicting. I followed someone else's instructions. The trick was to use these commands to remove kexts beginning with Ge and NV. Then, install 9f23 and efistudio from here: http://scottdangel.com/blog/?page_id=20, then install the efistring for Geforce 7300 GT 256, reboot, all good. rm -Rf /System/Library/Extensions/Ge* rm -Rf /System/Library/Extensions/NV* rm -Rf /System/Library/Extensions.mkext Then install 9f23, efistudio Run efistudio to install efi string. reboot. video goodness. vram reported correctly, gl working, qe working, ci working
  12. schnogg

    8600gt not enough vram?

    didn't help. I'm not sure what the problem is here.
  13. schnogg

    Drivers for Nvidia Geforce 9400 GT - Success

    Nice work. Would this possibly be a fix for my 7300 GT that stopped working with compositing after 10.5.7 update?
  14. schnogg

    OSX Leopard 10.5.7 + Nvidia 7300

    That sounds easy. Where do I find this titan.kext plz?
  15. schnogg

    8600gt not enough vram?

    I've got this exact same problem with my Geforce 7300GT after updating to 10.5.7. I've been banging my head on the desk for a week now. My symptoms are: Blender stopped working VLC just shows a black screen. Quicktime crashes when it tries to display a video. Essentially it seems that for some reason now, the amount of video memory is being reported wrong. The side effect of this is that the compositing engine now refuses to do its job. I thought that maybe changing the Configuration.plist file in cd /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/Configuration.plist so that the threshold of how much VRAM it needs is 0. That might make it work, but I dunno. If I don't come back, its because it failed.
×