Thanks for the reply. I do have some new info. It does seem as though once it has had a chance to build thumbnails for an entire folder, it does not hang. I was eventually able to work just fine in the folder where I had first noticed a problem, but then I had a similar problem with another new folder. The behavior seems to be that I can move the window around back and forth between screens for a minute or so, but then it freezes. It's as though something has killed the process in mid-flight, as it does not show up in the taskmgr. There is nothing for me to kill, the screen is frozen with an image of the window, which may or may not be fully moved onto the 2nd screen, just wherever it happened to be when it crashed. At that point, I can no longer use the 2nd screen at all for any app. The mouse won't move onto it. I can launch another instance of Qimage, keeping it on the first screen, but I have only been able to recover the use of the 2nd screen by doing a restart. I have a feeling that if I launch Qimage in the main screen, navigate to a new folder, then let it do it's thing for a while, things will be ok after that. Similar to what you suggest.

Just upgraded to this version. Now I'm having an issue where Qimage causes my 2nd screen, where I do most of my work to lock up. The Qimage window in it's last state is showing there, but there is no interaction possible. It seems to be caused by selecting a large folder (3.27G). I can no longer access that screen at all. I am able to launch another instance of Qimage where I can select a smaller folder to avoid the problem next time, but then the only way I have been able to free up the screen is with a restart. I can't seem to find the process in the taskmgr that is hanging up. I don't know if this is an issue with previous versions, as I never tried to access this folder with older versions. System is Win 10, Dell XPS15, x64, i7-6700HQ 2.6GHz, 16G Ram, SSD has 190G free space. Second monitor is Dell 2007WFP.

Fred, you are probably right. The R1800 did have long periods of weeks and sometimes months of inactivity. I can easily see where there could be dried up ink blockages in various parts of the ink delivery system that were beyond the ability of Qimage unclogging and Epson cleaning routines to handle. Perhaps there is a more thorough manual cleaning process that could be done by disassembling the unit, but that seems like just too much effort. I plan to take advantage of the Qimage scheduled unclogging feature to keep the P600 in top shape. Lesson learned.

Thanks for your comments.

- Ken

Just to follow up on this old topic, I finally bought a new Epson P600 to replace the R1800. It is producing prints that match the monitor perfectly, including the example provided to Fred. For some reason, the R1800 had been distorting colors such that there was no predictability without making several test prints for each image to be printed. Don't know if it was software or hardware, (driver had been reinstalled), but given it's age, a new printer seemed like the best way to go. So far, I'm loving the new printer!

Thanks, Fred, for your efforts.  I think the EXIF data from the dog/man image may have been lost when it was emailed to me directly from an iPhone. It was shot on an iPhone 6 Plus.  The color chart was my own very quick and very dirty way to get an image with some reference tones. I admit that what I got is by no means a reference, and I should take the time to shoot it under controlled conditions. It was just laid out on a walkway in shaded sunlight. Anyway, it's very helpful to have an independent verification that the images themselves are not the problem. I've poured over my Epson driver and Qimage settings again and again. I've run the Qimage unclog pattern and Epson nozzle check and things look fine.  Maybe the next step is to try reinstalling the Epson driver. A corrupted driver seems unlikely, though.

Thanks, Fred, for your response.

It also happens with some images taken with my Olympus E-30. I shoot raw+jpeg, Adobe RGB. I only chose this image because it is the most recent example. This has been going on for a while. I have pursued it in the past, then just set it aside. There was a time when this wan't happening, so some time ago, something changed. I used to print with Photoshop with good results, and then switched to Qimage with good results for some time. Monitor and printer have been the same throughout. Software versions have received updates, except I stopped at PS CS5. The printer driver is the latest one provided by Epson, which dates to 2007. Installed it a few years ago after switching the OS from XP to Win7.

Softproof looks correct. Real prints are too dark.

I've already done that. I can see slight color variations using various profiles, letting the printer manage colors with various printer options, but always too dark.

Thanks, I'll take you up on that.

My aging R1800 is still capable of producing great prints, however, I have been unable to get results that match the monitor in many cases. There is both a color shift and density issue. The most recent example is a set of prints I made with Qimage Ultimate from an iphone, which uses sRGB color space. The prints come out about one stop too dark and slightly blue-shifted. I have gone through all of the usual steps in the past, i.e. monitor calibration, double and triple checking driver settings, etc. I even have profiles made with Profile Prism. The puzzling part is that I have ColorMatch RGB reference image that seems to match nearly perfectly. The problems seem to be somewhat image-dependent, making predictatble corrections difficult. For now, I have resorted to making test images in small formats. Once adjustments are made, they hold when when scaled up to larger prints. The frustrating part is that I didn't always have these problems. Somewhere along the line these issues got introduced. Something I haven't tried is uninstalling/reinstalling the Epson driver, because that just doesn't seem to make sense to me. I have considered replacing the printer with a new model, but I'm not sure there isn't something else in my workflow causing the problem. I'm having trouble letting go of the belief that there is something I can do to get back to making great prints on the first try with this printer. Thanks for any advice.