![]() Once it was installed, the command line: display_manager.py res 1920 1200 ext0 I'm afraid to try it to set the black external monitor to be my main screen, and that seems to be the only experiment it might be useful for.įinally, I found a solution that worked for me! In another Ask Different question, " change screen resolution with AppleScript", more than one AppleScript solution was offered (which I didn't try) AND posted a link to a utility developed at the University of Utah, Display Manager which worked for me.ĭisplay Manager supposedly has a GUI interface available, but I couldn't find where it had been installed to invoke it, so I used the command line interface. I looked at the doc for hmscreen and it confirms that it deals with ScreenIDs, screen positions, and which screen is the main screen, not resolution. ![]() Similarly, the answer about hmscreen is about Arrangement, not Resolution. I can verify that Colorsync Utility.app does nothing for resolution, only color profile, and my profile is likewise set to Factory Default. This sounds like exactly the problem that reported, same cause, same results. When I return to Mirror Displays mode, I can see that the wrong resolution is set and when I set the proper one, I get both monitors work - but ONLY if I stay in Mirror Displays mode. ![]() I cannot see the System Preferences > Displays control dialog for that monitor because it's on the black screen. When in separate mode, the external monitor is black except for a message saying "DVI NO SIGNAL". I, too, clicked on the wrong resolution for my external monitor and now I can only use the monitor in "Mirror Displays" mode. Maybe I can move the ball forward a couple of inches. Neither of the above two answers has solved the problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |