Jump to content


  • Content count

  • Joined

  • Last visited

About obijohn

  • Rank
    InsanelyMac Protégé
  1. Whew! Finally figured it out. When I compared com.apple.Boot.plist on both partitions, I thought they were identical. Turns out there was a very slight difference. Here's the version that was on my tiger partition: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Kernel</key> <string>mach_kernel</string> <key>Kernel Flags</key> <string></string> <key>Timeout</key> <string>4</string> <key>Boot Graphics</key> <string>Yes</string> </dict> </plist> And here's the version that was on my leopard partition (which didn't throw an error): <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Kernel</key> <string>mach_kernel</string> <key>Kernel Flags</key> <string></string> <key>Timeout</key> <string>4</string> <key>Boot Graphics</key> <string>Yes</string> </dict> </plist> Spot the difference? In the DOCTYPE section, the leopard version has "Apple" and the tiger version had "Apple Computer". Well, when I changed it to just "Apple", the tiger partition boots without any errors now. I have NO IDEA why it didn't throw an error on the other hard drive but it did on the new one. Anyway, now I can sleep peacefully before Christmas!
  2. After further investigation, it appears that Unsupported.kext is NOT the culprit. The "error parsing plist" is displayed immediately before any of the kexts are loaded, and Unsupported.kext just happens to be the last before the 5-second pause and then the boot continues. The only thing different after putting in the new cloned HD is the UUID of the drive. Perhaps there's a plist somewhere that has the old UUID, which is loaded very early on in the boot process? It's not com.apple.Boot.plist, I have not EFI strings or anything like that in there. Is there another place I can look?
  3. One more little clue I just found. When I boot with the -v option into the Tiger partition, it spits out a bunch of kexts it's loading and the one directly before the "error parsing" message is System.kext/Plugins/Unsupported.kext I checked it's Info.plist and that seems fine. I have a second backup of my extensions folder and I copied the System.kext from the backup, but I still get the error. I repaired permissions as well, so that's not the problem either. This has really got me stumped!
  4. So I got myself an early Christmas present, a new 750GB hard drive for my hackintosh laptop. My setup is a dual-boot of Leopard and Tiger. I partitioned the new drive and then cloned the laptop's two partitions to the new drive using Carbon Copy Cloner at the block level (I had to boot into Leopard to clone the Tiger partition, and vise versa). I then re-install Chameleon as the boot-loader on the new drive, and after this everything seemed to work except for one small hiccup. The first partition, Leopard, boots without errors. When I select to boot the Tiger partition from the Chameleon boot prompt, I immediately get a message that says "Error parsing plist fileDarwin/x86" and then "Pausing for 5 seconds", after which it boots into Tiger just fine with no other errors. Running dmesg doesn't show the error, it just begins with the info right after the pause as it starts the regular boot. I did some searching, but every place I saw this error mentioned, the person could not boot beyond that point, either freezing there or going back to the boot menu. I can't find another situation where it went straight from there into the regular boot process, so I'm kind of stuck on how to fix this error as it adds an additional 5 or 6 seconds to the boot time. Most mention com.apple.Boot.plist as the culprit, but I've already checked the file on both partitions, and they are identical with no added options by me other than changing the timeout to 4 from 8. Why would it boot Leopard without this error but throw it when booting Tiger? If it's not com.apple.Boot.plist, what other plist file could it be? Any suggestions? EDIT: Solved! Turns out it WAS com.apple.Boot.plist, although the "error" was not obvious at all. See my post #4 below to fix if this happens to you.
  5. ATI Framebuffer development

    I got very excited when I read this, but it doesn't work for me. My card is X300. I renamed ATIRadeonX1000GLDriver.bundle to ATIRadeon9700GLDriver.bundle, then in Contents/MacOS renamed ATIRadeonX1000GLDriver to ATIRadeon9700GLDriver. I edited the Info.plist and changed every "X1000" to "9700". But I still don't have QE/CI (I just have software CI, but no QE). I am so sad!
  6. ATI Framebuffer development

    Slice, need a little help. Finally got ATI.kext and ATILead.kext to load properly, but system hangs after loading them. No crash is reported, no kernel panic, just a hang. Attached are my dmesg dump (not loading ATI.kext or ATILead.kext since I can't run dmesg after they hang, but not using Callisto either), the "RadeonDump -r 0,100" dump, and the "RadeonDump -i" dump. According to ioreg, my device address is 0xffffffffd000000, so I tried both "0" and "0xd0000000". I tried "RS300", "RS400", "X300", "9700", "M24" and "M22" for the model name in the ATILead.kext info.plist, but I'm not sure if the model name is the problem. One thing odd is that RadeonDump doen't give an EDID, could that indicate an incompatibility with my hardware? Also, for linebytes I used 288000 (1920x1200/8) but I'm not sure if that's the correct number for that resolution of my laptop monitor. EDIT: added relevant part of system.log. After it hangs during boot, if I reboot in safe mode the reboot dumps a lot of irrelevant info into the system.log, so instead I rebooted into Tiger (dual-boot here) and copied the last part of system.log from the last boot of Leopard that hangs. There don't appear to be any errors in the log, so I'm kinda at a loss. Let me know if you need any more info. radeondump_i.txt radeondump_r.txt dmesg.txt systemlog.txt
  7. ATI Framebuffer development

    I'd like to try these two kexts (ATILead and ATI) but I'm not sure what to edit in the Info.plist of ATILead.kext. I've read through the thread but I'm having trouble understanding exactly what I should edit. My card is a Radeon X300 Mobility (it shows up as an M300 (M22) under System Profiler, although it's really supposed to be M24), the device ID is 0x5460, and right now I've got native resolution of 1920x1200@32 using Callisto (but of course no QE/CI). It's a PCIe card, would this possibly work with the kexts? I understand that I'm supposed to edit the Info.plist to add my device ID and the resolution, but I could use a little help on where to put this info and in what format.
  8. OSX86 on macbook

    You should be able to install a retail version of Tiger, instead of the modified osx86 versions we have to use.
  9. Update woes

    Use the Mysticus C updater
  10. Its time to update!

    See Complete 10.5.3 and Latest Updates
  11. No, it's not. It might be illegal to reverse-engineer a patented software algorithm (although the legality of software patents is being challenged in many countries). But it is not illegal to simply reverse-engineer some software. It's not even a violation of copyright (which protects the right of the copyright holder to distribution of the work). That's why it's never been illegal to reverse-engineer the format of a Microsoft Word document. And it's not illegal to reverse-engineer a driver for some hardware. Almost. Copyright deals with the right of the owner of the copyrighted work to copy and distribute the work, and makes it illegal for you to copy and distribute it yourself. The EULA is a license, created by the copyright holder, which specifies how you can use the work which is being distributed to you. Most EULA terms which have been challenged in court have been struck down because it is a one-sided "contract" without the necessary offer, acceptance, and consideration by both parties. The question is this: Is it illegal to purchase a retail copy of Leopard and then re-sell it? It might be in violation of the EULA to do so, but it's not a violation of copyright law. It would be a copyright violation if you made a copy and then sold (or gave away) that copy. Another question: Is it a violation of Apple's trademark to say that the computer you're selling will run OS X? If you answer "yes", how then can Apple legally say that a Mac can run Windows? You can't have your cake and eat it too. Now, if you stick an Apple logo on the box, you are violating Apple's trademark. But simply making a claim about your product? No. But here's the tricky question: Are any of Apple's rights (copyright, patent, and trademark) being infringed if you take a legal piece of hardware that you purchased and built, a legal piece of software that your purchased at retail, install that software on that hardware, and THEN re-sell it (along with the retail disk of the software)? Since it's not illegal to reverse-engineer a hardware driver, and it's not illegal to re-sell a software disk, and it's not illegal to say that your hardware will run another company's software, I don't think Apple can claim any of their rights are being infringed by putting it all together. BTW, I am a lawyer.
  12. no network after install

    Yes, Tiger allows you to configure the settings for your ethernet card. Go to System Preferences, select Network, in the second drop-down list select your ethernet card. There's quite a bit you can set, and under TCP/IP you can set such things as DHCP or manual IP (and if manual you can set everything).
  13. VMWare Fusion vs BootCamp

    Slow down sparky. You say you're going to be doing video editing? Then boot camp is definitely the way to go. Running a VM in fusion is "useable" for everyday stuff like word processing and web browsing or anything that doesn't put a strain on your hardware. Video editing puts a definite strain on your hardware, CPU and GPU. Granted, not as much as ray tracing and 3d rendering, but a strain nonetheless. You can give it a try, but I promise your results will be less than satisfying. However, boot camp allows you to boot into the "pure" OS as it was meant to run on the hardware. The difference is quite measurable.
  14. Mac Os X Tiger Lite

    How old and what specs?