Hi



Ive been having big troubles installing, and I'm yet to see a solution even after searching for hours, dont know if iI'm searching for the wrong thing... anyway

I have already installed Vista some time ago, and want iAtkos 7 installed, so I can dualboot, well I've followed this tut: Hack Attack : Dual Boot Leopard and Windows Vista | dailyApps Because I did'nt think there was a big difference between version 1 and 7 installation wise, well big mistake, because I cant seem to find the Darwin boot option anywhere, even after pushing install and costumize, Darwin boot is nowhere to be found, I cancelled the installation, and tried to boot up in vista again, boot to my big surprise iAtkos had already fucked my vista boot up, now if I succesfully install iAtkos 7, do you think my vista will come back? Because not even my vista DVD can find any operating system to repair, and how am I going to install it, without Darwin boot? Are there an alternative? And if, how is the installation done now?



Regards
Jacob

You just need to install OSx86 on new partition. It does not matter if it's on the same or different hard drive with the Vista.

I installed Vista and iPC OSx86 on same HD with 4 partitions (Vista OS, NTSF data, Leopard OS, MAC data). You may get error missing MBR when booting up to the Vista cause by OSx86 installation; just do a setup and repair of Vista to get it back? After boot up with Vista, download and install free software EasyBCD and configure the dual boot.

You can add an entry by select corresponding OS and HD partition as show in image



EasyBCD is NeoSmart Technologies' multiple award-winning answer to tweaking the new Windows Vista bootloader. With EasyBCD, almost anything is possible. Setting up and configuring Windows boot entries is simple, and there is no easier way to quickly boot right into Linux, Mac OS X, or BSD straight from the Windows Vista bootloader - on the fly, no expert knowledge needed!

Yeah well, I just tried installing it, and when it was done, Icouldn't boot into vista, I popped my vista disk in, and pushed repair, it asked me what operating system I wanted to repair, but I couldn't choose any, so I tried manually repairing the BCD but that didn't work either, so I ended up just installing Windows 7 RC, but seriously I didn't think it could screw so much up :O

Well it's tool late now it seems . . . there was away to get Vista to have been re-seen using the Vista boot disk or a Vista emergency repair disk and the command line first.

Sometimes you should just slow down and think before hitting keys - if you do not know what you are doing don't try it at all.

Both OS's need to be primary partitions. Vista should have been working. Install EasyBCD first. Then install the MAC OS. After install of MAC OS you go back in and repair the Vista boot. The MAC OS works better in the first physical partition on the drive. You could have resized and slid forward Vista with an appropriate Vista resize partition tool. (only a few work) Then get into EasyBCD and add the Mac OS to it's boot, then reboot and the boot manager will work correctly then. This assumes you now how to install the MAC OS correctly in the first place.

Too late now as I said. After a successful install of the MAC OS and it does not boot all the way . . . then

You need to boot with -s. If it loads that to a command line, you've got likely kext problems. Then try -x -v so you can see where it stops, slows, issues errors or hangs. If you get in that way to a desktop you've got probably video kext problems. these can be LOTS of different problems depending on whose distribution you installed and how old it is. Get the newest one - right now which is 10.5.6. IPC has some issues with laptop keyboards not working after install - IDeneb seems to go better.

NO ONE can help you right now. You do not say what is wrong, you do not say what you did that does not work and you offer no clues as to your level of expertise as to EXACTLY where you are stumped. You just scream "please help me".

If you go to a Medical Doctor and just scream "please help me" and will give no symptoms or clues as to what is going on - even a Doctor cannot help you but begin guessing - and guess what - they get paid to do so - no one here is being paid by you, and still the doctor could end up killing you rather than saving you because you did not tell a critic piece of information - like a severe allergy or something like that which could kill you in his efforts to help you. Computers - especially the OS's of computers are NO DIFFERENT.

You do not say what is going on. No one is a mind reader here and were not sitting in front of your machine.

Usually a Kext is likely probably not loading or blocking something - or the kernel panics. that means dies the horrible crash like a aircraft pilot would it the pilot panic'ed in an emergency situation and did not know what to do.

The kexts are vendor and device ID specific - so if the kext does not have the right vendor and model ID referenced in the kext file - it will fail - or pass up the device anyway.

You have to figure this out yourself - it is YOUR machine. They are all different as to what is in the unit from the manufacturer, and even if using common device components - the vendor and device ID may be different that what the kext might have in it.

If you have Windows still on the same machine - and it is working - you can do kext editing from inside windows by installing some helper tools to look into the HPS drive. Use Windows Text Editor Download and Download Ext2Fsd 0.46 - An open source Ext2 File System Driver for Windows - Softpedia and Catacombae - HFSExplorer (HFS Explorer) to see and get at the Mac files in Windows; OR you can BUY Macdrive. If you are having dual boot problems try installing EasyBCD from inside Windows to boot between the two. Its free.

This above will only work if you have been smart enough to do a dual boot machine where Windows is on another partition or permanent drive in the same computer. If Windows will not boot use a Vista repair disk or the XP disk to repair the boot sector - then install EasyBCD through Windows and it will see the MAC partition to let you set it up on the boot manager. Google how to get one if you do not have them.

You can see the vendor and device ID in Windows, and the kext will have a name and you can find the vendor and device ID in the text of the kext info.plist. You can edit this from the windows side with the editor above - and use no other - they will not work.

After you get in through safe mode, you can run "diskutils repairpermissions /" (without the quotes) and to fix the changes you made from the Windows side.

You come in single user with the -s command at the prompt. Do what it says to mount the volume and then

You do a "sudo -s" first (no quotes)
cd /System/Library
chmod -R 755 Extensions /
touch Extensions /
diskutil repairpermissions /

There are other ways to do this and much more from the -s boot option (single user mode) but it is really getting UNIX specific as to the commands, and if you are there and know nothing anyway - you should probably pay someone, buy a real MAC or just give up - OR get ready for a real extensive learning curve and research on the web.

You need to do some research on how the MAC OS works. Match your kext families with the missing parts of the OS not loading - change the vendor and device ID's and one at a time - you'll get them working and the boot errors will go away.

If you have/had IPC 10.5.6 ppf4 or ppf5 you would likely have most of the kexts - but they might not have the right vendor ID and device ID for the unit you are trying to install on. it works for both CPUs Intel or AMD. IDeneb 10.5.6. might go more successfully.

Once installed, you need to boot in safe mode from the Darwin prompt with the -x option. Use -v also so you can see what it is loading and if it does stop in safe mode and where. Then you can try -v -f on another boot to see if it will make it all the way

The MacOS is at it's core - UNIX - you cannot just lump a question in something and throw it here that is non-descriptive as to tell anyone not at your PC what is TRULY going on, even though I am a UNIX engineer.

No one can help you if they cannot tell what is really going on - and if you are not ready to learn some UNIX - give up now.

If you install the right kexts (Kernel EXTensionS) with the right vendor id's applicable the system will load them as it finds the hardware during the boot process.

Read the clues of the boot process yourself and do some research as to what they mean and then if you have a specific question you cannot find on the Internet or in the forums - that someone can identify - post that.

Of course you can always BUY a real MAC, and then holler "please help me" all you want to Apple Computer Support, and at some point they will tell you the same thing.

If you install the right kexts (Kernel EXTensionS) with the right vendor id's applicable the system will load them as it finds the hardware during the boot process.

Read the clues of the boot process yourself and do some research as to what they mean and then if you have a specific question you cannot find on the Internet or in the forums - that someone can identify - post that.

Visit the Main Page - OSx86 for the best source of simple question info

Thanks alot for your description, I'm sorry I was so agressive at first, I just hate when I'm following a tut, that a point is missing, thats why Well actually I tried alot of things before trying to install it, first when I found that the darwin boot thing was missing, I cancelled everything, but already there my boot order had been rendered useless, I tried repairing, but even there it couldn't find my OS to repair....

I'm having the same problem as Jacob except that I tried dualbooting Vista and iAtkos V7. After "installing" osx it prompted me to reboot. No Darwin bootloader just a "boot:0 error". It was late so I decided to quickly boot into Vista, I popped in the recovery disc and clicked repair. No operating systems were found, hmmm. I clicked "load drivers" not knowing what drivers were being talked about. I looked at My Computer and I saw that I now had four partitions and my c drive had moved to d and my d drive to e. My local disk was some weird 40 megabyte partition. Not knowing what to do I clicked "startup repair" and restarted. Vista booted, but all I could see was a blue screen with my cursor in the middle. Now I want to either fix Vista or get OSX and Vista dualboot working. I didn't know that I had to create an OSX boot option prior to installation, funny thing is that I had Easybcd installed on Vista. Please help as I'm out of my computer.

thanks for wasting those 2 minutes of my life bobburns for your destructive criticism. I feel more stupid now. But how about addressing their immediate problem.

with a little research and youtube oddly enough I was able to find out your guys problem with repairing the vista partition not repairing. To fix the problem, when u load up vista install and go into repair option, open up command prompt and type DISKPART and this will get you into the partition of your drives. I'm running off a single had drive right now so all i had to do is set my current vista partition to the active drive

EX: 1. LIST DISK (this should me all of my current drives, since i know I set my vista and Leopard partition on Disk 0 [my 750g HDD as it should indicated close to your current HDD] i need to set up that drive).
2. LIST PARTITION (both OS' set themselves as primary partitions so vista for some reason gets confused and can't except this because when u installed leopard or whatever OS your active partition [u can't dual boot w/o a partition] became whatever partition you made for your secondary OS).
3. SELECT PARTITION 0 ( partition 0 is my vista partition because it should come first but i also know how much gigs i had on it, and partition 1 in my case is my leopard partition).
4. ACTIVE (my vista partition is ready for repair [o other way i know of to work around it]).

Close out the cmd window and restart and try to repair vista again. This time you should see Vista show up in the repair dialogue and it should repair properly and load straight into your vista desktop after one last reboot.

Hope this helps.