tohico

Graphics cards should be able to do any configuration that falls within the DisplayPort specification, including 1440p 144 Hz or 1080p 240 Hz for DP 1.2. Any graphics card with DisplayPort 1.2 should be able to do this. I don't believe the GTX 780 has a limit of 1440p @ 120 Hz. There can sometimes be limitations depending on the monitor, for example some FreeSync monitors like the MG279Q (1440p 144 Hz) have been reported to have a maximum of 120 Hz on NVIDIA graphics cards, but this is mainly a problem with communication between the monitor and graphics card and can generally be fixed with EDID overrides.
 
There can be differences between graphics cards when it comes to operating beyond spec (i.e. display overclocking) but generally it is unusual for this to come into play, and it is not a very well explored area.

I recommend to change the overdrive setting, the extreme setting overshoots like crazy - that's why you see the black ghosts. Going from extreme (gtg 4.0 ms, overshoot 40.0 %) to medium (gtg 5.2 ms, overshoot 0.4 %) will cost you only 1 ms in response time and there will be absolutely no noticeable overshoot
 
It's very common to not go for the highest setting with overdrive, the highest one is often set up to overshoot here and there. It's not meant for the everyday use.

I'd go for the PG279Q (again) simply because of the photo editing requirements. Asus has very conservative approach with their top line up monitors regarding calibration, so they come very well calibrated out of the box (instead of trying to recreate wow effect for being different like other gaming monitors), there are very simple steps how to bring it to perfection as well (racing+warm, or for even better follow tftcentral's calibration) and the osd adjustments doesn't degrade the white/grey by that much (=more flexible osd calibration, more accurate calibration with colorimeters).
 
I believe this is the best monitor for the combination of gaming, photo editing and conservative use. Although the big trade off is the quality. Prepare yourself on potentially sending a few units back in case you get some bad ones and don't expect perfection from them either. Just make sure it works well enough for you. Let me explain what to look for in regards to any editing. Firstly, the BLB isn't as a big of a deal imho unless you get a very nasty one. Just make sure it doesn't bother you - sometimes they aren't naturally visible unless you look at them directly on black background (=not in an angle), so if there's one like on the bottom, you won't see it because you don't have the bottom frame at your eye level, etc. Secondly, and most importantly for editing work, watch out for the uniformity (color/temperature). This is always a problem on gaming monitors, because it's simply not something gamers care about. Even Dell yolos it on gaming monitors these days. But this can get pretty bad on this one. Check out for the color shifts / accents (on white background) as well as the temperature shifts (on light grey background) to see how bad it is and whether the affected area affects you in editing. And the last thing to watch out - for the first month or so, keep an eye whether the monitor doesn't yellow-out. Like by using a second monitor as the reference. In very small extent, it happens naturally after small period of use (discovered by people getting these for triple monitor setups), but there are a few rare cases that seem that got pretty nasty.
 
Whether to wait, it depends. If you don't mind waiting like even a year for a successor to PG279Q, then I'd strongly suggest to wait. This monitor has just too many QC issues and yet, there's no better alternative like this atm. And whether to wait for OLED, I don't think it will be ready for mainstream that soon. But I'm not sure, I'm not fan of the OLED yet anyway. Simply because I don't like it when there's way too much contrast. But that's more of a matter of content adjusting to the better technology, I'm hoping 10 bit plus some new standards and habits will fix this before OLED becomes a mainstream.

The short answer is yes.
 
The a-hole answer is you'll still have input lag. All 3ms of it.

All 3 of them are very good, but since you have the budget for it, I'd exclude the PG278Q for one simple reason - why would you get TN panel, if you don't have to.
 
Also don't worry about the response time that much, the 1 ms isn't real anyway. The PG278Q's response time is 3 ms with overdrive set to normal, PG279Q is 5 ms at 144 Hz which is very good for IPS, and the X34 is 9 ms or 7.5 ms if ran overclocked at 100 Hz. I compare it with overdrive set to medium, because that's what you're going to most likely use - no OD is significantly slower and maxed out OD has noticeable overshoots. Also, since we're talking about milliseconds. If you want it for competitive play too, don't forget about input lags which are always more problematic on larger resolutions. The PG279Q is the winner here, 3.25 ms, then PG278Q 4 ms, and the X34 9.2 ms, which is still very good for such large resolution these days.
 
Regarding the quality, all these are gaming monitors - so the quality won't be the best on any of them (in 90% cases, gaming oriented = bad quality) compared to their price tags. But that doesn't change the fact that they're amazing monitors, I just recommend you to do your research first to know what to expect and don't be afraid to send it back if you're not happy with the QC of the piece you get. But all the issues aren't usually associated with gaming / media use, rather than with the quality any human being would expect for those price tags. You know, like uniformity, color shifts, blb / glow, not derping out, etc...
 
You probably already know this, but solid research materials: (not regarding QC though)
 
http://www.tftcentral.co.uk/reviews/acer_predator_x34.htm
http://www.tftcentral.co.uk/reviews/asus_rog_swift_pg279q.htm
http://www.tftcentral.co.uk/reviews/asus_rog_swift_pg278q.htm

i think he wants it "disabled unless specified otherwise"
 
at which point he should do what you said, but the exact opposite

in the nvidia control panel you can set options for specific games, if your game of choice isnt in the (usually pretty accurate) prepared list, just browse for the executable.
 
you just add the profile for the game, and change anything you want to be different from default (this is also where you can for example force anti aliasing on things that do not internally support it, etc.) and leave everything else at default.
 
now.. since my windows install is *still* on dutch, i'm gonna be off with the naming of things, so i'll just point
- you open the control panel
- there's a bunch of options on the left, a block of "3D settings" a block of display settings, and some more crap.
- the block of "3D settings" has 3 blue link-like things in it, the second one is the one you need (it's simething like "configure 3D settings"
- this brings you to a page with settings, and at the top of the settings there's two tabs, the "generic settings" and the "program settings"
- the tab "program settings" is what allows you to enforce settings for specific applications.
 
EDIT: should add, gsync is under the vsync settings, as "adaptive" IIRC.

Come on mate, you know these numbers doesn't mean anything... And more contrast doesn't always mean better, especially not on 8 bit panels. I find too much contrast very uncomfortable and any dynamic contrast features to crank those numbers up are nightmares for all content creators. The healthy dose of contrast on PC should be around 1000:1 imho, which is very common for IPS panels.
 
Anyway, professional reviews on such monitors are very rare so it'll be hard to pick when we really get down to this. But I dig out some measured numbers for the mentioned contrast. The AOC has around 1000:1 (source) while the Acer has 550:1 (source), so yeah, the Acer is actually worse in this regard. EDIT: That review actually seems fishy, I found the Acer on Prad as well (very trustworthy professional monitor reviews) and they measured 930:1 (source), so it's fairly close to the AOC.
 
And OP, I'm just proving the wrong methodology, there's much more about these monitors than the contrast ratio. So don't take this as the recommendation, I don't know these monitors at all.

GSYNC = If you can't reach consistently the fps that your monitor's refresh rate requires. (=makes the game to not stutter)
VSYNC = If you easily get the fps and you play it casually. (=solves tearing, puts less load on your gpu = longer lifespan, less noise, consumes less power = you're saving the environment, yay!)
Neither = When you play competitively and need to reduce the input lag to absolute minimum. In such case, you go down with the settings, cap the fps at like 300 fps and try to keep it up there consistently. It's quite important for games like csgo if you play competitively and you're cereal with it. I'm not sure how much it's important for the MOBA games though.

I must say I'm disappointed in the ending, it was a bit sloppy and not very informative. Here's my idea how to improve it in the next one:
 
1) Proper showcasing the builds - We didn't get any chance to look at the builds very well. They were always somewhere in the corner, with bad lighting, and while something else was going on. Please, take a few shots of them in the studio next time. Like give them at least a little of the proper treatment like you do while doing reviews. We want to see them too, the builds are the whole point of this series.
 
2) Components summary - Summarize the components and even better, show it on the screen (like small summary on a side with transparent background while the context fit - eg. showcasing or before benchmarking). How are we supposed to remember what deal you managed to get 3 weeks ago. I still don't know what gpu Luke got, nor what processor exactly he got, the only thing I remember is that it was first gen i7.
 
3) Benchmarks and scoring summary - There was no way I was able to keep a track who was winning, especially during the benchmarks when the monitors weren't even next to each other. I'd suggest putting the summary of benchmark results and judge's scores in the video, so we can see and keep track of it easily.
 

I must say I'm disappointed in the ending, it was a bit sloppy and not very informative. Here's my idea how to improve it in the next one:
 
1) Proper showcasing the builds - We didn't get any chance to look at the builds very well. They were always somewhere in the corner, with bad lighting, and while something else was going on. Please, take a few shots of them in the studio next time. Like give them at least a little of the proper treatment like you do while doing reviews. We want to see them too, the builds are the whole point of this series.
 
2) Components summary - Summarize the components and even better, show it on the screen (like small summary on a side with transparent background while the context fit - eg. showcasing or before benchmarking). How are we supposed to remember what deal you managed to get 3 weeks ago. I still don't know what gpu Luke got, nor what processor exactly he got, the only thing I remember is that it was first gen i7.
 
3) Benchmarks and scoring summary - There was no way I was able to keep a track who was winning, especially during the benchmarks when the monitors weren't even next to each other. I'd suggest putting the summary of benchmark results and judge's scores in the video, so we can see and keep track of it easily.
 

I must say I'm disappointed in the ending, it was a bit sloppy and not very informative. Here's my idea how to improve it in the next one:
 
1) Proper showcasing the builds - We didn't get any chance to look at the builds very well. They were always somewhere in the corner, with bad lighting, and while something else was going on. Please, take a few shots of them in the studio next time. Like give them at least a little of the proper treatment like you do while doing reviews. We want to see them too, the builds are the whole point of this series.
 
2) Components summary - Summarize the components and even better, show it on the screen (like small summary on a side with transparent background while the context fit - eg. showcasing or before benchmarking). How are we supposed to remember what deal you managed to get 3 weeks ago. I still don't know what gpu Luke got, nor what processor exactly he got, the only thing I remember is that it was first gen i7.
 
3) Benchmarks and scoring summary - There was no way I was able to keep a track who was winning, especially during the benchmarks when the monitors weren't even next to each other. I'd suggest putting the summary of benchmark results and judge's scores in the video, so we can see and keep track of it easily.
 

I must say I'm disappointed in the ending, it was a bit sloppy and not very informative. Here's my idea how to improve it in the next one:
 
1) Proper showcasing the builds - We didn't get any chance to look at the builds very well. They were always somewhere in the corner, with bad lighting, and while something else was going on. Please, take a few shots of them in the studio next time. Like give them at least a little of the proper treatment like you do while doing reviews. We want to see them too, the builds are the whole point of this series.
 
2) Components summary - Summarize the components and even better, show it on the screen (like small summary on a side with transparent background while the context fit - eg. showcasing or before benchmarking). How are we supposed to remember what deal you managed to get 3 weeks ago. I still don't know what gpu Luke got, nor what processor exactly he got, the only thing I remember is that it was first gen i7.
 
3) Benchmarks and scoring summary - There was no way I was able to keep a track who was winning, especially during the benchmarks when the monitors weren't even next to each other. I'd suggest putting the summary of benchmark results and judge's scores in the video, so we can see and keep track of it easily.
 

I must say I'm disappointed in the ending, it was a bit sloppy and not very informative. Here's my idea how to improve it in the next one:
 
1) Proper showcasing the builds - We didn't get any chance to look at the builds very well. They were always somewhere in the corner, with bad lighting, and while something else was going on. Please, take a few shots of them in the studio next time. Like give them at least a little of the proper treatment like you do while doing reviews. We want to see them too, the builds are the whole point of this series.
 
2) Components summary - Summarize the components and even better, show it on the screen (like small summary on a side with transparent background while the context fit - eg. showcasing or before benchmarking). How are we supposed to remember what deal you managed to get 3 weeks ago. I still don't know what gpu Luke got, nor what processor exactly he got, the only thing I remember is that it was first gen i7.
 
3) Benchmarks and scoring summary - There was no way I was able to keep a track who was winning, especially during the benchmarks when the monitors weren't even next to each other. I'd suggest putting the summary of benchmark results and judge's scores in the video, so we can see and keep track of it easily.
 

I must say I'm disappointed in the ending, it was a bit sloppy and not very informative. Here's my idea how to improve it in the next one:
 
1) Proper showcasing the builds - We didn't get any chance to look at the builds very well. They were always somewhere in the corner, with bad lighting, and while something else was going on. Please, take a few shots of them in the studio next time. Like give them at least a little of the proper treatment like you do while doing reviews. We want to see them too, the builds are the whole point of this series.
 
2) Components summary - Summarize the components and even better, show it on the screen (like small summary on a side with transparent background while the context fit - eg. showcasing or before benchmarking). How are we supposed to remember what deal you managed to get 3 weeks ago. I still don't know what gpu Luke got, nor what processor exactly he got, the only thing I remember is that it was first gen i7.
 
3) Benchmarks and scoring summary - There was no way I was able to keep a track who was winning, especially during the benchmarks when the monitors weren't even next to each other. I'd suggest putting the summary of benchmark results and judge's scores in the video, so we can see and keep track of it easily.
 

I must say I'm disappointed in the ending, it was a bit sloppy and not very informative. Here's my idea how to improve it in the next one:
 
1) Proper showcasing the builds - We didn't get any chance to look at the builds very well. They were always somewhere in the corner, with bad lighting, and while something else was going on. Please, take a few shots of them in the studio next time. Like give them at least a little of the proper treatment like you do while doing reviews. We want to see them too, the builds are the whole point of this series.
 
2) Components summary - Summarize the components and even better, show it on the screen (like small summary on a side with transparent background while the context fit - eg. showcasing or before benchmarking). How are we supposed to remember what deal you managed to get 3 weeks ago. I still don't know what gpu Luke got, nor what processor exactly he got, the only thing I remember is that it was first gen i7.
 
3) Benchmarks and scoring summary - There was no way I was able to keep a track who was winning, especially during the benchmarks when the monitors weren't even next to each other. I'd suggest putting the summary of benchmark results and judge's scores in the video, so we can see and keep track of it easily.
 

I must say I'm disappointed in the ending, it was a bit sloppy and not very informative. Here's my idea how to improve it in the next one:
 
1) Proper showcasing the builds - We didn't get any chance to look at the builds very well. They were always somewhere in the corner, with bad lighting, and while something else was going on. Please, take a few shots of them in the studio next time. Like give them at least a little of the proper treatment like you do while doing reviews. We want to see them too, the builds are the whole point of this series.
 
2) Components summary - Summarize the components and even better, show it on the screen (like small summary on a side with transparent background while the context fit - eg. showcasing or before benchmarking). How are we supposed to remember what deal you managed to get 3 weeks ago. I still don't know what gpu Luke got, nor what processor exactly he got, the only thing I remember is that it was first gen i7.
 
3) Benchmarks and scoring summary - There was no way I was able to keep a track who was winning, especially during the benchmarks when the monitors weren't even next to each other. I'd suggest putting the summary of benchmark results and judge's scores in the video, so we can see and keep track of it easily.
 

I must say I'm disappointed in the ending, it was a bit sloppy and not very informative. Here's my idea how to improve it in the next one:
 
1) Proper showcasing the builds - We didn't get any chance to look at the builds very well. They were always somewhere in the corner, with bad lighting, and while something else was going on. Please, take a few shots of them in the studio next time. Like give them at least a little of the proper treatment like you do while doing reviews. We want to see them too, the builds are the whole point of this series.
 
2) Components summary - Summarize the components and even better, show it on the screen (like small summary on a side with transparent background while the context fit - eg. showcasing or before benchmarking). How are we supposed to remember what deal you managed to get 3 weeks ago. I still don't know what gpu Luke got, nor what processor exactly he got, the only thing I remember is that it was first gen i7.
 
3) Benchmarks and scoring summary - There was no way I was able to keep a track who was winning, especially during the benchmarks when the monitors weren't even next to each other. I'd suggest putting the summary of benchmark results and judge's scores in the video, so we can see and keep track of it easily.
 

I must say I'm disappointed in the ending, it was a bit sloppy and not very informative. Here's my idea how to improve it in the next one:
 
1) Proper showcasing the builds - We didn't get any chance to look at the builds very well. They were always somewhere in the corner, with bad lighting, and while something else was going on. Please, take a few shots of them in the studio next time. Like give them at least a little of the proper treatment like you do while doing reviews. We want to see them too, the builds are the whole point of this series.
 
2) Components summary - Summarize the components and even better, show it on the screen (like small summary on a side with transparent background while the context fit - eg. showcasing or before benchmarking). How are we supposed to remember what deal you managed to get 3 weeks ago. I still don't know what gpu Luke got, nor what processor exactly he got, the only thing I remember is that it was first gen i7.
 
3) Benchmarks and scoring summary - There was no way I was able to keep a track who was winning, especially during the benchmarks when the monitors weren't even next to each other. I'd suggest putting the summary of benchmark results and judge's scores in the video, so we can see and keep track of it easily.
 

Love this series, can't wait for another one! :3
 
I was surprised you went both with Intel CPUs. Back in the old days, AMD CPUs were pretty good for gaming on budget. For example, you can get the AMD Athlon II X4 series (eg. 640) for similar money as the Q6600, maybe even cheaper, and it takes it on a whole new level in games.

you may have to go down the line of a full install.
 
but you could use the cmd to unlock the drive. then run the repair again.   but it may not work at all and leave you with a non booting system.

If she wants it for strictly reading, any of the Kindles would be perfect.  My mother has one and uses it everyday.
Regular Kindle:http://www.amazon.com/gp/product/B007HCCNJU/ref=topnav_storetab_kinh
 
Kindle Paperwhite:http://www.amazon.com/gp/product/B00AWH595M/ref=kin_kp_kstore?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=center-2&pf_rd_r=0P590BRM49ZC2ZKSYZ8K&pf_rd_t=101&pf_rd_p=1627481542&pf_rd_i=133141011

I think your PC just sees two boot sectos and won't know which one to boot from so it asks you. But regarding the post from lutzee. 
I had a program (forgot the name), in which you could set paramiters when booting. So you could say it would default to Drive A after 10 seconds of no interaction. 
But if you wanted to boot to the second OS you could just press down and enter and you'd boot to OS 2. But if you'd just turn on your pc it would boot automatically without user input.
 
If that's what you're looking for.

Yes, thats what a boot manager does, linux by default uses grub (normally, some distros may come with syslinux, and some let you choose)
If you are installing linux, then let it be the boot drive, grub and syslinux will both detect any other OSs loaded on the PC and automatically add them to the boot manager screen, of which are both extremely customisable and you can make them look however you like
Of just do as I originally said

Yes, you set a main boot drive in the bios, but the bios normally has a boot select when you turn your PC on, normally mapped to something like f11, of course there still isn't a standard button for it. I use it when I need to boot into windows.