Click to view our Accessibility Statement or contact us with accessibility-related questions
Showing 1 of 778 conversations about:
SirDodo
0
Oct 13, 2014
bookmark_border
Drop Refurbished
Like-new products you can trustDrop Rewards
Get $5 for every 500 points you earn! Learn more
Drop Keyboard Club
Become a member and expand your keycap collectionCollaborate With Us
For Brands & DesignersFollow Drop
I learned a few things in this process: 1) regarding DisplayPort, DisplayPort 1.2 is required to use the monitor at full resolution at 60Hz. That's because the bit rate needed is (just) beyond the nominal 10Gbps supported by earlier versions of the DisplayPort standard. Fortunately I had DisplayPort 1.2 on my motherboard (SuperMicro X10SAT). 2) Thunderbolt 2 is required for Thunderbolt support of the monitor at full resolution at 60Hz. Prior to Thunderbolt 2, Thunderbolt supported discrete 10Gbps channels - insufficient for this resolution and frequency. My mobo did not support Thunderbolt 2, but I was OK with DisplayPort 1.2. 3) The screen split software is a 'tiling' program. I didn't like it. I wanted the maximize button to toggle between filling the partition of the screen and a smaller window within the partition, but it toggled between filling the partition and filling the whole screen. 4) installing the screen split program also installed an ASM driver and a TI driver. That messed up my computer. (I've had trouble with my AS Media drivers on this Mobo.) I restored to an earlier image. I regretted not having taken a backup before this install. 5) I was OK with the ability of programs to resize content to something workable at the higher DPI (I've been using two old 19" EIZO monitors). Office was great. Browser content was fine. Quicken was annoying and needs work, but I could have lived with it.
The repositioning and resizing of windows was ultimately more than I wanted to accept, so I took the monitor back for a refund. L&G said the window resizing/repositioning was a video driver issue, disclaimed responsibility and were no help. I'm not sure, but I think this is an issue MicroSoft should address. I could have used a blank screen saver to avoid the issue, but I want the computer to be able to sleep, and a screen saver wouldn't have skirted the repositioning issue after waking up from sleep. Maybe I'll try again in a year or so.