Is this problem still present in version 1.34? I changed how the output from ddcprobe and xresprobe is handled, and hope it will get a more useful resolution information from the monitor. Happy hacking, -- Petter Reinholdtsen