Sponsored Content
Operating Systems OS X (Apple) OS X Support RSS Mac OS X: No video after changing resolutions in Display preferences Post 302240946 by Linux Bot on Saturday 27th of September 2008 07:12:39 AM
Old 09-27-2008
Mac OS X: No video after changing resolutions in Display preferences

If you deselect the checkbox for "Show modes recommended by display" and then choose a non-recommended resolution, the display may go blank (display no image). Note: This document applies to Mac OS X 10.0 through 10.3.9. If you deselect the checkbox for "Show modes recommended by display" and then choose a non-recommended resolution, the display may go blank (display no image).

More from Apple OS X Support ...
 

2 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Display resolutions

Hi, I have recently install SUSE 9.1 on my laptop The resolution only comes up in 800x600 i dont get any other options but also is shown as a small box rather than the whole screen. In windows it is fine and covers the full display. I tried to set the dismensions but this doesn't work ... (3 Replies)
Discussion started by: billett05
3 Replies

2. Solaris

video display

i needed to build a quick and dirty solaris 10 box for some dev work. basically a web server. anyway, i grab some deal off tigerdirect and have a x86 install. however, i'm running into problems with the video display. currently have a SAPPHIRE 100122L Radeon X700 256MB 64-bit DDR PCI Express x16... (1 Reply)
Discussion started by: pupp
1 Replies
XInitThreads(3X11)						  XLIB FUNCTIONS						XInitThreads(3X11)

NAME
XInitThreads, XLockDisplay, XUnlockDisplay - multi-threading support SYNTAX
Status XInitThreads(); void XLockDisplay(display) Display *display; void XUnlockDisplay(display) Display *display; ARGUMENTS
display Specifies the connection to the X server. DESCRIPTION
The XInitThreads function initializes Xlib support for concurrent threads. This function must be the first Xlib function a multi-threaded program calls, and it must complete before any other Xlib call is made. This function returns a nonzero status if initialization was suc- cessful; otherwise, it returns zero. On systems that do not support threads, this function always returns zero. It is only necessary to call this function if multiple threads might use Xlib concurrently. If all calls to Xlib functions are protected by some other access mechanism (for example, a mutual exclusion lock in a toolkit or through explicit client programming), Xlib thread ini- tialization is not required. It is recommended that single-threaded programs not call this function. The XLockDisplay function locks out all other threads from using the specified display. Other threads attempting to use the display will block until the display is unlocked by this thread. Nested calls to XLockDisplay work correctly; the display will not actually be unlocked until XUnlockDisplay has been called the same number of times as XLockDisplay. This function has no effect unless Xlib was successfully initialized for threads using XInitThreads. The XUnlockDisplay function allows other threads to use the specified display again. Any threads that have blocked on the display are allowed to continue. Nested locking works correctly; if XLockDisplay has been called multiple times by a thread, then XUnlockDisplay must be called an equal number of times before the display is actually unlocked. This function has no effect unless Xlib was successfully ini- tialized for threads using XInitThreads. SEE ALSO
Xlib - C Language X Interface X Version 11 Release 6.6 XInitThreads(3X11)
All times are GMT -4. The time now is 03:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy