Jump to content

ginsu417

Members
  • Content count

    10
  • Joined

  • Last visited

About ginsu417

  • Rank
    InsanelyMac Protégé
  1. ginsu417

    MSI Wind u100 Webcam Solution

    Like most wind u100 owners, my MSI came with an evil BisonCam ver 0.3. You can sort of get it to work with CamTwist, but the latency is ridiculous. I ordered a replacement cam for it on ebay from a newer model u100 thinking it would be more compatible, and received a BisonCam Ver. 3.08. Sadly, this camera is even less compatible with OSX. I did a lot of research here and on InsanelyWind and the solutions I found were far from elegant - most of them were Wind owners whining about their particular cameras not working, CamTwist not finding their particular BisonCam, or attempts to contact the manufacturer and beg for an OSX driver. PART 1 - The right camera So I thought... it's a standard USB device... why not just buy a known-working camera? To solve the problem, I purchased a Toshiba X205 webcam board with the cable on ebay for about $7.00 shipped - which I knew would work in OSX because I had just built an X205 hackintosh. I chose this camera because it was the same physical dimensions as the BisonCam, the connector was on the correct side, and the indicator light was in generally the correct spot. I knew the connector on the webcam was different than the BisonCam, but since the one I bought came with the Toshiba cable, I had intended to clip the connector on the MSI and frankenstein it into the factory wiring. Turns out, I didn't have to. I found that the cable that comes with the Toshiba X205 camera is obviously a different type, but because the pins are the correct distance apart, it still fits into the MSI Wind u100 motherboard, where the old cable came out. The cable you get may be slightly different as far as colors, but so far all the ones I've seen appear to be the same. The wire closest to the BOTTOM of the camera when it's installed, is the +5 line - which should be red. And that goes to pin 1 on the MSI logic board. The connector can go in backwards, because it's not the right one for this board - so make sure you're plugging it in the correct way. The cable that came with my Toshiba X205 cam was very long, and shielded with a conductive material, which had the potential to short out the logic board. So I sprayed it with clear acrylic before installing it. You may want to wrap yours in electrical tape, or remove the shielding all together. The webcam board fits nicely into the slot where the bison cam used to sit. Even the indicator light is in the perfect spot, and it's blue so it matches the power button, rather than that ugly deep amber color that the original BisonCam came with. It's a Chicony, and it is a supported UVC device that is NOT laggy, but it is not a high-res camera, which is why it doesn't work natively with FaceTime and Photobooth. Part 2 tells you how to get around that. Part 2 - Using a Low-Res Netbook Cam with FaceTime and Photobooth My next problem was figuring out how to get FaceTime and Photobooth working, since I use FaceTime exclusively. I performed this on OSX 10.6.6, but I see no reason it won't work on newer versions of the OS. The problem with FaceTime is actually quite elementary. It wants to use a high resolution video camera - which most netbooks just don't come with. That's why your netbook camera will work in iChat, but not in Photobooth or FaceTime. CamTwist will trick FaceTime into accepting a lower-resolution feed, by switching the camera to native resolution behind FaceTime's back. But getting it to work requires you to first launch FaceTime, and then launch CamTwist with an Auto-Load profile. This can get annoyingly cumbersome, so I've setup an automated means of doing it. First step - Install CamTwist. http://camtwiststudio.com/download/ Setup a default profile for your camera, save it, and make sure it's set to AutoLoad. Second step - Open AppleScript editor, and build an AppleScript to launch FaceTime: This script will start FaceTime and Camtwist, Bring FaceTime to the foreground, and then close CamTwist after 15 seconds (it's no longer needed, once you get a video feed in FaceTime). If you want to make one for Photo booth, just change "FaceTime" to "Photo Booth". Once you've tested it to make sure it compiles, save it as an Application (not a script) to your Applications Folder, change the icon (if you like) and drag your new icon to the dock. Happy modding.
  2. ginsu417

    ALC880 on ICH6

    Hey gang. I've run into somewhat of a snag with my ALC880. I'm running 10.5.8, which I installed using iPC 10.5.6 and the combo update. I've managed to get sound, but I don't have a working line-in. I tried the voodooHDA .22 driver, but then Line-in doesn't show in the sound options - all I get is CD and microphone. So I resorted to a patched AppleHDA.kext for 10.5.2 and ALCinject.kext, which now shows line-in, but I get no audio from it. I trashed that, and hacked up the AppleHDA.kext (version 1.7.1 I believe) by creating the correct Layout and Pathnodes (I verified they were correct, per my codec dump) and HDAEnabler.kext and I was able to get audio out and line-in to show up there, but I still get no audio when I try to record from line-in. Has anyone else encountered this?
  3. ginsu417

    GMA X4500

    Willing to help with testing, research, and development. Have a Toshiba L305 coming in with Intel 4500MHD chip. Rusty with xcode, but lots of Assembly and debug experience. Let me know if I can be of assistance.
  4. I am able to run Tiger using a virtual SCSI device, but not leopard. Near as I can tell, the SCSI devices aren't allowed to be mounted until after the OS is started in Init-1 (multi-user) presumably because OS-X sees them as external devices - and even after it's in multi-user mode, it appears the default mounting scheme for anything on the SCSI bus is nosuid nosgid, which plays havoc with logs at boot. I can see that all the kexts for the SCSI devices are loading ok in single user mode, but I'm guessing there's a switch somewhere that's flagging external SCSI devices as write-locked. Long story short - does anyone here know where Leo gets these default settings from? Is there a config setting I can change somewhere that will trick Leo into thinking a device is mounted internally, or a setting I can change to allow external SCSI devices to be mounted read/write? Maybe add a static fstab entry for the boot volume? If we can get the LSILogic devices to mount at boot time, leo might actually be usable in VM.
  5. Laptop Prebuilt? (Y) Manufacturer: Gateway Model: MX6453 Install Methods summary: Installed with Zephyroth 10.5.2 DVD Does EFI and/or the Vanilla kernel work? EFI V8 Installed Motherboard Manufacturer: Gateway Motherboard Model: No idea Chipset: ATI SB450 BIOS Version: , Revision: BIOS setup options: Setup Defaults Audio: AppleHDAPatcher using codec dump from Linux, added 0x437B1002 to device ID in AppleHDAController.kext info.plist LAN: Added 0x435211AB to yukon.kext info.plist SATA & IDE: Needed this - http://forum.insanelymac.com/index.php?showtopic=9847 Processor Processor Model: AMD Turion 64 X2 Speed: 1.6ghz Recognized as what in System Profiler: Unknown Video Card What type of card (PCI Express/AGP/Integrated): Integrated NVIDIA/ATI/Intel: ATI Model: Radeon Xpress 1150 Memory: 128mb Board Manufacturer: On-Board Patches used: Callisto QE/CI: No QE/CI All resolutions available? Yes Other PCI/PCI-e Components Wireless: Working out of box PCCardBus: Needed this - http://forum.insanelymac.com/index.php?showtopic=81036
  6. Current OS X Version: 10.5.2 Desktop Prebuilt? (Y) Manufacturer: Gateway Model: GT4010 Install Methods summary: Installed with Leo4All 10.5.2 DVD Does EFI and/or the Vanilla kernel work? EFI V8 Installed Motherboard Manufacturer: Gateway Motherboard Model: No idea Chipset: NForce MCP61 BIOS Version: , Revision: BIOS setup options: Setup Defaults Audio: Needed this - http://forum.insanelymac.com/index.php?showtopic=18642 LAN: Needed this - http://forum.insanelymac.com/index.php?sho...mp;#entry157020 SATA & IDE: Works Processor Processor Model: AMD 64 3500+ Speed: 2.2ghz Recognized as what in System Profiler: Unknown Video Card What type of card (PCI Express/AGP/Integrated): Integrated NVIDIA/ATI/Intel: NVidia Model: GeForce 6100 Memory: 128mb Board Manufacturer: On-Board Patches used: Doesn't Work QE/CI: Doesn't Work All resolutions available? No What type of card (PCI Express/AGP/Integrated): PCI Express NVIDIA/ATI/Intel: NVidia Model: GeForce 7900GS Memory: 256mb Board Manufacturer: eVGA Patches used: NVInject, and GeForce.kext plist to include only devid 10de:0292 QE/CI: Yes All resolutions available? Yes
  7. The installer on Parallels Desktop fails on most AMD machines with version 3+. I figured out how to manually install it, and figured I'd post here. I know this write-up is kind of 2nd grade for some people here, but hopefully someone finds it useful. With Parallels, you can run most other OS's as Virtual Machines inside of OS-X, and get all the benefits of OS-X's Firewall and security. It's a similar product to VMWare - and I prefer it over VMWare. The installer basically checks your CPU manufacturer code for GenuineIntel before installing. If it doesn't find that, it bombs out and says you can't use it. There's two ways to get around this - automatic and manual. The automatic method works on build 5584 and 5160. But it may not work on newer releases, so if you have trouble, try the manual method. I do not have a way to bypass the activation, and I do not condone stealing this product - please pay for it if you intend to use it. Automatic Method (Fresh Install or Upgrade) Use this method to modify the installer package so it doesn't check your CPUID ================================================== * Open the DMG you downloaded from Parallels.com * Drag the "Install Parallels" icon onto your desktop * Open the Terminal application (Applications -> Utilities -> Terminal) and enter the following lines one at a time. $ cd ~/Desktop $ nano Install\ Parallels\ Desktop.pkg/Contents/Info.plist * Remove the following lines: <key>IFRequirementDicts</key> <array> <dict> <key>Level</key> <string>requires</string> <key>SpecArgument</key> <string>machdep.cpu.vendor</string> <key>SpecType</key> <string>sysctl</string> <key>TestObject</key> <string>GenuineIntel</string> <key>TestOperator</key> <string>eq</string> </dict> </array> * Save and exit * Close the Terminal and Double-click the "Install Parallels Desktop" icon on your desktop. Manual Method (Fresh Install Only) Use this only if you've never installed Parallels on your machine before. ============================================= * Open the DMG you downloaded from Parallels.com * Open the Terminal application (Applications -> Utilities -> Terminal) and enter the following lines one at a time. $ cd ~/Desktop $ mkdir ParallelsTemp $ sudo -s # cd ParallelsTemp # ditto -x /Volumes/Parallels\ Desktop/Install\ Parallels\ Desktop.pkg/Contents/Archive.pax.gz . # chown -R root:wheel System Library # chmod -R 755 System Library # mv Applications/* /Applications/ # mv System/Library/Extensions/* /System/Library/Extensions/ # mv Library/Parallels /Library/ # mv Library/StartupItems/* /Library/StartupItems/ # /Volumes/Parallels\ Desktop/Install\ Parallels\ Desktop.pkg/Contents/Resources/postflight # cd .. # rm -Rf ParallelsTemp Now you should be able to run Parallels desktop. Manual Method (For Upgrade or Reinstall) Parallels releases new versions all the time. To upgrade your existing, follow this guide instead. ============================================================ * Open the DMG you downloaded from Parallels.com * Make sure Parallels is closed, and that you don't have any VMs suspended. * Open the Terminal application (Applications -> Utilities -> Terminal) and enter the following lines one at a time. $ cd ~/Desktop $ mkdir ParallelsTemp $ sudo -s # cd ParallelsTemp # ditto -x /Volumes/Parallels\ Desktop/Install\ Parallels\ Desktop.pkg/Contents/Archive.pax.gz . # chown -R root:wheel System Library # chmod -R 755 System Library # /Volumes/Parallels\ Desktop/Install\ Parallels\ Desktop.pkg/Contents/Resources/preflight # mv Applications/* /Applications/ # mv System/Library/Extensions/* /System/Library/Extensions/ # mv Library/Parallels /Library/ # mv Library/StartupItems/* /Library/StartupItems/ # /Volumes/Parallels\ Desktop/Install\ Parallels\ Desktop.pkg/Contents/Resources/postflight # cd .. # rm -Rf ParallelsTemp ================================= Once you have it installed, make sure when it asks, that you do not turn on Intel VT-X. VT-X does not work on AMD chips, and your machine will crash if you enable it. Unfortunately, I can't help with much except the installation, so if you have trouble after you get it installed, you're on your own. Thanks for reading.
  8. ginsu417

    Windows Vista

    I like computers.
  9. ginsu417

    InsanelyHacked!

    Oh how I've missed this place.... You have no idea! Oh the pain and suffering! (now I can finish trying to get my Radeon card working... LOL)
  10. ginsu417

    borisbadenov ATI X1000-series Solution

    I can verify that this solution works for ATI X1300 Pro AGP (ID 7142), with QE/CI. This is more difficult than the Natit solution, but I prefer it, because I can't get QE/CI with Natit on this card.
×