Russell Proulx <rproulx@r2p2.com>: When they then loaded the i1 software to create a profile it completely messed what was displayed on screen.
There is something hinky going on. As I mentioned, I've never used an i1 but doesn't it come with a calibration puck that is used in conjunction with the calibration software? That's the way it works with the Datacolor Spyder--I plug in the Spyder puck's usb cable into a USB port on my system (Win7/Pro/64bit by the way) and then start the Spyder software (if you start the software without the puck plugged in, it displays a message that there is no puck plugged in), one then positions the puck based on the software display and then one proceeds through the calibration process as the puck reads the screen display with is now under the control of the Spyder software.
If the hardware is calibrated correctly I'm not sure there's even any need to produce a custom profile as the sRGB and aRGB modes would then be accurate using the canned profile. No?
Uhhh...no... The whole point of the hardware calibration is to produce a monitor profile that characterizes the monitor so that things like sRGB and aRGB (and other color managed stuff) work properly...
I really prefer my Dell monitors and its custom i1 software calibrates the monitor hardware AND also creates a custom profile that's saved in the appropriate system folder.
That's what I get with the Datacolor Spyder. While my PA248Q came with the (starter) monitor profile, I had to supply my own monitor calibrator/software as Asus didn't supply it--I never knew they offered monitors with a calibrator.
The documentation suppled with the Asus ProArt montor is lacking detail.
I wasn't impressed with the Asus documentation either and don't get me started the total crap experience I had with I contacted Asus support--will never do that again. That said, I've been happy with my PA248Q monitor and would likely buy another of their PA-level monitors. On thing you didn't answer is which Windows O/S your friend is using? I suspect that it's probably Windows 10 and given what I've read about Win10, it wouldn't surprise me if that was the root of the issue. Win10...ugh! '-}} Terrie tlbtlb@mail.com