Jump to content

kneekos

Members
  • Content count

    3
  • Joined

  • Last visited

About kneekos

  • Rank
    InsanelyMac Protégé
  1. I did not have this problem last week with a previous installation of the same ideneb v1.3. The only difference is I then had an old version of Chameleon which booted the system normally. Could it be a drive mapping problem on the Chameleon? Nevertheless I reinstalled an RC2 chameleon version with all the drives attached now. No solution. Are there any mapping commands in chameleon?
  2. ERROR

    Hello, I get the same memory allocation error (0xf000f000, x02) error but not on the main OSX disk. I get it when I have a USB seageate freeagent 500GB attached on the system. The system halts on the bios screen. If I remove it then the system boots normally. It does not happen with my other usb 250GB drive. I did not have this problem last week with a previous installation of the same ideneb v1.3. The only difference is I then had an old version of Chameleon which booted the system normally. I installed the latest Chameleon RC3 without all the drives attached. Could it be a drive mapping problem on the Chameleon? Nevertheless I reinstalled an RC2 chameleon version with all the drives attached now. No solution. Are there any mapping commands in chameleon?
  3. Hello, I am using the latest version of Chamelon running RC3. I get the memory allocation error (0xf000f000, 0x2) during boot and when I have the usb hard drive attached. I did get the error once with the usb keyboard but it resolved itself on rebooting. -I will try to install a previous version of Chameleon. RC2 or RC1. I think I was using RC1 before rebuilding the system and everything was fine. Another thing I will try is to reinstall the current version of chameleon with all the devices attached on usb. It might behave differently. Changing the sequence of the drives and the active partition (I have xp as well) does not make a difference. I also found this, but did not comprehend much. http://translate.google.com/translate?js=y...history_state0= Does anyone know what could be happening??
×