[Solved] Screen resolution problem in a qemu guest

Hi, I have a problem with my arch os on qemu : there is a black line (near 100 pixels high) on the bottom of the virtual screen, and when i put the cursor on the bottom the screen slide (I don't see the top part of the virtual screen). I use "-vga qxl" option, and I use dwm on both the guest and the host.
Have you any ideas from where this problem could come from?
Thanks for reading, and sorry for my English, I hope you understood what I said...
Last edited by c4ffein (2014-07-26 15:08:08)

Well, you can set the resolution yourself, check 'xrandr'.
Did you set the mouse to -usbdevice tablet or -usbdevice mouse?, otherwise try the latter former. There is some kind of solution https://wiki.archlinux.org/index.php/QE … or_erratic, which don't work good enough for me, but might work for you.
Btw. nothing wrong with your English
edit;it was late
Last edited by qinohe (2014-07-26 13:36:57)

Similar Messages

[SOLVED] Screen/Resolution problem in Gnome/Xfce

Hello,
My default resolution on starting gnome or xfce is 1024x768. It looks fine and the fonts are definitely pleasant.
One problem: The screen is cut off from the left and right (two black bands on the sides), because of which I'm losing, say, 1/5th of the width (moreover, its irritating).
I'm able to change the resolution from within gnome/xfce to 1280x800 in which case the black bands on the sides disappear and gnome/xfce is using the full width. But now the fonts are not that good; not as smooth.
Is this some basic hardware recognition problem?
Faraz.
Last edited by fh (2009-07-13 17:31:38)

This is now solved. I changed xorg.conf to include 1280x768 along with other resolutions. And then xfce/Appearance lets me set LCD, GRB, aliasing options.

How to solve screen resolution in bdc

hi experts,
please tell me how to solve screen resolution in bdc.
regards.
subhasis

Hi,
<b>Pls check other posts in SDN before posting ur thread..there is same thread related to this on this forum on same day.</b>
Screen resolution means different in the screen display depending on ur system screen resolution.
suppose ur system resolution is diff and another's system is different then like in Tcode VA01, there will be 3 lineitems and another there will be 5 lineitems ,
so while doing recording and page down that will bw diff so there will be some problem
So u have to set the screen resolution as default by using CTU parameters..
write this code then
f_option-updmode = 'S'.
f_option-defsize = 'X'.* f
_option-dismode = 'N'.
*call transaction 'VA01' using bdcdata options from f_option messages into bdcerror.
Hope it helps.
Regards,
Sonika

EHP1 Upgarde Monitor screen resolution problem in a support message

Hi Experts,
We have recently upgraded our Solution manager to EHP1, iam facing a screen resolution problem with 15 inch monitors.
Our key users have 15 inch monitors to their system and when they try to reply a support message under transaction data-> Overview tab -> reply it is showing only one line for them , due to which they are unable to enter the complete data in it.
How ever We have found that this does not occur with 17 inc monitors as the required screen resoution 1280* 1024 is possible due to bigger size of the monitor.
can any one suggest how to make the overview tab visible completely with small resolution monitors.
Thanks
Nanda

>
Nanda Kishore wrote:
> Hi
>
> There is an note from sap on this issue i couldnt remember the note number which talks about updating your package levell
>
> Kindly check this note it was released in SEP 09 a very recent one. this will resolve your probelm.
SAP Note 1351673 Size of containers not changed for support messages
Best regards,
Ruediger

Screen resolution problem in table control

when i was transfering data in BDC using table control,i got screen resolution problem.
how to rectify the problem?

Hi,
Check this coding.
WA_CTU_PARAMS type ctu_params.
WA_CTU_PARAMS-DISMODE = 'N'. "no screen mode
WA_CTU_PARAMS-UPDMODE = 'S'. "synchronous update
WA_CTU_PARAMS-NOBINPT = 'X'.
WA_CTU_PARAMS-NOBIEND = 'X'.
WA_CTU_PARAMS-DEFSIZE = 'X'. "Default size
CALL TRANSACTION 'VA01' USING it_bdcdata
OPTIONS FROM WA_CTU_PARAMS
MESSAGES INTO it_mesg.
Default size will play good role in terms of resolution. in one system in table control you can see 10rows, but in others system it will show 20 records. it depends on resolution. but when you set the default size then it will take same (default screen size) in all the systems when you run BDC.
Hope this resolves your query.
Reward all the helpful answers.
Regards

Screen Resolution Problem in Session Method

Hi
I want to use session method in BDC. How to resolve screen resolution problem in Session Method?
Please give me the code or steps regarding this.
Thanks & Regards
venkateswararao

Hi
U can only run the session with the option Dynpro Standard Size setted.
In this way the system should be use the same resolution for every situation.
Max

To Resolve Screen Resolution Problem

Hi
How to resolve screen resolution problem in BDC Session Method. can't we use ctu_params?
Thanx & Regards
venkat

Hi Venkat,
Yes, you can use ctu_params.
This is for Default screen size for CALL TRANSACTION. It signifies the screen size will be constant irrespective of the screen resolution(which can vary for different user). The importance of this lies in programs(module pool) that contain table controls. With default screen size we can control the no of rows in the table control which otherwise may vary depending on the screen resolution.
DEFSIZE is the Selection as to whether the screens of the called transaction are displayed in the standard screen size. Values "X" (standard size), " " (current size).
sample.
data : x_ctu_params type ctu_params.
To have default screen size, mode and update
x_ctu_params-defsize = 'X'.
x_ctu_params-dismode = 'X'.
x_ctu_params-updmode = 'X'.
call transaction tscode using bdcdata
options from x_ctu_params
Regards,
Ferry Lianto
Please reward points if helpful.

Message says "screen resolution problem" and says to set higher than 1020 x 600. My screen resolution is set higher. Why am I getting this message all the time I use firefox?

when I go on to Firefox I keep getting the message that there is a screen resolution problem and it says I should set it higher a than 1020 X 600. But my screen resolution is set higher. It is set at 1360 x 768. Why am I getting this message continuously?

I've had the problem too... for at least a month or more. It would happen when logging into yahoo mail. But it happens only with firefox... not explorer. I contacted yahoo and he had me first disable add ons... no change... and since it didn't happen with explorer, they said to contact firefox. So I followed the advice of cor-el's post (on this page) and made the text on my page smaller... It did fix the issue.... but, I liked the size of the text the way I had it. So, how do I get it back to that size, and not have that annoying message any longer? thanks!!

Screen resolution problem in Microsoft Test Manager by Testing Windows Store Apps

Hi,
we are trying to perform tests of Windows Store Apps in a remote device (tablet), so as it is explained in:
http://msdn.microsoft.com/en-us/library/hh405417.aspx
However, when we take a screenshot or we record a video, it is only shown a little part of the screen, because PC and Tablet screen resolutions are different.
How could we solve this problem? Any idea?
Thanks.

Hi david_vr,
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

NB200-10G Screen resolution problem

Hi,
My new NB200 does not display the toolbar when booted. It is there, I think, because if I click wildly below the visible screen there is sometimes a reaction. This seems like a screen resolution issue. When the system boots, the windows theme is distorted, as if the resolution was for a bigger screen. I have tried every combination of screen resolution but it doesn't solve it.
Please help; this is totally destroying my pleasure at owning this new machine!
Many thanks
Satis

Hi,
I have a new NB200 and exactly the same thing has occurred: The NB200 booted up correctly (POST test BIOS screen OK), but when the display switched to Windows, the login dialog box was shifted down: From there on in, the task bar was not visible (but worked when pressing the windows hot key) and the desktop items were re-sorted. The Auto hide taskbar feature is disabled.
Rebooting the PC (Power down & restart) fixes the display problem about 50% of the time.
Did anyone resolve this issue?
Thanks - Richard.

Screen Resolution Problem (Max. Resolution of only 1024x768)

Hello,
I just upgraded my T61 laptop from Windows XP to Windows 7, Everything was fine at first. But one day when I turned on my laptop, I found out that the screen resolution was wrong. It was only 1024x768 (not wide screen). As a result, the screen was on the left, leaving a thick black bar on the right. The given resolutions which I could choose are only 800x600 and 1024x768, no wide screen options. Tried nvidia control panel, it was still the same. Tried to connect to an external monitor (16:9 wide screen), the resolution was, however, perfect (fit the external monitor).
I already have the newest display driver (nvidia Quadro NVS 140m - downloaded from Lenovo). I even reinstalled the driver and installed the monitor driver provided by Lenovo, but the problem still exists.
By the way, after I encountered this problem, when I turn on the laptop, there is no more screen showing the ThinkVantage and the Intel logo. There is also no screen for "Starting Windows". It will straight away enter windows logon screen. It means, I have no way to enter BIOS or the recovery tools by pressing the ThinkVantage button at startup. (I cannot see anything!)
Anyone can please help me?
Thanks!

ahboy0207, welcome to the forum,
you need to install the monitot inf file from here. Scroll down the page for installation instructions.
As you have installed another OS on your system you will have changed the Master Boot Record, (MBR), which contains the information allowing the ThinkVantage button to work at boot. If you left the recovery partition intact, i.e. didn't format it, it may be possible to repair the MBR in order that you can access it. However, the recovery partition will have the original XP image on it and not your W7.
You can enter BIOS by pressing F1 at boot.
Hope this helps
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

3000/N100 Mouse/Screen Resolution Problems with Windows 7

This is my first post and I appreciate your service. My problem is that after I upgraded from Vista to Windows 7, I find that my touchpad mouse will freeze up & the screen resolution will changes occasionally when I boot up my computer. When this happens, I have to restart my computer and hope that the mouse works and screen resolution is correct. If it does work, it will continue to work until I turn off or restart the computer, then I cross my fingers again. All my drivers are updated. If the touchpad mouse is frozen, I can get my usb mouse to work, but I don't want to have to do that. Has anyone else had this problem, or can anyone offer suggestions?
I never had this problem until I upgraded to Windows 7.
Thanks in advance,
Mike

I am using the Win 7 Enterprise 32 bit trial version.
It is the FULL version, NOT an upgrade.
If you used Upgrade, that may be a clue?
Synaptics touchpad Ver 6.2 (From Synaptics)
File: v14_0_3_C_XP32_Vista32_Win732...
Graphics: Intel VER. 8.15.10.1930
From Windows update.
You did not post your model number, so you may have Alps and Nvidia, who knows?

Screen resolution problem after i-tunes installed on XP pro

Just purchased 5th Generation 60Gb for my daughters 16th Birthday which starts in about 14 minutes! Loaded the software on her XPpro service pack 2 laptop. When itunes executed the screen resolution drops to 8 bit! It can be changed in control panel and all works fine. but each time re boot itunes and the problem returns!
Loaded on my desktop and everything fine also. tried the ms config stuff as per site and immediate problem when ms software disabled. Would seem to be a software conflict and compatability problem. The laptop is a fujitsu which is 2 years old. the older version of i-tunes which she downloaded about a year ago worked ok. Sadly we uninstalled it before installing the new version from the disc. Tried update from the site but it indicates the DC version is the latest.
Interesting to read some of the problems that flks have had with the ipods. This one seems OK but does have a 'do not disconnect logo which hangs up and doesn't go away. However, if I do disconnect the computer 'burps' at me then all is well and forgotten!
Oh yes. how do you delete unwanted songs once uploaded? Is there a simple 'delete' button?
Any thoughts anyone as I've now spent all evening on it and it's her birthday in the morning (8th June)
thanks in anticipation
Gwynne (minolta man)

sorted problem by changing computer! probably softward hardware conflict with iTunes

|Solved| - Screen resolution and nVidia

I installed arch, xorg, nvidia's drives, openbox and gnome.
I can run gnome and openbox without any problem, however, my screen resolution isn't recognised. Here's my /etc/X11/xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder58) Thu Jun 5 00:08:24 PDT 2008
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# Files section. This allows default font and rgb paths to be set
# Server flags section.
# Input devices
# Core keyboard's InputDevice section
# Core Pointer's InputDevice section
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
# Device configured by xorgconfig:
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
# Section "DRI"
# Mode 0666
# EndSection
Section "ServerLayout"
# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
Identifier "Simple Layout"
Screen "Screen 1" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# RgbPath "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# FontPath "/usr/share/fonts/TTF"
# FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
EndSection
Section "Module"
# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# Load "type1"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
# Load "xtt"
Load "glx"
EndSection
Section "InputDevice"
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbRules" "xorg"
Option "XkbModel" "logicd"
Option "XkbLayout" "pt"
Option "XkbVariant" "pt"
EndSection
Section "InputDevice"
# Identifier and driver
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mice"
# Mouse-speed setting for PS/2 mouse.
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection
Section "Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
Identifier "My Monitor"
HorizSync 80.0 - 80.0
VertRefresh 75.0
EndSection
Section "Device"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
Identifier "Standard VGA"
Driver "nvidia"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
# unsupported card
#VideoRam 319488
# Insert Clocks lines here if appropriate
Identifier "My Video Card"
Driver "nvidia"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "My Video Card"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1440x900"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1440x900"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1440x900"
EndSubSection
EndSection
If I run "xorgconfig" and after that "nvidia-xconfig", my screen resolution is 1024x860, but after changed very mode to my native resolution ("1440x900"), is changes to "800x600".
Last edited by Nomearod (2008-07-23 09:19:07)

heleos wrote:
Widescreen resolutions are not possible with newest vista and linux drivers if the tft is connected with dvi.
Use an older driver or the vga-port instead.
There are maybe some hacks, but I tried many times in vista and linux. And it's always the same, only 1280x1024.
did some googling:
http://forums.nvidia.com/lofiversion/in … 20005.html
Thanks for the reply, but I don't believe that's the problem since that topic is from 2006 and I didn't had any problems last time I instaled arch (3 months ago).

Screen resolution problem - HP computer and LED Cinema Display

I just purchased an HP Envy Phoenix H9-1330 with Windows 8, and I connected it to my 27" Mac LED Cinema Display, but the resolution is horrible. The highest option in the screen resolution menu is 1280 x 720, and I'm getting the error message "Your resolution is lower than 1024 x 768. Some items might not fit and apps might not open". How do I fix this? What kind of issue is this (Windows 8? Graphics card? HP can't support my monitor? etc...)?
I just bought another brand new computer, but not an HP, with Windows 8 and I have no problems with the resolution - it looks absolutely beautiful. I want to use my monitor with my HP desktop though.
Thanks for any help

Still haven't figured it out....
BUT I did notice that, on the back of the computer, there are 2 additional DVI connections that are covered with a black cover and screwed in (and they say 'please do not remove'.... I'm asuming it's because they aren't connected to anything? Or maybe they aren't connected to the graphics card?). Is it possible that just my DVI connection is wrong, and I'll need to connect to one of these covered-up DVI inputs instead? But why are they covered up? Do I need to take it in so they can be connected to the graphics card?? Help! I don't want to return this computer, but I will have to if I can't get the resolution fixed.

[Solved] Screen resolution problem in a qemu guest

Similar Messages

Maybe you are looking for