Jump to content
InsanelyMac Forum

R. Bear Helms

  • Content count

  • Joined

  • Last visited

About R. Bear Helms

  • Rank
    InsanelyMac Sage
  1. R. Bear Helms

    Nooby question, please reply

    Sounds fairly standard to me, but Apple tended to be in bed with Motorola during the time they implemented PC Card interfaces, so I'd not be too surprised they didn't create an OS X driver. The Darwin project (look for open darwin in search) has more drivers and more compatibility in general than any OS X 10.4.3 or beyond. You can download an installer for Darwin for free, and legally - then boot it up, see if you can initialize ethernet... You may have to actually install it, and the Unix commands to get PCMCIA initialized may or may not be necessary.
  2. R. Bear Helms

    Compatible Parts

    Newegg is good that way, especially if you're buying a replacement part from them instead of going for a full refund... actually they take 15% off either way I think except under certain circumstances. The Wiki will remain out of date if you don't add a pass/fail info to the appropriate list. I could only do my mom's gateway and add that my success with 945GM-FR wasn't identical to that stated previously.
  3. R. Bear Helms

    Dual Boot

    Quick way is to use a partition utility (xp has a command-line one called diskpart) to set the OS X partition as "active" (usually this should auto-clear active off the XP partition) and boot the install DVD for OS X. Don't type anything and the loader should notice the nice ready OS X partition and boot it. Another thing people do, assuming OS X is on the slave drive and XP is on the Master drive, both on the primary IDE channel, is to get a small file called CHAIN0. There should be a link on the boards somewhere - it's a generic boot the slave drive switching program. You edit C:\boot.ini to have the line added at the bottom: c:\chain0="Mac OS X" This requires the chain0 file be stored in C:\ directory. Then when XP boots, you'll have a menu of Windows XP and Mac OS X.
  4. Where Electrostatic Discharge enters an equation, logic exits. It's like trying to puzzle just exactly why lightning struck this tree instead of that. Controller state may have gotten jumbled by the confusing signals it heard during reconnection - from an input circuit's standpoint, the 2,000,000,000 nanoseconds it took to hook the drive up each had their own peculiar ups and downs, all very confusing to any circuit or state machine. It likely went through many illegal or impossible states - and most programmers don't code for failure cases that "never happen."
  5. MSI 945GM-FR... no sound, or it's coming out LINE OUT without any ability to perform volume control (I've been too lazy to play around with the output plugs). Ethernet ok, QE/CI are ok except in 10.4.5 - you need the AppleIntelFramebuffer.kext or some file by a similar name restored from the 10.4.4 extensions backup Maxxuss recommends. USB no problem... seems I needed to turn off SATA altogether, disable any RAID, and dedicate myself to use the primary IDE channel only. Using the other IDE channel from the motherboard either made my DVD-RW disappear or put it on like the 3rd IDE, which OS X tends to not understand exists. Definitely something unclear as to how you configure this for two IDE busses, primary and secondary, and no SATA. Seems SATA has to be taking the IDE secondary controller address and any additional IDE cable always has to be the tertiary. OS X has been not completely reliable either - erasing it off my system after performing these copies of data onto FAT32 partitions.
  6. Electrical connection of an IDE interface "live" represents a number of threats. Modern electronics are made to be hardened against these threats, but still are quite vulnerable. 1) Electrostatic discharge. Often, when you have 2 separate units that do not share the same logic ground suddenly connected together, you create an electrostatic discharge from the unit with greater potential to the unit with lesser potential. Since electrostatic discharge is much like miniature lightning, it actually can fry components on both sides of the connection. You do not necessarily hear a "snap" or smell ozone when this happens. If you do, chances are very significant something just fried. 2) Power surge. Sudden establishment of both power sinking and power sourcing elements sometimes activate during a moment of voltage hysteresis when a peripheral is suddenly connected. Most all circuits have a "crazy time" during which a RESET signal is usually built-in or asserted to stabilize operation. Plugging in a drive live can circumvent this necessary reset, leaving the interface in a confused if not inoperable state. Why can you plug and unplug USB then? It's designed for that use in mind. First off, circuits may not draw more than 100ma from the USB interface. This significantly reduces damage potential from the get-go. Also, the shielding (static discharge/ potential equalizing) part of the USB interface comes together first before the electronic communications signals can. Unless you can really jab a USB plug home in a split second, there's almost zero danger from ESD. Lastly, the connections of USB almost definitely are using opto-isolators or similar protective circuitry. This may explain why it took a while for high speed USB 2.0 to come about; opto-isolators can only switch so fast.
  7. His patched kernels need to be changed to the name mach_kernel, and need to replace whatever one you have at the "root" of the 10.4.4 volume. This usually means /Volumes/mac_osx_10.4.4/ - whatever the mounted drive name is for your 10.4.4 disk. The extra stuff he says to do after the patch is a terminal session. The last bunch of stuff he says to do is what you'd type in after booting the 10.4.4 volume and pressing F8 before it loads, then typing "-s" to get into single user mode. Then the rest, the fsck -fy command and so forth, are typed in at the console you'll see after single user mode is finished booting and is ready for you. There's no GUI shown - it will be a full-screen terminal session.
  8. R. Bear Helms

    Compatible Parts

    Yup. There are some 10.4.5 drivers that work together as a set. It'll be a trial and error process if the 10.4.3 driver for whatever broke in 10.4.5 don't do the trick. Maxxuss has the general list (2) of kernel extensions you need to restore back from 10.4.4. There's a 10.4.4 AppleIntelFramebuffer.kext file (something like that) needing replacement from the pre-10.4.5 patch (backup directory maxxuss suggests) that re-enables screen resolution with various graphics chipsets.
  9. R. Bear Helms

    Motherboard/CPU recommendations?

    I actually regret building a PC to conform to OS X. First off, sound should have worked and didn't - does in Windows, indicated as "no volume control exists for this device" in OS X. Tried about a dozen different combinations of kernel extensions, kext editing attempts, Darwin and 10.4.3 kext files... ended up just buying a USB sound dongle. Later, when 10.4.5 seemed to be running well, iLife '06 just decided to quit on me after about 6 hours of work not yet saved. When a program crashes, it tells you it did and gives you an option to restart, cancel, or bug report to Apple. This didn't do that, which makes me believe a TPM check came later on and failed. I don't know what resources Maxxuss has to find when and where TPM checks are done and whether he's circumvented all of them, but his site seems to warn that 10.4.5 software (and I assume any Intel software Apple supplies) has an amount of CPU architecture, hardware environment, etc., checks in it BESIDE the TPM check. So this OS post 10.4.3 is always going to be suspiciously functional on a PC. I can almost assure anyone who attempts to spend a full day working on most any project or playing most any game to find themselves wondering why it's not working so well - and we'll have to suspect it's Apple's tertiary level of copy protection at fault. 10.4.3 is real nice and compatible - I been restoring gigs worth of backup data all day here - but parts of it are really broken, like Mail. As soon as I get my data all on FAT32 volumes, OSx86 is history - erased from all partitions I got. Windows doesn't goose your software because it feels it's not been authenticated. It will give you 30 days before it insists on authentication... OS X shuts down instantly the moment it finds something wrong (mostly TPM wise, but who's to tell?).
  10. R. Bear Helms

    Compatible Parts

    Both, assuredly. There are going to be several broken things on 10.4.5 needing the driver from 10.4.4, 10.4.3, or Darwin 8.01. Nothing new broke for me on 10.4.5, well actually the GMA900 stopped having display resolution choices - turns out I needed to restore the old 10.4.4 AppleIntelFramebuffer.kext or something similar to that name. It didn't FIX anything with my system - but I think the graphics performance was nicer once I repaired the framebuffer kext. I had iLife '06 iDVD 6.01 just unexplainedly quit on me - not crash. Crashes give an option to restart the app or report the error to Apple. This just plain old quit without asking me if I wanted to save. I have a suspicion TPM checks exist in the Intel version of Apple software, some of them wait a while before giving you the screw-over.
  11. R. Bear Helms

    waiting for root device?

    Waiting for root device has a number of possible problems. Without a view of what other complaints came prior to that error, even the following list may be inadequate: * Cannot understand the IDE/ATA/SATA interface method supported by your hardware. * Found an NTFS volume and no others * No HFS volume exists on the primary drive (IDE Master) * CD-ROM interface is too unstandard for booting from. Image files may be placed into an existing partition, but by Disk Utility which needs you to get beyond "Waiting for root device" before it is available. The torrent sites have a Symantec "Ghost" image of a 10.4.4 partition. However, it won't restore onto a hard drive with less than 22.3 Gb (approx) free space. You'd restore creating a new partition. At the boot prompt, the general root syntax is like this: disk0s2 That would refer to the primary (Master) IDE drive, 2nd partition. I assume your first partition would be Windows. disk1s3 Sometimes this is how you refer to the CD-ROM boot. Change the last number downward to 1 in attempts to continue. The Wiki (link at the top of the forum) has a Technical FAQ. I recommend you prepare a hard drive with a partition to receive OS x86 prior to booting the install DVD. There's an answer there about prepping a hard drive using Windows XP.
  12. R. Bear Helms

    My opinion on OS X on the PC

    I thoroughly object to a chip placed in a computer I pay hard cash to buy where that circuit's main purpose is to give its manufacturer final say-so on whether certain software may or may not run on the computer. Yes, it has a good reason to exist - block malware like viruses, trojans, spyware. But it can be put to a dark purpose, and as far as I know, computers don't understand ethics. They only understand binary. TPM can give the power to the supplier "tattletale" information about what software has been added and removed, as well as what changes to the operating environment (what hardware added, removed, reconfigured) has happened. I am unsure if the chip Apple employs has the ability to have its internal private key reset or reprogrammed. If it does, the first malware program to exploit that feature will be causing Apple computers to become unbootable everywhere they're attacked by that software. The circuit has no place in a user-friendly computer. OS X presumes guilt the moment the TPM circuit blows the whistle, and the computer instantly halts operations. Contrast that with Windows XP which at least gives you 30 days grace working with the Operating System before it insists it be activated.
  13. R. Bear Helms

    XP Loading instructions posted on Contest Forums

    Wow, maybe people with a MacBook *can* escape having it remote controlled by Apple
  14. R. Bear Helms

    Welcome video repeats after installation?

    The video can be disabled by creating a file somewhere, but I forget the name and where it goes. It's like Library/Preferences/SystemConfiguration/.whateveritscalled However, most working systems can play that video without this problem. I'd be suspecting you don't have all the AMD patches in place, or that the nForce chipset support is boned for OS X, which would be what I'd gamble is the problem.
  15. R. Bear Helms

    Compatible Parts

    Should be OK. Apple is a snake-in-the-grass with hardware sensitivity. It's by design; each release they've made the software more and more assume the CPU, resources, etc., etc., are ONLY that that are supposed to be found inside an iMac Core Duo, or the Mini Core Solo or Core Duo.