Peter gave me permission to mention that my IDimager Version 5 Workbook is now available. Information about its contents, key features and how to purchase it are available at www.HowToCatalog.com. If you have additional questions, please don't hesitate to contact me at Buckley@HowToCatalog.com

Dave,

If you have enabled "Store Hashes." you might have noticed the dialog box that appears after clicking "Run."  That dialog reminds you that "the Store Hashes setting will not be saved as part of the job."  I haven't seen Marc discuss this, but that appears to me to be a safety factor intentionally designed to prevent from accidentally storing a new hash the next time you run a job.

Due to that, you will be able to construct a preset that enables everythng you want except enabling the "Store Hashes" function.  That particular aspect of the job has to be manually set for reasons that I think are good.

If it's something else that's not being stored in your presets, be sure to check back in.  I am having no more issues with my folders not being stored; that's stilll working fine on my system.

--Mike

Marc,

Though it has been a short while since the folders were first being saved, they are now consistently being saved.  So long as that functionaly continues to work properly, I am going to move on and simply assume that this is Bill Gates's way of giving me his blessing.    Thanks for your concern and feedback!

Marc,

Yes, the "Default" job saves the folder list.  Considering that tonight for the first time all of my jobs are now saving the folder list, I don't know if that information is helpful. 

When I access the External Log, two windows appear containing the information shown below about the two sessions that occurred today.  They show activities only for today's date.  Is that what is supposed to be shown?


2009-Feb-19 02:08:44: App launched
2009-Feb-19 02:09:07: Verifying folder C:\Users\Homw\Pictures\Catalogued\Galleries\Location\North America\United States\Virginia\(folder name changed for security reasons)
2009-Feb-19 02:11:13: Processed folder C:\Users\Homw\Pictures\Catalogued\Galleries\Location\North America\United States\Virginia\(folder name changed for security reasons)(209 files)
2009-Feb-19 02:11:13: Waiting for process 988 in finishAllWorkers
2009-Feb-19 02:11:13: Waiting for process 4960 in finishAllWorkers
2009-Feb-19 02:11:13: Waiting for process 7536 in finishAllWorkers
2009-Feb-19 02:11:13: Waiting for process 4328 in finishAllWorkers
2009-Feb-19 02:11:13: Waiting for process 5908 in finishAllWorkers
2009-Feb-19 02:11:14: Waiting for process 3928 in finishAllWorkers
2009-Feb-19 02:11:14: Waiting for process 3264 in finishAllWorkers
2009-Feb-19 02:11:15: Waiting for process 3336 in finishAllWorkers
2009-Feb-19 02:18:09: Verifying folder C:\Users\Homw\Pictures\Catalogued\Galleries\Location\North America\United States\Virginia\(folder name changed for security reasons)
2009-Feb-19 02:20:09: Processed folder C:\Users\Homw\Pictures\Catalogued\Galleries\Location\North America\United States\Virginia\(folder name changed for security reasons)(209 files)
2009-Feb-19 02:20:11: Waiting for process 5332 in finishAllWorkers
2009-Feb-19 02:20:14: Waiting for process 5100 in finishAllWorkers
2009-Feb-19 02:20:14: Waiting for process 7468 in finishAllWorkers
2009-Feb-19 02:20:17: Waiting for process 6824 in finishAllWorkers
2009-Feb-19 02:20:17: Waiting for process 6488 in finishAllWorkers
2009-Feb-19 02:20:17: Waiting for process 3160 in finishAllWorkers
2009-Feb-19 02:20:17: Waiting for process 7040 in finishAllWorkers
2009-Feb-19 02:20:17: Waiting for process 5836 in finishAllWorkers
2009-Feb-19 02:20:46: Quitting

-----------

2009-Feb-19 22:14:38: App launched
2009-Feb-19 22:15:44: Verifying folder C:\Users\Homw\Pictures\Catalogued\Pictures not by Mike or Joellen
2009-Feb-19 22:15:44: Processed folder C:\Users\Homw\Pictures\Catalogued\Pictures not by Mike or Joellen (2 files)

Marc,

I explained in an earlier post that I suspected that the file count may not be being reported accurately.  I'm now convinced that that's the case.  For me, this is an unimportant issue.  I'm reporting it only in case you and others care about it. 

Take a look at the two job reports shown below.  Notice that, according to the reports, the second job processed one more file than the first job.  It also stored two more hashes. Yet the number of kept hashes remained unchanged.  That combination is a mathematical impossibility. 

The reports should indicate that the second job stored one hash, not two.

Job: Store the Hash in Catalogued
Start Date/Time: 2009-02-18 09:31:33
Stop Date/Time: 2009-02-18 09:35:09
Status: OK (interactive)

(No Suspected Invalid Images recorded.)

Run Log:

Verification Checks: Structure
Existing Hashes Kept (not rehashed)

Total processed: 7457
Total skipped: 917
Total hashes kept: 6539 (not verified)
Total valid: 1 (1 hashes stored)
Total invalid: 0Total indeterminate: 0
Total error: 0
Total hash error: 0

Valid JPEGs: 1

Skipped Extensions:
   DOC: 6
   XMP: 911

--------------------------------

Job: Store the Hash in Catalogued
Start Date/Time: 2009-02-19 00:59:02
Stop Date/Time: 2009-02-19 01:02:14
Status: OK (interactive)

(No Suspected Invalid Images recorded.)

Run Log:

Verification Checks: Structure
Existing Hashes Kept (not rehashed)

Total processed: 7458
Total skipped: 917
Total hashes kept: 6539 (not verified)
Total valid: 2 (2 hashes stored)
Total invalid: 0Total indeterminate: 0
Total error: 0
Total hash error: 0

Valid JPEGs: 2

Skipped Extensions:
   DOC: 6
   XMP: 911

--Mike

Marc,

If the confirming dialog box fails to appear again, I'll be sure to mention it.  However, I use IV almost daily and that happened only once.

--Mike

Marc,

About the job that stored a new hash in all of my files the first time I ran the new version rather than keeping the hashes: It occurred to me a long time after I wrote the post that the normal confirming dialog box informing whether or not the hashes will be overwritten did not appear.  Instead, immediately after clicking "Run," the job began without the confirming dialog box.

To compare two files of the same image, I would need to restore one of the files from the backup set.  I'd rather not have to go to the trouble, but I appreciate you offering to take a look at them.  If the issue persists, I'll eventually send some to you.

--Mike

Marc,

I've got some new issues.

After installing the new version, I ran a job on all of my images.  The instructions were to store a hash and keep the existing hashes.  It should have stored hashes on only 12 valid files.  Instead it stored the hashes on all 5592 valid files.  The job that should have taken only a few minutes took almost 35 minutes.  Is it possible that the new version is not supposed to recognize the existing hashes that had been created by the previous version?

The above job finished running at 3:03am.  (Yep, I worked in the middle of the night.) I ran the exact same job minutes later, beginning at 3:18am.  In between running the two jobs, I had no software loaded that could have added new image files.  However, the job stored 13 hashes.  In this case, I can think only of the following possibilities: the report is inaccurate or ImageVerifier did not recognize the 13 existing hashes. 

Any ideas?

--Mike

As I mentioned in the other thread, great job, Marc!

I noticed that the website documentation page still indicates in a red font that it is a beta version.  You'll want to change that.

--Mike

Thanks, Marc!  It is really a BIG help now that the results panel is now resizable.  In fact, I waited to examine a long filepath until after downloading the new version.

Thanks also for adding the flexibility to choose whether subfolders are to be verified.

It is probably just a coincidence, but after installing the new version the job folder is now being saved as part of the saved job in one of my three saved jobs.  One is better than none!   

You might remember that in my initial post to you, I reported Issue #1 as a situation that a lot of files were being returned after comparing hashes even though I had not edited the images or changed their metadata.  I have since learned that my DAM software changes a file when syncing the thumbnail with the database even though no other changes are made.  That explains why the two hashes are different and makes me believe that IV is working properly.

--Mike

No, it isn't blank.  Instead, it's a file path that usually is not the file path shown in the folders line.  As best as I can remember, if I run a job and bring up a different saved job, the filepath remains unchanged and causes me to manually edit the filepath.

Seeing that each file has a "folders" line, I did some more investigating.

One time when I opened IV and immediately brought up each of the saved jobs, the folders indeed changed as each job is brought up.  But only one time out of about six attempts.  Immediately after the one successful attempt, I then ran a job.  Having done that, the saved jobs no longer consistently brought up their respective saved folders.  Sometimes one job would and sometimes no jobs would.  Never did more than one of the jobs bring up their respective folders.

The only pattern I was able to detect is that the saved job that most often brings up its folder is the job file, "Store the Hash in Catalogued."  I was never able to get either of the other two jobs to bring up their respective folders.

--Mike

Randall,

Thanks for being so helpful in trying to figure out this stuff.  You and Marc are being so persistent that I've got to mention that it's really not a major problem for me that a saved job doesn't also save a filepath on my system.  My interest is mostly to inform Marc that his current documentation is at odds with how things seem to work on my system and, considering that the program is still in the beta status, I'm confident that he would want to know that.


It's located in the following path:  Desktop >> Homw (that's not a typo) >> AppData >> Roaming >> ImageVerifier (no space between the two words) >> IVMain


I have the Default fle and two additional files.   All of them are shown below in their entirety.

Default
Version   1
Date   Mon Feb 09 10:18:30 2009
ProcessNoExtension   0
TIFisRaw   0
CheckHashes   1
CheckStructure   0
VerifyRaws   1
IgnoreTIFFErrors   0
Folders   C:\Users\Homw\Pictures\Catalogued
ExtensionsJPEG   -JPG-JPEG-
ExtensionsTIFF   -TIF-TIFF-
ExtensionsRAW   -CR2-CRW-DCR-KDC-MRW-NEF-ORF-PEF-RAF-RAW-SRF-X3F-EEF-ARW-SR2-MEF-
ExtensionsDNG   -DNG-

Compare Hashes on Local Drive
Version   1
Date   Wed Feb 04 10:30:00 2009
ProcessNoExtension   0
TIFisRaw   0
CheckHashes   1
CheckStructure   0
VerifyRaws   1
IgnoreTIFFErrors   0
Folders   C:\Users\Homw\Pictures\Catalogued\Galleries\Location\North America\United States\Utah\Capitol Reef National Park
ExtensionsJPEG   -JPG-JPEG-
ExtensionsTIFF   -TIF-TIFF-
ExtensionsRAW   -CR2-CRW-DCR-KDC-MRW-NEF-ORF-PEF-RAF-RAW-SRF-X3F-EEF-ARW-SR2-MEF-
ExtensionsDNG   -DNG-

Store the Hash in Catalogue
Version   1
Date   Mon Feb 09 10:21:02 2009
ProcessNoExtension   0
TIFisRaw   0
CheckHashes   0
CheckStructure   1
VerifyRaws   1
IgnoreTIFFErrors   0
ExtensionsJPEG   -JPG-JPEG-
ExtensionsTIFF   -TIF-TIFF-
ExtensionsRAW   -CR2-CRW-DCR-KDC-MRW-NEF-ORF-PEF-RAF-RAW-SRF-X3F-EEF-ARW-SR2-MEF-
ExtensionsDNG   -DNG-
Folders   C:\Users\Homw\Pictures\Catalogued\Galleries\Family\Matthew Jr\Johns Hopkins NICU

Thanks again!

--Mike

Marc,

You're using a Vista Business edition but mine is Vista Home Premium.  I have no idea if that could matter.

Thanks to you and Randall for looking into this!

        

--Mike