1004 when using mx_internal

I'm trying to use mx_internal to override changeHighlightedSelection in a DropDownList subclass.  I've imported the namespace and used it, but FlashBuilder's complaining:
1004: Namespace was not found or is not a compile-time constant.
override mx_internal function changeHighlightedSelection(newIndex:int, scrollToTop:Boolean=false):void
Is there something I'm missing to make this work?
Thanks

This sounds like a compiler bug. It should have been OK to put the 'use namespace mx_internal' directive inside the class. If you could reduce this problem to a simple case and file a bug, that would be very helpful.
Gordon Smith
Adobe Flex SDK Team

Similar Messages

  • [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.

  • Sy-tabix when using secondary key

    Hi,
    I have an internal table with records that contain a field with the line index of another table entry that they depend on.
    I can process this table recursively, by passing the parent index inside and using a
    LOOP AT ... USING KEY secondary_key WHERE index = iv_index.
    Unfortunately the sy-tabix is afterwards not correct, it contains the position in the secondary key probably instead the position in the internal table.
    Is there a way how I could find out the current table index, when using a secondary key to read a record?
    Regards,
    Bruno

    I rewrote it to include the row index also, not only the dependency.. was thinking too generic

  • Often lose wireless connection when using HDTV as monitor

    I have an unusual wireless networking problem when using my Samsung HDTV in my living room as a monitor for my MacBook (when watching Internet TV shows, for example). Frequently when I switch URLs, networking freezes, even though the connection appears strong, with the Airport symbol at the top of my screen showing all bars. To re-establish the wireless connection, I have to go through the process of re-joining my network through the “Join Other Network" option. The signal holds as long as I don’t try to change it, as in selecting another URL.
    I connect to my HDTV via HDMI cable, using a mini-DVI to HDMI adapter from my Macbook’s video-out port. The audio connection is a mini-plug from the Mac’s headphone out jack to stereo RCA plugs associated with the TV’s HDMI port.
    The wireless connection is through a Lynksys Wireless-G 2.4 Ghz, 54 Mpbs Broadband router.
    I’d appreciate any solutions the Apple user community has to offer.

    I'd say this has nothing to do with your display. The problem will likely lie in either your router settings, network settings or a simple signal strength issue. Try first changing the broadcast channel on your router, and make sure all settings are correct for your desired network.

  • Since installing LTR 5.4, which I've now upgraded to 5.6, I've encountered repeated slowness and malfunctions in operations, especially when using the Compare View function and the Tab key to open and close the right and left side panels.  Such problems n

    Since installing LTR 5.4, which I've now upgraded to 5.6, I've encountered repeated slowness and malfunctions in operations, especially when using the Compare View function and the Tab key to open and close the right and left side panels.  Such problems never arose during two years of using LTR-4 and nothing else has changed on my computer.  I have a pretty simple system with only a few plug-ins, which are usually not in operation.  I have 12GB of RAM in my Windows 7 PC.  I could illustrate these problems with screen shots if you would tell me how to submit screen shots.  Otherwise I will try to describe the problems in words.
    The problem is clearly cumulative, growing worse as usage time passes.  Compare View feature gradually slows down and eventually seems to choke as my work session proceeds. If I Exit LTR and re-enter and start all over, things will work normally for maybe 30 minutes, but then the Compare View feature begins to become very slow to respond.   In a recent example with my screen full of thumbnails in Library mode I highlighted two images to compare. LTR started to open the Compare View screen by first having the top row of thumbnails disappear to be replaced by the "SELECT" and "CANDIDATE" words in their spaces  (but no images), but Compare View never succeeded in gaining control of the screen. After some seconds the top row of thumbnails reasserted its position and the Compare View windows disappeared. But LTR kept trying to bring them back. Again the top row of thumbnails would go away, Select and candidate would reappear, try again, and give up. This went on for at least 2-3 minutes before I tried to choose File and Exit, but even that did not initially want to respond. It doesn't like to accept other commands when it's trying to open Compare View. Finally it allowed me to exit.
    To experiment I created a new catalog of 1100 images.  After 30-40 minutes, the Compare View function began to operate very slowly. With left and right side panels visible and two thumbnails highlighted, hitting Compare View can take half a minute before the two mid-size  images open in their respective SELECT and CANDIDATE windows. When the side panels are open and two images are in the Select/Candidate spaces, hitting the Tab button to close the side panels produces a very delayed response--25-30 seconds to close them, a few more seconds to enlarge the two images to full size. To reverse the process (i.e., to recall the two side panels), hitting Tab would make the two sides of the screen go black for up to a minute, with no words visible. Eventually the info fields in the panels would open up.
    I also created a new user account and imported a folder of 160 images. After half an hour Compare View began mis-placing data.  (I have a screen shot to show this.)  CANDIDATE appears on the left side of SELECT, whereas it should be on the right. The accompanying camera exposure data appears almost entirely to the left of the mid-screen dividing line. Although the Candidate and Select headings were transposed, the image exposure data was not, but the data for the image on the right was almost entirely to the left of the line dividing the screen in two.
    Gurus in The Lightroom Forum have examined Task Manager data showing Processes running and Performance indicators and they see nothing wrong.  I could also send screen shots of this data.
    At this point, the only way I can process my images is to work 30-40 minutes and then shut down everything, exit, and re-start LTR.  This is not normal.  I hope you can find the cause, and then the solution.  If you would like to see my screen shots, tell me how to submit them.
    Ollie
    [email protected]

    Since installing LTR 5.4, which I've now upgraded to 5.6, I've encountered repeated slowness and malfunctions in operations, especially when using the Compare View function and the Tab key to open and close the right and left side panels.  Such problems never arose during two years of using LTR-4 and nothing else has changed on my computer.  I have a pretty simple system with only a few plug-ins, which are usually not in operation.  I have 12GB of RAM in my Windows 7 PC.  I could illustrate these problems with screen shots if you would tell me how to submit screen shots.  Otherwise I will try to describe the problems in words.
    The problem is clearly cumulative, growing worse as usage time passes.  Compare View feature gradually slows down and eventually seems to choke as my work session proceeds. If I Exit LTR and re-enter and start all over, things will work normally for maybe 30 minutes, but then the Compare View feature begins to become very slow to respond.   In a recent example with my screen full of thumbnails in Library mode I highlighted two images to compare. LTR started to open the Compare View screen by first having the top row of thumbnails disappear to be replaced by the "SELECT" and "CANDIDATE" words in their spaces  (but no images), but Compare View never succeeded in gaining control of the screen. After some seconds the top row of thumbnails reasserted its position and the Compare View windows disappeared. But LTR kept trying to bring them back. Again the top row of thumbnails would go away, Select and candidate would reappear, try again, and give up. This went on for at least 2-3 minutes before I tried to choose File and Exit, but even that did not initially want to respond. It doesn't like to accept other commands when it's trying to open Compare View. Finally it allowed me to exit.
    To experiment I created a new catalog of 1100 images.  After 30-40 minutes, the Compare View function began to operate very slowly. With left and right side panels visible and two thumbnails highlighted, hitting Compare View can take half a minute before the two mid-size  images open in their respective SELECT and CANDIDATE windows. When the side panels are open and two images are in the Select/Candidate spaces, hitting the Tab button to close the side panels produces a very delayed response--25-30 seconds to close them, a few more seconds to enlarge the two images to full size. To reverse the process (i.e., to recall the two side panels), hitting Tab would make the two sides of the screen go black for up to a minute, with no words visible. Eventually the info fields in the panels would open up.
    I also created a new user account and imported a folder of 160 images. After half an hour Compare View began mis-placing data.  (I have a screen shot to show this.)  CANDIDATE appears on the left side of SELECT, whereas it should be on the right. The accompanying camera exposure data appears almost entirely to the left of the mid-screen dividing line. Although the Candidate and Select headings were transposed, the image exposure data was not, but the data for the image on the right was almost entirely to the left of the line dividing the screen in two.
    Gurus in The Lightroom Forum have examined Task Manager data showing Processes running and Performance indicators and they see nothing wrong.  I could also send screen shots of this data.
    At this point, the only way I can process my images is to work 30-40 minutes and then shut down everything, exit, and re-start LTR.  This is not normal.  I hope you can find the cause, and then the solution.  If you would like to see my screen shots, tell me how to submit them.
    Ollie
    [email protected]

  • How can I show only text edits and not text formatting when using print comments summary?

    Acrobat 9.3.0 for Mac.
    Here is the scenario: I used the Compare command to see the changes between 2 PDFs. The resulting file some edits are inserts and some are deletions. I want to print a comments summary only showing the text edits. In the Compare Option pane, I select Text and deselect Images, Annotations, Formatting, Headers/Footers, and Backgrounds. Now on the screen I see inserts are highlighted in blue and deletions are marked with sort of a caret and vertical bar symbol. So all looks good at this point. However, when I show the Comments List, I see addtional comments that indicate "Replace - The following text attributes were changed: fill color." Those comments do not appear in the page view unless I check the Formatting check box to show them. With Formatting unchecked, I print a comments summary and all of the "Replace - Fill Color" comments" appear on the resulting comments summary.
    I only want to show text edits, not text formatting changes. So questions are:
    1. Why, when the Formatting checkbox is unchecked, do the text formatting comments still appear in the comments list when they do not appear on the page display.
    2. How can I print only the text content edits and not show the text formatting changes when using Print Comments Summary.

    Hi,
    You can set ExecuteWithParams as default activity in the task flow then method activity to return total no of rows passing to Router activity if your method has value 0 then call Create insert operation else do directly to page.
    Following idea could be your task flow
    Execute With param (default) > SetCurrentRowWithKey > GetTotalNoOfRows (VOImpl Method)
    |
    v
    Router
    1. If pageFlowScope outcome is 0 then call CreateInsert > MyPage
    2. if pageFlowScope outcome > 0 then MyPage
    hope it helps,
    Zeeshan

  • I have a new MAcBook Air and my photos don't fit on the internal hard drive.  I want to store my photos on an external hard drive which I will connect to my Air when using Iphoto.  How do I set an external hard drive as the default drive?

    I have a new MAcBook Air and my photos don't fit on the internal hard drive.  I want to store my photos on an external hard drive which I will connect to my Air when using Iphoto.  How do I set an external hard drive as the default drive in Iphoto?

    Make sure the drive is formatted Mac OS Extended (Journaled)
    1. Quit iPhoto
    2. Copy the iPhoto Library from your Pictures Folder to the External Disk.
    3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
    4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
    Regards
    TD

  • Why when using Adobe Bridge,  I apply a star rating,  the rating does not show up in Photoshop Elements? [tags]

    Why when using Adobe Bridge,  I apply a star rating,   the rating does not show up in Photoshop Elements.  I use Elements as my organizer and Bridge to view as it is much more user friendly.  Anyone any solutions??

    Most likely you have set the wrong file as the external editor. You don't want the obvious one; that's just a link to the welcome screen. Go back and choose this one, which is hidden away inside the folder Support Files:

  • Adobe Photoshop CS4/5 Crashes when using the Move Tool

    Hello. I'm here because I'm having an issue with Photoshop.
    I was trying out CS5 when it started to crash every time I tried to use the Move Tool. It was the generic error message: "Adobe Photoshop CS4 has stopped working.
    A problem has caused Adobe Photoshop CS4 to stop working correctly. Windows will close the program and notify you if a solution is available."
    Thinking that it was a CS5 issue, I went back to my copy of CS4, only to find the same thing happening there (I also downgraded because CS5 was also crashing at other random times for some reason, but that's an issue for another time).
    This puzzles me because both were working fine before. Granted, I hadn't opened them for a while, but it was a sudden thing.
    My first impulse was to uninstall and reinstall CS4. No luck. So then, I uninstalled all third-party plugins, thinking that might be it. Still, the same problem. I started looking around on Google for solutions and found the instructions on resetting the Tool preferences (I chose to reset the preferences for ALL of the tools). When that didn't work, I tried deleting the preferences file outright, which said instructions recommended. Nothing.
    I should note that Photoshop crashes when using the Move Tool to move an object without ant lines around it, i.e., a layer. I'll move the object, and after two to three seconds, the mentioned error message will appear and Windows will close Photoshop. This, however, only seems to happen after selecting, copying, and pasting part of a large object with some variation of the Marqee Tool (thus making that part a new layer by default) while working at a zoom of 100%. So, in short, working with a large image like <a href=http://www.wallpaper4me.com/images/wallpapers/ergo_proxy_267_1280-862301.jpeg>This</a> at 100% zoom. The image linked is the image that I was using and am currently using to reproduce the problem. It is 1280x1024 pixels. I have tested this with somewhat smaller, yet comparable images too. Same problem. I have never had this problem working with large images before, and I wonder if anyone has any suggestions short of formatting my hard drive.
    The error code, from Event Viewer:
    Faulting application name: Photoshop.exe, version: 11.0.2.0, time stamp: 0x4bf2d4f6
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x65637275
    Faulting process id: 0xe28
    Faulting application start time: 0x01cb2bb3471d87bf
    Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CS4\Photoshop.exe
    Faulting module path: unknown
    Report Id: b412e368-97ab-11df-8f49-001d60b646ef
    Details:
    System
    Provider
    [  Name]
    Application  Error
    EventID
    1000
    [  Qualifiers]
    0
    Level
    2
    Task
    100
    Keywords
    0x80000000000000
    TimeCreated
    [  SystemTime]
    2010-07-25T05:15:57.000000000Z
    EventRecordID
    78845
    Channel
    Application
    Computer
    Gatherum
    Security
    EventData
    Photoshop.exe
    11.0.2.0
    4bf2d4f6
    unknown
    0.0.0.0
    00000000
    c0000005
    65637275
    e28
    01cb2bb3471d87bf
    C:\Program  Files\Adobe\Adobe Photoshop CS4\Photoshop.exe
    unknown
    b412e368-97ab-11df-8f49-001d60b646ef
    Details in XML View:
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-07-25T05:15:57.000000000Z" />
    <EventRecordID>78845</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Gatherum</Computer>
    <Security />
    </System>
    - <EventData>
    <Data>Photoshop.exe</Data>
    <Data>11.0.2.0</Data>
    <Data>4bf2d4f6</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>65637275</Data>
    <Data>e28</Data>
    <Data>01cb2bb3471d87bf</Data>
    <Data>C:\Program Files\Adobe\Adobe Photoshop CS4\Photoshop.exe</Data>
    <Data>unknown</Data>
    <Data>b412e368-97ab-11df-8f49-001d60b646ef</Data>
    </EventData>
    </Event>
    System Specifications:
    Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7600)
    System Manufacturer: HP-Pavilion
    System Model: GN697AA-ABA a6214x
    Processor: Intel Pentium Dual CPU E2160 @ 1.80 GHz (2 CPUs)
    Memory: 2048MB RAM
    DirectX Version: DirectX 11
    Display Device:
    Name: NVIDIA GeForce 8600 GTS
    Manufacturer: NVIDIA
    DAC Type: Integrated RAMDAC
    Approx. Total Memory: 1010 MB
    Current Display Mode: 1440 x 900 (32 bit) (60 Hz)
    Photoshop Version: CS4 Extended 11.0.2

    Even a decent RAM upgrade is usually only a few hundred dollars nowadays, but it's not a trivially simple process.  That said, with a little research and care you can do it.  Alternatively, you can hire people (e.g., "Geek Squad") to do such an upgrade.
    First, you'll need to know what your operating system capacity is.  For example, a 32 bit Windows system can really only use up to a bit more than 3 GB of RAM, while a 64 bit Windows system can use all the RAM you can find a place to plug in.  What version of Windows are you running?
    Then you'll need to determine what RAM you have installed and what your computer's maximum RAM capacity is - usually you can do this through internet research, either by visiting your computer manufacturer's web site or doing google searches.  There are even RAM manufacturer web sites that will tell you what kind of RAM your computer needs and suggest sources, for example:
    http://www.kingston.com/
    It may be that you can just plug additional chips into currently empty sockets, or it is possible you'll need to replace the RAM chips you have installed in your computer to make room for an upgrade.  Every computer is different.
    If you list your computer model and current RAM that you have installed here, it may be that someone can help with more specific advice.
    -Noel

  • When using the camera downloader in Adobe Bridge CS6 with Nikon D5200 we are unable to see previews of the photos and it is very slow to download. The issue occurs under a the users rights, but not under admin level. This is a new issue

    When using the camera downloader in Adobe Bridge CS6 with Nikon D5200 we are unable to see previews of the photos and it is very slow to download. The issue occurs under a the users rights, but not under admin level. This is a new issue.

    Hi Jdentremont,
    Lync client gets user photos by first querying the Address Book Web Query (ABWQ) service on the server, which is exposed through the Distribution List Expansion web service. The client receives
    the image file and then copies it to the user's cache to avoid downloading the image each time it needs to be displayed. The attribute values returned from the query are also stored in the cached Address Book Service entry for the user. The Address Book Service
    deletes all cached images every 24 hours, which means that it can take up to 24 hours for new user images to be updated in the cache on the server.
    To troubleshoot your problem, please follow the steps below:
    1.  Navigate to
     “X:\share\1-WebServices-1\ABfiles\000000000\000000000” folder. (ABS file share)
    You should see some photo files in this folder as the following screenshot.
    2. Delete all the files in this folder.
    3. On test PC, delete local cache files.
    %userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]
    4. Sign-in Lync with the test account.
    5. Go back to the ABS file share, check if there is any Photo file in the folder.
    Best regards,
    Eric
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Photoshop CS4 "Program Error" when using Text tool

    Hello. I was having problems with Photoshop displaying a "Program Error" every so often, so I deleted the preference file and all seemed good. But after deleting the preference file for my Photoshop CS4 and re-launching Photoshop, the text tool causes Photoshop to display a Program Error when using the tool. It never did this before. Should I reinstall Photoshop? I am using a Powermac G5 running 10.5.8. I have already tried repairing the disk permissions.
    Thanks

    Thats kinda what I thought too, but the problem started happening randomly. It started when we were trying to use photomerge with large photos. The program just started giving the program errors. I still think it may be a font problem, but without going through my 2000+ fonts and disabling them one by one, how can I resolve this issue?
    Thanks

  • Unable to insert date and time when using date datatype

    Hi
    I am hitting a bit of a problem when using the date datatype. When trying to save a row to the table where the field it throws an error ora 01830 and complains about converting the date format picture ends...etc. Now when I do the insert, I use the to_date function with the format of "dd-mon-yyyy hh24:mi:ss". Of course, when I remove the time element, everything is perfect.
    Checking sysdate, I noticed that the time element wasn't be displayed, and I used alter session set nls_date_format to set the date and time I want to save to the table, which worked!
    Then based on advice in a previous thread to permanently fix the problem, I used alter system set nls_date_format ="dd-mon-yyyy hh24:mi:ss" scope=spfile; This showed that it was altered, and I can see the setting in the em. In sqlplus, I shutdown the database, and restarted with startup mount; alter database open; and then selecting sysdate, it still shows the date as dd-mon-yy, and still no time! Checking the em, and looking up the nls_date_format the setting is still shown as "dd-mon-yyyy hh24:mi:ss".
    So, my question is this - what am I doing wrong? Why can't save date and time using date in Oracle 11g?????
    Thanks

    user633278 wrote:
    Hi
    I am hitting a bit of a problem when using the date datatype. When trying to save a row to the table where the field it throws an error ora 01830 and complains about converting the date format picture ends...etc. Now when I do the insert, I use the to_date function with the format of "dd-mon-yyyy hh24:mi:ss". Of course, when I remove the time element, everything is perfect.
    Checking sysdate, I noticed that the time element wasn't be displayed, and I used alter session set nls_date_format to set the date and time I want to save to the table, which worked!
    Then based on advice in a previous thread to permanently fix the problem, I used alter system set nls_date_format ="dd-mon-yyyy hh24:mi:ss" scope=spfile; This showed that it was altered, and I can see the setting in the em. In sqlplus, I shutdown the database, and restarted with startup mount; alter database open; and then selecting sysdate, it still shows the date as dd-mon-yy, and still no time! Checking the em, and looking up the nls_date_format the setting is still shown as "dd-mon-yyyy hh24:mi:ss".
    So, my question is this - what am I doing wrong? Why can't save date and time using date in Oracle 11g?????
    ThanksYou most certainly can save the time. A DATE column, by definition stores date and time. What you describe is a presentation problem, and setting nls_date_format at the system as an init parm is the weakest of all settings as it is overridden by several other locations.
    without seeing the exact sql that produced the error (not just your description of what you think you were doing) it is impossible to say for sure.
    However, I'd suggest you read http://edstevensdba.wordpress.com/2011/04/07/nls_date_format/

  • Live! Cam Voice Shuts Down When Using Motion Detection Feature

    I'm running XP Media Center 2002.
    I just installed Live! Cam Voice. Started using it and is was fine out of the box. I updated the drivers and i also decided to update the drivers for my SoundBlaster Audigy 2 ZS.
    The problem only seemed to occur when using the Motion Detection. Shortly after using it, I'd get a Microsoft error prompting the WebCam Center to shut down.
    First I uninstalled the software and reinstalled it using the original drivers on the supplied disk. I still had the problem. So i rolled back the drivers on my sound card. That seems to have fixed the problem... Thought you'd want to know.
    To be clear the Cam driver I'm using is .0.8.206. I believe this is the one that came w/ the install disk. Hope this helps anyone else who's experienced similar problems.....

    I have the same problem. I only get 6-7 fps max. I've never seen anything above 0 fps which is a disgrace. My computer is and Athlon64 X2 4800 with 2GB RAM so it's nothing to do with spec. This behaviour was the same in driver version .0.8 as well as the latest one... .0.02 or something.
    Also, since the last driver update, the whitebalance and focus when on automatic is dreadful. I'm not impressed.

  • Machine freezez/lock ups when using password protected certificates in IE 11 Windows 8.1 Pro

    When using certificates that have a password enabled and private keys we find the machine hangs up competly with the memory usage jumping to 99%. The main process being the Local Secuirty Authority Process that causes the machine to lock up. The work
    around we have is to remove this certificate and import a new certificate making sure we un-tick the check box for private key password.
    Not sure if this
    KB2813237 is linked, but this hotfix is available for Windows 8.1 Pro OS.

    Hi  Simon,
    You can try that suggestion and check whether it is solved and give your result, if there is any other issue, you can post it back.
    Regards
    Wade Liu
    TechNet Community Support

  • Using smart previews on iMac to control two sets of identical original files on two external drives --- render previews setting when using smart previews

    I’m just getting started with Lightroom and if someone can help me I’ll be very appreciative.
    I’m using an iMac with a 1TB drive and two external 2.5 TB drives for backup.  My active files are on all three drives and I’m running out of room on the iMac drive.
    With the smart previews capability of Lightroom 5, I’m hoping to remove all the active files from the iMac drive.  I hope to import existing images into the LR catalog from two identical drives with identical folders and have both sets of images reflect the changes I make using smart previews on my iMac.
    I just created two identical test folders of junk images on the external drives and was following a beginners tutorial on importing. However, I see nothing about using smart previews on my iMac that, when connected, will update more than one external drive at the same time.
    I’m also wondering if, when using smart previews, it matters how I set the render previews during the import process.
    Many thanks for any help,
    Karl Hentz

    I don't see any way to use smart previews to update both external drives at the same time. The smart previews are linked to a specific set of images. But it seems to me that if both drives are in fact identical, once the catalog is updated when one of those drives is connected those changes should also apply to the files on the other drive. It's actually the catalog that gets updated, not the images.  Smart previews and regular import previews are completely unrelated. How you have your import previews configured will have no effect on your smart previews.
    Incidentally, in order for my suggestion to work it would be necessary to only have one of those external drives connected. And when the other EHD is connected it would have to have the same drive letter or name. In other words it would have to appear to the iMac that it is precisely the same drive.

Maybe you are looking for