dudeinco

Members
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dudeinco

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  1. Looks like the current installed Chameleon is v2.0-RC4, so something is very wrong here. I ran the installer for 2.2, but apparently it didn't take. Edit: Turns out installing the bootloader on Disk1 doesn't do anything because Disk0 is the default bootloader. Now, that's Windows, which means EasyBCD is injecting the Chameleon bootloader? Hmm... so this makes things more difficult. Edit: Doesn't matter anyways - booting from Disk1 does the same reboot - At this point, it looks like I'm stuck with a USB for a bootloader, which kind of sucks, but hey... what are you going to do?
  2. Got the full error message!! By hitting a key and then pause over and over (and rebooting about 5x, because the timing had to be perfect): efi_inject_get_devprop_string NULL trying stringdata Now we've got something to work with. Tried reinstalling Chameleon using the stand alone installer, still no good.
  3. As an update, when it goes to the loader and reboots, just before the reboot, there is a message on the top that is too fast to read, but what I can make out is that "NULL" is in the sentence. And maybe "string?" Not sure - I'm a developer, so perhaps I'm seeing things... There's definitely a "get_" and "develop" and "efi_inject" in the message... It is a split second message, so I am going to have to restart a few hundred times to get the message.
  4. Anyone? There has to be something that can be copied from the USB if the USB will boot Mavericks on the disk, but the installed Mavericks won't, right?
  5. Well, I have a working copy of OSX running perfectly, so I guess that's a good start. Here's what happened: I had W8.1 installed on a machine, and decided to make a dual boot 10.9. First off, I had to mix a Niresh .dmg I found with a Niresh ISO just to get the thing to boot (SMC failures). Then I had to copy files into the kexts directory for my machine from some random zip. Needless to say, the install is a total Frankenstein. Anyhow, I went and installed 10.9 into disk 2, and everything was great (video acceleration, sound, etc). Everything worked great, EXCEPT I could only boot into OSX by booting from the USB install bootloader. I went through the process of marking the drive partition for OSX as active. (also upgraded to 10.9.4) I booted into Windows, and used EasyBCD to create an entry for OSX, and set the drive to d: for the operating system (where OSX lives). When I select OSX from a new boot, I get a different loader (chameleon logo - press any key to boot - press f8 for advanced options). If I just hit a key, it will think for a few, then reboot. If I hit F8, it shows the expected drives to boot from. If I let it go, it will perpetually go through the think, then reboot, again and again. So, what am I missing here? Does this have something to do with the kexts in the installer needing to be copied over to my current copy? Does it seem like I missed something? Here's what I'm thinking: since I copied the kexts into the extensions directory of the installation USB that allows the installer to work without the SMC issues, perhaps I need to copy those kexts to my Mac install as well? Totally shooting from the hip, being new at this. Edit: I used the copy process for kexts from the sticky on the 10.9.2 to copy the kexts from the install extras directory (how I originally got past the SMC failures). No love. Complete failure even with installer - had to reinstall. I like the idea of using the Windows BCD to boot into Mavericks - not gonna happen? P6T Deluxe + 12Gb + I7 920