Jump to content

The Gonif

  • Content count

  • Joined

  • Last visited

About The Gonif

  • Rank
    InsanelyMac Protégé
  1. Quick question about Chameleon and Boot 132

    Ah, now it is clear. I had figured they must be about the same thing, since you'd think that you'd need a boot loader + an EFI emulator for both booting to install DVD and booting into the installed OS, but I guess not. Thank you for taking the time to explain this!
  2. Quick question about Chameleon and Boot 132

    Anyone? Was this a dumb question?
  3. Hi, I installed Leopard on my Abit IP35e about a year and a half ago... it worked great but then an update killed it and after a lot of struggling I sort of gave up on it. Now I'm getting the itch to try again. Things have changed a bit in that time. I'm trying to catch up but I'm confused about Chameleon. It emulates EFI, right? And is it also a bootloader? Some of the install guides use both Boot 132 and Chameleon, but from what I read it seems like all you'd need is Chameleon. Can someone explain what these tools are used for? I'm trying to get a pure vanilla installation going. Not sure if it's possible, but my mobo has a P35 / ICH9 chipset, which is identical to some of the Gigabytes, I think. Thanks!
  4. How much do you trust your hackintosh?

    So did you all consult the hardware compatibility guide and buy your PCs based on that? And then you can just use a generic OS X install DVD and PC-EFI?
  5. How much do you trust your hackintosh?

    Hey guys, for those of you who have had no trouble with your hackintoshes, is your hardware similar enough to an actual Mac that you can just install OS X on it, or do you have to use an OSX86 distribution? How do OS updates work, can you just install it or do you have to take special steps? I had a PC with an Abit IP35-e motherboard and NVidia 8600GTS video card that I managed to get OS X installed on, but I had lots of problems with the audio and video drivers, and ultimately an OS update killed it and I gave up and bought an iMac. But a friend of mine wants to get a Mac to try it out and he's wondering if he can buy a PC laptop and run OS X on it. Is there any way that "normal" people could make this work or is it always a struggle with hacked drivers and kernel extensions and special steps every time you install a software update? Thanks for all the good input!
  6. About to give up

    I recently built a new PC, and thought I'd install OS X on it to try my hand at some Mac OS/iPhone software development. The motherboard was an Abit IP35-e, the processor a Core 2 Duo, and the video card an NVidia 7600GTS. After struggling with it off and on for several months, I think I'm about to throw in the towel and declare Apple the victor. For a while, 10.5.2 ran reasonably well, although it wouldn't reboot or shut down; that and the occasional graphics glitch caused me to upgrade to 10.5.4 which broke everything, and I've been unsuccessful in getting things going ever since. If anyone with this setup has any advice to share, I'm all ears. I'm kind of thinking that maybe most hackintoshes use that Gigabyte motherboard, though, and that the Abit just has too many differences to really work. Regardless, thanks to everyone in the forums for their tireless efforts and helpful attitudes. I couldn't have gotten as far as I did without you.
  7. AppleACPIPS2Nub for Leopard only

    Hey guys, I can't get it working. What am I doing wrong? So I lost the PS2 keyboard when I upgraded from 10.5.2 to 10.5.4. I tried a bunch of things to fix it, but basically this is how it stands now: AppleACPIPlatform.kext is in the Extensions folder, version 1.0.3 The new AppleACPIPS2Nub.kext is in the plugins folder of the above kext ApplePS2Controller.kext is in the Extensions folder, version 1.1.0 Is there something missing? Why won't it work?
  8. Slight graphics lag -- is this normal?

    Hey guys, come on... nobody can confirm that this is normal for them or not normal for them?
  9. Leaked nVidia GTX 280

    You know, I've always wondered why that is. Is it because Mac marketshare is too low for nVidia to spend the time writing OS X drivers? If so, maybe that will change as more people switch to Macs. It's frustrating because it seems that the video card manufacturers stop at nothing to insure their Windows drivers are as highly performing as possible, and then they don't even bother getting most the cards even working on Macs.
  10. Poor font smoothing?

    Changes take effect on a per-application level. The next time you launch an app, it will use the new antialiasing level.
  11. Hey everyone, I've got 10.5.2 running great, but one thing is kind of odd so I thought I'd ask to see if it's normal. If I click on a window's title bar (any window) and then rapidly move the mouse back and forth, the cursor icon slightly detaches from the window as the two of them zigzag around the screen. It's as if the window can't quite keep up with the speed of the cursor. Or maybe another way to put it is that it's as if a piece of rubber band connected the cursor and the window. As the cursor jerks around the screen, the inertia of the window sort of stretches the rubber band and the window falls behind a bit. Does anyone else experience this? If not, any idea what's causing it or how to fix it? Everything else seems fine. Quartz Extreme is supported. This is on a 2.2 GHz Core 2 Duo machine with an 8600GTS video card. Thanks!
  12. Shutdown is not shutting down.

    Hey, I was looking at the code for that poweroff fix, and it looks like it uses CHUD to disable all cores but one. It also looks like the code is called when the computer starts up. I must be misunderstanding this, because nobody's complained about it, but this shutdown fix isn't slowing down our computers by only enabling one core at bootup, is it?
  13. Hi everyone, So my original plan was to build a new PC to replace my old Pentium III machine and then buy a new Mac Pro to replace my old G3 tower. I build the PC, put Windows XP on it, and then with a spare drive started experimenting with getting OS X running on it. Well, it runs pretty well! It doesn't like to shut down, but boy is it fast! It works well enough that it made me reconsider buying a Mac Pro. So I was wondering something: all of us here have turned PC hardware into Macintoshes. And most of us have some quirks with it (won't shutdown, random crashes, inconsistent video card support, etc). So how many of you would trust your great, new OS X experiment enough to make it your primary computer? Keep all your documents on there, your resume, your taxes, your music, all your family photos? Has anyone actually lost any data due to an OS update gone bad or anything like that? What do you all think?
  14. Well, I don't really understand how all this works technically, to be honest. For my setup, all I did was pull the usr/standalone/i386/guid/boot0.guid file off of the installation DVD and drop it into the root of my Windows XP hard drive. The name of the file shouldn't matter because in boot.ini (in Windows) you put a reference to that file. So if your file is called "boot0" then in C:\boot.ini you put "C:\boot0=OSX". If the file is called ILIKEGOATS then in boot.ini you'd put "C:\ILIKEGOATS=OSX", right? I don't have an official Leopard DVD on hand at the moment, but my guess is that the file is actually called "boot0" and is inside of the usr/standalone/i386/guid directory on the DVD. So look for this file and copy it into C:\ on your Windows drive and then add that line to boot.ini (also on the Windows drive) and that should be all you have to do. I didn't have to touch anything on my Leopard drive at all for this to work. Give that a try and let us know how it worked out.
  15. @Wppley, thanks for making this post. I have XP installed on one drive and OS X on a second drive, and I've been searching without luck for a way to dual boot them (other than using the BIOS) for weeks now. Your method worked perfectly! @Ayce, the files you're looking for may be on the Leopard installation DVD, not your hard drive. Put your Leopard DVD into your Mac and go to usr/standalone/i386/guid and you should see the boot0 file. In my case, there was a file called boot0.guid, but it's possible that this is really just the usr/standalone/i386/guid/boot0 file that someone renamed to "boot0.guid" to make it clear which boot0 it was, since there's also a different boot0 file in usr/standalone/i386. Anyway, just wanted to say that this method totally works if you have OS X installed on a separate hard drive from XP, and are using the GUID partition scheme instead of MBR.