Boots to blue screen with black vertical bar

I have IDeneb 10.5.5 as new install on a Sony VGN-NR385E. 2 Gig ram, 320 Gig SATA drive w 16 meg cache. Easy BCD lets me share XP and Windows 7 with the Mac OSx. All boot. When the Mac boots I get a cleanly formatted blue screen with about 1 inch black on both sides - then it goes to a full blue screen with a vertical black bar about 2 inches wide with about 2 inches blue to the right and 8 inches blue to the left with three white with red horizontal lines evenly spaced across the screen.

I have used MacDrive to see all the files on the Mac drive. Ext Journaled. The installation appears to have gone fine.

This is an Intel 965 (GMA 3100) board with T5500 Core 2 Duo.

I have tried the graphics mode command but the same thing comes up.

Is there anyway to stop this to a command line? I have a bit of Linux experience and experience with X. I am pretty sure this is graphics problem with X - but I do not know what with the Mac OSx

I am currently downloading 10.5.6 ppf4 - but I really do not want to add insult to injury with a new install and new problems

Has anyone seen this and know how to fix it?

You are jumping from the skillet into the fire

Here's my standard paste. Visit the link at the bottom to get started on all you need to know. Remember the mac does not run windows programs - so this is not the solution it appears you think it is.

Use the Vista partition tool to make a partition to install it into so at least you can return to Vista. 25 Gig at least as a primary. Put on EasyBCD first. After install restore the vista boot partition with a boot or recovery CD and go into Vista and EasyBCD and enable the Mac boot you just set up. If you do not know what I just said - you should probably forget this mac idea for your dads laptop.

See - "Read first Before Posting" - Read First Before Posting

There are no "magic settings" to an install the OS, but a proper hard drive setup for the OS to install to. It needs to be Journaled. Use the disk utility at the top menu bar. if it boots to the apple screen only you need to f8 and to darwin prompt - and read this fully

Read this all the way through - but . . . you need to Google for your answers and do some research instead of relying on and expecting a spoon fed answer. Every machine is different. Visit the link at the bottom of this post.

Here is a link to generically what is largely supported in IPC 10.5.6 iPC OSx86 10.5.6 Final PPF5 Complete driver list. | OSX86

netkas.org Leopard supports some of the newer more esoteric NVidia GPU's

If it is not there in the list above or - it is not supported at this time - so do not cry you want it to be. do not expect someone here to spoon feed you a fix for free. This is a standard paste I use prefaced with a preamble to the question usually. So many people ask the same kind of question - this generic answer fits most all of them.

First remember someone is sitting at a computer on THEIR time for FREE to answer your question. No one here is getting a salary from Apple. ( I am not - and I am a UNIX engineer) If it is a wild or ridiculous question, or you just keep posting mulitple questions, you'll get noticed and then ignored. If you want some kind of esoteric solution - at first it will be seen as funny and then - at least I will ignore it.

Second, please realize, the "hackintosh" MAC OS is NOT a commercial software OS product. It is built usually by various individuals - who in their own time put the OS together as a hobby or proof of concept. Trying to upgrade it using ceertain Apple software will lock it up or disable some features. This is not an Apple support line or source, and no one "owes" you anything for FREE support demonstration software. Apple allows this kind of thing - or turns a blind eye so far - because it supports the next product line of computers they might support or retail and helps them refine the use of the UNIX base OS in their business sell legitimate OS software.

so that said . . . after a successful install, and it does not boot all they way through then f8 at boot, or get to the Darwin prompt, and then . . .

You need to boot with -s as the command line flag. 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. The Apple retail product in some cases does not have all the support (kexts) for generic

machines the hackintosh OS's do - but some distros are not as good as others.

Look for what loads and what does not load

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". Posting that you think you got it working without understanding what you did does not help either. You might now really have it working as it should be.

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. The kexts ARE the drivers - and sometimes you only need to change or add the vendor and device ID.

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. You can use a Windows Text Editor - Editpad Lite (only one that will work) and 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 /

If you had trouble with the registration looping or other things then . . . after that above of mounting the volume make a password for root by typing

passwd root

Then when done type

touch /var/db/.AppleSetupDone

reboot

There are lots of 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. You can also read the boot errors that went by too fast in the log after you get in to the OS.

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. Remember the kext might be there - but have the wrong vendor and device ID - so it will get passed up.

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