[�]

So nice that my server's controlstrip gives all the wrong monitorsettings. Most of them are a high resolution @ 120 Hz.

I have 2 21 inch screens hooked up on my server. I mainly use one.
I noticed that my monitorsetting was set to 1280x960 @ 75 Hz. So I thought, lets increase that to 1280x960@ 85 Hz.
It worked fine, initially, but after a reboot my screen went black.
rebooted with techtool 3.0.4 so I could maybe set the screen resolution to 640x480 @60Hz (and then after restart increase it to normal settings)Well, that did not work (work = give visual).
Zapping PRAM did not work either.
Reinstalling the monitorextensions from OS9.2 installcd did not work. Deleting the monitorpreferences did not work.

B]Adding the xtra monitor[/B] did not work (hoping the extra screen was in visual mode so i could try it from there)

So, I reinstalled the whole machine with OS9.2.2 again.
All this fuss took me 2 1/2 hours of inactivity. I really don't hope I will encounter this problem again.

What is the proper way of resetting monitorresolutions?

<img border="0" alt="[Hmmm]" title="" src="graemlins/hmmm.gif" />

<small>[ 06-25-2002, 02:46 PM: Message edited by: � ]</small>

[jay999]

I heard that pressing M on startup or opt + M goes through your monitor res's but I had the same problem as you and it didnt work. I think I ended up either trashing a bunch of prefs (started up from cd) like system prefs, finder prefs or reinstalling OS. Pain in the A$$.

j

[danbrew]

I have successfully booted the machine with NO monitor attached and then rebooted via the reset button with the monitor attached and it worked fine.

Step 1: Doh! Screw up the settings and get your monitor inop.
Step 2: Unplug the monitor(s).
Step 3: Restart via the reset button.
Step 4: Wait 5 minutes or so (or however long you're sure is your boot process - I just went and got a coke and came back in 5 minutes).
Step 5: Unplug the machine
Step 6: Plug in monitor(s).
Step 7: Plug in and boot.

Seems to work for me...

[j mars]

I have had a similar experience with my son's AIO (Beige G4@400, ATI Nexus card). He has been using a 15" KDS as a second monitor off the Nexus. Once he set the resolution higher than the monitor would support, realized his mistake and changed it back to 1024x768 @85hz. Since then however every time he boots with the second monitor on he gets a message that it is out of range, evidentually generated by the monitor itself. It boots fine in OS 9.2.1 but not in 10.1.5. I have tried trashing prefpanes, zapping PRAM , you name it. The only way around it is to wait until he has logged in before turning on the second monitor then all is fine, the second monitor assumes the resolution it was last set at. This has to be a problem file in Boot X or somewhere early in the boot process that is not modified later in the startup/login process. This message appears either before the gray boot screen or during it. Wish to the devil I could figure it out. Unfortunately he had put his startup sceen and menus on the second monitor which leaves us in no mans land if the second monitor is powered up. I believe that OSX is not consistent in writing to PRAM or to a pref file in BootX but finding a BootX file is beyond my knowledge.

[cube-dude]

Topic: monitors
Forum: Peripherals

Thread moved