2nd monitor won't work correctly !!!

Fresh install of xp on msi kt600 motherboard, and trying to get my G450 dual video card to work. Every time I try to enable dual monitor the 2nd screen seens to have really bad resolution and bad refresh rates. Can't figure out what is going on ....

Thats sounds far more likely to be an issue with the AGP Card or Drivers over the MoBo TBH??
If it's a fresh install have you ensured that you put the exact same Drivers back in etc lol?? I know that's a patronising question and I hate asking it, but it's so easily done these days with so much stuff we install too lol !!
Otherwise, more info too to go on and then hope ya sorted soon !!

Similar Messages

2nd Monitor won't work

I bought a Pavillion p6210f last week with Win7 loaded to replace my Dell/Vista. I was using two monitors with a VGA port and DVI port on the old PC, so I tried plugging in the same on my new HP and the DVI would not fit. In examining the pins I found that, althought the Manual said DVI, but the plug has the pin/bar arrangement of a DVI-D. So, I bought a VGAto DVI-D adapter and everything plugged in snuggly. All pins and bar appear a match.
But, it won't work. This is what is showing
NVIDIA nForce Serial ATA Controller HP RC Mirror Driver [Display adapter]
NVIDIA GeForce 9100 [Display adapter]
Acer P241W [Monitor] (24.0"vis, s/n LB4040014320, March 2008)the one working monitor....
After hours with the 800 support and hours of reversing the two Acer monitors, the DVI-D port is simply dead. Anything plugged in to the VGA works fine, anything and any combination plugged into the DVI-D and cable switching etc. the 2nd monitor is not even recoginized. The NVIDIA control panel doesn't recognize it. The amber power light just stays that way and nothing ever flashes on the 2nd screen. That is, it is the same as not plugging in at all.
I was less than pleased when 800 tech and supervisor suggested I take it to a repair center. A week old? I have put way too much setup and data transfer into the new HP to go back to the retailer for a replacement.
Techs didn't know, but could there be a DVI-X with the same pins that also fits

Eldric, did you update to the latest video driver from nVidia? It sounds to me like a driver problem. Update and let us know if that solves your problem.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

My Viewsonic monitor won't work with the Imac using the Mini Port to DVI adapter.

My Viewsonic monitor won't work with the Imac using the Mini Port to DVI adapter. I also tried the HDMI to DVI adapter ane the Mac-Mini with same result. The monitor does work on my older Macbook Pro that has the DVI connector. Is it a Software/Driver issue ?

Should be extremely simple, please carefully read Connect multiple displays to your Mac. If you still have problems then it's probably a cable issue that would be resolved by replacing the adapter cable. You should be using this adapter. If you are using a third party adapter that might be your problem!

I set up a new airport time capsule. Most devices work fine however now my apple tv 2nd gen won't work.

I set up a new airport time capsule. Most devices connected fine however now my apple tv 2nd gen won't work. I turn it on and it searches for time and date but goes no further. I can't by pass it either. Any suggestions?

I can't by pass it either. Any suggestions?
Does that mean you cannot move it to the TC and plug in by ethernet? What does bypass mean?
I would still move it closer to the TC.. and just trial it there. Range on some AC models for 2.4ghz is worse than old one. For some people.
Another thing to try is fixed wireless channels.. one of the very few options still available in the AC model.. lock the 2.4ghz to 11, 6, 1 .. try it in that order.

Flash Pro CC Debug won't work correctly

Hello. I am using trial version of Flash Pro CC and I think it's a glitch.
If there are multiple layers that have own frame script and run Debut(ctrl + alt + enter ), debug won't work correctly.
for example there are 2 layers on main stage Layer A and Layer B..
Layer A has this one trace script,
trace("1");
Layer B has those 2 trace scripts.
trace("2");
trace("3);
And I put breakpoint on trace("1"); of Layer A, and run Debug and use "Step In" to run all scripts manually.
And if trace("1"); is finished, you are supposed to get to trace("2"); but instead you will get to trace("3"); in this case.
I mean little yellow arrow, which tells me what script is running right now, is marked on trace("3");.. not on trace("2");
It seems Flash pro CC thinks Layer A's trace("1"); == Layer B's trace("2"). He can't recognize Layer A and Layer B are different.
I think it's a glitch. Does anybody notice this glitch?

Does anybody notice this glitch? I want to check if it's really a glitch or not before using newest version of Flash CC.
If it's a glitch, I will stick with CS6.

External Monitor won't work

I have a MBP 17" Late 2011 model with the Intel HD 3000 and AMD 6770M grpahics cards. I have read through many of these posts and found the exact same problem that I am having as well. I hook up a monitor through the VGA connection; Windows sees the monitor and even correctly idenifies the model; however no picture on the screen. Also, when monitor is connected is shows the startup windows screen and even the Safe boot screen; but the second it gets into the desktop the screen goes away on the 2nd monitor. I have tried many of the solutions; updating boot camp drivers, updating AMD drivers, etc. and no joy. When updating the AMD drivers, AMD's website detected that the hardware was the 6700 series and windows 64-bit; gave me the drivers to install and when installed the drivers their program ended up saying that the hardware was incompatible and not the right one. Why is this so hard and can anyone tell me what to do, also is it possible to get windows to see the Intel HD 3000 card or is that just not possible.

I have followed your advice and still no go with dual monitor through VGA. However, here is an interesting note. Using the ATI drivers from bootcamp 4.0 disk, the program detects the graphics card as a 6740 and not a 6770M. However, AMD's own website detects it as what Apple stats in their specs, a 6770M and when it give the the drivers to install that, the program won't load it saying it is the incorrect hardware/software match up, but it does the SAME decting with the boot camp drivers and goes a head and installs the drivers for the 6740. I am not sure what to do, so here's a run down again of what I have and what I need to do:
MBP 17" 2.4 GHz Intel i7, 4GB RAM 1333
Bootcamp 4.0
Windows 7 Home Premium 64-bit edition
Trying to use dual monitors through the VGA adapter, VGA adapter and cable work (works in safe mode, start up, and in OSX). Once in Windows 7 desktop, 2nd monitor goes dark and won't respond. I have gone into safe mode, uninstalled the display drivers, clean registry, reboot into safe mode, then install the bootcamp ATI graphics drivers (no go), rinse, repeat, tried using the drivers that AMD's website detects of the device (no go), rinse repeat went back to the bootcamp ATI drivers just so I can still use the main screen.Has anyone else figured out this problem.

Dual monitors won't work independently

Using win 7 ATI Raedon 4200 card. My second monitor displays only the primary desktop back ground. Followed all setup correctly please help

Vnyga, thanks but that's not it. The geek squad said something about my monitor plug ins I told them my computer recognizes the dual setup but won't work independently. He said you can keep tweak it but he has 3 monitors an although they will learn his only remembers about 70% of the time. I'm going to try hooking it up toy TV as a monitor. I just want to use it for security cameras. I do have a DVR I could use but I normally just use that when I'm ghost hunting. I'm actually I union millwright and part time ghost hunter so I'm not to well versed in computers or the talkology but I'm learning. Anyway my laptop w win8 works just fine. But... I truly appreciate I taking the time to respond an at least offer a solution thanks so much an I apologize for running my mouth on an on. Take care V.

Spry Menu Bar won't work correctly.

This is an image of what the overall menu bar layout should be like-all of the links and sublinks.
I have a few problems that I am having all relating to the spry menu bar.
I ran my code through w3c validation service but it came up with alot of errors which when corrected didn't make sense or work either.
I made this menu bar in a widget called spry menu bar 2.0. I then edited it to place in the correct names and it doesn't work correctly and the w3c validation code seems to have 43 errors with the spry bar. I am been over it a dozen times and I can't seem to figure it out. Here is the code.
Also, have I made the links correctly?
I would appreciate any help you could offer! thank you
Dreamweaver cs 5.5
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Untitled Document</title>



<style type="text/css">
#container {
    width: 1000px;
#header {
    width: 1000px;
</style>
<link href="../Stylesheet_Unicorn_main_layout_template.css" rel="stylesheet" type="text/css" />
<link href="../Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
<script src="../Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryWidget.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
<style type="text/css">
/* BeginOAWidget_Instance_2141544: #MenuBar */
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
    these rules, with the exception of the images used for down or right pointing arrows, which are in the file SpryMenuBasic.css
     These assume the following widget classes for menu layout (set in a preset)
    .MenuBar - Applies to all menubars - default is horizontal bar, all submenus are vertical - 2nd level subs and beyond are pull-right.
    .MenuBarVertical - vertical main bar; all submenus are pull-right.
    You can also pass in extra classnames to set your desired top level menu bar layout. Normally, these are set by using a preset.
    They only apply to horizontal menu bars:
        MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
        MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
        MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
        MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                        and centered in its parent container.
        MenuBarFullwidth - Grows to fill its parent container width.
    In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
    with the rules. This permits use of multiple MenuBarBasic widgets on the same page with different layouts. Because of IE6 limitations,
    there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
    background-color:#000000;
    font-family: "Comic Sans MS", cursive; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                MenuItem, and MenuItemLabel
                                                at a given level all use same definition for ems.
                                                Note that this means the size is also inherited to child submenus,
                                                so use caution in using relative sizes other than
                                                100% on submenu fonts. */
    font-weight: normal;
    font-size: 18px;
    font-style: normal;
    padding:0;
    border-color: #ffffff #ffffff #ffffff #ffffff;
    border-width:0px;
    border-style: none none none none;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
    display:none;
.MenuBarLeftShrink {
    float: left; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarRightShrink {
    float: right; /* shrink to content, as well as float the MenuBar */
    width: auto;
.MenuBarFixedLeft {
    float: left;
    width: 80em;
.MenuBarFixedCentered {
    float: none;
    width: 80em;
    margin-left:auto;
    margin-right:auto;
.MenuBarFixedCentered br {
    clear:both;
    display:block;
.MenuBarFixedCentered .SubMenu br {
    display:none;
.MenuBarFullwidth {
    float: left;
    width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
    padding: 0px 0px 0px 0px;
    margin: 0;     /* Zero out margin on the item containers. The MenuItem is the active hover area.
                For most items, we have to do top or bottom padding or borders only on the MenuItem
                or a child so we keep the entire submenu tiled with items.
                Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
    padding: 0px 10px 0px 0px;
    background-color:#000000;
    border-width:1px;
    border-color: #cccccc #ffffff #cccccc #ffffff;
    border-style: none solid none solid;
#MenuBar .MenuItemFirst {
    border-style: none none none none;
#MenuBar .MenuItemLast {
    border-style: none solid none none;
#MenuBar .MenuItem .MenuItemLabel{
    text-align:left;
    line-height:1.4em;
    color:#ff00ff;
    background-color:#000000;
    padding: 3px 3px 3px 3px;
    width: 10em;
    width:auto;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
    width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
    font-family: Arial, Helvetica, sans-serif;
    font-weight: normal;
    font-size: 16px;
    font-style: normal;
    background-color:#000000;
    padding:0px 2px 0px 0px;
    border-width:1px;
    border-color: #cccccc #cccccc #cccccc #cccccc;
    /* Border styles are overriden by first and last items */
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst {
    border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
    padding-top: 6px;
#MenuBar .SubMenu .MenuItemLast {
    border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
    padding-bottom: 6px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
    text-align:left;
    line-height:1em;
    background-color:#000033;
    color:#ff00ff;
    padding: 6px 12px 6px 5px;
    width: 7em;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
    background-color: #999999;
    border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
    background-color: #999999; /* consider exposing this prop separately*/
    color: #ff0000;
#MenuBar .MenuItemHover .MenuItemLabel{
    background-color: #999999;
    color: #ff0000;
#MenuBar .SubMenu .MenuItemHover {
    background-color: #cccccc;
    border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
    background-color: #cccccc;
    color: #ff0000;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
    background-color: #000000;
    min-width:0%; /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
    border-color: #ffffff #ffffff #ffffff #ffffff;
    border-width:0px;
    border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
    top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
    left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                    and your personal taste.
                    0px will left align the dropdown with the content area of the MenuItemContainer. Assuming you keep the margins 0
                    on MenuItemContainer and MenuItem on the parent
                    menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                    the dropdown with the left of the menu item label.*/
    z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
    top: 0px;
    left:100%;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
    background-color: #000000;
    min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
    top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                vertically 'centered' on its invoking item */
    left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                to use px or ems to get the offset you want. */
/* IE6 rules - you can delete these if you do not want to support IE6 */
/* A note about multiple classes in IE6.
* Some of the rules above use multiple class names on an element for selection, such as "hover" (MenuItemHover) and "has a subMenu" (MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in a selector for an element. For a selector such as '.foo.bar.baz', IE6 ignores
* all but the final classname (here, '.baz'), and sets the specificity accordingly, counting just one of those classs as significant. To get around this
* problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
* Since there are a lot of these needed, the plugin does not generate the extra classes for modern browsers, and we use the CSS2 style mutltiple class
* syntax for that. Since IE6 both applies rules where
* it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
* So, we put the multiple class rule first. IE6 will mistakenly apply this rule. We follow this with the single-class rule that it would
* mistakenly override, making sure the misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
* We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
* the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
* css style block to make it easy to delete if you want to drop IE6 support.
* If you decide you do not need IE6 support, you can get rid of these, as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.js script.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser is Internet Explorer 6. This avoids the necessity of IE conditional comments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
    background-color: #999999; /* consider exposing this prop separately*/
    color: #ff0000;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
    background-color: #cccccc; /* consider exposing this prop separately*/
    color: #ff0000;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
    margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
/* EndOAWidget_Instance_2141544 */
</style>
<script type="text/xml">

</script>
</head>
<body>
<div id="container">
<div id="header">Unicorn Writers Conference</div>

<div id="menubar_left">
    <ul id="MenuBar">
      <li> <a href= "../Pages/home.html">Home</a></li>
      <li> <a href="#">Events</a>
      <li> <a href="#">Mission Statement</a>
      <li> <a href="#">Resources</a>
        <ul>
          <li> <a href="#">Advanced networking</a></li>
          <li> <a href="#">Query Review</a>
          <li> <a href="#">Ms Review Sessions</a>
          <li> <a href="#">1-1 Sessions</a>
          <li> <a href="#">Workshops</a>
          <li> <a href="#">Genre Chart</a>
          <li> <a href="#">Writers Links</a>
               </ul></li>
                  <li> <a href="#">Key Presenters</a>
                      <ul>
                        <li> <a href="#">Speakers</a>
                            <ul>
                                <li> <a href="../Pages/2013_speakers_page.html">Speakers 2013</a></li>
                                <li> <a href="#">Speakers 2012</a>
                            </ul>
                        <li> <a href="#">Editors</a>
                            <ul>
                                <li> <a href="#">Editors 2013</a></li>
                                <li> <a href="../Pages/2012_editors.html">Editors 2012</a>
                            </ul>
                        <li> <a href="#">Literary Agents</a>
                            <ul>
                                <li> <a href="../Pages/2013_L_agents.html">Literary Agents 2013</a></li>
                                <li> <a href="../Pages/2012_editors.html">Literary Agents 2012</a>
                          </ul>
                     </ul>
                  <li> <a href="#">Information</a>
                      <ul>
                        <li> <a href="#">St. Clements</a></li>
                        <li> <a href="#">Directions</a></li>
                        <li> <a href="#">Hotels</a></li>
                        <li> <a href="#">Menu</a></li>
                        <li> <a href="#">Unicorn Photo Gallery</a></li>
                        <li> <a href="#">Day Schedule</a></li>
                        <li> <a href="#">FAQ</a></li>
                        <li> <a href="#">Staff</a></li>
                        <li> <a href="#">Contact</a></li>
                      </ul>
                  <li> <a href="#">Registration</a></li>
                  <li> <a href="#">Acclaim</a>
                      <ul>
                          <li> <a href="#">Spotlights</a></li>
                          <li> <a href="#">Testamonials</a>
                        <li> <a href="#">Sponsorship</a>
                    </ul>
                  <li> <a href="#">Classifieds</a>
                      <ul>
                        <li> <a href="#">View</a></li>
                        <li> <a href="#">Place</a></li>
                    </ul>
                  <li> <li> <a href="#">Merchandise</a></li>
                </ul>
              </li>
          </li>
        </ul>
      </li>
    </ul>
    <script type="text/javascript">
// BeginOAWidget_Instance_2141544: #MenuBar
var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
      widgetID: "MenuBar",
      widgetClass: "MenuBar MenuBarVertical MenuBarMenuBarVerticalLeftShrink",
      insertMenuBarBreak: true,
      mainMenuShowDelay: 100,
      mainMenuHideDelay: 200,
      subMenuShowDelay: 200,
      subMenuHideDelay: 200
// EndOAWidget_Instance_2141544
    </script>
</div>

<div id="main_content">Content for New Div Tag Goes Here</div>
</div>
<div id="footer">Content for id "footer" Goes Here</div>
</body>
</html>

These Spry support files are all 404 Not found on server.
<link href="../Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
<script src="../Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryWidget.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
Nancy O.

Ipod shuffle 2nd gen won't work, light flashing green and orange

My 2nd gen ipod shuffle won't work and the light is flashing green and orange. Or green, orange, orange, orange. I've Reset, Restarted, Restored and Re-installed, so before I chuck it out I wondered if there were any other suggestions to get it working? Thanks,

Sounds like it's still under warranty (one year). Take it back for replacement.

My MacBook and my Monitor won't work together anymore

Ok i have a macbook i got less than a year ago and for the last 2 months i have been running my old samsung monitor off of a mac mini port to VGA and now it won't work anymore when ever i connect it the monitors light just flashes on and off repeatedly but the screen turns black i have tried adjusting the sizing but it wont work...
I know its connected cause the screen blinks blue and the windows that are set to open on it still do and i have to drag them over to see them

Try:
- Reset the iOS device. Nothing will be lost
Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Reset all settings
Go to Settings > General > Reset and tap Reset All Settings.
All your preferences and settings are reset. Information (such as contacts and calendars) and media (such as songs and videos) aren’t affected.
- Restore from backup. See:
iOS: Back up and restore your iOS device with iCloud or iTunes
- Restore to factory settings/new iOS device.
If still problem, make an appointment at the Genius Bar of an Apple store since it appears you have a hardware problem.
Apple Retail Store - Genius Bar
Unless you purchased the optional AppleCare+ extended warranty,
Apple will exchange your iPod for a refurbished one for $99 for 16 GB 5G and $149 for the other 4Gs. They do not fix yours.
Apple - iPod Repair price

Hyundai LCD monitor won't work with OS9

New Hyundai LCD monitor -dual input. Works fine with Windows XP, & with OS 10 but when I boot into OS9 the screen goes black, & the screen's menu button won't work. Have started os9 in safe mode but cannot find how to change the display/resolution/refresh settings. Where do I look to change these settings? And what settings should I try?

Have posted more on this in thread in "older hardware".
http://discussions.apple.com/thread.jspa?messageID=6115403#6115403. I hope this is the right link, thought I shouldn't duplicate postings.
Would very much welcome any more suggestions you might have
It's ATY rage 128 pro, VRAM 16MB
1024x768@60HZ, 32 bit colour

Preview Monitor won't Work

I am using a Blackmagic card and have updated the codecs - I did a chat with Adobe and they remotely controlled my computer and still couldn't get it to work. The monitor works fine with Final Cut but won't work with Premier CC. Help.

Hmmm ... not sure where to even start, you didn't include enough details really ...
For starters ... OS/version, which CC build you're running, some things like that? Around here this is a puzzle-out space with most of participants being "peers" in being users and not Adobe staff. Some staff post here on their own time, and are a great help. But so are many of the regular joe's and joeleen's who inhabit this space.
Not thrilled that Adobe chat & help folks couldn't find the issue, but we'll see if someone around here will take on the challenge ...
neil

G4 AGP Graphics - 2nd display won't work after upgrading from os 10.2

I have a desktop G4 AGP Graphics with two displays. When I was running os 9-10.2, the second display worked fine, but after upgrading the os (now running 10.4), the second display still works, but has turned gray and pixelated.
When I take a screen shot, the picture shows that both displays appear clear (and in color).
Am I missing something? Thanks in advance for any suggestions

so do you have 2 different video cards driving two different monitors? or is it One video card with 2 displays?
the info you listed isnt very detailed but it does tell me you got an ATI video card with 16MB VRAM.
I assume that thats the Stock AGP 2x graphics card that came the The PowerMac G4 AGP graphics model.
why is your display set to 8bit depth? a stock 2x AGP card with 16MB VRAM should be able to support 16bit or 24bit depth even at 1024 x 768 res.
the info says also Core image not support as well as Quartz Extreme no supported. Which is significant because it could be why the 2nd Monitor doesnt display properly with Tiger.
under 10.2 there were less stringent requirements for driving video.
OSX 10.4 Tiger is much more advanced OS and has higher graphics cards requirements now.
I could be wrong, but I think you may need a newer video card that supports Quartz Extreme and Core image.
hopefully someone else will run by this topic and offer some insight aside from my own.

Have compaq desk top, trying to hook up HD flat screen monitor, won't work?

Haave Compaq, desk top, trying to hook up, HD, flat screen monitor, won't work

Hello redheadjennieo,
I'm not sure Apple is going to write drivers for a Windows Operating System, so we may have to rely on the generic drivers.
What model pavilion do you have?
What operating system?
Does the monitor say anything on the screen when it's connected to the computer and you turn it? (e.g. signal out of range, no input, etc)
If I have helped you in any way click the Kudos button to say Thanks.
The community works together, click Accept as Solution on the post that solves your issue for other members of the community to benefit from the solution.
- Friendship is magical.

2nd monitor fails to work after upgrade to 10.4.6

Hi,
I have been running fine with 2 monitors until I upgraded to 10.4.6, and now my 2nd monitor is not detected (even after I click the detect displays).
Apart from the upgrade - I have changed nothing
Other Info:
GeForce FX 5200:
Chipset Model: GeForce FX 5200
Type: Display
Bus: AGP
Slot: SLOT-1
VRAM (Total): 64 MB
Vendor: nVIDIA (0x10de)
Device ID: 0x0321
Revision ID: 0x00a2
ROM Revision: 2060
Displays:
Cinema HD Display:
Display Type: LCD
Resolution: 1920 x 1200
Depth: 32-bit Color
Core Image: Supported
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display:
Status: No display connected
Any thoughts/ideas.
cheers
-brett

Resolved:
After a few reboots and a couple of power cycles, it all just started working.
cheers
-brett

2nd monitor won't work correctly !!!

Similar Messages

Maybe you are looking for