Printing in a Blue/Purple tint... ?

Suddenly it seems that my iPhoto will only prints photos in very bluish to purplish hues.
I can't think of anything I've changed. I've been printing just fine since my last ink change maybe 5-6 weeks ago, including photos. Now it prints everything in blue/purple for the most part.

Try Fix 101: delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your User/Library/Preferences folder.
Also have you run the nozzle cleaning routine and the nozzle check print to make sure they all are clear and printing correctly?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier versions) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. There are versions that are compatible with iPhoto 5, 6, 7 and 8 libraries and Tiger and Leopard. Just put the application in the Dock and click on it whenever you want to backup the dB file. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
NOTE: The new rebuild option in iPhoto 09 (v. 8.0.2), Rebuild the iPhoto Library Database from automatic backup" makes this tip obsolete.

Similar Messages

  • Strange Color issue for my display (blue - purple tint)

    hi guys,
    I have a white macbook.
    Recently, I realize some color issue on displaying blue.
    check this picture below (I uploaded to my flickr)
    and when it occurs I can only restart my computer, sometimes it changes back to normal...
    or I can just use an external screen to ignore this problem (which I am doing it now)
    anyone have any ideas?

    I fixed it by going back into each diffuse texture and choosing "Edit UV Properties" and hitting OK - this seem to reset and re-render each texture.
    Seems like a bug unless you can't use Image Size on documents that contain 3D layers maybe?

  • Start up screen purple tint, won't boot, then vertical blue lines

    I'm having trouble with my  macbook pro late  2011 model running maverick
    When I try turning it on I get a start up screen with a purple tint then the apple logo just disappears and the entire screen is with that purple tint (see pic below, sorry if tint isn't too visible and also for the upside down pic, this pc is driving me crazy)
    Then when I try booting in safe mode the screen suddenly turns to a screen with blue vertical lines as below.
    Funny thing is that a few days later everything went back to normal, then a few weeks later happened again. Now third time it's happening. I also notice once or twice the fan was working hard prior to computer freezing... perhaps not related not sure.
    Took it to an apple service center and they tested for 3 days and werent able to come up with solution they ordered a replacement display and in a few weeks will replace. They say if that doesn't work they'll have to replace the video card..
    Anyone have any clue what this might be?
    When I called Apple support they were inclined to suggest it's defective memory non apple, but I don't see that to be the case...
    I'm overseas and can't bring in to apple store.. thanks

    Thank you
    Where I'm currently located no local apple only a authorized service center... brought to them and they decided to order a new display panel. I have to wait two weeks til they get it then if that doesn't work they'll order a new motherboard..
    They ran a series of tests on the notebook for two dates... wouldn't they have uncovered if it was memory related?

  • [Solved] X11 has purple tint when using catalyst-test drivers

    Hey guys, so I turned the TV on for my HTPC last night hoping to watch some anime. But when it turned on the screen had a purple tint! I tried to do some debugging over SSH from my phone while in bed, but decided to just go to sleep instead.
    Tonight I narrowed down the problem a bit, it's certainly related to the catalyst drivers (No problems when using xf86-video-ati).
    I'm noticing warnings from various programs that look like
    libpng warning: iCCP: known incorrect sRGB profile
    Taking a screenshot using `scrot` and viewing it the screen looks fine..
    Here's my xorg.conf (which is just the default genearted by aticonfig --initial)
    Section "ServerLayout"
    Identifier "aticonfig Layout"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    BusID "PCI:0:1:0"
    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
    I suspected that it might have been a package upgrade, but downgrading packages that looked like they might have been the problem didn't solve anything.
    Any ideas?
    Edit: Just tried with xorg1.13 with Catalyst 13.4 (stable).. same problem.
    Edit 2: After starting and then stopping X this problem happens in the framebuffer too.. hmmm (It doesn't happen during boot time or during initial login, it's not a bad cable connection!)
    Edit 3: The problem does not occur when using the VGA d-sub output, only when using the HDMI output
    Edit 4: Here's my Xorg.0.log
    [ 1826.112]
    X.Org X Server 1.14.2
    Release Date: 2013-06-25
    [ 1826.112] X Protocol Version 11, Revision 0
    [ 1826.112] Build Operating System: Linux 3.9.7-1-ARCH x86_64
    [ 1826.112] Current Operating System: Linux htpc 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:45:16 CEST 2013 x86_64
    [ 1826.112] Kernel command line: initrd=\initramfs-linux.img root=UUID=03f6bfa4-7815-4841-8386-5545dfa4cd33 ro loglevel=0 nomodeset
    [ 1826.112] Build Date: 01 July 2013 10:48:42AM
    [ 1826.112]
    [ 1826.113] Current version of pixman: 0.30.0
    [ 1826.113] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 1826.113] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 1826.113] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 22 08:39:14 2013
    [ 1826.113] (==) Using config file: "/etc/X11/xorg.conf"
    [ 1826.113] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 1826.113] (==) ServerLayout "aticonfig Layout"
    [ 1826.113] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
    [ 1826.113] (**) | |-->Monitor "aticonfig-Monitor[0]-0"
    [ 1826.114] (**) | |-->Device "aticonfig-Device[0]-0"
    [ 1826.114] (==) Automatically adding devices
    [ 1826.114] (==) Automatically enabling devices
    [ 1826.114] (==) Automatically adding GPU devices
    [ 1826.114] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
    [ 1826.114] Entry deleted from font path.
    [ 1826.114] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 1826.114] Entry deleted from font path.
    [ 1826.114] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 1826.114] Entry deleted from font path.
    [ 1826.114] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 1826.114] Entry deleted from font path.
    [ 1826.114] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 1826.114] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 1826.114] Entry deleted from font path.
    [ 1826.114] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 1826.114] (==) FontPath set to:
    /usr/share/fonts/misc/
    [ 1826.114] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 1826.114] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 1826.114] (II) Loader magic: 0x7fdc20
    [ 1826.114] (II) Module ABI versions:
    [ 1826.114] X.Org ANSI C Emulation: 0.4
    [ 1826.114] X.Org Video Driver: 14.1
    [ 1826.114] X.Org XInput driver : 19.1
    [ 1826.114] X.Org Server Extension : 7.0
    [ 1826.117] (--) PCI:*(0:0:1:0) 1002:964a:1565:1707 rev 0, Mem @ 0xc0000000/268435456, 0xfef00000/262144, I/O @ 0x0000f000/256
    [ 1826.117] Initializing built-in extension Generic Event Extension
    [ 1826.117] Initializing built-in extension SHAPE
    [ 1826.117] Initializing built-in extension MIT-SHM
    [ 1826.117] Initializing built-in extension XInputExtension
    [ 1826.117] Initializing built-in extension XTEST
    [ 1826.117] Initializing built-in extension BIG-REQUESTS
    [ 1826.117] Initializing built-in extension SYNC
    [ 1826.117] Initializing built-in extension XKEYBOARD
    [ 1826.117] Initializing built-in extension XC-MISC
    [ 1826.117] Initializing built-in extension SECURITY
    [ 1826.117] Initializing built-in extension XINERAMA
    [ 1826.117] Initializing built-in extension XFIXES
    [ 1826.117] Initializing built-in extension RENDER
    [ 1826.117] Initializing built-in extension RANDR
    [ 1826.117] Initializing built-in extension COMPOSITE
    [ 1826.117] Initializing built-in extension DAMAGE
    [ 1826.117] Initializing built-in extension MIT-SCREEN-SAVER
    [ 1826.117] Initializing built-in extension DOUBLE-BUFFER
    [ 1826.117] Initializing built-in extension RECORD
    [ 1826.117] Initializing built-in extension DPMS
    [ 1826.117] Initializing built-in extension X-Resource
    [ 1826.117] Initializing built-in extension XVideo
    [ 1826.117] Initializing built-in extension XVideo-MotionCompensation
    [ 1826.117] Initializing built-in extension XFree86-VidModeExtension
    [ 1826.117] Initializing built-in extension XFree86-DGA
    [ 1826.117] Initializing built-in extension XFree86-DRI
    [ 1826.117] Initializing built-in extension DRI2
    [ 1826.117] (II) "glx" will be loaded by default.
    [ 1826.117] (II) LoadModule: "glx"
    [ 1826.117] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 1826.117] (II) Module glx: vendor="Advanced Micro Devices, Inc."
    [ 1826.117] compiled for 6.9.0, module version = 1.0.0
    [ 1826.118] Loading extension GLX
    [ 1826.118] (II) LoadModule: "fglrx"
    [ 1826.118] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
    [ 1826.134] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
    [ 1826.134] compiled for 1.4.99.906, module version = 13.10.10
    [ 1826.134] Module class: X.Org Video Driver
    [ 1826.134] (II) Loading sub module "fglrxdrm"
    [ 1826.134] (II) LoadModule: "fglrxdrm"
    [ 1826.134] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
    [ 1826.134] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
    [ 1826.134] compiled for 1.4.99.906, module version = 13.10.10
    [ 1826.134] (II) AMD Proprietary Linux Driver Version Identifier:13.10.10
    [ 1826.134] (II) AMD Proprietary Linux Driver Release Identifier: UNSUPPORTED-13.101
    [ 1826.134] (II) AMD Proprietary Linux Driver Build Date: May 23 2013 15:49:35
    [ 1826.134] (++) using VT number 4
    [ 1826.136] (WW) Falling back to old probe method for fglrx
    [ 1826.150] (II) Loading PCS database from /etc/ati/amdpcsdb /etc/ati/amdpcsdb.default
    [ 1826.154] ukiDynamicMajor: found major device number 250
    [ 1826.154] ukiDynamicMajor: found major device number 250
    [ 1826.154] ukiOpenByBusid: Searching for BusID PCI:0:1:0
    [ 1826.154] ukiOpenDevice: node name is /dev/ati/card0
    [ 1826.154] ukiOpenDevice: open result is 9, (OK)
    [ 1826.154] ukiOpenByBusid: ukiOpenMinor returns 9
    [ 1826.154] ukiOpenByBusid: ukiGetBusid reports PCI:0:1:0
    [ 1826.156] (--) Chipset Supported AMD Graphics Processor (0x964A) found
    [ 1826.156] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:1:1) found
    [ 1826.156] (II) AMD Video driver is running on a device belonging to a group targeted for this release
    [ 1826.156] (II) AMD Video driver is signed
    [ 1826.157] (II) fglrx(0): pEnt->device->identifier=0xcf8900
    [ 1826.157] (II) fglrx(0): === [xdl_xs114_atiddxPreInit] === begin
    [ 1826.157] (II) Loading sub module "vgahw"
    [ 1826.157] (II) LoadModule: "vgahw"
    [ 1826.157] (II) Loading /usr/lib/xorg/modules/libvgahw.so
    [ 1826.157] (II) Module vgahw: vendor="X.Org Foundation"
    [ 1826.157] compiled for 1.14.2, module version = 0.1.0
    [ 1826.157] ABI class: X.Org Video Driver, version 14.1
    [ 1826.158] (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
    [ 1826.158] (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
    [ 1826.158] (==) fglrx(0): Default visual is TrueColor
    [ 1826.158] (**) fglrx(0): Option "DPMS" "true"
    [ 1826.158] (==) fglrx(0): RGB weight 888
    [ 1826.158] (II) fglrx(0): Using 8 bits per RGB
    [ 1826.158] (==) fglrx(0): Buffer Tiling is ON
    [ 1826.158] (II) Loading sub module "fglrxdrm"
    [ 1826.158] (II) LoadModule: "fglrxdrm"
    [ 1826.158] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
    [ 1826.158] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
    [ 1826.158] compiled for 1.4.99.906, module version = 13.10.10
    [ 1826.161] ukiDynamicMajor: found major device number 250
    [ 1826.162] ukiDynamicMajor: found major device number 250
    [ 1826.162] ukiOpenByBusid: Searching for BusID PCI:0:1:0
    [ 1826.162] ukiOpenDevice: node name is /dev/ati/card0
    [ 1826.162] ukiOpenDevice: open result is 12, (OK)
    [ 1826.162] ukiOpenByBusid: ukiOpenMinor returns 12
    [ 1826.162] ukiOpenByBusid: ukiGetBusid reports PCI:0:1:0
    [ 1826.162] (**) fglrx(0): NoAccel = NO
    [ 1826.162] (**) fglrx(0): AMD 2D Acceleration Architecture enabled
    [ 1826.162] (--) fglrx(0): Chipset: "AMD Radeon HD 6530D" (Chipset = 0x964a)
    [ 1826.162] (--) fglrx(0): (PciSubVendor = 0x1565, PciSubDevice = 0x1707)
    [ 1826.162] (==) fglrx(0): board vendor info: third party graphics adapter - NOT original AMD
    [ 1826.162] (--) fglrx(0): Linear framebuffer (phys) at 0xc0000000
    [ 1826.162] (--) fglrx(0): MMIO registers at 0xfef00000
    [ 1826.162] (--) fglrx(0): I/O port at 0x0000f000
    [ 1826.162] (==) fglrx(0): ROM-BIOS at 0x000c0000
    [ 1826.163] (II) fglrx(0): AC Adapter is used
    [ 1826.163] (II) fglrx(0): AMD Video BIOS revision 9 or later detected
    [ 1826.163] (--) fglrx(0): Video RAM: 524288 kByte, Type: DDR3
    [ 1826.163] (II) fglrx(0): PCIE card detected
    [ 1826.163] (--) fglrx(0): Using per-process page tables (PPPT) as GART.
    [ 1826.163] (WW) fglrx(0): board is an unknown third party board, chipset is supported
    [ 1826.163] (II) fglrx(0): [FB] MC range(MCFBBase = 0xf00000000, MCFBSize = 0x20000000)
    [ 1826.163] (II) fglrx(0): RandR 1.2 support is enabled!
    [ 1826.163] (II) fglrx(0): RandR 1.2 rotation support is enabled!
    [ 1826.163] (==) fglrx(0): Center Mode is disabled
    [ 1826.163] (II) Loading sub module "fb"
    [ 1826.163] (II) LoadModule: "fb"
    [ 1826.163] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 1826.164] (II) Module fb: vendor="X.Org Foundation"
    [ 1826.164] compiled for 1.14.2, module version = 1.0.0
    [ 1826.164] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 1826.164] (II) Loading sub module "ddc"
    [ 1826.164] (II) LoadModule: "ddc"
    [ 1826.164] (II) Module "ddc" already built-in
    [ 1826.293] (II) fglrx(0): Output DFP1 using monitor section aticonfig-Monitor[0]-0
    [ 1826.293] (II) fglrx(0): Output CRT1 has no monitor section
    [ 1826.293] (II) Loading sub module "ddc"
    [ 1826.293] (II) LoadModule: "ddc"
    [ 1826.293] (II) Module "ddc" already built-in
    [ 1826.293] (II) fglrx(0): Connected Display0: DFP1
    [ 1826.293] (II) fglrx(0): Display0: Failed to get EDID information.
    [ 1826.294] (II) fglrx(0): EDID for output DFP1
    [ 1826.294] (II) fglrx(0): Manufacturer: EXP Model: 901 Serial#: 1
    [ 1826.294] (II) fglrx(0): Year: 2004 Week: 0
    [ 1826.294] (II) fglrx(0): EDID Version: 1.3
    [ 1826.294] (II) fglrx(0): Digital Display Input
    [ 1826.294] (II) fglrx(0): Max Image Size [cm]: horiz.: 115 vert.: 65
    [ 1826.294] (II) fglrx(0): Gamma: 2.20
    [ 1826.294] (II) fglrx(0): DPMS capabilities: Off
    [ 1826.294] (II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 1826.294] (II) fglrx(0): First detailed timing is preferred mode
    [ 1826.294] (II) fglrx(0): redX: 0.618 redY: 0.351 greenX: 0.280 greenY: 0.605
    [ 1826.294] (II) fglrx(0): blueX: 0.152 blueY: 0.063 whiteX: 0.312 whiteY: 0.329
    [ 1826.294] (II) fglrx(0): Supported established timings:
    [ 1826.294] (II) fglrx(0): 640x480@60Hz
    [ 1826.294] (II) fglrx(0): 800x600@60Hz
    [ 1826.294] (II) fglrx(0): 1024x768@60Hz
    [ 1826.294] (II) fglrx(0): Manufacturer's mask: 0
    [ 1826.294] (II) fglrx(0): Supported detailed timing:
    [ 1826.294] (II) fglrx(0): clock: 74.2 MHz Image Size: 16 x 9 mm
    [ 1826.294] (II) fglrx(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 1826.294] (II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 1826.294] (II) fglrx(0): Supported detailed timing:
    [ 1826.294] (II) fglrx(0): clock: 27.0 MHz Image Size: 4 x 3 mm
    [ 1826.294] (II) fglrx(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
    [ 1826.294] (II) fglrx(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
    [ 1826.294] (II) fglrx(0): Monitor name: EP-HDMI-RX
    [ 1826.294] (II) fglrx(0): Ranges: V min: 59 V max: 61 Hz, H min: 15 H max: 46 kHz, PixClock max 85 MHz
    [ 1826.294] (II) fglrx(0): Supported detailed timing:
    [ 1826.294] (II) fglrx(0): clock: 74.2 MHz Image Size: 16 x 9 mm
    [ 1826.294] (II) fglrx(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 1826.294] (II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 1826.294] (II) fglrx(0): Supported detailed timing:
    [ 1826.294] (II) fglrx(0): clock: 74.2 MHz Image Size: 16 x 9 mm
    [ 1826.294] (II) fglrx(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 1826.294] (II) fglrx(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 1826.294] (II) fglrx(0): Supported detailed timing:
    [ 1826.294] (II) fglrx(0): clock: 74.2 MHz Image Size: 16 x 9 mm
    [ 1826.294] (II) fglrx(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
    [ 1826.294] (II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 1826.294] (II) fglrx(0): Supported detailed timing:
    [ 1826.294] (II) fglrx(0): clock: 74.2 MHz Image Size: 16 x 9 mm
    [ 1826.294] (II) fglrx(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
    [ 1826.294] (II) fglrx(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 1826.294] (II) fglrx(0): Number of EDID sections to follow: 1
    [ 1826.294] (II) fglrx(0): EDID (in hex):
    [ 1826.294] (II) fglrx(0): 00ffffffffffff001710010901000000
    [ 1826.294] (II) fglrx(0): 000e0103807341782a7c119e59479b27
    [ 1826.294] (II) fglrx(0): 10505421080001010101010101010101
    [ 1826.294] (II) fglrx(0): 010101010101011d007251d01e206e28
    [ 1826.294] (II) fglrx(0): 550010090000001e8c0ad08a20e02d10
    [ 1826.294] (II) fglrx(0): 103e9600040300000018000000fc0045
    [ 1826.294] (II) fglrx(0): 502d48444d492d52580a2020000000fd
    [ 1826.294] (II) fglrx(0): 003b3d0f2e08000a20202020202001ab
    [ 1826.294] (II) fglrx(0): EDID vendor "EXP", prod id 2305
    [ 1826.294] (II) fglrx(0): Using EDID range info for horizontal sync
    [ 1826.294] (II) fglrx(0): Using EDID range info for vertical refresh
    [ 1826.294] (II) fglrx(0): Printing DDC gathered Modelines:
    [ 1826.294] (II) fglrx(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz eP)
    [ 1826.294] (II) fglrx(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 1826.294] (II) fglrx(0): Printing probed modes for output DFP1
    [ 1826.294] (II) fglrx(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz eP)
    [ 1826.294] (II) fglrx(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1920x1080"x60.0 74.25 1920 2008 2052 2200 1080 1085 1095 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1920x1080"x50.0 74.25 1920 2448 2492 2640 1080 1085 1095 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1920x1080"x59.9 74.18 1920 2008 2052 2200 1080 1085 1095 1125 interlace +hsync +vsync (33.7 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1776x1000"x59.9 148.35 1776 1864 1908 2200 1000 1004 1009 1125 +hsync +vsync (67.4 kHz ez)
    [ 1826.294] (II) fglrx(0): Modeline "1776x1000"x50.0 74.25 1776 2304 2348 2640 1000 1005 1015 1125 interlace +hsync +vsync (28.1 kHz ez)
    [ 1826.294] (II) fglrx(0): Modeline "1776x1000"x59.9 74.18 1776 1864 1908 2200 1000 1005 1015 1125 interlace +hsync +vsync (33.7 kHz ez)
    [ 1826.294] (II) fglrx(0): Modeline "1680x1050"x60.0 148.50 1680 2008 2052 2200 1050 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1680x1050"x59.9 148.35 1680 2008 2052 2200 1050 1084 1089 1125 +hsync +vsync (67.4 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1400x1050"x60.0 148.50 1400 2008 2052 2200 1050 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1400x1050"x59.9 148.35 1400 2008 2052 2200 1050 1084 1089 1125 +hsync +vsync (67.4 kHz e)
    [ 1826.294] (II) fglrx(0): Modeline "1600x900"x59.9 148.35 1600 1864 1908 2200 900 1004 1009 1125 +hsync +vsync (67.4 kHz ez)
    [ 1826.294] (II) fglrx(0): Modeline "1280x1024"x60.0 148.50 1280 2008 2052 2200 1024 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "1280x1024"x59.9 148.35 1280 2008 2052 2200 1024 1084 1089 1125 +hsync +vsync (67.4 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "1440x900"x59.9 148.35 1440 1864 1908 2200 900 1004 1009 1125 +hsync +vsync (67.4 kHz ez)
    [ 1826.295] (II) fglrx(0): Modeline "1280x960"x59.9 148.35 1280 1864 1908 2200 960 1004 1009 1125 +hsync +vsync (67.4 kHz ez)
    [ 1826.295] (II) fglrx(0): Modeline "1280x768"x59.9 148.35 1280 1864 1908 2200 768 1004 1009 1125 +hsync +vsync (67.4 kHz ez)
    [ 1826.295] (II) fglrx(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "1152x648"x50.0 74.25 1152 1592 1632 1980 648 653 658 750 +hsync +vsync (37.5 kHz ez)
    [ 1826.295] (II) fglrx(0): Modeline "1152x648"x59.9 74.18 1152 1262 1302 1650 648 653 658 750 +hsync +vsync (45.0 kHz ez)
    [ 1826.295] (II) fglrx(0): Modeline "800x600"x50.0 74.25 800 1720 1760 1980 600 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "800x600"x60.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "720x480"x50.0 74.25 720 1720 1760 1980 480 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "640x480"x50.0 74.25 640 1720 1760 1980 480 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 1826.295] (II) fglrx(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 1826.295] (II) fglrx(0): EDID for output CRT1
    [ 1826.295] (II) fglrx(0): Output DFP1 connected
    [ 1826.295] (II) fglrx(0): Output CRT1 disconnected
    [ 1826.295] (II) fglrx(0): Using exact sizes for initial modes
    [ 1826.295] (II) fglrx(0): Output DFP1 using initial mode 1280x720
    [ 1826.295] (II) fglrx(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 1826.295] (II) fglrx(0): Display dimensions: (1150, 650) mm
    [ 1826.295] (II) fglrx(0): DPI set to (28, 28)
    [ 1826.295] (II) fglrx(0): Adapter AMD Radeon HD 6530D has 2 configurable heads and 1 displays connected.
    [ 1826.295] (==) fglrx(0): PseudoColor visuals disabled
    [ 1826.295] (II) Loading sub module "ramdac"
    [ 1826.295] (II) LoadModule: "ramdac"
    [ 1826.295] (II) Module "ramdac" already built-in
    [ 1826.295] (==) fglrx(0): NoDRI = NO
    [ 1826.295] (==) fglrx(0): Capabilities: 0x00000000
    [ 1826.295] (==) fglrx(0): CapabilitiesEx: 0x00000000
    [ 1826.295] (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
    [ 1826.295] (==) fglrx(0): UseFastTLS=0
    [ 1826.295] (II) fglrx(0): Shadow Primary option: ShadowPrimary is enabled
    [ 1826.295] (--) Depth 24 pixmap format is 32 bpp
    [ 1826.295] Loading extension ATIFGLRXDRI
    [ 1826.295] (II) fglrx(0): doing swlDriScreenInit
    [ 1826.295] (II) fglrx(0): swlDriScreenInit for fglrx driver
    [ 1826.295] ukiDynamicMajor: found major device number 250
    [ 1826.295] ukiDynamicMajor: found major device number 250
    [ 1826.295] ukiDynamicMajor: found major device number 250
    [ 1826.295] ukiOpenByBusid: Searching for BusID PCI:0:1:0
    [ 1826.295] ukiOpenDevice: node name is /dev/ati/card0
    [ 1826.295] ukiOpenDevice: open result is 13, (OK)
    [ 1826.295] ukiOpenByBusid: ukiOpenMinor returns 13
    [ 1826.295] ukiOpenByBusid: ukiGetBusid reports PCI:0:1:0
    [ 1826.295] (II) fglrx(0): [uki] DRM interface version 1.0
    [ 1826.295] (II) fglrx(0): [uki] created "fglrx" driver at busid "PCI:0:1:0"
    [ 1826.295] (II) fglrx(0): [uki] added 8192 byte SAREA at 0x7a000
    [ 1826.295] (II) fglrx(0): [uki] mapped SAREA 0x7a000 to 0x7ff504c21000
    [ 1826.295] (II) fglrx(0): [uki] framebuffer handle = 0x7b000
    [ 1826.295] (II) fglrx(0): [uki] added 1 reserved context for kernel
    [ 1826.295] (II) fglrx(0): swlDriScreenInit done
    [ 1826.295] (II) fglrx(0): Kernel Module Version Information:
    [ 1826.295] (II) fglrx(0): Name: fglrx
    [ 1826.295] (II) fglrx(0): Version: 13.10.10
    [ 1826.295] (II) fglrx(0): Date: May 23 2013
    [ 1826.295] (II) fglrx(0): Desc: AMD FireGL DRM kernel module
    [ 1826.296] (II) fglrx(0): Kernel Module version matches driver.
    [ 1826.296] (II) fglrx(0): Kernel Module Build Time Information:
    [ 1826.296] (II) fglrx(0): Build-Kernel UTS_RELEASE: 3.9.9-1-ARCH
    [ 1826.296] (II) fglrx(0): Build-Kernel MODVERSIONS: yes
    [ 1826.296] (II) fglrx(0): Build-Kernel __SMP__: yes
    [ 1826.296] (II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
    [ 1826.296] (II) fglrx(0): [uki] register handle = 0x0007c000
    [ 1826.296] (II) fglrx(0): DRI initialization successfull
    [ 1826.296] (II) fglrx(0): FBADPhys: 0xf00000000 FBMappedSize: 0x0102c000
    [ 1826.297] (==) fglrx(0): Backing store disabled
    [ 1826.297] Loading extension FGLRXEXTENSION
    [ 1826.297] (**) fglrx(0): DPMS enabled
    [ 1826.297] (II) fglrx(0): Initialized in-driver Xinerama extension
    [ 1826.297] (**) fglrx(0): Textured Video is enabled.
    [ 1826.297] (II) LoadModule: "glesx"
    [ 1826.297] (II) Loading /usr/lib/xorg/modules/glesx.so
    [ 1826.298] (II) Module glesx: vendor="X.Org Foundation"
    [ 1826.298] compiled for 1.4.99.906, module version = 1.0.0
    [ 1826.298] Loading extension GLESX
    [ 1826.298] (II) fglrx(0): GLESX enableFlags = 592
    [ 1826.298] (II) fglrx(0): GLESX is enabled
    [ 1826.298] (II) LoadModule: "amdxmm"
    [ 1826.298] (II) Loading /usr/lib/xorg/modules/amdxmm.so
    [ 1826.298] (II) Module amdxmm: vendor="X.Org Foundation"
    [ 1826.298] compiled for 1.4.99.906, module version = 2.0.0
    [ 1826.324] Loading extension AMDXVOPL
    [ 1826.324] Loading extension AMDXVBA
    [ 1826.324] (II) fglrx(0): UVD feature is enabled(II) fglrx(0):
    [ 1826.326] (II) fglrx(0): Enable composite support successfully
    [ 1826.326] (WW) fglrx(0): Option "VendorName" is not used
    [ 1826.326] (WW) fglrx(0): Option "ModelName" is not used
    [ 1826.326] (II) fglrx(0): X context handle = 0x4
    [ 1826.326] (II) fglrx(0): [DRI] installation complete
    [ 1826.326] (==) fglrx(0): Silken mouse enabled
    [ 1826.326] (==) fglrx(0): Using HW cursor of display infrastructure!
    [ 1826.327] (II) fglrx(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    Last edited by EvanPurkhiser (2013-07-22 13:14:56)

    This was fixed by changing the "Pixel Format" in the catalyst control center to "RGB (Full RGB)".. Somehow it got changed to "YcBcr".
    I removed the /etc/ati/amdpcsdb file that the fglrx driver likes to put settings in and did a fresh reinstall of catalyst-test and everything looks good now. Really no idea how the pixel profile got changed. Also noticed that my resolution was much lower than it should have been (which for some reason doesn't affect XBMC which runs in native resolution no matter what?), but that was an easy fix of adding Mode "1920x1080" to my Display section in xorg.

  • Unsatisfactory E71 auto white balance, blue/purple...

    The E71's camera doesn't really shine with regard to automatic white balance. There's almost always some blue to purple tint. It seems to depend whether the "flash" was used and whether the camera is used in day or "night" mode. The other (non-auto) white balance modes usually don't match the actual lighting conditions too. Is it a deficient white-balance algorithm or is this tint just from the heavy noise in non-night mode? Is there any workaround (on the phone, not postprocessing on a PC) or fix, maybe it is improved in 200.x firmware? - Kolja

    Here:
    fw: 200.x
    Start camera as normal
    before capturing any picture,  set white balance to day light and press Ok
    After that set it back to automatic
    Purple tint is gone
    You must do it after capturing
    Nokia's guys please fix it

  • Apple, I have an iPhone 5 and the purple tint in pictures is real and is going to be the most costly mistake to have changed the lens to a sapphire crystal lens. This is HUGE! Why did you fix what is not broken?

    Why, because some clumsy, careless humans couldn't stop scratching a less that 1/4 inch wide lens?  That is no reason for replacing the lens and pandering to their inability to handle advanced technology is not going to push the technology forward. Tossing out cheap cases like you did for the imagined iPhone 4 antenna "problem" will not fix this VERY real problem. I have been a loyal customer since 2005 and this, as stated in the title, could be your most costly mistake. Either your software engineers are going to have to compensate for the purple tint appearing in photos or you're going to sacrifice massive profits to physically replace the lens in every iPhone 5 you have sold and continue to sell. I've read that Apple customer service has tried to sweep this away by falsely claiming that the purple tint is "normal". It is absolutely not normal by any stretch of the imagination. Do not be silent Apple customers! Let the complaints pour like Niagara Falls or settle for the garbage that has been sold.
    My former iPhone 4 took better pics.
    I hope Apple didn't do the same with the pending iPad mini or this could turn into a maelstrom that even Steve Jobs would not have tolerated.
    Signed,
    Extremely dissapointed

    Read: http://support.apple.com/kb/TS4436
    It is pretty short so here is the entire text:
    Symptoms
    A purplish or other colored flare, haze, or spot is imaged from out-of-scene bright light sources during still image or video capture.
    Resolution
    Most small cameras, including those in every generation of iPhone, may exhibit some form of flare at the edge of the frame when capturing an image with out-of-scene light sources. This can happen when a light source is positioned at an angle (usually just outside the field of view) so that it causes a reflection off the surfaces inside the camera module and onto the camera sensor. Moving the camera slightly to change the position at which the bright light is entering the lens, or shielding the lens with your hand, should minimize or eliminate the effect.
    Which is exactly what eelw wrote.
    No one on Apple Support Communities has authority to speak on behalf of Apple, unless their avatar is accompanied by this Apple image:
    ... identifying themselves as Apple employees.

  • Why are photos in pagemaker & PDF printing in solid blue?

    I publish a newsletter that I layout in Pagemaker 7.0. When I printed it out to proof, all the photos, color and B&W printed out in one solid bright blue block. Also some pieces of text were missing in the print out. Same thing happened when I printed out the PDF version. (Everything looked fine on the screen). Burned it on a CD and took it to the print shop and the photos were fine, no missing blocks of print. Now any new document I create, or if I go into an old one, make changes and save, all photos print in bright blue. No problems printing photos from preview or photoshop. My printer is an Espson stylus photo 1280. My non-mac son thinks it might be a corrupted printer driver, but I'm reluctant to download a new one for fear I won't be able to print anything if I screw it up. Any ideas?

    Is the colour profile of the files the same as that set in the printer driver?
    This article from Apple might be helpful:
    http://docs.info.apple.com/article.html?artnum=301175
    Last but by no means least are the Gutenprint drivers (which I use) which are superb and give you many more options than the original drivers:
    http://gimp-print.sourceforge.net/MacOSX.php3

  • Monitor occasionally takes a blue-green tint

    Why does my monitor occasionally, at very irregular times,  take on a blue green tint?
    It lasts from a few seconds to a few minutes, online and off.
    E. C. S.

    Hi,
    Welcome to the HP Forum!
    EverettCS wrote:
    Why does my monitor occasionally, at very irregular times,  take on a blue green tint?
    It lasts from a few seconds to a few minutes, online and off.
    E. C. S.
    It would help if you identified the display. locate the barcoded sticker on the back of the monitor and post the p/n that is there.
    To see if the monitor itself has issues remove it and connect another display to see if your PC duplicates the problem on the other monitor. The idea is to isolate the issue  for troubleshooting as either a monitor of video card problem. Alternately you can conect the monitor to another PC to accomplish the same effect.
    regards,
    erico
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • Using ID CS3 -- Can I change a B&W PDF to print in process blue?

    Would like to change a B&W PDF to print in process blue - is this possible?

    Huh. I was pretty sure it's tiff only, no psd - but then I ran a test and found that I could add a swatch to my test psd within InDesign. And I thought that it was bitmap-only, but I just saved an 8-bit greyscale tiff out of PS and colorized it without issue.
    (click click click)
    Aha! Back in 2009, Peter said that transparency prevents color-ize-ability of tiffs in ID. That'd be the explanation, I bet.

  • When I type documents in word they show black on the screen, black font is on but they print all in blue ink only.  help

    I am using word.  I type in black font, it shows black on the monitor but prints only in blue ink.  What is wrong? 

    You sure that the monitor isn't set to a color or darkness that doesn't make dark blue look like black?
    I would force the text color with Microsoft Word to black or automatic, and see if it makes a difference.  It should be obvious by the spectrum when you choose it what color it is using.  If it is not on the complete dark end of the spectrum, it could be picking dark blue.

  • What is that blue-purple line

    Hello,
    There is a wide blue-purple line running down the right side of my footage view in FCP. What is that? It isn't part of the footage, it is some UI thing. Can I make it go away?
    Thanks
    Bob

    Actually, it means you are AFTER the last frame in the sequence, meaning you have no more clips in the timeline. The bracket in the lower right corner means you're ON the last frame. The playhead sits BEFORE the frame you see, not after. The purpose of this is so that if you have a sequence that may possibly have a small clip WAY WAY down the line, that you thought you deleted while you were editing, you'll know it's there without having to FIT TO WINDOW the sequence. If you go to the intended end of your sequence (meaning you are snapped to the end of the clip), if you have no more footage, you'll see the last frame still, and you'll see the blue bar. If there is another frame down the line, you will see no blue bar and black instead of the frame.

  • What is the differnce between Blue,Purple and Orange Audio Tracks. Can you convert either to Green Midi Track?

    What is the differnce between Blue,Purple and Orange Audio Tracks. Can you convert either to Green Midi Track?

    Are you asking about Garageband? Your signature also mentions Logic, but I have never worked with that.
    Concerning Garageband:
    Real Instrument regions from your recordings are purple.
    Real Instrument regions from Apple Loops are blue.
    Regions from imported audio files are orange.
    Software Instrument regions from recordings, loops, and imported MIDI files are green.
    So far as I know you can convert software instrument loops to real instrument loops, but not real instrument loops to software instrument loops.

  • N8 purple tint issue

    Hi friends
    recently i observed purple tint on my n8 I've taken to Nokia care and shown my friends n8 along with mine for showing them the difference
    thEY realised it and taken my mobile to replace led after two days when i taken from them now it is showing black tint
    i don't know whether they replaced my display or tuned it
    what should i do?
    wamsy

    If a Nokia N8 (or Nokia C7) is determined by a Nokia Care point to have purple tint, the screen is replaced.
    Perhaps you could explain what you mean by "black tint"? Have you discussed your concerns with the NCP that carried out the work on your behalf?
    If this or any post answers your question, please remember to help others by pressing the 'Accept as solution' button.

  • HELP! Two new HTC Thunderbolts & one screen has a purple tint!

    So I just bought two HTC Thunderbolts, got them all set up and then realized that one has a purple tint!  I compared all the settings to the other phone and everything matched.
    The color was like this before any 3rd party applications were downloaded & the phone is not rooted or altered in any way.
    I've googled to try to find any calibration apps or if anyone else has this problem and have come out unsuccessful.  I know I can always perform a hard reset but wanted to see if there is any other alternate way to fix this issue.
    Thanks in advance for any help!

    Thanks for all the feed back!  Certainly is a strange issue for a brand new, out of the box phone.  I did in fact perform the master reset, went through the setup process, personalized the phone & long behold, the same issue. 
    Again, I compared the settings to the other Thunderbolt; Identical.  Tried different wallpapers, skins, themes and nothing has changed.
    Went through and checked for SW update, there was a firmware update that I did start.  After it was completed, same issue.
    I'm at a loss for what may be causing this.  I mean, it is bothersome that EVERYTHING on the screen has a purple tint... 
    I'm not 100% sure that this is a "warranty" issue?  Maybe it's something AraceliT_VZW can answer for me? 
    Thanks for all the help!

  • LCD as second screen has purple tint!! Help!!

    Hello all,
    I have just connected a 19" LCD screen to my iBook 14" through the DVI adapter that came with my mac. While the iBook has instantaneously mirrored my desktop, the LCD screen has a heavy purple tint on it. The screen on my iBook is still fine but the LCD screen is unworkable. Everything appears on it, its just heavily purple-ised. Does anyone know why this is, and what I can do about it?
    Any help greatly appreciated
    regards,
    Glen Kristensen

    Sorry, my mistake, the LCD screen I am using as a second screen is 17" not 19". I Have tried on another screen (but the same model) so I am sure the problem is with the iBook. I don't really see why the iBook underpowering the external screen would make it turn purple. Let me just clarify, the screen is displaying everything crystal clearly, the only problem is that there is a purple hue or tint over everything. So for example the colour white isn't white on the second screen but purple.

Maybe you are looking for

  • Changes in Demand Forecast after its final release.

    Hi We are releasing final forecast of next month in the mid of previous month (e.g. on 15th Jan we will release final forecast of Feb ) to SNP. Then in Feb'09 can we make chhanges in Forecast because in Feb'09 the feild is grey out and also it is not

  • Upgrade from 4.7C to ECC 6.0

    Hi Gurus,               I am going to do a functional upgrade from 4.7C to ECC 6.0 (classic GL, not new GL). Can someone please list me the steps that I need to do to achieve the upgrade. I would be very grateful and would assign points as a gesture

  • Restoring old data onto new iPhone 4S

    I had an iPhone 4 and just got the 4S, but when I plugged the 4S into my mac it registered as a new phone and didn't ask to restore it from my old one. How do I get my old data on this new phone?

  • Remote Mail Error

    Hi there, We are getting error messages in SOST and some of the emails are not going out. The error messages is "Cannot process message, no route from USERNAME to SID:500:USERNAME". This client on that SID is used for CUA purposes and the connection

  • BPM Need Help ASAP

    hi all, Im doinga ccBPM. this BPM receive data from a WS>JDBC>JDBC-->WS that means i send a request from WS, open a S/A bridge> map the ws request to a SP-> the SP send me a response like this <resp> .....<route> ..........<xxxx> ..........<xxxx> ...