Now the bad news. Often I am unable to use XnView. Apparently because the number of captures is too high?
I get a message while the thumbnails are loading:
"XnView for Windows has stopped working.
Windows is checking for a solution to the problem..."
Followed by this message:
"XnView for Windows has stopped working.
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
There is another freeware program, Vallen JPegger, that I switch to using when XnView won't finish loading the captures. JPegger is a very nice program in it's own right, but it lacks the robust sorting of XnView, so when I have to use it for this purpose I spend a lot more time reviewing. XnView is definitely a time saver for this task.
I checked, "Use high quality" is unmarked in Options.
Caching was on, so I turned it off and emptied it. With it off, more thumbnails load and faster, but XnView still stops before it can finish a high number.
CPU and memory do not seem exceptional when XnView stops working. CPU for XnView is around 47% with around 80% total utilization (E6850 3ghz Core2 Duo). 6 Gig memory (Win7 Pro SP1 64-bit) that climbs from 2.0G to 3.8G at the time XnView stops working. I'm looking at Process Explorer by Windows Sysinternals for these figures.
A side note. Some time back I put in a feature request for a date-range with time-range (e.g. date/time-from through date/time-to), please forgive a shameless plug now for my suggestion

Please let me know what else I can check or I can do? Thank you for any help.
Kind regards,
--appyface