Jump to content

Memorial

Members
  • Content count

    120
  • Joined

  • Last visited

  1. Verbs wont differ between platforms, they are set by the Intel HDA standard, which you should probably get a copy of. It's good that you have sound. I have never tried to get the internal mic working (AppleAzaliaAudio is playback only and I never bothered to play much with AppleHDA). (Sorry, still haven't had time to look into patching at all).
  2. Are your speakers broken or you just don't have sound? I haven't though about pin configuration and AppleHDA patching for a while. So it will take me a while to respond to this. You should try The KiNG's AppleHDA (partial) patching guide from August 2009 on ProjectOSX if you get a chance.
  3. Try AppleAzaliaAudio.kext if you can. I can look at AppleHDA in Snow Leopard sometime this month (I need to update anyway).
  4. Memorial

    [UPDATED] LiveUSB OS X

    I hope you know that you can cut the size down significantly to fit on a 4.7 GB disc if necessary (especially with SL). I am glad to hear you got it working, I've been meaning to make a Chameleon/EFI hybrid for a while for my machine and apple hardware, but got lazy about it.
  5. 1. Learn to use Google. 2. Learn to add things to the (LoginHook) script. (I bet you forgot to use quotes for the name of the "System Reserved" Volume) 3. Use UUID instead of LABEL in the fstab. 4. If you are using Paragon NTFS (this may also apply to NTFS-3G, which you are using) try this
  6. Memorial

    Steve Jobs on Adobe Flash

    Talking to several iPhone/iPod/iPad developers over the past few months (and having worked with the devices myself), I have to tell you something: most of them don't seem to care about the C/C++/Objective-C limitation. Most serious iDevice developers use Objective-C and Apple's libraries anyway. Also note, there is nothing that says you have to use XCode. All you have to link directly against Apple's Documented APIs. The people that are too lazy to learn Objective-C/C/C++ shouldn't be writing application for Apple''s devices anyway. The more troubling clause for iDevice device developers is 3.3.9, which limits data collection (i.e. which devices are running your app, which OS version, are they on WiFi or 3G, etc). This is problematic for developers as this is useful information, which, if you are a serious developer, you really care about. If you watched the D8 with Steve Jobs, you would have seen his take on this. Apple was pissed off that they didn't know data collection of this sort was happening and third party data collection firms that let developers use their service were registering new Apple devices on their campus and violating Apple's privacy policy on top of that. This situation hints that this clause will be modified shortly, but no yet.
  7. Memorial

    Random kernel panics

    You look at the KP trace that gets printed on the screen if you boot debug=0x100 like I advised.
  8. Memorial

    Random kernel panics

    Non-mac hardware cannot log kernel panics in general (need NVRAM). You have to see them as they arrive. When you boot, or to your com.apple.Boot.plist add "debug=0x100" without quotation marks. This will disable the graphic and display the action panic details on the screen. Take a good picture and post it.
  9. You should be able to install on top of the current OS as long as you disable version checks on the disk. However, clean is better, always. Did some of you guys just delete you /Library/Receipts or screw with permissions of the Receipts? How did any of you get to the point that Disk Utility is blanking on the installation receipts?
  10. Memorial

    ntfs cause kernel panic!

    If you don't need ntfs, move it out of /S/L/E and clear extensions. This is odd though. You might want to post the output of the kernel panic as a whole (I know it's a pain to write it down, but it might be helpful).
  11. Editing /etc/fstab generally works, unless you have Paragon NTFS installed. If you "never" want to be able to mount the windows partition in OS X ( if you do mount it, don't mount it rw too often, people tell tales of corruption and I have has this happen myself) then you can add a launchd daemons that will unmount the specified file system whenever a mount event occurs. For the later, do the following: Make a file /Users/Shared/unmount (or w/e else you please) with the following content: #!/bin/bash diskutil unmount <insert UUID of Windows partition or /dev path> Next in terminal: chmod +x /Users/Shared/unmount Then, put a file /Users/<your user>/Library/LaunchAgents/unmount.plist with the following content: <?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>Label</key> <string>unmount</string> <key>ProgramArguments</key> <array> <string>/Users/Shared/unmount</string> </array> <key>StartOnMount</key> <true/> <key>RunAtLoad</key> <true/> </dict> </plist> Reboot and your windows 7 partition will always unmount as you are using one user (if you have multiple users, you can put the second file in /Library/LaunchDaemons/) To fix your mounting errors, run chkdsk on you windows partitions, it might help unless there is that annoying partition misalignment that windows loves so much. You can also do similar things with /etc/rc.local I believe. Also, for the love of god learn to use Google or any other search engine for that matter (searching the title of this topic will provide you with exactly what you need).
  12. Scrolling takes a bit more work. Look into the Voodoo driver or the older FFScroll adaptations.
  13. With a good viewing angle. P.S. Do you really need Flash that bad?
  14. Memorial

    iMac doesn´t boot

    If it was actually boot from DVD, it shouldn't hang kernel panic. Clearing your PRAM will not really help (but you can try it, hold down command, option, P, R http://support.apple.com/kb/HT1379). Either figure out why it is kernel panicking and fix it. Or reinstall.
  15. No*. *Unless you assemble your own iPhone like hardware and call it a PC...Or you write your own VM.
×