Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
Exactly, the thunderboltex card has been vaporware. Asus reps stopped answering questions about it around a year ago (around when it was reported that it failed certification with intel). Educated speculation has been that intel will never certify such a card as it allows pass-thru of...
I know, I saw that article and pic. You can also see the header in asus's own pic, though only some of the TB_HEADER lettering is visible.http://www.asus.com/media/global/products/1rZrl1Syxkizi57k/gHs0cHv29XX9X8Wl_1000.jpg
Nevertheless, the header remains undocumented in use in the manual...
The manual for the asus gryphon z87 shows a thunderbolt header: http://dlcdnet.asus.com/pub/ASUS/mb/LGA1150/GRYPHON-Z87/E7870_GRYPHON_Z87.pdf
I wonder if this is a mistake, as the thunderbolt header isn't listed on asus's spec overview.
Since last year's asus thunderboltex card never shipped...
Galaxy tab 10.1 still in stock @staples around here. Just picked one up with this great deal. They didn't even have them on display yet - surprising they are willing to give such a good discount on product they haven't even had a chance to sell at MSRP yet.
Well perhaps the consumer drivers have code in there but it's not functioning with nearly all consumer cards. It seems ati only supports 10 bit per channel on the 5870, and not on any of the lower end cards, even other evergreen class cards.
In fact you are the first to report that you've...
You're missing one of the points which is that some users are thread-crapping on the various u3011 threads concerning wide gamut, thus making it more difficult for the rest of us (like myself) who *do* care about wide gamut.
Oh and please spare me the attitude, ok thanks.
Startup123,
recommend you add 'dog to your ignore list. He trolls wide gamut discussions arguing against them and ignores facts presented that disprove his claims and conjecture. Its a waste of time arguing against an anonymous troll who behaves that way.
PC_User, we do have a wide gamut...
Well not knowing about a problem is what you can expect from CSRs, but a "cannot happen" response is not. I suspected a firmware issue all along too but that doesn't get dell to identify the problem.
This is where a forum can help turn the "cannot happen" into a known pervasive problem. If...
I spoke with a CSR about this problem weeks ago, before reporting it here, even. The CSR spoke with his manager, and they concluded that the problem couldn't happen. I reminded them that the problem happened with two different u3011 monitors I had, two different computers, two different...
The prefixes don't match, but the last 12 digits do.
So I would not sweat it.
In the "calibration report" the prefix is CN0DYMWD
whereas the s/n on the back of the monitor's prefix is CN-OPH5NY
Interestingly, if you look at the monitor EDID information you get a match on just the last 7 digits...
This same topic again?
Forum needs a moderator and some stickies...
Anyways, when comparing those two monitors, don't forget about differences in return policy, customer support, dead pixel policy, etc.
I did originally calibrate my u3011 with an i1 display 2. I wouldn't use the word "successfully" given the problems with custom color mode settings changing on their own, and the fact that the colorimeter isn't quite measuring wide gamut colors correctly. Not to mention the lack of...
You will of course easily have that problem with any application that is not fully color management aware. (There is a separate thread for wide-gamut applications if you're interested in that, though the thread is a bit cluttered with thread-crap).
The simplest fix I've found for the custom color mode setting problem is to use:
Menu->color settings->reset color settings
Menu->Other settings->factory reset->reset all settings works as well but that warps your brightness back to the factory "torch" mode.