Jump to content
8 posts in this topic

Recommended Posts

This has been my experience with Mac OS X 86 on my

Hardware Specs:

Issues:

Could not Validate 'MacOSX 10.5' Package

Chain Boot Error

Need tulip.kext

 

I have 2 HDDs ((1)1 with Vista installed and (2)the other just for music)

I portioned HDD (1) to install OSX86.

I installed OSX86, but was only able to do so by switching my IDE mode to AHCI from my BIOS.

I booted into -s mode and did fdisk -e /dev/rdisk0 | flag 1 | quit | reboot.

I tried to get into vista, but got a winload error so I inserted the Vista disk and did a repair and restart.

The OSX boot loader was gone, so I booted into -s mode again and did "fdisk -e /dev/rdisk0 | flag 2 | quit | reboot"

I restarted my computer and it still didn't boot into OSX so i did "fdisk -e /dev/rdisk0 | flag 2| update | write | quit | reboot"

It still wouldnt boot into OSX unless I had the OSX86 Leopard disk in. I thought to myself "ok fine, the dual boot instrustions were wrong, so I guess Ill try to fix the fact that my LAN doesnt work. I already knew that my LAN wasnt going to work without tulip.kext (for some reason people don't want to give up their pre-compiled tulip.kext files because they want you to suffer to make it) , so I downloaded the source for it. I followed the instructions for compiling it, but guess what... "make command not found" so i was patient and decided to fix my vista mbr so i get get to the internet to research the issue. I was told that I needed apple developer tools, so I was like "fine, I will download this and put it on my other HDD since OSX86 can see my other HDDs. I knew theere might have been an issue there so I ALSO put it on a DVD just incase.

I booted into OSX86 again using -s so i can restore it's MBR so i can install developer tools "xtools".

I tried to install xtools and guess what... Cannout validate the 'Mac OSX10.5' package.

I said "fine, forget this. ill come back to that too. Lemmy try ti see if there is another way to dual boot"

I found this tutorial on copying chain0 from the OSX86 install disk and creating a "boot.ini" file and thought that would work, but hey.... NOTHING worked so far, so why should this.

and sure enought I was right ... "Chain Boot Error"

 

What's going on here.

Thanks in advance.

Hmm, are you using a desktop or a laptop?

 

If you are using a desktop do you have a spare one or know someone who will let you stick your hard drive in as slave and let you fix it that way?

hmm, that statement seems a bit rediculae

search is your friend

http://forum.insanelymac.com/index.php?showtopic=6115&hl=

the above tulip driver seems to work perfectly "AS IS" for me

 

 

(for some reason people don't want to give up their pre-compiled tulip.kext files because they want you to suffer to make it) ,
Hmm, are you using a desktop or a laptop?If you are using a desktop do you have a spare one or know someone who will let you stick your hard drive in as slave and let you fix it that way?
Yes, those specs you see above are desktop specs
hmm, that statement seems a bit rediculaesearch is your friendhttp://forum.insanelymac.com/index.php?showtopic=6115&hl=the above tulip driver seems to work perfectly "AS IS" for me
Thank you so muchAny idea about my other issues?
What I mean is if you can't boot into your HD there is something wrong. I would remove the Chain0 from the windows partition.

I can boot into Vista fine.

A lot of people are getting "Chain Boot Error" on x64 systems for some reason i think.

×
×
  • Create New...