Is there a way to turnt he monitor off? i tried the power management thing and it doesnt turn it off, i also tried setting a screen saver and it wont work either :"(
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Turn off monitor in windows?
- Thread starter evangelion-01
- Start date
- Sort by reaction score
turn off imac monitor in windows?
did you figure out how to turn off the monitor in bootcamp windows? I'm having the same problem.
did you figure out how to turn off the monitor in bootcamp windows? I'm having the same problem.
Start/Control Panel/Display (I make a shortcut for this on my Desktop)/Screen Saver -- and pick a wallpaper and time delay.
Or
Start/Control Panel/Power Options -- and then pick a Power Scheme from the drop down list and make whatever modifications you want to the settings that power down your monitor.
If those don't work, perhaps I'm not really understanding what you're wanting to do.
Or
Start/Control Panel/Power Options -- and then pick a Power Scheme from the drop down list and make whatever modifications you want to the settings that power down your monitor.
If those don't work, perhaps I'm not really understanding what you're wanting to do.
I'm having this same problem, with the newest BootCamp. (downloaded it today). How do I turn off this monitor?!
Turn off Monitor?
I'm having the same trouble - not being able to turn off the monitor in Windows XP with Boot Camp 1.4 ( or 1.2, 1.3). I've had this problem all along. I have the 24" iMac. Maybe that's why...? My laptop and 17" iMac are fine. Something with this computer.
Any ideas? It's driving me crazy - thinking that the screen will burn out one day...
There must be more than 2 other people in the world out there experiencing this!
Thanks,
I'm having the same trouble - not being able to turn off the monitor in Windows XP with Boot Camp 1.4 ( or 1.2, 1.3). I've had this problem all along. I have the 24" iMac. Maybe that's why...? My laptop and 17" iMac are fine. Something with this computer.
Any ideas? It's driving me crazy - thinking that the screen will burn out one day...
There must be more than 2 other people in the world out there experiencing this!
Thanks,
I was able to turn off (as in disable) the monitor on my mbp by setting options in the ATI catalyst control center. I have x1600 graphics.
short version:
1. Boot camp 2.1 hosed my video drivers: 4-bit color, 640x480 resolution, unchangeable
2. ATI driver download page yielded no solution
3. Googled ATI bootcamp driver: this provided a working driver from ATI
4. downloaded and installed this driver: repaired graphics resolution, color depth
5. these drivers didn't allow much control over monitor options
6a. Downloaded catalyst control center from same web page in step 3.
6b. installation/running the control center was not successful, yields cryptic error message
6c. uninstalled control center, downloaded and installed dot NET framework from microsoft, reinstalled control center
7a. (for notebook users) go to windows' power management, select "do nothing" upon closing lid
7b. in the catalyst control center software, set my external monitor (LCD TV) as primary monitor, disabled the mbp's fixed LCD. Corrected the stupid default underscan setting to have perfect output in 1080p mode.
Now I have what amounts to clamshell mode working in windows XP, and can play windows games from my sofa with a wireless keyboard and mouse.
short version:
1. Boot camp 2.1 hosed my video drivers: 4-bit color, 640x480 resolution, unchangeable
2. ATI driver download page yielded no solution
3. Googled ATI bootcamp driver: this provided a working driver from ATI
4. downloaded and installed this driver: repaired graphics resolution, color depth
5. these drivers didn't allow much control over monitor options
6a. Downloaded catalyst control center from same web page in step 3.
6b. installation/running the control center was not successful, yields cryptic error message
6c. uninstalled control center, downloaded and installed dot NET framework from microsoft, reinstalled control center
7a. (for notebook users) go to windows' power management, select "do nothing" upon closing lid
7b. in the catalyst control center software, set my external monitor (LCD TV) as primary monitor, disabled the mbp's fixed LCD. Corrected the stupid default underscan setting to have perfect output in 1080p mode.
Now I have what amounts to clamshell mode working in windows XP, and can play windows games from my sofa with a wireless keyboard and mouse.
1) There is NO SUCH THING as "bootcamp Windows". The OS is called "Microsoft Windows". PERIOD.
2) BootCamp Assistant is an OSX application, and has nothing to do with the operation of Windows.
3) BootCamp Assistant is ONLY a partitioning utility, EXPRESSLY used for creating Windows system partitions on an Intel-based Apple PC.
4) Once the Windows OS is loaded into memory, OS X simply does NOT exist to Windows. Nor does BootCamp Assistant, since it is NOT a Windows application.
5) The OS X partitions do not exist once Windows is loaded into memory.
6) There is NO COMMUNICATION between OS X and Windows once Windows takes over the machine.
7) In fine, BootCamp Assistant has NOTHING TO DO WITH THE OPERATION OF WINDOWS. PERIOD.
PLEASE, get your information from the source, not Apple.
1) Apple does NOT support Windows.
2) Microsoft does NOT support Apple.
WHY ask Mac users about Windows? Ask WINDOWS users, if you want information.
Donald L McDaniel
Correction to your very first statement:
While you DO have an "x1600" card, keep in mind that it is a MOBILITY card, not a normal Desktop card. It cannot use Desktop drivers.
To answer the rest:
1) BootCamp has nothing to do with Windows drivers. Therefore, it could NOT have "hosed your drivers" in Windows, being nothing but an OS X partitioning utility for creating Windows Partitions on your HFS+ formatted drive. Maybe in OS X, but NOT Windows itself, since once Windows is in control of the machine, BootCamp Assistant is NO LONGER in memory, being an OS X application. The two OS's code-bases are MUTUALLY EXCLUSIVE, since they are -- guess what: TWO different OS's.
1-Continued) If, on the other-hand, you are referring to the "Macintosh Drivers for Microsoft Windows" installation utility, you must speak to Apple about it, since THEY write it, NOT Microsoft. Apple is reponsible for their OWN drivers. Microsoft does NOT write OEM drivers. PERIOD. Apple is nothing but another OEM, as far as Microsoft is concerned. Get used to it.
2) ATI does NOT publish Mobility drivers for Macintoshes running Windows.
The ONLY place to get such drivers is: You guessed it: APPLE!
3) The ATI Control panel installation under Windows requires the presence of .NET 2.0. Which is why you probably got "cryptic characters" on the display. If you want to use the ATI control panel, you must install DOTNET 2.0 or above.
6c) If you had read the instructions for installation of the drivers, you would not have had to do this step, since you would already have installed .NET 2.0 BEFORE attempting to install the drivers and the Control Panel (unless of course, you simply refused to believe a word spoken about Microsoft Windows.)
7B). The "default" setting for ATI's Control Panel is to "use the display's built-in scan settings". If you want to blame someone for the "stupid underscan settings" for your Mac Book Pro's display, blame APPLE, not ATI or Microsoft, neither of whom had anything to do with the display's construction, its default scan settings, or the Apple display driver model.
Donald L McDaniel
As far as I know, LCDs do not "burn out", nor do they have a "burn-in" problem like CRTs do.
Additionally, the latest drivers are NOT "2.1 BootCamp" drivers. They are "Macintosh Drivers for Microsoft Windows."
BootCamp Assistant does not use these drivers, OS X does not use these drivers, nor does Linux use these drivers. MICROSOFT WINDOWS ALONE uses the drivers (poor as they are).
Additionally, if your display DOES "burn out" while using Microsoft Windows, neither Microsoft NOR apple will replace the display, since Microsoft Windows is not supported by Apple, nor are Apple drivers supported by Microsoft.
Donald L McDaniel
These drivers are NOT "Boot Camp drivers". PERIOD.
They are "Macintosh Drivers for Microsoft Windows." (i.e., "WINDOWS DRIVERS")
Donald L McDaniel
1) While you ARE using Microsoft Windows on your Apple Intel-based PC, you do NOT have "Windows XP with BootCamp": You have "Windows XP installed on your Apple Intel-based PC." Nothing more, nothing less.
2) BootCamp Assistant has absolutely NOTHING to do with the operation of Windows. It is a strictly OSX application, and because of this, does NOT exist as far as Windows XP is concerned.
3) My idea? Get rid of your iMac and get a proper machine for running Windows. Then you won't have to deal with shoddily-constructed Windows drivers written by non-Windows programmers.
Donald L McDaniel
Why can't you just turn the display off by pressing the display power key?
"DOH!!"
Donald L McDaniel
There is simple way of doing this on your Apple Intel PC: turn it off using the Display's hardware Power button."
DOH!!
Donald L McDaniel
Correction to your very first statement:
While you DO have an "x1600" card, keep in mind that it is a MOBILITY card, not a normal Desktop card. It cannot use Desktop drivers.
To answer the rest:
1) BootCamp has nothing to do with Windows drivers. Therefore, it could NOT have "hosed your drivers" in Windows, being nothing but an OS X partitioning utility for creating Windows Partitions on your HFS+ formatted drive. Maybe in OS X, but NOT Windows itself, since once Windows is in control of the machine, BootCamp Assistant is NO LONGER in memory, being an OS X application. The two OS's code-bases are MUTUALLY EXCLUSIVE, since they are -- guess what: TWO different OS's.
1-Continued) If, on the other-hand, you are referring to the "Macintosh Drivers for Microsoft Windows" installation utility, you must speak to Apple about it, since THEY write it, NOT Microsoft. Apple is reponsible for their OWN drivers. Microsoft does NOT write OEM drivers. PERIOD. Apple is nothing but another OEM, as far as Microsoft is concerned. Get used to it.
2) ATI does NOT publish Mobility drivers for Macintoshes running Windows.
The ONLY place to get such drivers is: You guessed it: APPLE!
3) The ATI Control panel installation under Windows requires the presence of .NET 2.0. Which is why you probably got "cryptic characters" on the display. If you want to use the ATI control panel, you must install DOTNET 2.0 or above.
6c) If you had read the instructions for installation of the drivers, you would not have had to do this step, since you would already have installed .NET 2.0 BEFORE attempting to install the drivers and the Control Panel (unless of course, you simply refused to believe a word spoken about Microsoft Windows.)
7B). The "default" setting for ATI's Control Panel is to "use the display's built-in scan settings". If you want to blame someone for the "stupid underscan settings" for your Mac Book Pro's display, blame APPLE, not ATI or Microsoft, neither of whom had anything to do with the display's construction, its default scan settings, or the Apple display driver model.
Donald L McDaniel
vista trollboy = epic fail
ATI drivers for macs can be found here:
http://ati.amd.com/support/drivers/mac/bootcamp-xp.html
I've used and administered windows machines for well over a decade. I am pretty certain that it is reasonable to specify windows in boot camp, as many, including myself, also run windows in a virtual machine.
Re: Turn off monitor in Windows?
The ONLY "problem" Boot Camp Assistant "fixes" is giving OSX users a cheap means of creating a Windows System Partition on their HFS+ formatted drives.
As I have said over and over and over, "BOOT CAMP ASSISTANT has absolutely NOTHING to do with the way Windows operates once it is installed."
The "Macintosh Drivers for Microsoft Windows" have nothing to do with BootCamp Assistant. They are strictly WINDOWS DRIVERS, for use within WINDOWS. Like all other OEM drivers, they are NOT written by Microsoft, and any support for them will come from APPLE, not Microsoft, which does NOT provide support for OEM software/hardware. Like Apple, Microsoft ONLY supports its OWN hardware/software. DRIVERS are NOT "Microsoft software". They are "OEM" software, which Microsoft does NOT support.
Of course, Apple has stated that it does not "officially" support the use of Windows on their machines, anyway. This includes, apparently, support for their OWN OEM Windows drivers.
So, really, when it gets right down to it, NO ONE IS GOING TO SUPPORT you, so you might as well learn how to support yourself, as Windows users have been doing for years. You wanted "in". Now live with it.
Donald L McDaniel
I have the same problem on my MacBook PRO SR 2.4 too...
Latest Boot Camp doesn`t fix that problem, so waiting for new drivers
The ONLY "problem" Boot Camp Assistant "fixes" is giving OSX users a cheap means of creating a Windows System Partition on their HFS+ formatted drives.
As I have said over and over and over, "BOOT CAMP ASSISTANT has absolutely NOTHING to do with the way Windows operates once it is installed."
The "Macintosh Drivers for Microsoft Windows" have nothing to do with BootCamp Assistant. They are strictly WINDOWS DRIVERS, for use within WINDOWS. Like all other OEM drivers, they are NOT written by Microsoft, and any support for them will come from APPLE, not Microsoft, which does NOT provide support for OEM software/hardware. Like Apple, Microsoft ONLY supports its OWN hardware/software. DRIVERS are NOT "Microsoft software". They are "OEM" software, which Microsoft does NOT support.
Of course, Apple has stated that it does not "officially" support the use of Windows on their machines, anyway. This includes, apparently, support for their OWN OEM Windows drivers.
So, really, when it gets right down to it, NO ONE IS GOING TO SUPPORT you, so you might as well learn how to support yourself, as Windows users have been doing for years. You wanted "in". Now live with it.
Donald L McDaniel
1. This is an old thread.
2. Try other third party drivers for windows
https://forums.macrumors.com/showthread.php?p=5377806#post5377806
2. Try other third party drivers for windows
https://forums.macrumors.com/showthread.php?p=5377806#post5377806
Solution work for me
First download nVIDIA ForceWare X 179.13 for Windows XP/2K from http://www.laptopvideo2go.com/forum/index.php?showtopic=20809
download both driver and moddedinf replace.
extract driver to somewhere and replace moddedinf file in the folder
finally just install from setup and reboot
the problem should be solved
Enjoy hope u all happy with this problem now
First download nVIDIA ForceWare X 179.13 for Windows XP/2K from http://www.laptopvideo2go.com/forum/index.php?showtopic=20809
download both driver and moddedinf replace.
extract driver to somewhere and replace moddedinf file in the folder
finally just install from setup and reboot
the problem should be solved
Enjoy hope u all happy with this problem now
problem solved.
It works for me also. The difference is my Mac is Imac 24'' and the graphic driver is Nvidia Geforce 7300GT. I downloaded the latest driver from http://www.nvidia.com/Download/index.aspx?lang=en-us
After installation and restart, my monitor can be turned off autonomously now!
It works for me also. The difference is my Mac is Imac 24'' and the graphic driver is Nvidia Geforce 7300GT. I downloaded the latest driver from http://www.nvidia.com/Download/index.aspx?lang=en-us
After installation and restart, my monitor can be turned off autonomously now!
This one: http://www.laptopvideo2go.com/forum/index.php?showtopic=21308
works good for the 8600M GT MacBook Pros.
works good for the 8600M GT MacBook Pros.