Cure Your Errors

Fix Windows Errors & Optimize Your System

Windows/Mac OS/Linux
Support Guide

Home

Video transfer from Lumia 520 to PC

How do I transfer video files from my Lumia 520 onto my computer without a cable or what do I do after uploading on Skydrive ?

If you have Windows 8 or later, you can see your OneDrive folders in WIndows Explorer, otherwise log in to https://onedrive.live.com/ using your Microsoft Account credentials.

Solution

1. Download & Run DLLEscort - Download Now

2. Click 'Start Scan' to analyze your System.

3. Click 'Fix Errors' and you're done!

 

Related Content

V_NL Net price report problem


VZW to VZW text messages have call back number in every message after Tango update


VZW Customer NO MORE After 8-1/2 Years


VZW Access manager freezing MacBook Pro


VZ Contact Transfer will not work on Wi-Fi; Synch with iTunes sets up mail


VXML for Flash, please help


VXC 2100 series over VPN


VWLC + ISE 1.2 = Randomly won't authenticate users until reboot?


VWIC is showing as "WIC module not supported/disabled in this slot"


VW WIFI Auto-On No Longer Works


VV501 error in Posting Goods Issue (VL02N)


VTS,VOB,IFO,BUP  VIDEO files wont play on Mac???


vtml_speed tag not functioning correctly in 5.5


VTML-Tags for text-to-speech do not work in Captivate 6 - are they working in Cap. 7 again?


VT03N Output could not be issued (VW086)


VT02n : User Exit (Urgent)


VT02N - do PGI and Invoice for certain deliveries either based on certain conditions


VT advantage not being recognized by windows xp


VSTS loadtest error while running Loadtest with Runsettings as No of test iterations , ERROR is : could not read result repository: unknown transaction id in results:


VSTO development outlook plugin how to get the full storage path attachment send mail attachments added


I have a Vizio Smart TV and just over the last couple of days I cannot seem to get it to stay connect to my Linksys e1200 router.  I will start a movie on Netflix and it will play for about 10 minutes and then disconnect.  I talked to somebody in Cisco Linksys Customer support and they said that the problem had something to do with IP Addresses.  I have no idea what he was talking about.  All I know is last week I could watch an entire movie without losing connection and this week it only stays connect for 10 minutes and then I have to turn the TV off to re-connect. 
Ideas?
Thanks

Using Arch x86_64
Nvidia 450 GTS
Nvidia 430 GT
So I am trying to output to my Vizio 37" HDTV via HDMI on my 450 GTS, but I always get the error "Not Support!" displayed on my TV. I have 3 monitors configured in nvidia-settings, all 3 are in the "separate X screens" configuration. I have an Acer 23" (DVI) and the Vizio on my 450 GTS and I have a 19" LG (also DVI) on my 430 GT.
I have been able to get this working easily on past distros (ubuntu) but I fear this may have something do with the newer Xorg version from Arch, but I am not sure and would like to work around it if i can. Here is my Xorg.0.log file:
[ 11.961]
X.Org X Server 1.11.3
Release Date: 2011-12-16
[ 11.961] X Protocol Version 11, Revision 0
[ 11.961] Build Operating System: Linux 3.1.5-1-ARCH x86_64
[ 11.961] Current Operating System: Linux TeetoArch 3.2.2-1-ARCH #1 SMP PREEMPT Thu Jan 26 08:40:20 CET 2012 x86_64
[ 11.961] Kernel command line: root=/dev/disk/by-uuid/a581f4d1-b664-4b00-832b-7ad7323d7e0e ro
[ 11.961] Build Date: 17 December 2011 09:17:41AM
[ 11.961]
[ 11.961] Current version of pixman: 0.24.2
[ 11.961] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 11.961] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 11.961] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 2 01:51:52 2012
[ 11.971] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 11.984] (==) ServerLayout "Layout0"
[ 11.984] (**) |-->Screen "Screen0" (0)
[ 11.984] (**) | |-->Monitor "Monitor0"
[ 11.984] (**) | |-->Device "Device0"
[ 11.984] (**) |-->Screen "Screen1" (1)
[ 11.984] (**) | |-->Monitor "Monitor1"
[ 11.984] (**) | |-->Device "Device1"
[ 11.984] (**) |-->Screen "Screen2" (2)
[ 11.984] (**) | |-->Monitor "Monitor2"
[ 11.984] (**) | |-->Device "Device2"
[ 11.984] (**) |-->Input Device "Keyboard0"
[ 11.984] (**) |-->Input Device "Mouse0"
[ 11.984] (**) Option "Xinerama" "0"
[ 11.984] (==) Automatically adding devices
[ 11.984] (==) Automatically enabling devices
[ 12.021] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 12.021] Entry deleted from font path.
[ 12.030] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 12.030] Entry deleted from font path.
[ 12.030] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 12.030] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 12.030] Entry deleted from font path.
[ 12.030] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 12.030] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 12.030] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 12.030] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 12.030] (WW) Disabling Keyboard0
[ 12.030] (WW) Disabling Mouse0
[ 12.030] (II) Loader magic: 0x7ccae0
[ 12.030] (II) Module ABI versions:
[ 12.030] X.Org ANSI C Emulation: 0.4
[ 12.030] X.Org Video Driver: 11.0
[ 12.030] X.Org XInput driver : 13.0
[ 12.030] X.Org Server Extension : 6.0
[ 12.031] (--) PCI:*(0:1:0:0) 10de:0dc4:10de:085a rev 161, Mem @ 0xf4000000/16777216, 0xe0000000/134217728, 0xec000000/33554432, I/O @ 0x0000ef00/128, BIOS @ 0x????????/524288
[ 12.031] (--) PCI: (0:2:0:0) 10de:0de1:10de:0828 rev 161, Mem @ 0xf9000000/16777216, 0xd0000000/134217728, 0xde000000/33554432, I/O @ 0x0000df00/128, BIOS @ 0x????????/524288
[ 12.031] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 12.031] (II) LoadModule: "extmod"
[ 12.043] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 12.051] (II) Module extmod: vendor="X.Org Foundation"
[ 12.051] compiled for 1.11.3, module version = 1.0.0
[ 12.051] Module class: X.Org Server Extension
[ 12.051] ABI class: X.Org Server Extension, version 6.0
[ 12.051] (II) Loading extension MIT-SCREEN-SAVER
[ 12.051] (II) Loading extension XFree86-VidModeExtension
[ 12.051] (II) Loading extension XFree86-DGA
[ 12.051] (II) Loading extension DPMS
[ 12.051] (II) Loading extension XVideo
[ 12.051] (II) Loading extension XVideo-MotionCompensation
[ 12.051] (II) Loading extension X-Resource
[ 12.051] (II) LoadModule: "dbe"
[ 12.051] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 12.051] (II) Module dbe: vendor="X.Org Foundation"
[ 12.051] compiled for 1.11.3, module version = 1.0.0
[ 12.051] Module class: X.Org Server Extension
[ 12.051] ABI class: X.Org Server Extension, version 6.0
[ 12.051] (II) Loading extension DOUBLE-BUFFER
[ 12.051] (II) LoadModule: "glx"
[ 12.051] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 12.407] (II) Module glx: vendor="NVIDIA Corporation"
[ 12.415] compiled for 4.0.2, module version = 1.0.0
[ 12.415] Module class: X.Org Server Extension
[ 12.415] (II) NVIDIA GLX Module 290.10 Wed Nov 16 18:01:24 PST 2011
[ 12.415] (II) Loading extension GLX
[ 12.415] (II) LoadModule: "record"
[ 12.415] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 12.426] (II) Module record: vendor="X.Org Foundation"
[ 12.426] compiled for 1.11.3, module version = 1.13.0
[ 12.426] Module class: X.Org Server Extension
[ 12.426] ABI class: X.Org Server Extension, version 6.0
[ 12.426] (II) Loading extension RECORD
[ 12.426] (II) LoadModule: "dri"
[ 12.426] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 12.442] (II) Module dri: vendor="X.Org Foundation"
[ 12.442] compiled for 1.11.3, module version = 1.0.0
[ 12.442] ABI class: X.Org Server Extension, version 6.0
[ 12.442] (II) Loading extension XFree86-DRI
[ 12.442] (II) LoadModule: "dri2"
[ 12.442] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 12.443] (II) Module dri2: vendor="X.Org Foundation"
[ 12.443] compiled for 1.11.3, module version = 1.2.0
[ 12.443] ABI class: X.Org Server Extension, version 6.0
[ 12.443] (II) Loading extension DRI2
[ 12.443] (II) LoadModule: "nvidia"
[ 12.443] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 12.503] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 12.504] compiled for 4.0.2, module version = 1.0.0
[ 12.504] Module class: X.Org Video Driver
[ 12.513] (II) NVIDIA dlloader X Driver 290.10 Wed Nov 16 17:41:10 PST 2011
[ 12.513] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 12.513] (++) using VT number 7
[ 12.516] (II) Loading sub module "fb"
[ 12.516] (II) LoadModule: "fb"
[ 12.516] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 12.521] (II) Module fb: vendor="X.Org Foundation"
[ 12.521] compiled for 1.11.3, module version = 1.0.0
[ 12.521] ABI class: X.Org ANSI C Emulation, version 0.4
[ 12.521] (II) Loading sub module "wfb"
[ 12.521] (II) LoadModule: "wfb"
[ 12.521] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 12.532] (II) Module wfb: vendor="X.Org Foundation"
[ 12.532] compiled for 1.11.3, module version = 1.0.0
[ 12.532] ABI class: X.Org ANSI C Emulation, version 0.4
[ 12.532] (II) Loading sub module "ramdac"
[ 12.532] (II) LoadModule: "ramdac"
[ 12.532] (II) Module "ramdac" already built-in
[ 12.533] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 12.533] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 12.533] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 12.535] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 12.535] (==) NVIDIA(0): RGB weight 888
[ 12.535] (==) NVIDIA(0): Default visual is TrueColor
[ 12.535] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 12.535] (**) NVIDIA(0): Option "TwinView" "0"
[ 12.535] (**) NVIDIA(0): Option "MetaModes" "DFP-0: nvidia-auto-select +0+0"
[ 12.535] (**) NVIDIA(0): Enabling 2D acceleration
[ 13.375] (II) NVIDIA(GPU-0): Display (Acer S231HL (DFP-0)) does not support NVIDIA 3D
[ 13.375] (II) NVIDIA(GPU-0): Vision stereo.
[ 13.408] (II) NVIDIA(GPU-0): Display (VIZ VO370M (DFP-1)) does not support NVIDIA 3D Vision
[ 13.408] (II) NVIDIA(GPU-0): stereo.
[ 13.409] (II) NVIDIA(0): NVIDIA GPU GeForce GTS 450 (GF106) at PCI:1:0:0 (GPU-0)
[ 13.409] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 13.409] (--) NVIDIA(0): VideoBIOS: 70.06.1f.00.01
[ 13.409] (II) NVIDIA(0): Detected PCI Express Link width: 8X
[ 13.409] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 13.409] (--) NVIDIA(0): Connected display device(s) on GeForce GTS 450 at PCI:1:0:0
[ 13.409] (--) NVIDIA(0): Acer S231HL (DFP-0)
[ 13.409] (--) NVIDIA(0): VIZ VO370M (DFP-1)
[ 13.409] (--) NVIDIA(0): Acer S231HL (DFP-0): 330.0 MHz maximum pixel clock
[ 13.409] (--) NVIDIA(0): Acer S231HL (DFP-0): Internal Dual Link TMDS
[ 13.409] (--) NVIDIA(0): VIZ VO370M (DFP-1): 165.0 MHz maximum pixel clock
[ 13.409] (--) NVIDIA(0): VIZ VO370M (DFP-1): Internal Single Link TMDS
[ 13.410] (II) NVIDIA(0): Display Device found referenced in MetaMode: DFP-0
[ 13.410] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID has been
[ 13.410] (**) NVIDIA(0): enabled on all display devices.
[ 13.430] (II) NVIDIA(0): Assigned Display Device: DFP-0
[ 13.430] (II) NVIDIA(0): Validated modes:
[ 13.430] (II) NVIDIA(0): "DFP-0:nvidia-auto-select+0+0"
[ 13.430] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 13.458] (--) NVIDIA(0): DPI set to (95, 94); computed from "UseEdidDpi" X config
[ 13.458] (--) NVIDIA(0): option
[ 13.458] (**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
[ 13.458] (==) NVIDIA(1): RGB weight 888
[ 13.458] (==) NVIDIA(1): Default visual is TrueColor
[ 13.458] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
[ 13.458] (**) NVIDIA(1): Option "TwinView" "0"
[ 13.458] (**) NVIDIA(1): Option "MetaModes" "nvidia-auto-select +0+0"
[ 13.458] (**) NVIDIA(1): Enabling 2D acceleration
[ 14.402] (II) NVIDIA(GPU-1): Display (LG Electronics L196W (DFP-0)) does not support NVIDIA
[ 14.402] (II) NVIDIA(GPU-1): 3D Vision stereo.
[ 14.403] (II) NVIDIA(1): NVIDIA GPU GeForce GT 430 (GF108) at PCI:2:0:0 (GPU-1)
[ 14.403] (--) NVIDIA(1): Memory: 1048576 kBytes
[ 14.403] (--) NVIDIA(1): VideoBIOS: 70.08.29.00.01
[ 14.403] (II) NVIDIA(1): Detected PCI Express Link width: 8X
[ 14.403] (--) NVIDIA(1): Interlaced video modes are supported on this GPU
[ 14.403] (--) NVIDIA(1): Connected display device(s) on GeForce GT 430 at PCI:2:0:0
[ 14.403] (--) NVIDIA(1): LG Electronics L196W (DFP-0)
[ 14.403] (--) NVIDIA(1): LG Electronics L196W (DFP-0): 330.0 MHz maximum pixel clock
[ 14.403] (--) NVIDIA(1): LG Electronics L196W (DFP-0): Internal Dual Link TMDS
[ 14.405] (II) NVIDIA(1): Display Device found referenced in MetaMode: DFP-0
[ 14.405] (**) NVIDIA(1): Using HorizSync/VertRefresh ranges from the EDID has been
[ 14.405] (**) NVIDIA(1): enabled on all display devices.
[ 14.425] (II) NVIDIA(1): Assigned Display Device: DFP-0
[ 14.425] (II) NVIDIA(1): Validated modes:
[ 14.425] (II) NVIDIA(1): "nvidia-auto-select+0+0"
[ 14.425] (II) NVIDIA(1): Virtual screen size determined to be 1440 x 900
[ 14.428] (--) NVIDIA(1): DPI set to (89, 87); computed from "UseEdidDpi" X config
[ 14.428] (--) NVIDIA(1): option
[ 14.428] (**) NVIDIA(2): Depth 24, (--) framebuffer bpp 32
[ 14.428] (==) NVIDIA(2): RGB weight 888
[ 14.428] (==) NVIDIA(2): Default visual is TrueColor
[ 14.428] (==) NVIDIA(2): Using gamma correction (1.0, 1.0, 1.0)
[ 14.428] (**) NVIDIA(2): Option "TwinView" "0"
[ 14.428] (**) NVIDIA(2): Option "MetaModes" "DFP-1: nvidia-auto-select +0+0; DFP-1: 1920x1080 +0+0"
[ 14.428] (II) NVIDIA(2): NVIDIA GPU GeForce GTS 450 (GF106) at PCI:1:0:0 (GPU-0)
[ 14.428] (--) NVIDIA(2): Memory: 1048576 kBytes
[ 14.428] (--) NVIDIA(2): VideoBIOS: 70.06.1f.00.01
[ 14.428] (II) NVIDIA(2): Detected PCI Express Link width: 8X
[ 14.428] (--) NVIDIA(2): Interlaced video modes are supported on this GPU
[ 14.428] (--) NVIDIA(2): Connected display device(s) on GeForce GTS 450 at PCI:1:0:0
[ 14.428] (--) NVIDIA(2): Acer S231HL (DFP-0)
[ 14.428] (--) NVIDIA(2): VIZ VO370M (DFP-1)
[ 14.428] (--) NVIDIA(2): Acer S231HL (DFP-0): 330.0 MHz maximum pixel clock
[ 14.428] (--) NVIDIA(2): Acer S231HL (DFP-0): Internal Dual Link TMDS
[ 14.428] (--) NVIDIA(2): VIZ VO370M (DFP-1): 165.0 MHz maximum pixel clock
[ 14.428] (--) NVIDIA(2): VIZ VO370M (DFP-1): Internal Single Link TMDS
[ 14.429] (II) NVIDIA(2): Display Device found referenced in MetaMode: DFP-1
[ 14.429] (**) NVIDIA(2): Using HorizSync/VertRefresh ranges from the EDID has been
[ 14.429] (**) NVIDIA(2): enabled on all display devices.
[ 14.429] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.429] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.429] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.429] (WW) NVIDIA(2): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 14.429] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.429] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.429] (WW) NVIDIA(2): "720x576" is specified in the EDID; however, the EDID's
[ 14.429] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.429] (WW) NVIDIA(2): this mode's HorizSync (15.6 kHz); ignoring HorizSync check
[ 14.429] (WW) NVIDIA(2): for mode "720x576".
[ 14.429] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.429] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.429] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.429] (WW) NVIDIA(2): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 14.429] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.429] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.429] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.429] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.429] (WW) NVIDIA(2): this mode's HorizSync (27.0 kHz); ignoring HorizSync check
[ 14.429] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.429] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.429] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.429] (WW) NVIDIA(2): valid VertRefresh range (50.000-77.000 Hz) would exclude
[ 14.429] (WW) NVIDIA(2): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
[ 14.429] (WW) NVIDIA(2): check for mode "1920x1080".
[ 14.430] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.430] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.430] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.430] (WW) NVIDIA(2): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 14.430] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.431] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.431] (WW) NVIDIA(2): "720x576" is specified in the EDID; however, the EDID's
[ 14.431] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.431] (WW) NVIDIA(2): this mode's HorizSync (15.6 kHz); ignoring HorizSync check
[ 14.431] (WW) NVIDIA(2): for mode "720x576".
[ 14.432] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.432] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.432] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.432] (WW) NVIDIA(2): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 14.432] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.432] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.432] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.432] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.432] (WW) NVIDIA(2): this mode's HorizSync (27.0 kHz); ignoring HorizSync check
[ 14.432] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.432] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.432] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.432] (WW) NVIDIA(2): valid VertRefresh range (50.000-77.000 Hz) would exclude
[ 14.432] (WW) NVIDIA(2): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
[ 14.432] (WW) NVIDIA(2): check for mode "1920x1080".
[ 14.451] (II) NVIDIA(2): Assigned Display Device: DFP-1
[ 14.451] (II) NVIDIA(2): Validated modes:
[ 14.451] (II) NVIDIA(2): "DFP-1:nvidia-auto-select+0+0"
[ 14.451] (II) NVIDIA(2): "DFP-1:1920x1080+0+0"
[ 14.451] (II) NVIDIA(2): Virtual screen size determined to be 1920 x 1080
[ 14.454] (WW) NVIDIA(2): Cannot find size of first mode for Acer S231HL (DFP-0); cannot
[ 14.454] (WW) NVIDIA(2): compute DPI from Acer S231HL (DFP-0)'s EDID.
[ 14.454] (==) NVIDIA(2): DPI set to (75, 75); computed from built-in default
[ 14.454] (--) Depth 24 pixmap format is 32 bpp
[ 14.454] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 14.454] (II) NVIDIA: access.
[ 14.456] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 14.456] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 14.456] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 14.456] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 14.456] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 14.456] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 14.456] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 14.456] (II) NVIDIA(0): Config Options in the README.
[ 14.458] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select+0+0"
[ 14.490] (II) Loading extension NV-GLX
[ 14.556] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 14.556] (==) NVIDIA(0): Backing store disabled
[ 14.556] (==) NVIDIA(0): Silken mouse enabled
[ 14.556] (**) NVIDIA(0): DPMS enabled
[ 14.556] (II) Loading extension NV-CONTROL
[ 14.556] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "CRT", but no
[ 14.556] (WW) NVIDIA(0): such display device could be found, or all display devices
[ 14.556] (WW) NVIDIA(0): by that name are currently unavailable.
[ 14.556] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "TV", but no such
[ 14.556] (WW) NVIDIA(0): display device could be found, or all display devices by
[ 14.556] (WW) NVIDIA(0): that name are currently unavailable.
[ 14.556] (II) Loading extension XINERAMA
[ 14.556] (II) Loading sub module "dri2"
[ 14.556] (II) LoadModule: "dri2"
[ 14.557] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 14.557] (II) Module dri2: vendor="X.Org Foundation"
[ 14.557] compiled for 1.11.3, module version = 1.2.0
[ 14.557] ABI class: X.Org Server Extension, version 6.0
[ 14.557] (II) NVIDIA(0): [DRI2] Setup complete
[ 14.557] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 14.557] (==) RandR enabled
[ 14.559] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 14.559] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
[ 14.559] (II) NVIDIA(1): configuration option may not be set correctly. When the
[ 14.559] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
[ 14.559] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
[ 14.559] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
[ 14.559] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
[ 14.559] (II) NVIDIA(1): Config Options in the README.
[ 14.561] (II) NVIDIA(1): Setting mode "nvidia-auto-select+0+0"
[ 14.654] (==) NVIDIA(1): Disabling shared memory pixmaps
[ 14.654] (==) NVIDIA(1): Backing store disabled
[ 14.654] (==) NVIDIA(1): Silken mouse enabled
[ 14.655] (**) NVIDIA(1): DPMS enabled
[ 14.655] (II) Loading sub module "dri2"
[ 14.655] (II) LoadModule: "dri2"
[ 14.655] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 14.655] (II) Module dri2: vendor="X.Org Foundation"
[ 14.655] compiled for 1.11.3, module version = 1.2.0
[ 14.655] ABI class: X.Org Server Extension, version 6.0
[ 14.655] (II) NVIDIA(1): [DRI2] Setup complete
[ 14.655] (II) NVIDIA(1): [DRI2] VDPAU driver: nvidia
[ 14.655] (==) RandR enabled
[ 14.657] (II) NVIDIA(2): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 14.657] (II) NVIDIA(2): may not be running or the "AcpidSocketPath" X
[ 14.657] (II) NVIDIA(2): configuration option may not be set correctly. When the
[ 14.657] (II) NVIDIA(2): ACPI event daemon is available, the NVIDIA X driver will
[ 14.657] (II) NVIDIA(2): try to use it to receive ACPI event notifications. For
[ 14.657] (II) NVIDIA(2): details, please see the "ConnectToAcpid" and
[ 14.657] (II) NVIDIA(2): "AcpidSocketPath" X configuration options in Appendix B: X
[ 14.657] (II) NVIDIA(2): Config Options in the README.
[ 14.657] (II) NVIDIA(2): Setting mode "DFP-1:nvidia-auto-select+0+0"
[ 14.834] (==) NVIDIA(2): Disabling shared memory pixmaps
[ 14.834] (==) NVIDIA(2): Backing store disabled
[ 14.834] (==) NVIDIA(2): Silken mouse enabled
[ 14.834] (**) NVIDIA(2): DPMS enabled
[ 14.834] (II) Loading sub module "dri2"
[ 14.834] (II) LoadModule: "dri2"
[ 14.834] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 14.834] (II) Module dri2: vendor="X.Org Foundation"
[ 14.834] compiled for 1.11.3, module version = 1.2.0
[ 14.834] ABI class: X.Org Server Extension, version 6.0
[ 14.834] (II) NVIDIA(2): [DRI2] Setup complete
[ 14.834] (II) NVIDIA(2): [DRI2] VDPAU driver: nvidia
[ 14.834] (==) RandR enabled
[ 14.834] (II) Initializing built-in extension Generic Event Extension
[ 14.834] (II) Initializing built-in extension SHAPE
[ 14.834] (II) Initializing built-in extension MIT-SHM
[ 14.834] (II) Initializing built-in extension XInputExtension
[ 14.834] (II) Initializing built-in extension XTEST
[ 14.834] (II) Initializing built-in extension BIG-REQUESTS
[ 14.834] (II) Initializing built-in extension SYNC
[ 14.834] (II) Initializing built-in extension XKEYBOARD
[ 14.834] (II) Initializing built-in extension XC-MISC
[ 14.834] (II) Initializing built-in extension SECURITY
[ 14.834] (II) Initializing built-in extension XINERAMA
[ 14.834] (II) Initializing built-in extension XFIXES
[ 14.834] (II) Initializing built-in extension RENDER
[ 14.834] (II) Initializing built-in extension RANDR
[ 14.834] (II) Initializing built-in extension COMPOSITE
[ 14.834] (II) Initializing built-in extension DAMAGE
[ 14.835] (II) Initializing extension GLX
[ 15.155] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 15.155] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 15.156] (II) LoadModule: "evdev"
[ 15.156] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 15.161] (II) Module evdev: vendor="X.Org Foundation"
[ 15.161] compiled for 1.10.99.902, module version = 2.6.0
[ 15.161] Module class: X.Org XInput Driver
[ 15.161] ABI class: X.Org XInput driver, version 13.0
[ 15.161] (II) Using input driver 'evdev' for 'Power Button'
[ 15.161] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 15.161] (**) Power Button: always reports core events
[ 15.161] (**) Power Button: Device: "/dev/input/event4"
[ 15.161] (--) Power Button: Found keys
[ 15.161] (II) Power Button: Configuring as keyboard
[ 15.161] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
[ 15.161] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 15.161] (**) Option "xkb_rules" "evdev"
[ 15.161] (**) Option "xkb_model" "evdev"
[ 15.161] (**) Option "xkb_layout" "us"
[ 15.172] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 15.172] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 15.172] (II) Using input driver 'evdev' for 'Power Button'
[ 15.172] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 15.172] (**) Power Button: always reports core events
[ 15.172] (**) Power Button: Device: "/dev/input/event3"
[ 15.172] (--) Power Button: Found keys
[ 15.172] (II) Power Button: Configuring as keyboard
[ 15.172] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3/event3"
[ 15.172] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 15.172] (**) Option "xkb_rules" "evdev"
[ 15.172] (**) Option "xkb_model" "evdev"
[ 15.172] (**) Option "xkb_layout" "us"
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event6)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event7)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event8)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event9)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event10)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event11)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event12)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event13)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.174] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:1025 (/dev/input/event1)
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: Applying InputClass "evdev pointer catchall"
[ 15.174] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:1025'
[ 15.174] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: always reports core events
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: Device: "/dev/input/event1"
[ 15.174] (--) Logitech Unifying Device. Wireless PID:1025: Found 20 mouse buttons
[ 15.174] (--) Logitech Unifying Device. Wireless PID:1025: Found scroll wheel(s)
[ 15.174] (--) Logitech Unifying Device. Wireless PID:1025: Found relative axes
[ 15.174] (--) Logitech Unifying Device. Wireless PID:1025: Found x and y relative axes
[ 15.174] (II) Logitech Unifying Device. Wireless PID:1025: Configuring as mouse
[ 15.174] (II) Logitech Unifying Device. Wireless PID:1025: Adding scrollwheel support
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: YAxisMapping: buttons 4 and 5
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 15.174] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.4/1-1.2.1.4:1.2/0003:046D:C52B.0005/input/input1/event1"
[ 15.174] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:1025" (type: MOUSE, id 8)
[ 15.174] (II) Logitech Unifying Device. Wireless PID:1025: initialized for relative axes.
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: (accel) keeping acceleration scheme 1
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: (accel) acceleration profile 0
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: (accel) acceleration factor: 2.000
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: (accel) acceleration threshold: 4
[ 15.174] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:1025 (/dev/input/mouse0)
[ 15.174] (II) No input driver/identifier specified (ignoring)
[ 15.174] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4004 (/dev/input/event2)
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: Applying InputClass "evdev keyboard catchall"
[ 15.174] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:4004'
[ 15.174] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: always reports core events
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: Device: "/dev/input/event2"
[ 15.174] (--) Logitech Unifying Device. Wireless PID:4004: Found 1 mouse buttons
[ 15.174] (--) Logitech Unifying Device. Wireless PID:4004: Found scroll wheel(s)
[ 15.174] (--) Logitech Unifying Device. Wireless PID:4004: Found relative axes
[ 15.174] (--) Logitech Unifying Device. Wireless PID:4004: Found absolute axes
[ 15.174] (--) Logitech Unifying Device. Wireless PID:4004: Found keys
[ 15.174] (II) Logitech Unifying Device. Wireless PID:4004: Configuring as mouse
[ 15.174] (II) Logitech Unifying Device. Wireless PID:4004: Configuring as keyboard
[ 15.174] (II) Logitech Unifying Device. Wireless PID:4004: Adding scrollwheel support
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: YAxisMapping: buttons 4 and 5
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 15.174] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.4/1-1.2.1.4:1.2/0003:046D:C52B.0005/input/input2/event2"
[ 15.174] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:4004" (type: KEYBOARD, id 9)
[ 15.174] (**) Option "xkb_rules" "evdev"
[ 15.174] (**) Option "xkb_model" "evdev"
[ 15.174] (**) Option "xkb_layout" "us"
[ 15.174] (EE) Logitech Unifying Device. Wireless PID:4004: failed to initialize for relative axes.
[ 15.174] (II) Logitech Unifying Device. Wireless PID:4004: initialized for absolute axes.
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: (accel) keeping acceleration scheme 1
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: (accel) acceleration profile 0
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: (accel) acceleration factor: 2.000
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: (accel) acceleration threshold: 4
[ 15.175] (II) config/udev: Adding input device raphnet.net GC/N64_USB (/dev/input/event0)
[ 15.175] (II) No input driver/identifier specified (ignoring)
[ 15.175] (II) config/udev: Adding input device raphnet.net GC/N64_USB (/dev/input/js0)
[ 15.175] (II) No input driver/identifier specified (ignoring)
[ 15.175] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 15.175] (II) No input driver/identifier specified (ignoring)
Lines 14.429 - 14.432 are what interests me the most. What I got from it was that the refresh rates weren't set right, but after I changed those values in my /etc/X11/xorg.conf.d/10-monitor.conf file to what this log suggested, it still did not work. Here is that file:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 290.10 ([email protected]) Wed Nov 16 18:46:42 PST 2011
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 1920 0
Screen 1 "Screen1" RightOf "Screen0"
Screen 2 "Screen2" LeftOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Acer S231HL"
HorizSync 30.0 - 80.0
VertRefresh 55.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor1"
VendorName "Unknown"
ModelName "LG Electronics L196W"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor2"
VendorName "Unknown"
ModelName "VIZ VO370M"
HorizSync 27.0 - 70.0
VertRefresh 24.0 - 77.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTS 450"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GT 430"
BusID "PCI:2:0:0"
EndSection
Section "Device"
Identifier "Device2"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTS 450"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "DFP-0: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen2"
Device "Device2"
Monitor "Monitor2"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "DFP-1: nvidia-auto-select +0+0; DFP-1: 1920x1080 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
I am really out of ideas, I know the tv works inputs work fine because I watch tv on it (!). Does anyone have any suggestions?

I'm trying to configure the resolution for a Vizio va22lfhdtv10t on a Mini. When I used a DVI to VGA adapter the resolution was very good at 1920*1080. Now that I'm using a DVI to HDMI cable it defaults to 1080p with 30hz refresh. Font resolution is terrible on this setting and only marginally better when trying the other resolution options. I have seen some posts about creating a custom resolution, but don't know how to do this, or if there is a danger of damaging the LCD with improper settings. Has anyone gotten this HDTV to work other than as a VGA display?
Thanks!

I have WRT54G router.  The VIZIO VBR231 unit finds the network OK and indicates it is connected, but nothing will stream, and  when I run a Network Test it gives me this 3 line error:
Connection to 0.0.0.0... successfully established
Resolving... could not be established
Please check your connection and try again.
The VIZIO support folks were not helpful at all, and said something about Port 80 or Port 43 not being open or available.  When I talked to linksys support, they said I needed to add the VIZIO player's IP (which appears to be 0.0.0.0 in the system settings).  Can anyone tell me what I would need to do, step by step?  I poked around a bit, including the Port Forwarding tab on the router setup, but could not see a way to assign 0.0.0.0 to one of these ports, and I am hesitant to experiment.
I'll probably just return the unit to Costco, but I'm trying this forum as a last ditch effort.  BTW I have a VIZIO internet TV that I love, and that had absolutely no problem at all connecting to the wireless.  Thank you!

I've searched online and throughout the apple forum, but I can't find any info that discusses the best sequence and project settings to use with a Canon Vixia HF200 camera. I bought ten of the Vixia HF200's for our school to use with Final Cut Pro 6.06 running on Quad Core and a few 8 core Intel Macs. We can ingest perfectly. No issue. And I am probably using the wrong settings, but I set the sequence preset to Apple Pro Res HQ 1920x1080 24p. Our cameras are all set to cinema mode24p. For easy setup we have been using Format:HD, Rate:all and Use at DVCPro HD-1080pA24. Our sequence settings are 1920x1080 Custom 16:9, Pixel Aspect=1440x1080, timebase=23.98 and compressor apple Pro res HQ. I've played with other settings and editing is fine and the video looks fine. However, on most of these settings we are seeing some weird by product. All exported 1920x1080 video has flash frames throughout the video. You can watch the video on an NTSC monitor or on the computer monitor and there are no flash frames. But once you export using Quicktime Movie Apple Pro Res HQ 1920x1080, then that exported file shows multiple flash frames. Again, I'm sure I have all the wrong settings. Can someone respond with the optimal settings for editing AVCHD @ 24MB from a Canon Vixia HF200 within FCP 6.06?

Hello
Everyone I have a Vivitar Media card reader and every card I put in shows up read only? Any ideas?

I have now updated following many many times, in my free Best Buy guide - Vantage Technology Magazine - so it's time to post an update here... Just as I done in PreCentral ;-)
WebOS is now the clearly best alternative, for most people - but the Personal Information Management functionality, got a lot worse since the "old" Palm OS and that is a huge problem, because a really smart PIM suite with excellent ToDo and calender functions, can really improve your life and that make it the most valuable part of a smartphone, if it work great... And if Palm finally begin to fix this limitations, can they also advertise "We make the best mobile OS even better" each time they update and not just use the updates as bug fixes...
Then do I live in Sweden and we don't got the Palm Pre yet - so I could not test anything myself and that mean that some details below might be wrong or already fixed... So please email me - [email protected] - if something need adjustment... And that also mean that I maybe missed some more problems, that was very hard or impossible to see in screen shots and reviews... And I will actually not buy any device with webOS before most of the first 8 limitations below, are fixed either by Palm or someone else - because I simply don't want to pay for clearly worse functionality, than I already have with my "old" lovely Palm Treo 680!!
I read that many share my views, about following problems - but PLEASE comment this post anyhow, if you feel the same about ANY part... So Palm finally wake up, understand that people actually are very different (with dramatically different needs) and simply give us the vital options / settings, that only will make webOS dramatically better for heavy users and absolutely NOT make anything less fancy, if they simply let the current "look" be the default setting... Type Palm will only win, if they make "the best mobile OS" even better!!
01) There is still no complete desktop sync for every important Personal Information Management part, as ToDo lists with categories... Except if you are connected to an Exchange server... You can only back up automatically to Palm's servers, but without any option to edit your own text from your notebook... So complete desktop sync should actually be included in the box, as an alternative and offer sync through both USB and Wifi, plus maybe Bluetooth... And naturally include some kind of desktop application, so you can save and edit the calendar and tasks in your notebook... Now must you first buy MS Outlook (if you not have that) and a third party sync program, that not even handle ToDo lists... But palm have at least a migration tool, that help you move all your data (one way only) from an old Palm device and Palm desktop (or MS Outlook) to a new pre...
02) There is a lot of "elegant" waste of screen space and very BIG fonts, in almost every basic view... That should naturally be an option, because and absolutely not a default setting, you can't even change... Because most people need just 33% more space, to max 50% more if you have huge finger tips, for accurate finger navigation (compared to a stylus) and NOT more than twice the space, to show the same text info... They should at least offer two extra alternative settings - that show two or three times as much info (at every view that now use huge fonts) and that would anyhow be easy to navigate with your fingertips... Yes, the events have now small text in the calender (that not should get smaller) and many may love the new spacious design, with a lot of empty space and huge fonts... But there should naturally be some alternative setting - for everyone that have normal finger tips, a lot of info in the smartphone and don't want to scroll like crazy.... And it's especially very easy to miss vital info, if you can't see it directly, as in Tasks and Contacts... So I sincerely hope it soon will be possible to "tighten" up all the new empty space between text lines and at least select smaller fonts (naturally together with less empty space around the letters) in the settings... And the absolute best would be if you can select that options separately for the tasks, contacts, email, calendar and messaging... And then choose between four text sizes, with the current as 4 with a bit bigger text for calendar events and "modern" or roman fonts... Because if some tightening NOT is possible, will the the bigger screen only be useful for web browsing and that would be very very sad... Yes, you can now only see HALF the info in Tasks (without scrolling or missing vital stuff) even if the screen is much bigger, than I can see directly in my "old" Palm Treo 680 and that vital missing option, would make Palm Pre practically useless for me!!
03) The included Task application seems to be almost worthless, because of five big usability limitations... -1- You can't see if there is an "extra note page" connected to the task... -2- It don't show the priority either... -3- You can now only select 3 priority levels (just as in Windows mobile and Symbian) even if it was 5 levels before... -4- The huge fonts and plenty of empty space around the text, make it only possible to view 6 task without scrolling, instead of the 11 task that I can view on the much smaller Treo 680 screen and that is almost insane, when a simple setting / option could allow 12 task in Pre, with clearly more empty space around the text (for easy finger navigation) than before... -5- Then will task only sync with Exchange servers (if you have that) but not with Google, as example... But the lousy task management, can of course be fixed soon by Palm or in good time, with extra programs... And it support at least "multiple todo lists" as categories, so it work slightly better than simple Nokia smartphones... Then can you anyhow use the old PalmOS task application (that not have any of this limitations) with help of the amazing "Classic" emulator, instead of the crippled webOS version!!
04) The last BIG problem I found, was the fact that webOS not support any categories (as friends, biz, service and shops) in the contacts application any more - which are very bad news, if you have about 200 contacts and extremely inconvenient for people with a lot more than 600 contacts... Note that otherwise is webOS contact application clearly more advanced than before... And I expect there will be some even more advanced contact applications, with category functionality, pretty soon - even if that naturally should be included by Palm, from the start... Then can you actually use the old PalmOS contact application (that not have this limitation) with help of the amazing "Classic" emulator, instead of the otherwise great webOS version!!
05) In the calendar should you also be able to remove the fancy "empty time holder" completely, to free up even more space for real calender info!!
06) The "date picker" that help you select another day for an entry in the calendar, should naturally show a mini calendar (with dated and weekdays) as it was before and not just let you select days from a list, guessing what weekday that might be!!
07) The "universal" search don't search in the Calendar, any documents, in the message part of emails or Tasks* and that is very strange - it should at least be a two step search, with a "Search deeper in Pre" option, before Pre offer you to search in Google... Or even get a finer possibility, to select where the Pre normally should search... * But you can search Task, if you are inside.
08) There is no longer any "scroll bar" that show where you are, not even as an option and it should be a slim transparent indicator, that also show how big the actual view is of the total page.
09) Then do I also want the magnificent "floating event" functionality (at least in a third party application) that I now have in DateBk6 so you can show vital events that should be done today, in the calender and get them automatically moved to next day, every new day... But before you get this in a webOS application, can you use DateBk6 (made for the old PalmOS) that have this great functionality, with help of the amazing "Classic" emulator!!
10) The pretty "Memo" application is pointless (just as before) when you anyhow have Task and Calender... And it is not possible to sync, so what you really need is a good plain text editor - that is easy to back up and open from your notebook, rock solid, ultra fast, has smart search & replace and handle minimum 144 huge text documents, in 12 folders... Including at least txt, html and hopefully some other file types... I sincerely hope (and guess) that someone will make a fine text editor, because a true Word document editor IS a lot more clumsy and slower to use, in a smartphone... But you can probably use the excellent old PalmOS application CardTXT that have the text functionality you may need and more, with help of the amazing "Classic" emulator!!
11) There is no multiple email management, so you have to delete or move each email separately and that should naturally be fixed... Even if you (maybe) can do that in Google email or outlook, instead? * And you can now "delete all" in the trash folder!
12) You can't change the alert sound for texts and emails!
13) Then is the new program launcher, rather limited... You get only three windows, without any helpful category names - like main, games, web favo, friends, settings and extra - you get only a simple I to III style indicator at bottom... But you will probably be able to buy a more advanced launcher, soon... And you can temporary put your 12 main programs (that not is on the quick bar) on the first page, web favo's plus settings on the second and everything else on the last page... But there is now a free "patch" at www.precentral.net that add extra pages and two more, that show 4 or 5 icons on each row... And you can in addition use the old PalmOS application manager (that not have this limitations) for any excellent "old" programs, with help of the amazing "Classic" emulator!
14) Pre shuts down the phone, when you connect it as a USB drive and you have to enter your PIN to get back online.... Yes, that is one thing that even iPhone handle better.
15) You use right or left swiping to view another day and the same method to view another week, in that view... But you must swipe up and down in month view and that's just dumb!!
16) Some part of the ultra smart "Synergy" integration give you also trouble, because if you include your Facebook account will everyone you "know" there (you can't just select a few) be saved as contacts and that may result in ton's of contacts, you don't want in your smartphone - but it will probably come some extra program that "filter" that later and the other new "Synergy" contacts functionality, work like magic.
17) Then does copy & paste not work in IM or SMS messages, but that should be very easy to fix... ** But copy & paste (of text) work now in both emails and web pages, plus many many other places!
18) You can't change how many "message lines" you can see in the email preview.
19) Pre work normally very fast, but there is a delay when you open new programs and no "hourglass" so you might sometimes wonder if something happen, the first times you open a heavy program... But I don't know if that really need a fix or just some getting use to?!
20) Then might the ring signal be too quiet, but only according to 1 of 9 reviewers and another one say it's loud enough... And the alarm clock use now the ringtone volume, so it should be fine... Even if the alarm clock naturally have a separate volume!!
This replace naturally my old version, that I did post here over one year ago!

I am visualizing some MII data using Xcelsius 2008.  For the most part I have been successful, particularly when visualizing within an MII session.  However there are some cases where my users will encounter a Flash error #2048, which is related to some security within Flash that will not allow cross-domain access to data.
You may ask, if you are within the MII environment why would it be cross domain.  Well, as it turns out Flash does not use a very complex mechanism for determining the domain, if the shortcut that my users use to access MII is
http://<server>:50000/MII
  instead of
http://<server>.<domain>.<company>.net:50000/XMII
Flash thinks that this is a cross-domain call if the URL embedded in Xcelsius uses the fully qualified domain name.
While I could send out new shortcuts to everyone, there are other issues.  And some future initiatives that may require cross-domain calls.
When Flash encounters a cross domain call, it looks for a policy file on the root of the datasource called crossdomain.xml which may look something like
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
     <site-control permitted-cross-domain-policies="master-only"/>
     <allow-access-from domain="*"/>
     <allow-http-request-headers-from domain="*" headers="SOAPAction"/>
</cross-domain-policy>
There are some SDN posts detailing how to get this file into the root on an ABAP WAS, however nothing about how to do it on a Java only server.   It would need to be accessible at:
http://<server>.<domain>.<company>.net:50000/crossdomain.xml
I realize this post crosses several different SAP technologies, any help would be appreciated, or direction on where I should post this.
Rod

I've seen other posts related to this but haven't found the exact issue, so here goes (and thanks in advance for your insights):
Instead of using appleTV, I hardwired my nice, huge sony tv to my macpro with a DVI-to-HDMI cable.  I did this because I like to have the iTunes visualizer running during parties and such (because, APPLE, the ATV won't freaking do it!)
The problem is that the iTunes visualizer apparently doesn't count as "activity," and the displays (including my tv) go to sleep after the interval that I've set in system preferences for display sleep.
I know that I can fix this by simply changing my system preferences when I intend to use my TV in this way, and I know that this isn't hard to do.  But I want to make sure that there isn't an option that I've missed.
Is there a way to tell the OS, one time and permanently, not to put the display(s) to sleep if the visualizer is running?
Thanks again y'all!

Hello,
I’m new at this forum and I don’t know if this is the right place to ask, but I hope it is ok.
The question is a little bit complicated, so I will divide it in two points:
1) I’ve bought one external 1TB HD and I plugged it in my Macbook via USB to use it with the Time Machine for Back-up, when I did it the Time Machine took care of it, formatted it to be useable and everything works fine; besides the back-up, I put in the external HD other files to be use that were not in the MacBook. The problem is: when I connect the same external HD to be use as well in one PC, doesn’t matter the OS (XP, Vista, etc), nothing appears, not even the drive itself, is it possible to solve it?
2) After a while, I decided to “upgrade” my back-up with the same external HD doing it wireless via Airport Extreme, I had some problems at the beginning with the first back-up, velocity of connection (still have) and so on, but in the end it is working acceptable. The problem is: as it created another backup modus (before was a direct folder structure and now it is a “disc Image”) all of sudden my external drive is full, just 50Gb free, I’ve checked it using even “JDiskReport 1.3.1” and “OmniDiskSweeper-1.7.1”, the “disk image” shows 0kb and the other files about 300Gb, my first back-up via USB I deleted, but nothing changed and the second via wireless connection should not have more than 200Gb (the first back-up that takes two days to do it was 130Gb), and it is not more than 1 month and no “big” file was add to my MacBook since then. P.S.: I still can not see the files at the PC via network.
Sorry for this complicated question, but these are two questions that I need your support, if possible.
Thank you in advance,
Clayton