Jump to content
4 posts in this topic

Recommended Posts

Hey all. I apologize in advance if my technical nomenclature isn't 100% accurate. I'll try to be as clear as possible. Hopefully it gets the idea across - just bear with me. :|

 

PROBLEM: My screen is stuck in blue mode when in fully-booted MacOS GUI. Just plain old sky blue with no text or graphical indicators of what's going on.

 

PROBABLE CAUSE: In my working OS I tried to change the resolution using System Preferences. As soon as I clicked the resolution I wanted to test (trying to change to 1600 x 1200) the screen went blue as described above. I hit escape, but I got an alert sound. As far as I could tell the OS was running, but I could see nothing. Obviously I can't change it back if I can't see what's going on!

 

SOLUTION: What I want to do is use the Darwin console (where you type in "-v" at startup) to change the resolution back manually. This should, in theory, give it the proper resolution and cause it to not be blue when it finishes loading to MacOS.

 

WHY I NEED YOUR HELP: How to I do this? I have virtually no experience working with Darwin console besides typing "-v" or "update -v" if I'm feeling crazy :P . If someone can post a short set of instructions on what to do and type, I'd greatly appreciate it.

 

SPECS: Here's the specs of my hardware and software if it counts.

Software: MacOS Leopard 10.5.2 hacked by Kalyway, upgraded to 10.5.7 using the standard guide on this website. No dual boot or partitioning used - an entire hard drive is devoted to MacOS.

Hardware:

Intel Core 2 Extreme Kentsfield 3.0 GHz LGA 775 Quad-Core

GeForce 8600GT 256MB

4 x 1GB DD2 1066 RAM (4 gigs total)

Seagate Barracuda 250 GB SATA (MacOS drive - primary master) - Mac OS Extended format

Seagate Barracuda 1000 GB SATA (Windows drive - primary slave) - NTFS format

 

Thanks for any help you can provide on this!

 

Also, if anyone knows of a good Darwin console guide I'd appreciate it, since it'll make the process of doing this easier. I have extensive experience with DOS and Windows Console if that counts for anything.

I don't think the problem is with the resolution.

 

Before trying anything else, connect your monitor to the other output on the video card, and unplug your TV if you have one plugged in. Then boot.

I don't think the problem is with the resolution.

 

Before trying anything else, connect your monitor to the other output on the video card, and unplug your TV if you have one plugged in. Then boot.

 

I tried it and it worked! I honestly didn't think it would! Thanks!

It's the little things.

 

On OS X, the primary output is normally the one closest to the motherboard. On Windows it doesn't make any difference where you plug in your monitor, so this happens to a lot of people.

×
×
  • Create New...