Jump to content


  • Content Count

  • Joined

  • Last visited

About GeekMan

  • Rank
    InsanelyMac Protégé
  1. Old topic, I know. But there's always room for more solutions: I was back inside my sister's Hackintosh recently to add an extra hard drive. I noticed for the first time that the DVD drive was connected with an old 40-wire ATA cable as opposed to the more modern 80-wire UltraDMA cable. The cables have the same connectors and look similar, so if you don't know the difference you should look here: http://www.pcguide.com/ref/hdd/if/ide/confCable80-c.html If was a stupid mistake which I must have made whilst rummaging around in my parts box when I was originally modifying the machine (I'm assuming that HP wasn't stupid enough to ship their machine with an older IDE cable). Without a proper UltraDMA cable, functions on modern optical drives (booting from CD/DVD, burning) can malfunction. This might have been the cause of all my problems to begin with. So, if you've never been able to get burning to work correctly on your hackintosh, you might want to check what kind of cable it is connected with. It's definitely worth a shot.
  2. I wasn't sure where to put this, though I figured the people watching this forum would have the most experience with the technologies at hand. I've got a two-CD MCE XP installer. It mostly works with my MacBook for Boot Camp, but I'm unable to eject the first CD during the install process, which forces me to install a bunch of components manually later on. So I'd like to combine them into one DVD. I've been told that boot DVDs can't be multisession, so that's out. Nero's interface fills me with hate, so I tried using Disk Utility to rip the disc to a .DMG, convert it to read/write, and then simply resize it to accomodate the data on the second disc. However, with whatever I've tried, Disk Utiltiy simply refuses to resize the disc image. I tried using hdutil -size in the command line, but "sudo hdiutil resize -size 1G /discimage.dmg" gives the output: hdiutil: resize: failed. Operation not permitted (1) I figure that dd can probably resize the image, but dd's arguments confuse me, and I am of the understanding that need to skip over the MBR for this to work correctly. Can anyone enlgihten me? Thanks.
  3. GeekMan

    NVidia GeForce FX 5200

    Okay! I'm good to go. CI/QE Supported, dual monitor support enabled. The NVCAP is spot-on! I used the NVInject provided by monaco78 and the OSX NVidia drivers from http://diabolik1605.com/DHF/ I put my card's Device/Vendor ID string (0x032210de&0x000ffff) into the PrimaryIOPCIMatch field of "Info.plist" in GeForce.kext, NVDANV30HAL.kext, and NVDAResman.kext monaco78: I'm perplexed though. When I had a look at the Info.plist of the NVinject.kext which you provided, the PrimaryIOPCIMatch field was generic (0x000010de&0x000ffff). The vendor ID is there, but not the specific device. It was my understanding that it was a requirement to put your specific Dev/Ven ID in the plist of your injector. This seems not to be the case. Can you clarify? That being asked, thank you so much! Cheers, - GeekMan
  4. GeekMan

    NVidia GeForce FX 5200

    Synaesthesia, Monaco78 - Great suggestions. Thank you! I will try them out as soon as I get home today.
  5. GeekMan

    NVidia GeForce FX 5200

    UPDATE: I've switched from NVInject and Titan to Natit. Still no CI/QE. I'm starting to suspect that the problem is with the GeForce drivers themselves. What version should I be using? Do I need GeForce kexts from a 10.4.x system?
  6. GeekMan

    NVidia GeForce FX 5200

    I hate to be this poster, but I'm stumped and I need assistance. I'm trying to get CI/QE working on my PCI NVidia GeForce FX 5200, but to no avail. The card is correctly recognized in System Profiler, and I can change to multiple resolutions, but CI/QE still elude me! I'm using Kalyway's 10.5.2 with ToH's Sleep_Kernel. I have done the following: - Installed NVInject 0.2.1, NVDAResman.kext, NVDANV30Hal.kext, GeForce.kext, and Titan.kext - I have set the IOPCIMatch to my card's ID (0x032210de) in the Info.plists of the above, where applicable - Repaired all permissions and ownership - Set my NVCAP in NVInject using Property List Editor.app - Tried removing the individual kexts listed above in varying combinations - Booted with -v -f most of the time Does anyone have any suggestions? A lot of the How-Tos on this forum were meant for 10.4.x, so I've no idea if I'm following up-to-date or archaic instructions. Any help would be greatly appreciated. Thanks.
  7. GeekMan

    Install Ipod-Support

    I'm pleased to say that I may have a solution to this issue. I was having this same problem with my sister's Hackintosh: a 10.5.2 Kalaway install with ToH's sleep kernel (Intel architecture). She has a 3rd gen iPod nano. Earlier posts have suggested using the vanilla kernel to solve this problem, but in our case this unfortunately was not an option. Reinstalling the iPod support software from disc solved the problem, but would not carry over reboots for some reason. Neither deleting the kextcache nor repairing permissions fixed the issue. After much investigation, it seemed that part of the driver was not being loaded at boot. You can fix this problem with the following command (as root): kextload -t /System/Library/Extensions/iPodDriver.kext/Contents/PlugIns/iPodSBCDriver.kext I've added this command as a launchd User Daemon item using Lingon, so it runs at login. This loads the iPod driver maually. If you have a Firewire-connected iPod, it looks like you also might need to load: kextload -t /System/Library/Extensions/iPodDriver.kext/Contents/PlugIns/iPodFireWireTransportSupport.kext Good luck!
  8. Okay. So to solve my sister's immediate problem, I gave her my own Hackintosh's LG DVD-RW, then took her non-burning TS-H652M home to test on my Hackintosh. The TS-H652M burns DVDs on my machine. I would have then presumed that there's something wrong with my sister's machine, but the LG drive I gave her burns discs just fine. This makes absolutely no sense, because both machines have the same fresh copy of Kalaway installed on them. There's something I'm not thinking of. - Burn speed? - Media brand/compatibility? - Interaction between the drive and the system's IDE controller? I've no idea. I almost would have been happier if the TSST drive just hadn't worked on my machine. Then I'd be able to assign blame to a particular part of the hardware configuration. I'm eager to hear reports from other TSST/HP DVD-RW users. Try moving the drive to a different location on the IDE chain, changing the jumper settings, change the media, change the burn speed. Personally, I'm going to try to break my current configuration. At least then we'll have some suggestions for other people having problems with their drives. - Geekman
  9. I have no idea. Somehow I doubt it. The firmware update I applied at work did not enable burning in Windows Explorer. My correspondence with HP has basically boiled down to "you need to be running Windows Vista for all the hardware to work correctly", and they referred me to a Microsoft tech article on how to burn a CD. Hmpf. Also, I discovered that DVD burning on the drive works with Nero 7, but not in Windows Explorer. It doesn't make a lot of sense, because optical drives are generic hardware and should just work without drivers. There's something we're not being told, and that annoys me. I wonder how Linux users get around this issue?
  10. evelez, Not sure if you're still paying attention to this thread, but I just found out that my HP drive at work is the exact same model that you're using: the TS-H653L. Apparently, there are firmware updates available from HP's website. For Windows XP: http://h10025.www1.hp.com/ewfrf/wc/generic...=en&lang=en For Windows Vista: http://h10025.www1.hp.com/ewfrf/wc/softwar...093&lang=en Of course, you'll need some version of Windows to apply a firmware update. I have no idea if either of these will improve functionality in Mac OS X, but it's worth a try. I'll report my own successes/failures later. - GeekMan
  11. The problem is the "TSSTCorp". That is, "Toshiba Samsung Storage Technology". Try going to their website, there's nothing there. It seems that neither company is responsible for the line of drives they jointly develop and manufacture. Some initial Googling shows however that some of the TSST drives have synonymous model numbers in the Samsung or Toshiba lines. So it may be possible to reflash the firmware using that of its generic counterpart. This isn't a problem specific to Mac OS X either. I have a brand new HP machine at work that came with Vista pre-installed, which I wiped and replaced with our VLK Windows XP. It also has a TSST CD/DVD RW lightscribe drive that's very simillar to my sister's drive. Disc burning does not work in XP. Hmm... More Googling shows lots of reports from Gateway desktop users with the same problem: after a clean OS install their TSST DVD writer doesn't work. I suspect some sort of OEM lock-in. I'll try calling HP support about my machine at work, but I suspect the response excuse will be that the machine isn't supported under XP. Will hopefully update. - GeekMan
  12. Bump. My sister's Hackintosh is an HP machine and has the same problem. It didn't work in 10.4 with Patchburn and it gives the same error in 10.5 with EFI. I seem to have a recollection of having trouble getting an aftermarket HP DVD drive to burn in Windows at my workplace a few years ago. Luckily we had a former HP support employee working with us at the time. He tracked down some special obscure software from the HP site that enabled burning. My suspicion is that the HP drives communicate in some non-standard way. If an HP driver is required for burning, we may be out of luck. - GeekMan
  13. GeekMan

    OSx86 Device Manager

    Goodness, I've brought in the ringers! Thanks for the replies. I actually hadn't heard of DPCI Manager before. It seems like a useful tool. I was actually thinking more along the lines of something that would also show the kext associated with any given PCI device, with the ability to load/unload kexts through a GUI. It would allow for some more organization of our "dirty tricks", especially when juggling different driver versions (how many copies of AppleSMBIOS are out there?). Perhaps this sort of thing isn't really practical from a programming perspective. Besides, I hardly expect hacking to be a user-friendly experience. In any case, I've recently gotten my hands on a Kalaway 10.5.2 image, which has made my Hackintosh life much, much easier. Cheers, - GeekMan
  14. GeekMan

    OSx86 Device Manager

    Hello all, The title says it all. I'm sure it's been brought up before, but wouldn't it be great if we had a device manager for OSx86? Mac OS X doesn't have one because it usually doesn't have to run on the Frakenstein-esque hardware platforms that Windows or Ubuntu have to face. Unless of course you're running OSx86. I wish I had the programming skills to pull off such a feat. An OS X device manager could identify unassigned hardware, load and unload kexts (whilst fixing bad permissions), and make the process of configuring drivers and hardware less painful. And as an added bonus, it might result in less questions to the InsanelyMac forums. I doubt someone's going to undertake such a program anytime soon. Nevertheless I figured I'd ask if anyone else has been hankering for such a thing, or if anyone was already working on something. Thoughts? - GeekMan
  15. GeekMan

    Forcing Leopard to use onboard video

    That's a tough one. As far as I know it's the hardware (and as such, the BIOS) which determines the primary video adapter. In my experience, however, OS X has a habit of ignoring video adapters that don't have a monitor plugged into them. Have you tried booting up without anything plugged into the NVidia card?