Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About p.c.27618349

  • Rank
    InsanelyMac Protégé
  1. Getting KPs when using an internet browser?

    As far as I know, 32-bit systems can't handle more than 4GB of RAM. While that shouldn't cause your system to crash, you COULD try removing a stick or two of RAM to get it under that number and see what happens.
  2. Thinkpad Upgrade 10.6.4 to 10.6.6

    I also tried rolling back the IOUSBFamily.kext using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]. That didn't work - in fact it caused my ApplePS2Controller.kext to start throwing visible error messages saying that there was an error in installation. I reverted back to 10.6.4 for the time being, since I need my laptop fully functional tomorrow. When I get the chance, I'll try upgrading via Apple Software Update (I upgraded via a manually downloaded combo update earlier) and fully remove the SleepEnabler.kext before doing so rather than replacing it. Looking at the verbose boot after I reverted, it picks up something via ApplePS2Trackpad. PS/2 has nothing to do with USB, whose kext Apple messes with in the update. So how does it get affected by the update? And in my experience, the ApplePS2Controller.kext enables both the trackpad AND the keyboard - yet when I updated, only the trackpad didn't work rather than both keyboard and trackpad not working. Very strange.
  3. Hi all, I just upgraded my Thinkpad from 10.6.4 to 10.6.6. I replaced the SleepEnabler.kext in the Extra folder with the new one tailored for 10.6.6 with the pmVersions and all that before I upgraded/restarted. It booted up fine, everything seems to be fine, but then sleep problems popped up. It could sleep but it got the infamous "Error 0192" on boot-up. Sleep worked before on 10.6.4 without the Error 0192 perfectly fine, though multiple sleep-wake cycles seemed to make the system more unstable until it crashed. I tried replacing the new SleepEnabler.kext with the old one and booting with the "pmVersion=21" flag but that did no good either. I also noticed that my trackpad/trackpoint didn't work either. I had used ApplePS2Controller. Looking at the verbose boot-up, it seems that "IOHIDSystem: Seize of ApplePS2Controller failed." (or was it ApplePS2Keyboard...i don't remember) I tried VoodooPS2Controller, but that failed period. Didn't even work out of the box. I have a clone backup of 10.6.4 to revert back to, but I really don't want to. This AppStore really is something.
  4. GT 240 Woes

    Never mind, I've gotten it working with the Lizard tool.
  5. GT 240 Woes

    I did give it a go. Only the "Add EFI String" gives that assigning a zero to a boolean error that was mentioned above, b/c OSx86Tools was orphaned and the final version wasn't built for Snow Leopard. It's great that it works with yours, but it doesn't with mine. That's why I was asking how to edit the com.apple.Boot.plist file manually.
  6. GT 240 Woes

    Sorry for the confusion but i editted the original post around 10-20 min after i posted it to tell you the OSx86Tools does NOT work in Snow Leopard... Guess i editted it a bit too late... sorry But that aside, even when editting the one in /L/P/SC/ and the one in /Extra, the EFI edits do nothing, as mentioned above. Here's my boot plist for your reference: <?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>Boot Graphics</key> <string>Yes</string> <key>Quiet Boot</key> <string>No</string> <key>Timeout</key> <string>5</string> <key>arch</key> <string>i386</string> <key>Legacy Logo</key> <string>Yes</string> <key>device-properties</key> <string>6c0200000100000001000000600200000d00000002010c00d041030a000000000101060000027fff04000e 0000004e00560050004d0000002000000001000000000000000000000000000000000000000000000000000000220000 005600520041004d002c0074006f00740061006c00730069007a006500000008000000000000401c00000064006500760 06900630065005f00740079007000650000000f0000004e5644412c506172656e740e0000006e0061006d00650000000b 000000646973706c617922000000400030002c006400650076006900630065005f00740079007000650000000b0000006 46973706c617922000000400031002c006400650076006900630065005f00740079007000650000000b00000064697370 6c6179100000006d006f00640065006c000000180000006e5669646961204765466f72636520475432343020000000400 031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d61631400000040003000 2c006e0061006d0065000000120000004e5644412c446973706c61792d4114000000400031002c006e0061006d0065000 000120000004e5644412c446973706c61792d4220000000400030002c0063006f006d00700061007400690062006c0065 0000000e0000004e5644412c4e564d6163100000004e005600430041005000000022000000d38d34d34d34d34d34d37d 34d38d34d34d34d34d34d34d3bd34d34d34d341e00000072006f006d002d007200650076006900730069006f006e00000 02c0000006e5669646961204765466f726365204754323430204f70656e474c20456e67696e65205b4546495d</string> </dict> </plist>
  7. GT 240 Woes

    yup, the addition of those two files works a charm. new question: once i have the EFI string, how do i put it in com.apple.Boot.plist? i copied a boot.plist from /Library/Preferences/SystemConfiguration/ to /Extra with the new EFI string editted in but there was no change upon reboot. In System Profiler, the graphics is still listed as "GPU". I then changed the one in /L/P/SC/ to no avail. One can't use OSx86Tools since development for that stopped at the Leopard level. If you try to click "Add EFI String" in SL it results in an error involving assigning a 0 value to a boolean.
  8. GT 240 Woes

    Same problem, even when formatted with FAT.
  9. GT 240 Woes

    Hey, it comes up with an error in DOS: No DPMI - get csdpmi*b.zip Might it have something to do with the fact that the HP USB formatting tool formatted the flash drive in FAT32? It didn't have plain FAT...
  10. Select the file, the folders it is in, and the hard drive, and "Get Info". At the bottom of the menu is a permissions box that you have to change to "Read/Write" instead of "Read-Only" for "everyone". Make sure to repair permissions via Disk Utility after you're done.
  11. Random Firefox 3.0.10 Crashes

    I still don't know what the problem is. I now use Safari as my default browser, and so far, it's okay. The few times I use Firefox, it hasn't crashed yet.
  12. When I use the PowerManagement.bundle in the first post, it actually deletes my pre-existing battery meter, which was used with the PowerManagement.bundle in the attachment. However, with the downloaded PowerManagement.bundle, sleep suddenly works. When I reinstall the old one to get the battery meter back, sleep stops working. Any ideas why? Is there a way to get the best of both worlds?
  13. Is it possible in Applescript to display the current volume, like how striking the "volume up" key displays the little translucent box with the volume level? Maybe in a dialog box?
  14. Intel 3945abg pro/wireles

    Sorry for the English reply. http://projectcamphor.mercurysquad.com/ It is currently in development.
  15. Using the β54(3815) version, updating it from a lower version which had the same problem, I encountered this problem. Quicksilver would refuse to respond to Ctrl+Space. Strangely enough, if I click out of a window so the active program becomes Finder, Alt-Escape seems to call Quicksilver up. And the usual buttons for switching virtual desktops, Alt-Left and Alt-Right, are strangely refusing to work, as well as the Hyperspaces corner on the bottom right of my screen. Rebooting solves the problem, but only temporarily because the problem resurfaces if I don't shut down my computer regularly (aka after a certain amount of uptime, possibly?). It just pops up at random and goes back into dormancy after a reboot. Any ideas on how this could be?