Cs4PSD InDesign Epson SP1400/PM-G4500 Benq G2400w Colorsync Huey

Situation: printing a 30pg book from indesign onto my Epson printer.
Problem: colors are do not match screen, while printing from Ps and Id
Possible reasons:
1. non-postscript printer
2. monitor uncalibrated
3. settings in colorsync
4. settings in psd
5. huey is not insufficient as a monitor calibrator. need another color management hardware: screen-to-papaer matching, thingy???
6. maybe i need to create new profiles: monitor profile, paper profile
What i know/ What I have been told/ What I've already performed:
printing from epson desktop printer:
1. keep images at RGB
2. save as eps8bit-but this is for outsourcing to a printer company
3. if all else fails, when colors don't match, print in illustrator or acrobat
4. printer head and alignment has been performed numerous times
5. ink has been changed every 2 -weeks
6. settings in psd:
Adobe RGB (1998)
U.S. Web Coated (SWOP) v2
7. test printed on epson super fine paper in CS4 PSD
"document: Epson sRGB" also "document: Adobe RGB (1998)"
"photoshop determine color"
"SP 1400 1410 PQIJ"
Results:  prints still look bad
What i don't know:
1. i'm guessing this printer isn't post-script, does it need to be in order to match what i see on screen and on paper
2. how to create new profiles, do i need to???
3. CS4 still unstable with epson 1400/ pm-g4500
4. huey: after calibration in a dark room, creates a monitor profile that has more red tint. is this right?
Hardware:
Japan Epson PM-G4500 (U.S. epson Stylus Photo 1400)
using the epson driver: 12571.dmg -(u.s. driver, i can't read the japanese version), so im using their paper profiles are shown in PSD
Benq G2400w
5 default settings: using the sRGB setting: un-edited
Huey Monitor Calibrator
??? 1.0.4 software update, sometimes appears on the desktop menu bar, sometimes not. somewhere it is said i might need to extract files and place into preferences, don't know details, so can't perform this task
OSx: 10.5.6
SystemPreferences/Displays/Color/DisplayProfile/ D65 G1.8 A??? turned off Huey and Calibrated by eye
then applied Huey. it came out to d65 G2.2 A0.00. cannot be edited---Huey GAVE MY MONITOR A MORE RED Tint
CS4 Psd 11.0.1
CS4 Indesign 6.0.1
Colorsync:checking a total of 82 profiles    13 bad files??? don't know if this is relevant to the problem
when opening file:
Embedded: Epson sRGB, so I Discard and use Adobe RGB (1998)
saved as tiff, jpeg, psd
PSD settings:
RGB: Adobe (1998)
CMYK: U.S. SWOP
Color Management:
Document (Profile: Adobe RGB (1998)
Photoshop Manages Colors
Printer Profile: SP14001410 PQJI ("super fine paper")
people have mentioned to turn of colorsync to improve color matching. cannot turn of colorsync in psd. it is grayed out and is autmatically selected.
so, i opened the  "preview" software:
file/print/colormatching/ the option to choose color sync or epson is there. but i have to select one.
Suggestions, anyone
1. Do i need a rips software: ex. Colorbyte's product, "Imageprint" my epson is only a sp 1400/pm g-4500, so is this necessary?
2. Get a different monitor?
3. Buy a different monitor calibrator?
4. Do i need to trash/replace anything in the preferences?
i know i have a monitor calibration problem, but i also have a printer problem. What should I do? I've seen test screens available on the internet, but I don't want to make corrections just by eyesight. Is this my only option left?

Rich....answers below you questions.
--agree, i think the monitor [i have] is for purely gaming. big mistake on my part. i will try to pick-up a huey pro. if i recall correctly, huey pro allows you to edit the profiles. i could be wrong. are there any monitors you suggest, IPS??? i think that's what they're called? i just found a name-drop on the apple web store;p --"eizo"
If you are serious about color matching, start with a monitor profiling package.  Your monitor may be more than good enough, so save the money.  You'll need a monitor profiling package anyway, so start there.  Then, if that doesn't cut it, get a new monitor.  Unless you are doing high end work and have money to burn, you probably don't need an Eizo.  Nice, but expensive.
Second, you need an accurate printer profile for your printer/paper/ink combination, and you need to print with the correct settings and profiles.
-- to tell you the truth, for this project, i will be using non-epson paper. i will research these vendors for their paper profile, if available- Kokuyo. yes, its non-epson, but their are some cool papers out there that are "dying" to be used by someone.
Profiles provided by paper and/or ink manufacturers vary tremendously.  Even the good ones are only good for printers that closely adhere to the "standard" used to generate the profile.  If your printer happens to be coincide with the standard, great.  But, even then, some profiles are well made and others are not.  Try them and see how they work.  If they work great, fantastic, but you still need to compare your results to a properly calibrated and profiled monitor, otherwise, forget it.
...ambient lighting and viewing lights will also affect your perception of the viewed print, so they need to be controlled.
--I'm using 2 flourescent lights. one, close to the screen to the left and the other a ceiling type for the entire room.  i've tried huey both at night and during the day. checking the monitor,  colors, and prints, i preferably, do during the day.
You probably have bigger fish to fry, so save the lighting for later.  If you can, look at your prints using filtered daylight (e.g., soft, indirect light from a north facing window, with the sun in the south.  Don't hold the print next to a green or red wall, bright yellow curtains, etc).  Filtered daylight will give you fairly accurate representation of the colors in your print.  When ready for viewing lights, we can talk again.
...then you will need a postscript RIP, but that seems unnecessary, especially at this level.
--i'm trying to stay "low-brow" as long as possible. Is messing with the curves the best work around, so far. the work ahead of me looks daunting. ;p
Don't get a RIP, especially at this point.  Get the basics handled and it is highly unlikely you will need a RIP.
I don't have a Huey, but I have heard mixed reviews on them.
--are there any that you suggest?
i1 Display is a decent, cost effective package.  Check with www.Chromix.com and see what they suggest.  This package will ONLY profile monitors, not printers.  If you want to generate your own printer profiles, be prepared to spend a lot more money.
  other questions:
1. are you using color sync throughout your workflow? No...I am working on a PC, which doesn't have colorsync.
2. there were 19 damaged profiles out of 39 in my color sync. is it important i fix these? Not even sure what this means.  Check with a Mac person.
3. from what i understand so far, there are profiles for the following:
a. epson paper
b. monitor
c. photoshop/ and illus.
Am i missing the concept here?
If all the files in this book were created with an embedded EpsonRGB, theoretically I should print to epson with the printer profile set as: EpsonRGB. its one straight line, but i'm guessing this is one way. i have yet to test it. the other way of course, is to zero out all variables, use working profile when opening in psd and then print... that's what i've got to work out still.
I am guessing EpsonRGB is probably their captive name for sRGB, but I don't know.  You really need to understand the concepts before getting hung up on details.  Real World Color Management is the place to start.  Typically, you will be dealing with three types of profiles....Monitor profiles so your images display accurately, printer profiles (inkjet, press, etc) which will make sure your colors print accurately, and working space profiles (sRGB, Adobe RGB, ProPhoto RGB, etc).  They all tie together, using a device independent, mathematical model of human vision as the universal translator.  Get the book.
4. i presume printing the book as a pdf on acrobat is one "work-around" solution.
It depends what you mean by work-around.  Yes, you can output to PDF, but you still need to make sure you are not screwing up the color by improperly implementing color management.  The principles still apply.  You can hose the color in a PDF too if you don't handle it properly.
5. from what it sounds like creating a post-script is not necessary, so i'll focus more on the pdf printing in acrobat
If you are talking about sending a job to a printing press, I'd send InDesign or PDF files to your printer (or Illustrator for simple layouts).  The commercial printer will RIP the file and create plates for the press.  So, you don't have to create postscript yourself.  For simple inkjet prints, you normally don't need a postscript RIP.
6. come to think of it, i've had problems with printing on cs3, using the above mentioned monitor.
a. is this right? 1. calibrate the screen first.but how do i tell psd to tell the monitor that its too red: a.) color sync? b.) soft proofing
Again....Read Real World Color Management.  You need to understand the principles first.  Asking detailed questions without having a solid understanding of principles is the long, hard way.  A monitor profiling package will calibrate and profile your monitor, bringing it back to standard benchmark.  You want consistency and accuracy. 

Similar Messages

  • Macbook 2.2 & BenQ G2400w

    I've recently bought two BenQ G2400W (DVI-HDMI 1900 x 1200 )monitors for use with two different Macbooks 2.2 (Santa Rosa chipset & Leopard).
    The problem is this; Whilst I can get the monitors to work over the analogue connection it is impossible to get an image via the DVI or HDMI connectors.I have tried to use four different Mini DVI to DVI connectors as well as DVI cables. The Macbooks have no problem working via the DVI with some Formac displays I also have.
    Can anyone help? Thanking you in advance for your time.

    I have the same issue, "no signal detected" when using dvi or hdmi. The macbook (2,2 SR) detects g2400w properly only when it's connected to the monitor via dvi and the monitor is set to hdmi in, or vice versa. When I change to dvi in, macbook instantly drops the monitor, and "no signal detected" is displayed on the external monitor. No matter what resolution i choose.
    I'm pretty sure it's an issue somehow related to EDID-signal sent by the monitor. And what is strange, there's one way I manage to get anything displayed on the monitor: first i shut down the computer, then plug it to the monitor with dvi, set the monitor to hdmi in, start the mac and close instantly the lid, and then change the monitor settings to dvi in. This way i can see the white startup screen with the gray apple displayed in the middle, which, however, disappears just before the logon screen and "no signal detected", again.
    The strangest thing about this is that i somehow managed to get it work ONCE, when testing several times different versions of the routine i described above. I could get it working just as it should, log on and tested hd trailers and such but since the next time i turned the monitor off, it has been as dead as before. Any suggestions???

  • I am having trouble printing multi-page documents on my Epson printer. 13" Macbook Pro, Adobe InDesign, Epson WF-7520

    I have a multi-page document and I want to print some of the pages, double-sided, to check my work. I can't seem to get the interface to recognise that I want to print a specific range of pages, so it will print just one page [no double-sided] or, I assume, it will print the WHOLE LOT [not good at this stage!] HEEEELLLLPPP!! 
    To explain, the dialogue box which opens when you hit Command+P has an option of 'Pages' or 'Range' but 'Range' gives you only two options:  All Pages or A4V. If I click the 'Printer' button I get another dialogue box with more options and from there I can choose to print 'All' or 'Pages' . . . and you change 1 to 1 to say, 1 to 3 for example. There is also an option to print double-sided. But nothing seems to be working and as soon as you finish with this second dialogue box it seems to forget every parameter you choose there. The summary page on the first dialogue box also seems suspiciously sketchy on details of what, exactly, it is about to print. By the way I have installed the latest driver set from Apple for this printer. Is anyone else having the same problem?

    Thank you so much Eric. I did what you said. I still had the same result, but finally [somehow] I ended up clicking on something which doesn't even look clickable - this is a tiny set of back- and forward arrows in the 'Range' option. Using this feature seems pretty hit-and-miss but I persevered and was able to get it to accept my parameters, i.e. "1 - 2" in range. You have to go into the second ["Printer"] dialogue box each and every time you print, to enable two-sided printing. At last I was able to get it to print pages 1 and 2 of my three-page document. Now maybe I can test-print pages from my 108 page tome! Fingers crossed . . .   

  • Epson SP1400 Borderless Printing No More with 10.6

    Before upgrading to Snow Leopard, I had no problem printing borderless up to Super B (13" X 19") in LR 2 all margins set to zero.  Once I upgraded, I can no longer print borderless on anything other than 4" X 6".  There is now an 1/8" border around all prints larger than 4X6, again borders set to zero, paper size checked.  I even tried zoom to fill function to no avail.  Now if I could set negative margins, I probably could solve the problem ;-).  For what it is worth, I experience the same problem printing from CS4.
    So, even though there are no margins showing in LR Print module preview mode, I still get borders.  Is this a new "feature"?
    Any thoughts or comments are greatly appreciated.

    Thank you both for quick replies.  I think there is a print driver issue.  My LR2 Print presets are the same as before the 10.6 upgrade and using the same paper as before.  B4 the upgrade I was printing borderless on 13" x 19", 8" X 10", and 8.5" X 11" with no problems.  Since the upgrade, the prints now come out with a border even thought all LR and print settings indicated borderless and the paper is designed for borderless.
    Not sure what to do.  I am going to try tech support's direct line and hope they can assist.
    Thank you again for your comments.
    Matt

  • PDFs and InDesign spooling but not printing

    The printer is an Epson SP1400 connected via USB to a G3 iMac running 10.2.9 (ya, I know).
    It is shared by 4 other Macs in the office of various configs, 3 running Tiger and one running Leopard. All have the same problem.
    When using Adobe CS3 apps, files from Photoshop CS3 or Illustrator CS3 will print over the network to this shared printer. However, PDFs won't print from Acrobat Reader 7 or 8 or Acrobat CS3, nor will InDesign CS3 files print.
    The same PDF files opened in Preview do print to this shared printer.
    All other programs (Word, Excel, mail, browsers, Preview, TextEdit) all print to this shared printer.
    Some of these PDF files are older archive files and are known to have printed when the operating system was Panther.
    The permissions have been repaired on all machines and are repaired on a regular schedule along with the other routine maintenance. The printer queues have been reset and reloaded. The latest Epson driver was downloaded and is in use on all 5 machines. Epson blames Adobe, Adobe blames Epson, they both blame Apple. But no answers.
    I will try reloading my CS2 apps to see if Acrobat and InD work there.
    Meanwhile, any clues?

    I have the exact same problem, except with a different printer... a Brother HL-4040cn. I am running CS3, connecting USB and also running 10.4.11. Any InDesign or PDF files briefly spool and then get dumped into the 'completed' files bin w/o printing. Any other app works fine.

  • Judder using Mplayer... maybe force different resolution/refresh rate?

    Hi!
    (I posted this in the newbie section too, but this is maybe the most appropriate place??)
    I've set up my computer as a media center using Freevo. As the main media player in Freevo I use Mplayer. The setup is working beautifully, but I'm getting some judder and it's a bit annoying. It's most noticable during bright, fast moving scenes.
    So I've been trying to figure out how to remedy this, but it's harder than I thought. My setup is the following:
    AMD 4200+ dual core, 2 gigs ram, Nvidia 7800GTX, 24" LCD and Pioneer LX508D plasma TV, and I'm using CoreAVC as decoder (amazing piece of software )
    When I bought the 24" screen for my computer the sales guy (using windows) forced the resolution to 1920x1080. It looked a bit stretched, but if I could do this in Linux I'd avoid having parts of the picture missing on my TV. Now I have to use 1920x1200 resolution as main X session and since my TV is 1920x1080 parts of the desktop is out of view on my TV. This isn't too big of a deal though cause when playing movies they come out in 1920x1080. It'd be nice though to get the correct aspect ratio between my pc screen and my TV (I've been trying to use Twinview and clone, but it's impossible to use 1920x1200 on the 24" and 1920x1080 on the TV at the same time). I've tried to force my pc screen to use 1920x1080 (since it worked in windows it's supposed to be possible), but when I enable it through xorg.conf the screen goes blank. Using nvidia-settings doesn't give me the option of using 1920x1080 on the 24" at all.
    So what I'm hoping to be able to do is to force the computer screen to use 1920x1080 and a refresh rate of 72Hz. This should eliminate alot of the judder and at the same time I won't have to use the "PC mode" on my TV (PC mode restrict the Hz to max 60Hz). Hopefully the TV will accept the 1920x1080 72Hz as any input and let me use the normal input (and then be able to use 72Hz... or 96Hz for that matter).
    Anyone know how I might be able to do that? I'd really appreciate any help at all since this is the only thing that's not perfect with my setup.

    Ok, I tried to change the xorg.conf file to 72Hz on the TV and it when black again. This is what the xorg.0.log shows:
    X.Org X Server 1.4.2
    Release Date: 11 June 2008
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.25-ARCH i686
    Current Operating System: Linux arch 2.6.25-ARCH #1 SMP PREEMPT Mon Jul 14 15:25:51 UTC 2008 i686
    Build Date: 21 June 2008 05:47:59PM
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Module Loader present
    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 Jul 19 13:36:04 2008
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "X.org Configured"
    (**) |-->Screen "Screen0" (0)
    (**) | |-->Monitor "Monitor0"
    (**) | |-->Device "Videocard0"
    (**) |-->Input Device "Mouse0"
    (**) |-->Input Device "Keyboard0"
    (**) Option "Xinerama" "0"
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (WW) The directory "/usr/share/fonts/Type1" does not exist.
    Entry deleted from font path.
    (==) Including the default font path /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1.
    (**) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
    (**) RgbPath set to "/usr/share/X11/rgb"
    (**) ModulePath set to "/usr/lib/xorg/modules"
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) No APM support in BIOS or kernel
    (II) Loader magic: 0x81e0a60
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.3
    X.Org Video Driver: 2.0
    X.Org XInput driver : 2.0
    X.Org Server Extension : 0.3
    X.Org Font Renderer : 0.5
    (II) Loader running on linux
    (II) LoadModule: "pcidata"
    (II) Loading /usr/lib/xorg/modules//libpcidata.so
    (II) Module pcidata: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    ABI class: X.Org Video Driver, version 2.0
    (--) using VT number 3
    (II) PCI: PCI scan (all values are in hex)
    (II) PCI: 00:00:0: chip 1002,5950 card 103c,2a24 rev 10 class 06,00,00 hdr 00
    (II) PCI: 00:02:0: chip 1002,5a34 card 0000,0000 rev 00 class 06,04,00 hdr 01
    (II) PCI: 00:12:0: chip 1002,4379 card 103c,2a24 rev 00 class 01,01,8f hdr 00
    (II) PCI: 00:13:0: chip 1002,4374 card 103c,2a24 rev 00 class 0c,03,10 hdr 80
    (II) PCI: 00:13:1: chip 1002,4375 card 103c,2a24 rev 00 class 0c,03,10 hdr 00
    (II) PCI: 00:13:2: chip 1002,4373 card 103c,2a24 rev 00 class 0c,03,20 hdr 00
    (II) PCI: 00:14:0: chip 1002,4372 card 103c,2a24 rev 11 class 0c,05,00 hdr 80
    (II) PCI: 00:14:1: chip 1002,4376 card 103c,2a24 rev 00 class 01,01,8a hdr 00
    (II) PCI: 00:14:3: chip 1002,4377 card 103c,2a24 rev 00 class 06,01,00 hdr 80
    (II) PCI: 00:14:4: chip 1002,4371 card 0000,0000 rev 00 class 06,04,01 hdr 81
    (II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 01:00:0: chip 10de,0091 card 10de,02c2 rev a1 class 03,00,00 hdr 00
    (II) PCI: 02:01:0: chip 13f6,0111 card 153b,1144 rev 10 class 04,01,00 hdr 00
    (II) PCI: 02:03:0: chip 10ec,8139 card 103c,2a24 rev 10 class 02,00,00 hdr 00
    (II) PCI: 02:04:0: chip 1106,3044 card 103c,2a24 rev 80 class 0c,00,10 hdr 00
    (II) PCI: End of PCI scan
    (II) Host-to-PCI bridge:
    (II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
    (II) Bus 0 I/O range:
    [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) Bus 0 non-prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    (II) Bus 0 prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 1: bridge is at (0:2:0), (0,1,1), BCTRL: 0x000a (VGA_EN is set)
    (II) Bus 1 I/O range:
    [0] -1 0 0x0000e000 - 0x0000efff (0x1000) IX[b]
    (II) Bus 1 non-prefetchable memory range:
    [0] -1 0 0xfa000000 - 0xfcffffff (0x3000000) MX[b]
    (II) Bus 1 prefetchable memory range:
    [0] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b]
    (II) PCI-to-ISA bridge:
    (II) Bus -1: bridge is at (0:20:3), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
    (II) Subtractive PCI-to-PCI bridge:
    (II) Bus 2: bridge is at (0:20:4), (0,2,2), BCTRL: 0x0002 (VGA_EN is cleared)
    (II) Bus 2 I/O range:
    [0] -1 0 0x0000d000 - 0x0000dfff (0x1000) IX[b]
    (II) Bus 2 non-prefetchable memory range:
    [0] -1 0 0xfde00000 - 0xfdefffff (0x100000) MX[b]
    (II) Bus 2 prefetchable memory range:
    [0] -1 0 0xfdd00000 - 0xfddfffff (0x100000) MX[b]
    (--) PCI:*(1:0:0) nVidia Corporation G70 [GeForce 7800 GTX] rev 161, Mem @ 0xfa000000/24, 0xd0000000/28, 0xfb000000/24, I/O @ 0xef00/7
    (II) Addressable bus resource ranges are
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) OS-reported resource ranges:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    (II) PCI I/O resource overlap reduced 0x00004100 from 0x0000411f to 0x000040ff
    (II) PCI Memory resource overlap reduced 0xe0000000 from 0xe0000000 to 0xdfffffff
    (II) Active PCI resource ranges:
    [0] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [1] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [2] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [3] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [4] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [5] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [6] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [7] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [8] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [9] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [10] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [11] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [12] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [13] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [14] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [15] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [16] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [17] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [18] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [19] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [20] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [21] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [22] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [23] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [24] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [25] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    (II) Inactive PCI resource ranges:
    [0] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    (II) Active PCI resource ranges after removing overlaps:
    [0] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [1] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [2] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [3] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [4] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [5] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [6] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [7] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [8] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [9] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [10] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [11] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [12] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [13] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [14] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [15] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [16] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [17] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [18] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [19] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [20] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [21] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [22] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [23] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [24] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [25] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    (II) Inactive PCI resource ranges after removing overlaps:
    [0] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    (II) OS-reported resource ranges after removing overlaps with PCI:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    (II) All system resource ranges:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [17] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [18] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [19] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [20] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [21] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [22] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [24] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [25] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [26] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [27] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [28] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [29] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [30] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [31] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    [32] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
    (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    (II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
    (II) "record" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dri" will be loaded by default.
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Server Extension
    (II) NVIDIA GLX Module 173.14.09 Thu Jun 5 00:07:40 PDT 2008
    (II) Loading extension GLX
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "xtrap"
    (II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
    (II) Module xtrap: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension DEC-XTRAP
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension SHAPE
    (II) Loading extension MIT-SUNDRY-NONSTANDARD
    (II) Loading extension BIG-REQUESTS
    (II) Loading extension SYNC
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XC-MISC
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-Misc
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension TOG-CUP
    (II) Loading extension Extended-Visual-Information
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "record"
    (II) Loading /usr/lib/xorg/modules/extensions//librecord.so
    (II) Module record: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension RECORD
    (II) LoadModule: "freetype"
    (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
    (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
    compiled for 1.4.2, module version = 2.1.0
    Module class: X.Org Font Renderer
    ABI class: X.Org Font Renderer, version 0.5
    (II) Loading font FreeType
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "nvidia"
    (II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
    (II) Module nvidia: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Video Driver
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.3.0
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.0
    (II) LoadModule: "kbd"
    (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
    (II) Module kbd: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.3.1
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.0
    (II) NVIDIA dlloader X Driver 173.14.09 Wed Jun 4 23:47:25 PDT 2008
    (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    (II) Primary Device is: PCI 01:00:0
    (--) Assigning device section with no busID to primary device
    (--) Chipset NVIDIA GPU found
    (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.4.2, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.3
    (II) Loading sub module "wfb"
    (II) LoadModule: "wfb"
    (II) Loading /usr/lib/xorg/modules//libwfb.so
    (II) Module wfb: vendor="X.Org Foundation"
    compiled for 1.4.2, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.3
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
    (II) resource ranges after xf86ClaimFixedResources() call:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [17] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [18] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [19] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [20] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [21] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [22] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [24] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [25] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [26] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [27] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [28] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [29] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [30] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [31] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    [32] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    (II) resource ranges after probing:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [20] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [21] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [22] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [23] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [24] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [25] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [26] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [27] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [28] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [29] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [30] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [31] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [32] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [33] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [34] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    [35] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    [36] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [37] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) Setting vga for screen 0.
    (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    (==) NVIDIA(0): RGB weight 888
    (==) NVIDIA(0): Default visual is TrueColor
    (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    (**) NVIDIA(0): Option "NoLogo" "true"
    (**) NVIDIA(0): Option "TwinView" "1"
    (**) NVIDIA(0): Option "TwinViewOrientation" "Clone"
    (**) NVIDIA(0): Option "MetaModes" "DFP-0: 1920x1200 +0+0, DFP-1: 1920x1080_72 +0+0"
    (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0"
    (**) NVIDIA(0): Enabling RENDER acceleration
    (**) NVIDIA(0): TwinView enabled
    (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
    (II) NVIDIA(0): enabled.
    (II) NVIDIA(0): NVIDIA GPU GeForce 7800 GTX (G70) at PCI:1:0:0 (GPU-0)
    (--) NVIDIA(0): Memory: 262144 kBytes
    (--) NVIDIA(0): VideoBIOS: 05.70.02.11.20
    (II) NVIDIA(0): Detected PCI Express Link width: 16X
    (--) NVIDIA(0): Interlaced video modes are supported on this GPU
    (--) NVIDIA(0): Connected display device(s) on GeForce 7800 GTX at PCI:1:0:0:
    (--) NVIDIA(0): BenQ G2400W (DFP-0)
    (--) NVIDIA(0): PIONEER_PDP. (DFP-1)
    (--) NVIDIA(0): BenQ G2400W (DFP-0): 310.0 MHz maximum pixel clock
    (--) NVIDIA(0): BenQ G2400W (DFP-0): Internal Dual Link TMDS
    (--) NVIDIA(0): PIONEER_PDP. (DFP-1): 155.0 MHz maximum pixel clock
    (--) NVIDIA(0): PIONEER_PDP. (DFP-1): Internal Single Link TMDS
    (II) NVIDIA(0): Display Devices found referenced in MetaMode: DFP-0, DFP-1
    (II) NVIDIA(0): Assigned Display Devices: DFP-0, DFP-1
    (II) NVIDIA(0): Validated modes:
    (II) NVIDIA(0): "DFP-0:1920x1200+0+0,DFP-1:1920x1080_72+0+0"
    (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1200
    (--) NVIDIA(0): DPI set to (93, 95); computed from "UseEdidDpi" X config
    (--) NVIDIA(0): option
    (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
    (--) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC? No, I don't.
    (II) resource ranges after preInit:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
    [5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
    [6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
    [7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
    [8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
    [9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
    [10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
    [11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
    [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
    [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [20] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
    [21] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
    [22] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
    [23] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
    [24] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [25] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [26] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
    [27] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
    [28] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
    [29] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
    [30] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
    [31] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [32] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
    [33] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
    [34] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
    [35] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
    [36] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [37] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) NVIDIA(0): Initialized GPU GART.
    (II) NVIDIA(0): Unable to connect to the ACPI daemon; the ACPI daemon may not
    (II) NVIDIA(0): be running or the "AcpidSocketPath" X configuration option
    (II) NVIDIA(0): may not be set correctly. When the ACPI daemon is
    (II) NVIDIA(0): available, the NVIDIA X driver can use it to receive ACPI
    (II) NVIDIA(0): events. For details, please see the "ConnectToAcpid" and
    (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    (II) NVIDIA(0): Config Options in the README.
    (II) NVIDIA(0): Setting mode "DFP-0:1920x1200+0+0,DFP-1:1920x1080_72+0+0"
    (II) Loading extension NV-GLX
    (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
    (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
    (==) NVIDIA(0): Backing store disabled
    (==) NVIDIA(0): Silken mouse enabled
    (II) Loading extension NV-CONTROL
    (==) RandR enabled
    (II) Setting vga for screen 0.
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension XAccessControlExtension
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension XFree86-Bigfont
    (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) Initializing built-in extension XEVIE
    (II) Initializing extension GLX
    (**) Option "Protocol" "auto"
    (**) Mouse0: Device: "/dev/input/mice"
    (**) Mouse0: Protocol: "auto"
    (**) Option "CorePointer"
    (**) Mouse0: always reports core events
    (**) Option "Device" "/dev/input/mice"
    (**) Option "Emulate3Buttons" "yes"
    (**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
    (**) Option "ZAxisMapping" "4 5 6 7"
    (**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7
    (**) Mouse0: Buttons: 11
    (**) Mouse0: Sensitivity: 1
    (**) Option "CoreKeyboard"
    (**) Keyboard0: always reports core events
    (**) Option "Protocol" "standard"
    (**) Keyboard0: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) Keyboard0: XkbRules: "xorg"
    (**) Option "XkbModel" "trustda"
    (**) Keyboard0: XkbModel: "trustda"
    (**) Option "XkbLayout" "no"
    (**) Keyboard0: XkbLayout: "no"
    (**) Option "CustomKeycodes" "off"
    (**) Keyboard0: CustomKeycodes disabled
    (II) evaluating device (Keyboard0)
    (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
    (II) evaluating device (Mouse0)
    (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
    (--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
    (II) Mouse0: ps2EnableDataReporting: succeeded
    Could not init font path element /usr/share/fonts/Type1, removing from list!
    My xorg.conf looks like this now (I don't know what values to use for HorizSync and VertFresh on my TV, the ones that are in there I just made up ):
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings: version 1.0 (buildmeister@builder63) Mon May 19 00:34:28 PDT 2008
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "glx"
    Load "dbe"
    Load "xtrap"
    Load "extmod"
    Load "record"
    Load "freetype"
    EndSection
    Section "ServerFlags"
    Option "Xinerama" "0"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "trustda"
    Option "XkbLayout" "no"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    Option "Emulate3Buttons" "yes"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "BenQ G2400W"
    HorizSync 31.0 - 94.0
    VertRefresh 50.0 - 85.0
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "PIONEER_PDP."
    # HorizSync 15.0 - 80.0
    # VertRefresh 23.0 - 60.0
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "G70 [GeForce 7800 GTX]"
    BusID "PCI:1:0:0"
    EndSection
    Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7800 GTX"
    EndSection
    Section "Device"
    Identifier "Videocard1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7800 GTX"
    BusID "PCI:1:0:0"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Videocard0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "NoLogo" "true"
    Option "TwinViewOrientation" "Clone"
    Option "TwinView" "1"
    Option "TwinViewXineramaInfoOrder" "DFP-0"
    Option "metamodes" "DFP-0: 1920x1200 +0+0, DFP-1: 1920x1080_72 +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    I read somewhere that the TV is supposed to be able to show 1080p in 72Hz. But when I try that it goes blank. Maybe it has something to do with the monitor being 1920x1200 and the TV 1920x1080. The monitor won't accept 1920x1080 as resolution so I guess that can only be done in Windows...

  • OSX, Acrobat Reader 5 and printing problems

    Not sure this is in the right place (possibly should go to the Adobe Reader section) but help needed.
    I have PDFs that look just fine on screen, but when they are printed out, the image is being reduced in size. It is as if there are some margins set someplace (although where, I have no idea) that are over-riding the PDF as it appears on screen. Is this behaviour typical with reader 5? Is there a setting somewhere that will cause the image to be reduced in size? If this is a bug, does anyone know if it is fixed in the Adobe reader range? Is anyone else experiencing this?
    My set up is a Mac G4 sawtooth, with upgraded processor (1.5GHz) and new hard drive running 'out of the box' OSX 10.4.6 (Tiger) with Classic accessing the original OS9 installation on the original hard drive.
    Range of Adobe products running in Classic (PS 5.5, AI 9.2, ID 1.2) from which some of the PDFs originate.
    Old OS9 compatible printer (Epson SP1200) died recently, new printer (Epson SP1400) is only comaptible with OSX, except going via Laserwriter8.
    Problem was present with old printer before it died as well, so OS/printer incompatibility is probably the issue.
    Upgrading to CS3 is an option, but an expensive one, so wish to explore the Portable Document Format option first!

    It cannot be a problem of the installation, because at least Windows 7
    was a fresh install with nothing but Reader additionally installed.
    By the way, what do you mean by "risky", I followed straight the
    documentation from Adobe, where one is allowed to place function calls
    requiring a privileged context.
    Have you any better idea where to place the call to save? It must be
    called automatically, when the User closes the window, no additional
    interaction is possible.
    One other thing is the call to exportXFAData, have you any idea why
    there is a difference in behavior between reader version 7 / 10 and 9?
    I wrote that in version 9 the user entered data is missing.
    Am Donnerstag, den 21.07.2011, 05:53 -0600 schrieb try67:
    No, it doesn't work.
    Sorry, I don't have any ideas except for trying to repair the installation
    of Reader.
    However, placing code in the WillClose event is considered risky and should
    be avoided if there are alternatives available.
    >

  • File spooling but not printing - InD CS3

    I am at a loss as to why InD CS3 (and Acrobat and Reader) will not print to a shared printer. Illustrator CS3 and Photoshop CS3 will print to this shared printer. Why not InD CS3? This has been ongoing since CS3 came out.
    The file spools, all images and fonts are downloaded but the file never appears in the print queue. Not on the originating machine or the sharing machine. It just vanishes.
    CS3 Pro versions Loaded on Mac G5 dual 2gig (non-intel) running Tiger. Three other machines have the same issue. All various machine configs (G4 single/Tiger, G5 dual 1.8/Tiger, and an Intel iMac/Leopard).
    - Printer is shared through a networked G3 running Jaguar (yeah, yeah, working on it).
    - The printer is an Epson SP1400
    - All drivers updated on all machines.
    - All CS3 patches done.
    - Permissions done.
    - OnyX system maintenance done.
    - Preferences trashed. Machines restarted (printer and macs).
    - The InD CS3 file can be printed from CS3 to a networked Panasonic postscript printer. So it's not the file.
    - The InD file can be saved down using Interchange to CS2 and that will print to the shared printer.
    - The InD CS3 file will print to this printer if the printer is connected directly to the machine it is printing from.
    Apple and Epson have pointed out that because other CS3 apps do print to the printer, there is something going on with InD, Acrobat and Reader and the sharing function. Is it the G3 and Jag? Or something to do with CUPS or .local or a sharing protocol? Please help me out with this.

    Anything interesting in the logs on the printing machine or the sharing machine?
    In the Print button in the Adobe Print dialog, click the popup to Error Handling and tell it to cough up an error page if it fails to print. Maybe the printer will give you feedback about why it's failing then.
    If that does nothing, then what if you print the file to postscript and drop the PS file onto the printer icon in the Dock? That would at least guarantee you were getting a file and let you experiment with why it isn't making it all the way through the process.
    A final thought is to raster it completely [make a Transparency Flattener set to 100% raster @ whatever DPI] and see if just a bitmap will print correctly. That tells you if it's something weird with the postscript at least.
    It's all guesses, really. But at least it might give you something new to play with... Best of luck!

  • [Help] wine (AUR) + ATI WoW = crash on launch

    Howdy
    Been using Arch for a long time (came from Gentoo), but not been much of a gamer the last years, for that i had a MS rig with xp then vista.
    I installed the 32-wine from AUR (thanks for that by the way), everything seems ok.
    I downloaded the apropriate installers for WoW, both normal and Burning Crusade.
    Both install fine, and i can "launch" the game from the "desktop shortcut".
    The problem does not start when I hit "play", then my screen all gets "twisted", and everything gets pixelated.
    (Kind of when a game crashes and messes up the screen)
    the only fix i found so far is ctrl+alt+<--" to get back into KDE to get it working again.
    this is run on a 3870 card from ATI, everything else works fine, include compizfusion (turned of when i try to run the game).
    Everything else seems to work fine.
    I assume it is some sort of gfx bug, prolly relates to directx, but i get same result when i use -opengl to launch launcher.exe
    The problem "breaks" everything, even when run in a containerwindow.
    Settings are for xp (winecfg)
    Posting xorg.conf incase there might be something related to that.
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "dbe"
    Load "glx"
    Load "dri"
    Load "extmod"
    Load "GLcore"
    Load "record"
    Load "xtrap"
    Load "freetype"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "trustda"
    Option "XkbLayout" "no"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    #DisplaySize 520 320 # mm
    ### Comment all HorizSync and VertRefresh values to use DDC:
    Identifier "Monitor0"
    VendorName "BNQ"
    ModelName "BenQ G2400W"
    HorizSync 31.0 - 94.0
    VertRefresh 50.0 - 85.0
    Option "DPMS"
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Device"
    Option "DRI" "true"
    Identifier "Card0"
    Driver "radeon"
    VendorName "ATI Technologies Inc"
    BoardName "Unknown Board"
    BusID "PCI:1:0:0"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    BusID "PCI:1:0:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]-0"
    Device "aticonfig-Device[0]-0"
    Monitor "aticonfig-Monitor[0]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "DRI"
    Mode 0666
    EndSection
    Running on a 24" monitor @ 1920x1200.
    Any help apriciated.
    Last edited by AllFather (2008-07-21 22:07:38)

    That's a really convoluted xorg.conf (two Screens, two Devices, two Monitors). If you look, you're using aticonfig-Monitor, aticonfig-Screen, and aticonfig-Device. I would try your other entries in different combinations (Screen0, Card0, Monitor0) and try tuning them.
    How did you make that config? Try hwd -xa as well.
    Last edited by Ranguvar (2009-02-19 04:26:41)

  • Printing with ColorSync Problems!

    I cannot seem to print anything with Aperture using ColorSync for color management. I have set my monitor to Cinema display calibrated (yes, I have) and I set all the epson stylus photo 1800 settings, choosing ColorSync for color management, but my prints come out like darkened mud.
    If I print with photoshop I get great prints, if I print with Preview and ColorSync I get reasonably good prints.
    Any ideas?
    dual 2gHz G5   Mac OS X (10.4.3)  

    I figured out, after a while, that in the print settings window of Aperture you must set the color settings in 2 places. In the printer settings, as one would expect. But then there is a second drop down menu below the printer settings where you must set the printer/paper profile match that you want.
    Once I figured that out, I am getting consistently more accurate color matches to what I see onscreen than I was in Photoshop.
    (I use a 20" Apple Cinema Display with Monaco Optix color calibration)
    Thanks for the suggestions though.
    -Sol

  • What's going on with my Media settings?

    Hello,
    I'm using Acrobat 9 pro for Mac (snow leopard) and experiencing a few issues.
    When I select the print settings dialog, I am presented with the following (attatched). I am un able to print to Epson gloss, semi-gloss or lustre papers, only Matte is listed. In colour handling, I have all the ICC profiles for each paper type, so I can use colorsync for a better result... The problem is there are hardly any papers listed and I have no idea how to 'get them there'.
    I've posted this in the Illustrator forum too as I was asking if Ai and Acrobat have the same color management capabilities...a member on that thread has a similar setup to me and he is able to few a much wider range of papers.
    Thank You
    (I have an Epson R2880)

    Prior to changing the colorsync profile and paper, I would be able to change the gamma and color, but that's it... there is no option for paper under advanced
    Thank you for your help.

  • CS5 and Lightroom 3 printing differently

    I have recently upgraded Lightroom to v3.0 and took advantage,at the same time, to upgrade my CS3 to CS5.
    I printed something from CS5 and was very dissapointed in the result.  The printed result was much too dark.  I recalibrated my printer, using Spyder3 print, for the printer/ink/paper combination I was using.  I reprinted with the same results (much too dark).  I have set CS5 to manage colour and selected the newly created profile and switched colour management off in the printer driver (Epson R2400).
    I then tried printing the same image from within Lightroom 3.  I set the profile to the same as used in CS5 and set colour management off in the printer driver.  In both cases the rendering intent was set to Relative.  This printed almost perfectly.  Perhaps a little darker than on-screen but the colour rendering was fine.
    To give you an idea as to how different the results are I took a picture of the screen with LR3 and CS5 showing the same image and with their respective prints propped below.
    Any ideas what the problem might be?
    Regards,
    Norman

    I have the same problem with CS5, but I don't have LR to compare it to. CS5 prints are much darker than displayed on monitor. Photoshop manages colors. Epson R1400. Monitor calibrated with Pantone Huey. Colors are accurate - just darker than screen. My everyday Canon MP640 shows same results, so I suspect the problem is tied to the display. Any hints?
    Regards,
    DJ

  • Duplicate Profiles Showing

    In Photoshop I see one Epson Stylus xxx. profile for each paper type. In Aperture I am seeing 2 (a duplicate) profile for each paper type. Unfortunately, I can not even find the location of the Epson profiles - even if using Spotlight to search by "Epson" and/or ".icc", etc, etc. as I assume there are duplicate profiles roaming on my drive somewhere. I had initially thought that duplicates were in the root and user librarys but not so. Any help appreciated.

    The duplicate and in my case 5 listings of each are due to selecting multiple sub printers from your printer driver. It's probably a bug but if you want to see only one move the ICC profiles from the Epson folder to Startup Drive>Library>ColorSync>Profiles. You can then delete the Epson folder from "Printers". If you want them back again someday just run Printer Setup Utility and add your printer(s) again.
    Dual Core 2 GHz G5   Mac OS X (10.4.3)   GeForce 7800GT, 2.5G RAM, 74GB Raptor, 250GB

  • Colors off when printing on Epson printer from Indesign

    I'm new to Indesign. I'm a photographer trying to print a booklet for a handmade book.
    My question is about preparing photographic images for use in Indesign.
    I have JPEGS, saved as RGB files at 300DPI. I'm printing on an Epson R2000 using a custom paper and custom ICC profile. In my Color Management dialog I have Let Indesign handle colors and the correct printer profile selected. Output color is Composite RGB. The colors are really off so obviously I'm doing something wrong. I'm no expert so any advice much appreciated!

    Hi - I disabled the custom profile for my Moab paper and whilst the green hue is gone, the colors are dull. My question is should I save my images in Photoshop to CMYK? As opposed to RGB?
    Should I change the color profile assigned to Indesign to Adobe RGB? This was the original color profile of the image in Photoshop.

  • Printing problem with Epson R290 Illustrator and inDesign

    I am running CS2 on Leopard and have recently purchased an Epson R290. The first time I used it with Illustrator and InDesign it worked fine but now whenever I print anything it prints a tiny version (about a sixth of the real size) of the design in the top left corner of the page. It does this both with new documents and old ones that used to print ok.

    Since I posted the message about this problem I have discovered that it can be worked around by choosing a higher quality print. ie if you choose plain paper when printing from Illustrator or InDesign the printer prints a reduced size image but if you choose Ink jet mat or glossy the print comes out fine. I don't have this problem with Photoshop but that may be that I always print high quality from that application. I don't use Appleworks Draw so don't know whether this solves the problem for that application but iWork documents print ok.

Maybe you are looking for