Resolution of Screen

Is there a way to change the resolution of the screen in the program, to run in every computer??
Thank's

client-server, web? It is impossible to respond to posts when you do not specify what version of forms you are using.

Similar Messages

  • N-Series NEEDS a high-resolution touch-screen!

    Dear Nokis,
    If you only do one good thing in 2008 please let it be an N-Series S60v3 phone with the following specifications:
    *Larger, higher resolution touch-screen.
    *Alloy casing, not all plastic.
    *5MP camera with Xenon flash.
    *640*480 30fps video recording.
    *Integrated GPS.
    Hell, basically all I want is a phone which has all the features of the N82 but with the larger, higher resolution touch-screen. I use my N82 for internet when I am out of the office and even with Opera Mini browsing is a complete pain in the **bleep**. A touchscreen would help with browsing so much it would completely change the way we use the phones, and a higher resolution would make it so much more practical.
    If you need to make the phone bigger then so be it, just PLEASE give us a higher res touchscreen!
    *begs*

    16-Jan-2008 11:21 AM
    psychomania wrote:
    A nokia touch screen is in development and we should see one this year.
    No specs or firm info is available to the public yet.
    Keep your eyes on popular phone news sites for the latest info.
    I do keep my eyes on the news sites and saw that one had been demo'd, its just I fear that the models that will eventually be released wont be as fully featured as I specified in my original post!

  • GeForce FX 5600 - LAST NVIDIA driver Resolution of screen

    Hi all,
    I have recently bought BattleField Vietnam and this game requiers the last NVIDIA Driver. I have downloaded them here : http://www.nvidia.com
    The game is OK but i have problems with my Resolution of screen... I can't  choose a resolution between 1024*768 and 1280*1024... It is either one or the other but not between  
    MSI doesn't proposes the last nvidia driver  
    PLEASE HELP ME.

    How can that be I just checked my game And I have 1152x864 in the list. Are you sure that your monitor supports that resilution?
    One thing you may try is Go and find a file called VideoDefault.con in your /mods/BfVietnam/settings Directory under Battlefield Vietnam open it with notepad and change this line renderer.allowAllRefreshRates 0 from 0 to 1 and save and close. This will now allow all refresh rates in the game.
    The game came with the 56.56 drivers not the 56.64 drivers

  • Macbook air mini dp output resolution / full screen app issues

    I've successfully connected my new macbook air 13" to my LED tv with a mini DP to hdmi adapter + hdmi wire. I am able to get video and audio (obviously.)
    My issue is that no matter when resolution I try (1080p, 1080i, 720p, etc) and wether I am "mirroring" the display or "extending" the display,
    My samsung 46" LED tv can not get full screen there is always black bars on the left and right.
    When I connect my PC via VGA wire  there are no bars and it is in full land scape view.
    Also I've noticed in lion that full screen apps show up as the "linen wallpaper" on the second display.
    the only way i can slightly alleviate the problem is full screening a video within youtube but not within the OS it self... even then there is still black bars which is weird because when i use the TV as a extended monitor the wallpaper is using the whole display just full screen video has black bars.
    I am unable to get 1920 x 1200 output display to my HDTV is this possible? is it my mini DP to hdmi adapter that is at fault?
    thanks in advanced to whoever helps sorry about the long post my brain is scattered on the issue because my VGA connetion works fine i don't understand why HDMI + mini DP has worse resolution...

    No, it doesn't list the resolution explicitly like that - the top few items in the list are "480i", "480p", "720p", "1080i" and "1080p", each with a small TV icon to the right. Non-television resolutions follow, and are listed with explicit pixel dimensions (and no TV icon), but the list stops at 1440x900, the native resolution of the MacBook's built-in display; it doesn't list resolutions higher than that.
    Needless to say, I've tried every setting in the entire list, and they all suffer from the same problem of displaying shrunk down on the plasma TV with a margin around the desktop.
    I wonder if the difference between your Display control panel and mine is that I'm running Snow Leopard? (Sorry - no screen grabs to show, I'm at work right now)

  • After 1366x768 resolution - Black screen

    Hi,
    I have a Mac mini (Early 2006) DualCore with a Sony Bravia KDL-40V2000. I have connected both electronic devices with a Belkin cable (HDMI to DVI-D)
    I have some problems to choose the screen resolution. The best TV Sony Bravia resolution is 1366x768, but the Mac Mini resolution more near is 1280x720.
    I have configured through DisplayConfigX 1366x768 resolution and then I have to reboot Mac mini.
    But after the Mac mini reboot, I can't see anything on Sony Bravia Display. All the screen is black.
    Only workaround that I have tested is connect a VGA display and try to change the display configuration, but Sony Bravia display configuration doesn't appear. Only VGA display connected is available to change config.
    How can I do to resolve this big deal? Thank you very much!!
    How can I do to configure the best resolution as possible to enjoy that?
    Thanks in advance!!!

    When I started setting up my Intel Mini with my TV, I also had trouble getting it to work at 1366x768. I tried DisplayConfigX, but found it too technical. I was able to get SwitchResX to work. I don't have the same TV as you, nor am I using HDMI (mine is DVI), but perhaps you could try SwitchResX to get you working.
    From a previous post, here is what I did:
    I created a custom resolution. On the settings for that, I chose "Custom" (rather than scaled), I clicked on the "Use simplified settings: GTF". I used 1366 (horizontal) and 768 (vertical) for the "Active" setting, and 60 Hz for the Vertical Scan rate. All the rest of the fields adjusted themselves.
    As also stipulated before, I don't really know what most of these settings mean, just that they work.

  • Resolution Stretched/Screen Viewing Problem

    I was just cleaning my imac 27" and cleaned the keyboard while its on (silly i know ) and my screen size seems to have stretched. My resolution is at the maximum 2560 x 1440 but i have to move the mouse cursor up and the screen moves so i can see the file/edit/view bars at the top. Then to get back to the dock at the bottom the screen slides down (same left and right as well). How do i get my resolution back to automatically fit the screen. Its really annoying me now
    Thanks
    Max

    Den.thed has probably nailed it, but another possibility is that the Zoom function became enabled via a keyboard combo. To check for the, open the Unversal Access pane in System Preferences; select the Seeing item in the top area. If Zoom is active, and you do not want that feature, turn it off. If this is the cause, the screen will immediately fix itself.

  • How do I change picture resolution from screen capture?

    If I want to take the image on the screen in Encore CS5 and save it as a photoshop picture the resolution is 70 DPI.  Is there any way to change this resolution?  I would like sharper pictures if possible, 100 DPI to 200 DPI if this can be done.
    Encore CS5
    Core 4 2.4 ghz processor
    6 GB Ram
    700 GB free on hard drive
    Windows 7 64 bit

    I completely agree with your goal - getting as a good a resolution print as possible.  But your focus on dpi for the capture of a frame will not help you.
    Kind of like scanning an image.  If you are going to blow it up later you want to scan at higher resolutions than if you don't.  There is of course image quality versus file size issues, etc. etc. but at least I would have the option to change resolutions on capture.
    Scanning at a higher resolution adds more pixels.  So, for example, scanning a finely detailed 7.2 x 4.8 inch image at 300 dpi produces 2160 x 1440 pixels.  Scan a grainy photograph similarly, and it will be 2160 x 1440 and look lousy.  Use a 5 megapixel camera to shoot the original scene, you've got more pixels.  If you have only the SD video image, all you have is the 720 x 480 pixel image.  It doesn't matter how you set the dpi on capture, just that you capture all 720 x 480 pixels.
    In Premier Pro CS5 and Encore CS5 the image size is 10 inches by 6.667 inches and the resolution is 72 pixels/inch.
    Pulling from womble the image size is 7.2 inches by 4.8 inches and the resolution is 100 pixels/inch.
    The part you are not listing is the fact that for each of those the pixel size is 720x480.  As long as you capture the 720 x 480, the resolution of the image is not improved by flagging it as 72 dpi or 100 dpi.  You can change that in photoshop for either of those captures, and you get a different print size, but no more or less pixels.
    In either case, re-sizing the image in photoshop doesn't change the pixels/inch resolution.  I want to capture the original image in as good resolution as possible rather than having to correct it after capture.
    "As good resolution as possible" is 720 x 480.

  • Images the same resolution as screen get scaled

    Images that have the same resolution as the screen on either plane are not fully pixel mapped when shown in full, but suffer a loss in sharpness along the center axis due to scaling. While not readily visible in most images, it is an undesirable and unnecessary artifact.
    Replication steps:
    1. Create an image the same resolution as the phone's screen, e.g. 1080x1920 pixels, and fill it with a 2x2 pixel checkerboard pattern (every other pixel white and every other pixel black). Save it as PNG, or as JPEG with minimum compression.
    2. Copy the image to the phone (e.g. the Pictures folder).
    3. View the image at full size using Album, oriented the same direction as the screen such that it should display pixel mapped.
    4. Observe the loss of sharpness that occurs as neighboring pixel values are blended in areas of the image.
    This problem was observed on an Xperia Z3 with Album version 6.6.A.0.6 and earlier.
    I'll try putting together some examples later and add them to this thread.

    iPod:
    4-inch (diagonal) widescreen display with Multi-Touch IPS technology
    Retina display
    1136-by-640-pixel resolution at 326 pixels per inch
    800:1 contrast ratio (typical)
    500 cd/m2 max brightness (typical)
    Fingerprint-resistant oleophobic coating
    iPhone:
    Retina display
    4-inch (diagonal) widescreen Multi-Touch display
    1136-by-640-pixel resolution at 326 ppi
    800:1 contrast ratio (typical)
    500 cd/m2 max brightness (typical)
    Fingerprint-resistant oleophobic coating on front
    Support for display of multiple languages and characters simultaneously

  • N95, low screen resolution /light screen problems

    Hi people!
    Can someone help, ive not done anything to my phone bar take it out from my pocket and notice the screen display had changed.
    The screen seems to be really light and pale all of a sudden, no change in brightness, but it just seems brighter.
    the resolution seems diminshed too-when i go on the net any pictures are in less detail as if the resolutions been lowered.
    ive tried turnin the phone off and removing the battery.when it starts up agtain the NOKIA symbol come on in its normal strong blue but while its booting the NOKIA turns to the lighter shade of blue and the display again just loads at a lighter version of what its normally like.
    HELP!

    You need to check it's not a hardware issue.
    One thing you can try is to reset the phone using the instructions you can find in this post :
    /discussions/board/message?board.id=smartphones&message.id=4007
    However please be aware that doing so will wipe ALL the data from your phone such as information in your calendar, contacts and so on.
    In order to save your data you can use the PC Suite application to save and restore the data from your phone - this software can be found here :
    http://www.nokia.com/pcsuite
    One thing to note is that as part of these diagnostics, you should NOT restore any backup or install any software on the phone as you could be putting the problem back onto the phone.
    If this doesn't work then it's likely you have a hardware fault and you should approach your local Nokia Service Centre to get your phone fixed.
    Hope this helps.
    Please let me know how you get on.
    Regards,
    Edward

  • GDM resolution/virtual screen too big

    Well, I got GDM to load on bootup, but whenever it loads, it has the resolution too high and I get a virtual screen :shock: , it's starting to get on my nerves scrolling around the screen. I want the resolution to 1024x768 but it's way too high(hmm, my graphics card supports it though, damn x.org). Can anyone tell me how to do this?
    NOTE: I already tried gdm.conf

    Try the X config - in xfree86 it's XF86Config in /etc/X11 but I don't remember its name in x.org - the format is the same though. You should have a screen config section inside - something like this:
    Section "Screen"
    Identifier "MonitorPhilips"
    Device "NvidiaGeForce4MX440"
    Monitor "Philips109MP"
    DefaultDepth 24
    Subsection "Display"
    Depth 8
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
    Depth 16
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
    Depth 24
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    EndSubsection
    EndSection
    You can remove 1280x1024 and you should have 1024x768 (of course names at the begining of the section must be as in your config :-) just change the display subsections).
    EDIT: it should probably be xorg.conf

  • Resetting my resolution, MY SCREEN WENT BLANK!

    I was checking to see what was the highest resolution i can set my monitor to and it would seem to work. when i got to one setting, the screen went blank and the montor it self said something about being out of range. the screen now stays blank and cant get it to come back on to change the setting to something i can see anymore. I have restarted the computer and can see the loading screen but just bfore it goes to the desktop, the screen cuts off again. is there some kind of "safe mode" or way i can get things to work again? right now i cant use the computer at all being i cant see anything
    help!!!

    Hi G F2:
    There is a safe-boot mode: hold down the shift-key during startup; this may actually take longer than a normal boot, so don't worry.
    If that doesn't work, you could try resetting your PRAM: hold the commandoption+pr keys during boot, and wait for three chimes (to be safe). Then let go and let it boot. This should restore to the default screen resolution.
    By the way, I've done the same thing, and sometimes the only way to get it back is to connect a different monitor that has a higher resolution than what you're testing. Sometimes, using the up-arrow key will change the resolution back to a previous (lower) selection.
    Good luck!
    Andrew

  • Bigger resolution then screen

    Sometimes when I log in, the resolution too big. If i go to System > settings > monitor, the screen flashing, and set the good (1280*800) size.
    Before tfis metfot, my desktop looks like this:
    in my xorg.conf:
    Section "Screen"
            Identifier      "Screen0"
            Device  "Card0"
            Monitor "Monitor0"
            DefaultColorDepth 24
            SubSection "Display"
                    Depth   24
                    Modes "1280x800"
            EndSubSection
    EndSection
    But i tried to delete it, not sovlad. I tried the old gdm, isnt solved (an othet problem with the new gdm, sometimes it isnt appear. When i change to tty1 and back, it apperas)
    can someone help me?
    thx
    Last edited by barii (2010-05-08 16:44:46)

    without xorg.conf:
    [quote=n0dix]Post your Xorg.0.log.[/quote]
    X.Org X Server 1.7.6
    Release Date: 2010-03-17
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.33-ARCH i686
    Current Operating System: Linux arch-notebook 2.6.33-ARCH #1 SMP PREEMPT Mon Apr 26 20:00:20 CEST 2010 i686
    Kernel command line: root=/dev/sda8 ro noapic
    Build Date: 01 April 2010 05:35:33PM
    Current version of pixman: 0.18.0
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sat May 8 18:29:18 2010
    (II) Loader magic: 0x81e4c60
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 6.0
    X.Org XInput driver : 7.0
    X.Org Server Extension : 2.0
    (++) using VT number 8
    (--) PCI:*(0:0:2:0) 8086:2a42:1028:0263 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller rev 7, Mem @ 0xf6c00000/4194304, 0xe0000000/268435456, I/O @ 0x0000efe8/8
    (--) PCI: (0:0:2:1) 8086:2a43:1028:0263 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller rev 7, Mem @ 0xf6b00000/1048576
    (==) Using default built-in configuration (30 lines)
    (==) --- Start of built-in configuration ---
    Section "Device"
    Identifier "Builtin Default intel Device 0"
    Driver "intel"
    EndSection
    Section "Screen"
    Identifier "Builtin Default intel Screen 0"
    Device "Builtin Default intel Device 0"
    EndSection
    Section "Device"
    Identifier "Builtin Default vesa Device 0"
    Driver "vesa"
    EndSection
    Section "Screen"
    Identifier "Builtin Default vesa Screen 0"
    Device "Builtin Default vesa Device 0"
    EndSection
    Section "Device"
    Identifier "Builtin Default fbdev Device 0"
    Driver "fbdev"
    EndSection
    Section "Screen"
    Identifier "Builtin Default fbdev Screen 0"
    Device "Builtin Default fbdev Device 0"
    EndSection
    Section "ServerLayout"
    Identifier "Builtin Default Layout"
    Screen "Builtin Default intel Screen 0"
    Screen "Builtin Default vesa Screen 0"
    Screen "Builtin Default fbdev Screen 0"
    EndSection
    (==) --- End of built-in configuration ---
    (==) ServerLayout "Builtin Default Layout"
    (**) |-->Screen "Builtin Default intel Screen 0" (0)
    (**) | |-->Monitor "<default monitor>"
    (**) | |-->Device "Builtin Default intel Device 0"
    (==) No monitor specified for screen "Builtin Default intel Screen 0".
    Using a default monitor configuration.
    (**) |-->Screen "Builtin Default vesa Screen 0" (1)
    (**) | |-->Monitor "<default monitor>"
    (**) | |-->Device "Builtin Default vesa Device 0"
    (==) No monitor specified for screen "Builtin Default vesa Screen 0".
    Using a default monitor configuration.
    (**) |-->Screen "Builtin Default fbdev Screen 0" (2)
    (**) | |-->Monitor "<default monitor>"
    (**) | |-->Device "Builtin Default fbdev Device 0"
    (==) No monitor specified for screen "Builtin Default fbdev Screen 0".
    Using a default monitor configuration.
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (==) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (II) Cannot locate a core pointer device.
    (II) Cannot locate a core keyboard device.
    (II) The server relies on HAL to provide the list of input devices.
    If no devices become available, reconfigure HAL or disable AutoAddDevices.
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.7.6, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.7.6, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    (II) Module glx: vendor="X.Org Foundation"
    compiled for 1.7.6, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
    (==) AIGLX enabled
    (II) Loading extension GLX
    (II) LoadModule: "record"
    (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    (II) Module record: vendor="X.Org Foundation"
    compiled for 1.7.6, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension RECORD
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 1.7.6, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "dri2"
    (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    (II) Module dri2: vendor="X.Org Foundation"
    compiled for 1.7.6, module version = 1.1.0
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension DRI2
    (II) LoadModule: "intel"
    (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    (II) Module intel: vendor="X.Org Foundation"
    compiled for 1.7.4.901, module version = 2.10.0
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 6.0
    (II) LoadModule: "vesa"
    (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    (II) Module vesa: vendor="X.Org Foundation"
    compiled for 1.7.5, module version = 2.3.0
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 6.0
    (II) LoadModule: "fbdev"
    (WW) Warning, couldn't open module fbdev
    (II) UnloadModule: "fbdev"
    (EE) Failed to load module "fbdev" (module does not exist, 0)
    (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, Clarkdale, Arrandale
    (II) VESA: driver for VESA chipsets: vesa
    (II) Primary Device is: PCI 00@00:02:0
    (WW) Falling back to old probe method for vesa
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 8, (OK)
    drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 8, (OK)
    drmOpenByBusid: drmOpenMinor returns 8
    drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    (II) intel(0): Creating default Display subsection in Screen section
    "Builtin Default intel Screen 0" for depth/fbbpp 24/32
    (==) intel(0): Depth 24, (--) framebuffer bpp 32
    (==) intel(0): RGB weight 888
    (==) intel(0): Default visual is TrueColor
    (II) intel(0): Integrated Graphics Chipset: Intel(R) GM45
    (--) intel(0): Chipset: "GM45"
    (==) intel(0): video overlay key set to 0x101fe
    (II) intel(0): Output VGA1 has no monitor section
    (II) intel(0): Output LVDS1 has no monitor section
    (II) intel(0): found backlight control interface /sys/class/backlight/acpi_video0
    (II) intel(0): Output HDMI1 has no monitor section
    (II) intel(0): Output DP1 has no monitor section
    (II) intel(0): Output HDMI2 has no monitor section
    (II) intel(0): Output DP2 has no monitor section
    (II) intel(0): Output DP3 has no monitor section
    (II) intel(0): Output TV1 has no monitor section
    (II) intel(0): Output VGA1 disconnected
    (II) intel(0): Output LVDS1 connected
    (II) intel(0): Output HDMI1 disconnected
    (II) intel(0): Output DP1 disconnected
    (II) intel(0): Output HDMI2 disconnected
    (II) intel(0): Output DP2 disconnected
    (II) intel(0): Output DP3 disconnected
    (II) intel(0): Output TV1 disconnected
    (II) intel(0): Using exact sizes for initial modes
    (II) intel(0): Output LVDS1 using initial mode 1280x800
    (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    (==) intel(0): DPI set to (96, 96)
    (II) Loading sub module "fb"
    (II) LoadModule: "fb"
    (II) Loading /usr/lib/xorg/modules/libfb.so
    (II) Module fb: vendor="X.Org Foundation"
    compiled for 1.7.6, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
    (II) UnloadModule: "vesa"
    (II) Unloading /usr/lib/xorg/modules/drivers/vesa_drv.so
    (==) Depth 24 pixmap format is 32 bpp
    (II) intel(0): [DRI2] Setup complete
    (**) intel(0): Tiling enabled
    (**) intel(0): SwapBuffers wait enabled
    (==) intel(0): VideoRam: 262144 KB
    (II) intel(0): Attempting memory allocation with tiled buffers.
    (II) intel(0): Tiled allocation successful.
    (II) UXA(0): Driver registered support for the following operations:
    (II) solid
    (II) copy
    (II) composite (RENDER acceleration)
    (II) put_image
    (==) intel(0): Backing store disabled
    (==) intel(0): Silken mouse enabled
    (II) intel(0): Initializing HW Cursor
    (II) intel(0): No memory allocations
    (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    (==) intel(0): DPMS enabled
    (==) intel(0): Intel XvMC decoder enabled
    (II) intel(0): Set up textured video
    (II) intel(0): [XvMC] xvmc_vld driver initialized.
    (II) intel(0): direct rendering: DRI2 Enabled
    (--) RandR disabled
    (II) Initializing built-in extension Generic Event Extension
    (II) Initializing built-in extension SHAPE
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension BIG-REQUESTS
    (II) Initializing built-in extension SYNC
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-MISC
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    (II) AIGLX: enabled GLX_SGI_make_current_read
    (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    (II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i965_dri.so
    (II) GLX: Initialized DRI2 GL provider for screen 0
    (II) intel(0): Setting screen physical size to 338 x 211
    (II) config/hal: Adding input device AT Translated Set 2 keyboard
    (II) LoadModule: "evdev"
    (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    (II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.7.3, module version = 2.3.2
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 7.0
    (**) AT Translated Set 2 keyboard: always reports core events
    (**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
    (II) AT Translated Set 2 keyboard: Found keys
    (II) AT Translated Set 2 keyboard: Configuring as keyboard
    (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us"
    (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    (II) config/hal: Adding input device Dell WMI hotkeys
    (**) Dell WMI hotkeys: always reports core events
    (**) Dell WMI hotkeys: Device: "/dev/input/event17"
    (II) Dell WMI hotkeys: Found keys
    (II) Dell WMI hotkeys: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us"
    (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    (II) config/hal: Adding input device Macintosh mouse button emulation
    (**) Macintosh mouse button emulation: always reports core events
    (**) Macintosh mouse button emulation: Device: "/dev/input/event0"
    (II) Macintosh mouse button emulation: Found 3 mouse buttons
    (II) Macintosh mouse button emulation: Found relative axes
    (II) Macintosh mouse button emulation: Found x and y relative axes
    (II) Macintosh mouse button emulation: Configuring as mouse
    (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
    (**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
    (**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
    (**) Macintosh mouse button emulation: (accel) acceleration profile 0
    (II) Macintosh mouse button emulation: initialized for relative axes.
    (II) config/hal: Adding input device AlpsPS/2 ALPS DualPoint TouchPad
    (II) LoadModule: "synaptics"
    (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    (II) Module synaptics: vendor="X.Org Foundation"
    compiled for 1.7.3, module version = 1.2.1
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 7.0
    (II) Synaptics touchpad driver version 1.2.1
    (**) Option "Device" "/dev/input/event16"
    (II) AlpsPS/2 ALPS DualPoint TouchPad: x-axis range 0 - 1023
    (II) AlpsPS/2 ALPS DualPoint TouchPad: y-axis range 0 - 767
    (II) AlpsPS/2 ALPS DualPoint TouchPad: pressure range 0 - 127
    (II) AlpsPS/2 ALPS DualPoint TouchPad: finger width range 0 - 0
    (II) AlpsPS/2 ALPS DualPoint TouchPad: buttons: left right middle
    (**) Option "TapButton1" "1"
    (**) Option "TapButton2" "2"
    (**) Option "TapButton3" "3"
    (--) AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
    (**) AlpsPS/2 ALPS DualPoint TouchPad: always reports core events
    (II) XINPUT: Adding extended input device "AlpsPS/2 ALPS DualPoint TouchPad" (type: TOUCHPAD)
    (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) keeping acceleration scheme 1
    (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration profile 0
    (--) AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
    (II) config/hal: Adding input device DualPoint Stick
    (**) DualPoint Stick: always reports core events
    (**) DualPoint Stick: Device: "/dev/input/event15"
    (II) DualPoint Stick: Found 3 mouse buttons
    (II) DualPoint Stick: Found relative axes
    (II) DualPoint Stick: Found x and y relative axes
    (II) DualPoint Stick: Configuring as mouse
    (**) DualPoint Stick: YAxisMapping: buttons 4 and 5
    (**) DualPoint Stick: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "DualPoint Stick" (type: MOUSE)
    (**) DualPoint Stick: (accel) keeping acceleration scheme 1
    (**) DualPoint Stick: (accel) acceleration profile 0
    (II) DualPoint Stick: initialized for relative axes.
    (II) config/hal: Adding input device HID 413c:8158
    (**) HID 413c:8158: always reports core events
    (**) HID 413c:8158: Device: "/dev/input/event10"
    (II) HID 413c:8158: Found 3 mouse buttons
    (II) HID 413c:8158: Found relative axes
    (II) HID 413c:8158: Found x and y relative axes
    (II) HID 413c:8158: Configuring as mouse
    (**) HID 413c:8158: YAxisMapping: buttons 4 and 5
    (**) HID 413c:8158: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "HID 413c:8158" (type: MOUSE)
    (**) HID 413c:8158: (accel) keeping acceleration scheme 1
    (**) HID 413c:8158: (accel) acceleration profile 0
    (II) HID 413c:8158: initialized for relative axes.
    (II) config/hal: Adding input device HID 413c:8157
    (**) HID 413c:8157: always reports core events
    (**) HID 413c:8157: Device: "/dev/input/event9"
    (II) HID 413c:8157: Found keys
    (II) HID 413c:8157: Configuring as keyboard
    (II) XINPUT: Adding extended input device "HID 413c:8157" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us"
    (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    (II) config/hal: Adding input device Logitech USB Receiver
    (**) Logitech USB Receiver: always reports core events
    (**) Logitech USB Receiver: Device: "/dev/input/event8"
    (II) Logitech USB Receiver: Found 1 mouse buttons
    (II) Logitech USB Receiver: Found scroll wheel(s)
    (II) Logitech USB Receiver: Found relative axes
    (II) Logitech USB Receiver: Found absolute axes
    (II) Logitech USB Receiver: Found keys
    (II) Logitech USB Receiver: Configuring as mouse
    (II) Logitech USB Receiver: Configuring as keyboard
    (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
    (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us"
    (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    (EE) Logitech USB Receiver: failed to initialize for relative axes.
    (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
    (**) Logitech USB Receiver: (accel) acceleration profile 0
    (II) Logitech USB Receiver: initialized for absolute axes.
    (II) config/hal: Adding input device Logitech USB Receiver
    (**) Logitech USB Receiver: always reports core events
    (**) Logitech USB Receiver: Device: "/dev/input/event7"
    (II) Logitech USB Receiver: Found 20 mouse buttons
    (II) Logitech USB Receiver: Found scroll wheel(s)
    (II) Logitech USB Receiver: Found relative axes
    (II) Logitech USB Receiver: Found x and y relative axes
    (II) Logitech USB Receiver: Configuring as mouse
    (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
    (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE)
    (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
    (**) Logitech USB Receiver: (accel) acceleration profile 0
    (II) Logitech USB Receiver: initialized for relative axes.
    (II) config/hal: Adding input device Sleep Button
    (**) Sleep Button: always reports core events
    (**) Sleep Button: Device: "/dev/input/event4"
    (II) Sleep Button: Found keys
    (II) Sleep Button: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us"
    (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    (II) config/hal: Adding input device Power Button
    (**) Power Button: always reports core events
    (**) Power Button: Device: "/dev/input/event3"
    (II) Power Button: Found keys
    (II) Power Button: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us"
    (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    (II) config/hal: Adding input device Video Bus
    (**) Video Bus: always reports core events
    (**) Video Bus: Device: "/dev/input/event5"
    (II) Video Bus: Found keys
    (II) Video Bus: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us"
    (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): Allocate new frame buffer 2128x800 stride 2176
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): Allocate new frame buffer 1280x800 stride 1280
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): Allocate new frame buffer 2128x800 stride 2176
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): Allocate new frame buffer 1280x800 stride 1280
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): Allocate new frame buffer 2128x800 stride 2176
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    (II) intel(0): Allocate new frame buffer 1280x800 stride 1280
    (II) intel(0): EDID vendor "SEC", prod id 21569
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1280x800"x0.0 74.76 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (50.0 kHz)
    (II) intel(0): Modeline "1280x800"x0.0 49.84 1280 1296 1344 1494 800 801 804 834 +hsync -vsync (33.4 kHz)
    Last edited by barii (2010-05-08 23:42:57)

  • I am having trouble with my resolution, my screen is to small and my fonts are to big

    I have an Dell E172 FP (OLD) but I can use it very well. Today I put in a CD Of games and after that my desk top dose not want to take the normal setting I had. Can u help? I can't even use Facebook because it sends a message that its too small.

    Did you check the screen settings in the Windows Control Panel?
    *Control Panel > Display
    If it only happens in Firefox then check that you do not run Firefox in compatibility mode or with a reduced screen resolution.
    You can open the Properties of the Firefox desktop shortcut via the right-click context menu and check the "Compatibility" tab.
    Make sure that all items are deselected in the "Compatibility" tab of the Properties window.

  • Can Apple provide manually setting resolution of Screen

    My LCD TV can support up to 1280*720 (16:9)
    but the result of auto-negotiate from OSX only support 1024*768 (4:3)
    Can I manually setting the resolution for my LCD TV ?

    Did you try clicking [Detect Displays] in the displays preferences?

  • How to know the current resolution of screen?

    Help me please

    Actually, that's misleading. It's Toolkit.getDefaultToolkit().getScreenSize(). That gets the X x Y pixel count of the screen. Toolkit.getDefaultToolkit().getScreenResolution() gives the DPI of a screen (supposedly).

Maybe you are looking for

  • Projects and Albums out of order

    It used to be Projects and Albums would line up in alphabetical order when created in Aperture Libraries. It hasbn't been happening for me in recent updates, and I can't find a way to set this in preferences. Even worse, some times albums won't let m

  • Publish To Portal Error

    Hi All, I have a problem Publishing web templates or reports from Report Designer from BI to portal. Portal has been configured.Has both ABAP+JAVA stack.I use BI7. When I do Pubilsh - >To portal in web templates or report designer (I have tried only

  • Question about XSL

    Hi suppose i have a XML file as below, i want to print only value where id = name. I want to do this using XSL, not java program for example once i read throug all the XML file, i should get output as 123 and 456 <xml> <name>abc</name> <name>xyz</nam

  • Epson cx4200

    I have an ibook G4 and am trying to run an epson cx 4200. When purchased it worked but had some missing file from printer download. contacted epson got that resolved but now the laptop doesnt recognize the printer and it wont let me add it at all. Th

  • Add Iso image in the Pxe sever of WDS

    Hello sorry for my bad english. Is there any solution to add an iso image (boot cd like "utltimate boot cd")  in the PXE menu of WDS ? Thanks a lot